149 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. Atlas backup to second region

   We would like the option to have our Atlas backups automatically copied to a 2nd region to support our DR initiative. I realize we could create a live database node in a 2nd region, but that is more costly and complex. Having the backup sync to another region that we can restore off of in case the primary region fails would be simpler and more cost effective.

   Is this something that is on your roadmap, and if so, when will it be released?

   Thanks!

   169 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

   32 comments  ·  Backup  ·  Delete…  ·  Admin →
   completed  ·  AdminEvin Roesle (Senior Product Manager, Cloud, MongoDB) responded

   Hi Everyone!
   We are excited to officially announce the general availability of Snapshot Distribution (multi-region backups)!
   You can find it available in your clusters today. 

   
   

   It is available through the UI (at the bottom of the cluster backup policy tab called “Additional Backup Copies”) and through the API. 

   
   

   Check out our resources to learn more - Docs | Blog post.

   
   

   Sincerely,

   The MongoDB Team

3. option to create a final snapshot before deleting a cluster

   Today when an Atlas cluster is deleted, all backups/snapshots of this cluster are deleted along with it.

   This is especially an issue when working with automation tools like terraform, where a cluster can be deleted by accident easily.

   In AWS Aurora Postgres, for example, there is an option to create a "final snapshot" before deleting the cluster.

   If this option is enabled for a cluster, whenever a user triggers the deletion of the cluster (either manually, via API, or any other method), a final snapshot will be created, before the cluster is deleted.

   This final snapshot is then available independently of the deleted cluster, so in case of accidental deletion, we can create a new cluster based on this snapshot.

   This would be a huge security and safety improvement.

   Today when an Atlas cluster is deleted, all backups/snapshots of this cluster are deleted along with it.

   This is especially an issue when working with automation tools like terraform, where a cluster can be deleted by accident easily.

   In AWS Aurora Postgres, for example, there is an option to create a "final snapshot" before deleting the cluster.

   If this option is enabled for a cluster, whenever a user triggers the deletion of the cluster (either manually, via API, or any other method), a final snapshot will be created, before the cluster is deleted.

   This final snapshot is then available independently… more

   91 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  ·  Backup  ·  Delete…  ·  Admin →
   completed  ·  AdminEvin Roesle (Senior Product Manager, Cloud, MongoDB) responded

   Hello All,

   
   

   I am pleased to announce that in Atlas you now have an option to retain all backups when terminating an M10+ cluster.

   
   

   When you terminated a cluster through the Atlas Ui, on the termination confirmation pop up, you will now see an additional toggle labeled "Keep existing snapshots after termination". If you select this option when terminating your cluster, all of your backups for that cluster will be retained. 

   
   

   You can also choose to retain you backups for a cluster when deleting a cluster through the Atlas Administration API. When deleting a cluster through the API, you can include the retainBackups parameter and this will retain all of your backups after termination as well.

   
   

   You can view or use the backups from a terminated (or other active) M10+ cluster by selecting the "Backup" tab in the left side navigation of the Atlas UI.

   
   

   At any time before terminating a cluster, you can choose to take an On-Demand Snapshot, if you would like a final snapshot.

   
   

   To protect from accidentally deleting a cluster in general, you can utilize the Termination Protection setting in Atlas, which when enabled prevents users from deleting any cluster.

   
   

   In addition to these options, if you would like to protect your backups, in all scenarios, from ever being deleted before the designated retention period has ended, please learn more about our new backup feature called Backup Compliance Policy. This ensures your backups are never deleted early.

   Hello All,

   
   

   I am pleased to announce that in Atlas you now have an option to retain all backups when terminating an M10+ cluster.

   
   

   When you terminated a cluster through the Atlas Ui, on the termination confirmation pop up, you will now see an additional toggle labeled "Keep existing snapshots after termination". If you select this option when terminating your cluster, all of your backups for that cluster will be retained. 

   
   

   You can also choose to retain you backups for a cluster when deleting a cluster through the Atlas Administration API. When deleting a cluster through the API, you can include the retainBackups parameter and this will retain all of your backups after termination as well.

   
   

   You can view or use the backups from a terminated (or other active) M10+ cluster by selecting the "Backup" tab in the left side navigation of the Atlas UI.

   
   

   At any… more

