Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
138 results found
-
Provide "Last Login Date" for Atlas users via Atlas API
The Atlas API should include "Last Login Date" for the
GET /orgs/{ORG-ID}/usersendpoint.14 votes -
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 voteThe US5 Datadog site is available in Atlas.
-
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 -
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 votesHello,
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…
-
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 votesHello,
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…
-
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 voteHi,
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
-
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 votesThis is now out in version 1.4.2
-
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 -
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 votesHi 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
-
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
mongodbatlascloudbackupsnapshotrestorejobThis 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/restoresWould 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 voteReleased as part of v1.11.0, try today and thank you for all the feedback!
-
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 -
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/exportBucketshttps://docs.atlas.mongodb.com/reference/api/cloud-backup/export/create-one-export-bucket/
2 votesThis feature is now available in version 1.3.0 of the provider.
-
Dark mode
Please release a dark mode MongoDB Atlas interface. Thank you.
749 votes -
write concern terraform
Allow configuring "defaultWriteConcern" using the terraform plugin.
6 votesAvailable as of provider version 1.0.2. Thank you!
-
9 votes
-
Add option to create project without alerts
Currently a project is created with a set of default alerts. We need to customize these but we can only add new alerts via terraform. It would be helpful if there was a boolean flag in the mongodbatlas_project resource to disable default alert creation
17 votesJust added in the latest version 1.1.1: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project#with_default_alerts_settings
-
Automatic backup outside Atlas
For DR strategy, one need to have its backups outside Atlas.
This can be achieved in several ways. Some are:
- Provide APIs to download the current backups and let the customers automate this on their side
- Write backups in the customer provided cloud account (aws s3, azure blob stroage...) My favorite optionI found many ideas related to my needs, but they were too specific. This need is more general: just provide a way to have backups automatically outside of atlas.
5 votesThis feature has been released, you can see how to utilize it here —> https://docs.atlas.mongodb.com/backup/cloud-backup/export/
-
Support multi-cloud
Support multi-cloud as available in the Atlas UI
7 votesThis has been released in the latest Terraform MongoDB Atlas Provider, https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/advanced_cluster Thank you!
-
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…
26 votesWe 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.
-
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…
91 votesHello 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…
- Don't see your idea?