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

139 results found

  1. Create Snapshot Export Bucket using Terraform

    Create Snapshot Export Bucket using Terraform- required to export Snapshots to S3.
    Implement the following API call by the provider:
    POST /groups/{GROUP-ID}/backup/exportBuckets

    https://docs.atlas.mongodb.com/reference/api/cloud-backup/export/create-one-export-bucket/

    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

  2. Add CFN resource to manage PrivateLink endpoints

    As per the title, add a new CFN resource MongoDB::Atlas::PrivateEndpoint to manage PrivateLink interfaces into Atlas, based on https://docs.atlas.mongodb.com/reference/api/private-endpoints/

    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

  3. Support the regions parameter of a network peering container

    In the API documentation you mention a regions parameter usable when creating a network container with a network smaller than /18. In terraform there is no such parameter. I would like to see that supported (for creating networks smaller than /18 on GCP).

    See: https://docs.atlas.mongodb.com/reference/api/vpc-create-container/#request-body-parameters

    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

  4. Show all team users on one page

    When we do SOC2 reviews, we have to take screenshots of the permissions various users have. Currently, a specific "team" in Atlas only shows 5 users at a time and is paginated. Taking screenshots of 5 users at a time is pretty tedious, so it would be amazing to have a page with the full list.

    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

    completed  ·  0 comments  ·  IAM  ·  Admin →
  5. Change Azure snapshot backups from LRS to GRS

    Sorry but this is a must. GRS is a 2 region datacenter backup, LRS only 1. Fire or disaster will take out everything if LRS is used.

    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

    3 comments  ·  Backup  ·  Admin →

    Hello,


    We recently released a feature that we call Snapshot Distribution which allows any Atlas user to copy their backups into additional cloud provider regions that are supported in Atlas. 


    This allows you to store the backups in whatever region you prefer automatically. In the event of a disaster in a cloud provider region, Atlas will intelligently use a backup copy in an additional region for a restore.


    You can read more about this in this blog, https://www.mongodb.com/blog/post/introducing-snapshot-distribution-atlas , and our docs, https://www.mongodb.com/docs/atlas/backup/cloud-backup/scheduling/#configure-service-to-automatically-copy-snapshots-to-other-regions .

  6. DNS

    In much the same way that Amazon RDS has a public/private setting, could you add a setting to Atlas that lets us make the DNS entries for our cluster resolve to their private IPs all the time instead of just inside a VPC?

    This would improve security by routing our connection through a VPN into a VPC that has a peering connection with Atlas' VPC. To accomplish this now, one must to find the private IPs of a cluster and create local, manual DNS entries in a router or on a machine.

    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

    completed  ·  2 comments  ·  Admin →
  7. Add Atlas instance in Azure Norway

    We host data that is preferred to reside in Norway. Do you have plans to expand to the newly added Azure Norway data center?

    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

    completed  ·  1 comment  ·  Other  ·  Admin →
  8. Add support for name as argument for the team data sources

    Currently, there is a datasource for team, but it requires an ID as argument.
    There are available APIs with look ups by ID but also by name.
    Can we support the data source look up by name as well? That would be interesting as could avoid knowing the ID of the project or team and look up that ID via name.

    Thanks.

    (Note Admin edit -> as project missing name as an argument was a regression that is corrected in v0.4.1. However team is still up for later consideration for name expansion so leaving for feedback.)

    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

  9. Allow creation of API Keys and their Whitelists via Terraform

    Currently it is not possible to create an Organization API Key via terraform and manage its IP Whitelist. This would be a very useful feature for large organizations: https://docs.atlas.mongodb.com/reference/api/apiKeys-orgs-create-one/

    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

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

  14. 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)

    We’ll send you updates on this idea

  15. 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)

    We’ll send you updates on this idea

  16. 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)

    We’ll send you updates on this idea

  17. Support webhook notification type for alert configurations

    The mongodbatlas_alert_configuration allows me to define a notification with type of WEBHOOK but I can't complete the configuration because it doesn't seem to support any arguments to provide the webhook URL and webhook secret/integration key.

    https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/alert_configuration#argument-reference

    Please add support for the webhook URL and secret, since otherwise the WEBHOOK type notification can't be used. Thanks

    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

  18. Enable setting encryption at rest details for project

    Please allow us to set the encryption at rest KMS details for the project when we create the project

    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

  19. Datadog integration for US5

    Hi I am using US5 datadog, and as I learned that Atlas only supports US1, it would be great if the integration with US5 is also added.

    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

  20. Granular permissions via roles / hashicorp vault

    We are using the Hashicorp Vault Atlas plugin in order to generate credentials for Atlas.
    We are able to generate roles on the Atlas end and then use those roles to provision vault users.
    However, I don't see a way to restrict those roles to just certain resources/clusters.
    So the user can access all the deployments in a project.
    It should be possible to restrict roles to certain resources only.

    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

    Hi,  


    This has already been added some time ago.   You need to specify the scopes you want to include, here's the code - https://github.com/hashicorp/vault-plugin-database-mongodbatlas/blob/master/mongodbatlas.go#L206. It should be an array like roles, but with the resource name and then if it's a cluster or data lake (see scopes here: https://www.mongodb.com/docs/atlas/reference/api/database-users-create-a-user/).   I hope that helps! 


    Best, 

    Melissa


  • Don't see your idea?

Feedback and Knowledge Base