Build It Yourself — Cloud DevOps Capstone
The same production platform, with the files removed. Eight guided modules where you write every line, and the finished repository is the answer key rather than the starting point.
- terraform
- ansible
- aws
- kubernetes
- kustomize
- docker
- jenkins
- argocd
- trivy
- sonarqube
- prometheus
- grafana
Author
Why it exists
Most tutorials hand you a finished 200-line file and call it the config. You copy it, it works, and you have learned nothing you could reproduce a week later. This is the inverse. The workspace ships empty on purpose — seven phase directories and `src`, and nothing in them. Every module states the problem first, shows why the naive approach fails, and only then has you write the file. The finished platform sits in a separate repository as the answer key, to check yourself against when you have been stuck for fifteen minutes. It is the same system either way: EKS provisioned by Terraform, a build host configured by Ansible, Jenkins building and scanning, Argo CD reconciling, Prometheus watching. One route hands you the answer; this one makes you derive it.
What's inside
- 00 Prerequisites — the account, the tooling and the keys, before anything is built
- 01 Docker — the application containerised, multi-stage and non-root
- 02 Terraform — the AWS account described as code, with remote locked state
- 03 Ansible — the build host configured with no manual step
- 04 Kubernetes — workloads, storage, routing and policy on EKS
- 05 Jenkins — a pipeline that scans before it ships
- 06 Argo CD — GitOps reconciliation, in sync waves
- 07 Monitoring — Prometheus and Grafana, with alerts a human can act on
- A cheatsheet and an errors reference for when a command does not do what the guide said it would