Course
Everyone ships on these
AWS and Beyond
Startups, big tech, and everything in between run on some or all of these services every day. Knowing them gives you leverage over peers who only know the happy path, and unlocks opportunities that stay closed otherwise.
- Services
- 24
- Lab guides
- 37
- Lab sessions
- 291+
- Total time
- ~180h
- Mode
- Build · verify · break
01What this is
- Hands-on labs across the AWS services teams actually run. Not slide decks, not cert dumps.
- Every lab is built, verified, then deliberately broken so you learn how things fail in the real world.
- Breadth with depth: compute, data, messaging, IAM, observability. The stack behind modern products.
02Why it matters
- These services show up in the same form at a 5-person startup and a Fortune 500. The scale changes, the primitives don't.
- Interviews and promotions reward people who can reason about systems, not just follow a tutorial.
- Peers who only know one or two services hit a ceiling. Fluency across the stack is career leverage.
03What you'll walk away with
- Confidence with the services that show up in job descriptions and on-call rotations.
- A method for debugging failures instead of guessing, or waiting for someone else to fix it.
- Enough range to own work beyond the two or three services you already touch today.
04Start where you actually are
Pick one path. Don't overthink it. You can switch later.
Path 01Beginner
New to cloud and AWS. Start from zero without pretending otherwise.
- 1.Getting Started: account, billing safety, mental models
- 2.AWS Overview: how the pieces connect
- 3.Then pick your first service track
Path 02Working knowledge
You know cloud basics and a few services. Ready to go deeper.
- 1.Skip Getting Started if the account setup is already done
- 2.Fill the gaps. Start with what you use at work
- 3.Add services you haven't owned yet
Path 03Specialist
Strong on a few job services. Ready to expand the rest of the stack.
- 1.Skim AWS Overview only if you want the big picture refreshed
- 2.Pick a service you don't own yet
- 3.Run its failure labs. That's the point
05Pick a service
Click a service to see outcomes.