AWS Certified CloudOps Engineer - Associate

Terraform and Git for CloudOps

The third-party half of infrastructure as code: how Terraform state works and why it needs a locked remote backend on AWS, the write-plan-apply workflow, how Terraform differs from CloudFormation operationally, and the Git workflow that makes any of it safe in a team.

Intermediate 26 minutes 6 Learning Objectives
  1. Explain what Terraform state is and why losing or corrupting it breaks a deployment
  2. Configure an S3 backend with locking, versioning, and encryption for team use
  3. Sequence the write-plan-apply workflow and interpret a plan's create, update, replace, and destroy actions
  4. Compare Terraform and CloudFormation on state, rollback, drift, and provider scope
  5. Bring an existing AWS resource under Terraform management with an import
  6. Describe a branch-and-pull-request workflow for infrastructure code and what CI should run at each stage