INTERMEDIATE · 8 MODULES · 64 LESSONS

Terraform and Infrastructure as Code

Stop creating AWS infrastructure by hand and declare it as code, so a single command can recreate or tear down the whole stack reproducibly.

For you if
You've created AWS resources command by command and want reproducibility, review, and history in Git.
By the end
You'll know how to write HCL, manage state and drift, import existing resources, and build reusable modules.
You need
The AWS core services guide, Docker, basic terminal skills, and a LocalStack account.
  1. 01Why Infrastructure As Code8 LESSONS
    1. Introduction to the guide: from commands to code
    2. The trouble with imperative infrastructure
    3. What is infrastructure as code
    4. Terraform and its alternatives: why Terraform, what is OpenTofu
    5. Hands-on: installing Terraform and a clean start
    6. Hands-on: connecting Terraform to LocalStack
    7. Hands-on: your first resource, end to end
    8. Project: bootstrapping Andes Cargo's Terraform repository
  2. 02Hcl And The Terraform Workflow8 LESSONS
    1. Introduction: reading and writing HCL with judgment
    2. Anatomy of an HCL block
    3. `resource` vs. `data`: creating vs. reading
    4. The dependency graph: implicit and explicit
    5. The `plan` → `apply` → `destroy` cycle, in depth
    6. Hands-on: `fmt` and `validate`
    7. Hands-on: proving idempotency
    8. Project: Andes Cargo's first declared resource
  3. 03Variables Outputs And Locals8 LESSONS
    1. Introduction: from fixed values to parameterized configuration
    2. Input variables and types
    3. `.tfvars` files and precedence
    4. `locals` for computed values
    5. `output` and string interpolation
    6. The `random` provider, with a fixed seed
    7. Hands-on: parameterizing the Andes Cargo bucket
    8. Project: a configurable stack for Andes Cargo
  4. 04State The Source Of Truth8 LESSONS
    1. Introduction: what Terraform remembers between runs
    2. What is `terraform.tfstate`
    3. Why state is the source of truth
    4. Hands-on: detecting drift
    5. Hands-on: importing existing infrastructure
    6. Backends: local (what this guide uses) vs. remote
    7. The security risk of state
    8. Project: Andes Cargo's state under control
  5. 05Reusable Modules8 LESSONS
    1. Introduction: stop copying and pasting HCL
    2. What is a Terraform module
    3. Anatomy of a child module
    4. Calling a module: `source` and inputs
    5. `for_each` and `count` for repeated resources
    6. Hands-on: the `s3-bucket` module
    7. Hands-on: the `iam-role` module
    8. Project: Andes Cargo's module library
  6. 06Codifying Identity And Storage8 LESSONS
    1. Introduction: the access and storage model, now in code
    2. Recap: Andes Cargo's identity and storage model
    3. IAM policies as declarative data
    4. Hands-on: declaring `LambdaManifestProcessorRole`
    5. Hands-on: declaring `AppServerRole`
    6. Bucket versioning and policy as separate resources
    7. Hands-on: declaring `andes-cargo-shipment-docs`
    8. Project: Andes Cargo's identity and storage as code
  7. 07Codifying Compute And Data8 LESSONS
    1. Introduction: compute and data, now in code
    2. Recap: Andes Cargo's processing and data model
    3. Packaging Lambda code with `archive_file`
    4. Hands-on: declaring the Lambda function
    5. Hands-on: declaring the `Shipments` table
    6. Wiring the S3 trigger
    7. Hands-on: applying the full pipeline
    8. Project: Andes Cargo's pipeline as code
  8. 08Capstone The Andes Cargo Platform As Code8 LESSONS
    1. Introduction to the capstone
    2. Architecture review: the full stack as code
    3. End-to-end: recreate from zero
    4. `plan` as a PR review, and `apply` guardrails
    5. Blast radius: the Claude Code `destroy` incident
    6. Hands-on: the same code with OpenTofu
    7. What Andes Cargo still needs
    8. Final project: Andes Cargo's infrastructure 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