1 Answer
- Newest
- Most votes
- Most comments
0
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/
answered 10 days ago
Relevant content
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 17 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 14 days ago