kozlone's questions

The question is pretty straightforward but a little background always could be helpful. I need to get a container id from the container itself, and the value of it will be used as a logfile name. According to the docs ECS_CONTAINER_METADATA_URI_V4 is injected to each container. But when I'm connection to a Fargate hosted containers through SSH, there is no such variable. Which is expected and I had created the topic for that before just to make sure my guess is correct.

So, is there a way to get the value of ECS_CONTAINER_METADATA_URI_V4

I have configured ECS containers. Everything works, however when I'm connecting to a container through SSH, there are no environment variables that are defined in a task definition. Is there a way to persist them?

Currently, I'm trying to figure out how to configure communication between ECS services. I'm planning to have the following setup:

1. Backend service
2. Fronted service
3. One application load balancer

I have the following options in my mind:

1. Configure 2 target groups for ALB and forward requests according to path. For instance, alb.amazonaws.com/backend/ will forward a request to the backend-target-group which will supply the request to the backend ECS tasks.
2. In each ECS task run a script which will retrieve IP addresses of running tasks using AWS cli and service discovery. Not sure if this will work and it is relatively hard to test.

None of them seems like the right way to do it. I don't want to use a separate ALB for each service because of financial limits. What I'm thinking of is some kind of internal DNS name for ECS services. I've examined the following links, but can't figure out how to apply it to my case.

• https://docs.aws.amazon.com/cloud-map/latest/dg/what-is-cloud-map.html
• https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html
• https://aws.amazon.com/blogs/aws/amazon-ecs-service-discovery/
• https://aws.amazon.com/blogs/compute/task-networking-in-aws-fargate/

Related issue: AWS ECS container communication

So, ideally what I would like to achieve is: having an internal DNS name for the backend services and send requests from the fronted services to the backend.