Skip to content

Atlas

← MongoDB Feedback Engine
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

How can we improve the platform?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

176 results found

  1. Adding description in user database using Terraform

    I'm not able to set description on user database using terraform. This feature is available on API but not in the terraform provider.

    7 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Terraform Provider  ·  Admin →

  2. Add sendCollectionLatencyMetrics and sendDatabaseMetrics switches for Datadog Integration

    Atlas API supports (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Third-Party-Integrations/operation/createThirdPartyIntegration) two (relatively new) keys for Datadog integration:
    * sendCollectionLatencyMetrics
    * sendDatabaseMetrics

    We need to have these switches in the terraform provider as well.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Admin →

  3. Programatically disable/enable Auto indexing Serverless

    We have Serverless instances. We want to be able to programmatically (using atlas api and terraform resource) disable/enable
    mongo atlas to auto create suggested indexes for given mongo Serverless instance. Currently, it is enabled by default and can be disabled only by toggle in Mongo UI.

    With programmatically way we can easily disable/enable auto indexing on all our Serverless instances.

    This is important to us because we want to use only indexes that we create.

    15 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Serverless Instances  ·  Admin →

  4. Terraforming IP access list for project API key

    The Terraform provider supports setting up IP access lists for organization API keys with "mongodbatlasaccesslistapikey". For project API keys, however, there is no way of managing IP access lists with Terraform, and we have to do it manually using the MongoDB Atlas UI.

    Terraforming this is valuable because it would allow us to document the why and the what for each IP address or CIDR block. Having it in code will also increase the visibility of these access lists to the rest of the team, as changes to project API key access lists will be code-reviewed…

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  6 comments  ·  Terraform Provider  ·  Admin →

  5. Push Logs to AWS S3 bucket: Terraform

    Push Logs to AWS S3 bucket, This feature is helpful, It gives a flexibility for large organizations who need to segregate logs considering Inventory, Security and Observability to organize logs to a respective destinations from S3.However the terraform provider does have api's to fulfill this feature https://www.mongodb.com/docs/atlas/push-logs/ . If it can available in terms of terraform resources, This will help our organization to enable logging in terraform IAC to simplify the logging and deployments

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Terraform Provider  ·  Admin →

  6. Order the slow queries by shape

    We are trying to use the API to get slow queries from a given cluster. Today, each line represents a single command, but it would be very usefull if we could group it by command shape. This way we could for example group it and filter by average running time, so we could simply get the most expensive queries despite the query data.

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Performance Advisor  ·  Admin →

  7. Allow Restore of Cloud Backup across Organizations

    Current restore functionality limits restoring backups to clusters in the same Atlas Organization. Allowing restores across Organizations would allow for more flexibility.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Admin →
    completed  ·  AdminKaylee (Admin, MongoDB) responded

    Hi,

    This is already currently possible within the Atlas UI. We've called this out more explicitly in our documentation here: https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-snapshot/#restore-from-a-scheduled-or-on-demand-snapshot

  8. Yearly backup option is required

    We are planning to take backup yearly , but as of now available max monthly backup. If i want to take yearly backup need to take 12 months for single year which expensive , as per our audit team need 20 years back up retention then it is required 12X20 = 240 backups which is very expensive. If yearly backup is available only 20X1 = 20 only.
    As of now only available below options:
    Hourly
    Daily
    Weekly
    Monthly

    Raised case also in our support portal: 01198437

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Backup  ·  Admin →
    completed  ·  AdminKaylee (Admin, MongoDB) responded

    Hi! We added the yearly snapshot policy option earlier this year. If you do not see it in your backup policy table under the Backup tab of your cluster's Backup page, click the "+ Add Frequency Unit" button and select "Yearly Snapshot" from the dropdown. Thank you for submitting your feedback to the team!

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

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  CloudFormation Resources  ·  Admin →

  10. 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)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Admin →

  11. Terraform feature request: Cluster Termination Protection

    Termination Protection has been added. Would be great to add support for it in the terraform provider, so clusters can be provisioned and configured entirely via terraform.

    Without this support, we need to perform some configuration manually in the UI.

    15 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Terraform Provider  ·  Admin →

  12. Create option in terraform for keep backups after destruction

    I saw that a feature was released to keep the backups of a cluster even if it was terminated. Basically the idea is to add a bool in terraform that does the work of activating or deactivating this feature, because whoever destroys the cluster using terraform does not have the option to keep the backup.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Terraform Provider  ·  Admin →
    completed  ·  Zuhair responded

    Backup Compliance Policy was released with v1.9.0 and Retain Backup flag is available in mongodbatlas_cluster and mongodbatlas_advanced_cluster in v1.10.0. Thank you for the feedback. 

  13. Allow creation of free cluster (M0) through Coudformation & CDK

    This is already supported trough API and implemented in Terraform. I would like to see this extended to Cloudformation and CDK.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  CloudFormation Resources  ·  Admin →

  14. Add v1.5 API support to Terraform to support asymmetric hardware

    We use a base tier MongoDB cluster (M20) and an analytics tier (M30), where they are of different sizes due to different business requirements.

    Currently this is not supported by Terraform unless tiers use the same hardware (e.g. either both are set to M20 or M30).

    See the error message below.

    Error: error reading MongoDB Cluster (development): GET https://cloud.mongodb.com/api/atlas/v1.0/groups/1234567890/clusters/development: 400 (request "ASYMMETRICHARDWAREINVALID") Asymmetric hardware is not supported by the v1.0 API. Please use the v1.5 API instead. Documentation for the v1.5 API is available at https://docs.atlas.mongodb.com/reference/api/clusters-advanced/.

    Please add v1.5 API support to Terraform to support asymmetric hardware.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Terraform Provider  ·  Admin →

  15. Atlas backup to second region in a Terraform Module

    Feature for selecting "Atlas backup to second region" in Terraform Module.
    Currently, this option is only supported by the UI and the API.

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Terraform Provider  ·  Admin →

  16. Terraform Serverless VPC Endpoint configuration

    Create the equivalent of mongodbatlasprivatelinkendpoint but for serverless.

    8 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  8 comments  ·  Terraform Provider  ·  Admin →

  17. Shared-Tier (M2 & M5 Clusters) Snapshot and Restore Jobs Resource in Terraform

    Shared-Tier (M2 & M5 Clusters) Snapshot and Restore Jobs Data Sources are on the near-term roadmap for the MongoDB Atlas Terraform Provider, but is there any interest in also having a Terraform Resource as well? This way users will be able to create, update, and destroy these resources as well.

    Note: there is no DELETE http method in Atlas Admin API for either Shared-Tier Snapshot or Restore Jobs (https://lnkd.in/e3-GZH6M). So this will likely have to be supported first before team can create the associated Terraform resource which is likely going to be some time away.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Admin →
    completed  ·  Zuhair responded

    Released as part of v1.11.0, try today and thank you for all the feedback!  

  18. AtlasBasic CDK

    AtlasBasic CDK should include an option to create to serverless cluster as opposed to dedicated/shared.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  CloudFormation Resources  ·  Admin →

  19. GCP Export Cloud Backup Snapshot support

    Currently "Export Cloud Backup Snapshot" is a really good feature for off-line backups, but it only supports S3. This is quite limiting for organisations that don't use AWS. It would be really good if it also supported GCP Cloud Storage.

    52 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    14 comments  ·  Backup  ·  Admin →
    completed  ·  AdminKaylee (Admin, MongoDB) responded

    We are excited to announce that Atlas now supports exporting snapshots from any cloud provider to Google Cloud Storage using the Atlas Admin API.


    This release completes our support for exports to all three major cloud storage providers – AWS S3, Azure Blob Storage, and now GCP – giving you greater flexibility in where you can store your data for long-term archival or off-platform storage. To learn more, check out our docs here.

  20. Allow to add tags to Atlas Project Clusters

    Tagging resources is not a new idea and it is widely used across cloud/service providers, that allow the operators to use tags to better identify deployed business resources.
    Today, this is not available, making it harder to create processes that allow operators to identify deployed resources, in particular deployed clusters. Leading operators to use the cluster name or project name to build strict hierarchies, to distinguish, as an example, which projects or clusters are development or production by providing a prefix or suffix. This approach is brittle, since you cannot change the name of a cluster (or want to) needing…

    5 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Resource Tagging  ·  Admin →
← Previous 1 3 4 5 … 8 9
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)