AWS ECS Service Not Registering Tasks After Deployment with Fargate, Getting 'Task Definition Not Found' scenarios
I'm reviewing some code and I've been banging my head against this for hours... I'm converting an old project and I've tried everything I can think of but I'm stuck on something that should probably be simple..... I'm experiencing an scenario where my AWS ECS service is not registering the tasks after a new deployment using Fargate. I've created a service with a task definition that worked perfectly in earlier versions, but now when I try to deploy, I get the behavior message: **'Task definition not found'**. I have confirmed that the task definition is indeed present in the ECS console. The service is configured to use the latest revision of the task definition, but it fails to find it during deployment. Here’s the relevant part of my task definition in JSON format: ```json { "family": "my-task", "containerDefinitions": [ { "name": "my-container", "image": "123456789012.dkr.ecr.us-west-2.amazonaws.com/my-image:latest", "memory": 512, "cpu": 256, "essential": true, "portMappings": [ { "containerPort": 80, "hostPort": 80 } ] } ] } ``` I have also tried updating the service using the AWS CLI with the command: ```bash aws ecs update-service --cluster my-cluster --service my-service --force-new-deployment ``` However, this doesn't resolve the scenario. I verified that I have the correct IAM permissions to allow for ECS operations, and there are no apparent issues with the networking configuration (the VPC, subnets, and security groups are set up correctly). I've also looked into the CloudWatch logs for more insights, but there are no additional clues pointing towards the cause of this scenario. I'm not sure if there's a configuration step that I'm overlooking or a best practice that I might have missed. Any help would be greatly appreciated! This issue appeared after updating to Json 3.10. Any examples would be super helpful. I'm on Windows 10 using the latest version of Json. My team is using Json for this desktop app. Any ideas how to fix this? This issue appeared after updating to Json 3.9. Any ideas what could be causing this?