If you are on GCP or Azure you definitively want to use terraform, because alternative is either POS or doesn't exist. TF actually doesn't have much edge over

If you are on GCP or Azure you definitively want to use terraform, because alternative is either POS or doesn't exist. TF actually doesn't have much edge over CF. When TF was released it fixed many pain points of CF, but since then CF fixed those problems. The supposedly killer feature that you can use TF with multiple clouds is not that killer, since each cloud architecture is different so you can't just reuse your code. With CF you have extra benefits: - built in, no extra tool necessary - integral part of AWS, so no need to worry about being discontinued - available within AWS support - no need to worry about synchronizing state between people - import / export functionality, you can expose various variables, which following stacks can build on top of - ability to implement custom states with lambda - uses YAML or JSON, which means you can use existing tooling to generate config programmatically. Haven't used yet, but it appears that CDK is built on top of that, and that's much more powerful than terraform.