Section Introduction Terraform Foundations

• Why organizations adopt Terraform.
• The core building blocks of Terraform configurations.
• The standard workflow used day-to-day.
• How Terraform manages state and supports collaboration.
• When to use Terraform versus other infrastructure approaches.

​

What to expect in this section

• Why use Terraform: infrastructure as code (IaC), repeatability, auditability, and team collaboration.
• Core concepts: configuration files, providers, resources, variables, outputs, and state.
• Workflow basics: write → init → plan → apply → destroy, with examples of commands.
• Organization-level features: backends for remote state, locking, and collaboration patterns.
• How Terraform compares to manual cloud console operations and other automation tools.

​

Core Terraform workflow (quick reference)

1. Write configuration (*.tf) files that declare desired resources.
2. Initialize the working directory and download providers.
3. Review changes with a plan.
4. Apply the plan to reach the desired state.
5. Destroy resources when they’re no longer needed.

# initialize a Terraform working directory
terraform init

# create an execution plan and display changes
terraform plan

# apply the plan (create/update resources)
terraform apply

# destroy managed resources created by Terraform
terraform destroy

​

Key concepts — at a glance

​

Organization-level features and collaboration

• Backends: store state remotely (e.g., Terraform Cloud, S3, Azure Blob Storage) to share state and enable team workflows.
• State locking: prevents concurrent operations that could corrupt state (e.g., DynamoDB locking with S3 backend).
• Workspaces and remote runs: support multiple environment states and centralize execution.

terraform {
  backend "s3" {
    bucket = "my-terraform-state"
    key    = "envs/prod/terraform.tfstate"
    region = "us-east-1"
  }
}

​

When to choose Terraform vs. other approaches

​

Practical tips

• Keep state secure and use remote backends for team projects.
• Use terraform plan to review changes before applying.
• Break complex configs into modules for reuse and clarity.
• Track sensitive variables with environment variables or secret managers — avoid committing secrets.

​

Links and references

• HashiCorp: Terraform Documentation
• HashiCorp Certified: Terraform Associate exam guide
• Terraform Registry — providers and modules