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
  1. Support multi-cloud

    Support multi-cloud as available in the Atlas UI

    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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add option to create project without alerts

    Currently a project is created with a set of default alerts. We need to customize these but we can only add new alerts via terraform. It would be helpful if there was a boolean flag in the mongodbatlas_project resource to disable default alert creation

    13 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

    7 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ability to create/update a temporary Database user using terraform

    Hi
    Presently, we can only create permanent database users via Terraform Modules. The creation of temporary DB users is only allowed through the UI or by consuming MongoDb Atlas's APIs. In addition, the "deleteAfterDate" property is only applicable for a temporary user already existent. The point is to avoid using "null_resource" and "local-exec" in our Terraform Modules.

    4 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  10. Provide an option to disable password auth for database users

    Currently, it is not possible securely create a user in a terraform DevOps pipeline, since "Passwords may show up in Terraform related logs" according to the documentation. If the password was no longer required to create a user, we could avoid this issue by only using certificate authentication.

    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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  11. Create collections and indexes on cluster creation

    Allow creation of collections and indexes via terraform atlas plugin. The use case is that, when an atlas cluster is being set up, we want to enable the indexes on the collections from the start.

    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  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  12. create collection in new project

    Please create functionality for operating data in collections of MongoDB

    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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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…

    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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ability to create/update triggers using terraform

    Ability to create/update triggers using terraform

    10 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  15. Possibility to change 'frequency_type' of snapshot backup policy item via Terraform

    Hi,

    I’m facing an issue about Snapshot Backup Policy creation/modification via Terraform ( FYI, I open a case to the support of MongoDB  https://support.mongodb.com/case/00668262). Let me explain :

    When I want to create a MongoAtlas Cluster via terraform, I want to apply a custom Snahsphot Backup Policy with ONLY 2 items during the creation of the cluster :
    N° Item Frequency type Frequency Retention
    0 Daily 1 7 Days
    1 Weekly 1 (Saturday) 4 weeks

    However, during the creation of the mongo atlas cluster, I can see an error
    Error: Error applying plan:

    1 error occurred:

    * module.cluster_contrib.module.dpjmongoatlas.module.tfmodule-gcp-mongo-atlas-cluster.mongodbatlas_cloud_provider_snapshot_backup_policy.snapshot_backup:
    27 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

    2 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  16. Adding indexes using terraform

    Ability to add indexes after new clusters are created using Terraform and data has been loaded. It will help in more automation and auto recovery.

    14 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  17. Create databases and collections via API thorough Terraform

    Create databases (DB) and collections via API thorough Terraform after the cluster has been created in Atlas. This would provide the ease of writing and running it in a single script before any data is loaded.

    21 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

    5 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  18. A terraform resource for managing user access to the console

    We have a platform (as code using Terraform) where we integrate Mongo Atlas in AWS. We have multiple teams with various privileges who access the Mongo Atlas console daily basis. We would always like to manage the users in our version control. As Terraform is one of the best infrastructure configuration tools, we would like to have a terraform resource in order to manage the users via.

    8 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow Atlas clusters to be paused using terraform

    The ability to pause Atlas clusters through terraform would help with being able to pause our non-prod environments when not in use. Currently this has to be managed directly with the Atlas API

    23 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 Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow creation of Atlas organizations in Terraform

    there are really 3 steps for our dev teams to get moving in Atlas:
    1. create an org
    2. create a project
    3. create a cluster
    the first one is the only one that still has to be done from a console. if we had a terraform script to create an org in our account, we could trigger creation after approval in ServiceNow

    16 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

    2 comments  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base