Stop Learning AWS Randomly: A 30-Day Roadmap for Complete Beginners
Overwhelmed by hundreds of AWS services? This post gives you a simple 4-week learning order, from IAM and S3 to Lambda and DynamoDB, with a mini project each week so you build real skills instead of just watching tutorials.
AWS has hundreds of services, and beginners often burn out trying to learn them all. This roadmap fixes that with a simple order where each week builds on the last. It takes about 1 to 2 hours a day.
The plan at a glance
| Week | Focus | Services | Mini project |
|---|---|---|---|
| 1 | Safety and basics | IAM, Budgets | Sign in as a limited IAM user |
| 2 | Storage and compute | S3, EC2 | Host a one-page site on S3 |
| 3 | Serverless and data | Lambda, API Gateway, DynamoDB | A tiny notes API |
| 4 | Combine and publish | CloudWatch | Write up your project |
Week 1: Get safe and learn the basics
Goal: Set up your account properly and understand how AWS is organized.
Learn
- Regions, Availability Zones, and the shared responsibility model
- IAM: users, groups, roles, and policies
Do
- Turn on MFA for the root user
- Create a budget alert
- Create a limited IAM user and sign in with it
Watch out: Don’t use the root user for daily work.
Week 2: Storage and compute
Goal: Store files and run something.
Learn
- S3: buckets, objects, and public vs. private access
- EC2: launching, connecting to, and stopping a virtual server
Do
- Host a simple static website on S3
- Launch a small EC2 instance, connect, then terminate it
Watch out: A stopped EC2 instance still bills for its attached storage, so delete what you don’t need.
Week 3: Serverless and databases
Goal: Run code without managing servers, and store data.
Learn
- Lambda: functions and event triggers
- API Gateway: putting an HTTP endpoint in front of a function
- DynamoDB: tables, keys, and simple reads and writes
Do
- Build a tiny API that saves and returns a note
Watch out: Keep permissions narrow, so give your Lambda role only the access it needs.
Week 4: Put it together and prove it
Goal: Turn what you learned into something you can show.
Learn
- CloudWatch: reading logs and spotting errors
Do
- Combine your earlier pieces into one small project
- Draw the architecture
- Delete every resource you created
- Publish a short write-up of what you built and what broke
Watch out: Skipping cleanup is the most common way beginners get surprise bills.
Habits that make it work
- Build, don’t just watch. End every topic with something you made.
- Clean up the same day. Delete resources when you finish a lab.
- Use official docs and free training. Check the current Free Tier terms for your account, since they change.
- Go deep on one path before branching out.
After 30 days: pick a direction
| If you like... | Explore |
|---|---|
| AI and ML | Amazon SageMaker, Amazon Bedrock |
| Data | Amazon Athena, AWS Glue |
| Security | Deeper IAM, monitoring |
A common first certification is the AWS Cloud Practitioner, but check current exam details on the official AWS site.
Your turn
Which week would be hardest for a beginner, and what would you add? Share it in the comments and I’ll update the roadmap.
Before you publish
- Turn the first table into an image, or add an architecture diagram from Week 4. Visuals help posts get shared.
- Verify service names and Free Tier details on the official AWS pages, since I haven’t checked them against the latest versions.
- Add one true personal line about what confused you most when you started.
- Share the link on the day you publish, since early likes matter for your badge.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article