Glossary

AWS re:Invent session types, explained

Breakout, chalk talk, workshop, builders’ session, code talk. The catalogue names the format but does not tell you what walking into one is like — and the format decides how much of your week a single line item costs.

re:Invent labels every item in the catalogue with a format and a level. Both are load-bearing: the format tells you whether you will be listening, typing or arguing, and the level tells you whether the hour is worth spending given what you already know. Pick wrong and you burn two hours of a five-day week on something you could have watched on YouTube in January.

The formats

Keynote

The big room. Product announcements, demos, and the news the rest of the week is built on. They are streamed and recorded, so the real question is whether you want the room or the extra hour of sleep — and if you want the room, the queue starts long before the keynote does. Overflow rooms exist and are a perfectly good compromise.

Innovation talk

A keynote-shaped session one level down: an AWS leader on a theme rather than a product line, usually an hour, usually recorded. Strategy and direction, not implementation detail.

Breakout session

The default format and most of the catalogue. An hour, a speaker, a deck, a room of a few hundred people, and questions at the end if there is time. Breakouts are recorded and posted publicly afterwards, which makes them the easiest thing to cut from an over-full day: you can watch it in December from your sofa. What you cannot get later is the hallway conversation on the way out.

Chalk talk

An hour, a much smaller room, and a whiteboard. The presenter opens with a short framing — ten or fifteen minutes — and then the rest is the room asking questions and the architecture getting drawn live. Chalk talks are usually not recorded, which is precisely why they are worth a seat: this is where you get to say “yes, but our setup looks like this” and have someone from the service team answer it.

They fill up. If a chalk talk is the reason you came, reserve it, and turn up early anyway.

Workshop

Two hours, hands on, laptop required, usually in an AWS-provided account so you are not spending your own money or waiting on your own IAM. You work through a scenario at a table with a handful of other people and roaming staff to unstick you. Bring a laptop that can actually run a browser and a terminal for two hours on battery, because table power is not guaranteed.

Two hours is a quarter of a usable day. Book one, maybe two in a week — and check what it is next to before you do.

Builders’ session

The small one: an hour at a table of about six people with one AWS expert, working through a guided problem. Closer to a tutoring session than a talk. Highest ratio of expert attention to minutes spent in the whole catalogue, and correspondingly the hardest to get a seat in.

Code talk

An hour of somebody walking through actual code on screen and taking questions as they go. No slides to speak of. If you want to see how a thing is really wired rather than how it is positioned, this is the format.

Lightning talk

Twenty minutes on the expo floor, walk-up, no reservation. Good filler for the half-hour you cannot do anything else with, and a cheap way to sample a topic before committing an hour to it.

Dev chat, jams and bootcamps

Around the edges: informal community-led conversations, gamified team challenges that run for hours, and full- or half-day bootcamps that usually sit before the conference proper rather than inside it. All of them are large time commitments relative to a breakout — treat them as the thing you plan a day around, not the thing you slot into a gap.

The levels

Every session carries a number, and the number is about assumed knowledge, not about difficulty:

• 100 — Introductory. Assumes you have heard of the service. Overview, use cases, why it exists.
• 200 — Intermediate. Assumes you have used it. Goes into how the pieces fit.
• 300 — Advanced. Assumes you run it in production. Trade-offs, limits, failure modes.
• 400 — Expert. Assumes you have already hit the limits and want to know what people do about them.

The common mistake is levelling by seniority rather than by service. A principal engineer who has never touched the service in question wants the 200, and will get more out of it than out of the 400.

Reserved seats, walk-up lines, and repeats

Reserving a seat holds it up to a cut-off shortly before the session starts; after that it goes to the walk-up line. This cuts both ways. A reservation you turn up late for is a reservation you lose, and a session with no seats left is often still gettable if you are willing to stand in a line twenty minutes early.

Popular sessions are also repeated later in the week, sometimes at a different venue. The repeat is the release valve for a clash: when two things you want are at the same time, check whether one of them runs again somewhere you can be.

How this changes what you book

Read the catalogue with the format in mind and a week starts to allocate itself. Recorded breakouts are the flexible layer — valuable, but recoverable. Chalk talks, builders’ sessions and workshops are the part of re:Invent you can only get by being in the room, so they are what the rest of the day should be arranged around. And a two-hour workshop at the far end of the Strip does not just cost two hours; it costs the walk on both sides of it.

That last part is the one people get wrong, and it is a question about the map more than the calendar . If you are going for the first time, the first-timer guide covers the rest of the week around the sessions.