- Newest
- Most votes
- Most comments
It's not clear from the question but: Is the Lambda running in the context of a VPC? If so, are you using the VPC Route 53 DNS resolver?
If the answer to the second question is "yes" I'd suggest creating a support ticket because there is some other issue there that isn't obvious.
If you're using your own DNS resolver within the VPC then I would check the logs on that and see if it is experiencing any issues.
If the answer to the first question is "no" then I'd also suggest creating a support ticket.
Hi there! My hunch is your facing some sort of DNS quota issue since its intermittent. Have you looked at this troubleshooting guide? https://aws.amazon.com/premiumsupport/knowledge-center/vpc-find-cause-of-failed-dns-queries/
That what I found online as well but it doesn’t make sense as those failing dns queries are not during peak lambda executions. So weird…
Relevant content
- asked 8 months ago
- asked 4 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Hey, thanks for your response! The lambda is running under the default VPC (the one that is created with each AWS Account) that allows internet access etc, no custom DNS resolver is running under this VPC.
The default VPC generally has public subnets only; if you launch a Lambda function into a public subnet it does not get a public/elastic IP. In order to allow the Lambda function to communicate with public resources you will need to create private subnets, a NAT Gateway and use those private subnets for Lambda.