If I'm running on AWS App Mesh / ECS (not Kubernetes) - where does my application get the address/port of the local (it's own) Envoy sidecar in order to communicate with other services on the mesh?
Given this is ECS (Fargate) and I'm running with dynamic ports, it's not as though I can call e.g. localhost:some_known_port_here.
So, when my app goes:
my app (1) -> local envoy sidecar (2) -> remote envoy sidecar (3) -> remote app (4)
How do I make the hop from 1 to 2? Not sure where that address comes from.
This can not be through App Mesh now. Application ports are specified in the configuration so that the routing table is setup to not forward the traffic on those ports back to the Envoy but to the App.
How are you using dynamic ports today? Why wouldn't awsvpc mode wouldn't fit your need here?
With ECS task networking mode multiple containers(tasks) can run on the same port in a given ECS instance. There should not be any collision.
If you need support for dynamic ports, you can open a feature request here: https://github.com/aws/aws-app-mesh-roadmap/issues