Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
449 results found
-
Support for AWS China (Beijing/Ningxia) regions
Please make Atlas available in AWS's Beijing/Ningxia regions. This is important to due to China's internet restrictions to achieve the best possible performance/latency for our Mainland China customers.
14 votes -
max database users not visible
We need more than 100 database users, and have had the limit raised for existing projects, but new projects require us to have the limit increased. There is no way for us to verify which projects have the default 100 database users and which ones have had the limit raised. It would also be nice to track the percentage or number of database users available as a metric.
14 votes -
mongomirror with db rename
We have a need to rename our databases as we sync them over to Atlas. However, mongomirror doesn't support that. So that leaves us with mongodump and mongorestore but our databases are large enough that we can't take the outage window necessary to go down that path. When will mongomirror support renaming databases during the import process?
14 votes -
[Atlas] Enforce password policy for DB access
Currently is not possible to enforce any kind of password policy via Atlas UI.
Would be nice to let user define an expiration time and password policy that user should meet.14 votes -
Allow Alerts to be sent to an Atlas Team
Alerts can be configured to send to specific Atlas Users, but not Atlas Teams, which diminishes the value of setting up a team of users.
14 votes -
Ability to choose a Primary shard for newly created database
In a multi tenant architecture, the isolation of a tenant on a specific shard (when database sharding is involved) is expected. At this time, the ability to choose a Primary shard for newly created database would come in handy
13 votes -
Compact collection from UI
Compacting of a collection directly from the MongoDB Atlas website UI.
No need to run CLI commands and changing primary database.
Making regular maintenance easier.
13 votes -
Managed compact command
Hi there
MongoDB Atlas is a great service that offers out of the box a lot of cluster management command that will be otherwise tricky to perform without a great knowledge of mongodb.
Something that lacks in my opinion is related to disk management and especially when it comes to reclaim free space.
In my experience occured that for this scenarios:- Usage of online archive functionality to move huge amount of data
- Changes in the behavior of the application that relies on the cluster
- Or a bug in the application
Some collections (or the oplog) are left with a huge…
12 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 -
pause
An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.
12 votes -
Provide Atlas support for "Classic" VNet Peering topology
Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT
12 votes -
Extend / Configurable retention time of audit logs
This is a feature request to extend or have configurable retention time of audit logs more than 30 days in Atlas.
12 votes -
UUID Schema Validation
It would be very handy to have the ability to specify a schema validator using bson type UUID (binData subtype 4) instead of the more generic binData subtype 0.
11 votes -
Allow db.killOp() and manual restarts on secondaries
Please allow us to kill user threads on Mongo secondaries. Sometimes we have long running queries on secondaries and need to kill those threads but can't do anything about it since we don't have admin privileges to kill threads.
Also please add the ability to manually restart secondaries, not just failover the primary.Thanks.
11 votes -
billing
The billing invoice is split by project. If we have multiple team in the same project, it a puzzle. We need to bill by cluster in this case.
11 votes -
Being able to change the cluster name
a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..
11 votes -
Atlas - Queue cluster pause request to perform it when it's possible
It is impossible to pause a cluster that was recently resume.
The documentation indicates it is a voluntary feature (https://www.mongodb.com/developer/products/atlas/pause-resume-atlas-clusters/) to allow the Atlas service to apply any pending changes or fixes to the cluster that may have accumulated while it was paused.
I agree with this, but it cause a problem for automation (for example sometimes we launch a platform exclusively for testing purpose and then shut it down, it is complicated to add a delay for pausing the Atlas cluster) and even manually for example at the end of the day of work this requires either…
10 votes -
Use wildcard databases in user role privileges (like collections)
Use wildcard databases in user role privileges (like collections)
10 votes -
storage autoscaling at N %
Dear Mongo Team,
Your engineers advise to add more storage to the clusters when it reach 80 % usage as this is when performance degradation can occur. At the time of writing the autoscaling happens at 90 % disk usage. We want to be able to adjust at what % of usage the autoscaling happens and set it to the value of 80 % basically what your engineers advise.
10 votes -
Live Migrate modal: Allow users to point and click to select another Atlas source cluster
It is often practical to Live Migrate from one Atlas cluster to another Atlas cluster (e.g. to create another staging environment if backups are not enabled on the source, or migrate a production/staging environment to another dedicated project with minimal downtime).
Currently, the Live Migrate modal requires connection details from the source cluster, including the hostname of the primary, port, etc. Validation will fail if there are typos/errors in these inputs.
It would be easier to have a point-and-click option to "Migrate from another Atlas cluster" -- it could be a drop-down menu with names of other Atlas clusters in…
10 votes
- Don't see your idea?