Python Terraform CDK — ELI5

Imagine you want to build a whole city — houses, roads, parks, power lines. You could describe everything in a giant list: “one house here, one road there, connect power line A to B.” That is how Terraform normally works — you write a list of what you want, and Terraform builds it.

But what if you could draw the city using real building tools instead of just a list? What if you could say “build 10 houses in a row, each slightly bigger than the last” using a loop, instead of writing out each house individually?

That is what the Terraform CDK (Cloud Development Kit) does. It lets you use Python — a real programming language — to describe your cloud infrastructure. Instead of learning a special configuration language called HCL, you write normal Python code with loops, conditions, functions, and variables.

Why does this matter? A company might need 50 servers, each with a slightly different setup. With regular Terraform, you would copy and paste 50 blocks and edit each one. With CDK for Python, you write a loop: “for each server, create one with these settings, but change the name and size.” One block of code instead of fifty.

Companies like HashiCorp (the makers of Terraform) created CDK because many developers already know Python. Instead of learning a new language, they can use the language they are comfortable with to manage cloud resources on AWS, Google Cloud, Azure, and more.

The CDK generates regular Terraform files behind the scenes. So you get the best of both worlds: Python’s power for writing the code, and Terraform’s reliability for actually building the infrastructure.

The one thing to remember: Terraform CDK lets you use Python to describe cloud infrastructure — bringing loops, functions, and real programming power to something that used to require static configuration files.