Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
-
Restrict specific users or client IPs to only Analytics node(s)
There are use-cases where certain users or client IPs need to be given access restricted to only the Analytics node(s) . While it is possible to grant such users read-only permissions at the database/collection level, and have them use the ANALYTICS replica set tag in their connection string URI, it might still be possible for those users to connect to a Primary or a Secondary node (when not using the Analytics replica set tag) and run their query there.
Therefore, a feature that will either restrict specific users access to only the Analytics node(s) or a functionality that will restrict…
6 votes -
Log user Login to Activity Feed for Auditing
When a user logins into the Atlas Portal this is logged to the Activity Feed.
This feature would allow to better user auditing and identify potential security breaches.
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 -
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.
6 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.
6 votes -
More granular permissions *for API keys*
Allow API keys to have much more granular permissions (i.e: only the functions one may need to do a certain task).
Also, add a security category in the form to report possible improvements for Atlas.
And a UI/UX one.5 votes -
create API keys that support linked orgs
It is possible to link multiple orgs to each other. It should therefore be possible to use a single API key to access all linked orgs.
5 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…
5 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.
5 votes -
Tag/label poject
Give the ability to tag/label a project
5 votes -
Ability to delete account
I really need to delete my account as this is not what I am looking for.
5 votes -
Support for Azure VNet Gateway Transit
Azure VNet Peering is currently very limited as access is only possible from the VNet that is peered.
Could you please support access from onprem via private network (Express Route or S2S VPN) and Gateway Transit.
Maybe another way to achieve the same could be via "Private Endpoint".5 votes -
Live Migrate through VPC peering connections
Many teams put their databases in subnets without internet access or with just a NAT gateway. It would be great if the Live Migrate could be use through already configured VPC peering connections.
5 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.5 votes -
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.
5 votes -
Allow multiple Billing emails
Allow multiple billing e-mails instead of just one. There are multiple people in our org who want a copy of the invoices, but I don't want them sent to the entire org (which is what happens if there's no billing e-mail)
5 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}/usersendpoint.4 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
4 votes -
Compact collection from UI
Compacting of a collection directly from the MongoDB Atlas website UI.
No need to run CLI commands and changing primary database.
Making regular maintenance easier.
4 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,…4 votes
- Don't see your idea?