Some AWS portfolio projects look good in a README but do not teach much about
production infrastructure.
The better projects force you to answer practical questions:
- What can break?
- What costs money every month?
- Who can access it?
- How would I monitor it?
- How would I safely remove it later?
Here are project ideas that teach those habits.
Disclosure: Some links may be affiliate links. I only include resources that fit
the topic.
1. Cloud Bill Cleanup Report
Build or run a read-only scanner that finds common wasted AWS resources:
- unattached EBS volumes
- old snapshots
- unused Elastic IPs
- idle NAT gateways
- forgotten load balancers
This is a strong portfolio project because it connects AWS APIs, IAM,
CloudWatch, regions, and cost awareness.
I built a small tool for this:
Paid starter bundle:
https://basilian1.gumroad.com/l/aws-waste-finder?utm_source=devto&utm_medium=post&utm_campaign=product2_portfolio_projects
The key lesson is not "delete everything." The key lesson is learning how to
verify ownership, dependencies, traffic, backups, and rollback risk before
removing anything.
2. Cloud Resume Challenge
The Cloud Resume Challenge is still useful because it combines many real AWS
pieces into one small product:
- static hosting
- DNS
- HTTPS
- Lambda or serverless logic
- a database
- CI/CD
- IAM permissions
The important part is finishing the loop: deploy it, document it, and explain
what could cost money if it was left running.
3. Read-Only IAM Role for Automation
Create a role that allows inspection but not cleanup.
Then document:
- which APIs are allowed
- which APIs are intentionally denied
- how to test the role
- how CloudTrail records the activity
This project is small, but it shows mature judgment. A lot of real automation
should start read-only.
4. NAT Gateway Dependency Map
NAT gateways are expensive enough to be worth understanding.
Build a script or diagram that maps:
- NAT gateways
- subnets
- route tables
- private workloads
- CloudWatch traffic
Then explain how you would decide whether a NAT gateway is safe to remove.
This teaches VPC routing better than most abstract tutorials.
5. Snapshot Retention Cleaner
Create a report that lists old EBS snapshots and groups them by owner, age, and
likely purpose.
Do not auto-delete them at first.
A good portfolio version includes:
- age buckets
- volume references
- AMI references
- owner tags
- a manual approval checklist
Storage cleanup is easy to automate badly. Showing the safety checks matters.
What Makes These Projects Better
The best AWS portfolio projects do not just prove you can create cloud
resources. They prove you can operate them.
For each project, add a short section to the README:
- Monthly cost estimate
- Security model
- Failure modes
- Cleanup steps
- What you would monitor
That turns a toy project into evidence of real infrastructure thinking.
Final Thought
If you want AWS projects that teach production habits, start with the bill,
permissions, and cleanup path.
Every useful cloud system has a lifecycle: create it, run it, observe it, pay
for it, and eventually remove it safely.
Top comments (0)