Please release a dark mode MongoDB Atlas interface. Thank you.

We have a single project set up for our application, and multiple clusters under that project. Right now, it's impossible to create database users who only have access to certain clusters - the only configurable option is "database name".

The issue is that some of the clusters have the same "database name" but I don't want them to be able to access a database in a specific cluster, though I do want them to access a database with the same name in a different cluster.

Any plans to implement this?

We would like the ability to configure an auto scaling cluster via Terraform. Currently we need to modify our cluster after its creation via terraform to setup auto scaling parameters.

We would like to be able to use Terraform to configure LDAP authentication/authorization on projects.

The functionality is available via the API:
https://docs.atlas.mongodb.com/reference/api/ldaps-configuration/

However, go-client-mongodb-atlas does not have these endpoints implemented, so that would need to be done before this functionality is included in the provider.

The ability to pause Atlas clusters through terraform would help with being able to pause our non-prod environments when not in use. Currently this has to be managed directly with the Atlas API

It would be great if I could connect to and run commands against my cluster via the Atlas UI so I don't have to rely on downloading and running the shell locally.

I'd also be more confident I was running commands against the right cluster as I would have less reliance on managing connection strings and differentiating between them. This would be helpful if I'm not on my regular machine and need to do some ad-hoc querying or debugging.

Add a terraform resource for third party integrations (such as PagerDuty) to allow it to be set up.

Often in the cluster card, or in the cluster panel, one or more processes are marked with a yellow warning icon (instead of a green dot). However there is no indication about what this means or how to fix it.

Can there be a tooltip or explanation about what this icon represents?

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

It would be good if users are able to modify their First and Last Name after account creation.

Alerts are often very cryptic & don't provide any useful information. For example, when alerting that queries are returning too many rows, without informing me the query or at least the collection, that's very useless. I'm looking at a replication oplog window alert right now and I have no idea what to do about it.

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

Please add support to change the backup policy for Cloud Provider Snapshots.

This is the API I am referring to:
https://docs.atlas.mongodb.com/reference/api/cloud-provider-snapshot-schedule-modify-one/

Thanks.

It would be great to add more granularity when creating an Atlas-managed X.509 certificate for a MongoDB user, i mean by day at least.
Thank you

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.

We have a platform (as code using Terraform) where we integrate Mongo Atlas in AWS. We have multiple teams with various privileges who access the Mongo Atlas console daily basis. We would always like to manage the users in our version control. As Terraform is one of the best infrastructure configuration tools, we would like to have a terraform resource in order to manage the users via.

I would like to have an alert setting when MongoDB Atlas's performance advisor has any recommendations.

Currently there is no way to determine if the performance advisor has a suggested improvement on the main project console page.

Our prod project has a lot of clusters(with more planned). It is cumbersome to go in and check each one manually.