- Newest
- Most votes
- Most comments
After contacting AWS support, I found the solution, so I'm posting it here in case anyone else encounters this problem in the future. The CatalogId is the AccountID, and not the name of the Catalog as seen in the Athena Console. The solution was to replace the third line of the template I provided:
Type: AWS::Glue::Table
Properties:
CatalogId: !Sub '${AWS::AccountId}'
DatabaseName: !Sub 'db_{BucketName}'
TableInput:
Name: 'tbl_${LocalName}'
....
Start at 'Granting Cross Account Access' in the AWS Glue Developer Guide https://docs.aws.amazon.com/glue/latest/dg/cross-account-access.html#cross-account-limitations. Either resource policy or an IAM role policy. I can't tell from your Cloudformation snippet how your current access is configured.
Then check the limitations and access configurations in 'Fine-grained access to databases and tables in the AWS Glue Data Catalog' from the Amazon Athena User Guide. https://docs.aws.amazon.com/athena/latest/ug/fine-grained-access-to-glue-resources.html
Relevant content
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
