1 Answer
- Newest
- Most votes
- Most comments
1
There are a few things that could cause this. you could try these steps:
- Did you provide read permissions to your S3 bucket for the user - both at bucket and inside the bucket (eg."Resource": ["arn:aws:s3:::artless-reports-prod", "arn:aws:s3:::artless-reports-prod/"])? You can start with "s3:Get" and "s3:List*".
- Are your bucket and objects encrypted? If your bucket and objects are encrypted, I would make sure Lakeformation has the proper access to use the KMS Key (KMS Key Policy).
- Do you use Lakeformation? if so, has the data location registered for the datalake bucket/folder in LakeFormation?
- If the bucket is owned by the same account you are querying from, check out https://docs.aws.amazon.com/athena/latest/ug/s3-permissions.html.
- For cross account access, check https://docs.aws.amazon.com/athena/latest/ug/cross-account-permissions.html
- For federated queries, check https://docs.aws.amazon.com/athena/latest/ug/federated-query-iam-access.html
Reference: https://aws.amazon.com/premiumsupport/knowledge-center/access-denied-athena/
answered 3 years ago
Relevant content
- asked 4 years ago
- asked 3 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 4 months ago
