23 results found

1. Dark mode

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

   748 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  112 comments  ·  Other  ·  Delete…  ·  Admin →

2. Cluster Termination Protection

   It is possible to quickly delete an entire cluster, for example through terraform, if you're not careful.

   It would be great to have a "Termination Protection" feature that can only be disabled in the Admin UI and not via the public APIs.

   In terraform I could then enable it like so

   
   
   resource "mongodbatlas_cluster" "my_cluster" {
     enable_delete_protection = true
   }
   

   When I would run terraform destroy the cluster should not be destroyed and instead the API returns an error saying that the Cluster has Termination Protection enabled. If I want to disable it, I can login to the Admin UI, select the cluster, then click "Disable Termination Protection" somewhere.

   AWS has a similar feature where EC2 instances can have Termination Protection enabled. With Termination Protection enabled they cannot be deleted through code, even CloudFormation will throw an issue.

   It is possible to quickly delete an entire cluster, for example through terraform, if you're not careful.

   It would be great to have a "Termination Protection" feature that can only be disabled in the Admin UI and not via the public APIs.

   In terraform I could then enable it like so

   
   
   resource "mongodbatlas_cluster" "my_cluster" {
     enable_delete_protection = true
   }
   

   When I would run terraform destroy the cluster should not be destroyed and instead the API returns an error saying that the Cluster has Termination Protection enabled. If I want to disable it, I can login to the Admin UI, select… more

   66 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   9 comments  ·  Other  ·  Delete…  ·  Admin →
   completed  ·  AdminPhuong-Thao (Sue) (Admin, MongoDB) responded

   You can now set "Termination Protection" for your Atlas cluster.   For more information, see https://www.mongodb.com/docs/atlas/cluster-additional-settings/#termination-protection

3. Ability to create database users limited to specific clusters

   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?

   60 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   13 comments  ·  Other  ·  Delete…  ·  Admin →
   completed  ·  AdminAndrew Davidson (VP, Cloud Products, MongoDB) responded

   Folks I’m excited to share that database users scoped to particular sets of clusters (and Data Lakes) in an Atlas project is now live in Atlas!
   – It is now possible to create database users with privileges scoped to a specific set of clusters or Atlas Data Lakes in an Atlas project.
   – Existing users’ privileges can be edited to reduce their scope to a specific set of clusters or Atlas Data Lakes
   – All authentication mechanisms (SCRAM, X.509, LDAP, AWS IAM) may be used in conjunction with this ability

   Thanks for your patience: this was a long-time coming!

   Cheers
   -Andrew

4. "Chaos testing" for Atlas - simulate node(s) down

   The current "Test Failover" feature supports testing application/driver resiliency in case of elections. For additional testing, we want to be able to cause a node or nodes to be shut down and started up in a cluster. There should be selectivity allowing the entire node or just the mongod or mongos process to be shut down and started up.

   33 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  6 comments  ·  Other  ·  Delete…  ·  Admin →

5. Make it possible to add tags in the Datadog integration so I can tell my staging and production environments apart more easily

   Datadog recommends having only one account and feed data from all environments into it, and then it’s important to tell them apart by using tags.

   Please add the ability to set tags in the Datadog integration configuration, e.g. env:production

   24 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  7 comments  ·  Other  ·  Delete…  ·  Admin →

6. AWS EBS gp3 Volumes

   Please add support for the newly announced and already generally available AWS EBS feature. [1]

   The top capability is: "The new gp3 volumes deliver a baseline performance of 3,000 IOPS and 125 MB/s at any volume size. Customers looking for higher performance can scale up to 16,000 IOPS and 1,000 MB/s for an additional fee." [2]

   That basically means decoupling storage performance from storage size.
   It would eliminate all our IOPS pain as 3000k is more than enough for our usecase. Currently, we are slightly overprovisioning storage size in order to guarantee minimal IOPS performance.

   [1] https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ebs-general-purpose-volumes-gp3/
   [2] https://aws.amazon.com/ebs/general-purpose/

   17 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  4 comments  ·  Other  ·  Delete…  ·  Admin →

7. Provide "Last Login Date" for Atlas users via Atlas API

   The Atlas API should include "Last Login Date" for the GET /orgs/{ORG-ID}/users endpoint.

   14 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  3 comments  ·  Other  ·  Delete…  ·  Admin →

8. Security Key (FIDO2) MFA option

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

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   completed  ·  AdminFuat (Admin, MongoDB) responded

   MongoDB added webAuthn support as an MFA method. Please use "Security Key/Biometric" MFA. option to use it with your FIDO2 keys.

    

   https://www.mongodb.com/docs/atlas/security-multi-factor-authentication/

9. Send alert when there are performance advisor recommendations

   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.

   9 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   5 comments  ·  Other  ·  Delete…  ·  Admin →
   completed  ·  Rez responded

   We released Performance Advisor alerts on Week of Aug 7. It is available as a default alert.

