How ACD Bengaluru Became a Pan-India Homecoming

For the past few months, our lives as organizers of AWS Community Day Bengaluru were a mix of spreadsheets, speaker calls, venue checks, and late-night syncs. Now that the event is over and the dust has settled, I realise this wasn't just a Bengaluru event. It had the heartbeat of an AWS Community Day India.

It reminded me of my early days volunteering for AWS Community Day India 2022 and AWS Community Day Asia 2021, which we ran during the Covid pandemic. Back then, people didn't travel — they couldn't — but people from every corner of the country still contributed, just virtually. Same question then as now: "How can I help?"

In the corporate world, we measure value with metrics and KPIs. In a community, that logic doesn't work. You can't judge someone's contribution by how much time they gave. Someone gave one minute, someone gave their entire day — both mattered the same. It's driven by intent, not volume.

This event was proof of that. Below are the people and the stories that made it happen.

The Network Across Borders

We had a strong group of User Group leaders, Community Builders, and tech advocates from across India step up:

• Yeshwanth (UG Leader, Mysuru) brought regional momentum, and Shubham Singh (UG Leader, Wipro) bridged the gap between enterprise and community.

• Adit Modi (UG Leader, Vadodara, Golden Jacket holder) brought his experience running many events.

• Omshree, an AWS Community Builder, part of AWS User Group Women India, and a Golden Jacket holder.

• Shashank, an ex-AWS Solutions Architect who now leads the Indore UG, added real technical depth to our planning.

• Vivek Raja (UG Leader, Madurai) couldn't join in person because of work commitments, but kept guiding us from behind the scenes. Logesh Poobalan carried the Madurai flag on the ground.

• Ramya, an AWS Community Builder, part of AWS User Group Women India, and a long-time part of the Bengaluru UG, came back and stood by the team despite going through a tough personal time.

• Sri Hari, who volunteers across the Mumbai and Nashik UGs, showed that city lines don't matter when the passion is the same.

• Godhuli Das, from Kolkata and part of AWS UG Kolkata, who emceed last year's AWS Community Day Kolkata, came back again as a UG volunteer to help out.

This is the group that carried the event. Everything below is what they built.

Where It Started — Two Hours in a Cafe

The whole thing started with a cafe conversation after a meetup, with Jones. We sat for close to two hours, talking about what we could do differently this year. We recorded voice notes so we wouldn't lose the ideas.

In the next round of discussion, we got more specific: which activities do we actually run, and who owns each one? That second question mattered more than people think. An idea without an owner doesn't happen. So for every activity we finalised, we made sure there was one person or one small team responsible for it. That's the thread running through everything that follows.

The CFP That Set the Bar

When we opened the call for papers, we were clear on one thing: we didn't want the usual product-demo, happy-path talks. We wanted real experiences — including failures, including what people learned while building. Less AI-hype, more actual data and architecture thinking.

We got over 120 submissions. Going through them was hard on the team — shortlisting, waitlisting, following up with speakers, and in some cases reworking topics with them. I had already told my audience we'd deliver a strong lineup, so there was no room to fall short.

By the end, the feedback we heard from attendees was that the sessions were well curated, no matter which one they walked into. During the event, I didn't have one fixed responsibility, so I spent a lot of time walking around asking people directly: what session are you in, how did you find the Architecture Clinic, did you check out the Open Mic, how's the sponsor area, did you look at the job board. That's partly how I know what worked.

We also ran a pre-event workshop day on the 10th at the Amazon office. It went well — attendees liked every workshop we ran.

One small fun addition: Srushith came up with a "FOMO score" idea — a way for attendees to check how much they were missing out on, based on which sessions and workshops they'd actually attended.

Breaking the Mold: Podium vs. Round Table

When we sat down to plan the tracks, we had a choice — do the usual back-to-back stage presentations, or try something different.

Bengaluru runs on early-stage builders and people shipping fast. They don't just want to sit and listen. They want to talk through real, messy architecture. So we added a Round Table Track, run boardroom-style, no slides allowed. Just engineers sitting around a table, notes in hand, talking openly about what's actually breaking in their systems.

