In March 2026, I sat the AWS Certified Cloud Practitioner (CLF-C02) exam and passed. This isn't a deep architectural certification — it's the foundational one — but as a full-stack developer who deploys to AWS, it filled in a surprising number of gaps. Here's the honest version.

What the cert actually validates

The Cloud Practitioner exam covers four domains:

• Cloud Concepts — what the cloud is, the value proposition, deployment models
• Security and Compliance — the shared responsibility model, IAM, encryption basics
• Cloud Technology and Services — naming the right service for the right job (EC2, S3, Lambda, RDS, VPC, etc.)
• Billing, Pricing, and Support — how AWS actually charges you, support tiers, cost management tools

It's breadth over depth. You don't configure anything; you recognize what would be configured.

What I studied

My prep took about three weeks of evening study, building on hands-on AWS work I'd already done at Deloitte. The mix that worked:

The official AWS Skill Builder course

Free, structured, and aligned to the exam objectives. It's dry, but it's the source of truth.

Stephane Maarek's practice exams

The single highest-leverage prep material. Six practice exams, each with detailed explanations for every question — including the wrong answers. I scored ~65% on my first practice attempt and ~85% by the last one.

A small AWS sandbox account

You don't need hands-on for this exam, but I'd recommend it. Spinning up an EC2 instance, putting an object in S3, and creating an IAM user with restricted permissions cemented concepts that flashcards never could.

# Quickest sandbox setup
aws configure
aws s3 mb s3://my-test-bucket-2026
aws s3 cp ./local-file.txt s3://my-test-bucket-2026/
aws iam create-user --user-name read-only-tester

What surprised me

Three things I expected to be easy turned out to need real attention:

1. Pricing and billing. Memorizing service names is mechanical. Understanding why an EBS volume costs you when an instance is stopped, or how Reserved Instances actually save money, takes more thought.
2. The shared responsibility model. The exam tests this with a lot of "is AWS responsible or is the customer responsible?" questions. The model is simple in theory, fuzzy in practice.
3. Support tiers. Boring, but heavily tested. Know what Basic, Developer, Business, and Enterprise tiers actually include.

Was it worth it?

For a full-stack developer who already deploys to cloud platforms — yes, but with a caveat. The cert itself signals very little to a senior engineer who already lives in AWS. What it gave me was structured knowledge of AWS services I'd never touched (CloudFront, Route 53, Lambda use cases beyond the obvious) and a vocabulary for talking about cloud architecture in interviews and design discussions.

If you're early career and your day-to-day work touches cloud infrastructure even slightly, it's worth the three weeks. If you're already a Solutions Architect, skip ahead to the Associate-level certs.

What's next

Solutions Architect Associate is on my list for late 2026. The jump from foundational to associate-level is significant — the SAA exam expects you to design real systems, not just identify services. Different prep, different mindset. I'll write about that one when it's done.