Skip to content

Instantly share code, notes, and snippets.

@philippelatulippe

philippelatulippe/ecs-service-instance-missing-an-attribute.md

Created January 27, 2017 13:22
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save philippelatulippe/b635ae70368c3341077a7b1468d0ca15 to your computer and use it in GitHub Desktop.
Save philippelatulippe/b635ae70368c3341077a7b1468d0ca15 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
ecs-service-instance-missing-an-attribute.md

You make some changes, then the ECS Service tells you

The closest matching container-instance ... is missing an attribute required by your task.

Are you running the ECS agent on your own AMI? Maybe you need to update its config to enable some features that are enabled on the amazon AMI but not on by default in the agent.

In our case, we added an IAM role to the task, but this functionality isn't enabled by default. As a result, ECS would refuse to deploy on any of the instances on our cluster. We had to update our AMI with a new config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment