AWS ECS Task implementing in 'Pending' State with No Clear scenarios Message
I've encountered a strange issue with I'm working on a project and hit a roadblock. I'm working on a personal project and I'm running a service on AWS ECS with Fargate launch type, and my task is getting exploring in the 'Pending' state without any clear behavior message... I have set the task definition to use the latest Amazon Linux 2 image and allocated 512 MB of memory, but it seems like the task never transitions to 'Running'. Here's the relevant section of my task definition: ```json { "family": "my-service", "containerDefinitions": [ { "name": "my-container", "image": "amazonlinux:2", "memory": 512, "cpu": 256, "essential": true, "portMappings": [ { "containerPort": 80, "hostPort": 80 } ] } ] } ``` I’ve checked the cluster configuration and ensured that there are no resource constraints. I also verified that there are enough available task slots in the cluster and that my VPC subnet settings are correct, allowing for outbound internet access. However, when I look at the service events, it simply states, "Service is unable to start tasks" without providing any further details. I’ve tried restarting the service, updating the task definition to a newer version, and even creating a new service, but nothing seems to resolve the scenario. I’m wondering if there are any specific logs I can check or other settings I might have missed that could lead to this behavior. Any help would be greatly appreciated! I'm working on a web app that needs to handle this. Am I missing something obvious? Any examples would be super helpful. Is there a simpler solution I'm overlooking? I'm coming from a different tech stack and learning Json. Is this even possible?