Many Terraform practitioners think environment selection begins with variables, workspaces, or provider settings.
Terraform starts somewhere else.
It starts with state.
In this lesson, we revisit backend design and examine how S3 backend paths define environment identity. A backend is more than a storage location. It determines which infrastructure Terraform remembers and manages.
We also discuss why backend configuration loads before providers, how S3 native locking works with use_lockfile, and why backend mistakes can create a larger blast radius than configuration mistakes.
If dev, staging, and production environments are separated, the separation must exist in state first. Everything else builds on top of that foundation.