Inspiration
We built cool full stack apps, but when it came to deploying them... let's just say even Pikachu short-circuited. So we decided to demystify AWS and help fellow devs deploy without rage-quitting or summoning dark jutsu.
What it does
This guide walks you through deploying a full stack app (frontend + backend + database) on AWS using EC2, RDS, and S3—with humor, anime references, and cat/dog-approved explanations. 😺🐶☁️
How we built it
We: Set up an EC2 instance (aka our cloud ninja base) Installed backend/frontend tools Connected to RDS for database magic Used S3 to store static assets (and memes) Configured Nginx as our reverse proxy sensei Secured it all for battle in the real world!
Challenges we ran into
Wrangling EC2 firewalls felt like herding Meowths. Setting up RDS access securely took more retries than a Pokémon gym battle. Nginx configs? Let's just say it summoned some Itachi-level illusions at first.
Accomplishments that we're proud of
We built and deployed a full app on AWS—all by ourselves! Managed to make cloud architecture fun and beginner-friendly. Our pets finally stopped judging us... kinda.
What we learned
AWS isn't as scary as it looks (unless you're on a billing spree). EC2 + RDS + S3 = a simple, powerful full stack combo. Humor helps make cloud concepts way more digestible.
What's next for Deploying full stack app on AWS
Automate deployments with GitHub Actions (because we're lazy smart). Add Route 53 + HTTPS for pro-level polish. Explore serverless with Lambda (Ultra Instinct mode). Maybe… create a Deploying on AWS: The Anime?
Log in or sign up for Devpost to join the conversation.