Terraform
Integrate Terraform with Cloudaware to inventory organizations, projects, workspaces, teams, users, runs, registry modules, and registry providers for DevOps governance.
info
- Audience: Cloudaware administrators, DevOps teams, platform engineering teams, and cloud governance teams
- Outcome: Terraform Cloud or Terraform Enterprise metadata is available in CMDB for IaC visibility, workspace governance, ownership review, and reporting
Capabilities
The integration supports:
- Read-only discovery of Terraform Cloud or Terraform Enterprise metadata
- CMDB records for Terraform organizations, projects, workspaces, teams, users, runs, registry modules, registry providers, and AWS resources
- IaC coverage and governance reporting across Terraform workspaces and projects
- Search and reporting for Terraform objects using CMDB Navigator, CMDB list views, and reports
Prerequisites
Before you begin, make sure you have:
- Access to a Cloudaware account.
- A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
- Terraform API token with
Vieweraccess to Projects and Workspaces. The token can be a user, team, or organization token. - Terraform Enterprise instance URL reachable from Cloudaware, if using a self-hosted deployment.
Add a Terraform Token to Cloudaware
- In Cloudaware, go to Admin.
- Find Terraform, then click + ADD.
- Enter the following values:
- Token Name: A display name for the Terraform token.
- Terraform Token: The Terraform API token with Viewer access.
- URL: (optional)
- For Cloud-hosted (HCP Terraform): Leave blank, as Cloudaware will use
https://app.terraform.ioas the default endpoint. - For Self-hosted Deployments: The Terraform Enterprise instance URL in the format
https://terraform.companyname.com/.
- For Cloud-hosted (HCP Terraform): Leave blank, as Cloudaware will use
- Trust Certificate: Enable this option for self-hosted Terraform Enterprise endpoints only.
- Click Save.
- Confirm that the integration status indicator is green.
tip
Allow the initial discovery cycle to complete after enabling the integration.
View Terraform Data in CMDB
- In Cloudaware, open CMDB Navigator.
- In the left pane, select HCP TERRAFORMm.
- Open an object list, e.g., Terraform Software Packages, to view discovered records.
Supported Objects
Cloudaware ingests the following Terraform objects:
| Terraform Object | CMDB Object API Name |
|---|---|
| Terraform Cloud Resource AWS | CA10TF__CaTerraformCloudResourceAws__c |
| Terraform Organization | CA10TF__CaTerraformOrganization__c |
| Terraform Organization Member | CA10TF__CaTerraformOrganizationMember__c |
| Terraform Project | CA10TF__CaTerraformProject__c |
| Terraform Registry Module | CA10TF__CaTerraformRegistryModule__c |
| Terraform Registry Provider | CA10TF__CaTerraformRegistryProvider__c |
| Terraform Run | CA10TF__CaTerraformRun__c |
| Terraform Team | CA10TF__CaTerraformTeam__c |
| Terraform Team User Link | CA10TF__CaTerraformTeamUserLink__c |
| Terraform User | CA10TF__CaTerraformUser__c |
| Terraform Workspace | CA10TF__CaTerraformWorkspace__c |
Troubleshooting
note
Initial data collection may take time to complete.
Authentication Fails or Integration Shows Red Status
- Verify that the Terraform API token is correct and active.
- Confirm that the token has Viewer access to the organizations, projects, and workspaces expected in Cloudaware.
- For self-hosted Terraform Enterprise, verify that the URL is correct and reachable.
- If the endpoint uses a private or self-signed certificate, enable Trust Certificate if required.
No Terraform Data Appears in CMDB
- Allow the initial discovery cycle to complete.
- Confirm that the token can access the expected Terraform organizations and workspaces.
- In CMDB Navigator, verify that you are viewing the HCP TERRAFORMm section and related resources.
Some Workspaces or Projects Are Missing
- Confirm that the missing workspaces or projects are visible to the Terraform API token.
- Check whether the missing records belong to an organization outside the token scope.
- Review recent Terraform changes after the next discovery cycle completes.
Still stuck? Contact Cloudaware Support at support@cloudaware.com with the integration name and a brief description of the issue.
Reconfigure or Remove the Integration
warning
To rotate a Terraform token or change a self-hosted URL, edit the existing integration instead of deleting and re-creating it.
Update the Integration Details
- Go to Admin.
- Select Terraform.
- Under the tab Tokens and Organizations, select the specific integration.
- Open the three-dot menu (⋮), then click Edit.
- Update the required fields.
- Click Save.
Remove the Integration from Cloudaware
- Go to Admin.
- Select Terraform.
- Under the tab Tokens and Organizations, select the specific integration.
- Open the three-dot menu (⋮), then click Delete.
- Confirm the deletion if prompted.
Security Notes
- Use a dedicated Terraform token for Cloudaware discovery where possible.
- Grant the token only the Viewer access required for Terraform metadata discovery.
- Do not reuse personal administrator tokens for production integrations.
- Rotate Terraform tokens according to your organization's credential management policy.
- Review Terraform metadata visibility with your platform engineering team, because workspace names, run history, team membership, and resource references may reveal sensitive infrastructure context.
- Revoke unused Terraform tokens when the integration is retired.