- Newest
- Most votes
- Most comments
Based on your description, it appears you've done all the necessary steps to share your Lake Formation resources with Account B, and you've verified that you can access and query these resources from Athena.
However, not seeing the tables in QuickSight might be due to a couple of potential issues, including permissions and the QuickSight data source setup. Here's a few things you can check:
-
Lake Formation permissions: Lake Formation resources permissions should be correctly set. Please check whether the IAM role associated with QuickSight in Account B has the necessary permissions to access the Lake Formation resources. If it doesn't, you'll need to add these permissions.
-
QuickSight data source: When setting up the data source in QuickSight, make sure you've chosen Athena as the source and provided the correct database name. If everything is set correctly but it's still not working, try to create the data source again.
-
Cross-account setup: It's important to ensure that all your cross-account configurations are correctly set up. Make sure you have shared the resources from Account A with Account B and that the resource link has been created in Account B.
-
QuickSight IAM role permissions: Check the IAM role that QuickSight is using. This role needs to have quicksight:AthenaAccess and s3:GetObject, s3:ListBucket permissions on the data source (bucket) that you're trying to access.
-
Athena settings in QuickSight: If you've set up a custom Athena workgroup, make sure that you've selected it in the Athena settings in QuickSight.
-
Time taken for permissions to propagate: Sometimes, there may be a delay in the propagation of permissions across different AWS services. So, if you've just set the permissions, you might need to wait a bit before they take effect.
Thank you for your answer. The above issue has been resolved. The issue was with the lake formation permission. The console was not working, so I had to use the CLI to grant permission to the QuickSight IAM Role. Granting permission to the QuickSight User was also quite complicated.
Relevant content
- asked 8 months ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago