AWS ECS Service Connect | Client receive error 400 status code

Question

I'm attempting to use AWS ECS Service Connect for the first time, and I suspect I may have overlooked something simple.

Here's what I've done so far: I've created a cluster with several services, all within the same namespace. I've verified that each service has the appropriate service connect name (seen on the respective config tabs). Additionally, I've noticed that when I make calls to the services, the http headers show 'server:envoy'.

However, when a client service sends a request to its dependent service, the client receives a '400 Bad Request' error. After checking the client logs, I can confirm that the request is being sent to the correct URL as specified in the service configuration tab.

Any suggestions or insights on why I'm encountering this '400 Bad Request' issue would be greatly appreciated.

Answer

Hi,
usually 400 error are application level errors. So I think that you ECS Service Connect it's actually working correctly. My recommendation would be to login into one of the running container and try manually invoke some of the available API with "curl" to be sure that the ECS Service Connect configuration is actually correctly configured.

Using Amazon ECS Exec to access your containers on AWS Fargate and Amazon EC2:
https://aws.amazon.com/blogs/containers/new-using-amazon-ecs-exec-access-your-containers-fargate-ec2/

AWS ECS Service Connect | Client receive error 400 status code

Relevant content