It is really helpful to get use of indexes in numbers in last 24 hours to eastimate the use of particular index.

The "Host has index suggestions" alert notification does not contain any reference to the host/deployment that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.

can you make it so that you can connect from mongodb like you would in mongoose

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.

We are currently looking for a solution to secure our Atlas backups.

Something similar to AWS Glacier Vault Lock [1] or a simple grace period before backups are deleted once and for all would be nice.

It would be amazing to protect the Atlas backups from being deleted.
Currently, if one of our Atlas admins was compromised, the damage for the company would be enormously high. So we need to implement measures against the final deletion of our most mission critical data.

also mentioned in: [2]

[1] https://aws.amazon.com/de/blogs/security/amazon-glacier-introduces-vault-lock/
[2] https://developer.mongodb.com/community/forums/t/is-there-a-vault-lock-for-atlas-backups/11041

Unlike a connector (https://feedback.mongodb.com/forums/924145-atlas/suggestions/40688308-splunk-connector-for-atlas) it would be useful if Alerts could be sent to Splunk.

To speed up recovery after restoring from a snapshot or having a node replaced, it would be nice to have the option to use AWS Fast Snapshot Restore

https://aws.amazon.com/blogs/aws/new-amazon-ebs-fast-snapshot-restore-fsr/

This would allow the disk to have full performance as soon as available.

In the API documentation you mention a regions parameter usable when creating a network container with a network smaller than /18. In terraform there is no such parameter. I would like to see that supported (for creating networks smaller than /18 on GCP).

See: https://docs.atlas.mongodb.com/reference/api/vpc-create-container/#request-body-parameters

When adding IP addresses on a cluster/project (Network Access), it would be great to be able to provide a comma-delimited list of IP addresses instead of having to enter them one-by-one.

When filling in the password field in Atlas user, sometimes I click show then start typing a new password, or Home/end to highlight it. Somehow half the time it dismisses the dialog and I have to start over.

I suspect it is the dialog losing focus. Stop dismissing the dialog when I click off of the box. Other dialogs do the same thing. A lot of web apps do that now and it seems really dumb -- save one specific Cancel click to aggravate me many more times when the dialog I have worked on for 5 minutes disappears.

At the moment, Project Timezone setting can only be done via Atlas UI. We are automating project and cluster creation and setup for our application. We need an API to update Project Timezone setting just like other project settings. This feature is important for our organization to keep all the project with the same settings without a manual intervention.

Currently there is no way to test how applications behave during maintenance apart from waiting for maintenance, the ability to force a rolling cluster restart as happens during maintenance would be great. The failover is a different process and affects primary mainly.

As described in https://docs.mongodb.com/manual/tutorial/configure-a-hidden-replica-set-member/, on-prem mongodb deployments allow to configure a hidden replica set members which are good for workloads with different usage patterns from the other members in the replica set. It would be useful to have similar functionality for Atlas replica sets.
In fact, to elaborate, being able to configure an on-prem hidden replica set member for an Atlas replicaset will help in meeting regulatory requirements where organisations are required to host a near real time mirror of data on on-premises.

It could be very interresting to be able to setup the retention of the events by organisation, projets and clusters. Actually I understand that this value is 30 days. So it to short for us, so we need to download the activities logs and it difficult to seach in files after that.

Events (in the perimeter: organization, projects, cluster) are useful for monitoring activities. But it would be very useful to be able to set the alarm on these events. The goal is to be informed when certain actions occur.

The best is to be able to have a configuration control policy. Especially to control security, network configuration, etc ...

For example:
- Be able to avoid the use of user scram.
- Be able to avoid using unauthorized IP addresses
- Be able to avoid changing the configuration of access to database data (DataExplorer) from the Atlas portal

When performing a forensic analysis for the purposes of a restore, in order to determine the appropriate point in time when our data was last "sane", it would be awesome if we could start with a point-in-time restoration, and play the journal forward, e.g. performing a bisect on the data.

Currently all IdP federation set up must be done in the Atlas GUI. This prohibits scripting the setup of IdP organization and role mapping for new projects.

Customers can prefer setting this up via a scriptable Rest API interface for a new project. Everything else about the project has an API that is currently used to create projects and deploy clusters. Authentication is important part of the process and currently requires manual set up through the GUI.

On the Private Endpoint (and VPC Peering) setup screen in Atlas, present options to:

• include or modify "security group"


• attach a "tag = name"

That way when user has the AWS CLI command generated, it includes security & tag

On Atlas when creating private endpoints, add comments field to allow easier identification.