CompTIA Cloud+: The Course That Changed How I See Cloud Costs

I Wasn't Expecting Much

Honestly, when I signed up for the CompTIA Cloud+ course, my expectations were pretty low. Vendor-neutral certifications have a reputation for being broad and surface-level — the kind of thing you do to tick a box, not to actually learn something useful. I figured it would be a lot of "the cloud is like a utility" analogies and not much else.

I was wrong.

More AWS Than I Expected

The course leaned noticeably toward AWS during the lesson delivery, with some Microsoft Azure sprinkled in. The labs, though, were more balanced — they covered both AWS and Azure for most scenarios. I think the AWS focus during lessons was probably tailored to the class makeup rather than being the default structure, but either way, it worked out fine for me.

Here's a thing I'm actually glad about: I messed around with AWS EC2 more than ten years ago. No training, no real goal — just poking at it out of curiosity on the free tier. At the time I didn't think much of it. But walking into this course, that old memory gave me just enough of a mental scaffold to follow along without feeling completely lost.

If you're reading this and thinking about taking Cloud+, my honest advice is to go play with the free tier on AWS or Azure before you attend. It doesn't need to be structured. Just spin something up, break it, try to fix it. That surface-level familiarity will speed up your understanding in class more than any pre-reading will.

The Thing That Actually Blew My Mind

Okay, here's the part that genuinely surprised me — and not in a good way.

I think a lot of people, myself included before this course, carry this idea that moving to the cloud saves money. You don't need to buy physical hardware. You don't need to hire someone to maintain it. The infrastructure cost disappears. That part is true.

But almost everything else costs money. And when I say almost everything, I mean it's closer to 99% of services. CPU usage, monitoring, storage I/O — if AWS or Azure can find a way to meter it, they will. Coming from a background where I understood on-prem equipment, where you buy a licence and just use the thing, this pricing model hit differently. It's all subscription now. Every single layer.

Some people will say that's great for SMEs because the barrier to entry is so much lower than buying physical equipment. And yes, okay, that's technically true. But here's what really got to me during the course: cloud providers typically offer free ingress — meaning uploading your data to the cloud costs nothing. But downloading it? That costs money. Egress fees are real, and they add up.

Think about what that actually means. If an SME has been running on the cloud for five years and one day decides to move back to on-prem, or even just switch providers — the cost of pulling all that data out could be so high that it makes more financial sense to just delete everything and start fresh. That's not a hypothetical edge case. That's the actual economics of how it works.

It's a lock-in by design. The free ingress is the bait. The egress fees are the trap door.

My Honest Take for SMEs

I'm not saying don't use the cloud. I'm saying go in with eyes open. Understand what services you're actually using, what gets metered, and what your exit costs look like before you commit. Because once you're deep in, the switching costs — both financial and operational — can be brutal.

If your workload is predictable, your team is small, and you're not handling massive volumes of data, maybe the cloud math works out fine. But if you're an SME that hasn't really thought through the long-term pricing model, it might be worth sitting down with a spreadsheet before you migrate everything over.

Who This Course Is Actually For

I'd give Cloud+ a solid 4 out of 5. The content is genuinely good, the labs are practical, and the way the pricing realities were explained was honestly more valuable to me than any amount of technical configuration walkthrough.

That said, I wouldn't throw a complete beginner into this. I think you'd get the most out of it if you already have around two to three years of experience in some related IT field — networking, sysadmin, helpdesk, something adjacent. Not necessarily cloud, but you need enough of a baseline to follow the infrastructure concepts without getting lost in the fundamentals.

For me personally, it reframed how I think about cloud as a business decision, not just a technical one. That alone made it worth the time.