Automation & Delivery
DevOps — Jenkins
The CI/CD server that tests and deploys every piece of infrastructure in this stack: Terraform plans and applies, and the dbt docs build.
Architecture Decisions
Sits behind the ALB in a private subnet — no direct public exposure.
- EC2 — error log detection, high CPU, low CPU
The pipeline diagrams are in and the decisions above are what the old page documented — it cut off mid-list. Send me notes on the two pipelines (stages, approvals, how Terraform state and the dbt docs publish are handled) and I’ll finish this out.
Delivery Across the Stack
Jenkins is the execution layer, but delivery spans a few tools.
Every resource in this environment is declared in code across eight repositories, so the whole stack can be torn down and rebuilt reproducibly.
Runs the plan/apply pipelines and the dbt docs build. Behind the ALB in a private subnet.
GitOps continuous delivery for anything running inside the Kubernetes cluster — see Kubernetes.
Used alongside Jenkins for lighter-weight repository automation.