Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
470 results found
-
Multitenancy of the billing section in MongoDB Atlas
Hi MongoDB team,
as the organization owner I don't want that my organizational members (developers, project owners etc.) have access to the billing section. Currently every member (independent on the granted rights) has the rights to see the complete billing section and can see the whole invoice incl. the names of the projects. This isn't acceptable regarding compliance because we are working together with external companies and their colleagues shouldn't have the ability to see all invoices.
Please make the billing section of MongoDB Atlas available to handle multitenancy - so that only the organization owner can see the billing…
8 votes -
Ability to create more than one index at once
We have migrated a huge collection with nearly 100million records into Atlas. It takes 3 hours to add indexes to it using the rollover strategy and we have tens of indexes to create.
It would be great to simply define all indexes once before starting to apply them.
8 votes -
More detail and lead time around maintenance notifications
When we get email notifications of upcoming maintenances, it doesn't specify if the update is "urgent" or "low". When we received our last notice, it was 3 days out. If it's urgent, then we understand the short time frame around the notice. However, if it's a lower priority update, I would hope we could configure how far out we are aware of the maintenance or at a minimum get notified 2 weeks prior so we can communicate to our end users.
Additional information around what the maintenance is for would be appreciated as well. Something along the lines of "Patching…
8 votes -
Atlas - Preferences - My Date Format - allow 24hr
We can specify date format but the time format is limited to 12hr clock. Please allow us to specify 24hr so the activity log and rest of the UI is a little easier to read. Thanks
8 votes -
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 -
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.
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 -
LDAP Authentication: Allow Private Endpoint to the customer
Currently, LDAP Authentication from Atlas to a customer's LDAP service can go via the Internet or via VPC peering. In lieu of VPC peering, I propose using a Private Endpoint FROM Atlas TO a customer VPC that hosts the LDAP service.
NOTE: This would NOT be using the same Private Endpoint connection that Atlas currently supports today, which allows customers to reach their clusters privately (Customer -> Atlas).
This would be an additional Private Endpoint in the other direction (Atlas -> Customer).Advantages of using Private Endpoint vs VPC peering:
* Security: The customer VPC is not exposed to Atlas,…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 -
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 -
Change/Option to change Default Storage Compression to zlib
This is a feature request to change or provide an option to change Default Storage Compression to zlib
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 -
Lock a user account
We have an occasional need to disable/lock an individual database user. Either because of a run away process or inactivity. We do not want to change the password or drop the user as we may need to reenable the user quickly with the same permissions and password as before.
6 votes
- Don't see your idea?