What do you think of using your preferred programming language to provision your infrastructure?
AWS CDK (Cloud Development Kit), based on CloudFormation has been released a couple of years to achieve that.
As a big fan of Terraform, I had a keen interest in the CDKTF project which aims at using AWS CDK with Terraform.
Before jumping into CDKTF, let's revisit some fundamentals concepts.
Infrastructure as code (IaC) is basically, the process of managing and provisioning IT resources (in the cloud or not), through definition files or code rather than manual or interactive configuration.
The main objective is to provide a centralized way to manage configuration in terms of implementation and version control. Hereby, all changes can be validated, tested, and provisioned as part of a release process using standard deployment pipelines.
There are many benefits to using IaC for your next project:
- Speed and safety: You expend a lot less effort on simple and repetitive tasks.
- Documentation: You can easily document your code like any software project.
- Testing: You can write tests for your project.
Now that, we know what IaC is, let's talk about Terraform which is the most popular Iac tool out there!
Terraform is an open-source tool created by HashiCorp in 2014. It allows you to define the infrastructure as code using a simple, declarative language called HCL (stands for Hashicorp Configuration Language) to deploy and manage that infrastructure across a variety of public cloud providers (e.g., Amazon Web Services, Microsoft Azure, Google Cloud Platform, DigitalOcean), private cloud and virtualization platforms.
If you want to deep dive into Terraform, I recommend the excellent book: Terraform: Up & Running by O'Reilly.
The AWS Cloud Development Kit (AWS CDK) is an open-source framework initiated by AWS to define your cloud infrastructure in code and provision it through AWS CloudFormation.
Using the familiarity and expressive power of current programming languages, It provides high-level components called constructs that preconfigure cloud resources with proven defaults, so you can build cloud applications with ease.
You will find more information in the documentation
Cloud Development Kit for Terraform (CDKTF) is the fruit of a partnership between Hashicorp and AWS teams for leveraging the Terraform ecosystem to define and provision your infrastructure. This allows you to use Terraform without learning HashiCorp Configuration Language (HCL).
CDKTF currently supports TypeScript, Python, Java, C#, and Go (experimental).
More information from the documentation
For this tutorial, we will use Python.
Python is one of the most easiest languages to learn and is really helpful to write scripts and automate tasks quickly. If you are new in Python, I recommend you this platform to get started.
To use cdk with terraform, you must run the following command:
$ npm install --global cdktf-cli@latest
This installs the cdktf CLI that allows to spin up new projects for various languages.
We can scaffold a new python project by running:
$ mkdir s3-demo && cd s3-demo $ cdktf init --template="python" --local
We use the option --local to indicate that we will use local state storage for generated Terraform.
In a real project, it is recommended to use a remote backend.
There are many files created by default.
For our demo, we will use AWS as cloud provider so we need to install the required provider.
$ pipenv install cdktf-cdktf-provider-aws
You can edit the
main.py at the root of the project and add the code below:
#!/usr/bin/env python from constructs import Construct from cdktf import App, TerraformOutput, TerraformStack from cdktf_cdktf_provider_aws import AwsProvider, s3 # Define your stack class MyStack(TerraformStack): def __init__(self, scope: Construct, ns: str): super().__init__(scope, ns) # Configure the AWS provider to use the eu-west-3 region AwsProvider(self, "AWS", region="eu-west-3") # Create your first bucket # pass the id of the resource and the name of the bucket first_bucket = s3.S3Bucket( self, "first_bucket", bucket="blog.abdelfare.me", acl="public-read" ) TerraformOutput(self, "bucket_name", value=first_bucket.bucket) TerraformOutput(self, "bucket_arn", value=first_bucket.arn) app = App() MyStack(app, "s3-demo") app.synth()
I found the SDK really intuitive.
Basically, We created our
Main Stack inherited from the
TerraformStack class. We set up the aws provider (Don't forget to define the AWS profile) and We create our first S3 bucket in one line of code.
TerraformOutput allows to export some values and reuse them in another stack.
Now that, everything is ready, we can generate the terraform configuration files by running the command below:
$ cdktf synth
We can deploy our stack by running the command:
$ cdktf deploy
This command runs
terraform apply in the background.
We can see all the new changes and confirm the execution.
There we go!
Our bucket was created successfully.
We can see the output of your stack by using the following command:
We can now destroy our stack by running the command:
$ cdktf destroy
CDKTF offers many benefits, but it is not the right choice for every project. You should consider using CDKTF when:
- You have a strong preference or need to use a procedural language to define infrastructure.
- You need to create abstractions to help manage complexity.
- You are comfortable doing your own troubleshooting and do not require commercial support.
Some pain points to consider:
- Initial CDK setup is time consuming
- Deployment times can be slow due to the synthesizing steps
Do you have any experience with CDKTF? Have you used it in production?
Feel free to share you experience with us in comment.
You could find the code of this article on my github repo.
In a next article, I will set up a full containerized architecture with *ECS, Fargate, ECR, ALB, CDK + Terraform so stay tuned 😃!*