re:Invent 2026

The fact. Every session in the catalog carries its room — Caesars Palace | Promenade Level | Roman I — and a start and end time. When two sessions in your plan are at different properties, the gap between them is arithmetic on AWS's own published data. That number is what the warning states, and you can check it against the official catalog using the session code on every card.

The estimate. How long the hop takes is not published — AWS's FAQ says only to “allow for additional travel time between venues” and that shuttles “run continuously during conference hours”. So it is derived rather than guessed: the straight-line distance between the two properties, multiplied by 1.30 because a line between two hotels is not a route, divided by a walking pace of 60 m/min — slow on purpose, because this is casino floors and pedestrian bridges, not pavement — plus 10 min to get out of one room and into the next.

The distances are measured, not remembered. Each venue's position is the centroid of the building its sessions are actually in — the Venetian Expo rather than the Venetian tower, the MGM Grand Conference Center rather than the middle of the resort — taken from the OpenStreetMap footprints this page draws. The hand-written coordinates that preceded them were out by up to 508 m, which is a different end of the property from where you would be standing. Distance is a fact; only the pace below is an assumption, and it is yours to set.

Adjust: room to room min pace brisk, moving early steady (default) slow, peak crowds

The lanes are service clusters, not the catalog's Role facet. Role is too broad to filter on — “Solution / Systems Architect” alone returns hundreds of sessions. Each lane is a set of services, and every lane is one tap from the full catalog.

The catalog is not finished yet. AWS's own catalog page says it “will include more than 2,200 sessions”, and it currently publishes 2,253 — so roughly 102% of the final programme exists so far. Expect sessions to keep arriving right up to the event. That is what the scheduled refresh is for, and why a plan built today is a first draft.

Where the room comes from. Each session carries its location in AWS's own catalog data — MGM Grand | Level 3 | Room 301 — along with a venue and a seat count, and this page has one for every scheduled session. AWS's catalog page does not currently display the room, though it does offer Venue as a filter. Nothing here is inferred: it is the field AWS publishes, shown rather than hidden. Room assignments this far out should be treated as provisional.

How current this is, and how you can tell. The catalog is re-fetched from AWS every three hours by a scheduled job, and every hour from the fortnight before the event through to the last day — the cadence follows how fast the catalog actually moves, and on 23 September it moved twice in a day. The line at the top of this page works out its own age in your browser from the capture timestamp — so if the job ever stops running, the page says how old it is rather than quietly implying it is current. Three things guard the refresh: a fetch that comes back more than a fifth smaller than the stored catalog is refused rather than written, so a partial fetch cannot overwrite good data; the checks run before the commit, not after; and every session code on this page links to that session in AWS's own catalog, so nothing here has to be taken on trust. If a session you starred disappears from the catalog, your plan says so instead of quietly dropping it.

Session data captured from the official catalog on 2026-10-21. This page is not affiliated with AWS and is not the system of record: sessions get added, moved and cancelled, and reserved seating happens in the official catalog, not here.