0

I have an ECS cluster setup with a container that runs a microservice hosting a public and private HTTP server.

I have the public HTTP server being connected through an Elastic Load Balancer which is working correctly, however the internal HTTP server is being routed via AWS Cloud Map and Route 53 with a private hosted zone.

AWS Cloud Map finds the instance correctly, however when trying to access the private endpoint from another ECS task I get a no such host error.

Any suggestions on what could be the cause?

Thanks!

Myles S
  • 1
  • For anyone coming across this with the same issue, I managed to fix myself. I fixed this issue (for my use case) by changing the ECS service's DNS record to be A, and then allowing inbound connections from my internal network in the security group. – Myles S Nov 12 '21 at 18:51

1 Answers1

1

For me it's resolved that DNS Hostnames and DNS resolution are enabled in your VPC settings,

Go to your VPC dashboard then press on "Actions" button then

Press Edit DNS hostnames

Edit DNS hostnames

Check the "Enable" checkbox

Enable DNS hostnames

and same goes for DNS resolution.

Mawardy
  • 3,618
  • 2
  • 33
  • 37