4. Support GCP IAM for Cluster Authentication

   Achieve feature parity with AWS IAM cluster authentication support.

   85 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

   14 comments  ·  IAM  ·  Delete…  ·  Admin →
   completed  ·  AdminFuat (Admin, MongoDB) responded

   Your applications can now access Atlas Clusters with Google Service Accounts using MongoDB Workload Identity Federation (https://www.mongodb.com/docs/atlas/workload-oidc/). The feature is supported by MongoDB 7.0.11 dedicated clusters (M10 and above).

   
   

   For your workforce access, we recommend to use Workforce Identity Federation (https://www.mongodb.com/docs/atlas/workforce-oidc/) with your corporate identity provider.

   
   

   Thank you for your feedback.

5. Export metrics to Prometheus

   Currently there is only a community supported Prometheus integration (exporter) available which polls db.serverStatus() and doesn't include as much metrics as the Atlas UI/API provides. A similar integration as with New Relic and Datadog would help many customers that are using Prometheus and Grafana for monitoring.

   83 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  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →

6. I'd like to have a scheduled mongodump backup option

   I'm coming from mLab and I'm used to having an option in my backup strategy that includes a mongodump backup as well as what Atlas calls a CPS (cloud provider snapshot). The latter is actually a snapshot of the database directory at the filesystem level, which is great for instant restores within Atlas (same or different cluster). However, the mongodump backup (from mLab as an example) allows me to backup on a regular schedule and download those backups for restores locally and elsewhere outside of Atlas.

   Yes, I can run mongodump operations myself from a system outside of Atlas, but having those mongodump archives available within a rolling window is really great to quickly grab a backup and examine offline or in another environment entirely, with no additional management or systems from me to do so.

   I'm coming from mLab and I'm used to having an option in my backup strategy that includes a mongodump backup as well as what Atlas calls a CPS (cloud provider snapshot). The latter is actually a snapshot of the database directory at the filesystem level, which is great for instant restores within Atlas (same or different cluster). However, the mongodump backup (from mLab as an example) allows me to backup on a regular schedule and download those backups for restores locally and elsewhere outside of Atlas.

   Yes, I can run mongodump operations myself from a system outside of Atlas, but… more

   72 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  ·  Backup  ·  Delete…  ·  Admin →
   completed  ·  AdminBenjamin Cefalo (Director, Product Management, MongoDB) responded

   We have released the ability to export a snapshot to your own S3 bucket. More details here —> https://docs.atlas.mongodb.com/backup/cloud-backup/export/

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

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

9. Expose auto cluster scaling options via Terraform

   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.

   37 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

   11 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
   completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

   Thank you to everyone who provided input here and directly. We are about to release the provider, v0.6.0, which exposes the autoscale attributes for clusters and includes a recommendation to use a lifecycle block to prevent Terraform and Atlas from conflicting (this will be included in the clusters documentation that will come out w/ the release). Please continue to provide suggestions here or reach out directly to melissa.plunkett@mongodb.com. Thank you!

10. LDAP configuration using Terraform

    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.

    36 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  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    LDAP is now available in versions 0.9.0 of the provider.

11. Support tags on Mongo projects

    I support multiple orgs and projects falling under my enterprise. I'd like the ability to tag projects using a key value pair - similar to GCP, Azure, AWS. Tags will help us organise and understand what's running in our projects.

    Basic functionality that operates on tags will be helpful like filtering projects and enhanced billing that can group costs based on a tag would be beneficial.

    Right now, we need to add cost metadata to the project name, which is the only place where we can do so.

    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

    3 comments  ·  Resource Tagging  ·  Delete…  ·  Admin →
    completed  ·  AdminTonya Edmonds (Sr. Product Manager, MongoDB) responded

    I'm happy to share that this capability is now available in Atlas. You can use the Admin API or Atlas UI to add tags to new or existing projects. This functionality will be extended to Terraform and the Atlas CLI in the near future.

    
    

    http://www.mongodb.com/blog/post/enhanced-atlas-functionality-introducing-resource-tagging-for-projects 

12. "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 →

13. Support native Azure authentication for the DB, e.g. service principal

    Customers often want centralized permissioning for the database and LDAP is not generally supported well in the cloud. If a customer is using Azure, they want us to support Azure AD for database authentication. I believe that means using service principals

    32 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

    6 comments  ·  IAM  ·  Delete…  ·  Admin →
    completed  ·  AdminFuat (Admin, MongoDB) responded

    Your applications can now access Atlas Clusters with Azure Service Principals including Azure Managed Identities using MongoDB Workload Identity Federation (https://www.mongodb.com/docs/atlas/workload-oidc/). The feature is supported by MongoDB 7.0.11 dedicated clusters (M10 and above).

    
    

    For your workforce access, we recommend to use Workforce Identity Federation (https://www.mongodb.com/docs/atlas/workforce-oidc/) with your corporate identity provider such as Azure Entra ID.

    
    

    Thank you for your feedback.

14. Allow to set teams to users by Federated Authentication

    When an Atlas User logs in by a Federated Authentication (like Okta) there is only a "Default User Role" to control its permission, so all users get the same role. And after that, we must manually add to teams, or change their roles. It would be better to allow the IdP to set (and update) the groups/teams for each user automatically.

    32 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  ·  IAM  ·  Delete…  ·  Admin →
    completed  ·  AdminBenjamin Cefalo (Director, Product Management, MongoDB) responded

    This has been released —> https://docs.atlas.mongodb.com/security/manage-role-mapping

    You can now map IDP groups to Atlas Roles between Orgs and Projects. We do not support mapping to teams, that is not planned.

15. Terraform integration to manage project's API keys

    Hello team,

    we're still missing the capability to create project's API keys via terraform and have to deal with some python scripts to automatically provision new keys in dynamic way(when new projects come up).

    I know this question has been already asked and your idea is to use Vault, but probably it's not good idea to install this heavy tool for the single application...and we can't use Vault in dynamic way because it doesn't contain 'MongodbAtlas Secret Engine' available via terraform provider.

    Please consider to add possibility of creation API keys via terraform and let us decide whether it's security risk to keep it in the state file

    Hello team,

    we're still missing the capability to create project's API keys via terraform and have to deal with some python scripts to automatically provision new keys in dynamic way(when new projects come up).

    I know this question has been already asked and your idea is to use Vault, but probably it's not good idea to install this heavy tool for the single application...and we can't use Vault in dynamic way because it doesn't contain 'MongodbAtlas Secret Engine' available via terraform provider.

    Please consider to add possibility of creation API keys via terraform and let us decide whether it's security… more

    30 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  ·  9 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →

16. Possibility to change 'frequency_type' of snapshot backup policy item via Terraform

    Hi,

    I’m facing an issue about Snapshot Backup Policy creation/modification via Terraform ( FYI, I open a case to the support of MongoDB  https://support.mongodb.com/case/00668262). Let me explain :

    When I want to create a MongoAtlas Cluster via terraform, I want to apply a custom Snahsphot Backup Policy with ONLY 2 items during the creation of the cluster :
    N° Item Frequency type Frequency Retention
    0 Daily 1 7 Days
    1 Weekly 1 (Saturday) 4 weeks

    However, during the creation of the mongo atlas cluster, I can see an error
    Error: Error applying plan:

    1 error occurred:
    * module.clustercontrib.module.dpjmongoatlas.module.tfmodule-gcp-mongo-atlas-cluster.mongodbatlascloudprovidersnapshotbackuppolicy.snapshotbackup: 1 error occurred:
    * mongodbatlascloudprovidersnapshotbackuppolicy.snapshot_backup: error updating a Cloud Provider Snapshot Backup Policy: PATCH https://cloud.mongodb.com/api/atlas/v1.0/groups/XXXXXXXXXXXXXXXXX/clusters/contrib/backup/schedule: 400 (request "Bad Request") The frequency type of a policy item must not be changed.

    Indeed, during the creation of the MongoAtlas cluster, MongoAtlas apply the default Snapshot Backup Policy first (with 4 items hourly, daily, weekly, monthly) and after try to apply the custom snapshot backup policy I want (described in the terraform code). But, as we can see above, it seems impossible to change the frequency_type of an existing policy’s item…

    To resume clearly with this spreadsheet :
    N° Item Frequencytype of default policy Frequencytype of custom policy I want COMMENT
    0 Hourly Daily KO (because The frequency type of a policy item must not be changed)

    1 Daily Weekly KO (because The frequency type of a policy item must not be changed)

    2 Weekly NOTHING
    3 Monthly NOTHING

    Can we purpose a evolution to have the possibilty to modify the frequency_type of an existing policy item via Terraform/API?

    Regards,

    Hi,

    I’m facing an issue about Snapshot Backup Policy creation/modification via Terraform ( FYI, I open a case to the support of MongoDB  https://support.mongodb.com/case/00668262). Let me explain :

    When I want to create a MongoAtlas Cluster via terraform, I want to apply a custom Snahsphot Backup Policy with ONLY 2 items during the creation of the cluster :
    N° Item Frequency type Frequency Retention
    0 Daily 1 7 Days
    1 Weekly 1 (Saturday) 4 weeks

    However, during the creation of the mongo atlas cluster, I can see an error
    Error: Error applying plan:

    1 error occurred:
    * module.cluster… more

    28 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

    2 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    The Cloud Backup policy has been completely reworked as of provider version 1.0.0, with a few more fixes in 1.0.1 (coming shortly). This should address the pain points that have been raised here and elsewhere.

17. Integration with Microsoft Teams

    Add third-party service integration for Microsoft Teams, as we do for Slack.
    Most likely the following can be leveraged to achieve the integration: https://docs.microsoft.com/en-us/graph/teams-proactive-messaging

    28 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  ·  Integrations  ·  Delete…  ·  Admin →
    completed  ·  Elle responded

    This is now available! You can find the integration on the integrations page in Cloud. Documentation to follow in coming days. 

18. Allow modifying federation role mappings via API

    We would like to use the new role mapping feature for federated authentication to assign Atlas roles based on LDAP groups assigned to our users.

    However, we frequently create new projects programmatically and would need to manage the permissions to these new projects using role mapping. However, there is no public API available to manage role mappings programmatically. In addition, enabling role mapping disables the ability to manage roles for federated users with the API. So, at present, role mappings and permissions can only be managed manually through the UI.

    We would like to request the ability to modify role mappings (and possibly other federation features) through the Atlas API.

    We would like to use the new role mapping feature for federated authentication to assign Atlas roles based on LDAP groups assigned to our users.

    However, we frequently create new projects programmatically and would need to manage the permissions to these new projects using role mapping. However, there is no public API available to manage role mappings programmatically. In addition, enabling role mapping disables the ability to manage roles for federated users with the API. So, at present, role mappings and permissions can only be managed manually through the UI.

    We would like to request the ability to modify role… more

    26 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  ·  IAM  ·  Delete…  ·  Admin →
    completed  ·  AdminFuat (Admin, MongoDB) responded

    We are happy to announce that Federated Authentication Configuration can be now managed through Atlas Administration API. Please refer to API documentation for more information: https://docs.atlas.mongodb.com/reference/api/federation-configuration/

    
    

    Please let us know if you have any feedbacks.

19. Allow Atlas clusters to be paused using terraform

    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

    26 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

    0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    This is out as of today in version 1.2.0 of the provider.  See https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cluster#paused for details.  Thank you!

    
    

20. Annual Snapshot Retention Policy Option

    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.

    25 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

    7 comments  ·  Backup  ·  Delete…  ·  Admin →
    completed  ·  AdminEvin Roesle (Senior Product Manager, Cloud, MongoDB) responded

    As of March 2024, Atlas Backups now have a yearly snapshot frequency option in the UI and API. This is also available in our Terraform MongoDB Atlas Provider v1.16.0