INTERMEDIATE · 8 MODULES · 64 LESSONS

CI/CD and GitOps on AWS

Stop applying infrastructure changes by hand from your laptop: move them into a pipeline that reviews every change before merging and blocks the dangerous ones.

For you if
You already define infrastructure with Terraform and want nobody running apply by hand in production.
By the end
You'll know how to build GitHub Actions workflows, handle secrets without long-lived keys, detect drift, and roll back safely.
You need
The Terraform guide completed, Git, Docker, and a LocalStack account. No GitHub account needed.
  1. 01Why Cicd And Gitops8 LESSONS
    1. Introduction to the guide: from the terminal to the pipeline
    2. The trouble with manual `apply`
    3. CI, CD, and CD: three things, one acronym
    4. What is GitOps
    5. GitHub Actions and its alternatives, with market honesty
    6. Hands-on: installing `act`
    7. Hands-on: your first local workflow, end to end
    8. Project: bootstrapping Andes Cargo's pipeline
  2. 02Anatomy Of A Github Actions Workflow8 LESSONS
    1. Introduction: reading and writing a workflow with judgment
    2. A workflow block's complete anatomy
    3. Triggers: `push`, `pull_request`, `workflow_dispatch`
    4. The `schedule` trigger and cron syntax
    5. Reusable Actions: `uses`, `with`, and the supply-chain risk
    6. Hands-on: simulating events with `act -e`
    7. Hands-on: passing secrets to `act`
    8. Project: Andes Cargo's first real workflow
  3. 03The Iac Pipeline Fmt Validate Plan8 LESSONS
    1. Module introduction: what runs before merging
    2. The HashiCorp/GitHub pattern: `plan` on PR, `apply` on merge
    3. Installing Terraform inside an ephemeral runner
    4. Hands-on: `fmt` and `validate` as steps that can fail the job
    5. Connecting the runner to LocalStack through the host
    6. Hands-on: `terraform plan` running inside CI
    7. Publishing the `plan` as review evidence
    8. Project: Andes Cargo's `ci.yml`
  4. 04Secrets Environments And Identity8 LESSONS
    1. Introduction: who can apply what, and with which key
    2. Why credentials never belong in the repository
    3. GitHub Secrets: repo-scoped and environment-scoped
    4. What is OIDC federation
    5. The OIDC pattern in YAML, named
    6. GitHub Environments: `dev` and `prod`
    7. Hands-on: dummy credentials for LocalStack
    8. Project: Andes Cargo's secrets and environments plan
  5. 05Apply On Merge The Cd Half8 LESSONS
    1. Introduction: from review to apply
    2. The merge trigger: `push` to `main`
    3. Chaining jobs with `needs` and passing the exact `plan`
    4. Hands-on: building `apply.yml`
    5. Concurrency control: avoiding the double `apply`
    6. Scheduled drift detection
    7. Hands-on: running the drift job manually
    8. Project: Andes Cargo's full plan-to-apply pipeline
  6. 06Rollback And Safety Nets8 LESSONS
    1. Introduction: what to do when the `apply` goes wrong
    2. What rollback means for infrastructure
    3. Hands-on: the `git revert` pipeline
    4. Branch protection as a control
    5. Would a pipeline have stopped the Claude Code incident?
    6. Guardrails of `apply`, named
    7. Hands-on: a minimal, real, executed guardrail
    8. Project: Andes Cargo's safety net
  7. 07Gitops Beyond Terraform8 LESSONS
    1. Module 7 introduction: what this guide is not
    2. GitLab CI, CircleCI, and Jenkins by contrast
    3. GitOps for Kubernetes: ArgoCD and Flux, named
    4. *Push-based* vs. *pull-based*: two GitOps, one principle
    5. Application deployment strategies, named
    6. CI/CD for application code vs. infrastructure
    7. Hands-on: a minimal application pipeline, just for contrast
    8. Project: Andes Cargo's tooling decision
  8. 08Capstone The Andes Cargo Pipeline8 LESSONS
    1. Capstone introduction: the complete pipeline, end-to-end
    2. Architecture review: the complete pipeline
    3. End-to-end walkthrough: a real change crossing the pipeline
    4. End-to-end walkthrough: a rejected change
    5. What only a real GitHub account shows
    6. The security this guide didn't build
    7. What Andes Cargo still needs
    8. Final project: the Andes Cargo pipeline as a deliverable
Reviews

What students say

These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.

No approved reviews yet.

Be the first to share your experience!

SEC. 06 · THE STUDIO

Why this studio exists

For decades, building software belonged to technical profiles with years of training, and getting a digital product into the real world took companies months or years. No-code and AI have narrowed that gap, but the knowledge is still held by a few.

Tech Benders exists to open that knowledge up, so business teams and non-technical teams can put their ideas into production with the right technical decisions behind them. AI does what you ask of it. Without a technical base, what it builds may not scale with your company’s ecosystem, and its costs can run away over time.

The team knows the pains of large organizations and the speed at which they have to move. It brings solution architecture, data engineering, product built end to end from back end to front end, and daily work with AI. Software that solves what you need in days, not months, with the cost of AI kept in check.

Founders

The studioRead about Tech Benders →

Write to ushi@techbenders.io

Made with Wislab