• Connect to a Cluster >
• Connect via Driver

Connect via Driver

The Connect dialog for a cluster provides the details to connect to a cluster with an application using a MongoDB driver.

See also

Connection Limits and Cluster Tier

Prerequisites

Driver Version

Your driver version must be compatible with your version of the MongoDB server. We recommend choosing the latest driver that is compatible with your MongoDB server version to utilize the latest database features and prepare for future version upgrades.

For a list of driver versions that contain the full set of functionality for your version of the MongoDB server, check the compatibility matrix for your MongoDB driver.

Important

When you upgrade your driver version, some commands, methods or options may be deprecated and removed. Check your MongoDB driver API documentation to ensure a smooth transition.

3.6-Series Driver Compatibility with MongoDB 4.2

The drivers recommended for MongoDB 3.6 in the driver compatibility matrices are tested against MongoDB 4.2. Check the MongoDB driver documentation page for the driver compatibility matrix for your language.

Applications running with 3.6-series drivers will work against MongoDB clusters running MongoDB 4.2 as long as:

• No functionality new to MongoDB 4.0 is being used,
• No functionality new to MongoDB 4.2 is being used, and
• No commands, methods, or options removed in MongoDB 4.0 or removed in MongoDB 4.2 (which means geoNear, db.collection.group(), and db.eval()) are being used.

We still recommend using MongoDB 4.2-series drivers with MongoDB 4.2 to utilize newer database features and better prepare for future version upgrades.

TLS

Clients must support TLS to connect to an Atlas cluster.

Clients must support the SNI TLS extension to connect to an Atlas M0 Free Tier or M2/M5 shared starter cluster. To verify that your MongoDB driver supports the SNI TLS extension, refer to the Compatibility section of your driver’s documentation. If the driver is compatible with MongoDB 3.4 and later, it supports the SNI TLS extension.

Whitelist

To access a cluster, you must connect from an IP address on the Atlas project’s IP whitelist. If you need to add an IP address to the whitelist, you can do so in the Connect dialog. You can also add the IP address from the Security tab.

Database User

To access a cluster, you must create a database user with access to the desired database(s) on your Atlas cluster. Database users are separate from Atlas users. Database users have access to MongoDB databases, while Atlas users have access to the Atlas application itself.

You can create a database user to access to your Atlas cluster in the Connect dialog. You can also add the database user from the Clusters view.

Connect Your Application

1

Open the Connect dialog.

In the Clusters view, click the Connect button for the cluster to which you want to connect.

2

Choose your Connection Security.

Choose Connection Type from the set of available buttons.

Options Display if Feature Enabled

Atlas displays the connection type options after you enable Private IP for Peering, Private Endpoint, or both. If you haven’t enabled either feature, no buttons display and Connection Type defaults to Standard.

• Standard Connection
• Private IP for Peering
• Private Endpoint Connection

Use this connection type for whitelisted public IP addresses.

Use this connection type if you enabled peering:

• For GCP or Azure and are connecting with your driver from a peered network, or
• For AWS and are connecting with your driver from a peered network which uses a custom DNS service.

If neither of these apply, whitelist your IP address and use the Standard Connection string. If you are connecting directly to Atlas from an office or home network, this might be the preferred option.

Note

You can’t select this option unless one of your peers peers is marked as AVAILABLE. Navigate to Network Access to check the status of your peers.

Use the connection string for the appropriate interface endpoint if you are connecting with your driver over a Private Endpoint connection either because your driver:

• Runs inside your cloud provider network, or
• Has transitive network access to your cloud provider network.

If neither of these apply, whitelist your IP address and use the Standard Connection string. If you are connecting directly to Atlas from an office or home network, this might be the preferred option.

Note

You can’t select this option unless your configured PrivateLink connection is ready to use. Navigate to Network Access to check the status of your AWS PrivateLink.

3

Choose how you want to limit connections to your cluster.

Whitelist a Connection IP Address

Important

Skip this step if Atlas indicates in the Setup Connection Security step that you have already configured a whitelist entry in your cluster. To manage the IP whitelist, see Add Entries to the Whitelist.

Atlas allows standard client connections to the cluster from entries in the project’s whitelist. The project whitelist differs from the API whitelist, which restricts API access to specific IP or CIDR addresses.

If the whitelist is empty, Atlas prompts you to add an IP address to the project’s whitelist. You can either:

• Click Add Your Current IP Address to whitelist your current IP address.
• Click Add an IP Address to add a single IP address or a CIDR-notated range of addresses.

Provide an optional description for the newly added IP address or CIDR range. Click Add IP Address to add the address to the whitelist.

Whitelist a Connection IP Address

Important

Skip this step if Atlas indicates in the Setup Connection Security step that you have already configured a whitelist entry in your cluster. To manage the IP whitelist, see Add Entries to the Whitelist.

