Terraform and Infrastructure as Code roadmap
Describe whole cloud environments in code and change them safely.
3 to 4 months at 8 to 10 hours a week4 stages16 topicsSome experience helps
All roadmapsInfrastructure as code means your servers, networks and permissions live in Git and are reviewed like any other code. Terraform is the most widely used tool for it across AWS, Azure and Google Cloud. This path takes you from your first resource to modules, team workflows and policy.
Where you will end up
You can build and change real cloud environments with Terraform, organise code into modules, run it safely from a pipeline with remote state, and you are ready for the Terraform Associate exam.
Before you start
- Basic Git
- Some experience with one cloud provider (see the AWS, Azure or Google Cloud roadmaps)
Roles it leads to
- DevOps Engineer
- Cloud Engineer
- Platform Engineer
- 1
First steps
2 weeks0 of 4 done
Create, change and destroy infrastructure from code.
Prove it
A network from code
Create a VPC or VNet with two subnets and a VM, change one setting and read the plan, then destroy everything cleanly.
- 2
State and data
2 weeks0 of 4 done
Understand state, the part that bites teams most.
Prove it
Adopt something real
Import a resource you created by hand, move state to a locked remote backend, and refactor a resource name with a moved block and no downtime.
- 3
Modules and reuse
3 weeks0 of 4 done
Write code other people can use.
Prove it
One module, three environments
Package your network and app as a module and deploy it to dev and prod with different sizes from the same code.
- 4
Team workflows
3 weeks0 of 4 done
Change production safely as a team.
Prove it
A reviewed change to prod
Set up a pipeline where a pull request shows the plan, a policy check fails on a public bucket, and apply happens only after approval.
Certifications that fit
Optional, and never a substitute for projects. Exam details change, so confirm on the official page before you book.
The honest part
Terraform is easy to start and easy to hurt yourself with. Always read the plan, keep state remote and locked, and practise destroying and rebuilding environments until it feels boring. OpenTofu, the open-source fork, uses the same language, so the skills carry over.
Checked against
Written by CloudIskole and reviewed against the official sources below. Last verified November 2026. Spotted something out of date? Tell us and we will fix it.
These roadmaps are our own work. For another community view of learning paths, see roadmap.sh, which inspired the idea of a visual guide.


