AWS Builder Center is the official home for builders on AWS. Share and read what others are working on, follow people who inspire you, explore training and workshops, and find tools to support what you're building.
How to update task definition with least interruption to the service?
I have an ECS service running tasks on Fargate. I have multiple tasks running for the service during the time I want to introduce a change in memory. Let's say currently they are 1GB but the latest definition will be 2GB memory. When I change the service to point to the new definition, it creates a new set of tasks, and then immediately kill the old tasks with the old definition. Is there a way to do it gracefully part of the task autoscaling life cycle?
Note that all my tasks health status showing as unknown. Did not give it so much thought, but would that be a reason or replacing all tasks for a new definition is expected?
- Argomenti
- Contenitori
- Lingua
- English
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
It seems this answers most of what I'm looking for: https://aws.amazon.com/blogs/containers/a-deep-dive-into-amazon-ecs-task-health-and-task-replacement/
