Brief #09 · DevOps & SRE
AWS Infrastructure with Terraform
Medium⏱ 10-15 hSoon
No more clicking in the AWS console: every infrastructure change goes through a pull request with a reviewed plan.
Outlines are free · building with tracking needs Pro
AThe briefFrom the team
Our AWS account was built by hand over three years. Nobody knows why some security groups exist, and last month someone deleted the wrong subnet. We want infrastructure as code: every change reviewed, planned and applied by a pipeline.
What you'll build
- 1Terraform for a VPC with public and private subnets, a security group and one small instance.
- 2Remote state in S3 with locking.
- 3A GitHub Actions workflow that runs
terraform planon every PR and posts it as a comment. - 4Apply only on merge to main, with a manual approval step.
- 5Pipeline credentials via OIDC with a least-privilege IAM role, no long-lived keys.
Step-by-step walkthrough
Walkthrough coming soon
This project's step-by-step walkthrough, with real outputs at every step, is still being written. You can read the brief and try it on your own meanwhile; tracking opens when the walkthrough is ready.
Done when
- A PR shows the plan; merging applies it; nobody touched the console.
- No AWS access keys stored anywhere in the repo or its secrets.
terraform destroycleans everything up (and you ran it, to keep your bill at zero).- A README explains the module layout and how to add an environment.
Stretch goals
- Separate staging and production with workspaces or folders.
- Add
tflintandcheckovto fail PRs with risky changes.