ECS: Task start fails when using enableECSManagedTags
See original GitHub issueAWS SDK version: 2.376.0
ECS.runTask({..., enableECSManagedTags: true},...)
executes, but the task does not get into taskRunning
state. Stopped Reason is: Unexpected EC2 error while attempting to tag the network interface: InvalidParameterValue
arn:aws:iam::aws:policy/aws-service-role/AmazonECSServiceRolePolicy
contains CreateTag permission.
Issue Analytics
- State:
- Created 5 years ago
- Comments:20 (6 by maintainers)
Top Results From Across the Web
Troubleshoot ECS tasks stopping or failing to start - AWS
My Amazon Elastic Container Service (Amazon ECS) container exits unexpectedly, and tasks stop or fail to start. How can resolve the issue?
Read more >AWS ECS Cannot start task - Server Fault
The problem is with "Task tagging configuration" > DISABLE "Enable ECS managed tags". When this parameter is ...
Read more >AWS ECS service error: Task long arn format must be enabled ...
Upon task update, the service suddenly died with error: 'service my_service_name failed to launch a task with (error Task long arn format must ......
Read more >run-task — AWS CLI 2.9.10 Command Reference - ecs
Starts a new task using the specified task definition. ... <value>] [--enable-ecs-managed-tags | --no-enable-ecs-managed-tags] [--enable-execute-command ...
Read more >aws_ecs_service | Resources | hashicorp/aws
Provides an ECS service - effectively a task that is expected to run until an error ... Example: Create service with 2 instances...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@byF
The service team has indicated that this issue has been resolved.
So what is the bug? I’m also hitting this issue - do you have a URL or incident# for reference?