- Newest
- Most votes
- Most comments
To resolve the connection issue between QuickSight and your S3 bucket, you need to explicitly grant QuickSight permission to access your S3 bucket. This is required even when both services are in the same AWS account.
Here's how to fix the issue:
- In the QuickSight console, click on your profile icon in the top-right corner
- Select "Manage QuickSight"
- Choose "Security & permissions"
- Under "QuickSight access to AWS services", click "Manage"
- Select "Select S3 buckets"
- On the "Select Amazon S3 buckets" screen, find and select your bucket "yucheng816"
- Click "Select buckets" to confirm your selection
- Click "Finish" and "Save" to apply the changes
After granting these permissions, try creating your dataset again by uploading your manifest file.
The error you're seeing isn't related to the S3 bucket's public access settings. The "Block Public Access" setting prevents public internet access to your bucket, but it doesn't affect service-to-service permissions within AWS. QuickSight needs explicit permission to access your S3 bucket regardless of whether they're in the same account.
If you continue to have issues, verify that:
- Your manifest file format is correct
- The S3 paths in your manifest file are accurate
- You're referencing your bucket directly with the proper syntax (which you are with "s3://yucheng816/dummy/dummy.csv")
Sources
I can't connect to Amazon S3 - Amazon QuickSight
Datasets using S3 files in another AWS account - Amazon QuickSight
Integrate private Amazon S3 hosted images with Amazon QuickSight dashboards | AWS Business Intelligence Blog
answered 10 months ago
Relevant content
asked 3 years ago
asked 2 months ago
