🩺 Terraform Triage: Debug a Broken CI/CD Pipeline
Most pipelines don't break dramatically. They just quietly stop working while everyone finds a workaround.
An application team has a CI/CD pipeline to deploy their AWS infrastructure with Terraform and GitHub Actions, but it's been quietly broken for months while developers just deploy locally and pretend it's fine. They've left you a repo, a vague description of what it's supposed to do, and a Slack message that says "can you take a look?"
Your job: find what's broken, understand why, and fix it.
This is a hands-on debugging workshop, not a tutorial. There are no step-by-step instructions. There are broken things, real AWS infrastructure, and a clock. Work together, pair up, swarm around the hard ones, and share what you find. The room will get further collectively than anyone will alone. Use every tool available to you. Just make sure you understand what they're telling you.
What you'll practise:
🔍 Reading the evidence: Interpreting Terraform plan output, GitHub Actions logs, and AWS error messages to form a diagnosis.
🔗 Tracing the pipeline: Understanding how GitHub Actions, OIDC authentication, and Terraform connect end to end.
🪤 Avoiding the trap: Not every error is what it looks like. Some red herrings have been left in deliberately.
🛠️ Fixing with confidence: Applying fixes you actually understand, not just ones that make the error go away.
Who is this for? Engineers and Platform specialists who work with or alongside infrastructure and CI/CD pipelines. If you've ever inherited a broken pipeline and had to figure out where to even start, this session is for you.
🍕 Food & Drink: Doors open at 5:30 PM for drinks and networking, and pizza will be available just before 6:00 PM. We will kick off with a short intro while everyone eats and gets settled. The hands-on session will start at 6:15 PM.
⚠️ Prerequisites (Must Have): To ensure you can follow along, please have the following ready before you arrive:
A laptop.
Docker Desktop installed and running.
VS Code installed.
No API keys required.
👉 Click here for our Full Setup Guide (Please check this guide if you are on Windows to ensure WSL2 is configured correctly!)