1 Answer
- Newest
- Most votes
- Most comments
1
Hi, you probably have not defined some required credentials for QuickSight to access your S3 bucket: see https://docs.aws.amazon.com/quicksight/latest/user/troubleshoot-connect-S3.html on how to create those credentials
Also, see remark on this page
We strongly recommend that you make sure that your manifest file is valid.
If Amazon QuickSight can't parse your file, it gives you an error message.
That might be something like "We can't parse the manifest file as valid JSON"
or "We can't connect to the S3 bucket."
It is exactly what you have
Best,
Didier
Relevant content
- asked 2 years ago
AWS OFFICIALUpdated a month ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Hi @Didier, thanks for your direction. I have already implemented the allow access form both sides i.e. allowed S3 bucket operations on the Quicksight admin role and added bucket policy on the specific bucket to allow Quicksight service to access the bucket and its objects. Not sure what else can I do? Also parsed the maifest file using json validator and is valid. The error I keep getting is We can’t connect to this S3 bucket. Make sure any S3 buckets you specify are associated with the AWS account used to create this QuickSight account. Looking at error details :- sourceErrorCode: MANIFEST_NO_FILES_FOUND sourceErrorMessage: Input Manifest cudos_dataset does not contain any valid URIs