The Year I Fully Committed to the Cloud
When I began preparing for AWS certifications, I didn’t do it to collect badges. I did it because I needed deeper clarity, stronger fundamentals, and a structured way to validate the cloud decisions I was already making.
The more my role demanded architectural thinking, resilience planning, cost modeling, and migration strategies, the more I felt the need to formalize what I knew and uncover what I didn’t.
That’s when I decided to pursue AWS certifications the right way: with patience, consistency, curiosity, and structure.
This article is my complete journey. Not the “I passed in two weeks” version but the real version, the one filled with study routines, setbacks, “aha” moments, and the satisfaction of finally clicking Submit and seeing that Congratulations message.
If you are preparing for the Cloud Practitioner or Solutions Architect exam, my hope is that this story becomes your guide and your confidence boost.
Cloud Practitioner: My Foundation Phase
Cloud Practitioner is often underestimated. But it was the certification that grounded me. It wasn’t just AWS terminology. It wasn’t just pricing models or regions or EC2 categories. It was the philosophy of AWS.
What I used to study:
- A Cloud Guru: Great for approachable fundamentals and relatable examples. (A Cloud Guru is now part of Pluralsight)
- Pluralsight: Strengthened conceptual understanding
- AWS Skill Builder: Official training, surprisingly aligned with exam thinking
- AWS Whitepapers & Guides: Especially the Well-Architected Framework and Cloud Adoption Framework
I studied consistently for several weeks, short bursts, weekend blocks, and focused review sessions.
When I took the exam, it felt like AWS asking, “Do you really understand how the cloud works?”
It wasn’t hard. It was purposeful, and it built the base I needed for everything that came next.
AWS Solutions Architect Associate: The Real Challenge
If Cloud Practitioner was orientation day, Solutions Architect was the full marathon.
Suddenly, I had to think like an architect:
- Which service best fits this scenario?
- What keeps the system durable, scalable, and cost-effective?
- What’s the simplest design that solves the problem?
- How do you eliminate a single point of failure?
Study Stack (My Winning Formula)
- A Cloud Guru: Visual learning + demos + architecture basics.
- Pluralsight: Detailed walk-throughs on networking, databases, and security patterns.
- AWS Skill Builder (most important): Exam Prep, Hands-on labs, Builder Labs, and Practice exams that feel “just like the real thing”
- AWS Whitepapers & Guides & FAQs: Dry but priceless, especially for RDS, DynamoDB, S3, VPC, IAM, and EC2.
- YouTube Deep Dives: To demystify VPCs, NAT gateways, SQS vs SNS, and Lambda concurrency.
My Study Rhythm
- Mornings: quick note reviews
- Midday: 20 — 30 minutes of course content
- Evenings: labs + practice exams
- Weekends: mock exams + refactoring weak topics
There were weeks I felt stuck, and weeks where things clicked. But the momentum kept building.
Key Concepts That Finally “Clicked”
Several topics went from confusing → clear only after visualizing, practicing, and re-learning:
- VPC Networking
Subnets, route tables, gateways, NACLs, SGs finally made sense as a city’s transportation system. - High Availability vs Fault Tolerance
Multi-AZ vs multi-Region strategies, and when each matter. - Deciding Between Databases
The “why” behind Aurora vs DynamoDB vs RDS vs Redshift. - Designing for Cost
The exam subtly tests if you choose the solution that’s simple and cost-efficient, much like real-world AWS reviews.
Exam Day: The Moment All the Practice Paid Off
I scheduled the exam around Noon, stayed relaxed, and avoided last-minute cramming.
The biggest realization?
AWS Skill Builder practice questions were extremely similar to the real exam thinking style.
I wasn’t memorizing. I was solving, and when the results popped up.
I passed on my first attempt.
I took a breath and smiled. It wasn’t just a test result. It was validation that the entire journey had been worth it.
Two Sample “Twist” Questions to Expect
AWS exams rarely trick you. But they do test your reasoning by offering multiple “good” answers, but only one best one.
Example 1: Storage Confusion
Your application needs shared storage for EC2 instances across multiple Availability Zones. The data must persist even if one AZ goes down. Which service should you choose?
Choices might include:
☐ EBS
☐ Instance store
☐ EFS
☐ S3
All sound familiar. But only EFS offers shared, elastic storage across AZs for EC2. This is a classic AWS-style twist.
Example 2: High Availability Trap
Your application runs on an EC2 instance. You need the simplest way to ensure automatic recovery if the instance fails. What do you choose?
Choices might include:
☐ Auto Scaling Group with multi-AZ
☐ Multi-region failover
☐ EC2 Auto Recovery
☐ Elastic Load Balancing
Most people jump to ASG, but the simplest, most cost-effective answer is EC2 Auto Recovery, especially when the scenario doesn’t mention scaling needs.
What I Wish I Knew at the Start
- Cloud Practitioner matters more than you think. It builds architectural intuition.
- Don’t just memorize. Deeply understand. AWS tests your conceptual thinking.
- Practice exams are not optional. They sharpen your decision-making: “good” vs “best.”
- Labs change everything. Once you build VPCs, IAM policies, and S3 lifecycles yourself, the exam becomes much easier.
- Be consistent, not heroic. 30 minutes a day > 5 hours once a week.
What to Do Next After These Certifications
Once you have Cloud Practitioner and Solutions Architect under your belt, you stand at a powerful crossroad.
Here are the most impactful next steps depending on your career goals:
Go Deeper into Architecture
- AWS Solutions Architect — Professional (SAP-C02)
If you love multi-account strategy, complex architecture, cost optimization, and resilience engineering, this is your next mountain.
Specialize in a Domain
- Security
AWS Security Specialty
Perfect if you’re involved in governance, compliance, IAM strategy, or enterprise security. - Databases
AWS Database Specialty
Amazing for those handling migrations, Aurora, DynamoDB, or data modernization. - Networking
AWS Advanced Networking Specialty
For anyone designing multi-region, multi-VPC, on-prem connectivity, Transit Gateway, Direct Connect, etc. - ML, DevOps, or Observability
Depending on your role:
- DevOps Engineer
- Machine Learning Specialty
- Data Analytics Specialty
Apply AWS Knowledge at Work
Sometimes the best next step is not another exam. It’s applying your new architectural clarity to:
- review your company’s cloud costs
- redesign reliability patterns
- build internal governance
- modernize infrastructure
- drive resilience simulations
- improve scalability planning
Certifications give you confidence but applying them gives you mastery.
Beyond Certification: How This Journey Changed Me
Preparing for these AWS exams reshaped the way I:
- think about system design
- validate architectural choices
- lead platform engineering discussions
- approach resilience and cost optimization
- guide teams with clarity and confidence
It aligned beautifully with the Eat · Train · Lead philosophy:
Eat: Feed your mind deliberately.
AWS white-papers and labs became my intellectual nutrition.
Train: Practice until architecture becomes instinct
Every practice exam was another repetition.
Lead: Raise the bar for your team
The certification helped me bring more clarity, conviction, and structured thinking to our cloud initiatives.
Final Thoughts
If you’re preparing for AWS certifications, remember:
You don’t need to finish fast. You just need to finish strong.
Study in small consistent blocks. Do labs.
Take practice tests. Understand the “why” behind AWS services.
And when you feel stuck, remember, every architect has been there.
About the Author
Raj Chanolian is a Platform Engineering leader, AWS practitioner, and the creator of the Eat · Train · Lead philosophy, a lifestyle and leadership framework built around intentional learning, disciplined practice, and authentic personal growth. With years of experience driving cloud modernization, high-availability architecture, and engineering excellence, Raj blends technical depth with practical storytelling to help readers grow in their careers, health, and leadership journey.
Follow his writing for insights on cloud computing, fitness, mindful leadership, and building a life powered by discipline and clarity.
You don't need to finish fast. You just need to finish strong.
Certifications give you confidence but applying them gives you mastery.
AWS certifications are worth it if you already work in cloud environments — they force you to systematize knowledge that would otherwise remain fragmented intuition. Cloud Practitioner is underrated as a foundation; do not skip it. The real differentiator in the Solutions Architect exam is hands-on labs — people who only watch videos consistently struggle with scenario-based questions. Thirty focused minutes daily beats weekend cramming sessions every time.
What I'd Actually Do
- Start with Cloud Practitioner even if you have cloud experience — it builds architectural intuition that makes Solutions Architect click faster
- Do AWS Skill Builder labs for VPC, IAM, and S3 before attempting practice exams — hands-on experience converts abstract concepts into solved problems
- Use the 30-minutes-daily rhythm: morning note review, midday course content, evening practice questions; weekend mock exams
- When you get a practice question wrong, write down why the correct answer is better — not just what it is
- After passing, apply your knowledge at work for 3–6 months before pursuing the next certification; mastery comes from application, not collection