Skip to content

quicksight integration with S3Tables via Athena

2

Hello, we need to connect QuickSight to lake formation catalog in order to access Iceberg tables stored in S3Tables service. Data is in s3tables buckets, managed via Lake Formation. Our Glue does not have S3Tables catalogs mapped. We can access the data with Athena regularly without any problem, both via GUI and via python using athena hook. the QuickSight account is set and aws-quicksight-service-role-v0 has all read and list permissions set for Athena,Glue and Lake formation. in lake formation also set the permissions to describe,read, select for all datasets/namespaces/tables. We still not able to access the data. Are there any constraints that limits the data access to iceberg tables in s3tables service from QuickSight via Athena connector? example query:* select * from "s3tablescatalog/some_catalog"."some_namespace"."some_table"* --> works with Athena GUI and from python via Athena Hook Who can help me doing this connection? Thank you.

  • Facing this too — Athena works perfectly, but QuickSight can’t reach Iceberg data in S3Tables (LF permissions all granted).

    Any AWS team updates on QuickSight -> S3Tables/Iceberg support?

asked 9 months ago441 views

1 Answer
-3

To connect QuickSight to S3 Tables via Athena, there are several specific permissions and configurations you need to set up beyond the standard service role permissions.

Based on your description, while you've set up the aws-quicksight-service-role-v0 with permissions for Athena, Glue, and Lake Formation, there are additional QuickSight-specific permissions required:

  1. You need to identify the QuickSight admin user's ARN and grant Lake Formation permissions specifically to this user/ARN. You can find this by running:
aws quicksight list-users --aws-account-id <AWS Account ID> --namespace default --region <AWS Region>
  1. In Lake Formation, you need to grant permissions to this QuickSight admin user ARN:
  • Navigate to Lake Formation console > Data permissions > Grant
  • Under Principals, select "SAML users and groups" and add the QuickSight admin user's ARN
  • Select "Named Data Catalog Resources" and grant permissions at both:
  • Database level: Select the S3 Tables catalog and database
  • Table level: Select the S3 Tables catalog, database, and table
  1. In QuickSight, ensure you've authorized access to both Athena and the specific S3 buckets:
  • In QuickSight console, go to your profile > Manage QuickSight > Security & Permissions
  • Under "QuickSight access to AWS services", select Manage
  • Enable Athena and specify the S3 bucket that contains your data

Common issues that might be causing your problem:

  • The QuickSight service role permissions are different from the QuickSight user permissions in Lake Formation
  • Table or column names might contain capital letters, which can cause errors with S3 Tables
  • The QuickSight admin user specifically needs Lake Formation permissions, not just the service role

If you're still encountering issues after these steps, check for error messages in QuickSight when attempting to connect, as they can provide more specific guidance on what permissions might be missing.
Sources
Analyzing Amazon S3 Metadata with Amazon Athena and Amazon QuickSight | AWS Storage Blog
How to consume tabular data from Amazon S3 Tables for insights and business reporting | AWS Storage Blog
Use the solution - Amazon Marketing Cloud Insights on AWS
Querying Amazon S3 tables with Athena - Amazon Simple Storage Service
Visualizing table data with Quick Suite - Amazon Simple Storage Service

answered 9 months ago

  • Those articles cover either Athena with S3Tables (which we have no issues) or QuickSight with S3 Buckets that is not the same as S3Tables buckets. The question is a new question!

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.