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
-
Tag/label project
Give the ability to tag/label a project
8 votes -
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.
-
"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 the regions parameter of a network peering container
In the API documentation you mention a regions parameter usable when creating a network container with a network smaller than /18. In terraform there is no such parameter. I would like to see that supported (for creating networks smaller than /18 on GCP).
See: https://docs.atlas.mongodb.com/reference/api/vpc-create-container/#request-body-parameters
2 votesThis work is completed and in v0.9.0 of the provider.
-
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 votesThis 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.
-
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 -
in the explorer -> 'Global Writes' tab: compound shard key should support unique index property
set the compound index created during the Global Cluster configuration to be set as unique
today there is no option for that and it's a very basic need for those who using global clusters.
1 voteThis is a timely piece of feedback as we have been working behind the scenes to make this possible! I’d like to share some good news: Atlas now allows you to use a unique index as the shard key of a global writes collection. This capability allows you to enforce a unique constraint on the entire shard key combination. See https://docs.atlas.mongodb.com/data-explorer/global-writes/#procedure for more details.
-
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 votesLDAP is now available in versions 0.9.0 of the provider.
-
Ability to delete account
I really need to delete my account as this is not what I am looking for.
5 votesHello,
I just want to update this ticket that self-serve account deletion is supported since August 2021. Please note that once you delete your Atlas account, you cannot use the same email to create a new Atlas account.
-
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 votesThank 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!
-
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.
-
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].
-
Integrate Azure Private Endpoint
Enable connectivity in Azure using private endpoints
8 votes -
1 vote
Version 0.9.0 of the provider now supports arm64.
-
Add Switzerland Regions
Hello, our product heavily relies on mongo atlas and we're very happy with it. However, several of our (corporate) clients would like their application data to be hosted in Switzerland (for compliance/data protection reasons). I would love the ability to setup a Swiss only Atlas cluster for those clients, but the closes options we have in Germany only. Either cloud provider will be fine (ideally Azure). Many of your (future) clients would certainly welcome this too (banks! luxury! healthcare! pharma! transportation! public services!) - thanks for listening :)
1 vote -
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 -
Add 1 second granularity to ATLAS metrics
At present the finest granularity of ATLAS metrics is 1 minute ,as the metrics are averaged by 1 minute , this would not provide info on spikes lasting less than few seconds
reducing the granularity to 1 second would give more insight21 votes10-second level granularity for Atlas projects is available with M40+ clusters. More information on this is available here: https://www.mongodb.com/docs/atlas/monitor-cluster-metrics/#std-label-premium-monitoring
-
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…
72 votesWe 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/
-
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 votesFolks 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 abilityThanks for your patience: this was a long-time coming!
Cheers
-Andrew -
Third party integration resource with terraform
Add a terraform resource for third party integrations (such as PagerDuty) to allow it to be set up.
22 votesSupport for 3rd party integrations is now included in version 0.7.0 of the Terraform MongoDB Atlas Provider, available today!
Thank you for the feedback.
- Don't see your idea?