Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
426 results found
-
Allow customer encryption key validation time interval
Currently, Atlas has a 15 minute interval where it checks access to remotely stored Customer Managed Encryption keys for the custom encryption at rest feature.
This value is not changeable, and it implies a problem: access to encryption keys can be lost for longer periods than 15 minutes without that implying that the key has been invalidated by the customer.
A perfect example of this was the recent Azure AD global outage that prevented all authentication to the Azure platform for about 3 hours (complete outage description: https://app.azure.com/h/SM79-F88/691d78). While the key used for one of our clusters was not…
7 votes -
Using replica set tags for invoice categorization
Customer would like replica set tags added to the invoice as a column, in order to further categorize costs. In some instances, the customer has multiple products assigned to a single cluster, and putting the product name in the cluster won't suffice.
The current solution is to use the Invoice API, and then call the Cluster API, in order to programmatically build out a CSV containing the cluster tags as an additional column in the CSV.7 votesWe recently released tags on database deployments. You can apply tags to new or existing clusters or serverless instances.
https://www.mongodb.com/docs/atlas/tags/
We are planning to have these tags displayed in billing Invoices and we'd love to hear more from you. Reach out to me if you'd like to provide additional feedback about this feature request.
-
Enable setting the security.redactClientLogData parameter.
We're using Atlas to store PII (HIPAA), and we need to store the log files for an extended period of time, but we don't want any PII / HIPAA data to be stored in the logs.
7 votes -
Expose API for Self-Service Increase of the Clusters per Project Limit
Give Atlas users the ability to increase the number of clusters they can create in a single project above the 25 cluster limit without having to file a support ticket.
6 votes -
Add ability to chose the new primary node when you perform a test election
There's a "test failover" option, which shuts down the primary and forces an election. However, you have no control over which new primary will be elected (just the preferred region) which sometimes does not work as expected.
It would be really useful if you have the possibility to manually chose which node will be elected as the new primary.
6 votes -
Create Atlas UI Triggers Programatically
Currently, a trigger which gets displayed on the Atlas UI (under Data Services > Triggers) cannot be created programmatically, they may only be created by clicking through the Atlas UI.
The triggers created from the Atlas UI automatically creates a new realm app named "TriggersRealmApp" even when a realm app with the same name already exists. There is no way to have any of the triggers created under any other realm app displayed in the Atlas UI. The only way is to create them under the auto generated "TriggersRealmApp" which gets created after the first trigger from the…
6 votes -
Deletion Protection
Customer suggested protection from Cluster deletion similar to AWS RDS
https://www.amazonaws.cn/en/new/2018/amazon-rds-now-provides-database-deletion-protection/
TL;DR - a notification when a user tries to delete a cluster, that "this cluster is protected, if you need to delete please visit the console to enable deletion"
This would be a critical piece of functionality where roles/permissions are not sufficient.
6 votes -
Add the possibility to add a description for IP's in access control list for API keys
In the Atlas UI, allow to add a description in the IP's allowed to use an API key. This may improve security and ease management as it allows to easily maintain this list up to date.
6 votes -
MongoDB Atlas Provider for AWS CDK
We use AWS CDK to deploy our infrastructure. Currently there is only a Terraform provider available to automate the MongoDB Atlas deployment. We would like to have such a provider also for AWS CDK.
In a first step this provider should support:
- mongodbatlascluster create, edit and delete clusters
- mongodbatlasdatabaseUser create and remove usersLater full feature set like in Terraform should be supported.
Currently we use a self written provider. But this has hundreds of lines of code and means a lot of maintenance effort. For our teams this additional effort can be a reason to…
6 votes -
OCSP stapling support for Atlas Clusters
What is the problem that needs to be solved? As a user (MongoDB Driver) you'd like to check revocation status of X.509 certificate via TLS Certificate Status Request extension (also known as OCSP stapling) instead of doing outgoing HTTP connection to OCSP endpoint from a user (MongoDB Driver) side.
Why is it a problem? (the pain) MongoDB Server v. 4.4.X introduces OCSP stapling functionality, however OCSP stapling is not enabled on Atlas Clusters with MongoDB Server v. 4.4.X.
6 votes -
Unique VPC Peer CIDR
Prevent the same VPC Peer CIDR block, is it currently possible to have 2 projects with same CIDR block, which requires us to delete our clusters and peer before creating new clusters
There should be a way to prevent them from having same CIDR block or the ability to change the CIDR block AFTER they are created
6 votes -
Viewing Collection Pages
Would like the option to view collection pages by 10, 20, 50, 100. Along with ability to move to (<first) (last>). Similar to mLab
6 votes -
Allow multiregion sharded clusters to have Primary nodes in multiple regions
For multi-region sharded clusters, the primaries for each shard remain in a single (highest priority) region in Atlas. If these primaries can be spread across multiple regions, that will a) provide consistent average response time for applications that connect from multiple regions as active-active b) Limit the blast radius if the highest priority region is unavailable c) Better distribution of workload from an application side.
This architecture is currently possible with EA deployments but not with Atlas.
5 votes -
Atlas policies
In the MongoDB atlas portal, there should be a way to configure policies across an organization. ie: policies to restrict users from creating clusters from certain cloud providers (ie: azure), restrict users from creating databases of a certain size, etc.
5 votes -
Cancel restore
There should be an option to stop once the restoration is given. Or there should be an option to revert a backup restore. This is required because we can restore an old production back up to Production only. If by mistake we do that we should be able to revert back.
5 votes -
Support Private Endpoint TO customer's VPC/VNet
This would allow a Private Endpoint to connect FROM an Atlas Project TO a customer's VPC/Vnet (using AWS PrivateLink or Azure Private Link), for accessing private services like a private webhook for alerting, LDAP, and/or KMS
5 votes -
Add Cluster name to process list api
Currently the processes API (https://docs.atlas.mongodb.com/reference/api/processes-get-all/) returns only the ReplicaSet name of the process not the cluster name, while the cluster API (https://docs.atlas.mongodb.com/reference/api/clusters-get-all/) returns the replicaset name only in the MongoDB URI.
If you have multiple clusters in the same Atlas project and you list the processes is difficult to make an association between MongoDB processes and the Cluster (Atlas UI name)
Would be nice to have also the cluster name in the processes api
5 votes -
Ability to schedule monthly maintenance windows
Ideally we'd have the ability to schedule maintenance windows that are monthly. Either the option to say maintenance run on the 3rd of the month or every 2nd Tuesday. The current issue I see is that your non-prod clusters and prod clusters can share the same window and get patched at the same time, or you pick different days of the week for patches (e.g. Monday for non-prod, Friday for prod), but we risk having prod patched before non-prod in that situation.
I realize we have the ability to defer maintenances for a week, which is great. However, we're now…
5 votes -
Allow customers to download Atlas BI Connector process logs (similar to MongoDB Server logs)
What is the problem that needs to be solved? Customers are willing to troubleshoot / analyze Atlas BI Connector logs by themselves (they would like to investigate schema sampling timings, SQL/MongoDB query optimizations, connectivity issues, etc.).
Why is it a problem? (the pain) Currently available Download Logs option on Atlas Clusters does not include Atlas BI Connector process logs.
5 votes -
Have the ability to downgrade
Currently Atlas doesn't support the ability to downgrade major version. I know with Ops Manager on-prem you can do that, which is helpful if you find issues during an upgrade. Would it be possible to get the ability to downgrade one major version on the roadmap?
As of today, if we have issues with an upgrade, we have to build a new cluster with the older version, export and import into the new cluster. That's a much more painful process including the fact that you have to change the connection strings of your applications to point to the new cluster…
5 votes
- Don't see your idea?