Terraform Atlas Provider

Parent: MongoDB Atlas AWS Networking · Published reference · snapshot 2026-10-15

Depth-first rabbithole dossier for Terraform Atlas Provider; source-anchored research pack.

These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.

Structure and components

[low] Each sharded cluster has an additional electable node per region as part of the dedicated CSRS. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]

How it works

[low] compute_max_instance_size is required when compute_enabled is true. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] Atlas creates a VPC when you deploy the first M10+ dedicated paid cluster to a given provider and region. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] An Atlas cluster's public IP addresses must change when you add shards to a sharded cluster. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] An Atlas cluster's public IPs don't change when you convert a replica set to a sharded cluster, provided you make no other topology changes at the same time. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] The legacy architecture requires dedicated resources for each Atlas node, which can lead to IP address exhaustion. Sources: https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/docs/resources/privatelink_endpoint_service.md [source]

Problems, failure modes and limitations

[low] You can set database_edition on the mongodbatlas_advanced_cluster resource when creating a dedicated cluster, but you can't change it afterward and can't scale a dedicated cluster back to a Free or Flex cluster. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] storage_config.shard_size_limit_gb is required only if you include storage_config; if you omit storage_config, Atlas applies the default maximum storage limit. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] If you delete all your resources, you can't recover them. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] Non-port-mapped GCP private endpoints are deprecated and will be disabled on April 30, 2027. (verified as of 2026-10-15) Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
[low] You can't create a multi-region cluster in a project if it has one or more clusters spanning 100 or more nodes in other regions. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] If you create more than one private endpoint in a single region in AWS, you can't create private endpoints in Azure or any other AWS region. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
[low] If you create more than one private endpoint in a single region in Azure, you can't create private endpoints in AWS or any other Azure region. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
[low] If you would exceed the cross-region permissions limit when creating a cluster through the Atlas Administration API, the API returns an error. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] A querySrv ENOTFOUND _mongodb._tcp.abcd-pl-0.ab123c.mongodb.net error may occur. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]

Facts and statements

[low] The Atlas Terraform provider supports any MongoDB version that Atlas supports in your project and region, and Atlas Infinite clusters support the Atlas Terraform provider. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] The Atlas Terraform provider requires Terraform version ~> 1.0 and uses the mongodb/mongodbatlas source with version ~> 2.2. (verified as of 2026-10-15) Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] New Atlas resources can take a few minutes to provision, and the Atlas Terraform provider updates you every ten seconds until provisioning is complete. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] database_edition is unavailable for Free clusters, such as the M0 cluster, and for Flex clusters. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] To create a dedicated cluster on Atlas Infinite, set database_edition to "INFINITE" and set compute_enabled in auto_scaling. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] Dedicated Atlas Infinite clusters support the REPLICASET cluster type only. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] M30+ Atlas Infinite clusters are available on AWS Gen2 only, so append _GEN_2 to the tier name, as in M60_GEN_2. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] An Atlas Infinite cluster has two electable compute nodes, a primary and a standby, so set node_count to 2. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] The Organization Owner role is required to view the Organization ID, manage service accounts, and create or delete clusters and other project resources. Sources: https://www.mongodb.com/docs/atlas/terraform.md [source]
[low] An Atlas project, and its clusters, are associated with a region-specific VPC; to use a different VPC on the customer's own cloud infrastructure accounts, you would need to use MongoDB Cloud Manager or Ops Manager. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] For multi-region clusters, Atlas creates one VPC per region if there is not already a VPC for that region. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] Atlas limits the total number of nodes in other regions in one project to a total of 100, not including Google Cloud regions communicating with each other, Free clusters, or Flex clusters. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] If your firewall blocks outbound network connections, you must configure outbound access from your application environment to MongoDB Atlas. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] This feature is available for M10 clusters or higher. (verified as of 2026-10-15) Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
[low] Free clusters (formerly known as M0) and Flex clusters do not support connecting through a private endpoint. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
[low] In the port-mapped architecture, regardless of cloud provider, one service attachment can be mapped to up to 150 nodes via ports designated per node, enabling direct targeting of specific nodes using only one customer IP address. (verified as of 2026-10-15) Sources: https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/docs/resources/privatelink_endpoint_service.md [source]
[low] The NONE status indicates Atlas created the network load balancer and VPC endpoint service, but AWS hasn't yet created the VPC endpoint. Sources: https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/docs/resources/privatelink_endpoint_service.md [source]
[low] The PENDING_ACCEPTANCE status indicates AWS has received the connection request from your VPC endpoint to the Atlas VPC endpoint service. Sources: https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/docs/resources/privatelink_endpoint_service.md [source]
[low] The AVAILABLE status indicates Atlas VPC resources are connected to the VPC endpoint in your VPC, allowing you to connect to Atlas clusters in this region using AWS PrivateLink. Sources: https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/docs/resources/privatelink_endpoint_service.md [source]
[low] The INITIATING status indicates Atlas has not yet accepted the connection to your private endpoint. Sources: https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/docs/resources/privatelink_endpoint_service.md [source]
[low] To find the public IP address for any node in your cluster, use the nslookup tool from the command line. Sources: https://www.mongodb.com/docs/atlas/reference/faq/networking.md [source]
[low] AWS PrivateLink must be active in all regions where you deploy a multi-region cluster. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
[low] Azure Private Link must be active in all regions where you deploy a multi-region cluster. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
[low] Some Atlas clusters on Azure created before 10/16/2020 use Azure networking hardware that is incompatible with Azure Private Link. (verified as of 2026-10-15) Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
[low] The REJECTED status indicates AWS failed to establish a connection between Atlas VPC resources to the VPC endpoint in your VPC. Sources: https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/docs/resources/privatelink_endpoint_service.md [source]
[low] The FAILED status indicates Atlas failed to accept the connection to your private endpoint. Sources: https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/docs/resources/privatelink_endpoint_service.md [source]

Related concepts

Atlas — is a part of Terraform Atlas Provider
Terraform — is a part of Terraform Atlas Provider
Provider — is a part of Terraform Atlas Provider

Children

No children recorded.

← the whole tree · 3D view· how to read this page