AWS CDK vs Terraform
<p>IaC is one of the key DevOps practices, and AWS CDK & Terraform are both great IaC tools to manage your AWS infrastructure. Having used both extensively, let me share my experience with the 2 IaC tools.</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:700/1*QpQy9WAtRjUsR78A3NuOWg.png" style="height:278px; width:700px" /></p>
<p>AWS CDK vs Terraform</p>
<h2>Import Existing Resources</h2>
<p>There could be many scenarios where we will have existing cloud resources that are not managed via IaC. In environments where you start the IaC journey, the whole cloud infrastructure has to be imported into IaC first. Though it is a time consuming step, it brings your infrastructure into version control and makes future changes easier.</p>
<p>Importing resources in CDK is done so we can refer and change some of its properties, and it does not mean that the main resource itself becomes part of IaC. For example: to change permissions of existing s3 bucket, you can import an existing bucket. Let’s say you want to bring the existing s3 bucket into IaC first, CDK is not the tool for that.</p>
<p><a href="https://medium.com/@kansvignesh/aws-cdk-vs-terraform-738c39d91f7a"><strong>Read More</strong></a></p>