Bind task to specific IP address #426
Comments
|
IIUC you are asking on how can ECS tasks running on EC2 instances support ENIs. We are currently gathering requirements to support this and would love to understand more about your use-case. Is your case to assign one IP per task and have that IP constrained by policies defined in the VPC/Subnet/Security Groups? In the current system even if we support passing in IP in RunTask API, you need to know IP beforehand which is not true in RunTask case which doesn't take containerInstance as input. May be you meant StartTask API. Even in that scenario it is interesting to understand more about the end-to-end flow. Thanks for bringing this up. -kiran |
|
@abatsakis We're working on attaching ENIs to tasks and allowing IP addresses per task. Does the proposal in #701 address your use-case? |
---* Motivation *--- By hardcoding the host IP as 0.0.0.0, the agent is removing the ability for customers to specify specific host IP addresses (such as when there are multiple network interfaces). By default, the docker daemon defaults to 0.0.0.0, but this value may be overridden by launching the daemon with a --ip flag. https://docs.docker.com/engine/reference/commandline/dockerd/ This also has an implication for the CloudWatch Events published by ECS. Specifically, prior to this change the 'bindIP' field in the ECS Task Status events always contains '0.0.0.0'. This change will benefit the following customer use cases: * aws#426 * https://forums.aws.amazon.com/thread.jspa?threadID=173250 * https://serverfault.com/questions/695393/amazon-ecs-docker-binding-container-to-specific-ip-address ---* Detailed Description *--- Do not explicitly set the HostIP property when starting containers and instead defer to the daemon's default.
---* Motivation *--- By hardcoding the host IP as 0.0.0.0, the agent is removing the ability for customers to specify specific host IP addresses (such as when there are multiple network interfaces). By default, the docker daemon defaults to 0.0.0.0, but this value may be overridden by launching the daemon with a --ip flag. https://docs.docker.com/engine/reference/commandline/dockerd/ This also has an implication for the CloudWatch Events published by ECS. Specifically, prior to this change the 'bindIP' field in the ECS Task Status events always contains '0.0.0.0'. This change will benefit the following customer use cases: * #426 * https://forums.aws.amazon.com/thread.jspa?threadID=173250 * https://serverfault.com/questions/695393/amazon-ecs-docker-binding-container-to-specific-ip-address ---* Detailed Description *--- Do not explicitly set the HostIP property when starting containers and instead defer to the daemon's default.
|
@abatsakis We've released task networking for containers as proposed in #701. I'm closing this issue since we haven't heard back, but feel free to let us know if this addresses your use case. |
Hi all,
I was wondering if there are any plans in supporting the binding of a task to a specific IP address on the host that can e.g. provided at RunTask time similar to docker's -p IP:host_port:container_port
This is very handy for instances with multiple interfaces on different subnets
The text was updated successfully, but these errors were encountered: