1 Answer
- Newest
- Most votes
- Most comments
0
This is most probably due to access that your ID has (which Athena uses) versus the Glue Service Role that you have assigned to Glue Databrew. The service role has all the accesses needed. Check if you have these permissions:
"glue:GetDatabases", "glue:GetDatabase","glue:GetTables", "glue:GetPartitions","glue:GetPartition","glue:GetTable"
Do you have Lake formation turned on? If so, you would have to provide Database level and table level access from there.
In some cases, this could be due to compatibility of the table such as XML table - https://aws.amazon.com/premiumsupport/knowledge-center/athena-glue-tables-not-visible/
answered a year ago
Relevant content
- Accepted Answerasked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a month ago
Checking my ID I have the AWSGlueServiceRole which holds the permission "glue:*" and we don't have Lake formation turned on. Looking into the syntax of Athena, would the Database and table name being Capitalized be the issue?