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.

  • Get elastic beanstalk environment variables in docker container
  • Elastic Beanstalk CLI, how do I create the environment with an RDS instance?
  • Can I select which services to run with Atlassian's Localstack
  • Meteor build locally or on aws host
  • AWS Docker Golang. 'eb deploy' error
  • How do I access a POST requests body from AWS API Gateway in a connected ECS docker image
  • I am launching my service with 1 task and no ELB.

  • Can a docker image use executable from the host?
  • Selenium node/chrome docker image and selenium/hub docker image in different host machines
  • Virtualbox inside Docker
  • python fabric run awk command return a KeyError: 'print $1'
  • /bin/sh: 1: python: not found while running docker container
  • Image name dropdown is empty when configuring remote interpreter Docker in PyCharm 2016
  • 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.