152 results found

1. Enable setting encryption at rest details for project

   Please allow us to set the encryption at rest KMS details for the project when we create the project

   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  ·  Kubernetes Operator  ·  Delete…  ·  Admin →
   completed  ·  AdminDan (Admin, MongoDB) responded

   This is available and supported.

   
   

   https://www.mongodb.com/docs/atlas/atlas-operator/stable/ak8so-encryption-at-rest-customer-keys/

2. Create Organization using API or terraform in Atlas

   I support multiple business units (BU) within our company. Each BU uses multiple applications & teams. In order to offer service in Atlas, through automation, there is no option in Atlas to create/ delete Organization dynamically. It allows managing Projects and below.

   It will be good to add this feature to create/ delete Organization dynamically.

   It will also be good to manage, ie to create different Accounts dynamically (like AWS/GCP).

   This will help to have separate account & organization, for each BU to manage billing and manage the consumption, through automation.

   Thanks
   Rama Arumugam

   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

   3 comments  ·  Billing  ·  Delete…  ·  Admin →
   completed  ·  AdminFuat (Admin, MongoDB) responded

   You can now create Organizations via Atlas Administrator API. Please refer to the API specification for more details.

   
   

   CLI and Terraform support will be available in upcoming months.

3. Restore snapshots on s3 back to atlas cluster

   Currently we store Atlas snapshots on S3 for D.R purposes as well as for compliance reasons.

   There was a scenario where an instance was deleted by mistake, and once an instance is deleted all of the atlas managed backup snapshots were gone. In order to restore the Atlas instance we had to do the following:

   1) create a new atlas instance

   2) restore the snapshot from s3 to a temporary mongodb database and then do a dump and restore in order to migrate the data back into the new atlas instance.

   This is a time-consuming process, so if there is the ability to copy the snapshots directly back to the atlas instance that will save some time.

   In addition, this also can benefit a scenario where we archive/purge data on a periodic basis and if needing to restore the data back for compliance reasons we can restore the snapshot, stored in S3, taken before the purge/archive process to another Atlas instance. (with the understanding that the mongo snapshot versions are the same as what is being offered in atlas).

   Currently we store Atlas snapshots on S3 for D.R purposes as well as for compliance reasons.

   There was a scenario where an instance was deleted by mistake, and once an instance is deleted all of the atlas managed backup snapshots were gone. In order to restore the Atlas instance we had to do the following:

   1) create a new atlas instance

   2) restore the snapshot from s3 to a temporary mongodb database and then do a dump and restore in order to migrate the data back into the new atlas instance.

   This is a time-consuming process, so if there is… more

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

   Hello,

   
   

   I would like to update everyone on some changes we have made over the last couple of quarters that resolves multiple parts of the overall goal here, in addition to the methods Ben outlined in the past

   
   

   First, is Import Archive from S3 in Atlas. This walks you through how to import an archive from S3 back into Atlas.

   
   

   In addition to this we now have other protections around cluster and backup deletion protection to protect against human error but also to ensure you can comply with various requirements automatically 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.

   
   

   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. 

   - Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more.

   - With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes.

   - Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure to read our documentation thoroughly before enabling.

   
   

   In addition to Backup Compliance Policy, organizations can also utilize our multi-region Snapshot Distribution to automatically copy backups (snapshots and oplogs) to additional Atlas regions. If your primary cloud experiences a region outage then Atlas will be able to recover with a copied backup from another region, just like any normal restore.

   
   

   With all of these features, you can automatically  protect your data and meet compliance directly in Atlas.

   Hello,

   
   

   I would like to update everyone on some changes we have made over the last couple of quarters that resolves multiple parts of the overall goal here, in addition to the methods Ben outlined in the past

   
   

   First, is Import Archive from S3 in Atlas. This walks you through how to import an archive from S3 back into Atlas.

   
   

   In addition to this we now have other protections around cluster and backup deletion protection to protect against human error but also to ensure you can comply with various requirements automatically 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… more

4. ReadOnly DATA API

   Current DATA API feature looks promising. However there is no way provide access controls around it. If you have access to API key then you can potentially do both read-write to cluster. We did some PoC recently but couldnt promote to prod because of this problem. If we get a readonly Data API access that would be super helpful.

   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

   0 comments  ·  Data API  ·  Delete…  ·  Admin →
   completed  ·  Sumedha Mehta responded

   Hi all this should be completed now.

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

6. Datadog integration for US5

   Hi I am using US5 datadog, and as I learned that Atlas only supports US1, it would be great if the integration with US5 is also added.

   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  ·  Integrations  ·  Delete…  ·  Admin →
   completed  ·  AdminTonya (Sr. Product Manager, MongoDB) responded

   The US5 Datadog site is available in Atlas.

7. AWS CFN MongoDB::Atlas::<> in all AWS regions

   Please publish the MongoDB::Atlas::<> resources types into all AWS regions (currently only in us-east-1).
   Some of us have restrictions in place that deny the direct use of us-east-1.
   Thanks,

   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  ·  2 comments  ·  CloudFormation Resources  ·  Delete…  ·  Admin →

