It would be great if we could organize the projects and not have them all at the same level of organization.
We could use this hierarchy to put rights, consult costs ...
A bit like the idea of Azure's management group or GCP's "Folder".

Create databases (DB) and collections via API thorough Terraform after the cluster has been created in Atlas. This would provide the ease of writing and running it in a single script before any data is loaded.

Allow auto-scale for IOPS.

At present the finest granularity of ATLAS metrics is 1 minute ,as the metrics are averaged by 1 minute , this would not provide info on spikes lasting less than few seconds
reducing the granularity to 1 second would give more insight

Have an Export feature WITHIN Atlas UI (Data Explorer) where user can perform (select collection and export as .csv/.json directly from the website without using Compass/data dump) option for collection integrated into (JS) MongoDB Atlas Cloud.

mLab had the option to create a single-node deployment, which was very nice for development environments where redundancy isn't important, but keeping costs down is.

Would be nice to see this in Atlas as well.

there are really 3 steps for our dev teams to get moving in Atlas:
1. create an org
2. create a project
3. create a cluster
the first one is the only one that still has to be done from a console. if we had a terraform script to create an org in our account, we could trigger creation after approval in ServiceNow

Hi,

We'd like to have the ability to remove documents from an Online Archive. Mainly based on a date, but possibly other criteria.

Thanks!

Add support to send cluster metrics to Elastic. Elastic has recently been putting a lot of work into their APM and logging solution, this is now a viable alternative to NewRelic and Datadog and is gaining traction. It would be great if Atlas supported sending metrics to Elastic. Please see below for references

https://www.elastic.co/apm
https://www.elastic.co/siem

The use case for this is the same as NewRelic or Datadog. I wish to monitor my Atlas clusters from inside Elastic, create dashboards and set up alerting

Allow the "SET GLOBAL mongodbmaxvarcharlength = n" to be permanent after a Mongosqld restart. Currently, the setting is ephmeral and must be set everytime the mongosqld daemon is restarted. Currently, our production environment mongosqld can restart without our knowledge at anytime. This results in the mongodbmaxvarharlength variable being reset to zero, which can lead to a production outage. Is there anyway this can be automated, maybe through database trigger?

Hi.
We would like to have the possibility to administrate user rights also for the Billing area. In order to restrict all users seeing the invoices and to give this right only to particular people who are directly responsible for it. Please consider such feature for the next releases.

Ability to add indexes after new clusters are created using Terraform and data has been loaded. It will help in more automation and auto recovery.

Currently a project is created with a set of default alerts. We need to customize these but we can only add new alerts via terraform. It would be helpful if there was a boolean flag in the mongodbatlas_project resource to disable default alert creation

Add a button/toggle to Hide and Unhide an Index from the Data Explorer/Indexes display for a 4.4+ deployment.

It would be nice to have the killOp() action exposed when creating a custom role in Atlas.

I also think it would make sense to grant this action to the atlasAdmin role, but at a minimum I feel that Project Owners should be able to create a custom role that is allowed to kill ops that were initiated by other database users.

Would love to see an official connector to ServiceNow for automatic ticket creation triggered by various database alerts.

I have customers that would like the ability to retain annual snapshots going back 5 or so years for compliance reasons. Currently, you can do this with monthly snapshots by retaining for 5*12 months, but then you have to store all the monthly snapshots in between.

An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.