- Más nuevo
- Más votos
- Más comentarios
Hi
Choose IP addresses as the target group type. This is crucial because: Dynamic IPs: ECS tasks using awsvpc networking mode have dynamic private IP addresses assigned to their elastic network interfaces (ENIs). IP-Based Targeting: The ALB can effectively route traffic to your tasks' ENIs using their IP addresses.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-load-balancing.html
For services with tasks using the awsvpc network mode, when you create a target group for your service, you must choose ip as the target type, not instance. This is because tasks that use the awsvpc network mode are associated with an elastic network interface, not an Amazon EC2 instance
Add on Info: I would like to add one of the point i have experienced recently with ECS, You may have interfaces issues because based on the instance types you will have less number of the network interface which may affect your applications so here is the solution for this,
Enable trunking Enable the ECS elastic network interface trunking feature to increase the number of network interfaces that can be attached to supported EC2 container instance types. You must meet the following prerequisites before you can launch a container instance with the increased network interface limits:
- Your account must have the AWSServiceRoleForECS service-linked role for ECS.
- You must opt into the awsvpcTrunking account setting.
https://aws.amazon.com/blogs/compute/optimizing-amazon-ecs-task-density-using-awsvpc-network-mode/
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 4 meses
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años