Force New Task Definition Revision to run
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?
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?
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?
Unable to create a new revision of Task Definitionasked a year ago
Force New Task Definition Revision to runasked 23 days ago
RDS DB migrations using ECS and Fargateasked 2 years ago
One-shot docker containers using Docker composeasked 3 months ago
Charging operate Task for execution timeAccepted Answerasked 5 months ago
How to set up IAM roles/policies to run Fargate tasks inside a step function?asked 2 months ago
Fargate: how to stop task after finishingAccepted Answerasked 3 months ago
[ECS] Daemon services with awsvpc?Accepted Answerasked 5 months ago
ECS Fargate Task in EventBridge has ResourceInitializationErrorasked 2 months ago
defining the name of task definition json to run ecs task in github actionsasked 2 years ago