Most beginners treat Terraform state locking as a backend configuration detail.
The actual mechanism is coordination.
Two Terraform runs can read the same state snapshot simultaneously. Both plans can appear valid. The corruption risk appears when both applies attempt to write infrastructure changes back into shared state.
This lesson explains how Terraform uses S3 lockfiles to serialize state modification, why .tflock deletion permissions matter, and why failed lock cleanup can create false stuck-lock conditions.
The lesson also covers:
- S3 backend lockfile behavior
- Backend bucket requirements
- State object versioning
- IAM permissions for lock lifecycle operations
- Deprecated DynamoDB locking paths
Understanding state locking changes how you reason about Terraform safety in team environments.