# random


11/07/2021, 5:35 PM
yeah used it for years prior to moving to cdk


11/07/2021, 10:44 PM
yeah, we’ve got quite a bit set up with terraform

Joe Kendal

11/08/2021, 12:09 AM
I used it before discovering CDK. The benefit is fast deployment compared with CloudFormation. The disadvantage is HCL being dreadful (there is CDKTF in preview) and having to roll-your-own state management.
If you’re using AWS, just go with CDK as it does some of the IAM for you automatically. With Terraform you have to hardcode all the IAM and it is very time consuming. Only use Terraform if working with any cloud besides AWS.

Simon Reilly

11/08/2021, 10:23 AM
Adding to this. Terraform is more declarative, meaning you get exactly what you ask for, provisioned for you by the aws-sdk for golang (mostly). Terraform in my experience is better for very large organisations that need a unified deployment e.g. if you are running multi-account with SSO. Cdktf is not great unfortunately, it doesn't get the rich intellisense that aws-cdk benefits from, it mostly just knows the shape of the struct, and the string values. They are working on an adapter to work cdktf into aws-cdk. Hopefully that would mean cdk level type hints, with Terraform grade deploy speed.


11/08/2021, 2:51 PM
Terraform is so much faster 😢

Kevin Baker

11/10/2021, 11:33 PM
We use terraform for all our IaC on Azure. Pretty amazing
If SST ever wanted to support Azure and other clouds seems like an interesting option to explore CDKTF…