AWS Fargate - ECS run task encountered network interface issue

Question

After I had created a python job using Lambda, it processed only a small portion not the entire dataset. After making all sorts of troubleshooting, I come to a conclusion that I need an automate serverless service that provides me sufficient storage and computing capacity (Fargate). On switching to Fargate i come across this issue as below:

"Task stopped at: 2024-07-28T12:03:36.551Z Essential container in task exited"
"There was an error while describing network interfaces. The networkInterface ID 'eni-0b13ee03ada704935' does not exist".

Found no log streams in Cloudwatch though the log is set up correctly. Therefore, not sure what are the root causes.

I have checked everything seems to work fine, from my Docker image to Task definition, role & permission and VPC network configuration, but It just does not work.

Appreciate any help!

Thanks a lot.

Didier_Durand · Accepted Answer

Hi,

You may want to consider AWS Batch instead of a Fargate container to execute your jobs.

see doc at https://aws.amazon.com/batch/

As its name implies, it was expressely built to execute one-off autonomous jobs. Fargate is more specific to long-lasting server tasks answering to multiple clients.

BTW, AWS Batch is built on top of Fargate but is much simpler to implement for jobs: that is the option that I use (heavily !!) for my long jobs.

Some good starting points:
1. https://docs.aws.amazon.com/batch/latest/userguide/get-set-up-for-aws-batch.html
2. https://stackify.com/aws-batch-guide/
3. https://www.youtube.com/watch?v=k7r6i3x5d7Q

Best,

Didier

Basel Mohamed · Answer

The error message you encountered, indicates a problem with the Elastic Network Interface (ENI) associated with your ECS task on Fargate. 
Here are some steps to troubleshoot:

Task Definition:

networkMode should be awsvpc.
Subnets and Security Groups:

Verify configurations in the task definition.
IAM Role:

Ensure task execution role has required permissions.
Service Limits:

Check EC2 and VPC limits.
AWS VPC Flow Logs:

Enable VPC Flow Logs to capture IP traffic information.
Example IAM Policy for Task Execution Role:

```
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "logs:CreateLogStream",
        "logs:PutLogEvents",
        "logs:CreateLogGroup",
        "ecs:DescribeTasks",
        "ecs:DescribeTaskDefinition",
        "ec2:DescribeNetworkInterfaces",
        "ec2:CreateNetworkInterface",
        "ec2:DeleteNetworkInterface"
      ],
      "Resource": "*"
    }
  ]
}

```

Tram Nguyen · Answer

Solved! I found out the answer to the above issue with Fargate which is that you have to set up correctly service role and execution role (cloudwatch logs) so that you know which particular errors ocurred. Then whether you run it via ECS Fargate or Batch would lead to the same outcome.

AWS Fargate - ECS run task encountered network interface issue

Relevant content