The "new" Amazon ECS Console is missing fundamental options like container command overrides
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?
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.
This feature has been logged with the ECS team and will be reviewed.
can't edit - The If-Match version is missing or not valid for the resource.asked 10 months ago
The new Console Home is currently unavailable. Try refreshing the page.asked 4 months ago
Managing a stack with CloudFormation - how will new ECS ARN affect me?asked 3 years ago
The "new" Amazon ECS Console is missing fundamental options like container command overridesasked 4 months ago
ECS Environment Variables "Value from"asked 9 days ago
Missing attribute ecs.capability.gmsa
Upgrade ecs-agent on Windows 2016 ECS Optimized AM
Migrating Multi-container Docker running on Amazon Linux to ECS on Amazon Linux 2asked 2 months ago
ECS agent not available on Amazon ECS optimised AMIasked 2 years ago
Run Command Missing from EC2 ConsoleAccepted Answerasked 2 years ago