Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
426 results found
-
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 -
[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.13 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.
13 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 -
More granular permissions *for API keys*
Allow API keys to have much more granular permissions (i.e: only the functions one may need to do a certain task).
Also, add a security category in the form to report possible improvements for Atlas.
And a UI/UX one.12 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.
12 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.
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 -
API Improvements - OpenAPI and more auth options
The API should be documented with OpenAPI to allow better tooling.
Ideally using the above OpenAPI spec you could auto generate a SDK or API client for popular languages.
Lastly, the API should accept authentication options other than digest. There is very poor support for digest authentication by popular HTTP clients. I don't like trying to implement security protocols myself, as there is often some quirk I have not fully understood that ends up leaving me less secure than I hoped.
In many questions online when searching for information about digest authentication, the person asking the question is asking about…
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 -
Credits API
I need an API that will allow access to the items under credits in the billing page.
This will allow me to pull this information daily into our master usage database to support our dashboards11 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.
10 votes -
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.
10 votes -
API Key Expiration date
We have a security reqirement that secrets must expire after 2 years.
Therefore it would be awesome if MongoDB Atlas API Keys would support an expiration date.
Somethig similar exists for the IP Whitelisting. Here we have the option to remove IP Whitelist entries after er certain time period. But for API Keys it would be better to have an expiration date and keep the API Key in the list even if its expired.
In addition it would be good to have a daily notification once the expiration date is ahead less than 30 day.
10 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.
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 -
Share API key cross organizations
Today, it's not possible to share an API key between different organizations (https://www.mongodb.com/community/forums/t/sharing-api-key-between-different-organizations/190785/13)
It makes it impossible to restore snapshots from one organization to another automatically.It's very important for us, as we need this feature to clone our customers clusters into our organization
9 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.
9 votes -
Public API to get cluster pricing
Currently, we have to use the UI to get a pricing estimate for a cluster. Having a programmatic way to get this estimate would be very valuable.
9 votes
- Don't see your idea?