Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
137 results found
-
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 votesWe released Performance Advisor alerts on Week of Aug 7. It is available as a default alert.
-
immutable backups
currently Atlas - MongoDB backup are stated to be immutable, however, that is not true because there is no object lock on the s3 bucket.
We would like to request adding the option to have an object lock on the s3 bucket that our snapshots are located on which will make sure that the snapshots can only be deleted by retention and not modified or deleted by anyone else. This is to line up with WORM compliance while dealing with financial data.
https://www.telemessage.com/what-is-worm-compliance-and-when-is-it-needed/
https://aws.amazon.com/blogs/storage/protecting-data-with-amazon-s3-object-lock/
8 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.
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.
-
Terraform Serverless VPC Endpoint configuration
Create the equivalent of mongodbatlasprivatelinkendpoint but for serverless.
8 votes -
Add Prometheus as a Supported Third-Party Integration Settings type
Great work releasing the new Prometheus Integration functionality!
Ideally, we'd like to use Terraform to codify our interface with the Prometheus Integration, similar to how we leverage the existing Third-Party Integration Settings types.
8 votesThis is now out in version 1.4.2 of the provider.
-
Please add datadog US3 site also for the integration with MongoDB atlas
Please add datadog US3 site also for the integration with MongoDB atlas
8 votesThe US3 Datadog site is available.
-
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 Arumugam8 votesYou 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.
-
Atlas API Enhancements
Since we want to automate the user (de)provisioning for organizations and projects, we would like to see the following API enhancements:
Please enhance the Mongo Atlas API for the following functionalities:
- invite (existing mongo) user to organization (currently not possible)
- remove user from organization
- get invitation status from user
- cancel invitation for userThank you
8 votesThe work for invite management has been completed and added as endpoints to organizations and projects: https://docs.atlas.mongodb.com/reference/api/projects/ and https://docs.atlas.mongodb.com/reference/api/organizations/
-
Tag/label project
Give the ability to tag/label a project
8 votes -
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 -
Integrate Azure Private Endpoint
Enable connectivity in Azure using private endpoints
8 votes -
atlas portal ip whitelist
We were given this idea from a security audit.
From a security-in-depth perspective we would like to be able to restrict logins on the atlas portal to only whitelisted IP's, this would be analog as to how API whitelisting works at the organization level.
This is to prevent login's other than from our permitted sites.8 votes -
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 -
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 Realm to stream application logs to Splunk (or other third party services)
It would be ideal if there was some native way to send Realm application logs to Splunk (and other third-party log aggregation services), instead of having to build an application in a separate environment to poll this API endpoint (https://docs.mongodb.com/realm/admin/api/v3/#logging-apis) and push logs to Splunk from there.
7 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…
-
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 -
write concern terraform
Allow configuring "defaultWriteConcern" using the terraform plugin.
6 votesAvailable as of provider version 1.0.2. Thank you!
-
Recovery after cluster delete
Cloud Backups should be recoverable even after a cluster delete otherwise they can't really be considered backups. One way to do this would be to allow for automated backup downloads to customer specified cloud provider storage.
6 votesHello,
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.
As I mentioned…
-
Add a resource to configure the backup policy for Cloud Provider Snapshots
Please add support to change the backup policy for Cloud Provider Snapshots.
This is the API I am referring to:
https://docs.atlas.mongodb.com/reference/api/cloud-provider-snapshot-schedule-modify-one/Thanks.
6 votesThis is now out in version 0.5.1 of the provider. Once CPS in enabled the Atlas default schedule is imported and can be modified via terraform configuration (however if you chose to use the default no modification is needed). https://www.terraform.io/docs/providers/mongodbatlas/r/cloud_provider_snapshot_backup_policy.html
-
Define Default Backup Policy
The ability to save a custom backup policy as the default, so all new clusters don't have to be customized to meet the backup policy requirements.
6 votesHello,
I am pleased to announce that we have released our backup feature called Backup Compliance Policy, that enables the ability to define a default backup 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.
- Don't see your idea?