ECS updating service with same tasks but different docker image

I am an issue that either I do not understand well or something weird happening with aws ecs service.

I update my code, create a new docker image and push it to be deployed using ECS. The issue is, when the task definition does not changes, the code does not get deployed, even though the image in ECR got updated. How can get my code deployed then? I am assuming that when the image has changed, the services is run the already registered tasks which should pull the image right?

  • Getting Started with EC2 Container Registry
  • Installation of chef-client(Bootstrapping) on docker container in a VM on Azure/AWS
  • Docker: ECS vs Beanstalk vs Docker Cloud
  • Amazon EFS access denied while mounting in docker container
  • How to do container rollbacks using a multi docker configuration on elasticbeanstalk
  • Can't push image to Amazon ECR - fails with “no basic auth credentials”
  • Example of commands I run

    aws ecs register-task-definition --cli-input-json file:///deploy/tasks/my-task-definition.json
    aws ecs update-service --service my-service --cluster my-clusdter --task-definition my-task-defintion

    The first time I run these commands, the code is deployed, if I update my code, push the new image to the Registry, then run these commands, my code does not get deployed.

  • Is it possible to use vagrant + aws provider + docker provider?
  • Deploy Docker from Travis to AWS (or any other SSH able server)
  • Obtaining mapped port from within docker container
  • Deploying multicontainer docker environment (flask & nginx) with EBS
  • aws ecr access authenticator required
  • structure for ECR Repo
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.