AWS Cloud Practitioner: 15 Weeks of Real Study

The AWS Certified Cloud Practitioner certification is often described as the “easy” AWS exam.

That wasn’t my experience.

Covering more than 50 foundational AWS services and features, it took me 15 weeks of structured study with Digital Cloud Training — alongside teaching guitar full time — to complete it properly.

Here’s what that actually involved:

• 🎥 210 lesson videos
• 🛠 12 hands-on technical assignments inside AWS
• 🧪 48 practice tests
• 💬 Deep follow-up study sessions with ChatGPT to stress-test understanding

The assignments weren’t written coursework. They were practical AWS scenarios — configuring services, troubleshooting setups, and solving architecture problems.

And in the middle of all that…

I took over the hosting of my own teaching website.

Real-World Application: Taking Over My Own Hosting

Halfway through the course, I migrated my teaching website (cliffsmithguitarlessons.co.uk) from fully managed hosting to AWS Lightsail, redesigning it to be fully recoverable in the process. The move reduced hosting costs by approximately 91% per month.

That meant:

• Migrating WordPress to Lightsail (Bitnami stack)
• Allocating and attaching a static IP
• Provisioning SSL certificates
• Setting up snapshot and S3-based backup strategies
• Testing restores
• Managing DNS changes safely
• Verifying email records (MX, SPF, DKIM, DMARC)
• Checking HTTPS redirects
• Testing forms and user flows before cutover

Studying the theory while actively running production infrastructure created a powerful feedback loop.

Cloud concepts stopped being multiple-choice answers — they became responsibility. I reduced hosting costs significantly, but with no managed support in place, operational ownership was entirely mine.

The Foundation: Understanding Cloud Properly

At the core of the course was understanding how cloud systems are designed:

• On-demand provisioning
• Elastic scaling
• Global infrastructure
• Managed services
• Security-first architecture

The biggest shift wasn’t memorising services.

It was learning to think architecturally.

What This Certification Actually Requires

Despite its “entry-level” label, this certification demands:

• Understanding high availability vs scaling
• Knowing the difference between durability and availability
• Recognising when to use managed services
• Understanding identity and access control models
• Grasping networking fundamentals
• Thinking in terms of failure domains

Doing this while teaching guitar full time meant disciplined evenings and weekends.

And the 12 hands-on assignments forced me to apply concepts inside AWS — not just recognise them in multiple choice questions.

What I Actually Gained

Not just an exam score.

But:

• A structured mental model of cloud systems
• Clarity around resilience design
• Confidence managing real infrastructure
• A deeper understanding of cost and operational trade-offs
• The ability to reason about architecture decisions

More importantly — the knowledge feels usable. I now have many moreideas for future projects.

Final Reflection

This certification might be marketed as foundational.

But foundations matter.

15 weeks. 210 lessons. 12 technical AWS problem-solving assignments. 48 practice tests. A full website hosting migration in the middle of it.

If this is the “easy” one, I’m glad I didn’t treat it lightly.