Why use infrastructure as code?

With infrastructure as code, the desired state lives in a repository instead of a console. Changes go through review and a pipeline, and the tool computes a plan before applying it. That makes environments repeatable and gives you a history of who changed what.

Why it matters

• Reproducible environments from development through production
• Code review and automated policy checks before changes land
• Drift detection when someone edits resources manually
• Modules for reusable patterns such as networks and accounts
• A path to disaster recovery by rebuilding infrastructure from source

resource "aws_s3_bucket" "logs" {
  bucket = "vh-logs-prod"
}

resource "aws_s3_bucket_versioning" "logs" {
  bucket = aws_s3_bucket.logs.id
  versioning_configuration {
    status = "Enabled"
  }
}

State is the mapping between declared resources and real infrastructure. Store it remotely with locking, restrict access, and treat it as sensitive because it can contain secrets and resource details. Do not let two pipelines apply the same state concurrently.