
Weekend Creative Challenge: AWS User Group Piura Giveaway Website
I built an interactive game-show experience for live tech events. Attendees scan a projected QR code to join in real time, and their names appear on an animated spinning wheel rendered with canvas physics. Hit "Spin" and the whole room watches it slow down. It's part interactive toy, part roulette game that makes people smile. Built entirely with Kiro on a serverless stack: S3, CloudFront, API Gateway, Lambda, DynamoDB, and Route 53, all provisioned with Terraform. Every spin is a moment of fun.
Weekend Creative Challenge: AWS User Group Piura Giveaway Website
Vision & What the App Does
I built an interactive game-show experience for live tech community events. It's a serverless web app that turns the boring "let me pick a random name from a spreadsheet" moment into a playful, animated spectacle that makes an entire room smile.
During the past year I've been actively attending AWS Community events across Peru. These are great events with opportunities to network and interact with other professionals. At the end of most events, it's really common to have giveaways for merch, swag, or AWS credits. But every single event I attended had the same frustrating problem.
When organizers tried to use a "random name picker" website, they pulled the full list of people registered on Meetup.com. The issue? Only 20–30% of those people actually attended. So when they had 10 items to give away, the result was always the same: again and again and again, the selected "winner" hadn't shown up. The atmosphere would shift from exciting to boring in seconds. I always thought, "Why not just show a QR code so actual attendees can register on the spot, and then use that accurate list for the giveaway?" But by then it was always too late.
So when I started the AWS User Group Piura in Peru, that frustrating moment was NOT going to happen on my watch. I learned from those mistakes.
I built a serverless single-page application that reimagines giveaways as interactive play. Attendees scan a giant QR code projected on-screen and instantly join the game. Their names appear on a colorful, canvas-rendered spinning wheel in real time, like a game-show roulette. The presenter hits "Spin," the wheel accelerates with realistic physics, slows with exponential friction decay, and the room erupts when it lands on a winner. It's part interactive toy, part crowd participation game, designed to generate excitement, laughter, and genuine surprise every single time it's used.
How I Built It
My specialty is DevOps and Cloud Infrastructure, not frontend development. So I used Kiro to build this entire web app. I provided all the specifications upfront:
- Completely serverless architecture
- Frontend hosted on Amazon S3 as a static single-page application
- Participant data stored in DynamoDB (NoSQL)
- All backend logic running on AWS Lambda
- API routing through API Gateway
- CloudFront as CDN
- Custom domain hosted in AWS via Route 53
I also specified the user experience I wanted: a roulette wheel that updates in real time as new participants register, an admin panel to create/open/close/delete raffles, and a simple registration form so attendees can sign up effortlessly.
Thanks to Kiro, I didn't face any blocking challenges during the initial build. However, after testing the app at a couple of real events, I iterated on several improvements:
- Spin performance: I noticed the roulette took too long to spin and pick a winner when the internet connection was poor. I troubleshot the issue with Kiro and optimized the spin animation to use client-side physics with exponential friction decay, so it no longer depends on network speed once participants are loaded.
- Multi-raffle support: I realized other Peruvian tech communities could use this tool, so it needed to host multiple independent raffles simultaneously. I implemented that feature with Kiro, adding full CRUD for raffle management.
- Giant QR overlay: I added a full-screen QR button so I can display it in front of everyone on the projector, making it dead simple for attendees to scan and register.
- Easter egg: Just for fun, I added a little Kiro ghost floating across the bottom of the page. Click on it!
AWS Services Used / Architecture Overview
The entire stack is serverless: pay-per-use pricing, no servers to manage, and everything fits within the AWS Free Tier.
AWS Service | Purpose |
|---|---|
Route 53 | DNS for awsugpiura.com (domain bought on Namecheap, fully delegated to AWS) |
CloudFront | CDN in front of S3, TLS termination |
Amazon S3 | Static frontend SPA hosting (private bucket, OAC access) |
API Gateway | REST API routing with CORS |
AWS Lambda | Backend business logic (Node.js 20) |
DynamoDB | NoSQL storage, two tables: raffles and participants |
ACM | TLS certificate for the custom domain |
IAM | Lambda execution role with least-privilege permissions |
CloudWatch Logs | Lambda execution logging |
Architecture Diagram

Users → Route 53 (DNS) → CloudFront (CDN + TLS) → S3 (Frontend SPA) │ config.json (API URL) │ ▼ API Gateway (REST) │ AWS_PROXY │ ▼ Lambda (Node.js 20) │ │ ▼ ▼ DynamoDB DynamoDB (sorteos) (participantes)The frontend loads a
config.json file from S3 that contains the API Gateway URL (injected at deploy time by Terraform). The browser then makes direct HTTPS calls to the API Gateway endpoint. All infrastructure is provisioned with Terraform, so a single terraform apply builds and deploys everything.For a more detailed architecture breakdown including data flows, DynamoDB schemas, and IAM policies, check out the project repository documentation .
What I Learned
This was the first web application I developed using Kiro, and I genuinely enjoyed the experience. I'm getting better at prompting and iterating with Kiro. It feels like pair-programming with someone who never gets tired.
I was already comfortable with the AWS serverless suite of services, and this project only reinforced my conviction: serverless is the way. I'm not paying anything when the app isn't being used, I have no servers to manage, and deployments are a single command. It just works.
Some next steps I'm considering:
- Improved security: The admin panel is currently secured with a shared key. Implementing authentication via Amazon Cognito would be a proper upgrade.
- Winner exclusion: Past winners in a specific raffle should be excluded from subsequent spins in the same event, so the same person can't win twice.
- Analytics: Track participation trends across events to better understand community engagement.
Link to App or Repo
The app's interface is entirely in Spanish since it was built for Peruvian tech community events where all attendees are Spanish speakers. Feel free to explore it, the UX is intuitive enough to navigate regardless of language.
- Live app: https://awsugpiura.com/sorteo

Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article