AWS EC2实例部署MongoDB后无法通过Robo 3T连接求助

Let’s walk through the most common fixes for your connection problem—since you’ve already got MongoDB running locally and opened the security group, these are the key areas to check:

1. Check MongoDB’s Bind IP Configuration #

By default, MongoDB binds only to 127.0.0.1 (localhost), which means it won’t accept connections from outside the EC2 instance. Here’s how to fix it:

• Edit your MongoDB config file (usually at /etc/mongod.conf or /etc/mongodb.conf depending on your OS)
• Find the net section, then modify the bindIp line to either:
  • bindIp: 0.0.0.0 (allows connections from any IP—use this only if you’ve enabled authentication)
  • Or your EC2 instance’s private IP plus 127.0.0.1 (e.g., bindIp: 127.0.0.1,10.0.0.5)
• Restart MongoDB with sudo systemctl restart mongod (or sudo service mongodb restart for older systems)

2. Ensure Authentication is Enabled #

Even if you created users, MongoDB won’t enforce authentication unless you’ve turned it on in the config:

• In the same mongod.conf file, find the security section and add:

  security:
    authorization: enabled
  

• Restart MongoDB again to apply this change. Without this setting, your user credentials won’t be checked, but you also won’t be able to authenticate properly from Robo 3T.

3. Verify Your User Creation Details #

It’s easy to mix up which database you created the user in—MongoDB stores user credentials in the database where you ran the db.createUser() command. Make sure:

• You created the user in the correct database (not just admin unless you intended to use that as the auth DB)
• The user has the necessary permissions (e.g., readWrite on the target database, or userAdminAnyDatabase if it’s an admin user)
• Double-check the username and password—typos happen! You can verify users by connecting locally and running:

  use your_database_name
  db.getUsers()
  

4. Confirm EC2 Network Settings #

You opened the security group, but let’s double-check:

• The security group rule for port 27017 should allow inbound traffic from your local machine’s public IP (not just 0.0.0.0/0 if you want tighter security)
• Ensure your EC2 instance has a public IP attached (or you’re using an Elastic IP that’s assigned correctly)
• Check if the EC2 instance’s OS-level firewall is blocking the port:
  • For Ubuntu/Debian: Run sudo ufw status—if it’s active, add a rule with sudo ufw allow 27017
  • For RHEL/CentOS: Run sudo firewall-cmd --list-all—add the port with sudo firewall-cmd --add-port=27017/tcp --permanent then reload with sudo firewall-cmd --reload

5. Fix Robo 3T Connection Configuration #

When setting up the connection in Robo 3T, make sure:

• The Address field uses your EC2 instance’s public IP (not the private IP)
• Under the Authentication tab:
  • Check Perform authentication
  • Set Database to the exact database where you created your user (not admin unless that’s where you made it)
  • Enter the correct username and password
• If you’re using MongoDB 3.6+, try setting the Authentication Mechanism to SCRAM-SHA-1 or SCRAM-SHA-256 (older mechanisms might not work)

After going through these steps, test the connection again—most of the time, the issue is either the bind IP not allowing external connections, authentication not being enabled, or a minor misconfiguration in Robo 3T.

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