Force New Task Definition Revision to run
0
I have updated several task definitions and for the life of me I cannot get the latest revisions to run. We are using the AWS code management system, e.g. Code Deploy, Code Commit, etc. Wondering if there is a preferred way to get task definition to run the latest revision. I have tried stopping the service and updating with "Force new Deployment" checked and so far no dice. Any idea what I'm doing wrong?
asked 23 days ago4 views
1 Answers
0
Not very clear what is done on the Code family side or what is the expected workflow, but from ECS perspective, have you update / ensure your task definition with the desired image and also your service has been updated with the correct task definition version?
answered 23 days ago
Relevant questions
Unable to create a new revision of Task Definition
asked a year agoForce New Task Definition Revision to run
asked 23 days agoRDS DB migrations using ECS and Fargate
asked 2 years agoOne-shot docker containers using Docker compose
asked 3 months agoCharging operate Task for execution time
Accepted Answerasked 5 months agoHow to set up IAM roles/policies to run Fargate tasks inside a step function?
asked 2 months agoFargate: how to stop task after finishing
Accepted Answerasked 3 months ago[ECS] Daemon services with awsvpc?
Accepted Answerasked 5 months agoECS Fargate Task in EventBridge has ResourceInitializationError
asked 2 months agodefining the name of task definition json to run ecs task in github actions
asked 2 years ago
Task definition is updated, no new image, just updated health check within the definition. So we are running blue/green and deploy from changes in the code base. I want to run the latest revision of all of our tasks as all of them now have a health check defined. Another question how do I stop older revisions from running as well, it seems I have 2 tasks running for a few services, all running the newest revision, how do I remove the old task that's running the older revision?