Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
- or
1372 results found
-
Improve dashboard loading times from 3.5 minutes
Currently the dashboard takes well over 3.5 minutes to load on a gbps broadband connection waiting for
2 votes -
2 votes
-
Allow longer session duration values for Atlas UI
Currently Atlas allows configurable session timeout in Organization Settings, however it does not allow setting absolute session timeout above 12 hours. Need longer session durations.
1 vote -
1 vote
-
Dropdown State Bug: First Expandable Menu Item Becomes Unresponsive
I'm experiencing an issue with the user menu/dropdown component in the Atlas UI. There are dropdown items that contain expandable sub-menus, but I've noticed a bug where the first expandable item stops working after interacting with other expandable items. Specifically, after opening and closing any secondary expandable menu item, the first one becomes unresponsive and won't open/close anymore. This appears to be a state management issue where the first dropdown's toggle functionality is being disabled after other dropdown interactions occur.
1 vote -
Set Project Time Zone using cloudformation template
Currently the Project Time Zone setting can only be updated using Atlas UI , it is not yet supported in the project resource configuration. We are looking into not having any manual intervention and have everything done through IaC.
1 vote -
FinOps Cost Export - FOCUS Data Model
We need to export MongoDb Atlas, … usage data in FOCUS format to handle those in our internal automated accounting.
FOCUS is an essential part of FinOps Foundation evolved to be a industry standard.
We need that to automate internal cost allocation for all resources being part of our Cloud Infrastructure Platorm. MongoDB is on eoffering as part of that internal platform.
1 vote -
I don't even know what my username is. It displayed briefly, I copied the password, and then both the username and password disappeared!
Fix this mess!!!!
1 vote -
Enable though API a WAY to check status of SCRAM-SHA-256 at project level
There is no way for us to currently check the status of SCRAM-SHA-256 enablement at project level. We would like to have this feature enable at API level in order to have a better management and transparency with our configurations.
1 vote -
Bug Report - Login Issues
When signing up or signing in on MongoDB Atlas, if I enter a password and place the cursor in the middle of the input field to delete a specific character, pressing the Delete key removes the last character instead of the one at the cursor.
This makes it frustrating to fix typos and feels unintuitive. It seems like a bug with the input handling in the password field.
I've attached a screenshot to show the issue. Steps to reproduce:
Type a password (e.g., password123)
Place the cursor before the "o"
Press Delete
Instead of removing "o", it removes "3" (last character)
When signing up or signing in on MongoDB Atlas, if I enter a password and place the cursor in the middle of the input field to delete a specific character, pressing the Delete key removes the last character instead of the one at the cursor.
This makes it frustrating to fix typos and feels unintuitive. It seems like a bug with the input handling in the password field.
I've attached a screenshot to show the issue. Steps to reproduce:
Type a password (e.g., password123)
Place the cursor before the "o"
Press Delete
Instead of removing "o", it removes "3" (last…
1 vote -
in Atlas, a Resync button, as we have in OPS Manager
it should be interesting to have in the Atlas UI, a RESYNC button, as we have in OPS Manager, when we want to trigger a rsync on a node.
1 vote -
Support safe handling of shared project IP access list entries in Terraform (prevent deletes when the same IP is used by multiple services).
Description:
We are facing an issue managing project-level IP access lists in MongoDB Atlas when multiple services/profiles share the same IP address.Scenario:
One Atlas Project.
Service is deployed with different cluster profiles (e.g., integration, testing).
Each profile’s Terraform stack provisions:
An Atlas cluster (mongodbatlasadvancedcluster)
A backup schedule (mongodbatlascloudbackup_schedule)
A project IP access list entry (mongodbatlasprojectipaccesslist) using the same IP address.
Behavior Observed:
Integration profile deployment:
Creates cluster, backup, and adds Gateway IP to the project access list.
Testing profile deployment (same service, different profile):
Creates a second cluster and backup.
Attempts to add the same Gateway IP.
Atlas API accepts it (idempotent) → no duplicate error, but no new entry is created either.
Terraform state for the testing profile still assumes ownership of that IP entry.
Delete testing profile:
Destroys cluster and backup.
Also deletes the Gateway IP from the Atlas project (because state thinks it owns it).
Result: the integration profile’s cluster loses access, since the shared IP entry is gone.
Problem:
mongodbatlasprojectipaccesslist does not support safe handling of shared IPs across multiple Terraform states.
Unlike AWS Security Group rules (which have unique IDs per rule, making deletes safe), Atlas identifies IPs only by the IP address string.
This creates a state ownership conflict: one stack can remove IPs required by another.
Description:
We are facing an issue managing project-level IP access lists in MongoDB Atlas when multiple services/profiles share the same IP address.Scenario:
One Atlas Project.
Service is deployed with different cluster profiles (e.g., integration, testing).
Each profile’s Terraform stack provisions:
An Atlas cluster (mongodbatlasadvancedcluster)
A backup schedule (mongodbatlascloudbackup_schedule)
A project IP access list entry (mongodbatlasprojectipaccesslist) using the same IP address.
Behavior Observed:
Integration profile deployment:
Creates cluster, backup, and adds Gateway IP to the project access list.
Testing profile deployment (same service, different profile):
Creates a second cluster and backup.
Attempts…
1 vote -
Support safe handling of shared project IP access list entries in Terraform (prevent deletes when the same IP is used by multiple services).
Description:
We are facing an issue managing project-level IP access lists in MongoDB Atlas when multiple services/profiles share the same IP address.Scenario:
One Atlas Project.
Service is deployed with different cluster profiles (e.g., integration, testing).
Each profile’s Terraform stack provisions:
An Atlas cluster (mongodbatlasadvancedcluster)
A backup schedule (mongodbatlascloudbackup_schedule)
A project IP access list entry (mongodbatlasprojectipaccesslist) using the same IP address.
Behavior Observed:
Integration profile deployment:
Creates cluster, backup, and adds Gateway IP to the project access list. ✅
Testing profile deployment (same service, different profile):
Creates a second cluster and backup.
Attempts to add the same NAT Gateway IP.
Atlas API accepts it (idempotent) → no duplicate error, but no new entry is created either.
Terraform state for the testing profile still assumes ownership of that IP entry.
Delete testing profile:
Destroys cluster and backup.
Also deletes the NAT Gateway IP from the Atlas project (because state thinks it owns it).
❌ Result: the integration profile’s cluster loses access, since the shared IP entry is gone.
Problem:
mongodbatlasprojectipaccesslist does not support safe handling of shared IPs across multiple Terraform states.
Unlike AWS Security Group rules (which have unique IDs per rule, making deletes safe), Atlas identifies IPs only by the IP address string.
This creates a state ownership conflict: one stack can remove IPs required by another.
Description:
We are facing an issue managing project-level IP access lists in MongoDB Atlas when multiple services/profiles share the same IP address.Scenario:
One Atlas Project.
Service is deployed with different cluster profiles (e.g., integration, testing).
Each profile’s Terraform stack provisions:
An Atlas cluster (mongodbatlasadvancedcluster)
A backup schedule (mongodbatlascloudbackup_schedule)
A project IP access list entry (mongodbatlasprojectipaccesslist) using the same IP address.
Behavior Observed:
Integration profile deployment:
Creates cluster, backup, and adds Gateway IP to the project access list. ✅
Testing profile deployment (same service, different profile):
Creates a second cluster and backup.
…
1 vote -
Filtering and Pagination in Atlas Admin API for Downloading DB Logs
We are working on Sentinel (SIEM tool by MSFT) integration. We are using Atlas Admin API to download logs and ingest into Sentinel. But as there is no option to filter the logs, we have to do it in our Sentinel solution and also burden the customer with unnecessary N/w costs. If we could add filtering based on Category Type, ID etc. it will be great help for SIEM integrations. Also, adding options to assist in pagination would also be of great value. Like we could say greater than particular record and limit to "N" number of records.
1 vote -
Request for Pre-Maintenance Visibility in MongoDB Atlas UI
We would like the MongoDB Atlas UI to provide visibility into scheduled maintenance events, including the specific changes that will be applied. Currently, we are only able to view these details after the maintenance has occurred, which limits our ability to assess potential impact in advance. To improve planning and ensure system stability, we request a feature that allows users to view planned changes ahead of time—either through the UI or CLI.
1 vote -
Intro to MongoDB Learning Path Issue : I could complete 25% very long back. Kindly permit me to complete the remaining part and resume path
Intro to MongoDB Learning Path Issue : I could complete 25% very long back. Kindly permit me to complete the remaining part and resume path
1 vote -
CMK - Customer Master Key Region to allow multiple regions to select
Currently while setting up CMK for cluster only allowed to give one region as "Customer Master Key Region". For multi-region cluster, in case of Region outage, though MongoDB promotes writer to cross region, customer needs to re-configure the "Master Key Region" to another available region. If customers are using multi-region CMK, selecting only one region as "Master Key Region" needs manual intervention incase of region failures.
Could you have multiple region option "Master Key Region" to support multi-region CMK.1 vote -
Preventing archives from being orphaned due to certain sharding operations
When performing a moveCollection operation to move an unsharded collection from one shard to another, it would be ideal if the archive did not become orphaned. It would likewise be ideal if resharding and disabling sharding on a collection did not cause the archive to become orphaned.
1 vote -
We would like to know the how to find out the inactive atlas cluster which are not actively using user more than two weeks and how to pause
We would like to know the how to find out the inactive atlas cluster which are not actively using user more than two weeks and how to pause those cluster automatically which help us to save cost.
1 vote -
We would like to know the how to find out the inactive atlas cluster which are not actively using user more than two weeks and how to pause
We would like to know the how to find out the inactive atlas cluster which are not actively using user more than two weeks or some specific period and how to pause those cluster automatically which help us to save cost.
1 vote
- Don't see your idea?