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

149 results found

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

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

  3. 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  ·  5 comments  ·  Terraform Provider  ·  Admin →

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

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

  6. 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  ·  AdminZuhair (Admin, MongoDB) 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. 

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

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

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

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

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

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

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

  14. immutable backups

    currently Atlas - MongoDB backup are stated to be immutable, however, that is not true because there is no object lock on the s3 bucket.

    We would like to request adding the option to have an object lock on the s3 bucket that our snapshots are located on which will make sure that the snapshots can only be deleted by retention and not modified or deleted by anyone else. This is to line up with WORM compliance while dealing with financial data.

    https://www.telemessage.com/what-is-worm-compliance-and-when-is-it-needed/

    https://aws.amazon.com/blogs/storage/protecting-data-with-amazon-s3-object-lock/

    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

    0 comments  ·  Backup  ·  Admin →
    completed  ·  AdminEvin Roesle (Senior Product Manager, Cloud, MongoDB) responded

    Hello,

    I am pleased to announce that we have released our backup feature called Backup Compliance Policy, that protects your backups from being deleted by any user, ensuring WORM and full immutability (can not be edited/modified or deleted) for backups automatically in Atlas.


    Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more.


    With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes.


    Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure to read our documentation thoroughly before enabling.

  15. Make optimized connection strings available from api

    When creating a cluster that has Optimized Connection Strings as documented here: https://www.mongodb.com/docs/atlas/connect-to-database-deployment/#improve-connection-performance-for-sharded-clusters-behind-a-private-endpoint, those connection strings do not appear to be available through the Atlas API, and thus not available through the Terraform provider.

    Since legacy connection strings are not the default anymore, it would be important to make those optimized strings available through API and Terraform.

    In addition it would be nice to be able to get the legacy connection strings for old drivers even if the cluster qualifies for optimized connection strings. Those legacy connection strings are simply not populated unless the cluster was initially a replicaset…

    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

    1 comment  ·  Terraform Provider  ·  Admin →

  16. Terraform integration to manage project's API keys

    Hello team,

    we're still missing the capability to create project's API keys via terraform and have to deal with some python scripts to automatically provision new keys in dynamic way(when new projects come up).

    I know this question has been already asked and your idea is to use Vault, but probably it's not good idea to install this heavy tool for the single application...and we can't use Vault in dynamic way because it doesn't contain 'MongodbAtlas Secret Engine' available via terraform provider.

    Please consider to add possibility of creation API keys via terraform and let us decide whether it's security…

    30 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  ·  9 comments  ·  Terraform Provider  ·  Admin →

  17. Allow configuration of Data Federation via Terraform

    The mongodbatlas_data_lake (which should be renamed to reflect the new Data Federation name) doesn't allow you to specify the configuration. Without it, there is little value in having the resource defined in terraform at all.

    This issue: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/561 was created over a year ago to ask for this. A comment from MongoDB indicates its in the plan, just wanted to provide a vote for it.

    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  ·  2 comments  ·  Terraform Provider  ·  Admin →

  18. Add Enable Extended Storage Sizes in terraform project settings

    Add an Enable Extended Storage Sizes flag in terraform project settings

    Example:

    resource "mongodbatlasproject" "default" {
    name = var.name
    org    id = "TEST"

    iscollectdatabasespecificsstatisticsenabled = true
    is    dataexplorerenabled = true
    isperformanceadvisorenabled = true
    is    realtimeperformancepanelenabled = true
    is    schemaadvisorenabled = true
    isextendedstorage_sizes = true
    }

    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

    1 comment  ·  Terraform Provider  ·  Admin →

  19. mongodbatlas_serverless_privatelink_endpoint

    I'm trying to import a serverless private link endpoint but I have no success with the current resource "mongodbatlasprivatelinkendpoint". As I investigate I saw that "mongodbatlasprivatelinkendpoint" is using the "private endpoint" API not the "serverless private endpoint" API reference on this url https://www.mongodb.com/docs/atlas/reference/api/serverless-private-endpoints/ that is why its unable to get the resource I wanted to import.

    It is good if we have a separate resource for the serverless private endpoint because it is the only way to securely connect to AWS without using the network peering connection. As of this writing network peering is not yet…

    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  ·  3 comments  ·  Terraform Provider  ·  Admin →

  20. Add a datasource for members of an organization

    Problem: The mongodbatlas_teams resource only works with email addresses of user accounts which are existing members of the organization at apply time¹, and Team memberships can't (yet?) be managed via Identity Federation (third-party SAML IdP).

    Solution: If there was a datasource using the "Get All Organization Users" API² to return a list of organization members, that data could be used to filter the usernames input attribute of the mongodbatlas_teams resource to only add valid users.

    Workaround: We're using a Python script as an external datasource to get the data needed to perform said filtering.

    ¹: An error is thrown when…

    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

    1 comment  ·  Terraform Provider  ·  Admin →
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)