Welcome 👋
This space is where I’m documenting my journey toward the AWS Certified Solutions Architect exam.
I’m studying AWS not just to pass an exam, but to deeply understand how real-world systems are designed: scalable architectures, secure services, cost-efficient decisions, and the trade-offs that come with them. Writing things down helps me think clearly, and sharing them helps me learn better.
Why I’m documenting this
- To solidify my understanding by explaining concepts in plain English
- To build a practical reference I can come back to later
- To help others who are on the same path and might benefit from real, grounded explanations
- To stay consistent and accountable during exam prep
Everything here reflects how I think, question, and connect the dots as I go.
What you’ll find here
- Core AWS concepts (compute, storage, networking, security)
- Architecture patterns and best practices
- Notes from hands-on labs and experiments
- Exam-focused insights (what matters, what’s often misunderstood)
- Trade-offs and “why this over that” thinking — not just definitions
This isn’t meant to be official documentation or a shortcut guide. It’s a working notebook, shaped by curiosity, mistakes, and iteration.
Who this is for
- Anyone preparing for the AWS Solutions Architect exam
- Engineers who want a clearer mental model of AWS
- People who learn better through explanation and examples, not memorization
If you’re on a similar journey, I hope something here saves you time, confusion, or a few headaches.