Strongly agree. Support for new AWS features hits Terraform much faster than CloudFormation (still waiting for CF support for AWS&#x27;s managed ElasticSearch service that was unveiled two months ago--Terraform got it right away). Some of the critiques below are true... HCL is fine, but Terraform&#x27;s interpolation syntax has a long way to go. That said, CF&#x27;s JSON is way more painful to deal with. As for the other problems, they go back mainly to someone using a tool they don&#x27;t fully understand. Yes you can get into some odd states in rare cases, but Terraform gives you the ability to rapidly build and tear down your infrastructure over and over if necessary to work out details and you have fine-grained control over which pieces are built how. Not only that but you can inspect the logs to see what&#x27;s happening and if there are bugs, <i>you can fix them</i> yourself because the tool is open source and free. CloudFormation gives zero visibility, no fine-grained control, and it&#x27;s completely opaque and where it&#x27;s broken, you can&#x27;t fix it.<p>Terraform is relatively new and improving rapidly. It has its problems, but it&#x27;s light-years beyond CloudFormation. It&#x27;s clear that Amazon doesn&#x27;t place a high priority on making CloudFormation easy to use, or to support new features. The right approach to any problems with Terraform is not to spread FUD about it like below, but to contribute code fixes.