AWS Builder Center

Builder Center

What We Learned Building Our First AWS Student Community Day at IUSJC

From a campus student group to nearly 300 people learning, building and connecting together.

Jerry Davis NDJANA MENGUE

Chief Operating Officer at Hinkaku | Student at IUSJC
On September 12, 2026, we organized the first AWS Student Community Day at Institut Universitaire Saint Jean du Cameroun (IUSJC), on the Eyang Campus in Cameroon.
It was the largest event our AWS Student Builder Group had organized so far.
We had:
  • 278 registered attendees
  • Approximately 300 in-person participants
  • 292 members in our Meetup community
  • 5 parallel rooms
  • 15+ sessions and community activities
But the most interesting part of the event was not the numbers.
It was discovering what happens when you stop thinking of a Student Community Day as only a conference and start designing it as a community experience.
Our theme was:
> Learning Together to Build Together.
And almost every decision we made came back to that idea.
Nearly 300 students, builders, speakers and partners came together for the first AWS Student Community Day IUSJC.

The story started before the event

Our AWS Student Builder Group was created within Institut Universitaire Saint Jean du Cameroun to give students a practical space where they could learn together, meet professionals and connect technology learning to real projects, careers and opportunities.
We did not want to build another campus club where most of the activity happens in announcements and occasional meetings.
We wanted members to move through four stages:
Learn. Build. Connect. Lead.
Over time, the community grew.
By September 2026, our Meetup group had reached 292 members.
That was when organizing a Student Community Day started to feel like the natural next step: take a community that had been growing online and on campus and give it one full day to become visible, physical and real.
The Student Builder Group grew from a campus initiative into a community of 292 Meetup members.

Lesson 1: Design the experience, not only the agenda

One of our first decisions was to avoid naming our spaces “Room 1”, “Room 2” or “Room 3”.
We had five parallel rooms, so we called them:
  • EC2
  • S3
  • Lambda
  • RDS
  • DynamoDB
It was a small decision, but it changed how the event felt.
Students were not saying:
> “My next session is in Room 4.”
They were saying:
> “I’m going to Lambda.”
The campus itself became part of the AWS experience.
For a student event, these small design decisions matter more than we expected. They create identity, make navigation memorable and help participants feel that the event is more than a list of talks.
Five rooms named after AWS services turned the campus into part of the event experience.

Lesson 2: A first edition does not have to be small

Before the event, one of our biggest uncertainties was attendance.
How many people would actually come?
We ended with 278 registrations and welcomed approximately 300 people in person.
This was especially interesting because our Meetup community had 292 members by the time of the event.
The Community Day therefore attracted not only existing community members, but also students and guests outside the immediate group.
One lesson for other Student Builder Group Leaders is simple:
Do not estimate attendance only from your active core team.
A strong campus event can reach students who may never have joined your community before.
At the same time, prepare your logistics for a number higher than your registration count.
We learned that firsthand.
278 registrations, approximately 300 in-person participants and 292 Meetup members.

Lesson 3: Technical diversity helps more people find their place

We did not want every session to look the same.
Our program included topics such as:
  • testing AWS architectures locally with FLOCI;
  • building secure and scalable MVPs;
  • Infrastructure as Code with Terraform;
  • serverless computing;
  • AI-native startups;
  • resilient cloud architecture;
  • cloud security;
  • AWS WAF;
  • AI-assisted interface development;
  • IT project management.
That mix mattered.
Some attendees were discovering AWS for the first time.
Others were already building.
Some were interested in DevOps or security.
Others were more interested in AI, startups or software engineering.
A Student Community Day does not need every participant to follow the exact same path.
It needs enough entry points for people to find something relevant to where they are.
The technical program intentionally mixed cloud, security, DevOps, AI and software engineering topics.

Lesson 4: Peer-led sessions matter too

Not all meaningful sessions need to come from external experts.
Student leaders from our own club, as well as student leaders from other campuses in Yaoundé, also participated in discussions and sessions during the day.
That mattered because students sometimes relate differently to someone who is only one or two steps ahead of them.
Professional speakers show what is possible.
Peer leaders show that it is reachable.
For us, both were necessary.
Student leaders also contributed to the program, creating peer-led spaces for exchange and learning.

Lesson 5: Games are not a distraction from community building

