Foray / Infrastructure Automation EngineerInfrastructure Automation Engineer roadmap Replace manual operations with code: scripts, Terraform, Ansible, pipelines and GitOps, tested, secured and observable, so infrastructure can be rebuilt and changed safely by anyone on the team.
14 topics · 66 nodes · 63 covered · 1 partly · 2 planned · updated 2026-10-17
Sign in with your Mycelium account to see which nodes you have finished.
Show Whole map Gaps only 1. Core
Systems foundations You automate what you understand. The minimum operating-system and network knowledge automation depends on.
3 / 3 covered
Linux essentials Covered SSH for automation Covered Networking essentials Covered 2. Core
Version control Infrastructure lives in Git: history, review and rollback for free.
4 / 4 covered
Git basics Covered Branching and release policy Covered Pull requests and conflicts Covered Branch protection and hooks optional Covered 3. Core
Shell scripting The glue of operations. Write scripts that are safe to run twice.
5 / 5 covered
Bash fundamentals Covered JSON, curl and APIs Covered ShellCheck and testing Covered Robust scripts Covered Idempotency, locking and retries Covered 4. Core
Python for operations When a script outgrows Bash: structured data, APIs and real command-line tools.
6 / 6 covered
Environments and packaging Covered Command-line tools Covered Cloud automation with boto3 Covered Files, processes and structured data Covered HTTP APIs and retries Covered Testing and production quality Covered 5. Core
Infrastructure as code with Terraform Declare infrastructure, plan the change, apply it, repeat.
7 / 8 covered
The core workflow Covered State Covered Drift and lifecycle Covered Pulumi and the CDKs pick one Planned The language Covered Modules and project layout Covered Multi-account and migrations Covered Infrastructure as code on AWS optional Covered 6. Core
Configuration management with Ansible Configure what Terraform created, and keep it configured.
6 / 6 covered
Ansible fundamentals Covered Roles and project layout Covered Advanced Ansible optional Covered Modules, variables and templates Covered Safe operations Covered Ansible with Terraform and images Covered 7. Recommended
Containers and images Build once, run anywhere: images are the unit most automation ships.
3 / 4 covered
Docker fundamentals Covered Images in CI and registries Covered Reliable image builds Covered Building machine images with Packer optional Planned 8. Core
CI/CD automation Every change flows through a pipeline: build, test, plan, deploy.
6 / 6 covered
Pipeline basics Covered Reusable workflows and actions Covered Infrastructure code in CI Covered Pipelines for real projects Covered Deploying with environments and approvals Covered Pipeline design and reliability optional Covered 9. Core
GitOps Git is the source of truth; controllers make reality match it.
5 / 5 covered
What GitOps is Covered Repository structure and templating Covered Fleets, infrastructure and recovery optional Covered Argo CD and Flux Covered CI and GitOps together Covered 10. Core
Testing and quality for infrastructure Infrastructure code deserves the same checks as application code.
4 / 4 covered
Linting and validation Covered Policy and scanning Covered Automated tests Covered Testing pipelines themselves optional Covered 11. Core
Secrets and security for automation Automation holds the keys to everything. Protect them.
4 / 4 covered
Secrets in scripts and code Covered Securing pipelines Covered Ansible Vault and securing automation Covered Securing GitOps and secrets in GitOps Covered 12. Recommended
Release automation Automate how changes reach users, and how they are undone.
4 / 4 covered
Deployment strategies Covered Database migrations Covered Feature flags and progressive delivery Covered Artifacts and versioning Covered 13. Recommended
Self-service and platform Automation other teams can use without asking you.
3 / 3 covered
Golden paths Covered Developer portals optional Covered Self-service infrastructure Covered 14. Recommended
Operating what you automate Automation fails too. Monitor it, back it up and keep it cheap.
3 / 4 covered
Monitoring automation Covered Cost guardrails optional Covered Backups and state recovery Covered Automating Kubernetes optional Partly covered © 2026 Konstantinos Maglaras
