- Newest
- Most votes
- Most comments
You will need to check all the following to find the root cause.
Please check the expected version/build of the container has been published to the ECR.
Make sure a new task definition version was created pointing to the expected container tag/sha256
Ensure the ECS service is using the correct task def version.
Make sure that there’s no deployment failures on the service. If there’s an issue with spinning up the new container it will keep failing and retrying while still running an old version of your application.
Check the events on the service to make sure it’s actually trying to deploy a new image.
Upon a stable state, the old versions will not be stopped.
Hi,
did you try the CLI command aws ecs update-service
to see if it helps?
It is documented at https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ecs/update-service.html
Best,
Didier
Hello,
Thanks for the answer.
This command is the last step in my pipeline, but still the he changes are not visible in the application.
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Hello,
Thanks for the answer.
I already check that, everything looks fine and the latest version of the docker image has been deployed but still the changes are not visible in the app.
Perhaps there’s a build issue or your changes haven’t been merged into the correct branch? Not sure what else to suggest from here. Could it be an issue with your changes in your app not working as expected?