1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
Please check the Lambda function logs from CloudWatch Logs.
I saw the same error in a GitHub issue in the past, and at that time there was no network route to access S3 from Lambda, resulting in an error.
Additionally, if you are accessing S3 using a VPC endpoint, you must ensure that Lambda and S3 are in the same region.
https://github.com/awslabs/aws-athena-query-federation/issues/288
Relevant content
- asked 2 years ago
- asked 3 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 4 months ago