10. Expose minRetentionHours oplog option

    MongoDB 4.4 introduces the new minRetentionHours for the oplog.
    Currently this option is not exposed in the Atlas UI and the command replSetResizeOplog is not allowed.
    Would be nice to have this option available in Atlas (and be accessible via Terraform too)

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Other  ·  Delete…  ·  Admin →

11. Integrate Azure Private Endpoint

    Enable connectivity in Azure using private endpoints

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  5 comments  ·  Other  ·  Delete…  ·  Admin →

12. killop

    I have read the other two suggestions on providing more killOp() and read Andrew's comment on the difficulties in the medium term.

    I just watched a situation where a primary became unresponsive and the queues piled up. The solution was to cause an election, but the dba wanted to kill operations by user (the application user) and couldn't.

    It would be nice to have something more than the real-time panel, which in this situation had become unresponsive as well so it was no use, such as a DBA console where an authorized dba could kill operations started by other users.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Other  ·  Delete…  ·  Admin →

13. Ability to delete account

    I really need to delete my account as this is not what I am looking for.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    8 comments  ·  Other  ·  Delete…  ·  Admin →
    completed  ·  AdminFuat (Admin, MongoDB) responded

    Hello,

    I just want to update this ticket that self-serve account deletion is supported since August 2021. Please note that once you delete your Atlas account, you cannot use the same email to create a new Atlas account. 

    https://www.mongodb.com/docs/atlas/security/manage-your-mongodb-atlas-account/#delete-your-service-account

14. Support for tagging clusters in Atlas

    Please allow tagging at a cluster level. This will help in storing related metadata if required.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Other  ·  Delete…  ·  Admin →

15. Change M10+ cloud providers

    I would like to be able to change the cloud provider and region of a M10+ cluster.
    It would be nice also to have a per-cluster connection string that does not depend on the cloud provider. So we can change the provider and region without changing the application settings.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    completed  ·  AdminChristopher (Product Manager, Atlas, MongoDB) responded

    We have recently released multi-cloud clusters on Atlas: https://www.mongodb.com/blog/post/introducing-multicloud-clusters-on-mongodb-atlas

    This unlocks the ability for you to seamlessly migrate workloads across cloud providers!

    Give it a try and let us know what you think!

16. SSO integration for Atlas UI

    Enabling SSO for the Atlas interface would limit the ability for outside people to gain access to our accounts. It would also provide us with enterprise tools for managing user access.

    Currently we are using Atlas credentials to log into the Atlas frontend. This appears to be a security risk long term as people could hack into our account and create/destroy resources.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Other  ·  Delete…  ·  Admin →

17. Maintenance notification to Slack

    Would like to get notified for maintenance through slack channel as well as in mail or GUI banner

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Other  ·  Delete…  ·  Admin →

18. Shared Clusters upgrade to MongoDB 6.0+

    Currently MongoDB 6.0.1 is only available in dedicated clusters (M10+) and in serverless clusters.

    We need to use MongoDB 6.0.1 or higher in the shared cluster (M0/M2/M5).

    I understand that this should be in the roadmap anyway, but getting it sooner than later would be great.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Other  ·  Delete…  ·  Admin →

19. Add Atlas instance in Azure Norway

    We host data that is preferred to reside in Norway. Do you have plans to expand to the newly added Azure Norway data center?

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Other  ·  Delete…  ·  Admin →

20. Improve OKTA Location Detection

    Hi,

    This is really a message for your security / authentication engineers.

    When you use Okta PUSH MFA, the popup on my mobile device reads "Did you just try to sign in? near Ashburn, Virginia, United States"

    I am not near Ashburn, that's your server location. We use Okta Push at our company and had the same issue. It's a simple fix, tell your engineers to add:

    'X-Forwarded-For': <users ip>,
    

    With the user IP address that is sent to Okta, and it should geolocate properly. This is a small, albeit actual security issue with MongoDB, as I cannot safely differentiate between my own login request and a potential account takeover attack. In other words, because the location is not being provided properly, a user can circumvent my MFA by having just my password, and relying on an errant click since I may not realize the push request came from somewhere else.

    This is an easy fix for an actual security issue at MongoDB and you should probably elevate. I do consider that your engineers are probably aware of the issue, but I'm uncertain why they haven't fixed it :)

    Hi,

    This is really a message for your security / authentication engineers.

    When you use Okta PUSH MFA, the popup on my mobile device reads "Did you just try to sign in? near Ashburn, Virginia, United States"

    I am not near Ashburn, that's your server location. We use Okta Push at our company and had the same issue. It's a simple fix, tell your engineers to add:

    'X-Forwarded-For': <users ip>,
    

    With the user IP address that is sent to Okta, and it should geolocate properly. This is a small, albeit actual security issue with MongoDB, as I cannot safely differentiate… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    completed  ·  AdminFuat (Admin, MongoDB) responded

    Thank you for your kind feedback. This issue has been fixed and Okta Push app should show now show the correct location. Thank you!