This text will be hidden
This text will be hidd
Hi @alsarris
Welcome to the Quick Sight community!
In Quick Sight console, go to Manage Quick Sight ->Security & permissions, check that Athena and the right S3 buckets are authorized for Quick Sight. If managed by Lake Formation, grant proper Lake Formation permissions for Quick Sight to Glue tables/databases.
Please refer to the below Quick Sight documentations and community posts this might be helpful for you.
Thank you @xclipse for your quick response.
I have attempted the solution offered on first community post which is to add the following inline policy to aws-quicksight-service-role-v0 service role
{
“Version”: “2012-10-17”,
“Statement”: [
{
“Effect”: “Allow”,
“Action”: [
“glue:GetSchemaVersion”,
“glue:ListSchemaVersions”
],
“Resource”: [
“*”
]
}
]
}
Unlike Sewen, it did not work for me.
I also validated the second community link, and still cant see the columns.
QS: Check Athena workgroup is chosen correctly.
Athena: Check that the workgroup is set up correctly and points to the right bucket.
Identity policies: Check what is attached on your QS service role looks right. (Covers S3 and KMS)
Resource policies: Check for a deny anywhere on S3 bucket policy or KMS key policy
SCPs: Are there any blocking SCPs perhaps.
However, I was not able to add location and classification for tables on Glue per the advise from second community post. Referring to:
“General AWS Troubleshooting docs for the issue. One odd thing I found is that the Glue table must have a TableType defined in the schema”
Hi @alsarris
Could you please try correcting the AWS Glue table metadata and check if this resolves the missing column issue in Quick Sight for Athena sourced tables. Specifically, confirm that the Glue table contains the required metadata attributes like TableType in the schema definition. Missing or incorrect metadata may prevent Quick Sight from loading column information.
Please refer to the below documentations this might be helpful for you.
Hi @Xclipse Looking at both documents, I already have both policies AmazonAthenaFullAccess and AWSQuicksightAthenaAccess attached to my service role’s . The first link provided seems to be for analysis, and I cant get to an analysis before I’m able to fix and save a dataset.
With respect to assigning metadata attributes like TableType in the schema definition on Glue table, I’m not able to perform that, nor am I able to find proper guidance that I can follow exactly and amend, seems to be missing steps, or cant follow the instruction as its not available to me.
Also when I try to provide permission to the table columns within lake formation, I’m receiving the following error: “Grant permissions failed | Error granting catalog permissions to ARNs: arn:aws:quicksight:us-east-1:66317xxxxxxx:user/default/Admin/alsarris-Isengard. Unexpected error has occurred trying to grant permissions. Permissions modification is invalid.” This happens with all other IAM roles I’ve tried such as:
arn:aws:iam::66317xxxxxxx:role/Admin
arn:aws:iam::66317xxxxxxx:role/service-role/aws-quicksight-service-role-v0
arn:aws:iam::66317xxxxxxx:role/QS-Athena-access
Hi @alsarris
Sorry, I’m out of ideas. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!