ECS will not launch instance, “unable to place a task because the resources could not be found.”

I cannot figure out why my ecs service will not launch, and keep being given the error “service unable to place a task because the resources could not be found”.

In my task definition, I have 500 cpu units dedicated and 250 memory, for just a very small sample node app that’s just serving up my static assets.

  • Fetching AWS instance metadata from within Docker container?
  • AWS ElasticBeanstalk Multidocker is not creating an ECS task with a correct Cmd
  • AWS Discovery only tries 3 ports 5701, 5702 & 5703 while joining cluster
  • How to deploy AngularJS app using nginx + docker to Elastic Beanstalk?
  • How do you deploy properly to AWS with Elastic beanstalk and Dockerrun.aws.json?
  • Kubernetes authentication issues pulling ECR images
  • I am launching my service with 1 task and no ELB.

  • How to create a new docker image from a running container on Amazon?
  • How to detach from a docker in a docker?
  • psycopg2 installation for python:2.7-alpine in Docker
  • Using Docker, how do you execute PHP composer commands?
  • Can't overwrite file in docker compose
  • How to we login to docker hub(private registry) using chef recipe?
  • One Solution collect form web for “ECS will not launch instance, “unable to place a task because the resources could not be found.””

    my guess is that your cpu units is too high. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#container_definition_environment

    it’s a harder metric to guess if you haven’t really measured it much on your app.

    anyway, i’m hitting a similar issue, so i’m right there in the same boat, but i’d try erasing the cpu since it is optional and see if that resolves it.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.