AWS Cloud Practitioner: Useful Cloud Basics, Too Much AWS

I took the AWS Cloud Practitioner for Beginners course because I wanted a more rounded understanding of how hosting and cloud infrastructure actually work.

Before that, I'd used services like Netlify and understood the outcome: put something online, deploy it, use it. What I didn't really understand was much of what sat underneath that.

The AWS course helped with that.

Making "the cloud" feel more concrete

Before starting, my idea of cloud computing was still fairly vague.

I'd obviously used cloud storage, just like everyone with a smart phone. This was the first time I properly started thinking about cloud infrastructure as access to compute, storage, databases and services that could be scaled up without owning the physical hardware yourself.

That basic idea made sense - pay for better compute and storage.

So did concepts like regions, availability zones, different instance types, databases and the shared responsibility model.

For a beginner course, that kind of orientation is exactly what I wanted.

Useful terminology, repetitive teaching

The problem was the delivery.

The course covers a range of different areas, but the structure of the lessons became very repetitive.

A service would be introduced, the physical or traditional alternative would be discussed, then the AWS version would be presented as the better way to do it.

After a while, it started to feel less like learning about cloud computing and more like being gradually trained to become a long-term AWS customer.

I understand why. It's an AWS course teaching AWS services.

But it could have been a bit more restrained.

The presenters were good and clearly knew the material, although the enthusiasm could also become slightly exhausting. There is no way in the world an EC2 instance should bring that much joy to somebody.

All 3 hosts were fine on an individual basis. But as a collective had a cheap, cheesy, kids TV thing going on. They're more than manageable, but you've been warned if you're going to take the course.

Too much emphasis on remembering product names

The multiple-choice checks had a similar problem.

Some of them felt less about whether I understood cloud infrastructure and more about whether I could remember the exact AWS service name attached to a particular function.

That's useful if you're preparing for an AWS certification exam.

It's less useful if your main aim is simply to understand the concepts.

Why I didn't take the certification exam

I completed the course material, but I didn't sit the paid Cloud Practitioner certification exam.

At this level, I don't think the badge would add enough value for me to justify the cost.

The learning matters more.

If I move into more advanced cloud work later, then a more substantial certification may become worthwhile. But for an introductory course, I was happy to take the knowledge and move on.

Would I recommend it?

Maybe, with some reservations.

As an introduction to AWS terminology and the basic ideas behind cloud infrastructure, it did what I needed.

It made things like instances, regions and shared responsibility much less abstract, and that's already useful when I start thinking about where AI systems run, what should stay local, what can live in the cloud and how businesses might govern that split.

But the course is repetitive and too promotional.

I'm still likely to try another AWS course because the subject itself is useful, especially as I move further into hosting AI systems and understanding business infrastructure.

So my verdict is fairly simple:

Good as an eye-opener. Too much AWS salesmanship. Worth doing for the concepts, not for the badge.