DNS resolution with VPC based OpenSearch and Lambda
I've deployed an OpenSearch Domain and Lambda into a new VPC. The VPC has DNS hostnames and resolution enabled.
I've added a OpenSearch VPC Endpoint which is allowing me to connect to the OpenSearch UI so generally happy that the domain is up and running. However, I've put together a simple python lambda to try and post documents to the domain but when it tries to post, it fails with Name or Service not known.
I've then amended the lambda to do a DNS lookup and that is also failing - when I replace the hostname with google.com, it does the lookup fine.
Finally, I enabled the VPC DNS logging - when the lambda runs, I can see the request but the answers section is empty.
Any suggestions on how I can allow the lambda to resolve the hostname for the OpenSearch domain?
- Newest
- Most votes
- Most comments
Not sure if it's bad form to answer your own question ;) If anyone comes across something similar make sure no-one has created a hosted zone in route53 with the service domain i.e. <region>.1.es.amazonaws.com
Relevant content
- Accepted Answer
asked 3 years ago - asked 5 months ago
- Accepted Answerasked 8 months ago
- asked a year ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
The response is not super clear. Do you mean that you had hosted zone with "<region>.1.es.amazonaws.com" ? How did you resolve the issue ? By deleting the hosted zone ?