Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
158 results found
-
Ability to create/update triggers using terraform
Ability to create/update triggers using terraform
12 votesSupport for Triggers added in version 1.0.0 of the Terraform MongoDB Atlas Provider.
-
Integrate Azure Private Endpoint
Enable connectivity in Azure using private endpoints
8 votes -
Allow user to specify either more date types, or arbitrary archive criteria
Currently to configure the online archive service, you specify which column you want to use, which must be a Date type. Our collections often use integer fields holding the offset from the epoch, and there are other fields people might reasonably used.
My suggsetion would be to allow for a diverse set of date types, or ideally, allow the user to specify the criteria themselves with a mongo query.
5 votes -
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 weeksHowever, during the creation of the mongo atlas cluster, I can see an error
Error: Error applying plan:1 error occurred:
* module.cluster…28 votesThe 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.
-
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 votesAs 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
-
Add Alerts for Triggers
Add alerts for when Triggers are suspended or exceed a threshold.
14 votesThank you all for your feedback! There are alerts available for Trigger suspension that can be configured in your Project Alerts (App Services > Trigger > cannot be restarted or auto resumed). Additionally, we have added a multitude of alerts for the metrics you see in the metrics dashboard on the App homepage - reference sheet here. These can also be found in the Project Alerts under App Services > Metrics > [select condition/metric].
-
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
-
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…
-
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-messaging28 votesThis is now available! You can find the integration on the integrations page in Cloud. Documentation to follow in coming days.
-
Show all team users on one page
When we do SOC2 reviews, we have to take screenshots of the permissions various users have. Currently, a specific "team" in Atlas only shows 5 users at a time and is paginated. Taking screenshots of 5 users at a time is pretty tedious, so it would be amazing to have a page with the full list.
2 votes -
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 -
Change Azure snapshot backups from LRS to GRS
Sorry but this is a must. GRS is a 2 region datacenter backup, LRS only 1. Fire or disaster will take out everything if LRS is used.
2 votesHello,
We recently released a feature that we call Snapshot Distribution which allows any Atlas user to copy their backups into additional cloud provider regions that are supported in Atlas.
This allows you to store the backups in whatever region you prefer automatically. In the event of a disaster in a cloud provider region, Atlas will intelligently use a backup copy in an additional region for a restore.
You can read more about this in this blog, https://www.mongodb.com/blog/post/introducing-snapshot-distribution-atlas , and our docs, https://www.mongodb.com/docs/atlas/backup/cloud-backup/scheduling/#configure-service-to-automatically-copy-snapshots-to-other-regions .
-
Alert when a snapshot restore succeeds/fails
Simply send an email alert when a restore finishes (or errors).
This is important for us because we run a restore (from prod to qa) every weekend and it takes over 14 hours. If it fails, we need to know so we can quickly kick it off again before Monday. Otherwise the QA team will be dead in the water.
9 votesIn Atlas, you can now create alerts related to backup.
-
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 votesYour 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.
-
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 -
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 -
Atlas Activity feed should be searchable by cluster
The Atlas activity feed is currently searchable by Type of event. It should have an option to search by cluster name to quickly narrow down any particular activities relating to a particular cluster
1 voteThis was completed sometime ago.
-
Allow Pending Users to be Added to a Team
When trying to implement Atlas infrastructure for Organization/Project users, the Teams functionality is useless unless we can add pending users to a Team. Right now, if a new user doesn't login for two weeks, we can't assign them to a Team until two weeks after the implementation was supposed to be configured.
18 votes -
"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 -
Support a broader range of 2FA providers
Introduce compatibility with additional 2FA providers for Atlas customers, such as:
- Authy
- Microsoft Authenticator
- Okta Verify
- Duo1 vote
- Don't see your idea?