Terraform Cloud
Also known as: Terraform, HCL, HashiCorp Terraform, OpenTofu, Terraform Enterprise, IaC
Terraform is the most popular infrastructure-as-code tool, supporting 100+ cloud providers with HCL (HashiCorp Configuration Language).
Terraform Cloud is the managed platform for Terraform teams -- providing remote state storage, collaborative plan/apply workflows, team access controls, and policy enforcement via Sentinel.
Terraform Cloud, explained at three levels
At home
Terraform lets you write code describing your cloud infrastructure (servers, databases, networking) and create or update it with one command. Terraform Cloud adds a web interface and storage for your infrastructure state, making it easier for teams to collaborate.
At work
Teams using Terraform Cloud push their Terraform code; Terraform Cloud plans and applies changes in a controlled environment. No more 'someone ran Terraform from their laptop and left it in a broken state' -- all runs are centralized, logged, and require approval.
At home
Terraform's core workflow: Write (define resources in .tf files), Plan (preview changes -- 'will create 3 resources, modify 1, destroy 0'), Apply (execute the plan). State file tracks what's been created. Terraform Cloud stores the state file remotely (preventing conflicts from concurrent runs), streams plan/apply logs, and requires manual confirmation before applying.
At work
Terraform Cloud workspaces map to environments (dev/staging/prod). Variable sets store cloud credentials centrally -- no secrets in code. Policy as code via Sentinel (or OPA) enforces organizational standards (no public S3 buckets, all resources must have cost tags, EC2 instances must use approved instance types). Private Registry stores custom provider plugins and reusable modules.
At home
Terraform's dependency graph (directed acyclic graph) determines creation order from resource relationships. The for_each and count meta-arguments enable dynamic resource creation from maps or counts. Data sources query existing infrastructure; locals compute values; moved blocks handle resource renames without destroy/recreate. Remote state data sources allow cross-workspace references for modular architectures.
At work
Terraform stacks (2024) introduce a new higher-level construct for orchestrating multiple configurations together. Provider development uses the Terraform Plugin Framework (Go). At enterprise scale, Drift Detection (Terraform Cloud) compares actual cloud state to Terraform state, alerting on out-of-band changes. No-code provisioning in Terraform Cloud allows non-engineers to deploy approved modules through a UI without writing HCL.
Real-world examples
At home
Marcus uses Terraform to manage his DigitalOcean droplets. A single main.tf file describes his servers; `terraform apply` creates or updates them. He stores state in Terraform Cloud's free tier so the state isn't only on his laptop.
At work
Fatima's platform team manages all AWS infrastructure through Terraform Cloud. Every change goes through a PR; Terraform Cloud automatically runs a plan as a PR check. A senior engineer approves the plan before it applies. Sentinel policies block any configuration that doesn't follow company security standards.
Common confusions
- Terraform Cloud is required to use Terraform — Terraform (the CLI tool) is open-source and works standalone with local state. Terraform Cloud adds team collaboration features. Many teams start with local or S3-backed remote state before adopting Terraform Cloud.
- Terraform and Ansible do the same thing — Terraform provisions infrastructure (create a VM, set up a network). Ansible configures that infrastructure (install software, set up users, deploy applications). They're complementary: Terraform creates the server; Ansible configures it.
For analysts
Terraform Cloud's audit logs provide visibility into who changed what infrastructure and when -- directly relevant for compliance reporting, incident post-mortems, and understanding cost changes correlated with infrastructure modifications.
History & origin
HashiCorp released Terraform in 2014 as an open-source tool for provisioning infrastructure declaratively. Its provider model (plugins for AWS, Azure, GCP, Kubernetes, Datadog, GitHub, and hundreds more) made it the dominant multi-cloud IaC tool. Terraform Cloud launched to address the collaboration and state management challenges teams faced with Terraform. IBM acquired HashiCorp in 2024. The 2023 license change (BSL replacing MPL) prompted the community to fork Terraform as OpenTofu, donated to the Linux Foundation.