AWS ECS Service implementation guide Task Definition After Deploying New Version
I'm maintaining legacy code that Hey everyone, I'm running into an issue that's driving me crazy. I have a setup on AWS ECS where I am using Fargate to run my containers. I created a new task definition revision with a slight change in the container image tag. However, when I update the ECS service to use the new task definition, it doesn't seem to deploy the new version. The service remains in the 'UPDATING' state indefinitely, and I see the following behavior in the ECS console: 'SERVICE_STEADY_STATE_CONDITION_NOT_MET'. Here’s the code I'm using to update the service: ```python import boto3 ecs_client = boto3.client('ecs') response = ecs_client.update_service( cluster='my-cluster', service='my-service', taskDefinition='my-task:2', # New revision number desiredCount=1 ) print(response) ``` I've already tried stopping the service and scaling it down to zero before updating, but it doesn't help. Additionally, I checked the logs of the previous task definitions, and there are no clear errors that would indicate why the new task definition isn't being adopted. I ensured that the new container image is correctly pushed to ECR and accessible. My IAM roles seem fine too, as the service has permission to pull images. Is there anything I'm missing or any other configurations that I should check? How can I troubleshoot this situation to get my ECS service to update properly? Any suggestions would be helpful. Any pointers in the right direction? This is for a web app running on macOS.