137 results found

1. 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 like any other code. Ultimately, this should be good for MongoDB Atlas because it will increase the visibility and usage of this security feature.

   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… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  5 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Terraform Provider  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminZuhair (Admin, MongoDB) responded

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

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  1 comment  ·  CloudFormation Resources  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. AtlasBasic CDK

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

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  1 comment  ·  CloudFormation Resources  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   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. 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 or Mongo support intervenes.

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminZuhair (Admin, MongoDB) responded

   this feature has been released as part of v1.10.0. thank you for the feedback. 

   
   

   for more details see: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/advanced_cluster#connection_strings.private_endpoint.#.srv_shard_optimized_connection_string 

8. 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
   orgid = "TEST"

   iscollectdatabasespecificsstatisticsenabled = true
   isdataexplorerenabled = true
   isperformanceadvisorenabled = true
   isrealtimeperformancepanelenabled = true
   isschemaadvisorenabled = true
   isextendedstorage_sizes = true
   }

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminZuhair (Admin, MongoDB) responded

   hi this feature has been release as part of v1.10.0. thank you for the feedback. 

   
   

   for more details see: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project#is_extended_storage_sizes_enabled

9. 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 trying to add a user who hasn't logged into Atlas or isn't part of the organization: 401 (request "NOT_USER_ADMIN") The currently logged in user does not have the user administrator role for any group, team, or organization containing user.

   ²: https://www.mongodb.com/docs/atlas/reference/api/organization-users-get-all-users/#get-all-organization-users

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminZuhair (Admin, MongoDB) responded

   this feature has has been released as part of v1.10.0 release. thank you for the feedback. 

   
   

   for more details see: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/data-sources/organizations

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. 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 to come up with client side mapping rules to better manage the deployed clusters.

    Tagging project clusters allows operators to qualify and/or better identify the deployed resources, expanding their capabilities to build business logic process for resources management.

    These tags should be exposed via API calls, such as GetOneCluster.

    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… more

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Resource Tagging  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  3 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. 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 supported in serverless instances.

    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… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  3 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

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

17. Having tag/label in the Atlas UI

    Hello,

    The ATLAS portal used to view our organizations, projects, deployments, etc... does not offer a tag/label functionality at the visual interface level.

    This is problematic because when managing multiple organizations, projects, and deployments. We need to be able to put metadata on these objects/components (organization, project, deployment, user, custom group, API Key, Network address) in order to properly manage our inventory.

    In Azure, this notion of "tag" is very useful and can be used on all types of components (See attached image which presents tags that we have on an Azure component used for encryption at rest).

    We would like to have this functionality on the Atlas visual interface. I know there are "labels" that can be added to Atlas components/objects via APIs. Unfortunately, these do not appear on the screen.

    I hope you have the agility to make this feature available within an acceptable timeframe.

    Hello,

    The ATLAS portal used to view our organizations, projects, deployments, etc... does not offer a tag/label functionality at the visual interface level.

    This is problematic because when managing multiple organizations, projects, and deployments. We need to be able to put metadata on these objects/components (organization, project, deployment, user, custom group, API Key, Network address) in order to properly manage our inventory.

    In Azure, this notion of "tag" is very useful and can be used on all types of components (See attached image which presents tags that we have on an Azure component used for encryption at rest).

    We would… more

    • 

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Resource Tagging  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    completed  ·  AdminTonya Edmonds (Sr. Product Manager, MongoDB) responded

    I'm excited to announce that we recently released tags on database deployments. Check it out today.

    https://www.mongodb.com/docs/atlas/tags/

    
    

    Tags on projects is coming soon! If you want to be one of the first to test out tags on projects, let me know!

18. Shared Clusters upgrade to MongoDB 6.0+

    Currently MongoDB 6.0.1 is only available in dedicated clusters (M10+) and in serverless clusters.

    We need to use MongoDB 6.0.1 or higher in the shared cluster (M0/M2/M5).

    I understand that this should be in the roadmap anyway, but getting it sooner than later would be great.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. To not to delete the most recent backup when the DB is deleted

    After a cluster is terminated in MongoDB Atlas, the backups disappear with it. It will be good to preserve the most recent backup of this database. Otherwise, there is no point to have backup if the DB cannot be recover after accidental delete

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  0 comments  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Terraform Serverless VPC Endpoint configuration

    Create the equivalent of mongodbatlasprivatelinkendpoint but for serverless.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  8 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close