Your next chapter starts here

Hello, Tabang.
Let’s build your cloud path.

Cloud infrastructure is the invisible layer behind the apps people use every day. You don’t need to know everything at once — you need a direction, a habit of building, and a few real systems you can explain.

Small steps. Real systems. Strong foundations.

Think like an engineer: understand the layer below you, automate what repeats, and leave things better documented.

Student → Cloud builder

Six stages, one
practical direction.

You can move through these stages at your own pace. Each one gives you a useful mental model and something tangible to build.

01 · Foundations→
🧱

Linux & the command line

Files, processes, permissions, SSH, logs, packages and the confidence to explore a server.

02 · Connectivity→
🌐

Networks & the web

IP addresses, DNS, HTTP, TLS, firewalls and how a browser finds a service.

03 · Cloud basics→
☁️

Compute & storage

Virtual machines, containers, object storage, backups and choosing the right building block.

04 · Automation→
⚙️

Code your infrastructure

Git, scripts, CI/CD and infrastructure-as-code: make reliable changes repeatable.

05 · Reliability→
📈

Observe & improve

Metrics, logs, alerts, incident thinking and the calm discipline of good operations.

06 · Portfolio→
🚀

Ship something real

Deploy a useful project, document it clearly, and explain the decisions you made.

Make a tiny cloud lab.

Don’t wait for a perfect idea. Build a small environment you can break, fix, observe and explain.

1
Launch a small Linux serverConnect with SSH and create a non-root user.
2
Deploy a simple web pagePoint a domain at it and protect it with HTTPS.
3
Automate one repeatable taskBackups, updates or deployment — then document it.
tabang@cloud-lab:~$ whoami
a curious engineer in progress

tabang@cloud-lab:~$ cat next-step.txt
Learn one layer.
Build one thing.
Write down what happened.

tabang@cloud-lab:~$ echo $STATUS
READY_TO_BUILD

There is no magic shortcut.
That’s good news.

Cloud skills grow through curiosity, practice and the ability to explain your work. Keep showing up — your future systems will be built one layer at a time.

Start with foundations ↑