The Application I Almost Didn't Submit

Before we begin: When this story started, the program was called AWS Cloud Clubs. Today, it's known as AWS Student Builder Groups (AWS SBGs). The name has evolved, but the purpose remains the same: to help students learn, build, lead, and create meaningful communities together. Since this journey began as an AWS Cloud Club, I'll use that name when talking about those early moments.

If you had asked me six months ago whether I'd be leading a student tech community, organizing events, speaking in front of students, and writing about the experience, I probably would have laughed and said,

Ironically, that's almost exactly how this journey started.

During my semester vacation, someone I knew sent me the AWS Cloud Clubs leader application and said,

Naturally, I said no.

Not because it wasn't a good opportunity, but because I was perfectly comfortable staying within my comfort zone. Leadership sounded like responsibility. Responsibility sounded like pressure. And as someone who prefers observing over being in the spotlight, I wasn't exactly looking for either.

But they didn't take no for an answer.

After a few conversations and a fair amount of convincing, I finally gave in and opened the application just to "take a look."

That small decision changed everything.

As I filled out the form, I came across a faculty verification requirement. Since I was away from campus, I reached out through a senior who helped connect me with a faculty member willing to support me.

That led to a phone call I still remember.

He said yes.

At the time, it felt like a simple request.

Looking back, it was the first domino.

A few weeks later, I received the selection email: I had become an AWS Cloud Captain.

And honestly, I don't think I fully understood what that meant yet.

I knew I wanted to learn more about cloud computing, connect with like-minded students, and explore opportunities beyond the classroom. What I didn't realize was that the role would challenge me far beyond technology.

For years, I've consistently tested as an INFP, which explains more than I used to admit.

I've always preferred learning quietly, building things in the background, and staying out of the spotlight. Public speaking wasn't just uncomfortable; it was something I actively avoided.

But leadership has a way of challenging the versions of ourselves we are most comfortable with.

Slowly, I realized leadership wasn't just about organizing events or managing a team. It was about communication. It was about presence. It was about making people feel included in something bigger than themselves.

And that meant I couldn't stay hidden behind comfort forever.

Somewhere along the way, I also became the first woman AWS Cloud Captain in Sri Lanka. It wasn't something I set out to be, but it became a quiet reminder that representation matters more than we sometimes realize. Sometimes, simply showing up can help someone else believe they belong.

As I grew into the role, another realization hit me: leadership and communication are inseparable.

The more involved I became, the more I found myself in situations I would have once avoided: speaking in front of students, introducing speakers, representing the community.

Instead of avoiding it, I made a different choice this time.

I decided to learn it.

That mindset led me to apply for AWS New Voices 2026, a global program designed to help student leaders develop communication skills, share their journeys, and amplify stories around cloud and technology.

The irony isn't lost on me.

The person who used to avoid public speaking at all costs voluntarily applied for a program built around finding your voice.

And somehow, I got selected.

That experience became a turning point not because it changed who I was, but because it taught me I didn't need to be "ready" to start speaking. I just needed to start.

While all of this was unfolding personally, something bigger was happening around us.

At first, it looked like a rebrand.

But in reality, it reflected a shift in mindset.

Students weren't just learning anymore; they were building.

And I realized that it described my own journey too.

I wasn't just learning anymore.

I was building confidence.
Building skills.
Building connections.
And eventually, building something real.

That "something real" became our university community.

And that's when things got interesting.

Because building a community isn't just ideas and excitement, it's paperwork, approvals, meetings, and more approvals.

Lots of them.

There were days that felt less like leadership and more like walking between offices under the Vavuniya sun carrying documents that always needed "one more signature."

My Vice Captain knows exactly what I mean.

If community building had a fitness plan, we definitely completed it.

One of the biggest lessons I've learned is that communities are never built alone.

They're built by people who choose to believe in an idea.

From the beginning, our club advisor supported the vision and guided us through every challenge. His encouragement often made the difference between hesitation and progress.

My core team turned ideas into execution. Behind every event were planning sessions, problem-solving discussions, and last-minute adjustments that most people never see.

And then there was our Group Manager, who supported us throughout the transition from AWS Cloud Clubs to AWS Student Builder Groups, always ensuring we had direction when things felt uncertain.

None of this would have been possible without the AWS Student Builder Groups team, who continue to create opportunities for students around the world to learn, build, and lead.

All of it came together at the inaugural AWS Student Builder Group event at the University of Vavuniya.

Standing in that room and seeing students gathered under something that didn't exist a few months earlier felt surreal.

For a moment, everything slowed down.

The message I almost ignored.
The application I almost didn't submit.
The phone call.
The approvals.
The uncertainty.
The growth.

It all led here.

And that's when it felt real.

Not because we hosted an event.

But because a community had finally begun.

When I look back, it's still surprising how something so small as a message and an application I almost ignored became something so meaningful.

Since then, I've stepped into roles I never imagined, helped build a student community from scratch, witnessed AWS Cloud Clubs evolve into AWS Student Builder Groups, and even found myself in opportunities like AWS New Voices that once felt out of reach.

But none of these feels like an ending.

They feel like a starting point.

Because the inaugural meetup wasn't the conclusion of anything.

There are still students to reach, events to create, ideas to explore, and a community still taking shape.

And personally, there are still many comfort zones left to step out of.

If this journey has taught me anything, it's this:

For now, we're only getting started. ☁️💜