Atlas allows standard client connections to the cluster from entries in the project’s whitelist. The project whitelist differs from the API whitelist, which restricts API access to specific IP or CIDR addresses.

If the whitelist is empty, Atlas prompts you to add an IP address to the project’s whitelist. Click Add a Different IP Address to add a single IP address or a CIDR-notated range of addresses.

Provide an optional description for the newly added IP address or CIDR range. Click Add IP Address to add the address to the whitelist.

Choose PrivateLink

Select the PrivateLink in your AWS region from the Choose PrivateLink menu.

4

Create a Database User.

Important

Skip this step if Atlas indicates in the Setup connection security step that you have at least one database user configured in your project. To manage existing database users, see Configure Database Users.

To access the cluster, you need a MongoDB user with access to the desired database or databases on the cluster in your project. If your project has no MongoDB users, Atlas prompts you to create a new user with the Atlas Admin role.

1. Enter the new user’s Username
2. Enter a Password for this new user or click Autogenerate Secure Password.
3. Click Create Database User to save the user.

Use this user to connect to your cluster in the following step.

Once you have whitelisted an IP address and added a database user, click Choose Your Connection Method.

5

Select Connect Your Application.

In the Choose a connection method step, select Connect Your Application.

6

Select Your Driver and Version.

1. Select your driver and version from the dropdown menus.

2. The Connection String Only tab displays the connection string you can use to connect to your Atlas cluster. The Full Driver Example tab displays a code sample for your selected driver and version demonstrating a connection to your Atlas cluster.

   Note

   The connection string displayed in the UI uses a placeholder value for the password. Replace that placeholder with your own MongoDB password.

   Important

   If the password contains reserved URI characters, you must escape the characters per RFC 2396.

   Example

   If your password is @bc123, you must escape the @ character when specifying the password in the connection string; e.g. %40bc123.

For details on driver compatibility with MongoDB, see Driver Compatibility.

The connection string examples specify the test database for the initial connection. If the user is configured on a different database, specify that database in the connection string.

Driver Examples

In this example URI connection strings, the user kay provides their password myRealPassword to authenticate and connect to an Atlas cluster.

Select your driver from the following options:

• Python
• Java (Sync)
• Node.js
• PHP
• C
• Other
  • C++11
  • C#
  • Perl
  • Ruby
  • Scala
  • Go

Note

To connect to an Atlas M0 (Free Tier) cluster, you must use Python 2.7.9+ and use a Python driver version that supports MongoDB 3.6. For complete documentation on compatibility between the Python driver and MongoDB, see the MongoDB compatibility matrix.

copy

import pymongo
import dns # required for connecting with SRV

client = pymongo.MongoClient("mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?w=majority")
db = client.test

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 3.7 or later.
MongoDB 3.6	Version 3.6 or later.

macOS and Python 3.6 Installers

The Python 3.6 installers for macOS from https://www.python.org do not automatically install any CA certificates. Without installed CA certificates, connections to Atlas will fail certificate verification.

After you run the installer from https://www.python.org to install Python 3.6, you must run the following script to install an up-to-date CA bundle before connecting to Atlas:

copy

open "/Applications/Python 3.6/Install Certificates.command"

For more information on Python 3.6 installers for macOS from https://www.python.org, see https://bugs.python.org/issue29065#msg283984. Earlier versions of Python as well as Python 3.6 installed by other means (e.g. Homebrew), are not affected.

Note

To connect to an Atlas M0 (Free Tier) cluster, you must use Java version 8 or greater and use a Java driver version that supports MongoDB 3.6. For complete documentation on compatibility between the Java driver and MongoDB, see the MongoDB compatibility matrix.

copy

MongoClientURI uri = new MongoClientURI(
    "mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?w=majority");

MongoClient mongoClient = new MongoClient(uri);
MongoDatabase database = mongoClient.getDatabase("test");

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 3.8 or later.
MongoDB 3.6	Version 3.6 or later.

Note

To connect to an Atlas M0 (Free Tier) or M2/M5 shared tier cluster, you must use a Node.js driver version that supports MongoDB 3.6. For complete documentation on compatibility between the Node.js driver and MongoDB, see the MongoDB compatibility matrix.

copy

const MongoClient = require('mongodb').MongoClient;
const uri = "mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?w=majority";
const client = new MongoClient(uri, { useNewUrlParser: true });
client.connect(err => {
  const collection = client.db("test").collection("devices");
 // perform actions on the collection object
  client.close();
});

To connect to a database other than admin but still authenticate to the admin database, update the database component of the connection string.

copy

mongodb://username:password@host1:port1,...,hostN:portN/database?authSource=admin&...

Example

The following connection string specifies test in the database component and includes the authSource=admin option.

copy

