Second Time at AWS re:Invent: Here's What I'm Doing Differently

Attending AWS re:Invent for the first time can be an overwhelming yet exciting experience. Last year was my first time attending the conference, and while I walked away with tons of great knowledge, I also learned some valuable lessons on how to survive and thrive during re:Invent week. As I gear up for my second re:Invent this year, I’m taking those lessons with me and making some adjustments to ensure I get even more out of the event.

If you’re attending AWS re:Invent for the first time (or even the second time), here’s what I learned and how I’m planning to maximize my experience this year.

1. Comfortable Shoes (and Durable Clothes) are Non-Negotiable

Last year, I made the mistake of bringing only one pair of shoes—my Yeezy 450s—which, while stylish, were NOT the best choice for a conference that requires a ton of walking. By the end of each day, my feet were killing me. I wish I had brought my trusty Asics instead. And, as a proud member of the thick thighs gang, I also learned the hard way that wearing thin tights wasn’t the best idea. I wore a different pair each day and managed to rub holes into every single one by the end of the week. Walking all day, every day really does take a toll!

Plan for This Year:

This time, I’m bringing shoes that are built for comfort and support. AWS re:Invent involves an immense amount of walking across large venues all day, every day. Make sure you bring a pair of shoes you can wear comfortably for hours—your feet will thank you. And for my fellow thick thighs gang members, avoid thin tights! Go for sturdier leggings or pants to prevent chafing and wardrobe malfunctions. Trust me, you’ll want to be comfortable and ready for the long days ahead.

2. Syncing with Content Creators Ahead of Time

Lesson from Last Year:

I found it tough to sync up with fellow content creators on the fly last year. By the time I’d catch their Twitter updates about where they were (or see their DMs to me), I’d already be locked into a session or far away from their location. Plus, the cell phone signal can be terrible at large conferences like re:Invent, with messages often lagging or not coming through in time.

Plan for This Year:

This year, I’m planning ahead. I’m reaching out early to those I already have a rapport with, scheduling meetups ahead of time. For creators I don’t know personally but would love to meet, I’ve created a Twitter list of those attending re:Invent this year.

Many content creators post real-time updates on where they’ll be (like specific sessions, booths, or networking events) so that people can meet up with them and chat. By keeping an eye on this list, I can quickly see their posts and head over to those spots when they make themselves available for meetups—without missing out on important sessions I’ve booked. Planning ahead will allow for more meaningful interactions, which is key for networking at re:Invent.

3. Arrive the Day Before in the Morning

Lesson from Last Year:

I made the mistake of flying in the night before the conference last year, and it was chaos. As I made my way to the Uber pickup area at the airport, I found out that the badge machines at the airport were down. The re:Invent staff on-site were super friendly and helpful, informing everyone that the airport badge machines weren’t working and directing us to several other locations around Vegas where we could pick up our badges.

After waiting a long time for my Uber—along with tons of other just-arrived conference goers—I finally made it to my hotel to drop off my stuff. Since it was my first time in Vegas, I then had to figure out the nearest badge location (before it closed for the day). I ended up heading to the MGM Grand, but got dropped off at the hotel’s main entrance instead of the MGM Grand Conference Center, which made what should’ve been a quick 8-minute walk into a 20+ minute maze through the casino. Thankfully, re:Invent was well-staffed, and I appreciated how many staff members were stationed throughout MGM to guide people to the badge station—especially for folks like me who ended up on the wrong side. (I even have video of this!)

Plan for This Year:

This time, I’m flying in the morning before the conference. I’ll have time to grab my badge without the rush and crowds (hopefully), settle into my hotel, and maybe even explore a bit of Vegas. By arriving earlier, I can avoid last-minute chaos, long lines, and the frustration of figuring out badge locations while juggling everything else.

4. Don’t Overbook Sessions—Be Selective

Lesson from Last Year:

I tried to attend too many sessions last year and ended up exhausted, constantly racing across venues. I quickly learned it’s impossible to attend "all the things."

Plan for This Year:

This year, I’ve learned to be more selective. I didn’t rush to book my sessions right when the catalog opened. Instead, I focused on filtering for hands-on learning sessions that align with my current role and interests, which are heavily DevOps-focused. My goal is to walk away with skills I can use immediately at work, specifically around AWS Terraforming, monitoring and observability, and better understanding ECS.

I filtered for breakout sessions, workshops, builder sessions, gamified learning, and interactive training in DevOps-related topics. I’ve also made sure to add an AI hands-on learning session, as I’m looking to explore how to incorporate AI into my DevOps work. This way, I’ll leave with new ideas I can implement as soon as I’m back at work.

5. Explore Vegas—It’s More than Just the Conference

Lesson from Last Year:

I was so focused on the conference that I didn’t get to explore Vegas at all! I missed out on seeing what the city has to offer.

Plan for This Year:

This year, I’m making time to enjoy the city. By flying in a day or two early, I’ll have a chance to explore before the conference kicks into high gear. Whether it's checking out a few local spots or just taking in the sights, I’m planning to experience more than just the conference.

6. Rest and Recharge—Don’t Burn Out

Lesson from Last Year:

re:Invent is mentally and physically draining. Between navigating huge crowds, attending sessions, and networking, I underestimated how much energy it would take.

Plan for This Year:

This time, I’m prioritizing breaks and downtime. I plan to head back to my hotel during the day for short breaks to recharge—maybe even take a nap. I’ll stay hydrated, eat regularly, and make sure I’m well-rested so I can fully enjoy the conference without burning out. Having fam with me this year will help with balancing work and relaxation.

7. Have a Plan—Set Clear Goals for the Conference

Lesson from Last Year:

Last year, I didn’t have a solid plan beyond attending sessions, and that left me feeling a bit scattered.

Plan for This Year:

This year, I’m going in with clear goals. My plan is to focus on specific learning outcomes, particularly around DevOps, so I can bring valuable knowledge back to my team. I’ve created a "north star" for what I want to achieve at the conference: gaining skills I can immediately use on my current project and introducing new ideas to my team. Having this focus will keep me on track and help me maximize my time at re:Invent.

Conclusion:

AWS re:Invent is a massive event, and it can be overwhelming, especially for first-time attendees. However, with a bit of planning, comfortable shoes, and clear goals, you can make the most out of the experience. I’m looking forward to my second re:Invent and putting these lessons into practice.

If you’re heading to re:Invent this year, what’s your plan? Share your tips or lessons learned in the comments below!

Stay tuned for more!

After the conference, I’ll be sharing my reflections and lessons learned, including how well my new strategy worked, any unexpected surprises, and additional tips for future re:Invent attendees. I’ll also be diving deeper into some of the sessions and hands-on learning experiences that I’m most excited about. Be sure to follow along for more content after re:Invent!