Connect via Driver¶
The Connect dialog for a cluster provides the details to connect to a cluster with an application using a MongoDB driver.
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.
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.
The drivers recommended for MongoDB 3.6 in the driver compatibility matrices are tested against MongoDB 4.4. 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.4 as long as:
- No functionality new to MongoDB 4.0, MongoDB 4.2, or MongoDB 4.4 is being used, and
- No commands, methods, or options removed in
MongoDB 4.0,
MongoDB 4.2
(including
db.collection.geoNear()
,db.collection.group()
, anddb.eval()
), or MongoDB 4.4 are being used, and - Other compatibility changes in
MongoDB 4.4 to
projections
(including$slice projections
),$sort
,text search
, andmapReduce
do not impact them.
We still recommend using MongoDB 4.4-series drivers with MongoDB 4.4 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.
IP Access List¶
To access a cluster, you must connect from an IP address on the Atlas project's IP access list. If you need to add an IP address to the IP access list, you can do so in the Connect dialog. You can also add the IP address from the Network Access 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¶
Click Connect.¶
In the Clusters view, click Connect for the cluster to which you want to connect.
Choose your Connection Security.¶
Choose Connection Type from the set of available buttons.
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.
Use this connection type for allowed public IP addresses.
Choose how you want to limit connections to your cluster.¶
Add a Connection IP Address
Skip this step if Atlas indicates in the Setup connection security step that you have already configured an IP access list entry in your cluster. To manage the IP access list, see Add Entries to the Access List.
Atlas allows standard client connections to the cluster from entries in the project's IP access list. The project IP access list differs from the API access list, which restricts API access to specific IP or CIDR addresses.
If the IP access list is empty, Atlas prompts you to add an IP address to the project's IP access list. You can either:
- Click Add Your Current IP Address to allow access from your current IP address.
- Click Add an IP Address to add a single IP address or a CIDR