Learn AWS in depth in a local console, from accounts and IAM to networks, data services, security and cost, then the Linux, Kubernetes and Git work around it. Every task is checked, and the pathway ends in a release project, a timed assessment and the cloud engineer interview.
Take the steps in this order. Each step is a set of units from one course, not the whole course: the units this role uses. Open a unit to start its first lesson.
1
AWS in depth
The cloud provider is where the work happens. You set up accounts and regions, IAM roles and policies, S3, compute and disks, the network paths between services, events and queues, and managed data services, then monitoring and delivery, security reviews, architecture decisions and the cost of what you run.
Cloud servers and containers run Linux, and you reach them through a terminal. You move around the file system, change files safely, read logs with pipes, search and rewrite text, and handle permissions and failures.
Many services in the cloud run in containers on Kubernetes. You use kubectl and YAML to run Pods and Deployments, release and roll back, expose Services, add configuration and Secrets, set health checks and resources, and troubleshoot workloads that fail.
Infrastructure changes are code, reviewed in a repository like any other. You commit and inspect history, stage changes selectively, work on branches and sync with a remote.
Define resources and module interfaces in HCL, read the proposed plan and inspect state bindings before applying a change. Practice adoption, address moves, drift and recovery with an independent local provider model; hosted HCP runs and real cloud permissions need separate study.
Each project starts from a fictional company's brief and moves between tools the way the job does: what you build in one stage is where the next one starts. Every brief is free to read.
Velomint
GtGitK8Docker and KubernetesAWAWS
Project
Recover from a failed release
Release 2.14.0 broke one bike unlock in three until on-call rolled it back. Revert the bad commit in Git, ship 2.14.1 on Kubernetes behind a readiness probe, add the CloudWatch alarm that would have caught it, and write the incident report.
When you finish the units, test yourself across the tools of the job at once: 12 practical tasks in 50 minutes, each in the tool it is about and checked automatically. The clock keeps running if you close the page.
Tool
Tasks
Minutes
AWS
6
28
Linux and the shell
3
11
Git
3
11
How it is scored
Each tool
Ready when you get two thirds of its tasks right or more, Close at one third, otherwise Not yet. A coding task earns the share of its tests that pass.
Ready for interviews
75% or more overall, and every tool at Ready.
Nearly ready
50% or more overall, and no tool at Not yet.
Keep practicing
Anything else. The report lists every task you missed with the lesson that teaches it.
The assessment is free. The result is practice feedback in the Interview Hub's report format, not a hiring decision. Retakes draw different tasks where the question pools allow.
The interview
The Interview Hub runs the cloud engineer interview round by round, at a fictional employer: you answer out loud or in writing, the interviewer follows up, and the report quotes your answers.
The first unit of every course, with no account: 5 of the 39 units on this pathway. Every project brief is free to read, and the job-readiness assessment is free.
One Course
One course in full. On this pathway that is one of these: AWS (11 units), Linux and the shell (5 units), Kubernetes (6 units), Git (5 units), Terraform (12 units).
All Access
The whole pathway: every unit, every project stage and spoken interview practice.
A cloud engineer builds and runs the infrastructure a company’s software lives on in a public cloud: accounts and permissions, networks, servers and containers, storage and databases, and the monitoring that says when something is wrong. Every resource is billed, so cost is part of the job too. When something fails, they trace it through logs, metrics and the network path, and change the setup so it doesn’t happen again.
From the console to the cluster
AWS comes first and takes longest, because it is the job. Linux follows for the machines and containers you reach by terminal, then Kubernetes for running services at scale, and Git for keeping every change reviewed and reversible.
Showing what you can do
The Velomint project is a failed release from start to finish: revert the commit that broke bike rental payments in Git, ship 2.14.1 on Kubernetes behind a readiness probe, add the CloudWatch alarm that would have caught it and write the incident report. That is the kind of story cloud interviews ask you to tell. The assessment then shows which tool to practice before you apply.
Network and security practice
The networking course adds subnetting, switch and router commands, routing and packet evidence. For alert investigation, the SOC analyst course teaches log searches and incident handoffs. Use the cybersecurity practice path to connect these tasks with Security Labs and application security.
Infrastructure as code
Practice the Terraform course after the cloud and repository steps. A provider object, its recorded state binding and the desired configuration can disagree. Read the plan before choosing an operation, preserve object identity during a refactor and retain the evidence another engineer needs to review a recovery. The course runs a documented local teaching model. Real cloud access, hosted policies and team permissions require a separately authorized environment.
Common questions
How is this different from the DevOps pathway?
Both use the same tools. This one goes much further into AWS, with event and data services, security, architecture and cost, and keeps the shell and Git to the basics. The DevOps pathway spends longer on the shell, Git and containers, and less on AWS.
Why AWS and not Azure or Google Cloud?
AWS is the cloud this site teaches, and the ideas carry over: identity, networks, storage and monitoring work in similar ways on every provider. If your target jobs name another cloud, learn its names for the same things.
Do I need a certification?
Not for the pathway. If you want one, our AWS Cloud Practitioner guide covers the entry exam and the AWS course has practice tests for it.
How long does it take?
The lessons on this pathway add up to about 77 hours. We don't promise how long getting hired takes.
What does it cost?
The first unit of every course is free, with no account. One Course opens one course in full; All Access opens the whole pathway. The pricing page shows every plan and its price.