While using AWS multi-region key, if a customer selects a new region for their CMK, Atlas will trigger a key rotation process which could take some time to complete depending on the disk usage. Can we introduce native support for AWS multi-region key so Atlas does not have to re-encrypt data if CMK ID is the same in the new region.

https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html

Currently Project Owner permission is required to create and manage data lake clusters. This requires dangerously elevated privileges simply to manage Data Lake.

I simply would like to either use existing project roles or create new roles specific to Data Lake with similar duty segregation: Data Lake Manager(similar to Project Cluster Manager), Read-Only, Read-Write, etc.

Project Owner should not be required to administer or use data lake features. Non-granular roles are fine for this urgent need, we simply need reasonable coarse-grained roles that would satisfy usage in any security-minded enterprise.

Currently Project Owner permission is required to create and manage data lake clusters. This requires dangerously elevated privileges simply to manage Data Lake.

I simply would like to either use existing project roles or create new roles specific to Data Lake with similar duty segregation: Data Lake Manager(similar to Project Cluster Manager), Read-Only, Read-Write, etc.

Project Owner should not be required to administer or use data lake features. Non-granular roles are fine for this urgent need, we simply need reasonable coarse-grained roles that would satisfy usage in any security-minded enterprise.

Support live migration between Atlas Clusters through Atlas API. If we need to migrate, it'd be good to be able to do so through the API.

sorry to say but your service is very bad because when i upload a data collection after few hours my data automatically jumbled.

please send me the reason why this is happening.

It would be great to select specific privileges for on the Organization Level as well. Similar to what one can do on the Project Level. E.g. Org Member but without being able to see billing.

We had just migrated to another platform probably we did not approach you earlier

Target all Users of SAP !

kamal@zehan:~/Desktop/mongodb$ mongo "mongodb+srv://cluster0.d9ct7.mongodb.net/myFirstDatabase" --username mongo
MongoDB shell version v5.0.5
Enter password:
connecting to: mongodb://cluster0-shard-00-00.d9ct7.mongodb.net:27017,cluster0-shard-00-02.d9ct7.mongodb.net:27017,cluster0-shard-00-01.d9ct7.mongodb.net:27017/myFirstDatabase?compressors=disabled&gssapiServiceName=mongodb&ssl=true

*** You have failed to connect to a MongoDB Atlas cluster. Please ensure that your IP allowlist allows connections from your network.
Error: bad auth : Authentication failed. :
connect@src/mongo/shell/mongo.js:372:17
@(connect):2:6
exception: connect failed
exiting with code 1

After X number of days/months (say 12 months), accounts that haven't been accessed or have never been accessed go into a 3 month freeze period, before they are automatically disabled and deleted. A report of such accounts should be auto generated and archived. The freeze period intention sends a warning to the account holder as well as an alert to administrators of the atlas org.

Enable the use of the in-memory storage engine in atlas shards. That way atlas users can get the same level of functionality as enterprise. Atlas is a great platform, but not being able to use an in-memory storage engine replica set in a shard is a huge letdown (at least for me).

Hi,
Our clusters are in auto upgraded feature of MongoDB versions right now.

We want to stop the auto upgrade feature for now and migrate our clusters to new one with the MongoDB version 5.1.0.

But, when we try to create a new cluster it's not showing the option for version 5.1.0.
And we need 5.1.0, because we're going to restore the data from the current cluster which is versioned 5.1.0.

Your help is much appreciated.

Fix the broken link pointed out in the attached image.

Linode is a widely used cloud provider between developers that do not like the outrageous interface & costs of the main providers (Google, Atlas, AWS). Linode has free in-network bandwidth as well, making for private connections to be much cheaper.

No allowing non-voting members criples the ability to combine regional failover, while keeping the application servers in just two regions, where the event of having a third region primary may imply high latencies, that impacts SLOs.

This particular severe for architectures that rely on 2 main datacenters (regions) and use a 3rd for tiebreaking purposes only.

there should be option to download log files as native format, as we need to download multiple tools to get it to normal!!

The whole process of setting up the new 2FA or MFA is very tiring. It should be simplified with the roles who can add new members and set up the method for new team members.
Chat was helpful but it's not easy to follow up for every team person.

Also for a change in phone or lost device should have some details to get ahead for the user to access the db, after authentication.

As authenticator app gets lost with the device, it should not end in loop where it keep asking for Admin password.

The intercom window frequently pops up and blocks information when I log in to Atlas or refresh a page. This is annoying and it should never open automatically (or at least I should have an option to make it never open automatically)