Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1402 results found
-
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".
6 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.
10 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.8 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…
5 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:
…6 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.
12 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
7 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.
10 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.
8 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…3 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?
3 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.
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.17 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
4 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 -
Manage authentication tokens in account overview
When using Atlas CLI, you need to authenticate your account so that you can access the organisation/cluster. Unfortunately, there is no way to manage a list of previous authentications in your account settings.
This is important in case you are working on a machine that you have no control over and don't have a change to start the logout process from Atlas CLI on the machine you logged in.
A central UI that would allow to revoke previously granted access would be very helpful.1 vote -
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…
13 votes -
Use Semantic Versioning
Hi,
My problem is that the terraform provider doesn't use semantic versioning.
This has caused me quite a few problems.
Firstly - it's difficult when scrolling through your version releases to understand what's breaking and what's not (I lost an hour today having to check all the releases for updates, and then applying every couple of versions from an outdated provider to make sure there were no breaking changes).
Secondly, it means I have to pin a specific version in my terraform provider rather than leaving it to auto-update to the latest minor version "~> 1.0".
Lastly, it makes using…1 vote -
Create One Rolling Index in Terraform
This is a request to add our One Rolling Index request to our Terraform.
References:
* https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Rolling-Index/operation/createRollingIndexBenefits:
Many teams interact with Atlas via automation using Terraform. This has been highlighted as one of the important ones to have in Terraform.
2 votes -
Configuring provider with shared credentials file for secrets manager
Currently the provider allows configuration for secrets manager for the API key, however it looks like only static AWS credentials can be used which require assuming a role first and exporting environment variables. It would be much cleaner if you could support shared profiles, much like the AWS provider does https://registry.terraform.io/providers/hashicorp/aws/latest/docs#profile-1.
https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html
Specifically https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/internal/provider/credentials.go#L49 is static credentials, but would be great to add profile as an option as well.7 votes
- Don't see your idea?