adesso Blog

Even if you are a seasoned AWS CDK/CloudFormation veteran, it has most likely happened to you that you tried to work with a resource that was not yet available in CDK/CloudFormation (looking at you Lake Formation). Luckily if the resource and the accompanying operations are available through the AWS API then you are in good luck as AWS has a way to incorporate these API calls into your templates/code and bridge the gap created by the unavailability of some resources.

Modern IT has been full of buzzwords and groundbreaking approaches in the past few years. Infrastructure as Code (IaC) is the latter. IaC is the practice of defining your infrastructure through code templates rather than using a GUI or manual effort. Using IaC has several benefits, such as better reusability, CI/CD integration, etc.; but most notably: it helps you achieve greater speed by treating infrastructure like 'cattle' – not' pets.' While IaC tools have made a long way since they first emerged, and a few purpose-built languages have also popped up, the need to approach such things from traditional programming languages has never disappeared. Pulumi and CDK from AWS are such tools, and, in this blog post, we will be exploring the latter.