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.

  • Multiple library version management with Docker
  • Get elastic beanstalk environment variables in docker container
  • Deploy docker on AWS beanstalk with docker composer
  • Build a Docker image on top of CodeBuild Docker Image
  • When docker run, an error occurs. “ValueError: Unable to configure handler 'watchtower': You must specify a region.”
  • Run process as Daemon on AWS Infrastructure
  • I am launching my service with 1 task and no ELB.

  • PHPUnit Selenium tests fail on Docker localhost and pass using public IP
  • Kubernetes private registry doesn't work
  • nginx configuration: 405 not allowed?
  • How to connect to a remote socket in docker/engine-api?
  • Why am I getting an RTNETLINK Operation Not Permitted when using Pipework with Docker containers?
  • Changing node to manager in docker swarm - what command should I use
  • 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.