Renting computing properly: how to build, secure, run and pay for systems on AWS, Azure or Google Cloud.
Who it's for: Complete beginners through working engineers moving to cloud roles. No prior cloud experience assumed; the groundwork module covers Linux, networking and Git.
Sign in to keep your progress.
Groundwork to production: foundations, compute, storage, networking, security, containers, infrastructure as code, reliability, cost and architecture, ending in two projects you can show.
12 modules · 64 topics · ~295 estimated learning hours. Each module builds on the ones before it — follow the "Comes after" chips to stay on solid ground.
Cloud is mostly ordinary computing, rented. These are the skills every cloud task quietly assumes. Skip them and every later module will feel harder than it is.
What the cloud is, who is responsible for what, and where in the world your data sits. This module is also the whole of the entry-level certifications.
Machines you rent by the second, and the four different shapes they come in. Choosing between them is most of cloud architecture.
Where the data goes, and the two questions that matter: what happens when it grows, and what happens when it is lost.
The part that separates people who can deploy from people who can deploy safely. Most cloud data leaks are network mistakes.
The half of the shared responsibility model that is yours. Almost every cloud breach happens on this side of the line.
How software is packaged and run today. Learn containers properly before Kubernetes; most teams need the first and not the second.
Clicking in a console does not survive a second environment or a second engineer. This module is where cloud work becomes engineering.
Finding out before your users tell you, and being honest in numbers about how reliable you actually are.
The skill that gets people promoted and stops projects being cancelled. Nobody teaches it and every employer needs it.
Putting the pieces together for a real problem, and moving existing systems without a heroic weekend.
Evidence. Two things running that you built, one certification if it helps you, and a way to talk about both.