- Newest
- Most votes
- Most comments
Hello.
I think there are two ways.
The first method is to connect ELB to an ECS service and access from other ECS services via ELB.
If you are someone who regularly sets up ELB, I think you will be able to set it up right away as it is not that difficult.
Although only when using ALB, it can also support path-based routing and host-based routing.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html
The second method is to use ECS Service Connect or ECS service discovery.
Service Discovery registers the task's IP in Route53's private hosted zone via Cloud Map.
It is possible to communicate directly with tasks based on the results of name resolution in Route53.
Service Connect allows you to define endpoints for your services and communicate through them, eliminating the need to directly manage service addresses and port numbers.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/interconnecting-services.html
You can use AWS Lattice service: https://aws.amazon.com/blogs/containers/build-secure-application-networks-with-vpc-lattice-amazon-ecs-and-aws-lambda/ https://docs.aws.amazon.com/eks/latest/userguide/integration-vpc-lattice.html
Relevant content
- App with 2 microservices - should they run in two ECS clusters or two services in single ECS clusterAccepted Answerasked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 4 months ago