Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
468 results found
-
Feedback and public roadmap.
I have voted and written since 2020 several improvement ideas for your platform.
Being a client for a major insurance company, I'm disappointed to see that for several suggestions dating back more than 12 months, it doesn't even seem to have been looked at by your team.
It would be more than interesting to have an idea for your roadmap as well as a dynamic management of the catalog of ideas (feedback) maintained by your customers.
I consider this a lack of respect for your users and customers.
Some examples:
https://feedback.mongodb.com/forums/924145-atlas/suggestions/40638277-atlas-backup-to-second-region
https://feedback.mongodb.com/forums/924145-atlas/suggestions/43289796-max-database-users-not-visible
https://feedback.mongodb.com/forums/924145-atlas/suggestions/42163234-authentication-on-azure-iam
3 votes -
Atlas UI Show Snapshot ID in web
Please provide a capability to show the snapshot ID of a snapshot in the web GUI, currently we have to make an API call to get the snapshot-id
4 votes -
Create Atlas UI Triggers Programatically
Currently, a trigger which gets displayed on the Atlas UI (under Data Services > Triggers) cannot be created programmatically, they may only be created by clicking through the Atlas UI.
The triggers created from the Atlas UI automatically creates a new realm app named "TriggersRealmApp" even when a realm app with the same name already exists. There is no way to have any of the triggers created under any other realm app displayed in the Atlas UI. The only way is to create them under the auto generated "TriggersRealmApp" which gets created after the first trigger from the…
6 votes -
Download file button for GridFS on Atlas GUI
When using the "Browse Collection" feature from the Atlas Web frontend it would be nice to be able to download/view files stored in GridFS. Tools like "Studio3T" or "NoSQLBooster for MongoDB" support that use case.
2 votes -
Automatically detect location for Global Clusters
Currently Global Clusters require a location field for zone targeting. Could the user get an option to be auto-detected based on the incoming connection? The reason for this is, not all app services have the ability to include location, so would be good to auto-detect it.
1 vote -
AWS multi-region key (CMK)
While using AWS multi-region key, if a customer selects a new region for their CMK, Atlas will trigger a key rotation process which could take some time to complete depending on the disk usage. Can we introduce native support for AWS multi-region key so Atlas does not have to re-encrypt data if CMK ID is the same in the new region.
https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html
4 votes -
Multiple connection URLs for Atlas clusters
Allow generation of multiple application-specific connection strings/URIs to the same Atlas cluster. This would ease migration of databases to different clusters over time; consolidating smaller databases to lower costs, or separating busier databases to isolate performance impact.
Multiple connection strings will allow us to redirect connections seamlessly when migrating databases without requiring developers to re-deploy changes to application connection strings, minimizing downtime and coordination.
1 vote -
Reshard Global Writes Collections
MongoDB supports resharding, so not being able to change the global writes shard configuration is very strange. It makes it impossible to fix mistakes with the shard configuration. Even if it requires blocking to redo or remove the shard configuration it should be possible.
2 votes -
Make Real Time Performance Panel, Data Explorer and Performance Advisor and Profiler GDPR compliant
As the data used for Real Time Performance Panel, Data Explorer and Performance Advisor and Profiler are processed/routed in/over the USA european customers that need to be GDPR compliant can't activate those three options. Unfortunately these three features offer a great feature set which really hurts to not have. This is a high prio topic for us.
2 votes -
Need "Inactive" sessions "Terminated" connected via Atlas
We need a feature that would automatically timeout individual user "inactive" sessions after x number of minutes, connected via Atlas. Thanks
1 vote -
TDE Encryption Key automatically rotation
when we got the alert like "Azure encryption key needs rotation", we need connected to our it team and they rotated the key in azure key vault then they shared us the value of new Key Identifier, then we logged into atlas and under security-->Advanced under that we updated the Key Identifier under Encryption at Rest using your Key Management option, all these steps we were done manually.
Is it possible to rotate/update the key automatically, when the key is rotated in azure key vault, without doing it manually.
1 vote -
Add filters for easily finding projects that have encryption/audit enabled in the UI
The https://cloud.mongodb.com/v2#/clusters has certain filters to get specific Atlas clusters. Can we add couple of more filters that can easily identify, whether that project has been enabled for encryption at rest or if the auditing has been enabled/disabled. This will help us easily generate reports for cis20 reporting.
1 vote -
Allow --removeAutoIndexId option to Atlas live migration as default
Apparently Atlas live migration does not support --removeAutoIndexId option due to which some collections having
autoIndexId set to false
does not allow live migration to work successfully. Please add --removeAutoIndexId option to live migration.1 vote -
Support migration between Atlas clusters using Atlas API
Support live migration between Atlas Clusters through Atlas API. If we need to migrate, it'd be good to be able to do so through the API.
2 votes -
Add Atlas users to existing teams even though the Atlas user is still pending invite
Currently when we send invite emails for the organization we have to wait for the users to accept the invite before we are able to configure project level permissions. This often creates confusion and bad user experience; when users first sign in they are anticipating to see their projects but instead they see nothing until configuration is finalized.
Please make it possible to add users to teams which are still pending invite acceptance so the user experience is more seamless and less confusing.
8 votes -
API for Granting Infrastructure Access to MongoDB Support for 24 Hours
As per documentation at https://www.mongodb.com/docs/atlas/security-restrict-support-access/#grant-infrastructure-access-to-mongodb-support-for-24-hours one can grant access for support for 24h only via the UI. It would be very useful to be able to do this via the Atlas API.
1 vote -
Deletion Protection
Customer suggested protection from Cluster deletion similar to AWS RDS
https://www.amazonaws.cn/en/new/2018/amazon-rds-now-provides-database-deletion-protection/
TL;DR - a notification when a user tries to delete a cluster, that "this cluster is protected, if you need to delete please visit the console to enable deletion"
This would be a critical piece of functionality where roles/permissions are not sufficient.
6 votes -
Add Atlas instance in Azure Sweden
We host data that is preferred to reside in Sweden. Do you have plans to expand to the newly added Azure Sweden data centers?
2 votes -
Set MongoDB Production Support Employee Access to Atlas Backend Infrastructure at Project Level
The Restrict MongoDB Production Support Employee Access to Atlas Backend Infrastructure is currently set on the organizational level. This should also be possible at the project level. Secondly, add the possibility to grant access indefinitely until revoked.
12 votes -
Trigger runtime is US by default which is not GDPR compliant for EU countries
The ATLAS Trigger UI should let the user select the region for the realm deployment done in the background. At the moment it's not fair because (1) at no moment you're noticed the runtime will be in the US (and for UE countries it matters a lot, it's not GDPR compliant) and (2) it makes the nice ATLAS Trigger UI useless for UE countries...
We're forced to create a realm app manually to be able to select a local deployment. We appreciated the 'trigger' section on the ATLAS side. It's more integrated and makes following trigger operations easier. Now trigger…
1 vote
- Don't see your idea?