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
-
API Improvements - OpenAPI and more auth options
The API should be documented with OpenAPI to allow better tooling.
Ideally using the above OpenAPI spec you could auto generate a SDK or API client for popular languages.
Lastly, the API should accept authentication options other than digest. There is very poor support for digest authentication by popular HTTP clients. I don't like trying to implement security protocols myself, as there is often some quirk I have not fully understood that ends up leaving me less secure than I hoped.
In many questions online when searching for information about digest authentication, the person asking the question is asking about…
12 votes -
pause
An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.
12 votes -
billing
The billing invoice is split by project. If we have multiple team in the same project, it a puzzle. We need to bill by cluster in this case.
12 votes -
Provide Atlas support for "Classic" VNet Peering topology
Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT
12 votes -
Credits API
I need an API that will allow access to the items under credits in the billing page.
This will allow me to pull this information daily into our master usage database to support our dashboards12 votes -
More functionalities in Collection (Data Explorer) Tab in Atlas UI
Here are some suggested functionalities
- Import and export of bulk documents.
- Quickly filter and sort the required documents. (This is achievable in Compass but not in Atlas UI)12 votes -
Allow individual Atlas database user to connect from different specific IP address only
The feature request is to allow individual Atlas database user to be able to connect from different specific IP address, instead of compulsorily having the whitelisted IP address apply to all database users.
I.e.
UserA can only connect from ipA
UserB can only connect from ipB12 votes -
Support Google IdP for OIDC Workforce Federation
The Atlas supports federated login with external Identity Providers via OIDC (https://www.mongodb.com/docs/atlas/workforce-oidc/) for authenticating human users in tools like mongosh or Mongo Compass.
Unfortunately the OIDC login doesn't work with the GCP IdP: OAuth2 clients in Google IdP always have a client secret (even clients considered as "public"). There is no way to specify the client secret in Atlas UI in the Workload Federation configuration and this leads to "invalidrequest (clientsecret is missing.)" error returned from the IdP as it always expects a client secret to be present.
The support of an optional client secret in…
11 votes -
Support for push-based logging integration with Google Cloud Storage
As of now, MongoDB Atlas supports log export functionality exclusively with AWS S3. In addition to the existing AWS S3 bucket integration, would be good to have the capability of pushing logs to GCP Cloud Storage for organisations who depend on GCP for cloud infrastructure.
11 votes -
UUID Schema Validation
It would be very handy to have the ability to specify a schema validator using bson type UUID (binData subtype 4) instead of the more generic binData subtype 0.
11 votes -
Add support for allowDiskUse when using the Data API
The Data API doesn't support the allowDiskUse option, leaving no way to get around this error:
"Failed to aggregate documents: FunctionError: (QueryExceededMemoryLimitNoDiskUseAllowed) Exceeded memory limit for $group, but didn't allow external spilling; pass allowDiskUse:true to opt in"
11 votes -
Backup for project user
Hello,
it would be good if we could better granulate which users have access to cloud backups.
Currently only a project user with Project Owner rights can perform backups, restores etc. It would be really cool if some users, such as developers, could be given the right to work with the backup, and at the same time not have to have the Project Owner right, as it is not wanted to be able to add users, create and delete clusters etc...
11 votes -
Allow private dns names for Atlas private endpoints
When a customer requires the use of private DNS names for their Atlas private link connection strings, can we allow them to switch on this capability? Basically use a private dns zone instead of a public one and share it as part of the VPC endpoint setup? AWS seems to offer this capability. See this link here https://aws.amazon.com/about-aws/whats-new/2020/01/aws-privatelink-supports-private-dns-names-internal-3rd-party-services/
11 votes -
Serverless instances on AWS Paris (eu-west-3) region
We are impatiently awaiting the arrival of serverless in France. A lot of projects are needed !
11 votes -
Add Datadog integration to Atlas Serverless
Datadog ( and other monitoring tools ) integrate great with Atlas, it would be awesome to copy this integration to Atlas Serverless. Without this we can't monitor Atlas Serverless with our standard toolset. In conclusion, please bring 3rd party monitoring integration to Atlas Serverless !
11 votes -
Increase total number of archives limit
Hello,
We are looking to archive hundreds of collection from each of our clusters. Right now, online archive only allows you to archive maximum 50 collections. It would be very helpful to increase that limit to at least 500. It would be okay if all of them are not active, but it would really help if we could archive more than 50 collections in total.
11 votes -
Allow registering multiple security keys in MFA
Currently, only a single security key can be registered as an MFA device. As a backup to this key, only other mechanisms such as authenticator apps can be used. It would be nice if multiple keys could be registered to avoid having to use a different method as the backup.
11 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.
11 votes -
Disk queue length metric
Atlas exposes a few hardware metrics including Util% (presumably obtained from iostat or similar). However this metric is not very significant in the age of SSDs - a volume could be 100% utilized and still have spare capacity. A more useful storage-level metric is Average queue length - this is easier to interpret (high queue length = storage contention).
Would it be possible to add this metric to Atlas monitoring?
11 votes -
Allow db.killOp() and manual restarts on secondaries
Please allow us to kill user threads on Mongo secondaries. Sometimes we have long running queries on secondaries and need to kill those threads but can't do anything about it since we don't have admin privileges to kill threads.
Also please add the ability to manually restart secondaries, not just failover the primary.Thanks.
11 votes
- Don't see your idea?