1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
2
Hello.
The subnet where the ECS task is deployed should be a private subnet.
Also, make sure that there is a route to the NAT Gateway in the route table of the deployed subnet.
The configuration is similar to the following document.
https://docs.aws.amazon.com/AmazonECS/latest/bestpracticesguide/networking-outbound.html#networking-private-subnet
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 10 meses
- OFICIAL DE AWSActualizada hace 10 meses
Thanks for you answers, actually I also try a private subnet sir, It able to access to global via nat but the static ip still not get on ecs task
As described in this document, it is not possible to set an Elastic IP directly to a task. https://repost.aws/knowledge-center/ecs-fargate-static-elastic-ip-address
In other words, if the destination has IP address restrictions or other restrictions, it is necessary to register to allow the NAT Gateway's IP address.