AWS controltower documentation change
Summary
Updated documentation to reflect rebranding from 'Terraform Cloud' to 'HCP Terraform' throughout the file. Updated references to tokens, organizations, and management tools accordingly.
Security assessment
The changes are purely cosmetic rebranding updates without altering security guidance. Existing security recommendations about token handling (avoiding VCS storage, using SSM secure strings, periodic rotation) remain unchanged.
Diff
diff --git a/controltower/latest/userguide/version-supported.md b/controltower/latest/userguide/version-supported.md index dc2edfc88..63f2064bb 100644 --- a//controltower/latest/userguide/version-supported.md +++ b//controltower/latest/userguide/version-supported.md @@ -22 +22 @@ AFT supports three Terraform distributions: - * Terraform Cloud + * HCP Terraform @@ -31 +31 @@ These distributions are explained in the sections that follow. Provide the Terra -If you choose the Terraform Cloud or Terraform Enterprise distributions, the [API token](https://www.terraform.io/cloud-docs/users-teams-organizations/api-tokens) you specify for `terraform_token `must be a User or Team API token. An Organization token is not supported for all required APIs. For security reasons, you must avoid checking in this token's value to your version control system (VCS) by assigning a [terraform variable](https://www.terraform.io/cloud-docs/workspaces/variables/managing-variables), as shown in the example that follows. +If you choose the HCP Terraform or Terraform Enterprise distributions, the [API token](https://www.terraform.io/cloud-docs/users-teams-organizations/api-tokens) you specify for `terraform_token `must be a User or Team API token. An Organization token is not supported for all required APIs. For security reasons, you must avoid checking in this token's value to your version control system (VCS) by assigning a [terraform variable](https://www.terraform.io/cloud-docs/workspaces/variables/managing-variables), as shown in the example that follows. @@ -34 +34 @@ If you choose the Terraform Cloud or Terraform Enterprise distributions, the [AP - # Sensitive variable managed in Terraform Cloud: + # Sensitive variable managed in HCP Terraform: @@ -57 +57 @@ To select Terraform OSS as your distribution, provide the following input parame -### Terraform Cloud +### HCP Terraform @@ -59 +59 @@ To select Terraform OSS as your distribution, provide the following input parame -When you select Terraform Cloud as your distribution, AFT creates workspaces for the following components in your Terraform Cloud organization, which initiates an API-driven workflow. +When you select HCP Terraform as your distribution, AFT creates workspaces for the following components in your HCP Terraform organization, which initiates an API-driven workflow. @@ -72 +72 @@ When you select Terraform Cloud as your distribution, AFT creates workspaces for -Terraform Cloud manages the resulting Terraform state configuration. +HCP Terraform manages the resulting Terraform state configuration. @@ -74 +74 @@ Terraform Cloud manages the resulting Terraform state configuration. -When you select Terraform Cloud as your distribution, provide the following input parameters: +When you select HCP Terraform as your distribution, provide the following input parameters: @@ -78 +78 @@ When you select Terraform Cloud as your distribution, provide the following inpu - * `terraform_token` – This parameter contains the value of the Terraform Cloud token. AFT marks the as sensitive and stores the value as a secure string in the SSM parameter store in the AFT management account. We recommend that you periodically rotate the value of the Terraform token according to your company's security policies and compliance guidelines. The Terraform token should be a User or Team level API token. Organization tokens are not supported. + * `terraform_token` – This parameter contains the value of the HCP Terraform token. AFT marks the as sensitive and stores the value as a secure string in the SSM parameter store in the AFT management account. We recommend that you periodically rotate the value of the Terraform token according to your company's security policies and compliance guidelines. The Terraform token should be a User or Team level API token. Organization tokens are not supported. @@ -80 +80 @@ When you select Terraform Cloud as your distribution, provide the following inpu - * `terraform_org_name` – This parameter contains the name of your Terraform Cloud organization. + * `terraform_org_name` – This parameter contains the name of your HCP Terraform organization. @@ -87 +87 @@ When you select Terraform Cloud as your distribution, provide the following inpu -Multiple AFT deployments in a single Terraform Cloud organization is not supported. +Multiple AFT deployments in a single HCP Terraform organization is not supported. @@ -89 +89 @@ Multiple AFT deployments in a single Terraform Cloud organization is not support -For information about how to set up Terraform Cloud, see [the Terraform documentation](https://www.terraform.io/docs/cloud/index.html). +For information about how to set up HCP Terraform, see [the Terraform documentation](https://www.terraform.io/docs/cloud/index.html).