The "new" Amazon ECS Console is missing fundamental options like container command overrides
3
The "new" Amazon ECS Console, which is an opt-in experience, is missing important functionality. One such missing function is the ability to specify a custom entrypoint or command override for each container defined in an Amazon ECS Task Definition. This makes the usage of the "new" console almost impossible, and I have to fallback to using the old console.
When is the "new" ECS console going to be usable?
asked 4 months ago44 views
1 Answers
Relevant questions
can't edit - The If-Match version is missing or not valid for the resource.
asked 10 months agoThe new Console Home is currently unavailable. Try refreshing the page.
asked 4 months agoManaging a stack with CloudFormation - how will new ECS ARN affect me?
asked 3 years agoThe "new" Amazon ECS Console is missing fundamental options like container command overrides
asked 4 months agoECS Environment Variables "Value from"
asked 9 days agoMissing attribute ecs.capability.gmsa
asked 2 years agoUpgrade ecs-agent on Windows 2016 ECS Optimized AM
asked 2 years agoMigrating Multi-container Docker running on Amazon Linux to ECS on Amazon Linux 2
asked 2 months agoECS agent not available on Amazon ECS optimised AMI
asked 2 years agoRun Command Missing from EC2 Console
Accepted Answerasked 2 years ago
Agreed with original concerns here, just wasted like 20 minutes looking for those parameters on the new UI, knowing I had used them in the past to make some Task Definitions that are currently running.