AWS re:Invent 2K26: How to Get the Most Out of the Biggest Cloud Week of the Year!
After three AWS re:Invents, I’ve learned that getting the most out of this massive event isn’t about attending everything. It’s about planning smarter, choosing the right sessions, meeting the right people, and leaving room for the unexpected.
There is a moment at every AWS re:Invent when you realize you have made a terrible mistake. Usually, it happens around Wednesday afternoon.
You have already walked what feels like a half-marathon. Your calendar has six back-to-back sessions. Your phone is at 18%. You have three different AWS bags hanging from your shoulder. You are standing somewhere inside The Venetian trying to figure out whether your next session is a 5-minute walk or a 20-minute shuttle ride.
And somehow, you are still excited. That is re:Invent.
I’m heading into my fourth AWS re:Invent, and every year I learn something new. The first time, I was mostly trying to understand how the whole thing worked. The second time, I became better at planning. By the third, I stopped trying to attend everything. And that, honestly, was one of the biggest lessons.
You don't get the most out of re:Invent by attending the most sessions. You get the most out of it by being intentional about what you want to learn, who you want to meet, what questions you want answered, and what experiences you don't want to miss.
Here is how I approach it now.

First, understand what you are walking into
AWS re:Invent is not a normal technology conference. For 2026, AWS has planned more than ~ 2000 sessions across multiple Las Vegas venues, including keynotes, breakouts, workshops, chalk talks, builder sessions, labs, code talks and more.
And the venues are spread across a huge area - The Venetian, Wynn, Encore, MGM Grand, Caesars Palace etc.
Your calendar may say two sessions are only 30 minutes apart. Your legs may strongly disagree.
So the first rule is simple: Don't plan re:Invent like a normal conference.
Plan it like a small city. Give yourself travel time. Leave gaps. Know where your next session is before you leave the current one. And wear comfortable shoes.
1. Don't start with the session catalog. Start with your goals.
This is probably the biggest change I have made over the years. Earlier, I would open the session catalog and start adding everything interesting.
AWS Networking? Add it.
Security? Add it.
Containers? Add it.
AI? Obviously.
Landing Zones? Definitely.
FinOps? Why not?
And suddenly I had 37 sessions in my schedule. That's not a plan. That's a problem. Before looking at sessions, ask yourself:
What do I want to come back with?
For example, this year my themes might be:
- Platform engineering
- Agentic AI
- App modernization
- Security & Governance
Once you have three or four themes, session selection becomes dramatically easier. You stop asking:
"Does this session look interesting?"
And start asking:
"Does this session help me answer something I actually care about?"
That small change makes the entire week better.
2. Don't confuse "Favorite" with "Reserved"
This is one of those things you learn once and never forget. When you find an interesting session, you can favorite it. That does not mean you have a seat.
For sessions eligible for reserved seating, you need to actually reserve the seat through the attendee portal or AWS Events mobile app. My approach is to create three buckets:
Must Attend
These are sessions I genuinely don't want to miss. Reserve these first.
Would Like to Attend
Good sessions, but I am okay skipping them if something better comes up.
Backup
Interesting sessions happening at the same time as my primary choice. This gives you flexibility.
And here's another important lesson:
Don't build a schedule with zero breathing room.
If one session ends at 11:00 and another starts at 11:00 at a different hotel, you haven't created a schedule. You've created a race.
3. Arrive early. Even with a reservation.
A reserved seat isn't an excuse to walk into the room at the last minute. AWS currently states that reserved seats can be released to walk-up attendees if you haven't arrived at least 10 minutes before the session starts. I usually aim for 15-20 minutes. That gives me time to:
- Find the room
- Grab water
- Set up my laptop
- Say hello to people around me
- Look through the session details
- And most importantly, relax
Some of the best conversations at re:Invent don't happen during the session. They happen while everyone is waiting for the session to start.
4. Don't spend your entire day in breakout sessions
This is another mistake I made early on. Breakout sessions are great. But re has much more to offer.
Try to mix different formats.
Breakouts
Great for architecture patterns, customer stories and broader technical understanding.
Chalk Talks
These are gold if you already know the technology. You get much more interaction and can ask questions that don't fit into a standard presentation.
Workshops
If you want to actually build something, prioritize these.
Builder Sessions
Excellent when you want a more hands-on experience without committing to a long workshop.
Lightning Talks
Short, focused and easy to fit between other activities.
Expo
Don't treat the Expo as a place where you collect company stickers. There is a lot of useful technical content happening there. AWS has hundreds of partner booths and multiple community and learning areas. The 2026 agenda lists more than ~400 sponsors and booths in the Expo. Go there with questions.
5. Prepare questions before you go
This has probably given me more value than attending another ten sessions. Before re:Invent, write down five to ten problems you are currently dealing with at work.
Not generic questions. Real ones.
For example:
"How are teams controlling platform engineering costs at scale?"
"What does AWS recommend when standard automation doesn't fit a workload?"
"How are companies governing AI workloads across multiple AWS accounts?"
Now take those questions to AWS engineers, architects, partners and other customers. Suddenly re:Invent becomes a giant expert office hour and remember, the AWS booth isn't just for collecting swag. There are people there who actually work on the services you're using. Ask them something difficult.
6. Keynotes are not just announcements
Yes, the keynotes are where you hear about the big launches. But don't watch them only for the announcements. Watch for direction.
What is AWS investing in?
What problems are they trying to solve?
Which technologies are becoming strategic?
Where is the ecosystem moving?
That bigger picture is often more valuable than remembering the 47th new feature announced that morning. Also, don't underestimate the energy of being in the room when something major is announced. Watching it later on YouTube is useful. Being there is different.
7. Leave room for the unexpected
This might be the hardest advice for technical people. We love plans. re:Invent will destroy your plan. And that's okay.
Maybe you meet an AWS engineer after a session.
Maybe someone recommends a workshop you didn't know about.
Maybe you run into someone from your community.
Maybe you discover a service you had never considered.
Maybe you end up spending an hour discussing a problem with another architect over coffee.
Don't optimize every minute. Leave some white space.
Some of my favorite re memories have come from things that were never on my calendar.
8. Networking is easier than you think
You don't need a complicated networking strategy. Start with:
"Which sessions are you attending?"
That's it. You're surrounded by people who already have something in common with you.
AWS architects. Developers. Platform engineers. Security professionals. Startup founders.
CIOs. AWS Partners. Customers. Community Builders. AWS Ambassadors. AWS Heroes.
People building things at an incredible scale. Talk to them. And don't make every conversation about your job. Ask what they are building. What surprised them. What they learned. What they would do differently.
Those conversations are often more valuable than exchanging 20 LinkedIn connections.
9. The Expo and the swag: let's talk about it
Let's be honest. The swag is part of the fun. By day three, you will probably have enough T-shirts, stickers, socks, bottles, backpacks and random AWS-branded objects to open a small store.
My advice?
Don't collect everything.
You will regret carrying it. Instead, pick the things you actually like. And keep a little space in your luggage. Because somehow, no matter how disciplined you are, you will still come home with more stuff than you planned. Also remember that some conference activities and feedback mechanisms may have their own giveaways or redemption processes. AWS has historically used session evaluations and conference activities as opportunities for additional swag, although the exact approach can change year to year.
The bigger value of the Expo, though, is not the T-shirt. It's the conversations.
10. Don't underestimate food, water & sleep
This sounds boring. It isn't.
You are going to walk a lot.
You are going to eat at strange times.
You are going to stay up later than planned.
You are going to attend an evening event and then somehow convince yourself that a 7 AM session is a great idea.
It isn't. Carry water. Keep snacks with you. Wear comfortable shoes. Charge your phone whenever you get the opportunity. And sleep. You don't need to prove that you can survive on four hours of sleep just because you're at re:Invent.
The conference is five days long. Think marathon, not sprint.
11. Download everything you need before the week gets crazy
Your phone becomes your command center. The AWS Events app and event catalog are extremely useful for keeping track of sessions, schedules and event information. AWS recommends using the app for planning and navigating the event. I also recommend keeping these ready:
- Session schedule
- Hotel confirmation
- Flight details
- Conference registration details
- Important contact numbers
- Maps
- Your meeting schedule
- A note with your key questions
And keep your phone charged. A power bank is not optional.
12. Take photos, but don't experience re:Invent through your phone
This one took me a few years to learn. Take the photo. Record the keynote. Capture the ridiculous amount of AWS branding. Take the group picture. Take the photo with the giant re:Invent sign.
Then put the phone away. You don't want to return home with 800 photos and realize you barely remember what it felt like to be there. The best memories aren't always the polished ones.
Sometimes it's that random photo taken while walking between venues.
Sometimes it's the coffee conversation at 8 AM.
Sometimes it's the exhausted selfie at the end of day four.
Keep those.
13. Don't skip re:Play
You have spent five days talking about cloud architecture. You deserve one evening of not talking about cloud architecture. The 2026 re:Play party is scheduled for Thursday evening, with live music, food, games and other activities. Go. Even if parties aren't your thing, go for a while. It's part of the re:Invent experience. And yes, there will probably be another T-shirt.
14. My ideal re:Invent day
After three previous experiences, this is roughly how I like to structure my day:
Morning
One important technical session. Coffee. Another session or workshop.
Lunch
Eat properly. Have one or two meaningful conversations.
Afternoon
A mix of technical sessions and Expo. Leave some breathing room.
Late afternoon
Review notes. Meet people. Explore something unexpected.
Evening
Community event, partner event, dinner or just downtime. And some days? Skip the evening event.
Go back to the hotel. Sleep. Your future Wednesday-self will thank you.
15. The biggest mistake: trying to "complete" re:Invent
This is probably the most important lesson I can share. You cannot complete re:invent. There will always be another session you could have attended. Another announcement you missed. Another person you didn't meet. Another booth you didn't visit. Another workshop you couldn't fit in.
That's okay.
The goal isn't to consume everything. The goal is to leave Las Vegas with:
A few new ideas.
A few new relationships.
A few answers to real problems.
And a lot of energy to build something when you get back home.
That's a successful re:Invent.
My re:Invent Checklist
Before leaving for Vegas:
- Define 3-4 learning themes
- Build a realistic session schedule
- Reserve seats for your must-attend sessions
- Identify backup sessions
- Prepare 5-10 real technical questions
- Install the AWS Events app
- Plan your transportation between venues
- Carry comfortable shoes
- Carry a power bank
- Leave space in your luggage
- Keep some unscheduled time
- Plan at least a few networking conversations
- Make time for the Expo
- Attend the keynotes
- Proper Rest &Sleep
One last thing
My first re:Invent was about seeing what AWS was doing.
My second was about learning more.
My third was about connecting with people.
And going into my fourth, I think the goal is different again.
It's about connecting the dots. Taking what I learn from AWS engineers, customers, architects, partners and the community and bringing it back into the work we do every day. Because that's where the real value of re:Invent starts. Not in Las Vegas... When you get back home.
See you in Vegas. ☁️
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article