Skip to content

Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1242 results found

  1. API - Version 2

    We saw that the api version is now in v2 for some resources (as clusters) - https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Clusters/

    We tried to change some App services functions from v1 to v2, but ended resulting in some errors (or needing to add more parameters than the original one - in version 1).
    Using version 1, we only inform what we need to change ("instanceSize") plus the providerName.

    to use version 2, we need to inform all this parameters (if it's a replica-set. If it is a sharding we also need to inform the numShards):
    "replicationSpecs":[{"regionConfigs":[{"electableSpecs":{"instanceSize":"M10","nodeCount":"3"},"priority":"7","providerName":"GCP","regionName":"CENTRAL_US"}]}]}

    What I need to change is only the…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. MongoAtlas Orga - Maximum number API keys exceeded

    We have detected in our organisation that the limit of API keys has been reached. This is currently affecting our project teams in terms of resource distribution, so we are asking for an increase in the quoter in the short term.

    Problem: We can't create keys and also delete them. The problem is that the key does not have an owner. Only org owner can delete this key. They did but this is only a reference deletion.

    Alerting: Condition for alerting is not there

    What we want to achieve:
    - Transparency for the org owners about what the limit level…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Atlas DNS name more than 23 characters from the cluster name.

    Allow users to have longer DNS name from the cluster name. Currently, Atlas cuts the first 23 characters from the cluster name and the users can't check the cluster name inside the mongo shell.

    Example:

    Cluster name longer than 23 characters : xxxx-us-east-1-multi-use-1
    DNS name : xxxx-us-east-1-multi-us.xsj8t.mongodb.net

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Atlas metrics granularity after 48 hours

    For metrics older than 48 hours, the data is presented in 1-hour intervals. This level of granularity is often too coarse for a thorough examination of past events and trends. Such a broad view can obscure smaller yet significant details critical for understanding and resolving performance issues that occurred in the past.

    Suggested Improvement:

    having a smaller granularity value for historical metrics beyond the 48-hour timeframe. Providing data in smaller intervals would greatly enhance our ability to conduct in-depth analyses and diagnose past performance issues accurately. This would be particularly beneficial for conducting detailed investigations of historical data and identifying…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Better auditing of App Service actions in Activity Feed

    The Activity Feed should show who has created an app in the App Services. Currently this is not the case, instead you will find the following information in the Activity Feed:

    A user(or Code Deployment) has deployed changes successfully to an App Service.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. AWS gp3 Decouple IOPs from Disk Size

    With AWS EBS gp3 volumes, IOPs and throughput can be provisioned separately from EBS storage size. While Atlas now uses gp3 volumes and provides a base throughput of 3,000 IOPs, higher throughputs are still directly tied to disk size.

    We run IO-intensive workloads that require high throughput, and we have to severely over-size disks to get the needed throughput. We don't require the extra-low latency of provisioned IOPs (which is much more expensive than over-provisioning storage).

    According to the linked AWS documentation below, if the M60 instance size is running on an ec2 m5.4xlarge instance type, it can support a…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Manage federated database views via Terraform

    The mongodbatlasfederateddatabase_instance resource allows managing tables in the federated instance, but it does not allow us to manage views. Please update the provider so we can also create and manage views

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Support for GCP Saudi Arabia/Dammam me-central2 for Atlas

    GCP announced availability of services in me-central2. Can MongoDB please support this region in GCP?

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Retrieve latest/max oplog timestamp via the Atlas Administration API

    At the moment the latest/max oplog timestamp can be retrieved via the Atlas UI in the backups section for point in time restores. This feedback post is to make this information available as part of the atlas administration api.

    For example, in the UI it states:

    You can only restore up to this oplog timestamp: 1692580549 and this increment: 1.

    Would be good to have this value available to be retrieved via the API for restores requiring oplog timestamp values in this format.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Enable database users separate read/write permissions based on cluster

    We have multiple clusters in the same project, and we need to limit write access to certain CLUSTERS while leaving read only access to any other cluster. The problem is that we cannot do this by DATABASE name as there are many of them, as well as dynamically addition of new ones in clusters, so it will become obsolete and very hard to maintain.
    Trying to use the restriction does not help as it limits all access, including read only, to those clusters.
    What we'd like to see is that we can limit write access by cluster (not database/collection) and…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Datadog integration for AP1 region

    I am using Datadog region AP1 (Japan) and I learned that Atlas doesn't support the region for the integration.

    It would be really great and helpful if the integration supports the AP1 region.

    https://docs.datadoghq.com/getting_started/site/

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Support migration of existing projects, clusters, ... to be CloudFormation managed

    When MongoDB::Atlas::* resources are created and the specifed project, cluster, ... already exists, then these resources should not raise an error on resource creation but use the existing project, cluster, ... and apply the given configuration. In other words, the Create event that is initially sent by CloudFormation should be handled similar to an Update event but return the physical id of already existing resources. Apparently, this behaviour should be enabled by an opt-in flag.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Add a data source for the Atlas Control Plane inbound/outbound IPs

    It would be nice to be able to fetch all outbound and inbound IPs for the Atlas control plane so that we can add them to the list of allowed IPs on Azure keyvaults for example

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Remove the requirement to have an API Access List CIDR before being able to manage backup schedules

    The issue is described in this github issue, specifically in the linked comment: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/222#issuecomment-855905952

    Here is the requirement as described in the API docs: Remove All Cloud Backup Schedules
    Removes all cloud backup schedules for the specified cluster. "This schedule defines when MongoDB Cloud takes scheduled snapshots and how long it stores those snapshots. To use this resource, the requesting API Key must have the Project Atlas Admin role and an entry for the project access list."
    https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Backups/operation/deleteAllBackupSchedules

    Our request is that the requirement to have an API Access List to manage backup policies be removed.

    At the very least,…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. API to list clusters that has snapshots on it- even deleted clusters

    Today we use the API below to list the clusters that exists in a project

    https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Clusters/operation/listLegacyClusters

    GET https://cloud.mongodb.com/api/atlas/v1.0/groups/{GROUP-ID}/clusters?pretty=true

    After having the clusters list, we can list the snapshots from one specific clusters using the API:

    https://www.mongodb.com/docs/atlas/reference/api/cloud-backup/backup/get-all-backups/

    GET https://cloud.mongodb.com/api/atlas/v1.0/groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/backup/snapshots

    Now on Mongo Atlas I can delete a cluster and ask not to delete their snapshots. So if I want to use the same functions I can't, because the list of the clusters do not show the clusters that have been deleted but still has snapshots on atlas.

    It would be great if the API that lists the cluster also give us…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Provide option to remove hidden node in NVMe clusters

    NVMe clusters default to add a hidden node where backups are pulled from. This is due to the reduced durability of NVMe volumes. In cases where durability isn't a concern, I would like to disable backups and remove the hidden node altogether.

    The UI currently provides the ability to stop backups by modifying the backup policies (see attachment). However, I cannot remove the hidden node which is simply incurring extra cost.

    Obviously there would need to be a major warning provided to the user, but this is not unprecedented in industry. AWS has spot instances that are quite successful.

    My…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. disabling snapshots

    When we disable de snapshot from one cluster, the following message is shown in the same page but it does not appear at the page that shows the changes that are being made

    It would be better if this message were also at the second page (as image uploaded)

    Please Note: This action is irreversible. Turning off or altering your type of backup will delete all of your existing snapshots immediately. If you want to keep old versions of your data, visit the backup dashboard and download your snapshots

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Associate domains to an IDP at Organization level rather than for entire mongodb.com

    At this time domain to IDP associations apply to entire mongodb.com. This makes it very difficult for large companies that have several independent departments to use mongodb.com. Some departments might want to create separate Atlas organizations and others simply access Support section of mongodb.com web-site. They wouldn't want to share an IDP created within one Atlas organization.

    One possible approach to addressing this issue is for an Atlas organization to have a distinct sub-domain on mongodb.com (e.g. bigco-org-a.mongodb.com). Another approach would be to have a field for Atlas Organization name on logon page.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Suggestion to make the Organization Role Mappings page easier to navigate to

    Make Organization Role Mappings page in the Federation Management App quicker to navigate to. Currently the quickest way is to click the "Create Role Mapping" from the Overview page under "Optional: Set Up Advanced Settings" and then click Cancel.

    If the "Optional: Set Up Advanced Settings" box is not longer available in the Overview page, you'll have to click the Organization tab from the side navigation bar > [Organization Name] > Create Role Mapping > Cancel in order to reach the Organization Role Mappings page.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base