Docs Home → Start with Guides
In this guide, you will retrieve your database deployment's connection string.
- Add your IP address to the allowlist to allow access to your Atlas cluster.
- Locate your connection string and copy it.
Time required: 15 minutes
- A MongoDB account. See Sign Up for a MongoDB Account.
- An Atlas cluster. See Create a New Cluster.
- A MongoDB user. See Configure MongoDB Users in the Atlas documentation.
Click the Connect button on the cluster management panel. The following Atlas screenshot shows the Connect button:
In the Choose your connection method step in the modal, select the button marked Connect Your Application.
The following Atlas screenshot shows the connection option buttons:
Follow the instructions for your driver language and version.
If you have successfully completed this guide, you have retrieved your database deployment's connection string in your copy buffer.
Docs Home → MongoDB Atlas
Atlas does not guarantee that host names remain consistent with respect to node types during topology changes.
Example
If you have a cluster named foo123 containing an analytics node foo123-shard-00-03-a1b2c.mongodb.net:27017, Atlas does not guarantee that specific host name will continue to refer to an analytics node after a topology change, such as scaling a cluster to modify its number of nodes or regions.
To access a database deployment, 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.
To access a database deployment, you must create a database user with access to the desired database(s) on your Atlas database deployment. 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 your Atlas database deployment in the Connect dialog. You can also add the database user from the Database Deployment view.
Make sure your application can reach your MongoDB Atlas environment. To add the inbound network access from your application environment to Atlas, do one of the following:
Add the public IP addresses to your IP access list
Use VPC / VNet peering to add private IP addresses.
Add private endpoints.
Tip
See also:
If your firewall blocks outbound network connections, you must also open outbound access from your application environment to Atlas. You must configure your firewall to allow your applications to make outbound connections to ports 27015 to 27017 to TCP traffic on Atlas hosts. This grants your applications access to databases stored on Atlas.
Note
By default, MongoDB Atlas clusters do not need to be able to initiate connections to your application environments. If you wish to enable Atlas clusters with LDAP authentication and authorization, you must allow network access from Atlas clusters directly to your secure LDAP. You can allow access to your LDAP by using public or private IPs as long as a public DNS hostname points to an IP that the Atlas clusters can access.
If you are not using VPC / VNet peering and plan to connect to Atlas using public IP addresses, see the following pages for additional information:
Can I specify my own VPC for my MongoDB Atlas project?
Do Atlas clusters' public IPs ever change?
Note
If you are experiencing issues connecting to your database deployment, see Troubleshoot Connection Issues.
Tip
See also:
Connect via Your Application
Connect via Compass
Connect via mongosh
Connect via BI Connector for Atlas
Browse Data via the Atlas UI
Test Failover
Manage Connections with AWS Lambda
Connection Limits and Cluster Tier