Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
455 results found
-
Add usability to tags
Atlas has the option to set tags to clusters. But - now what? They are just pieces of text floating around, but are completely useless.
How about enabling to filter clusters in a project or even organization based on those tags? Split costs based on them? Query them with API calls? I have no use of those tags when they are just texts in the main page of Atlas...7 votes -
Mongo Atlas - Pause Cluster protection
Mongo added a feature where termination protection option has been added.
pause cluster protection is needed as well to prevent mistakes7 votes -
Add Atlas users to existing teams even though the Atlas user is still pending invite
Currently when we send invite emails for the organization we have to wait for the users to accept the invite before we are able to configure project level permissions. This often creates confusion and bad user experience; when users first sign in they are anticipating to see their projects but instead they see nothing until configuration is finalized.
Please make it possible to add users to teams which are still pending invite acceptance so the user experience is more seamless and less confusing.
7 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.
7 votes -
Ability to provide IP addresses as a list for Network Access
When adding IP addresses on a cluster/project (Network Access), it would be great to be able to provide a comma-delimited list of IP addresses instead of having to enter them one-by-one.
7 votes -
Support optional fallback to source cluster after cutover in Live Migration
Live Migrate allows for migrations from non-Atlas clusters into Atlas by syncing data from the source to the Atlas destination, and then cutting over the application to direct workload to the destination.
It's possible to test the application on the destination before cutover, but after cutover, there's no way to sync data in reverse in case unforeseen issues arise and it's necessary to fall back to the source (or another) cluster again.
Having a "fallback sync" option could help with this.
7 votes -
Support for delayed replicas
It would be great if Atlas provided support for hidden, priority 0 delayed replicas. For workloads that do not need real time data or situations where data recovery is needed, a delayed replica would be the fastest way to mitigate both of those scenarios.
7 votes -
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 -
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…
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 -
Hosting Atlas on DigitalOcean
In addition to AWS, Azure and GC, give an option to host on DigitalOcean. DigitalOcean has a really cheap and well-made Kubernetes system that requires VPC because container IPs are always changing, and I would want them to connect to Atlas without having to just open Atlas to whitelist every IP.
7 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
7 votes -
All Clusters permission for ORG level roles
Today, for you to be able to use All Clusters you need to have permissions on each project, your user needs to be included in each project.
When we use a federation, we generally don't grant permission for each project to a team of administrators. We grant ORGOWNER, for example. By doing this, we lose access to All Clusters. The idea was to include the permission to use All Clusters for project-level permissions that have permissions to read project resources, for example ORGOWNER or ORGREADONLY.
6 votes -
I would like to compact to oplog myself instead of opening cases to resize it
To compact my oplog and reclaim 300GB of disk space right after I finisihed migrating a database to Atlas using mongomirror, I had to open a support case. With that we were able to reduce our cluster tier thanks to lowering the disk tier (Azure deployment)
It would be nice to do it myself to be faster without opening a case with severity 4 that will take me at least 2 days to accomplish that. Also, I assume that people without a subscription can't do it since you have to open a case which is exclusive only if you have…
6 votes -
Activate bypass saml only for select users
We have recently activated SAML SSO on our Organization and we would like to only have 1 user that is able to bypass SSO as like a "break the glass" user in case our IDP fails. It would be ideal that not every user is able to use the bypass url.
Currently any users can use the bypass sso url
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.
6 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
- Don't see your idea?