They're similar in that they both have a way to build a desired state for your infrastructure and some code for executing the changes to make that happen. In T

They're similar in that they both have a way to build a desired state for your infrastructure and some code for executing the changes to make that happen. In Terraform you describe the desired state using a fairly limited language called HCL which looks a lot like a config file. In Pulumi you describe the state by running some code in a normal language and building objects to describe the state. This means you can use features of normal programming languages to abstract your state more thoroughly - stuff like functions, data structures, loops, etc. AWS and Terraform actually have a similar thing to Pulumi called CDK which uses a normal language to build either CloudFormation or HCL. This gives a lot of the benefits of Pulumi, but lets use use a more widely used tool like Terraform underneath. https://www.terraform.io/cdktf https://www.terraform.io/cdktf (still in development) https://aws.amazon.com/cdk/ https://aws.amazon.com/cdk/