It wasn't an easy yes at first. Shubham had a lot of valid questions — how do we get people to walk into a closed room and talk openly about their production problems? I told him: you know the level you're operating at, come up with the options, and we'll figure out the rest together.

Even up to the last day, Shubham and Yeshwanth were unsure how it would land — running a closed-door boardroom format at a large event isn't simple. I told them: believe in yourselves, I know you'll make it work, and we'll find the answers together.

They did. Shubham, Yeshwanth, and Abhishek nailed the format. The room had real energy, the conversations were honest, and sponsors loved what they saw.

The Architecture Clinic

This one goes back to a JS Lovers meetup organised by Smile Gupta. I saw a tweet with photos from that meetup and got the idea from there — bring people's real architecture problems to a whiteboard and have a discussion around them.

I'd wanted to try this for AWS Community Bengaluru before, but never had the right setup. This time, because we booked NIMHANS Convention Centre, we had the space to run multiple activities at once, so it finally fit. And to be clear, this is a separate activity from the Round Table — the Round Table was discussion with notes, no whiteboard; the Architecture Clinic is where the whiteboard actually came in.

The idea was simple: "show me your architecture." People bring their problem or their solution, and someone from the community or from AWS sits with them and works through it. My own view on this — there's no right or wrong in architecture, it's about how you build based on the information you have at the time.

We couldn't run this ourselves as organisers, so we handed it to Adit, Shashank, and — on their recommendation — Prabhu, who works closely with customers at AWS and who I'd only known through LinkedIn before this.

The three of them designed the format on their own. They wanted a scoring rubric and a small giveaway for people who did well. I wasn't convinced at first, but they made the case and I agreed. I had also pictured it as more whiteboard-heavy than what they ran, but they pushed back and ran it their way. It worked. People loved being back at a whiteboard, debating a real problem with someone who knew the space. We have good photos from that room.

The Open Mic Almost Nobody Saw Coming

Early on, we were just discussing how to make it work — while the rest of the team was already stretched thin on other logistics.

We decided to give full ownership to Omshree. She's an AWS Community Builder, a Golden Jacket holder, and part of AWS User Group Women India. Getting six speakers wasn't simple — some came from people who'd been turned down for the main track, and some came in through the registration form itself, where we'd asked attendees if they had something to share, so they'd get a shot too. That mix made shortlisting one of the harder jobs of the whole event, and she got it done.

The original plan was to keep it a true impromptu open mic — no lineup, just show up and speak. But once we looked at it closely, we realised that wasn't logistically workable for an event this size, so we moved to a curated set of speakers instead.

Then came the venue problem. The Open Mic room was upstairs on the first floor, tucked away, nothing pulling people toward it. She was worried no one would show up. I told her: believe in the concept, go talk to people directly, let them know something is happening in that room.

She did exactly that. When she came back, she told us — we nailed it, we had great traction, good conversations, and both attendees and speakers were happy with the format.

The Ones That Didn't Make It

Not everything we planned made it to the final event. Two ideas we discussed early on:

• An AWS Builder card game

• A DeepRacer track, which we'd planned to run with an ML-focused group

Both got dropped because of logistics and lack of organisational support at the time. They're both still on our list — we want to try them next year.

The Volunteer Who Found His Spot Last Minute

Ashutosh Jha, a software engineer and someone who's always been active in the community, had shown interest in volunteering early on. The problem was, by that point most of the ground-level roles were already settled, so I wasn't sure where to place him.

Then, last minute, one of our MCs dropped out. Ashutosh said he'd done MC work at a few meetups before and was happy to step in. That's how he landed the role — and he did a genuinely good job with it.

Whatever It Took, Whoever Was Free

AJ, Bhuvana, Jones, Srushith, and I divided up the work between us as core organisers. But that division was never rigid — everyone kept filling gaps wherever they showed up, because as organisers our job was to make sure things ran smoother, whoever's job it technically was.

Bhuvana is a good example. She recommended a food vendor — a friend of hers — whose food is genuinely good. We'd used the same vendor back at ACD Bengaluru 2024, and this time, thanks to her, we got the chance to bring them back. Attendees loved the food.

