As a web engineer doing full-stack work, I’ve spent years inside the AWS ecosystem. EC2, DynamoDB, Redis, Lambda, API Gateway, and S3 are part of my daily toolkit. I was comfortable building and deploying on them, but I also knew there was a lot of AWS I’d never touched and a lot of architectural reasoning I’d never had to do explicitly.

So this year I set myself a goal at work: pass the AWS Certified Solutions Architect – Associate exam. I wanted to go deeper on the services I only knew at the surface and get better at designing whole systems rather than wiring up the parts I already knew. I passed the SAA-C03 on my first attempt with a score of 903/1000, and this is the plan that got me there over about nine months.

What the exam actually tests

The Solutions Architect – Associate exam is less about knowing what each service does and more about knowing how they fit together into something secure, resilient, fast, and not needlessly expensive. The questions are scenario-based, and they cover four domains:

  • Design Secure Architectures (30%)
  • Design Resilient Architectures (26%)
  • Design High-Performing Architectures (24%)
  • Design Cost-Optimized Architectures (20%)

That spread means you can’t specialize your way through it. You need at least working knowledge of networking, databases, security, serverless, and more.

The four steps

I studied roughly five hours a week for nine months. My hands-on experience helped, but most of the value came from doing it in a deliberate order instead of cramming a stack of resources at once.

1. Get the lay of the land: Ben Piper’s study guide

I started with the AWS Certified Solutions Architect Study Guide by Ben Piper to get a high-level picture of everything the exam touches. It was a good way to see the whole territory at once and figure out which services I’d never used. I didn’t try to memorize anything here. The point was to know what existed before going deeper.

2. Go deep: Adrian Cantrill’s video course

Adrian Cantrill’s course (learn.cantrill.io) did most of the heavy lifting. He builds topics from the fundamentals up, so even the parts I thought I understood got a firmer foundation. The labs were where it clicked for me: I wasn’t watching, I was building, configuring, and breaking things.

Because I already knew EC2, Lambda, and DynamoDB, I moved quickly through those sections. The areas I rarely touch at work, complex networking especially (VPC peering, Transit Gateway, Direct Connect), are where his diagrams and explanations earned their keep. If you only do one thing on this list, do this course.

3. Test under pressure: Tutorials Dojo practice exams

After months of input, I needed to see what had stuck. The Tutorials Dojo practice exams match the real thing closely in difficulty and style. I took the first one in timed mode to feel the pressure and get an honest baseline.

The explanations are the real value. I reviewed every question, including the ones I got right, to understand why each answer was correct or wrong, and to find the documentation worth reading next. This is what surfaced my weak spots: on-premise migrations, AWS Organizations, and the parts of user management that go beyond basic IAM.

4. Consolidate: Tutorials Dojo eBook and cheat sheets

In the last few weeks I stopped learning new things and started reviewing. The Tutorials Dojo study guide eBook and their cheat sheets are dense summaries with good comparison tables, which is exactly what you want for the “when do I use which S3 storage class” kind of question. They’re built for fast revision, and they helped me lock in the differences between similar services.

Looking back

Scoring 903 felt good, and setting the exam as a yearly work goal was what kept me consistent. My existing work with DynamoDB, Lambda, and API Gateway gave me a head start, but the certification pushed me well outside it: networking, migration strategies, and AWS Organizations, all things I rarely touch day to day.

The result is that I now reason about AWS architecture more deliberately than I used to, and I’m more confident designing systems that have to be secure, scalable, and cost-aware from the start. If you’re considering it, the time cost is real, but the understanding you walk away with is worth more than the badge. Good luck.