1362 results found

1. Separate Atlas metric graphs of the outgoing traffic from the internal/replication traffic in Atlas cluster

   This is a request to separate Atlas metric graphs of the outgoing traffic from the internal/replication traffic in Atlas cluster

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Terminate existing connections from IPs when removed from the whitelist

   When removing entries from an Atlas Project's IP whitelist, existing connections from those IPs are maintained, and thus those hosts can continue to perform operations until the connection times out. I'm aware such connections can be dropped by doing a Test Failover or pausing and unpausing the cluster, but in some scenarios this is not ideal if even possible. This also seems like a security gap: When access is revoked from a particular IP or CIDR block, any existing client connections originating from that IP or CIDR should be terminated and the hosts behind that IP or CIDR should be disallowed from establishing new connections until such a time as they are re-added to the whitelist, if ever.

   When removing entries from an Atlas Project's IP whitelist, existing connections from those IPs are maintained, and thus those hosts can continue to perform operations until the connection times out. I'm aware such connections can be dropped by doing a Test Failover or pausing and unpausing the cluster, but in some scenarios this is not ideal if even possible. This also seems like a security gap: When access is revoked from a particular IP or CIDR block, any existing client connections originating from that IP or CIDR should be terminated and the hosts behind that IP or CIDR should be… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Description field for VPC peering page

   Add a description field to easily identity the peering items in Peerings tab. Example: "Peering for Stage Kubernetes cluster apps"

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Atlas - Preferences - My Date Format - allow 24hr

   We can specify date format but the time format is limited to 12hr clock. Please allow us to specify 24hr so the activity log and rest of the UI is a little easier to read. Thanks

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. 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 second change could result in an outage. This prevents accidental, concurrent changes from the start.

   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… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. 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 to
   - When and why it was added

   Benefits:
   - Improved manageability and clarity of access lists
   - Easier auditing and security reviews
   - Simplified troubleshooting and coordination across teams

   This functionality is already present in other parts of Atlas, such as the IP Access List for project-level IPs in Network Access, so bringing similar flexibility to the API Access List would be consistent and valuable (including Terraform resources).

   Additional UX request:
   In the Organization Access Manager, when managing API Keys, the Actions menu does not include an explicit Edit Access List option. To modify the access list, the user must click Edit Permissions, then proceed through the next steps before reaching the access list editor. This is less intuitive and inconsistent with the Project Access Manager, where Edit Access List is available directly.
   Please consider aligning the UX by adding a direct Edit Access List action in the Organization-level view as well. See attached images.

   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… more

   •  

   •  

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  IAM  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Allow API key with project owner rights the update of project API keys

    We would like to use the terraform provider mongodbatlas_access_list_api_key to maintain the access list of our existing API keys.
    We don't have an API key with organization owner rights. We have only an API key with project owner rights.
    When I do the changes via web ui project owner rights are enough. I don't understand why the terraform provider needs organization owner rights.
    In my understanding it should be possible to execute the provider mongodbatlas_access_list_api_key also with project owner rights.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Include “Tag” Field in the Cost Explorer API Response

    We would like to request an enhancement to the API functionality to better support our reporting needs. Specifically, we are asking for a “tag” field to be included in the response from the following endpoint:
    https://cloud.mongodb.com/api/atlas/v2/orgs/%s/billing/costExplorer/usage

    Background

    Our team generates detailed monthly reports on departmental usage costs using the API. Each month, we provide information such as:
    • Organization ID
    • Project ID
    • Cluster Name

    To categorize costs, we use tags to assign each cluster to specific internal department categories. These tags are already included in the CSV file available at billing > invoices > download > csv, allowing us to categorize costs accurately.

    Challenge

    While the current CSV file approach works, it requires downloading, parsing, and managing files, which introduces unnecessary complexity and file management overhead. Including the tag field directly in the API response would allow us to streamline this process and avoid handling files entirely.

    Request

    We kindly request the addition of a “tag” field in the response of the API endpoint mentioned above. This enhancement will enable us to:
    1. Automate our cost categorization and reporting process.
    2. Eliminate the need for manual file parsing and management.
    3. We can calculate costs by department or application and use resources more efficiently.

    We would like to request an enhancement to the API functionality to better support our reporting needs. Specifically, we are asking for a “tag” field to be included in the response from the following endpoint:
    https://cloud.mongodb.com/api/atlas/v2/orgs/%s/billing/costExplorer/usage

    Background

    Our team generates detailed monthly reports on departmental usage costs using the API. Each month, we provide information such as:
    • Organization ID
    • Project ID
    • Cluster Name

    To categorize costs, we use tags to assign each cluster to specific internal department categories. These tags are already included in the CSV file available at billing > invoices > download > csv, allowing… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Surface hourly usage data and charges

    Usage pattern can change very quickly throughout the day so a daily granularity of usage/cost is not sufficient for us to analyse usage behaviour.

    We need a further granularity which is the hour by hour usage and charges in order to help us monitor cost and spot pattern/irregularities.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Billing  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Add boolean for applying changes only during maintenance window

    Add boolean for applying changes only during maintenance window in order to not affect workloads during peak periods.

    E.g.: we want to modify the instance type of our cluster, but we don't want to affect workloads during the day, therefore, any change to the cluster should be applied only during maintenance hours. The same functionality should be available in the console. As a matter of fact, all changes should be by default applied during maintenance window and user can choose to opt out and apply them immediately.

    See DocumentDB as an example for this feature.
    https://docs.aws.amazon.com/documentdb/latest/developerguide/db-instance-modify.html

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. More information about snapshots and oplog sizes for backup optimization

    Backup optimizations always involve costs. However, currently, we only have access to the number of GB we are consuming. I'm not able to tell which snapshots are full or incremental. Also, when Continuous Backup is enabled, I can't see how much I'm spending on oplogs and snapshots.

    Without that information, I can't figure out if it would be better to reduce the Point-in-Time window, delete old snapshots, or change the snapshot policy.

    I went through these documentation, but I still miss the actual sizes of snapshots and logs to make the correct decision.
    - https://support.mongodb.com/article/000021504
    - https://support.mongodb.com/article/000021099

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Billing  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Option to prevent backups restores into particular cluster

    Today it is possible to accidentally restore backup into live production database. There is a "I confirm" dialog in the UI but it is not fool proof, plus when using terraform provider you still could do yourself harm.

    It would be nice to have an option similar to Termination Protection where I could mark a cluster that it should be impossible to restore backup into. If I want to restore backup into existing cluster I would have to turn the restore protection off. Or I could restore into a new cluster.

    Another way to do it would be to have backup restores possible only into a new cluster (similar to AWS Backup restores). That way you would never accidentally destroy your live production data by restoring old backup into existing cluster. In order to not break current functionalities this option could be turned on for the project. With the option off you could still restore into the existing cluster. With the option on you have to restore into new cluster.

    Today it is possible to accidentally restore backup into live production database. There is a "I confirm" dialog in the UI but it is not fool proof, plus when using terraform provider you still could do yourself harm.

    It would be nice to have an option similar to Termination Protection where I could mark a cluster that it should be impossible to restore backup into. If I want to restore backup into existing cluster I would have to turn the restore protection off. Or I could restore into a new cluster.

    Another way to do it would be to have… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Allow move jumbo chunks to admin users

    As an administrator I want to be able to move jumbo chunks by myself. Currently we are not allowed to clean the jumbo flag, so we need Support to do this.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Disable/Opt out of email notifications

    We would like the option to disable email alerts within an individual user's settings.
    We have users who need admin/owner level status for multiple projects but do not need to receive granular daily alerting like the rest of the project members. Differentiating alerts on user type alone will not solve our use case.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Edit PSC connections

    Allow admins to edit existing GCP PSC networks -- currently, if a client wants to increase the number of IPs allocated in a PSC, they have to increase the limit, delete the PSC, then create a new PSC.

    In a Production environment, this can cause 2 hours of downtime while reprovisioning PSC IPs that don't need to be provisioned, rather than scaling the number of IPs in-place.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Backup Compliance Policy to enforce "Snapshot Distribution"

    Backup Compliance policy currently can help with protecting snapshots in other regions using "Keep all snapshots when removing additional snapshot regions" option to prevent users from deleting backups copied to other regions. However we do not have a way to enforce that snapshot backups are copied to all regions where a primary could be elected.

    In order to achieve faster RTO having backup snapshots in all regions where a primary can be elected is important. Hence the feature to enforce copying backup snapshots and oplog backups to other regions via backup compliance policy is very important to compliance mandates and also makes backup compliance policy feature comprehensive/consistent covering all backup related features offered by Atlas.

    Backup Compliance policy currently can help with protecting snapshots in other regions using "Keep all snapshots when removing additional snapshot regions" option to prevent users from deleting backups copied to other regions. However we do not have a way to enforce that snapshot backups are copied to all regions where a primary could be elected.

    In order to achieve faster RTO having backup snapshots in all regions where a primary can be elected is important. Hence the feature to enforce copying backup snapshots and oplog backups to other regions via backup compliance policy is very important to compliance mandates and… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. There is no way I can delete my account.

    There is no way I can delete my account. It says I have to get rid of active organizations. When I try to get rid of my organization it says I have to get rid of my active clusters. When I try to get rid of my clusters. In clusters page it says I have no clusters.
    I tried to sign out and wait but the same problem continues.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating