Praise: - Often beats AWS to support on new features. AWS is traditionally not very good at coordinating service releases between IAM, CloudFormation, and what

Praise: - Often beats AWS to support on new features. AWS is traditionally not very good at coordinating service releases between IAM, CloudFormation, and whatever. - Modules better than nested stacks - Much better insight into what's going to change. This still seems to be the case with CloudFormation's change sets.. Particularly with nested stacks, which were sent to earth to torment us. - Nicer configuration than CloudFormation Woes: - Juggling multiple state files. This seems to be necessary if you are going to stamp out infrastructure across accounts and regions; this is double true if you want to roll changes gradually across regions/accounts. Prepare to write wrappers. - Creating modules is the only wait to organize tf files into folders. This can really rub you the wrong way because modules are isolated from the root and other modules' variables. You have to start passing in and out resource references :| There was an import proposal made 7 days ago that looks very nice. - Not much in the way of rollbacks.. - Potentially less flexible than CloudFormation; CloudFormation offers wait conditions, conditionals, rollbacks, update cancellations(with rollback), etc