How to Start AWS From Zero: The Week-by-Week Roadmap That Actually Works (2026)

Every week I get the same DM: "I want to learn AWS but I don't know where to start."

This article is the answer I give every time. Not the generic "watch some YouTube videos and get certified" advice. The actual week-by-week path that takes you from zero to job-ready in cloud.

I've watched hundreds of engineers fail at this — not because they weren't smart enough, but because they studied in the wrong order, skipped the hands-on work, or tried to learn everything at once.

This roadmap fixes all three mistakes.

Before You Start: The One Rule That Changes Everything

Never study without building something that week.

Every concept needs a project attached to it. Reading about S3 without deploying an S3 bucket is like reading about swimming without getting in the water. You'll forget it in 48 hours.

Every week in this roadmap has a project. Do the project. It matters more than the reading.

Week 1–2: Foundation

Goal: Understand what cloud actually is and get comfortable with the AWS console.

Create a free AWS account today. Not tomorrow. Today. AWS has a free tier that covers almost everything you'll need for the first 3 months of learning.

Then learn what these 5 services do — not from documentation, but from actually using them:

S3 — Object storage. Think of it as a hard drive in the cloud.
EC2 — Virtual machines. A computer you rent by the hour.
IAM — Identity and access management. Who can do what in your account.
VPC — Virtual private cloud. Your own private network inside AWS.
Lambda — Serverless functions. Code that runs without a server.

Recommended Resource: FreeCodeCamp's AWS Cloud Practitioner crash course on YouTube. Free, comprehensive, and gets you the vocabulary you need before anything else.

Week 1–2 Project: Deploy a Static Website on S3

Sounds simple. Teaches you S3 buckets, bucket policies, static website hosting, and public access settings — all concepts that appear in every AWS interview.

Why Cloud Practitioner first? Not to put on your resume. To understand the vocabulary. Without it, every other course will have you Googling basic terms every 5 minutes.

Week 3–4: Get Hands-On With Core Services

Goal: Move from understanding to doing.

Three projects this fortnight, one per concept:

Project 1: Launch an EC2 Instance and SSH Into It

This teaches you: instance types, key pairs, security groups, Elastic IPs, and basic Linux. Every cloud interview assumes you've done this. If you haven't, you'll feel it immediately.

Project 2: Create IAM Users, Groups, and Policies

This teaches you: the principle of least privilege, policy structure, and why IAM is the most important security layer in AWS. Create a user with read-only S3 access. Then create one with admin access. Understand the difference.

Project 3: Build a Simple VPC From Scratch

Create a VPC with a public subnet, a private subnet, an internet gateway, and a NAT gateway. Launch an EC2 in the public subnet. Try to reach the internet from the private subnet through the NAT.

This project alone teaches you more about cloud networking than any course.

Week 5–8: Solutions Architect Associate Preparation

Goal: Get the certification that actually matters for getting hired.

The AWS Solutions Architect Associate (SAA-C03) is the single most valuable cloud certification for job seekers in 2026. Recruiters look for it. Interviewers expect it. It proves you understand cloud architecture, not just cloud services.

The best course: Adrian Cantrill's Solutions Architect Associate course. It is not free (around $40 USD) but it is the best investment you will make in this journey. He builds everything from first principles and his course has the highest pass rate of any SAA prep material.

How to Study

One module per day, maximum.
After every module, do the hands-on lab if there is one.
Never move to the next topic without understanding the current one.

Week 5–8 Projects

Build one real project per week alongside studying:

Week 5: A serverless API using Lambda + API Gateway + DynamoDB
Week 6: A multi-tier web application with EC2, RDS, and an Application Load Balancer
Week 7: An S3 static site with CloudFront distribution and a custom domain
Week 8: An auto-scaling group that scales EC2 instances based on CPU utilization

These projects map directly to SAA exam scenarios and interview questions.

Practice exams: Tutorials Dojo SAA practice exams. Do them daily in the last 2 weeks before your exam. If you score above 85% consistently, you are ready.

Week 9–12: Interview Preparation

Goal: Turn your knowledge into job offers.

Passing the SAA exam and passing cloud interviews are different skills. The exam tests what you know. The interview tests how you think under pressure, how you explain your reasoning, and how you handle scenarios you have never seen before.

Most engineers study for the exam and show up to interviews unprepared for the conversation.

What Interviewers Actually Test in 2026

Can you debug a production scenario you have never seen?
Can you explain a complex concept to a non-technical stakeholder?
Can you defend an architectural decision when challenged?
Can you identify what went wrong from a set of symptoms?

These skills are not built by reading documentation. They are built by practicing out loud.

How to Practice

Use InterviewDrill.io — paste the job description of the role you are targeting and the platform generates the exact questions companies are asking for that role, pulled from real interview experiences. Then practice answering them with AI-powered mock interviews that give you feedback on your responses.

The first session is free. Use it before your first real interview.

Other Preparation

Read the AWS Well-Architected Framework (free, foundational for senior conversations).
Study the scenarios in this blog's interview question series.
Practice explaining every service you know in one sentence without jargon.

The Most Common Mistakes to Avoid

Mistake 1: Certification Collecting Without Building

Engineers who have 5 certifications but have never deployed a real application consistently fail interviews. Certifications prove you studied. Projects prove you can build.

Mistake 2: Studying in Isolation

Join a community. AWS has active subreddits, Discord servers, and LinkedIn groups. Explaining concepts to others is the fastest way to find your own gaps.

Mistake 3: Skipping IAM

Every cloud security interview, every production incident, every architecture decision involves IAM. Engineers who treat it as boring admin work get humbled in interviews. Master it early.

Mistake 4: Starting With the Wrong Certification

Do not start with the Developer Associate or the SysOps Administrator. Start with Cloud Practitioner for vocabulary, then Solutions Architect for architecture thinking. This order is not arbitrary.

Mistake 5: Waiting Until You Feel Ready

You will never feel ready. Apply for jobs when you have the SAA and two solid projects. Get rejected. Learn from the interviews. Apply again. The feedback loop from real interviews is more valuable than another month of studying.

Your 12-Week Summary

Week	Focus	Project
1–2	Foundation + Cloud Practitioner	Static S3 website
3–4	Core services hands-on	EC2, IAM, VPC projects
5–6	SAA prep + serverless	Lambda + API Gateway + DynamoDB API
7–8	SAA prep + multi-tier	EC2 + RDS + ALB application
9–10	SAA exam + practice tests	Auto-scaling group project
11–12	Interview prep	InterviewDrill mock sessions

What Comes After

Once you have the SAA and your first cloud job, the learning continues:

AWS DevOps Engineer Professional — the next certification for engineers who want to move into platform and DevOps roles.
Kubernetes and Containers — CKAD or CKA for anyone targeting cloud-native roles.
Terraform — infrastructure as code is expected at every senior level.

But that is a problem for 12 weeks from now. Start with Week 1.

One Last Thing

The engineers who make it in cloud are not the ones who studied the hardest. They are the ones who built the most, asked the most questions, and kept going when things broke.

Things will break. That is the job.

The faster you get comfortable with broken things, the faster you become the engineer everyone calls at 3 AM.

Start today.

Follow @naveenteja.cloud on Instagram for daily cloud and DevOps interview scenarios. New production incident decoded every day.