Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1415 results found
-
Early-Warning Alert for AWS PrivateLink Limits in MongoDB Atlas
Problem
- Cluster create/scale fails only after AWS PrivateLink endpoint quota is exhausted.
Request
- Add a threshold-based alert (e.g. 80 % of limit) via UI banner + email / webhook.
Benefit
- Prevents surprise downtime, lets admins request AWS quota increases or clean up unused endpoints in advance, and cuts support tickets.
Quick Implementation Ideas
Show current usage vs. limit in Network Access → PrivateLink and Admin API.
Allow per-project alert threshold.
Display projected endpoint use on the Review & Deploy screen.
9 votes -
Allow the creation of an Atlas Resource Policy based on database user authentication type
We would like to create Atlas Resource Policies based on the user authentication type. In a more specific example, we would like to allow ip("0.0.0.0/0") only when the database user authentication type available is Federated Auth. Another way to look at it is to deny ip("0.0.0.0/0") when the database user authentication types of x.509 or SCRAM are being used.
6 votes -
Identify users via API that are regular project users versus federated or built-in (e.g., charts) users
Expand the API to allow a way to identify and differentiate federated users and other non-manageable users (like "Charts User") from regular project users in MongoDB Atlas using API output, similar to how the Atlas UI visually marks federated users. For example, the Atlas UI displays a greyed-out edit icon and the ScreenTip displays a "Roles are managed through federated role mapping".
7 votes -
Enable Terraform export of HCL for existing Atlas configurations
Allow for a standardized export tool that outputs Terraform HCL from existing, manually provisioned Atlas resources (e.g., projects, clusters, users, role mappings, et cetera). This would be similar to GCP's Terraformer or Azure's Export for Terraform.
11 votes -
Add correlated IP address to network access alerts
Hi team, we need to monitor when a specific IP address is added to network access.
Now there's an option to monitor this action, however, we are not getting the added IP address in the alert summary or body.9 votes -
Return 'CreatedAt' for Programmatic API keys endpoints
We have an issue where we get emails from our internal Cybersecurity team 90 days after creating a MongoDB Atlas API key for rotation purposes.
For other SaaS providers we're able to stay ahead of those emails by querying their APIs and getting the date at which an API key will expire or the date after 90 days of when it has been created. This allows us to rotate keys before emails from Cyber.
The Mongo Atlas Administration API doesn't seem to provide that capability with the Programmatic access endpoints (though I am able to see the CreatedAt date in…
6 votes -
Add support for ephemeral password input in mongodbatlas_database_user resources
Terraform v1.10 added ephemeral resources that are not persisted in state, and v1.11 then added support for write-only resource attributes. To make use of this new resource type, resources must take a write-only input for applicable variables.
To make use of this in
mongodbatlas_database_user
, I propose adding an alternativepassword_wo
input that is mutually exclusive with the existingpassword
input, along with a supplementarypassword_wo_version
value that will trigger a change if required (this is the pattern used inaws_secretsmanager_secret_version
).The database user could then be configured as such, without the password being present in the terraform state:
…7 votes -
Terraform to have a generic org_owner_id instead of personal email for org creation
For now; I was told that the orgownerid while using org create using terraform has to be a non- generic email ID
data "mongodbatlasorguser" "test" {
orgid = mongodbatlasorguser.test.orgid
username = mongodbatlasorguser.test.username
}For example siri.bhar@centene.com can we have a feature to have a generic one in place or a distribution list?
4 votes -
Improve "Query Targeting Alerts" alert by including the database name and collection name
The "Query Targeting Alerts" alert notification does not contain any reference to the database or collection that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.
https://www.mongodb.com/docs/atlas/reference/alert-conditions/#query-targeting-alerts
9 votes -
Atlas Admin API endpoint to perform killOp
We would like to allow our on-call team members to view and terminate slow queries in MongoDB Atlas without granting full Atlas console access. The Project Observability Viewer role allows viewing slow queries, but stopping them (killOp) requires higher-level permissions that could expose PII and other sensitive data.
We are requesting an API endpoint for killOp that includes granular access controls. This would let our team manage problematic queries programmatically and securely, without needing elevated console permissions.4 votes -
Provide state import capability on mongodbatlas_organization resource
The mongodbatlas_organization resource does not have state import capabilities and I don't understand why. This doesn't seem to be a difficult one to implement and for us it will greatly help, because we have a need to import into state existing organisations which were created (unfortunately) outside terraform.
13 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.
11 votes -
Add support for custom comment field per API key access list entry
Currently, in the API Access List for an API Key in MongoDB Atlas, there is no way to associate metadata or context with each IP address or CIDR block. This makes it difficult to track the purpose or ownership of each entry, especially in environments with multiple users, services, or automation systems.
Please add support for an optional comment (description) field for each entry in the API Access List associated with an API Key. This field would allow users to provide human-readable context, such as:
- Who owns this IP address or range
- What system or service it corresponds…4 votes -
Enhancing Performance Advisor
Identify MongoDB Connection Users: Display which MongoDB connection users generated the queries listed in the index proposals. For instance, avoid creating indexes for queries originating from Atlas UI and MongoDB Compass.
Respect Custom Collation: Ensure that Performance Advisor respects custom collation settings. When creating an index from Performance Advisor, it should automatically include the custom collation options. Currently, these options are left empty, leading to potential negative impacts rather than improvements.
9 votes -
Add Atlas instance in GCP Sweden
Hi! We have applications running in GCP Sweden (europe-north2). Do you have any plans to add support for Atlas in that region?
4 votes -
Developer Sandbox M0 should be supported within private link
Part of the developer sandbox we can now provision M0 through self services. But we don't support private networking for M0. For FSI industry, Pharma especially this is a deal breaker as developers would want to use PII/PHI data for their PoCs/MVPs.
If we can provide M0s in their private network like other tier's there could be wide adoption of MongoDB by developers within these industries.
2 votes -
Improve "Host has index suggestions" alert by including the database name and collection name
The "Host has index suggestions" alert notification does not contain any reference to the database or collection that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.
6 votes -
Atlas tags exposed as labels in GCP billling
When you link your Atlas Account to the GCP Billing, the total cost comes through as an aggregated amount; I wish to use the Label functionality to further drill-down the costs by the Tag names and values assigned to Atlas resources (such as clusters).
This is a followup as suggested by Mongo support representative in support case #01436008
5 votes -
Request for Addition of Seoul Region to Reduce Latency
Sure! Here's the translation of your request:
A brief description of what you are looking to do
I would like to request the addition of the Seoul region because there is currently only the Japan region, which results in a 2-second delay for requests.How you think this will help
Adding the Seoul region will reduce the latency and improve the overall performance of our application.Why this matters to you
This matters to me because the current delay is affecting the user experience and efficiency of our services. Reducing latency is crucial for maintaining high performance and user satisfaction.18 votes -
Masking of PII fields
Context:
We have multiple downstream systems that consume data from MongoDB. These systems are not capable of decrypting sensitive Personally Identifiable Information (PII) fields. Currently, to protect PII, data is encrypted in MongoDB, but downstream systems cannot process or display these fields without decryption, which poses operational challenges and security risks.Request:
We would like MongoDB to provide a native field-level data masking feature that allows:Masking or redacting sensitive fields (e.g., PII fields) at query time without requiring the consumer to decrypt the data.
The masking should allow downstream systems to receive the data in a protected form (e.g.,…
1 vote
- Don't see your idea?