Elastic Beanstalk中Docker部署的Node应用无法连接同VPC内MongoDB求助

Let’s break down your problem step by step— that getaddrinfo ENOTFOUND error is telling us the Node app can’t resolve the target IP (even though you’re using a private IP, which shouldn’t require DNS, but there’s still something off). Here’s what to check:

1. Verify Basic Connectivity First #

Start with the simplest tests to rule out low-level network issues:

• SSH into your Node app’s EB instance and run ping <mongodb-private-ip>. If this fails, you’ve got a VPC routing or subnet issue:
  • Double-check both instances are in subnets that have a route table allowing internal VPC traffic (no internet gateway required here, just the default local route).
  • Ensure Network Access Control Lists (NACLs) for both subnets allow inbound and outbound traffic on port 27017. Security groups are instance-level, but NACLs act at the subnet level— they’re often overlooked.
• If ping works, test the port directly with nc -zv <mongodb-private-ip> 27017. If this fails, skip to step 2 (MongoDB isn’t listening correctly) or revalidate your security group rules (make sure the Node app’s security group is explicitly allowed in the MongoDB security group’s inbound 27017 rule).

2. Check MongoDB’s Binding & Port Mapping #

Since you’re running MongoDB in Docker, the most common culprit here is that MongoDB isn’t listening on the instance’s private IP:

• SSH into the MongoDB EB instance and run docker inspect <mongodb-container-id> (use docker ps to get the ID). Look for the PortBindings section— you should see 27017/tcp mapped to 0.0.0.0:27017 (or the instance’s private IP). If not, your Docker config isn’t exposing the port to the host.
• Next, check MongoDB’s bind configuration:
  • Enter the container with docker exec -it <mongodb-container-id> bash and open /etc/mongod.conf. Look for the bindIp setting— it should be set to 0.0.0.0 (to listen on all interfaces) or include the instance’s private IP.
  • If you’re starting MongoDB with a command line flag instead of a config file, ensure you’re using --bind_ip_all (or --bind_ip 0.0.0.0) to allow external connections to the container.

3. Validate Elastic Beanstalk Docker Network Settings #

EB’s default Docker setup uses bridge networking, which isolates containers from the host network— but you need to make sure your Node app container can reach the MongoDB instance’s host IP:

• Confirm you’re using the MongoDB EB instance’s private IP (not the Docker container’s internal IP) in your connection string. Container internal IPs are only accessible within the same instance’s Docker network, not across EB environments.
• If you’ve customized EB’s Docker network mode (e.g., using host mode), double-check that the network configuration doesn’t block cross-instance traffic. For most cases, bridge mode works as long as ports are mapped correctly.

4. Rule Out DNS Quirks (Even With IPs) #

Occasionally, container DNS configurations can misbehave and try to resolve IP addresses as hostnames:

• Enter your Node app’s Docker container (via SSH to the EB instance, then docker exec -it <node-container-id> bash) and run nslookup <mongodb-private-ip>. If this returns an error, your container’s DNS is broken.
• Fix this by updating your EB environment’s Docker configuration to use the VPC’s default DNS server (usually your VPC CIDR’s second IP, e.g., 10.0.0.2 for a 10.0.0.0/16 VPC). You can set this via the EB console’s "Configuration" > "Software" section, or in your .ebextensions config.

Final Quick Check #

Make sure your Node app’s connection string is formatted correctly— no typos in the IP, no extra characters. For example:

mongoose.connect('mongodb://<mongodb-private-ip>:27017/your-db-name');

内容的提问来源于stack exchange，提问作者Oskar Martin