Verifying Amazon ECS stopped task connectivity - Amazon Elastic Container Service
Testing the task connectivityFixing VPC endpoint issuesFixing network issues
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Verifying Amazon ECS stopped task connectivity

There are times when a task stops because of a network connectivity issue. It might be an intermittent issue, but it is most likely caused because the task cannot connect to an endpoint.

Testing the task connectivity

You can use AWSSupport-TroubleshootECSTaskFailedToStart runbook to test the task connectivity. When you use the runbook, you need the following resource information:

  • The task ID

    Use the ID of the most recent failed task.

  • The cluster that the task was in

For information about how to use the runbook, see AWSSupport-TroubleshootECSTaskFailedToStart in the Amazon Systems Manager Automation runbook reference.

The runbook analyzes the task. You can view the results in the Output section for the following issues that can prevent a task from starting:

  • Network connectivity to the configured container registry

  • VPC endpoint connectivity

  • Security group rule configuration

Fixing VPC endpoint issues

When the AWSSupport-TroubleshootECSTaskFailedToStart runbook result indicates the VPC endpoint issue, check the following configuration:

Fixing network issues

When the AWSSupport-TroubleshootECSTaskFailedToStart runbook result indicates a network issue, check the following configuration:

Perform the following configuration based on the runbook:

  • For tasks in public subnets, specify ENABLED for Auto-assign public IP when launching the task. For more information, see Running an application as an Amazon ECS task.

  • You need a gateway to handle internet traffic. The route table for the task subnet needs to have a route for traffic to the gateway.

    For more information, see Add and remove routes from a route table in the Amazon Virtual Private Cloud User Guide.

    Gateway type Route table destination Rout table target
    NAT 0.0.0.0/0 NAT gateway ID

    Internet gateway

    		 0.0.0.0/0 Internet gateway ID

  • If the task subnet has a network ACL, the following ACL rules are required:

    • An outbound rule that allows traffic that allows traffic on ports 1024-65535.

    • An inbound rule that allows TCP traffic on port 443.

    For information about how to configure rules, see Control traffic to subnets using network ACLs in the Amazon Virtual Private Cloud User Guide.

Perform the following configuration based on the runbook:

  • Choose DISABLED for Auto-assign public IP when launching the task.

  • Configure a NAT gateway in your VPC to route requests to the internet. For more information, see NAT Gateways in the Amazon Virtual Private Cloud User Guide.

  • The route table for the task subnet needs to have a route for traffic to the NAT gateway.

    For more information, see Add and remove routes from a route table in the Amazon Virtual Private Cloud User Guide.

    Gateway type Route table destination Rout table target
    NAT 0.0.0.0/0 NAT gateway ID

  • If the task subnet has a network ACL, the following ACL rules are required:

    • An outbound rule that allows traffic that allows traffic on ports 1024-65535.

    • An inbound rule that allows TCP traffic on port 443.

    For information about how to configure rules, see Control traffic to subnets using network ACLs in the Amazon Virtual Private Cloud User Guide.

Perform the following configuration based on the runbook:

  • Choose Turn on for Auto assign IP under Networking for Amazon EC2 instances when you create the cluster.

    This option assigns a public IP address to the instance primary network interface.

  • You need a gateway to handle internet traffic. The route table for the instance subnet needs to have a route for traffic to the gateway.

    For more information, see Add and remove routes from a route table in the Amazon Virtual Private Cloud User Guide.

    Gateway type Route table destination Rout table target
    NAT 0.0.0.0/0 NAT gateway ID

    Internet gateway

    		 0.0.0.0/0 Internet gateway ID

  • If the instance subnet has a network ACL, the following ACL rules are required:

    • An outbound rule that allows traffic that allows traffic on ports 1024-65535.

    • An inbound rule that allows TCP traffic on port 443.

    For information about how to configure rules, see Control traffic to subnets using network ACLs in the Amazon Virtual Private Cloud User Guide.

Perform the following configuration based on the runbook:

  • Choose Turn off for Auto assign IP under Networking for Amazon EC2 instances when you create the cluster.

  • Configure a NAT gateway in your VPC to route requests to the internet. For more information, see NAT Gateways in the Amazon VPC User Guide.

  • The route table for the instance subnet needs to have a route for traffic to the NAT gateway.

    For more information, see Add and remove routes from a route table in the Amazon Virtual Private Cloud User Guide.

    Gateway type Route table destination Rout table target
    NAT 0.0.0.0/0 NAT gateway ID

  • If the task subnet has a network ACL, the following ACL rules are required:

    • An outbound rule that allows traffic that allows traffic on ports 1024-65535.

    • An inbound rule that allows TCP traffic on port 443.

    For information about how to configure rules, see Control traffic to subnets using network ACLs in the Amazon Virtual Private Cloud User Guide.