Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1369 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 -
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,…8 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…
8 votes -
As a Collections tab, aka Data Explorer, user I want to view, search for, create and update UUID and GUID field values
The BSON spec includes support for UUID values, also known as GUID values.
The format of UUID values are defined in rfc4122.txt. For example,
f81d4fae-7dec-11d0-a765-00a0c91e6bf6
Users would like to work with UUID/GUID values in Data Explorer as a fully supported data type, including search support in the RFC layout, ability to create new document fields of type UUID, support for UUID type _id fields and the ability to edit UUID values in existing documents.
The mongo shell documentation provides this example:
UUID("3b241101-e2bb-4255-8caf-4136c566a962")
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 -
Allow Billing Alerts per Project
Currently, we can configure Atlas to send an alert when the current bill for any project is above a specific amount. It would be great to be able to set alerts for specific projects. This way we could more easily manage budget fors projects and alert project owners.
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 -
Tags on databases and use these tags in Billing dashboards
I want to be able to tag databases inside clusters and be able to build my custom Billing dashboards using these tags.
I have multiple databases within a cluster and each database serves a different feature or microservice. I'd like to know how much I spend by a tag for compute, storage and data transfer, etc.
I want to be able to apply the same tag across multiple clusters on multiple databases, so Billing can be calculated on multiple databases across multiple clusters.
This feature would greatly improve Mongo's FinOps capabilities.
7 votes -
general cpu class for M400 and M600
Currently when selecting M400 or M600 only "Low CPU" class is available. Our only option to increase CPU is going back to M300 with "General" class to get 96cpu. We would benefit a lot from "General" option of 128cpu and 160cpu.
7 votes -
Improve Admin API for API keys rotation
Given we have security mandates where we need to rotate API keys for an organization, every 365 days. It would be ideal if when calling
https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Programmatic-API-Keys/operation/getApiKeygetApiKey from admin api that it should return the created date. This way programmatically we can rotate keys and maintain security posture. As well if there was a way to just refresh the api secret and not generate a new one that would be a plus
7 votes -
Support Online Archive in Azure Switzerland North region
Please make Online Archive available in Azure's Switzerland North region
We are using MongoDB Atlas in Azure notably to store personal health data of patients. We are based in Switzerland (which is not part of the EU), and the regulation requires that health data remains in Switzerland. We would like to use the Online Archive on Azure feature for our Atlas data but require that it is available in the Switzerland North region.
7 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 -
Ability to "Mass Kill" slow running queries
Currently, Atlas has a "Kill Op" option which is useful to kill single long-running queries.
When upgrading to MongoDB 7.0, we were faced with a situation where the Slot-Based Query Engine (SBE) was causing 1000s of queries to execute slowly, we wanted to kill them all, but it was more than a human could do by clicking "Kill Op" 1-by-1. Hence a "Mass Kill" feature which kills queries longer than X seconds (X is configurable) would have helped us greatly in an outage scenario. We ultimately rebooted our cluster to kill queries, then manually implemented a script which did this…
7 votes -
Alerts for Atlas Limits
It would really help to get alerts on Atlas Limits (https://www.mongodb.com/docs/atlas/reference/atlas-limits/). Defining certain thresholds that would trigger an Alert as hitting these limits often involves work to re-structure something or creating a workaround. E.g. it is not possible to have more than 50 Endpoints per Project. But creating a new project is not a straightforward exercise. If the alert had occurred earlier there would have been more time to account for this.
7 votes -
activity feed filters
Currently it is not possible to filter out from activity feed by certain pattern e.g. we want to filter out all db users which start with smth-* and be able to see if there were db users created which follow a certain naming pattern. So we need to be able to filter activity feed by the username or any other detail in the activity feed text. Thank you so much!
7 votes -
Improve Mongo activity feed for project page
Mongo Atlas activity feed page does not update automatically nor does it have a refresh button. Each time the user wants to refresh the page they have to refresh the URL which removes all the filters(unless you copy the link). It would be very helpful if there was a refresh button which would not remove the filters as this means that the page does not have to be refreshed from the URL.
Additionally an auto-refresh(timed) option would enhance this feature more so that the user does not have to do anything on the page to see the latest updates, eg…
7 votes -
Replicaset elected new primary alert needs to show user given cluster name and the region in which the primary node is running
Replicaset elected new primary alert needs to show user given cluster name and the region in which the primary node is running. For a multi-region cluster, cross-region failovers are a major application impacting event, so the Alert needs to include details around the region in which the primary is running. Also Alerts should use the same node names that are visible in the Atlas console and not use the internal node names in the Alert. This very critical for support teams ability to identify impacted clsuters and applications.
7 votes -
Support Azure Blob Storage in addition to AWS S3 for Online Archive
Currently, there is only one option to store the archive data and that is in AWS S3 buckets. We have contractual obligations with clients to store data in Azure. It would be great if MongoDB gave an Azure alternative to AWS S3 like Azure Blob Storage.
7 votes -
Allow customers to specify the number of service attachments for PSC
To connect applications to MongoDB Atlas clusters/project via Google Private Service Connect, the documentation says we need to reserve 50 IP addresses in our subnet:
https://www.mongodb.com/docs/atlas/security-private-endpoint/
Each private endpoint in Google Cloud reserves an IP address within your Google Cloud VPC and forwards traffic from the endpoints' IP addresses to the
service attachments
. You must create an equal number of private endpoints to the number of service attachments. The number of service attachments defaults to 50.We would like the ability to not have to reserve 50 IP addresses per project as we have limited internal subnets. We would…
7 votes -
Last Database User Access
My team has found ourselves in the position of needing to iterate through the Database Access History Logs in order to discover whether or not a database user is still being used for the past t time periods.
We need to have this functionality in order to guarantee a seamless credential rotation.
With the current API this operation will require iterating over each cluster's access logs for the past t time periods. If I have "n" clusters and "t" time periods this is an O(n * t) runtime. I'm not really great at O() notation, but if t is greater…
7 votes
- Don't see your idea?