i've used both CFN and TF on the same infra so i think i have a reasonable (although dated by 1 yr) perspective on this. my main gripe with CFN is that when th

i've used both CFN and TF on the same infra so i think i have a reasonable (although dated by 1 yr) perspective on this. my main gripe with CFN is that when things get into a weird state, it is extremely difficult to do anything about it. You are basically stuck waiting at the hands of the black magic box of AWS to either revert or complete the change set. i found that TF was much more clear about what went wrong when a changeset got into a bad state. i've also had no problems using AWS services via TF, with the added bonus that it's easy to get heterogeneous cloud deployments working.