Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT

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.

It could be incredibly helpful if we had a way to set a schedule to pause any given cluster as well as a schedule to un-pause it. This would help with cost savings and would allow to shutdown development clusters on weekends, after hours and holidays.

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?

Mongorestore allows for the number of concurrent insertion workers per collection to be increased using the --numInsertionWorkersPerCollection option.

However, this is not available for mongomirror -- while you can increase the number of collections copied in parallel (--numParallelCollections), there's no parameter surfaced to allow more inserts to be occurring at the same time over multiple threads within each collection.

|t would be helpful to have a parameter like this to use to increase parallelization in order to increase the speed of migrations of large collections.

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.

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.

If I already have Cloud Manager backups, or can take an EBS snapshot, I want to be able to quickly Live Migrate this replica set to minimize migration time and load on my existing infrastructure.

Upload good tutorials in YouTube about connecting mongodb atlas with available three options.

Test environment are usually paused during the night and the weekends. Currently the only way to do that is to automatise a RestAPI call or call mongocli automatically (e.g. via crontab)
Would be nice to allow to define a time windows on which the cluster stays pause via UI

Currently to search through logs we have to download them and search through each log. It would be helpful to have a log browser capability that would allow us to look through and search all logs from the Atlas portal interface.

Atlas replica set members are pre-configured with tag sets: https://docs.atlas.mongodb.com/reference/replica-set-tags/

There's no way to see what the tags are set to via the UI. It would be helpful to see this information.

Please enable security key (e.g. https://www.yubico.com/gb/product/yubikey-5c-nfc/) option for MFA. Ideally using FIDO2 protocol

Live Migrate allows for migrations from non-Atlas clusters into Atlas by syncing data from the source to the Atlas destination, and then cutting over the application to direct workload to the destination.

It's possible to test the application on the destination before cutover, but after cutover, there's no way to sync data in reverse in case unforeseen issues arise and it's necessary to fall back to the source (or another) cluster again.

Having a "fallback sync" option could help with this.

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 ..

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 dashboards