Cheat sheet · Specialise
DevOps and cloud cheat sheet
Opens with creditsA quick-revision companion to the DevOps and cloud roadmap: Linux, networking, containers, AWS, Terraform, CI/CD, Kubernetes and observability in one place. Use it to refresh a command or concept before you touch a server, a pipeline or a cluster.
Chapters
10 chapters · 79 concepts
1Linux, the shell and scriptingAlmost every server, container and pipeline runner is Linux. These are the commands and ideas you use daily.8 concepts
- 1File permissionsEach file has an owner, a group and read, write and execute bits for owner, group and others.
- 2Users, groups and sudoLinux runs everything as some user.
- 3Processes and signalsA process is a running program with a PID.
- 4systemd servicessystemd is the init system on most distributions.
- 5System logssystemd collects service output in the journal, read with
journalctl. - 6Pipes, grep, sed and awkA pipe
|sends one command's output into the next. - 7Safe Bash scriptsA Bash script is a file of commands with a shebang line.
- 8cron and systemd timerscron runs commands on a schedule written as five fields: minute, hour, day of month, month, day of week. systemd timers do the same with logging and dependency…
8 in this chapterOpen this chapter2Git workflowsEverything in DevOps, from app code to infrastructure and pipeline definitions, lives in Git and changes through reviewed commits.6 concepts
- 1Branches and pull requestsA branch is a movable pointer to a line of commits.
- 2Merge vs rebase
git mergejoins histories with a merge commit. - 3Trunk-based developmentEveryone merges small changes into one main branch at least daily, hiding unfinished work behind feature flags.
- 4Undoing changes: revert vs reset
git revertadds a new commit that undoes an earlier one. - 5Tags and semantic versioningA tag names a specific commit, such as
v2.4.1. - 6.gitignore and secrets in Git
.gitignorelists files Git should not track, such as.env, build output and Terraform state.
6 in this chapterOpen this chapter- Networking for engineersHow traffic finds your servers and what to check when it does not. Most outages that look like app bugs are DNS, ports, firewalls or certificates.8 conceptsOpens with credits
- Containers with DockerPackage an app with everything it needs so it runs the same on a laptop, in CI and in production.9 conceptsOpens with credits
- Cloud on AWS: the core servicesThe AWS services nearly every workload uses. The ideas carry over to Azure and Google Cloud under different names.11 conceptsOpens with credits
- Infrastructure as code with TerraformDescribe infrastructure in versioned files, review changes as plans, and rebuild environments the same way every time.6 conceptsOpens with credits
- CI/CD pipelinesAutomate the path from a commit to production so every change is built, tested and deployed the same way.7 conceptsOpens with credits
- Kubernetes and GitOpsRun containers across a cluster of machines with self-healing, scaling and rollouts, and keep the cluster in sync with Git.10 conceptsOpens with credits
- Observability and incident responseSee what production is doing, get paged only for what matters, and learn from every incident.8 conceptsOpens with credits
- Security basicsThe habits that prevent most real-world breaches in cloud and DevOps work.6 conceptsOpens with credits
- 11Glossary, A to ZEvery concept in the sheet and the smaller terms it uses, in one list.221 terms
About this sheet
Linux, Docker, Kubernetes, AWS.
Related on Sefism
Picked from the other libraries by shared topics.
Roadmaps
See allBest practices
See all- Kubernetes Best PracticesRun workloads on Kubernetes that schedule well, survive restarts and node drains, and stay locked down: resources, probes, PDBs, Pod Security and RBAC.
- Terraform Best PracticesWrite Terraform that teams can review and change safely: file layout, version pinning, remote state with locking, secrets, modules, refactoring and tests.
- CI/CD Best PracticesBuild pipelines that are fast, trustworthy and safe to deploy from: trunk-based flow, fast tests, locked-down workflows, signed artifacts, canaries and DORA metrics.
Checklists
See all- Incident Response ChecklistPrepare for and handle production incidents: on-call, severity levels, declaring, roles, mitigation, security containment, status updates and blameless postmortems.
- Production Readiness ChecklistCheck a service before it takes real traffic: ownership, SLOs, capacity, timeouts and retries, alerts, rollout and rollback, backups, security and on-call.
- Kubernetes Production ChecklistVerify a workload and its cluster before real traffic: requests and limits, probes, PDBs, spread, Pod Security, RBAC, network policies, secrets, images, autoscaling, upgrades and backups.
Project structures
See all- Terraform project structureAn infrastructure repository for a small app on AWS: reusable modules, one folder per environment with its own remote state, pinned providers, tests and security scans, with plan on every pull request and apply from CI. For students who have finished the Terraform tutorials and want to know how a real team lays out the files. The same layout works unchanged with OpenTofu.
- Kubernetes with Helm project structureA Helm chart repository for one app: the chart that
helm creategives you, grown into a tested, versioned package with per-environment values, unit tests, install tests in a kind cluster and releases to an OCI registry. For students who can write a Deployment by hand and want to know how a team organises charts. It is about the repo layout and what each file does, not about cluster design. - Spring Boot project structureA REST API in Java with Spring Boot 4, PostgreSQL, Flyway and Testcontainers, organised by feature the way the Spring docs suggest. It grows from the Initializr scaffold to a service with JWT security, problem-detail errors, MapStruct DTOs, slice and integration tests, CI, containers and observability, and finally Modulith boundaries, contract and load tests. For students who know some Java and want to see how a real service is organised.
Career questions
See all- Do I need Docker and Kubernetes as a junior developer?Docker, yes: learn the basics, because nearly every team uses containers and you will be expected to run the project locally and read a Dockerfile. Kubernetes, mostly no: understand what it does and a few core terms, but deep Kubernetes can wait until your job or a DevOps direction needs it.
- What is platform engineering, and how is it different from DevOps?DevOps is a culture and set of practices: developers and operations sharing responsibility for shipping and running software. Platform engineering is one way to put that into practice at scale: a team builds an internal platform, a paved road of tools and templates, so product teams can ship without becoming infrastructure experts.
- Can I become an SRE or platform engineer straight after graduating?Sometimes, but it is rare, because these roles expect you to have run production systems. The more reliable path is a first job in backend, DevOps or cloud support, where you learn production, then a move into SRE or platform work within a couple of years.
Cheat sheets
See allWork with me
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com