In many cases, the community treats Terraform as a sane default when it comes to the infrastructure as code. I can’t entirely agree with that statement, mainly if this is wrongly motivated. Today, I would like to present the unique selling points that show when using AWS CDK is a better-suited tool for the job.
This question popped into my mind recently. After several sessions with the AWS CDK, when I worked through typical tasks that we all do as a Cloud Architect/DevOps Engineers on AWS, I realized that in the Infrastructure as Code space, we did not arrive at any breakthrough recently.
Choosing the best tool for your Infrastructure as Code is not an easy task. From one hand you are aware of the risks coming from the cloud providers including vendor lock-in. From the other hand, external tools impose many limitations. How to wisely choose the proper one? Let’s find out!