Roadmap

Resources

Cloud Engineering and DevOps in 12 weeks: free or official resources, in the order I follow them. Each week has a goal, a few focused links and a concrete outcome.

  1. Week 01Linux and the terminal4 links

    GoalLearn to use the terminal and manage files, permissions, processes and environment variables.

    OutcomeA comandi-linux.md file with at least 15 commands explained and tested.

  2. Week 02Networking basics and Git5 links

    GoalUnderstand IP, DNS, ports, HTTP/HTTPS and code versioning.

    OutcomeThe CloudOps Lab GitHub repository with a README and a browser → DNS → IP → port → application diagram.

  3. Week 03Docker and Docker Compose5 links

    GoalBuild images, run containers and manage services.

    OutcomeA working Dockerfile and compose.yaml for the API.

  4. Week 04FastAPI, APIs and databases5 links

    GoalBuild an API with validation, a database and automated tests.

    OutcomeAn API with a /health endpoint, sample data, a SQLite database and at least four tests.

  5. Week 05AWS fundamentals and costs7 links

    GoalUnderstand cloud services, IAM, AWS networking and the pricing model.

    OutcomeA minimal AWS diagram with the reasoning behind each choice and a cost estimate.

  6. Week 06First AWS deployment3 links

    GoalPublish a minimal version of the API and check that it is reachable from outside.

    OutcomeA /health endpoint reachable from outside, or a documented deployment report.

    Before you startBefore creating resources, check costs with the Pricing Calculator, review network rules (security groups and open ports) and prepare the steps to delete everything when you are done.

  7. Week 07CI/CD with GitHub Actions4 links

    GoalRun the tests automatically on every code change.

    OutcomeA workflow that runs the Python tests on every push and pull request.

  8. Week 08Logging, monitoring and security5 links

    GoalDiagnose errors, observe the service and protect its configuration.

    OutcomeReadable logs, a health check, error handling and a runbook to diagnose and restart the service.

  9. Week 09Terraform and Infrastructure as Code5 links

    GoalDescribe infrastructure in versioned files and review changes before applying them.

    OutcomeAn infra/ folder with a documented example and an explanation of init, validate, plan, apply and destroy.

    Before you startAlways read the terraform plan output before apply, and never commit state files or credentials to the repository.

  10. Week 10Reliability, backups and costs5 links

    GoalDesign services with failures, data recovery, scalability and running costs in mind.

    OutcomeA docs/operations.md document with failure scenarios, diagnostic checks, a backup strategy and a cost estimate.

  11. Week 11AWS Cloud Practitioner preparation5 links

    GoalConsolidate AWS concepts and assess readiness for the exam.

    OutcomeTwo practice runs, an error log and a reasoned decision on whether to book the exam.

    Before you startPrice, available languages, syllabus and booking options can change: check them on the official certification page before deciding.

  12. Week 12Portfolio, documentation and applications5 links

    GoalTurn the work done into a reproducible, presentable project.

    OutcomeA clean repository, a complete README, a diagram, verified instructions, a demo, an article and a project description for the CV.

Cross-cutting resources

References that stay useful for the whole path.