INTERMEDIATE · 8 MODULES · 64 LESSONS

SRE and Incident Response

Measure how reliable your system is in actual numbers, and respond to a production incident with clear roles, useful alerts, and a blameless postmortem.

For you if
Your AWS system already works, and nobody has defined what reliable means in numbers.
By the end
You'll know how to define SLIs, SLOs, and error budgets, alert on budget burn, run an incident, and write a runbook that works.
You need
An AWS project with its pipeline already in place, Docker, basic Python, and a LocalStack account.
  1. 01What Is Sre And Reliability As A Feature8 LESSONS
    1. Guide introduction: from "it works, it's secure, it fits the budget" to "it's reliable"
    2. What SRE is (and isn't)
    3. Reliability as a feature, not an accident
    4. Hands-on: reading Andes Cargo like an SRE would
    5. Two real incidents, two different questions
    6. Hands-on: the error budget the Claude Code incident burned
    7. The vocabulary you'll use all guide long
    8. Project: Andes Cargo's reliability charter
  2. 02Slis Slos And The Error Budget8 LESSONS
    1. Introduction: from vocabulary to math
    2. Choosing a good SLI: the four golden signals
    3. Hands-on: your first SLI definition
    4. Hands-on: the error budget calculator
    5. Choosing an SLO that means something
    6. Hands-on: burn rate, the consumption rate, not just the balance
    7. Hands-on: applying the calculator to a real Andes Cargo scenario
    8. Project: Andes Cargo's `SLO.md`
  3. 03Observability As Sli Input8 LESSONS
    1. Introduction: observability in service of a question, not a dashboard
    2. The three pillars, with an SRE lens
    3. Hands-on: real metrics from the inherited Lambda
    4. Hands-on: real logs with `jq`
    5. Hands-on: traces with OpenTelemetry and Jaeger
    6. Hands-on: Prometheus and Grafana, the stack the market asks for
    7. From raw telemetry to a measured SLI
    8. Project: Andes Cargo's observability-to-SLI pipeline
  4. 04Alerting On Error Budget Burn Rate8 LESSONS
    1. Introduction: why a static threshold isn't enough
    2. Multi-window, multi-burn-rate: the real Google SRE pattern
    3. Hands-on: the burn rate evaluator
    4. Hands-on: the real rule in Alertmanager
    5. Hands-on: a real CloudWatch alarm on the Lambda
    6. What AWS already automates: CloudWatch Application Signals, named
    7. Hands-on: routing the alert
    8. Project: Andes Cargo's alerting policy
  5. 05The Incident Lifecycle8 LESSONS
    1. Introduction: the framework before the case
    2. The lifecycle of an incident
    3. Severity levels, with real Andes Cargo examples
    4. Roles during an incident
    5. Hands-on: Andes Cargo's severity matrix
    6. On-call, with honesty about its cost
    7. Hands-on: a deterministic on-call rotation
    8. Project: Andes Cargo's `INCIDENT-RESPONSE-PLAN.md`
  6. 06Operating The Claude Code Incident8 LESSONS
    1. Introduction: operating, not narrating again
    2. Hands-on: reconstructing the exact timeline
    3. Hands-on: classifying the severity
    4. Hands-on: declaring the incident
    5. Communication during an incident: internal vs. external
    6. Hands-on: the mitigation decision tree
    7. This incident's error budget, with the full vocabulary
    8. Project: Andes Cargo's final `TIMELINE.md` for this case
  7. 07Blameless Postmortems And Runbooks8 LESSONS
    1. Introduction: from the timeline to systemic learning
    2. What makes a postmortem "blameless"
    3. Hands-on: writing the Claude Code incident postmortem
    4. Action items that actually get done
    5. What a runbook is (and is not)
    6. Hands-on: Andes Cargo's first real runbook
    7. Hands-on: the honest backup/restore attempt
    8. Project: Andes Cargo's postmortem and runbooks package
  8. 08Capstone The Andes Cargo Reliability Package8 LESSONS
    1. Introduction to the capstone
    2. Architecture review: the full reliability machine
    3. Hands-on: introducing a deterministic synthetic incident
    4. End-to-end: the alert fires, the incident gets declared
    5. End-to-end: the runbook mitigates, the postmortem closes
    6. What this guide left representative, final honesty
    7. What Andes Cargo still needs
    8. Final project: Andes Cargo's reliability package 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