User Manual MongoDB Atlas Service Discovery Back to User Manual
This guide explains how to browse resources that are visible to your stored MongoDB Atlas credentials and connect to a cluster.
The default view is a hierarchy:
v MongoDB Atlas
v Example Organization
v Production Project
> orders-prod
> inventory-prod
Resources that are visible through more than one configured credential appear once. The extension uses a working credential for later discovery requests, such as listing the cluster’s database users.
Use the view action on the MongoDB Atlas root item or its context menu to change the view.
| View | Contents |
|---|---|
| Tree view | Organizations, then projects, then clusters. This is the default. |
| List view | A flat list of clusters. Each cluster includes its organization · project context. |
The selected view is remembered for future sessions. Both views show the same clusters and recovery actions.
Atlas can show a cluster before it is ready for a database connection. The extension keeps these clusters visible and adds a status label.
| Status | Meaning |
|---|---|
| Paused | Resume the cluster in MongoDB Atlas before connecting. |
| Creating | Atlas is provisioning the cluster. |
| Updating | Atlas is applying a configuration or topology change. |
| Repairing | Atlas is repairing the cluster. |
| Deleting | The cluster is being removed. |
| Unknown state | Atlas returned a state that the extension cannot classify. |
A cluster can be connected only when it is running, reports the IDLE state, and provides an Atlas connection string. If these conditions are not met, wait for the Atlas operation to finish or correct the cluster configuration in Atlas.
The extension may show database-user names that it can read through the Atlas Admin API. It does not retrieve database passwords. Enter the password for the selected database user.
You can create the same connection without first browsing the tree:
The project list includes a Manage MongoDB Atlas Credentials option. Select it when the project or cluster you need is not shown. After adding or updating a credential, start discovery again to load the updated resource list.
After you save a discovered cluster, it appears in DocumentDB Connections like any other connection. You can work with the connection without reopening the discovery tree.
Changing or removing an Atlas discovery credential does not delete a saved connection. The saved connection still requires valid Atlas database credentials and network access.