⬡
The Axiom
Learning Path11 topics · ~7h

Cloud Engineer

AWS, containers, Kubernetes, infrastructure as code, and the failure modes, networking, and cost engineering that senior roles require.

  1. Cloud

    Cloud Engineering Brain

    Central hub for all cloud and platform engineering knowledge. Every page in the Cloud brain connects here.

  2. Cloud

    AWS Core Services

    The foundational services every cloud engineer needs to know. AWS dominates cloud (33% market share, 2026). These ten services underpin the vast majority of production architectures.

    ↳ The essential AWS services

  3. Cloud

    Docker

    Container runtime. Packages an application and its dependencies into a portable, reproducible image that runs identically in dev, CI, and production.

    ↳ Containers first

  4. Cloud

    Kubernetes

    Open-source container orchestration. Declare desired state; the control plane makes it so and keeps it so. The standard production substrate for containerised workloads.

    ↳ Orchestration at scale

  5. Cloud

    Terraform

    Infrastructure as Code tool by HashiCorp (now part of IBM, with community fork OpenTofu under MPL 2.0). Declare infrastructure in HCL, run plan-apply-destroy.

    ↳ Infrastructure as code

  6. Cloud

    Cloud Security

    Securing AWS infrastructure: IAM least privilege, preventive controls (SCPs, resource policies), detective controls (GuardDuty, CloudTrail, Security Hub), and network security (WAF, Security Groups, N...

  7. Cloud

    GitHub Actions

    CI/CD built into GitHub. Triggered by events (push, PR, schedule, manual). Runs jobs in parallel or sequence across GitHub-hosted or self-hosted runners.

    ↳ CI/CD pipelines

  8. Cloud

    Cloud Networking

    Network design underpins security, performance, and cost in cloud architectures. The same concepts — VPC, subnets, routing, firewalls — appear in all three major clouds with different names.

    ↳ VPC flow, DNS, request path from client to pod — most cloud issues are networking

  9. Cloud

    Disaster Recovery

    Planning and executing recovery from catastrophic failures — region outages, data corruption, ransomware, accidental mass deletion.

    ↳ What happens when a pod, node, or AZ fails — design for failure, not success

  10. Cloud

    Observability Stack

    The three pillars of observability: metrics (what's broken), logs (why it broke), traces (where it broke).

    ↳ Metrics, logs, traces together — how to debug incidents

  11. Cloud

    FinOps and Cloud Cost Management

    Engineering discipline for understanding, controlling, and optimising cloud spend.

    ↳ Right-sizing, scaling policies, waste detection

11 pages · ~7h estimated reading time

← Browse all topics