👀 Views: 0 💬 Answers: 1 📅 Created: 2025-06-12

aws ecs servicediscovery json

I'm attempting to set up I'm currently working with an scenario with AWS ECS Service Discovery where my services are unable to resolve each other's DNS names. I'm using the AWS Fargate launch type and I've configured service discovery using Route 53 with a private hosted zone. My task definitions use the following configuration for service discovery: ```json { "family": "my-service", "networkMode": "awsvpc", "containerDefinitions": [ { "name": "my-container", "image": "my-image:latest", "portMappings": [ { "containerPort": 80, "hostPort": 80 } ], "essential": true } ], "serviceDiscovery": { "type": "AWS Cloud Map", "name": "my-service.local" } } ``` When I deploy my service and try to ping the DNS name from within another container, I receive a `Name or service not known` behavior. I've confirmed that the security group rules allow traffic between the tasks, and I can see that the service discovery entries are being created correctly in Route 53. However, resolving the DNS name seems to unexpected result intermittently. I've also tried inspecting the Cloud Map entries, and they appear to have the correct IP addresses associated with them. The configurations for both services are identical, yet only one service can resolve to the other. I've scaled both services up and down, but it doesn't seem to resolve the scenario. Here's a quick command I run to check DNS resolution from one container: ```bash nslookup my-other-service.local ``` This command often returns `;; connection timed out; no servers could be reached` after a few seconds. I suspect there might be a misconfiguration with either the namespace or the task execution role permissions, but I'm not sure where to look. Any guidance on how to troubleshoot this further would be greatly appreciated! My team is using Json for this web app.