When I started studying for AWS certifications, my original plan was to go through the entire AWS Cloud Practitioner course from Mammoth Club, then work my way up to the Associate-level certifications. It seemed like the natural order, and it felt safe. But luckily, it’s still early in the game for me, and after doing some research and thinking about what I actually want out of this journey, I realized I needed to pivot, not just to save time, but to learn the right things in the right way.
After looking into the certification structure and talking to others in the cloud space, I found that the AWS Solutions Architect Associate certification already covers most of the material found in the Cloud Practitioner exam. It didn’t make sense for me to spend several extra hours reviewing foundational topics that I’d be learning again in more detail later. But more importantly, I realized that I don’t just want to pass a certification, I want to actually understand how AWS works under the hood. I want to build real-world infrastructure with code. I want to feel confident explaining why a certain service is better for a specific use case, and I want to automate it, deploy it, and fix it when it breaks.
That’s when I made the decision to completely rethink my study plan. I’m still going after the AWS Developer Associate and Solutions Architect Associate certifications, but I’m filling in the gaps between them with hands-on tools and deeper learning resources. This isn’t about rushing to get a badge — it’s about becoming job-ready.
Here’s what I’m doing instead:
My Updated, Job-Focused AWS Study Plan
Starting with Linux First (Before Diving into AWS)
Before I even touched EC2, IAM, or any of the AWS services, I decided to focus on Linux. It’s foundational. Almost everything in the cloud runs on it, and I wanted to build a real understanding, not just run a few commands.
I’ve been learning Linux through a combination of resources:
- Supplemental practice on LinuxJourney.com, which has been super helpful for hands-on experimentation
- A course on Udemy called Linux for Cloud & DevOps Engineers
I noticed that Linux Journey covered most of what was in that course actually. It was still a good course, but I think I actually preferred learning on Linux Journey better. The course was good though and many may prefer learning that way. I also spun up a few EC2 instances to practice SSH, remote updates, permission management, and more. But I’m not trying to rush it. I want to be truly comfortable in the terminal before diving deep into AWS services.
My Updated, Job-Focused AWS Study Plan
Once I get through the core Linux concepts, I’ll shift my focus back to AWS. But this time, I’m not just “studying for certs”—I’m building a toolkit that prepares me for real-world work.
Here’s what my new study roadmap looks like:
AWS Solutions Architect Associate: Stephane Maarek & LearnCantrill.io
I’m using two of the best resources out there to prepare for the Solutions Architect Associate certification:
- Ultimate AWS Certified Solutions Architect Associate 2025 course by Stephane Maarek on Udemy
- AWS Certified Solutions Architect – Associate (SAA-C03) course by Adrian Cantrill at LearnCantrill.io
These both go far beyond surface-level material. They focus on real-world scenarios and explain the why behind each AWS design pattern and decision. I’ll alternate between the two depending on the topic, so that I get a well-rounded understanding before I sit for the exam.
AWS CLI
Before getting too far into the cert prep, I’m also making sure I’m comfortable using the AWS Command Line Interface (CLI). I’ve already installed it in WSL and started using it to test configurations and deploy small resources. The CLI is a tool used constantly in real-world jobs, and learning it now makes everything else easier to practice and automate later.
Networking Deep Dive: VPC and Subnet Mastery
After that, I’ll dive into Chetan Agarwal’s VPC and Networking course on Udemy. AWS networking is a critical skill for cloud architects and engineers—so this is something I want to really understand. This course covers everything from VPCs and subnets to VPNs, Direct Connect, NACLs, and route tables. I don’t just want to memorize this for the exam. I want to be able to design and troubleshoot real cloud network environments.
Python Automation with Boto3
Next up is Python programming with Boto3. I’m not trying to become a Python expert or build full apps. My goal is to write clear scripts that automate common AWS tasks across services like EC2, S3, CloudWatch, and Lambda. Since most cloud support and engineering jobs list scripting as a key skill, this gives me a huge advantage, and it’s something I genuinely want to get better at.
Infrastructure-as-Code with AWS CDK
Once I’m comfortable with the CLI and Python automation, I’ll work through every project in Paula Dichone’s book, “Mastering AWS CDK”. This includes building API Gateway + Lambda stacks, setting up CI/CD pipelines, and managing full-stack deployments using TypeScript or Python. It’s not just about learning the CDK—it’s about learning how real teams build and manage infrastructure as code in production.
AWS Documentation + Best Practices
I’ll be using AWS’s official documentation along the way as a core part of my learning. I’ll refer to it for anything related to cost optimization, service limits, and DynamoDB performance and modeling. It’s where I go to double-check implementation details, stay up to date on service changes, and read about best practices. Knowing how to navigate and understand the docs is a real job skill that I want to build now, not later.
What This All Leads To
With this plan, I’m preparing to apply for entry-level cloud support or junior cloud engineering roles once I’ve completed my certifications and built a few solid projects. I don’t just want a certification, I want the skills to back it up.
This updated study path gives me:
- A deeper understanding of Linux and AWS internals
- Hands-on experience with the CLI, Python, and infrastructure-as-code
- Project-based learning that mirrors real job tasks
- Confidence to explain and troubleshoot what I’ve built
It’s no longer about “just getting certified.” I’m learning this to become someone who can deploy secure, scalable systems, write the code that launches them, and understand what’s happening at every step.
This plan feels a lot more focused and real to me now. I’m no longer studying to pass, I’m studying to build. I want to be able to deploy secure, scalable systems, write the code that launches them, and have a clear understanding of what’s happening at every step. That’s what I believe it takes to become a good cloud engineer, not just a certified one.
I’ll keep posting updates as I move through each stage. If you’re going through your own AWS journey and wondering whether to stick to the path or branch out, don’t be afraid to pivot. Sometimes the best move is to rethink the plan entirely. I will share my full study roadmap and notes over at my GitHub.