Terraform configuration is not infrastructure memory.
Terraform only knows which AWS object belongs to a resource block because state stores the binding between a Terraform address and a provider-generated ID.
This lesson breaks down the operational role of Terraform state:
- Why plans require state before comparison
- How repeat applies avoid duplicate resources
- Why destroy operations depend on stored bindings
- What Terraform actually stores inside state files
- Why state access becomes a security concern
The goal is to understand state as Terraform’s control record, not just a metadata file.