AWS Builder Center
 How We Built a Platform to Actually Connect With Our Community

How We Built a Platform to Actually Connect With Our Community

San Antonio AWS Users Group had 1,200+ Meetup members, but most were invisible no way to show their real community or escape the algorithm. So they built their own platform: real member faces, auto-synced events, a job board, no-code admin panel, and built-in security (Aikido Zen, rate limiting, PBKDF2). All built with Kiro, an AI dev environment, using AWS credits donated by a member. Now open-sourcing it for other tech communities.

Founder

The Disconnect

When I joined as co-leader of the San Antonio AWS Users Group, we had over 1,200 members on Meetup. But here's the thing: most of them were invisible. They'd join the group, maybe attend one event, and then disappear into the void.
We had no way to reach them outside of Meetup's algorithm. No way to show them what our community actually looks like. No way to say "hey, we're real people who get together and talk cloud; come hang out."
Meetup is great for RSVPs, but it's not a home. It's a listing.

What We Needed

We needed a space that felt like us. Somewhere that:
  • Shows the real faces of our community (not just event listings)
  • Makes it easy for someone new to understand what we're about in 5 seconds
  • Lets people find us through more than just Meetup search
  • Gives us a way to share job opportunities, resources, and connections
  • Doesn't require a developer to update every time something changes
We didn't want a generic WordPress template. We wanted something that actually represents a tech community: the people, the energy, the casual "no pitch decks, no name badges" vibe.


What We Built

We built a community platform from scratch. Here's what it solves:

People See People

The homepage has a scrolling carousel of real members: their photos, their names, their cities. When someone lands on our site, they don't see a corporate template. They see Caroline from San Antonio, Joe from Austin, Yogesh from the Valley. Real people.
That changes the conversation from "is this community active?" to "these are my people."


Events Just Work

Every event we create on Meetup automatically shows up on our website. Images, descriptions, workshop tags all synced. Past events become a history of what we've built together. Speakers get featured automatically from the co-host list.
I don't have to update two places. I create the event on Meetup, and the website takes care of itself.

The Job Board Creates Value

This was a big one. Members kept asking in Slack: "anyone hiring?" or "I'm looking for volunteers for my project." Now we have a dedicated job board. Job posts and volunteer opportunities live right on the site, visible to anyone who visits.
It gives members a reason to come back to the site even when there's no event coming up.

Anyone Can Manage It

I'm not a full-time developer. I don't want to SSH into a server to change the community tagline. The admin panel lets me:
  • Upload a new logo from my browser
  • Change the homepage text
  • Update social links
  • Manage speakers and sponsors
  • See contact form submissions

Everything is configurable from the browser. If tomorrow we rebrand or change our Meetup URL, I handle it in 30 seconds from the admin panel.

The Meetup Problem (and Our Workaround)

Here's something every community organizer knows: Meetup owns your relationship with your members. You can't export emails. You can't customize your page. You're at the mercy of their algorithm for visibility.
Our platform syncs from Meetup but lives independently. We own the website, the content, the branding. If Meetup changes their pricing or algorithm tomorrow, our community's public presence doesn't disappear.
The one trade-off: Meetup's API tokens expire every ~24 hours. It's annoying; I get an email, click "Reconnect" in the admin panel, and it's done in 10 seconds. The basic event sync (upcoming events) works without any token. Only the historical data and images need the reconnect.


Why It Matters for Community Building

Tech communities live and die by trust. Someone checking out your group for the first time is asking:
  • "Is this active?"
  • "Are these people like me?"
  • "Will I learn something?"
  • "Is it worth showing up?"
A Meetup page with a default banner and a list of dates doesn't answer those questions. A website that shows your members' faces, your past events, your speakers, your values that answers all of them.
We've seen the difference. People come to events and say "I saw the website, it looked like a real community, so I showed up." That's the whole point.

Security We Don't Have to Think About

One thing I didn't want to worry about as a community leader: getting hacked. We have a contact form, an admin panel, file uploads all the things that attract bots and attackers.
The platform handles this out of the box:
  • Aikido Zen: a runtime firewall that blocks SQL injection, path traversal, and SSRF attacks automatically. No configuration needed; it just runs.
  • Bot protection: the contact form uses honeypot fields and timing detection. If a submission happens faster than a human can type, it gets rejected.
  • Rate limiting: login attempts and form submissions are throttled so brute-force attacks don't work.
  • Strong password hashing: admin credentials use PBKDF2 with 600,000 iterations. Even if someone got the database, they couldn't crack the password.
  • Input validation: every API endpoint validates its input with strict schemas. You can't send garbage data and hope something breaks.
  • Security headers: Helmet sets all the headers that browsers need to prevent XSS, clickjacking, and other common attacks.
  • S3 credentials hidden: sensitive keys never appear in public API responses. Only authenticated admins can see them.
I never have to think about any of this. It's just there, protecting the site while I focus on the community.


For Other Communities

We're releasing this as open source in version 2. The idea is simple: any AWS User Group (or any tech community) can deploy this, configure it from the admin panel, connect their Meetup group, and have a professional community website running in an afternoon.
No monthly fees. No vendor lock-in. Your community, your data, your branding.
If you're a community leader spending hours on manual updates, or if your Meetup page is the only thing representing your group online, this is for you.

How We Built It

We built this entire platform using  Kiro , the AI-powered development environment. Daniel Morales, the lead of our community and an AWS Community Builder in the Security category, donated the AWS credits he received through the Community Builders program to power Kiro for the development of this project.
That means this platform was built by the community, for the community, using tools and resources that AWS provides to its builders. No agency fees, no freelancer invoices. Just a community leader with a vision, an AI development partner, and the credits to make it happen.
It's proof that community builders don't need a budget to ship real software. They need the right tools and the drive to solve their own problems.


The San Antonio AWS Users Group meets monthly to talk cloud, share projects, and help each other grow. Find us at  sanantonioaws.com  or on  Meetup .
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