Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1366 results found
-
Billing Alerts on Atlas
Currently the alerting for billing is based on fixed values. It would be better to have the option to set up billing alerting based on increased percentages instead of fixed values. This way it would be easier to set up applicable cross-functional alerts for enterprise organisations to monitor costs.
7 votes -
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 -
iops
Proactive Warnings for Concurrent Operations
The Problem: We experienced 1+ hour service outage because we made two separate changes (IOPS ) too close together.
We can see the guidance in docs but it cannot proactively prevent the issue.
from 3000 to 6000 : There was no node down issue
from 6000 to 8000 : Issue happened.
The Feature Request: Add a proactive warning system that detects when a cluster modification is already in progress. If a user tries to submit a second change, an alert should pop up explaining that a prior operation is still underway and that submitting a…4 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.
7 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 -
Global Cluster Configuration Warning & Guardrails
The Problem: We intended to perform a simple M30 to M40 scale-up but accidentally enabled the 'Global Cluster Configuration' option in the UI. This unintended action triggered sharding, leading to a severe and unexpected two-hour outage that resulted in revenue loss.
The Feature Request: We need to implement a more robust system for these critical changes to protect customers from operational mistakes.
A good solution would include:
Clear Warning Message: When a user attempts to activate the 'Global Cluster Configuration' option, a prominent and clear warning should appear, stating: "This action will initiate cluster sharding and may cause a service…
3 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_woinput that is mutually exclusive with the existingpasswordinput, along with a supplementarypassword_wo_versionvalue 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:
…8 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
10 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 -
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 -
Support Billing Alerts Based on Usage Date
Currently, Billing Alerts in MongoDB Atlas are triggered based on the Billed Date, not the Usage Date.
This often results in alerts caused by delayed reporting from cloud providers, rather than actual real-time usage spikes.I suggest adding an option to trigger Billing Alerts based on Usage Date.
This would make alerts more accurate, reflect actual activity, and help users respond promptly to unexpected cost increases.3 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.
13 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 -
Granular permission for project level
Atlas project-level roles (like readWriteAnyDatabase or readAnyDatabase) apply universally across all clusters within the project.
We understand the current limitation where roles like readWriteAnyDatabase or readAnyDatabase apply across all clusters within a project. However, for our use case, it is critical to assign granular database permissions per cluster for AWS IAM roles—especially to avoid unintentionally granting access to sensitive clusters like Unification.Given this, we would like to formally request this as a feature enhancement. Specifically, the ability to:Ensure isolation of role permissions per cluster within the same Atlas project. We also opened a case 01493221 for this with support
3 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 -
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 -
Collection size metrics
Hi,
From time to time we have Atlas auto-scale up our clusters' disks. We then need to start analyzing why. In some cases it is organic growth of the data we store, but in some cases we are missing TTLs or they are misconfigured and we accumulate data we do not need.
In both cases, trying to realize what causes the disk increase is a very tedious process as some clusters have thousands of collections.
To overcome this, we started running a small utility that gathers some data over all our collections. It iterates on all the organizations, all the…8 votes -
Display the error code within Atlas UI if an index fails
When creating an index via the Atlas UI, the interface currently does not display the error code if the index build fails. This lack of visibility makes it difficult for customers to understand the cause of failure without contacting support.
This limitation is particularly impactful for unique index creation. In these cases, mongod validates constraints only at the end of the build process. If duplicate keys are found, the index build fails after consuming significant time and resources — but the Atlas UI does not surface the underlying E11000 duplicate key error (or other relevant error codes).
If I submit…
2 votes
- Don't see your idea?