AWS SAA-C03 in six weeks: the plan that actually works

Most people fail SAA-C03 not because they do not know AWS, but because they study services in alphabetical order. The exam does not ask questions in alphabetical order.

Week one: the map before the territory

Before touching a single service, get the geography right — regions, Availability Zones, edge locations — and understand the shared responsibility model. Half of the "which service" questions collapse once you know whether the requirement is about durability, availability or latency.

Build one VPC by hand this week. Not from a template. Subnets, route tables, an internet gateway, a NAT gateway, two security groups. When it works, delete it and build it again.

Week two: identity and network

IAM is where marks are quietly lost. Learn the evaluation logic: explicit deny, then SCPs, then identity policies, then resource policies. Write a policy that allows s3:GetObject on one prefix and test it against a bucket in another account.

Then VPC peering, Transit Gateway and PrivateLink. Know why each exists and what it costs.

Week three: compute and storage

EC2 purchasing models are examination gold: on-demand, reserved, savings plans, spot, dedicated hosts. Know which one fits a workload that must run for three years versus one that can be interrupted.

For storage, memorise the S3 storage classes by access pattern, not by price. Then EBS volume types and EFS performance modes.

Week four: data

RDS multi-AZ versus read replicas is the classic trap. Multi-AZ is availability; read replicas are read scaling. Aurora has its own endpoint model. DynamoDB needs you to understand partition keys and why a bad key ruins throughput.

Week five: decoupling and delivery

SQS versus SNS versus EventBridge. Lambda concurrency and cold starts. CloudFront cache behaviours and origin access control. Route 53 routing policies with health checks.

Week six: practice and repair

Two timed practice sets, then repair the gaps rather than taking a third. Write down every question you got wrong, and the mechanism behind the right answer. If you cannot explain why an option is wrong, you do not yet know the topic.

What to skip

Do not memorise every service. The exam rewards judgement about trade-offs, and judgement comes from having built the thing once. Twenty hands-on labs beat two hundred flashcards.

If you want to do this with a room of people and an instructor who has broken these systems in production, the live SAA-C03 batch runs in six weeks.