ECS on EC2 - service [service-name] was unable to place a task because no container instance met all of its requirements.

0

Hi all, Getting a strange error that I'm not able to find the root cause of. Below is the error message:

"service [service-name] was unable to place a task because no container instance met all of its requirements. The closest matching container-instance [instance] is missing an attribute required by your task."

However, when running the suggested ecs-cli command, it comes back as not missing any required attributes.

**Container Instance ** dev-ec2cluster **Missing Attributes ** None

We are attempting to enable service connect for TLS and at the moment, we think it may be due to Service Connect defaulting to TLS 1.3 which may not be available on the EC2 instance. It is an Amazon Linux 2 instance, though, a bit older.

asked 7 months ago380 views
1 Answer
0

Check out this doc . Esp the part "...Amazon ECS service to run on a subnet that's different from the subnet for the container instance..."

--Syd

profile picture
answered 7 months ago
profile picture
EXPERT
reviewed 5 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions