1 Answer
- Newest
- Most votes
- Most comments
1
Hi,
Please verify that you are using the correct lambda execution role.
Please refer to the below articles for more information: https://aws.amazon.com/premiumsupport/knowledge-center/schedule-query-athena/ https://docs.aws.amazon.com/athena/latest/ug/federated-query-iam-access.html https://docs.aws.amazon.com/quicksight/latest/user/troubleshoot-connect-athena.html
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 9 months ago
Thanks for your information. The issue has been resolved after adding below policy (when trigger athena.startQueryExecution(...), it will invoke a Athena's lambda connector): { "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "lambda:InvokeFunction" ], "Resource": [ "arn:aws:lambda:us-west-2:accountID:function:test-datasource-connector" ] } ] }