Terraform Bulk Import: Bring Existing AWS Resources Under Management
You have 50 AWS resources created manually in the console. You need them in Terraform. The old terraform import CLI required importing one resource at …
You have 50 AWS resources created manually in the console. You need them in Terraform. The old terraform import CLI required importing one resource at …
Data sources let Terraform read information from your cloud provider or external systems without creating or managing resources. Use them to look up …
Terraform automatically determines resource ordering from references in your code. You rarely need depends_on — but when you do, it’s critical. …
Both count and for_each create multiple instances of a resource. The difference: count uses numeric indexes, for_each uses string keys. This matters …
Locals are computed values within your Terraform configuration — think of them as named constants or intermediate variables. They reduce duplication, …
Modules are Terraform’s unit of reuse — a directory of .tf files you can call from multiple places. Good modules save hours. Bad modules create …
Variables are inputs — values passed into your configuration. Outputs are results — values exposed after terraform apply. Together they define how …
Ephemeral resources are a newer Terraform feature (announced at HashiDays 2025) that solves a long-standing problem: how to use secrets during a …
The import block (Terraform 1.5+) lets you bring existing infrastructure under Terraform management without CLI commands. Write it in HCL, run …
The moved block (Terraform 1.1+) lets you rename resources, move them between modules, and refactor from count to for_each — all without destroying …
Terraform Stacks became generally available in late 2025 and represent the biggest new Terraform feature since workspaces. Stacks let you deploy …
LEARN BY DOING
Interactive, project-based learning — copy, paste, and understand