Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
23 results found
-
Shared Clusters upgrade to MongoDB 6.0+
Currently MongoDB 6.0.1 is only available in dedicated clusters (M10+) and in serverless clusters.
We need to use MongoDB 6.0.1 or higher in the shared cluster (M0/M2/M5).
I understand that this should be in the roadmap anyway, but getting it sooner than later would be great.
2 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 -
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 -
Dark mode
Please release a dark mode MongoDB Atlas interface. Thank you.
748 votes -
AWS EBS gp3 Volumes
Please add support for the newly announced and already generally available AWS EBS feature. [1]
The top capability is: "The new gp3 volumes deliver a baseline performance of 3,000 IOPS and 125 MB/s at any volume size. Customers looking for higher performance can scale up to 16,000 IOPS and 1,000 MB/s for an additional fee." [2]
That basically means decoupling storage performance from storage size.
It would eliminate all our IOPS pain as 3000k is more than enough for our usecase. Currently, we are slightly overprovisioning storage size in order to guarantee minimal IOPS performance.[1] https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ebs-general-purpose-volumes-gp3/
[2] https://aws.amazon.com/ebs/general-purpose/17 votes -
Security Key (FIDO2) MFA option
Please enable security key (e.g. https://www.yubico.com/gb/product/yubikey-5c-nfc/) option for MFA. Ideally using FIDO2 protocol
9 votesMongoDB added webAuthn support as an MFA method. Please use "Security Key/Biometric" MFA. option to use it with your FIDO2 keys.
https://www.mongodb.com/docs/atlas/security-multi-factor-authentication/
-
Improve OKTA Location Detection
Hi,
This is really a message for your security / authentication engineers.
When you use Okta PUSH MFA, the popup on my mobile device reads "Did you just try to sign in? near Ashburn, Virginia, United States"
I am not near Ashburn, that's your server location. We use Okta Push at our company and had the same issue. It's a simple fix, tell your engineers to add:
'X-Forwarded-For': <users ip>,
With the user IP address that is sent to Okta, and it should geolocate properly. This is a small, albeit actual security issue with MongoDB, as I cannot safely differentiate…
1 voteThank you for your kind feedback. This issue has been fixed and Okta Push app should show now show the correct location. Thank you!
-
Support for tagging clusters in Atlas
Please allow tagging at a cluster level. This will help in storing related metadata if required.
4 votes -
Cluster Termination Protection
It is possible to quickly delete an entire cluster, for example through terraform, if you're not careful.
It would be great to have a "Termination Protection" feature that can only be disabled in the Admin UI and not via the public APIs.
In terraform I could then enable it like so
resource "mongodbatlas_cluster" "my_cluster" { enable_delete_protection = true }
When I would run
terraform destroy
the cluster should not be destroyed and instead the API returns an error saying that the Cluster has Termination Protection enabled. If I want to disable it, I can login to the Admin UI, select…66 votesYou can now set "Termination Protection" for your Atlas cluster. For more information, see https://www.mongodb.com/docs/atlas/cluster-additional-settings/#termination-protection
-
"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 -
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 -
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.
-
Integrate Azure Private Endpoint
Enable connectivity in Azure using private endpoints
8 votes -
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 -
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 -
Change M10+ cloud providers
I would like to be able to change the cloud provider and region of a M10+ cluster.
It would be nice also to have a per-cluster connection string that does not depend on the cloud provider. So we can change the provider and region without changing the application settings.3 votesWe have recently released multi-cloud clusters on Atlas: https://www.mongodb.com/blog/post/introducing-multicloud-clusters-on-mongodb-atlas
This unlocks the ability for you to seamlessly migrate workloads across cloud providers!
Give it a try and let us know what you think!
-
Make it possible to add tags in the Datadog integration so I can tell my staging and production environments apart more easily
Datadog recommends having only one account and feed data from all environments into it, and then it’s important to tell them apart by using tags.
Please add the ability to set tags in the Datadog integration configuration, e.g. env:production
24 votes -
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.
-
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 -
Maintenance notification to Slack
Would like to get notified for maintenance through slack channel as well as in mail or GUI banner
3 votes
- Don't see your idea?