Even though everyone had their own role to play, NIMHANS gave us less support from the venue side than a hotel would have. So people ended up doing things outside their job whenever it was needed — down to small stuff like getting housekeeping to refill handwash or tissues in the washrooms, and sometimes just doing it ourselves when there was no one else to ask.

One partner who never wavered through all of this was Konfhub, Hari and Ganesh, our ticketing and community partner. They handled every bit of the approval process for us, start to finish, without us having to worry about it. They've been a steady pillar for AWS UG Bengaluru for a long time now.

The Night the LAN Cables Saved the Stream

Booking NIMHANS Convention Centre was cheaper than a hotel venue, but it meant we had to own a lot more of the logistics ourselves.

One of those was internet. The venue's own Wi-Fi had low bandwidth and wasn't reliable. We arranged a backup Wi-Fi vendor, but the vendor didn't supply LAN cables. Arjun, one of our volunteers, had prior experience volunteering with PyCon India and already knew NIMHANS Convention Centre well — what worked there and what didn't — and that experience helped a lot. He managed to source cable at the last minute, and he, along with AJ and a few others, stayed up through the night doing the crimping and setup themselves, just to get a working backup connection to the audio rooms.

It worked. This is one of the parts of the event most people never saw, and I want to make sure it doesn't go unnoticed — because without that, some part of the event would have been affected.

The Swag That Almost Didn't Make It

This time, we made a call to cut down on plastic and packaged-bottle waste. Instead of the usual swag, we decided to give everyone a reusable bottle at the entrance.

The plan was for the swag to arrive at the venue a day early. Instead, we found out it hadn't reached — the courier had made it to the city, but not to NIMHANS. So we tracked down the courier, arranged a van, and went and loaded all the swag cartons ourselves to get them to the venue in time.

The bigger lesson from this, and something I'd tell any community organiser: on the actual event day, don't lock yourself into one task. Keep yourself free. You don't know where you'll be needed — talking to someone, chasing an approval, handing off a Wi-Fi issue, solving a logistics problem nobody saw coming. Your job on the day is to be ready to fill whatever gap shows up, not to own one fixed thing.

More People Who Made It Happen

A few more shoutouts that deserve their own mention.

Poobalan built and maintained our event website, and he did a genuinely great job, two years running. He kept iterating — new ways to showcase things, new ideas — even when it meant a lot of back and forth, and he never once said no to a request. On top of that, he also managed our social media posts on the actual event day.

Monish and Logesh put in real work on our social media graphics and content, whatever way it was needed.

And a number of other volunteers showed up for us on event day and in the run-up to it: Ansh Mishra, G Monish Reddy, Masum Anand, Shaik Dadapeer, Shaik Mohammed Gouse, Sharvesh P G, Smile Gupta, Veerasolaiyappan, Aishwarya J.A, Vidhyadharan, and Parv Agarwal. Thank you, all of you.

The Support Nobody Sees

I'd committed the whole of event day to this, and I'd already talked it through with my wife, Trupti, who's always backed me whenever the community needed my time. But that same weekend, my wife's grandfather was turning 94, and the family had planned to go to the village for it. I told her I'd try to make it too, and figured my team could manage without me for a bit. She said no — you're needed there, we'll handle this side. She and my son, Advit, went without me.

That's the part people don't see when they look at an event like this. Doing community work, or really anything like this, needs a strong support system behind you — someone managing the rest of life so you can show up fully for this. For me, that's Trupti and Advit. I couldn't do any of this without them.

Closing

Every part of this event had a challenge behind it. A closed-door format nobody was sure would work. A room tucked away where nobody would think to go. A first-time activity with no template to follow. A Wi-Fi problem solved at 2 a.m. with a crimping tool.

None of it happened because one person planned it perfectly. It happened because we handed ownership to the right people, and they showed up — whether that was one hour of their time or an entire sleepless night.

That's what I mean when I say this event carried the heartbeat of the community. People from across India, some of whom couldn't even be there in person, helped make this happen. To everyone who contributed — whatever the size of it — thank you. This is your story as much as it is mine.

We're already thinking about next year, including the ideas we didn't get to this time. See you at the next one.