Cloud & DevOps Starter | Resources by Shumbul Arifa

โ˜๏ธ Cloud & DevOps Starter

"DevOps" appears on nearly every job posting now, and it looks intimidating. It is not. This is a calm, ordered path through the core skills, with free tools and hands-on projects at each step.

๐Ÿงฑ Ordered path ๐Ÿ› ๏ธ Hands-on ๐Ÿ†“ Free tiers

The DevOps mindset first

Before tools, the idea: automate the boring, repeatable stuff so releases are fast and mistakes are rare. Every tool below exists to serve that goal. Keep asking "what manual step can I automate?" and DevOps will make sense.

Stage 1: Linux & Git (the ground floor)

1

Live in the terminal

Almost all servers run Linux, and everything in DevOps assumes you are comfortable at the command line and with version control.

Linux commandsFile permissionsBash scriptingGitSSH
Build: spin up a free Linux VM (or use WSL), navigate the filesystem, and write a small bash script that automates a task (say, backing up a folder). New to Git? The Git Guide covers it.

Stage 2: Containers (Docker)

2

Package apps so they run anywhere

Docker packages an app with everything it needs into a "container" that runs the same on any machine. It solves "but it works on my laptop." This is the single most useful DevOps skill to learn first.

Images vs containersDockerfiledocker build / runVolumesdocker-compose
# A tiny Dockerfile for a Node app
FROM node:20-alpine
WORKDIR /app
COPY . .
RUN npm install
CMD ["node", "server.js"]
Build: containerize one of your own apps, then run it with docker run. Bonus: use docker-compose to run the app plus a database together.

Stage 3: CI/CD (automate build & deploy)

3

Ship automatically on every push

CI/CD means: every time you push code, a pipeline automatically tests it and (if it passes) deploys it. GitHub Actions is free and the easiest place to start.

GitHub ActionsPipelinesAutomated testsBuild & deploy steps
# .github/workflows/ci.yml (runs tests on every push)
name: CI
on: [push]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm install
      - run: npm test
Build: add a GitHub Actions workflow to one of your repos that runs your tests on every push, then extend it to auto-deploy to a free host.

Stage 4: One cloud provider

4

Run things on real infrastructure

Pick one cloud (AWS is the market leader; Azure and GCP are close cousins) and learn the core services. Do not try to learn all three, the concepts transfer.

Compute (EC2 / VMs)Storage (S3 / blobs)Networking basicsIAM & permissionsManaged databases
Build: deploy your Dockerized app to a cloud free tier. Then try a free-tier database and connect to it. A foundational cert (AWS Cloud Practitioner) is a solid, resume-friendly goal here.

Stage 5: Infrastructure as Code & Kubernetes

5

Scale it up (once the basics click)

These are the "advanced but valuable" skills. Infrastructure as Code (Terraform) lets you define servers in files instead of clicking around. Kubernetes runs and scales many containers. Learn these after you are comfortable with stages 1 to 4, not before.

TerraformKubernetes basicsMonitoring & logsSecrets management
Build: use Terraform to create one cloud resource from code. Then deploy a container to a small Kubernetes cluster (minikube runs one locally for free).

A sensible learning order

If you remember one thing: go in order and do not skip ahead. A common mistake is jumping straight to Kubernetes before understanding Linux, Git, and Docker, which makes everything confusing.

Linux & Git โ†’ Docker โ†’ CI/CD โ†’ one Cloud โ†’ Terraform & Kubernetes. Each stage makes the next one make sense.

Free places to learn

What to do next

๐ŸŒฑ What even is DevOps?

In plain words: DevOps is the set of practices and tools that get code from your laptop into the hands of users, quickly and reliably. Instead of "write code, throw it over the wall," one flow builds, tests, ships, and runs it. You do not need all of it at once, follow the stages below. Stuck on a concept? Tap โœฆ Ask AI.