»Using Providers and Modules from the Private Registry

All users in an organization can view the Terraform Cloud private registry and use the available providers and modules. A private registry has a few key differences from the public Terraform Registry:

• Location: You must use Terraform Cloud's web UI to search for providers, modules, and usage examples.
• Module source strings: Private modules use a four-part format: <HOSTNAME>/<ORGANIZATION>/<MODULE NAME>/<PROVIDER>.
• Authentication: Terraform Cloud workspaces using version 0.11 and higher can automatically access your private modules during Terraform runs. But when you run Terraform on the command line, you must authenticate to Terraform Cloud or your Terraform Enterprise instance.

»Finding Providers and Modules

To find available providers and modules, click the Registry button in the main navigation bar. The Registry page appears.

Click Providers and Modules to toggle back and forth between lists of available providers and modules in the private registry. You can also use the search field to filter for titles that contain a specific keyword. The search does not include READMEs or resource details.

»Shared Modules - Terraform Enterprise

On Terraform Enterprise, your module sharing configuration may grant you access to modules outside your organization. Modules that are shared with your current organization have a Shared badge in the private registry (below). Modules in your current organization that are shared with other organizations have a badge that says Sharing.

»Viewing Provider and Module Details and Versions

Click a provider or module to view its details page. Use the Versions menu in the upper right to switch between the available versions, and use the Readme, Inputs, Outputs, Dependencies, and Resources tabs to view more information about the selected version.

»Viewing Nested Modules and Examples

Use the Submodules menu to navigate to the detail pages for any nested modules. Use the Examples menu to navigate to the detail pages for any available example modules.

»Using Providers in Configurations

The syntax for public providers in a private registry is the same as for providers that you use directly from the public Terraform Registry. The syntax for the provider block source argument is <NAMESPACE>/<PROVIDER>.

terraform {
  required_providers {
    google = {
      source = "hashicorp/google"
      version = "4.0.0"
    }
  }

terraform {  required_providers {    google = {      source = "hashicorp/google"      version = "4.0.0"    }  }

»Using Modules in Configurations

Hands-on: Try the Use Modules from the Registry tutorial on HashiCorp Learn.

The syntax for referencing publicly curated modules in the module block source argument is <NAMESPACE>/<MODULE NAME>/<PROVIDER>.

module "subnets" {
  source  = "hashicorp/subnets/cidr"
  version = "1.0.0"
}

module "subnets" {  source  = "hashicorp/subnets/cidr"  version = "1.0.0"}

The syntax for referencing private modules in the module block source argument is <HOSTNAME>/<ORGANIZATION>/<MODULE NAME>/<PROVIDER>.

• Hostname: For the SaaS version of Terraform Cloud, use app.terraform.io. In Terraform Enterprise, use the hostname for your instance or the generic hostname.
• Organization: If you are using a shared module with Terraform Enterprise, the module's organization name may be different than your organization's name. Check the source string at the top of the module's registry page to find the proper organization name.

module "vpc" {
  source  = "app.terraform.io/example_corp/vpc/aws"
  version = "1.0.4"
}

module "vpc" {  source  = "app.terraform.io/example_corp/vpc/aws"  version = "1.0.4"}

To get started, you can copy and paste the usage example on the module's details page or use the configuration designer to select multiple modules and fill in their variables.

»Generic Hostname - Terraform Enterprise

You can use the generic hostname localterraform.com in module sources to reference modules without modifying the Terraform Enterprise instance. When you run Terraform, it automatically requests any localterraform.com modules from the Terraform Enterprise instance.

module "vpc" {
  source  = "localterraform.com/example_corp/vpc/aws"
  version = "1.0.4"
}

module "vpc" {  source  = "localterraform.com/example_corp/vpc/aws"  version = "1.0.4"}

To test configurations on a developer workstation without the remote backend configured, you must replace the generic hostname with a literal hostname in all module sources and then change them back before committing to VCS. We are working on making this workflow smoother, but we currently only recommend localterraform.com for large organizations that use multiple Terraform Enterprise instances.

»Module Availability

A workspace can only use private modules from its own organization's registry. When using modules from multiple organizations in the same configuration, we recommend:

• Terraform Cloud: Add modules to the registry for each organization that requires access.

• Terraform Enterprise: Check your site's module sharing configuration. Note that in Terraform Enterprise v202012-1 or higher, workspaces can also use private modules from organizations that are sharing modules with the workspace's organization.

»Running Configurations with Private Modules

»Version Requirements

Terraform 0.11 or later is required to:

• Use private modules in Terraform Cloud workspaces with no extra setup.
• Use the CLI to apply configurations with private modules.

»Authentication

You can use either a user token or a team token for authentication, but the type of token you choose may grant different permissions.

• User Token: Allows you to access modules from any organization in which you are a member. You are a member of an organization if you belong to any team in that organization. In Terraform Enterprise v202012-1 or higher, you can also access modules from any organization that is sharing modules with any of your organizations.

  Note When SAML SSO is enabled, there is a session timeout for user API tokens, requiring you to periodically re-authenticate through the web UI. Expired tokens produce a 401 Unauthorized error. A SAML SSO account with IsServiceAccount is treated as a service account and will not have the session timeout.

• Team Token: Allows you to access the private module registry from that team's organization and modules from any organizations that are sharing a private module registry with that team's organization.

A user belongs to three organizations (1, 2, and 3), and organizations 1 and 2 share private module access with each other. In this case, the user's token gives them access to the private module registries for all of the organizations they belong to: 1, 2, and 3. However, a team token from a team in organization 1 only gives the user access the private modules in organizations 1 and 2.

»Configure Authentication

To configure authentication to Terraform Cloud or your Terraform Enterprise instance, you can:

• (Terraform 0.12.21 or later) Use the terraform login command to obtain and save a user API token.
• Create a token and manually configure credentials in the CLI config file.

Make sure the hostname matches the hostname you use in module sources because if the same Terraform Cloud server is available at two hostnames, Terraform will not know that they are the same. To support multiple hostnames for module sources, use the terraform login command multiple times, and specify a different hostname each time.