This is probably one of the things I would strongly recommend to another Group Leader.
We included games during the day:
  • AWS BuilderCards
  • Le Ndem
  • Ludo
  • Monopoly
At first, games can look unrelated to a cloud event.
But they solved a very real problem.
At technology events, two people can spend an entire day sitting beside each other and never speak.
Put those same people around a game and within minutes they are talking, negotiating, laughing and learning each other’s names.
Games became one of our networking tools.
The goal was not to add games simply for entertainment.
The goal was to create interaction.
Games were part of the community design: they created low-pressure spaces for participants to meet and interact.

Lesson 6: A keynote should give the event a direction

Our opening keynote came from Lisa Bagley, from AWS Community Groups.
One message stayed with us throughout the day:
> “The gap between where you are now and where you want to be does not get closed by waiting. It gets closed by starting.”
That message worked because it spoke directly to students.
Many people wait until they know enough before they build something.
But building is how you learn.
Trying, failing, debugging and trying again are not interruptions to learning.
They are the learning.
Lisa also reinforced another idea that perfectly matched the theme of the event: no meaningful product, innovation or career is built in isolation.
That became one of the strongest messages of our Community Day.
Lisa Bagley’s opening keynote set the tone: start building before you feel fully ready.

Lesson 7: Community is also what happens between sessions

Not every valuable moment happened in front of a projector.
A large part of the value came from:
  • participants speaking with speakers after sessions;
  • students meeting people from other campuses;
  • conversations with exhibitors;
  • gaming sessions;
  • informal discussions during transitions;
  • networking at the end of the day.
This is something we would protect even more in a future edition.
When planning a schedule, it is tempting to fill every minute with content.
But a packed program can accidentally remove the very thing a Community Day is supposed to create:
community.
Some of the most valuable moments happened between sessions.

Lesson 8: Five rooms create opportunities — and complexity

Five rooms allowed us to offer a lot of content.
It also created coordination challenges.
You need:
  • people responsible for each room;
  • clear room naming;
  • timekeeping;
  • speaker coordination;
  • transitions;
  • technical equipment;
  • volunteers who know where things are happening.
The more tracks you add, the more operational complexity you create.
For our next edition, we would keep the benefits of parallel sessions while paying even more attention to synchronization and movement between spaces.

Lesson 9: Collect feedback formally

We observed strong attendance, enthusiastic participation and continued networking throughout the day.
But one thing we would improve immediately is the post-event feedback process.
We did not have a standardized survey strong enough to report a precise satisfaction percentage.
That means our observations are useful, but not yet as measurable as they could be.
For the next edition, we would capture:
  • overall satisfaction;
  • session ratings;
  • favorite formats;
  • learning outcomes;
  • networking value;
  • likelihood of returning;
  • topics participants want next.
This would make the next recap much more useful for both organizers and AWS.

Lesson 10: The event should create the next event

One line from the keynote captured this perfectly:
> “Today will end, but your student builder group will not.”
That is how we now think about the first Student Community Day.
It was not the end goal.
It was a milestone.
The real question is what happens after approximately 300 people spend a day learning together.
Do they come back?
Do they build projects?
Do they earn badges and certifications?
Do they become speakers?
Do they organize the next event?
Do they mentor another student?
That is the next phase.
The event ended, but the community continues.

What I would tell another Student Builder Group Leader

If you are thinking about organizing your first Student Community Day, here are the things I would remember:
  • Start earlier than you think.
  • Design the attendee journey, not only the speaker agenda.
  • Give students ownership.
  • Create room for networking.
  • Use activities that make strangers interact.
  • Prepare for more people than expected.
  • Assign clear ownership for every room.
  • Capture feedback from day one.
  • Do not build the event alone.
A Community Day should itself demonstrate what community means.

What comes next

Our first AWS Student Community Day transformed a growing campus initiative into a physical community of nearly 300 people learning, networking and building together.
Now the responsibility is to turn one successful day into a repeatable rhythm.
More workshops.
More student-led sessions.
More projects.
More builders.
Our theme remains the same:
> Learning Together to Build Together.
Because the most important outcome of a community is not the event it organizes.
It is what its members go on to build together.
About the community
AWS Student Builder Group IUSJC
Institut Universitaire Saint Jean du Cameroun
Cameroon
# aws-student-builders-groups# aws-community# aws-community-day-2026# aws-community-day-recaps# students
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article