1. Host a Static Portfolio Website on S3
This is the classic "hello world" of AWS. Upload an HTML/CSS site to an S3 bucket, enable static website hosting, and you have a live URL in minutes. Add CloudFront in front of it later to learn about CDNs and HTTPS.
Skills you'll learn: S3 buckets, bucket policies, static hosting, basic DNS
2. Build a Serverless "Like" Counter with Lambda + DynamoDB
Create a simple API using Lambda and API Gateway that increments a counter in DynamoDB every time it's called. Hook it up to a button on your portfolio site. It's small, but it touches four core AWS services at once.
Skills you'll learn: Lambda functions, API Gateway, DynamoDB, IAM roles
3. Automate Image Resizing with S3 Triggers
Set up an S3 bucket where uploading an image automatically triggers a Lambda function that creates a resized thumbnail and saves it to a second bucket. This is a great intro to event-driven architecture — one of the ideas that shows up constantly in real cloud jobs.
Skills you'll learn: S3 event notifications, Lambda triggers, image processing basics
4. Deploy a To-Do App with Elastic Beanstalk
If you've built a small backend app (Flask, Express, whatever you're comfortable with), deploy it using Elastic Beanstalk instead of managing EC2 instances by hand. It handles load balancing, scaling, and health checks for you, so you can focus on understanding what's happening rather than fighting infrastructure.
Skills you'll learn: Elastic Beanstalk, environment configuration, basic app deployment
5. Set Up a Personal Monitoring Dashboard with CloudWatch
Take any of the projects above and add CloudWatch alarms — for example, get notified if your Lambda function errors out or your S3 costs spike. This one doesn't feel as flashy, but understanding monitoring and alerting is exactly what separates "I deployed something once" from "I can operate something."
Skills you'll learn: CloudWatch metrics, alarms, SNS notifications
A Few Tips Before You Start
- Set a budget alert first. Before touching any project, set up AWS Budgets with an alert at $1. It takes two minutes and will save you a lot of stress.
- Tag everything. Get in the habit of tagging resources with your project name — it makes cleanup way easier later.
- Tear it down when you're done. Delete unused resources (especially anything with "always running" costs, like NAT gateways) once you've taken your screenshots for your portfolio.
- Write it up. A short README explaining what you built and why is often more impressive to recruiters than the project itself.
Loading article