Skip to content

Learn Cloud - Without Chasing a Certification

Plain-English explanations of cloud computing, networking, containers and DevOps for people who want to understand the technology, not just pass an exam.

Built and maintained by Patrick Wiloak - Ex-AWS Solutions Architect, 19x multi cloud certified, 64 certifications and accreditations, 10 years in tech. If certs aren't your goal, start here.

πŸŽ₯ @patrickwiloak | πŸ’Ό LinkedIn


Who this is for

You want to understand cloud, but:

  • You're not preparing for an exam (or not yet)
  • You want context and intuition, not 200-question fact dumps
  • You'd rather learn the why before drilling into vendor-specific details
  • You're a developer, founder, PM, analyst, or curious technologist

If you do want certifications, head back to the Study Hub - every cloud cert on this site, fully indexed.


What's in this hub

Brand new to all of this?

  • Day One - terminal, git, HTTP, servers. The pages assume nothing. If you've never opened a terminal, start here.

Bite-size concept pages

  • Concepts - 18 topic pages, 5-10 min each. Cloud primitives (regions, VPC, K8s, serverless), DevOps (CI/CD, Terraform, deployment strategies), networking (DNS, CDNs, load balancing), and operations (autoscaling, caching, observability, cost).

Structured learning paths

Learning AI, data or security?

Reference


How to use this

There's no "right order." Pick what fits:

If you want to... Start here
Start from absolute zero Day One
Look up a term you keep seeing Glossary
Understand one concept (VPC, DNS, containers, ...) Concepts
Build a foundation in cloud Cloud from Scratch
Compare AWS vs Azure vs GCP Service comparisons
See real architectures Architecture patterns
Try hands-on labs Hands-on projects

Why this exists

Most cloud content is either:

  1. Cert-shaped - exam objectives, fact sheets, practice questions (great if you have an exam date, useless if you just want to understand)
  2. Vendor marketing - "transform your business with the cloud!" (no actual technical content)
  3. Deeply specialized - PhD-level papers, engineering postmortems (skip the fundamentals you'd need to follow them)

This hub is the missing middle: technical, accurate, plain-English, no exam scaffolding.


Companion resources


Contributing

Spot something wrong, unclear, or missing? See CONTRIBUTING.md. Plain-English contributions especially welcome - if you can explain something better than I did, please do.