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

36 results found

  1. Allow to assign API Key to Project via Terraform by referencing public key

    Currently you can only assign an API Key to an Atlas Project via Terraform by referencing the ID of the API Key. Unfortunately, the ID is not exposed through the UI, only through the Atlas API. This is not very ideal for customers/users that are creating API Keys through the UI.

    Adding support for referencing the API Key in Terraform via the public key instead of the ID would fix this. Or alternatively, exposing the API Key ID in Atlas.

    2 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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. mongodbatlas_cluster should wait until cluster is operational

    mongodbatlas_cluster is regarded "created" before it's operational, which breaks things if you need to use attributes that aren't yet available, like connection_strings.

    This issue is acknowledged in the provider docs:

    connection_strings - Set of connection strings that your applications use to connect to this cluster. More info in Connection-strings. Use the parameters in this object to connect your applications to this cluster. To learn more about the formats of connection strings, see Connection String Options. NOTE: Atlas returns the contents of this object after the cluster is operational, not while it builds the cluster.

    (...)

    Private connection strings may…

    2 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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  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. For resource mongodbatlas_cluster all properties related to provider move to separate block

    Current resource

    resource "mongodbatlas_cluster" "cluster" {
      project_id   = var.project_id
      name         = var.cluster_name
      disk_size_gb = var.disk_size_gb
      num_shards   = var.num_shards
      replication_factor           = var.replication_factor
      auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled
      mongo_db_major_version       = var.mongo_db_major_version
      //Provider Settings "block"
      provider_name               = var.provider_name
      provider_disk_iops          = var.provider_disk_iops
      provider_volume_type        = var.provider_volume_type
      provider_instance_size_name = var.provider_instance_size_name
      provider_region_name        = var.provider_region_name
      provider_backup_enabled      = var.provider_backup_enabled
    }
    

    Suggested resource

    resource "mongodbatlas_cluster" "cluster" {
      project_id   = var.project_id
      name         = var.cluster_name
      disk_size_gb = var.disk_size_gb
      num_shards   = var.num_shards
      replication_factor           = var.replication_factor
      auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled
      mongo_db_major_version       = var.mongo_db_major_version
      //Provider Settings "block"
      cluster_provider = {
        name               = var.provider_name
        disk_iops          = var.provider_disk_iops
        volume_type        = var.provider_volume_type
        instance_size_name = var.provider_instance_size_name
        region_name        = var.provider_region_name
        backup_enabled     = var.provider_backup_enabled
    2 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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Attach a newly created Trigger to an existing AWS Event Bridge Bus via Terraform.

    Attach a newly created Trigger to an existing AWS Event Bridge Bus via Terraform.

    2 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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  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. upload prebuilt typescript provider for cdktf support

    I am trying to add the mongodb/mongodbatlas provider to a newly created cdktf project generated in the typescript language but the installation fails as npm is unable to find a prebuilt cdktf provider for the provider

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. mongodbatlas_database_connection

    A resource that creates a connection for a database.

    resource "mongodbatlas_database_connection" "connection" {
      database        = "test"     # Name of database
      connection_type = "Standard" # or Private Endpoint
      database_user   = "test"     # Name of DB_USER
      method          = "shell"    # other options  "application | compass | vscode"
    
      # For Standard Connection
      ip = "accessAnywhere" # or other IP Address
    
      # For Private Endpoint
      endpoint = "" # ID of Private Endpoint
    }
    
    

    OUTPUT ARGUMENTS

    • id
    • connection_string
    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Create Atlas App Services and Link Them To Clusters with Terraform

    It would be great to create App Services (Realm Apps) and then create the service link to an Atlas Cluster with Terraform.

    This is so that Trigger resources can be created fully within Terraform, rather than having to hack together API calls, CLI commands or manual steps.

    1 vote

    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

    planned  ·  1 comment  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  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. Add support for profile configuration file in the Terraform provider

    To be able to quickly change which account we use for the Terraform provider without having the keys in the terraform variables, supporting profile config file like what aws does for it's provider would be a great help for us.

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Backup Snapshot datasource and Restore Job resource and datasource for Shared clusters

    The following resources/datasources work only for dedicated clusters (M10 and above).

    mongodbatlascloudbackupsnapshots
    mongodbatlas
    cloudbackupsnapshotrestorejob

    This is because they call the /backup/snapshots and
    /backup/restoreJobs Atlas API endpoints respectively.

    There are different API endpoint for shared-tier clusters (M2/M5):
    /backup/tenant/snapshots
    /backup/tenant/restores

    Would it be possible to have new equivalent datasources/resources for shared-tier clusters or modify the existing datasources/resources to accommodate shared-tier clusters?

    Thanks in advance.

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  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. mongodbatlas_cloud_backup_snapshot_restore_job should wait until the restore operation is complete

    mongodbatlascloudbackupsnapshotrestorejob creates a job and returns immediately , but I think it should wait until the restore operation is complete. just like mongodbatlascluster that waits until the cluster is in ready state.

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  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. Allow setting of advanced server parameters such as disable flow control, ttlMonitor and redactClientLogData

    For some more advanced/demanding use cases, advanced server parameters are key to provide the performance/latency or security that applications will require, either due to contractual or complaince obligations.

    FlowControl throttles writes for consistency sake, but for very low latency use cases it becomes a factor for "perceived" client SLO breach. In such particular scenarios, the cost consistent across all replicas is higher than low latency reply.

    redactClientLogData is important to ensure complaince with several sectors such has identity management.

    TTL monitor should be able to be controled via API call to better manage the migrations between self-managed clusters and Atlas.

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  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. Allow provider-level configuration for project in Atlas terraform provider

    For the provider-level configuration, would be nice to be able to set the project at provider level vs. having to provide it at resource level.

    Currently, it doesn't seem that the provider accepts a project argument.

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  Admin →
    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 ISRG certificate selection in mongodbatlas_cluster

    As described in https://docs.atlas.mongodb.com/reference/faq/security/ and a recent email announcement, the root certificate is changing. Changing the cert used is available in the UI, but not in the provider.

    It would be useful to add support for certificate selection.

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Ideally migration of terraform state should be handled or provide a tool for migrating state

    Hello,
    We initially rolled out all our clusters with mongo atlas terraform provider version 0.7.0. Since we hadn't pinned the version, we started seeing warning listed below in the terraform plan.

    Updating as indicated based on the warning means, a deletion and recreation of the private endpoint/link related resources which will lead to downtime as the cluster will be inaccessible while the private endpoint/link is being recreated.

    Ideally migration of terraform state should be handled or provide a tool for migrating state so the resource can be migrated without recreation.

    ============================================

    There are warnings related to your configuration. If no…

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. The IPs of the newly created cluster should be in the terraform state directly

    We are trying to deploy a cluster in Azure using Terraform and then inspect the newly created cluster to get the hostnames and IP addresses. We need these IP Addresses so we update the Azure Firewall to allow the Azure Key Vault to communicate with the Atlas cluster. We are doing this test to enable encryption at rest with our own keys.

    We believe the IPs should be in the terraform state directly.

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  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. Indicate operation errors already in the plan phase

    This idea originates from my original bug report: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/284

    Changing the name of an existing custom_db_role is currently not possible without ending in an error in the apply step. The plan for a name change currently indicates the replacement due to the name change:

    # module.versioner.mongodbatlas_custom_db_role.this must be replaced
    -/+ resource "mongodbatlas_custom_db_role" "this" {
        ~ id         = "someid" -> (known after apply)
            project_id = "5c860ed2a6f2396cd47f4785"
        ~ role_name  = "old_name" -> "newName" # forces replacement
    

    Applying this results in the following error:

    Error: error deleting custom db role (mongoversioner): DELETE https://cloud.mongodb.com/api/atlas/v1.0/groups/projectid/customDBRoles/roles/old_name: 409 (request "Conflict") Deleting specified custom role would leave the…

    1 vote

    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  ·  Terraform Provider  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

Feedback and Knowledge Base