Foray

Cloud Engineer roadmap

Design, build and run workloads in the cloud: the operating system and network underneath, then accounts, compute, storage, data, security, infrastructure as code and cost. Taught on AWS; the ideas carry to other clouds.

14 topics · 60 nodes · 56 covered · 1 partly · 3 planned · updated 2026-10-17

Sign in with your Mycelium account to see which nodes you have finished.

Show
  • Covered
  • Partly covered
  • Planned
  1. 1. Core

    Linux and the shell

    Almost every cloud server runs Linux. Learn to move around it, manage access and run services before you rent machines.

    4 / 4 covered

  2. 2. Core

    Networking for the cloud

    A cloud is a network you configure. Addresses, DNS, routing and TLS come up in every design.

    6 / 6 covered

  3. 3. Core

    Cloud foundations on AWS

    Accounts, identity and the habits that keep a new account safe and affordable.

    5 / 5 covered

  4. 4. Core

    Compute and storage

    Where code runs and where data sits.

    5 / 5 covered

  5. 5. Core

    Networking on AWS

    VPCs, private subnets, DNS and content delivery.

    4 / 4 covered

  6. 6. Recommended

    Data and messaging

    Managed databases, caches and the queues that decouple services.

    3 / 4 covered

  7. 7. Recommended

    Serverless

    Run code without managing servers, and know where it stops being the right tool.

    4 / 4 covered

  8. 8. Core

    Infrastructure as code

    Describe the cloud in files, review it like code and rebuild it on demand.

    5 / 5 covered

  9. 9. Core

    Security and identity

    Least privilege, secrets, encryption and the services that watch for trouble.

    4 / 4 covered

  10. 10. Recommended

    Delivery and automation

    Ship changes to the cloud through a pipeline, not by hand.

    4 / 4 covered

  11. 11. Core

    Monitoring and operations

    Know when it is broken and why.

    4 / 4 covered

  12. 12. Recommended

    Reliability and recovery

    Survive failure: backups, failover and designing for the outage you have not had yet.

    4 / 4 covered

  13. 13. Core

    Cost management

    Cloud spend is an engineering concern: understand the bill, then shrink it.

    4 / 4 covered

  14. 14. Optional

    Other clouds

    The concepts transfer; the names and defaults do not.

    0 / 3 covered