2

Amazon ECS Service Discovery makes it possible for an ECS service to automatically register itself with a predictable and friendly DNS name in Amazon Route 53, for example backend.corp

However, assuming the use case of a web based app, host is not enough to communicate with service - also port number is required, especially when using dynamic port allocation on host(fixed container port is mapped to random host port)

How to manage dynamic port allocation with ECS Service Discovery? Sure, it is possible to use well-knows ports, but is limits number of hosts docker image can be run on.

Fedor
  • 559
  • 1
  • 7
  • 19

1 Answers1

3

ECS Service Discovery will register an SRV record for each task that is a combination of the Container Name and the Port (See Service Discovery Considerations). You can query these values to find the list of containers to which you can connect.

Update:

How you query DNS will be very dependant on your specific project, and the language and framework involved. In Java, for example, you'd use JNDI, in python you could use the dnspython library, and node, you'd probably use the built in dns module.

Jamie Starke
  • 8,776
  • 3
  • 38
  • 58
  • thx, for your response, Jamie. When can I find an example how to query Container Name and Port from my server-side app in docker? Unfortunately, AWS ECS Reference architecture(pet store) does not use ECS Service Discovery – Fedor Oct 01 '18 at 11:06
  • Assuming you're following the [Java Microservices example](https://aws.amazon.com/blogs/compute/deploying-java-microservices-on-amazon-ec2-container-service/), I'd check out the [Get DNS SRV Record with JNDI](https://docs.oracle.com/javase/7/docs/technotes/guides/jndi/jndi-dns.html). I've updated the answer with examples for other languages as well. – Jamie Starke Oct 02 '18 at 14:55