如何通过AWS Lambda连接物理MongoDB及解决连接报错问题

Hey there! Let's walk through fixing this AWS Lambda + on-prem MongoDB connection issue— that MongoServerSelectionError: getaddrinfo ENOTFOUND error is super common, and it almost always boils down to network access or a misconfigured connection string. Let's break it down step by step.

That error means your Lambda function can't resolve the hostname/IP of your on-prem MongoDB server, or it can't reach it over the network. Since Lambda runs in AWS's cloud environment, it needs a clear path to your physical server— either over the public internet (if your MongoDB has a public IP) or via a private network link (for internal-only servers).

This is the most critical part. Let's cover both scenarios for your MongoDB server:

Case A: Your MongoDB has a public IP address #

• Open your server's firewall/security group: Allow incoming traffic on MongoDB's default port (27017) from the IP range your Lambda uses. But here's the catch: Lambda's public IPs are dynamic if it's not in a VPC. A better approach is:
  1. Deploy your Lambda function into an AWS VPC (choose private subnets).
  2. Set up a NAT Gateway in a public subnet of that VPC— this lets your Lambda access the public internet to reach your MongoDB's public IP.
  3. Update your MongoDB server's firewall to allow traffic from your VPC's NAT Gateway IP (static, so easy to whitelist).

Case B: Your MongoDB is only on your internal network (no public IP) #

You need a private connection between AWS and your local network:

• Use AWS Site-to-Site VPN or AWS Direct Connect to link your AWS VPC to your on-prem network. This lets Lambda (running in your VPC) communicate directly with your internal MongoDB server.
• Update your local network's routing table to route traffic from your AWS VPC's CIDR range to your MongoDB server.
• Ensure your AWS VPC's security groups allow outbound traffic on port 27017, and your local firewall allows inbound traffic from your AWS VPC's CIDR on that port.

A typo here is another common culprit. Make sure your string follows this format:

mongodb://<username>:<password>@<mongodb-server-ip-or-hostname>:27017/<database-name>?authSource=admin

• Replace placeholders with your actual credentials, server IP/hostname, and database name.
• If you're using SSL (highly recommended), add &ssl=true to the end. For self-signed certificates, add &sslValidateCertificates=false (but only for testing— use proper certs in production).
• Pro Tip: Store this connection string in Lambda's environment variables instead of hardcoding it— it's safer and easier to update.

Here's a minimal, secure example using the official MongoDB driver:

const { MongoClient } = require('mongodb');

exports.handler = async (event) => {
  // Pull connection string from environment variable
  const mongoUri = process.env.MONGO_CONNECTION_STRING;
  const client = new MongoClient(mongoUri);

  try {
    // Connect to MongoDB
    await client.connect();
    console.log("Successfully connected to on-prem MongoDB");

    // Example: Fetch a document from a collection
    const db = client.db('your-database-name');
    const collection = db.collection('your-collection-name');
    const data = await collection.findOne({});

    return {
      statusCode: 200,
      body: JSON.stringify({ message: "Connection successful", data })
    };
  } catch (error) {
    console.error("Connection failed:", error);
    return {
      statusCode: 500,
      body: JSON.stringify({ error: error.message })
    };
  } finally {
    // Always close the connection
    await client.close();
  }
};

If you're still getting the error, run these checks:

• Test DNS resolution: Add this snippet to your Lambda to see if it can resolve your MongoDB server's hostname/IP:

  const dns = require('dns');
  
  exports.handler = async (event) => {
    try {
      const address = await dns.promises.lookup('your-mongodb-server-hostname-or-ip');
      console.log("Resolved address:", address);
      return { statusCode: 200, body: JSON.stringify(address) };
    } catch (err) {
      console.error("DNS lookup failed:", err);
      return { statusCode: 500, body: JSON.stringify(err.message) };
    }
  };
  

  If this fails, your network setup is blocking resolution— go back to step 2.
• Check MongoDB config: Ensure your mongod.conf has bindIp set to 0.0.0.0 (or your AWS VPC's CIDR) instead of 127.0.0.1 (which only allows local connections).
• Review server logs: Check your MongoDB server's logs to see if connection attempts are being blocked by authentication or firewall rules.

内容的提问来源于stack exchange，提问作者srinu nivas