var uriTestDb = "mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?ssl=true&authSource=admin&w=majority";
MongoClient.connect(uriTestDb, function(err, db) {
   db.close();
});

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 3.1 or later.
MongoDB 3.6	Version 3.0 or later.

Note

To connect to an Atlas M0 (Free Tier) or M2/M5 shared tier cluster, you must use a PHP driver version that supports MongoDB 3.6. For complete documentation on compatibility between the PHP driver and MongoDB, see the MongoDB compatibility matrix.

The following example uses the MongoDB PHP Library which provides a high-level abstraction around the lower-level PHP driver:

copy

$client = new MongoDB\Client(
    'mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?serverSelectionTryOnce=false&serverSelectionTimeoutMS=15000&w=majority"');

$db = $client->test;

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	PHPLIB 1.4 + mongodb-1.5.
MongoDB 3.6	PHPLIB 1.3 + mongodb-1.3.

Behavior

MongoDB drivers automatically attempt server selection following a cluster election or failover event. By default, the driver immediately raises an error if its first attempt to select a server fails. The following configuration settings may improve application connectivity to an Atlas cluster at the expense of spending more time in a server selection loop:

• Set serverSelectionTryOnce to false to direct the driver to perform server selection up to the time limit defined by serverSelectionTimeoutMS.
• Lower the serverSelectionTimeoutMS to 15000 from the default of 30000. MongoDB elections typically take 10 seconds, but can be as fast as 5 seconds on Atlas. Setting this value to 15 seconds (15000 milliseconds) covers the upper bound of election plus additional time for latency.

Note

To connect to an Atlas M0 (Free Tier) or M2/M5 shared tier cluster, you must use a C driver version that supports MongoDB 3.6. For complete documentation on compatibility between the C driver and MongoDB, see the MongoDB compatibility matrix.

copy

client = mongoc_client_new ("mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/?serverSelectionTryOnce=false&serverSelectionTimeoutMS=15000&w=majority");
db = mongoc_client_get_database (client, "test");

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 1.11 or later.
MongoDB 3.6	Version 1.9 or later.

Behavior

Note

The following configuration options only apply if running the C driver in single-threaded mode.

MongoDB drivers automatically attempt server selection following a cluster election or failover event. By default, the C driver immediately raises an error if its first attempt to select a server fails. The following configuration settings may improve application connectivity to an Atlas cluster at the expense of spending more time in a server selection loop:

• Set serverSelectionTryOnce to false to direct the C driver to perform server selection up to the time limit defined by serverSelectionTimeoutMS.
• Lower the serverSelectionTimeoutMS to 15000 from the default of 30000. MongoDB elections typically take 10 seconds, but can be as fast as 5 seconds on Atlas. Setting this value to 15 seconds (15000 milliseconds) covers the upper bound of election plus additional time for latency.

Note

To connect to an Atlas M0 (Free Tier) or M2/M5 shared tier cluster, you must use a C++ driver version that supports MongoDB 3.6. For complete documentation on compatibility between the C++ driver and MongoDB, see the MongoDB compatibility matrix.

copy

#include <mongocxx/client.hpp>
#include <mongocxx/instance.hpp>

//...

mongocxx::instance inst{};
mongocxx::client conn{mongocxx::uri{"mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?serverSelectionTryOnce=false&serverSelectionTimeoutMS=15000&w=majority"}};
mongocxx::database db = conn["test"];

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 3.4.x or later.
MongoDB 3.6	Version 3.3.x or later.

Note

The Legacy C++ driver has reached End-Of-Life, and is no longer supported.

Behavior

Note

The following configuration options only apply when using the C++ driver’s single-threaded mongocxx::client class to connect to the Atlas cluster.

MongoDB drivers automatically attempt server selection following a cluster election or failover event. By default, the C++ driver immediately raises an error if its first attempt to select a server fails. The following configuration settings may improve application connectivity to an Atlas cluster at the expense of spending more time in a server selection loop:

• Set serverSelectionTryOnce to false to direct the C++ driver to perform server selection up to the time limit defined by serverSelectionTimeoutMS.
• Lower the serverSelectionTimeoutMS to 15000 from the default of 30000. MongoDB elections typically take 10 seconds, but can be as fast as 5 seconds on Atlas. Setting this value to 15 seconds (15000 milliseconds) covers the upper bound of election plus additional time for latency.

Note

To connect to an Atlas M0 (Free Tier) or M2/M5 shared tier cluster, you must use a C#/.Net driver version that supports MongoDB 3.6. For complete documentation on compatibility between the C#/.Net driver and MongoDB, see the MongoDB compatibility matrix.

copy

var client = new MongoClient("mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?w=majority");
var database = client.GetDatabase("test");

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 2.7 or later.
MongoDB 3.6	Version 2.5 or later.

Note

Microsoft .NET Core library versions 2.1 and later support the SNI TLS extension on Linux and macOS. Applications using prior versions of .NET Core on these platforms cannot connect to a Atlas M0 Free Tier or M2/M5 shared-tier cluster.

