I understand that you are facing issue with connectivity between 2 ECS Services.
To test connectivity between 2 services, you can consider to perform the following:
-> Exec into the container of Task running in Service A and try reaching out to another service. Also try vice versa and if the connectivity is fine then that means both the services can reach each other and communicate as well.
-> Also you can test the connectivity for the service discovery endpoint of service B from service A
-> We can make use of dig or curl commands to <Service discovery endpoint> to check endpoint connectivity
This would help us to isolate the issue from networking side and further narrow down whether the issue is at application level or not. Also if our Tasks are healthy and we are using gRPC to connect 2 services, then it is also possible that error is coming from application container. However as mentioned above, the connectivity testing will help us to identify the cause of issue.
- asked 6 months ago
- Accepted Answerasked 10 months ago
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- How do I troubleshoot an Amazon ECS RunTask API for a Fargate task that fails with a "Capacity is unavailable" error?AWS OFFICIALUpdated 4 months ago
- Why am I receiving a "Failed to authenticate with service" error in my Application Migration Service replication server?AWS OFFICIALUpdated 10 months ago
- EXPERTpublished 7 months ago