1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 4 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 4 Jahren
- AWS OFFICIALAktualisiert vor 3 Monaten
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" ] } ] }