[strangelove026]

My preferred tool.

A few of the biggest selling points (for me):

- It feels like writing code instead of writing yaml.

- To the above you can define your own parameter object types in Terraform. To create a list parameter in cloudformation requires `CommaDelimitedList` which can only contain strings.

- To the above two points, your Terraform stacks can be DRY'd up a bit which makes them easier to read than a massive 1000 line cloudformation file.

- Terraform is run completely in your console which is faster and improves the developer experience.

- Resources are never "conditionally" replaced. They either are or are not. Don't know if this is still a thing in Cloudformation land but the resources change diff Terraform gives you is completely clear.

That all said I don't mind writing Cloudformation, but (again in my opinion) Terraform is vastly more powerful.

[tracer4201]

I’ll try it out. I’ve been writing CloudFormation and using SAM templates for some recent projects involving Lambda. Defining my general resources is easy enough but having to define through IAM roles and policies turns into a real pain super quick.