To learn more this requirement, see this dotnet/corefx issue.

Note

To connect to an Atlas M0 (Free Tier) or M2/M5 shared tier cluster, you must use a Perl driver version that supports MongoDB 3.6. For complete documentation on compatibility between the Perl driver and MongoDB, see the MongoDB compatibility matrix.

copy

my $client = MongoDB->connect('mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?w=majority');
my $db = $client->get_database( 'test' );

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 3.1 or later.
MongoDB 3.6	Version 3.0 or later.

Behavior

MongoDB drivers automatically attempt server selection following a cluster election or failover event. By default, the Perl driver immediately raises an error if its first attempt to select a server fails. The following configuration settings may improve application connectivity to an Atlas cluster at the expense of spending more time in a server selection loop:

• Set serverSelectionTryOnce to false to direct the Perl driver to perform server selection up to the time limit defined by serverSelectionTimeoutMS.
• Lower the serverSelectionTimeoutMS to 15000 from the default of 30000. MongoDB elections typically take 10 seconds, but can be as fast as 5 seconds on Atlas. Setting this value to 15 seconds (15000 milliseconds) covers the upper bound of election plus additional time for latency.

Note

To connect to an Atlas M0 (Free Tier) or M2/M5 shared tier cluster, you must use a Ruby driver version that supports MongoDB 3.6. For complete documentation on compatibility between the Ruby driver and MongoDB, see the MongoDB compatibility matrix.

copy

client = Mongo::Client.new('mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/?ssl=true&w=majority')

To connect to a database other than admin but still authenticate to the admin database, update the database component of the connection string.

copy

mongodb://username:password@host1:port1,...,hostN:portN/database?authSource=admin&...

Example

The following connection string specifies test in the database component and includes the authSource=admin option.

copy

client = Mongo::Client.new('mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?ssl=true&replicaSet=Mycluster0-shard-0&authSource=admin&w=majority')

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 2.6 or later.
MongoDB 3.6	Version 2.5 or later.

Mongoid Example

copy

production:
  # Configure available database clients. (required)
  clients:
    # Defines the default client. (required)
    default:
      # Defines the name of the default database that Mongoid can connect to.
      # (required).
      database: 'myDatabaseName'

      # Provides the hosts the default client can connect to. Must be an array
      # of host:port pairs. (required)
      hosts:
        - mycluster0-shard-00-00.mongodb.net:27017
        - mycluster0-shard-00-01.mongodb.net:27017
        - mycluster0-shard-00-02.mongodb.net:27017
      options:
        # The name of the user for authentication.
        user: kay

        # The password of the user for authentication.
        password: myRealPassword

        # The database or source to authenticate the user against. If the database
        # specified above is not admin, admin MUST be specified here.
        auth_source: admin

        # All Atlas servers use SSL. (default: false)
        ssl: true

MongoDB Version	Minimum ODM Version
MongoDB 4.0	Version 7.0.0 or later
MongoDB 3.6	Version 6.3.0 or later

Note

To connect to an Atlas M0 (Free Tier) or M2/M5 shared tier cluster, you must use a Scala driver version that supports MongoDB 3.6. For complete documentation on compatibility between the Scala driver and MongoDB, see the MongoDB compatibility matrix.

copy

val uri: String = "mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?w=majority"
System.setProperty("org.mongodb.async.type", "netty")
val client: MongoClient = MongoClient(uri)
val db: MongoDatabase = client.getDatabase("test")

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 2.4 or later.
MongoDB 3.6	Version 2.2 or later.

Note

To connect to an Atlas M0 (Free Tier) or M2/M5 shared tier cluster, you must use a Go driver version that supports MongoDB 3.6. For complete documentation on compatibility between the Go driver and MongoDB, see the MongoDB compatibility matrix.

copy

uri := "mongodb+srv://kay:myRealPassword@cluster0.mongodb.net/test?w=majority"

ctx, cancel := context.WithTimeout(context.Background(), 10*time.Second)
defer cancel()

client, err := mongo.Connect(ctx, options.Client().ApplyURI(uri))
if err != nil {
    panic(err)
}

defer func() {
    if err = client.Disconnect(ctx); err != nil {
        panic(err)
    }
}()

// Ping the primary
if err := client.Ping(ctx, readpref.Primary()); err != nil {
    panic(err)
}

MongoDB Version	Recommended Driver Version(s)
All	See the MongoDB compatibility matrix for the latest recommended driver versions.
MongoDB 4.0	Version 1.0.0 or later.
MongoDB 3.6	Version 1.0.0 or later.

Troubleshooting

If you are experiencing issues connecting to your cluster, see Troubleshoot Connection Issues.

←   Connect to a Cluster Connect via Compass  →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.