1 Answer
- Newest
- Most votes
- Most comments
0
SES integration with Lambda within a VPC is supported. Can you check to see:
- If the VPC Endpoint for SES is correctly configured and the security groups/route tables allow outbound access.
- If the Lambda function's VPC subnet and security group settings allow outbound access to the SES VPC Endpoint.
- Validate the IAM permissions for the Lambda function to access SES.
- Try testing the SES API connectivity from within the VPC, such as from an EC2 instance, to isolate if it's a VPC networking issue or an issue with the Lambda function itself.
- If none of the above works, and you still have timeouts, try changing the Lambda function's timeout or increasing it's memory allocation to give it enough resources to complete the SES API call.
- You can open up an AWS support case, if you are still having challenges https://docs.aws.amazon.com/awssupport/latest/user/getting-started.html
- I also see that you are reading from SQS queue. All the above recommendations holds true for the SQS as well. IAM permissions (lambda has necessary IAM role or IAM permissions), security groups(VPC endpoint - lambda & SQS) etc.
- Use a longer visibility timeout on the SQS queue to give the Lambda function more time to process messages.
Relevant content
asked 4 years ago
asked a year ago
asked 2 years ago
- AWS OFFICIALUpdated a year ago
