Learn Infrastructure as Code with Terraform Concepts
Describe intended state
Configuration declares the resources and relationships a team wants. Variables and reusable modules can reduce duplication, but should remain understandable to the people reviewing changes.
Review a plan before applying
A plan previews proposed changes; it is an important review artifact, not a guarantee that an operation is harmless. Check for replacement or deletion, network exposure, identity changes, and cost impact before approval.
Understand state and drift
State helps map configuration to managed resources. Protect it using the platform's recommended backend and access controls. Drift occurs when actual infrastructure differs from declared configuration; investigate the cause before applying corrective changes.
Protect credentials and environments
Keep provider credentials out of code and local state where possible. Use scoped identities, protected environments, and review requirements. Practice only in an approved sandbox with a cleanup plan.