DAS-C01 · Question #49
A data analyst is using Amazon QuickSight for data visualization across multiple datasets generated by applications. Each application stores files within a separate Amazon S3 bucket. AWS Glue Data…
The correct answer is B. Edit the permissions for the new S3 bucket from within the Amazon QuickSight console. Amazon QuickSight requires explicit, per-bucket S3 permissions to read data when using Athena as a data source. When a new S3 bucket is added, QuickSight does not automatically gain access to it. The fix is to go into the QuickSight console under 'Security & Permissions' and…
Question
A data analyst is using Amazon QuickSight for data visualization across multiple datasets generated by applications. Each application stores files within a separate Amazon S3 bucket. AWS Glue Data Catalog is used as a central catalog across all application data in Amazon S3. A new application stores its data within a separate S3 bucket. After updating the catalog to include the new application data source, the data analyst created a new Amazon QuickSight data source from an Amazon Athena table, but the import into SPICE failed. How should the data analyst resolve the issue?
Options
- AEdit the permissions for the AWS Glue Data Catalog from within the Amazon QuickSight console.
- BEdit the permissions for the new S3 bucket from within the Amazon QuickSight console.
- CEdit the permissions for the AWS Glue Data Catalog from within the AWS Glue console.
- DEdit the permissions for the new S3 bucket from within the S3 console.
How the community answered
(37 responses)- A8% (3)
- B78% (29)
- C3% (1)
- D11% (4)
Explanation
Amazon QuickSight requires explicit, per-bucket S3 permissions to read data when using Athena as a data source. When a new S3 bucket is added, QuickSight does not automatically gain access to it. The fix is to go into the QuickSight console under 'Security & Permissions' and grant QuickSight access to the specific new S3 bucket. The Glue Data Catalog itself was already updated and is not the issue. Editing S3 bucket permissions directly in the S3 console (Option D) does not grant QuickSight service-level access; that must be done within QuickSight's own permission management interface.
Topics
Community Discussion
No community discussion yet for this question.