Learn to provision, version and promote cloud resources with Terraform — modules, remote state, separate environments, safe secrets and automated deployments. Self-paced, hands-on, from an empty folder to a delivery pipeline.
Every manual change is a difference between what you think exists and what actually runs. Infrastructure as code removes the guesswork: the configuration is the source of truth, and the plan shows every difference before it happens.
By hand
Result: unknown. Reproducible: no.
resource "aws_s3_bucket" "logs" {
bucket = "app-logs-${var.env}"
tags = local.common_tags
}
# Same file. Every environment. Reviewed in Git.
Plan: 6 to add, 0 to change, 0 to destroy.
Writing a resource block is easy. Running real infrastructure from code depends on four things: reuse, a trustworthy record of state, clean separation between environments, and secrets that never leak.
fig.02 / module.reuse
Turn a working configuration into a module with typed inputs, useful outputs and a version tag. Then compose networks, services and databases from parts you trust instead of copying blocks between folders.
module "network" {
source = "./modules/network"
cidr = "10.20.0.0/16"
zones = 3
}
Understand what the state file holds and why it matters. Move it to a remote backend, enable locking so two applies never collide, and import, move or remove resources without recreating them.
terraform {
backend "s3" {
bucket = "ctc-tf-state"
key = "web/terraform.tfstate"
}
}
Promote one configuration through dev, staging and production with separate state and per-environment variables, so the differences are small, explicit and reviewed.
# envs/prod.tfvars instance_count = 3 instance_size = "large"
fig.04 / var.sensitive
Mark sensitive values, read credentials from a secrets manager or the CI environment, and keep them out of plan output, state snapshots and commit history.
variable "db_password" {
type = string
sensitive = true
}
The last module turns everything into a pipeline: every change is planned in CI, reviewed as a diff, and applied exactly as approved.
01
commit
Configuration changes land in Git as a pull request.
02
plan
CI runs fmt, validate and plan, and posts the diff.
03
review
A human reads the plan, not a guess about it.
04
apply
On merge, the exact reviewed plan is applied.
Each module ends with a hands-on lab, and each lab adds a piece to the same infrastructure — so by the end you have built the whole system, not seven separate demos.
7 modules · 28 lessons · 7 labs
Provision your first bucket and network from an empty folder.
Parameterise a web server stack without duplicating a single block.
Extract a reusable network module and consume it twice.
Migrate local state to a locked remote backend and import a hand-made resource.
Run one configuration as dev, staging and production.
Wire a database password end to end without it ever touching Git.
Build a pipeline that plans every pull request and applies on merge.
Course projects pull the modules together into infrastructure you could run. The plan excerpts below are examples of the output you will produce.
project 01
A VPC with public and private subnets across zones, packaged as a versioned module with documented inputs and outputs.
+ module.network.aws_vpc.main+ module.network.aws_subnet.private[0..2]+ module.network.aws_subnet.public[0..2]Plan: 9 to add, 0 to change, 0 to destroy.
project 02
Load balancer, compute and a managed database, deployed to dev, staging and production with remote, locked state.
~ aws_autoscaling_group.web desired_capacity: 2 → 3+ aws_db_instance.mainPlan: 1 to add, 1 to change, 0 to destroy.
project 03
CI that formats, validates and plans every pull request, posts the plan for review, and applies the saved plan on merge.
terraform fmt -check ✓terraform validate ✓terraform plan -out=tfplanNo changes. Your infrastructure matches the configuration.
For you if
Not for you if
What you need
Self-paced lessons and written labs. No schedules or live sessions — access is granted after payment.
One-time payment. Self-paced access is granted right after payment, and you can upgrade between plans later.
plan.plan
The fundamentals, end to end.
$129 one-time
plan.apply
RecommendedThe complete course.
$229 one-time
plan.apply_pipelines
Everything, plus production templates.
$349 one-time
You should be comfortable with a terminal, Git basics and the general idea of cloud resources such as servers and networks. No prior Terraform experience is required.
Labs are written against AWS because it is the most common target. The concepts — modules, state, environments, secrets and pipelines — work the same way with other providers, and lessons point out where things differ.
The course uses Terraform. OpenTofu is a compatible fork, and almost everything you learn applies to it unchanged.
Labs are designed around small, short-lived resources, and every lab ends with a destroy step. Your provider may still charge for usage, so check its pricing and clean up after each session.
Access is granted right after payment. You sign in with the email you used at checkout and can start with module 01 immediately.
There are no cohorts, schedules or live sessions. Lessons and labs are self-contained, so you can move through them at whatever speed fits your work.
Still unsure? Ask us directly.
No changes. Your infrastructure matches the configuration.
Seven modules, three projects and a pipeline you can reuse at work. Start whenever you are ready.