8. Backup Policy change approvals

   The Backup Policy configuration shows a checkbox allowing the altered backup policy to affect all prior backups. The problem with this is that someone could accidentally (or maliciously) delete all prior backups.

   This feature request would include implementing some sort of multi level approval prior to enacting said recursive backup policy changes (affecting prior backup snapshots).

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

   Hello,

   I am pleased to announce that we have addressed your concern of accidental or malicious deletion of all backups in a cluster. We have released our backup feature called Backup Compliance Policy, that protects your backups from being deleted by any user, ensuring WORM and full immutability (can not be edited/modified or deleted) for backups automatically in Atlas.

   
   

   Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more.

   
   

   With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes.

   
   

   Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure to read our documentation thoroughly before enabling.

   
   

   Hello,

   I am pleased to announce that we have addressed your concern of accidental or malicious deletion of all backups in a cluster. We have released our backup feature called Backup Compliance Policy, that protects your backups from being deleted by any user, ensuring WORM and full immutability (can not be edited/modified or deleted) for backups automatically in Atlas.

   
   

   Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more.

   
   

   With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes.

   
   

   Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure to read our… more

9. Disable Specific API's

   For certain API's, like the ability to Delete a backup, have the ability for an Owner to disable this API call entirely, to prevent bad actors from being able to destroy a system or even a good actor from unintentionally destroying a system. If a customer has a policy that no backups shall be deleted ever, have the ability to disable this API across the board.

   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

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

   Hello,

   
   

   I am pleased to announce that we have released our backup feature called Backup Compliance Policy, that protects your backups from being deleted by any user, ensuring WORM and full immutability (can not be edited/modified or deleted) for backups automatically in Atlas. This applies to any method of deleting backups, regardless of wheter it is through the UI or the API.

   
   

   Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more.

   
   

   With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes.

   
   

   Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure to read our documentation thoroughly before enabling.

   
   

   Hello,

   
   

   I am pleased to announce that we have released our backup feature called Backup Compliance Policy, that protects your backups from being deleted by any user, ensuring WORM and full immutability (can not be edited/modified or deleted) for backups automatically in Atlas. This applies to any method of deleting backups, regardless of wheter it is through the UI or the API.

   
   

   Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more.

   
   

   With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes.

   
   

   Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure… more

10. Granular permissions via roles / hashicorp vault

    We are using the Hashicorp Vault Atlas plugin in order to generate credentials for Atlas.
    We are able to generate roles on the Atlas end and then use those roles to provision vault users.
    However, I don't see a way to restrict those roles to just certain resources/clusters.
    So the user can access all the deployments in a project.
    It should be possible to restrict roles to certain resources only.

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

    Hi,  

    
    

    This has already been added some time ago.   You need to specify the scopes you want to include, here's the code - https://github.com/hashicorp/vault-plugin-database-mongodbatlas/blob/master/mongodbatlas.go#L206. It should be an array like roles, but with the resource name and then if it's a cluster or data lake (see scopes here: https://www.mongodb.com/docs/atlas/reference/api/database-users-create-a-user/).   I hope that helps! 

    
    

    Best, 

    Melissa

    
    

11. Allow Management of Identity Providers through Terraform

    The necessary API endpoints appear to exist, it would be great to expose them in the Terraform provider for Atlas to avoid having a split between Infrastructure-as-Code and having to browse the web interface.

    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

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

    This is now out in version 1.4.2   

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

13. Allow editing default project alerts via terraform

    For instance, the default Query Targeting alert is set at a 1000:1 ratio. I would like to have the default alert set to 5000:1 for a project via terraform.

    6 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  ·  Terraform Provider  ·  Delete…  ·  Admin →

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

15. Backup Snapshot datasource and Restore Job resource and datasource for Shared clusters

    The following resources/datasources work only for dedicated clusters (M10 and above).

    mongodbatlascloudbackupsnapshots
    mongodbatlascloudbackupsnapshotrestorejob

    This is because they call the /backup/snapshots and
    /backup/restoreJobs Atlas API endpoints respectively.

    There are different API endpoint for shared-tier clusters (M2/M5):
    /backup/tenant/snapshots
    /backup/tenant/restores

    Would it be possible to have new equivalent datasources/resources for shared-tier clusters or modify the existing datasources/resources to accommodate shared-tier clusters?

    Thanks in advance.

    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

    2 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  Zuhair responded

    Released as part of v1.11.0, try today and thank you for all the feedback!

16. Webhook From Atlas alerting to Teams

    Hi there,
    Is there a easy way to integrate Microsoft Teams Webhook?

    complicated : https://www.clearpeople.com/blog/sending-mongodb-atlas-webhooks-notifications-to-microsoft-teams

    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

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

17. Create Snapshot Export Bucket using Terraform

    Create Snapshot Export Bucket using Terraform- required to export Snapshots to S3.
    Implement the following API call by the provider:
    POST /groups/{GROUP-ID}/backup/exportBuckets

    https://docs.atlas.mongodb.com/reference/api/cloud-backup/export/create-one-export-bucket/

    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

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

    This feature is now available in version 1.3.0 of the provider.

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

19. write concern terraform

    Allow configuring "defaultWriteConcern" using the terraform plugin.

    6 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

    Available as of provider version 1.0.2. Thank you!

20. Add API endpoint to turn off/on Data Explorer
    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

    completed  ·  1 comment  ·  Data Explorer  ·  Delete…  ·  Admin →