Install CDK for Terraform and run a quick start demo
The Cloud Development Kit for Terraform (CDKTF) generates JSON Terraform configuration from code in C#, Python, TypeScript, Java, or Go, and creates infrastructure using Terraform. With CDKTF, you can use hundreds of providers and thousands of module definitions provided by HashiCorp and the Terraform community. By using your programming language of choice, you can take advantage of the features and development workflows you are familiar with.
CDKTF uses the Cloud Development Kit from AWS, which provides a set of language-native frameworks for defining infrastructure, and adapters that let underlying provisioning tools use those definitions. CDK for Terraform generates Terraform configuration to provision infrastructure with Terraform. The adapter works with existing Terraform providers and modules, and integrates with HCP Terraform and Terraform Enterprise. CDKTF uses the core Terraform workflow, including planning and applying your infrastructure changes.
Follow this tutorial to install CDKTF and try a quick start example that provisions a Docker container.
Prerequisites
In order to use CDKTF, you need:
- The Terraform CLI (1.2+).
- Node.js and npm v16+.
To follow the quickstart, you also need:
- Docker.
- a recent version of the programming language prefer. Select a tab below to follow this tutorial with the version of your preferred language that we have tested.
Python v3.7 and pipenv v2021.5.29
Install CDKTF
You can install CDKTF with npm on most operating systems. You can also install
CDKTF with Homebrew on MacOS.
To install the most recent stable release of CDKTF, use npm install with the
@latest tag.
$ npm install --global cdktf-cli@latestVerify the installation
Verify that you have CDKTF installed by running the cdktf help command to show
the available subcommands.
$ cdktf helpcdktf Commands: cdktf init Create a new cdktf project from a template. cdktf get Generate CDK Constructs for Terraform providers and modules. cdktf convert Converts a single file of HCL configuration to CDK for Terraform. Takes the file to be converted on stdin. cdktf deploy [stacks...] Deploy the given stacks [aliases: apply] cdktf destroy [stacks..] Destroy the given stacks cdktf diff [stack] Perform a diff (terraform plan) for the given stack [aliases: plan] cdktf list List stacks in app. cdktf login Retrieves an API token to connect to Terraform Cloud or Terraform Enterprise. cdktf synth Synthesizes Terraform code for the given app in a directory. [aliases: synthesize] cdktf watch [stacks..] [experimental] Watch for file changes and automatically trigger a deploy cdktf output [stacks..] Prints the output of stacks [aliases: outputs] cdktf debug Get debug information about the current project and environment cdktf provider A set of subcommands that facilitates provider management cdktf completion generate completion script Options: --version Show version number [boolean] --disable-plugin-cache-env Dont set TF_PLUGIN_CACHE_DIR automatically. This is useful when the plugin cache is configured differently. Supported using the env CDKTF_DISABLE_PLUGIN_CACHE_ENV. [boolean] [default: false] --log-level Which log level should be written. Only supported via setting the env CDKTF_LOG_LEVEL [string] -h, --help Show help [boolean] Options can be specified via environment variables with the "CDKTF_" prefix(e.g. "CDKTF_OUTPUT")Add --help to any subcommand to learn more about what it does and available options.
$ cdktf init --helpcdktf init Create a new cdktf project from a template. Options: --version Show version number [boolean] --disable-plugin-cache-env Dont set TF_PLUGIN_CACHE_DIR automatically. This is useful when the plugin cache is configured differently. Supported using the env CDKTF_DISABLE_PLUGIN_CACHE_ENV. [boolean] [default: false] --log-level Which log level should be written. Only supported via setting the env CDKTF_LOG_LEVEL [string] --template The template to be used to create a new project. Either URL to zip file or one of the built-in templates: ["csharp", "go", "java", "python", "python-pip", "typescript"] [string] --project-name The name of the project. [string] --project-description The description of the project. [string] --dist Install dependencies from a "dist" directory (for development) [string] --local Use local state storage for generated Terraform. [boolean] [default: false] --cdktf-version The cdktf version to use while creating a new project. [string] [default: "0.13.0"] --from-terraform-project Use a terraform project as the basis, CDK constructs will be generated based on the .tf files in the path [string] --enable-crash-reporting Enable crash reporting for the CLI, refer to https://cdk.tf/crash-reporting for more details [boolean] -h, --help Show help [boolean]Quick start tutorial
Now that you've installed cdktf, write code that will provision an
NGINX server using Docker
Desktop on Mac, Windows, or
Linux.
Start Docker Desktop if it is not already running.
Create and initialize the project
Start by creating a directory named learn-cdktf-docker for the project.
$ mkdir learn-cdktf-dockerThen, navigate into it.
$ cd learn-cdktf-dockerInside the directory, initialize CDKTF with the appropriate template for your
chosen language. Also specify that your project will use the Docker provider,
and include the --local flag to prevent CDKTF from using HCP
Terraform.
CDKTF will prompt you for information about your project, such as the name and description. Accept the defaults for these options.
$ cdktf init --template=python --providers=kreuzwerker/docker --localNote: By supplying '--local' option you have chosen local storage mode for storing the state of your stack.This means that your Terraform state file will be stored locally on disk in a file 'terraform.<STACK NAME>.tfstate' in the root of your project.? Project Name learn-cdktf-docker? Project Description A simple getting started project for cdktf.? Do you want to send crash reports to the CDKTF team? Seehttps://www.terraform.io/cdktf/create-and-deploy/configuration-file#enable-crash-reporting-for-the-cli for more information YesCreating a virtualenv for this project...Pipfile: /Users/rnorwood/code/tutorials/learn-cdktf-docker-py/PipfileUsing /usr/local/bin/python3 (3.10.6) to create virtualenv...⠏ Creating virtual environment...created virtual environment CPython3.10.6.final.0-64 in 1357ms creator CPython3Posix(dest=/Users/rnorwood/.local/share/virtualenvs/learn-cdktf-docker-py-ZHPmg_Ne, clear=False, no_vcs_ignore=False, global=False) seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/Users/rnorwood/Library/Application Support/virtualenv) added seed packages: pip==22.2.2, setuptools==65.3.0, wheel==0.37.1 activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator ✔ Successfully created virtual environment!Virtualenv location: /Users/rnorwood/.local/share/virtualenvs/learn-cdktf-docker-py-ZHPmg_NePipfile.lock not found, creating...Locking [packages] dependencies...Locking [dev-packages] dependencies...Updated Pipfile.lock (c0c5a6)!Installing dependencies from Pipfile.lock (c0c5a6)...To activate this project's virtualenv, run pipenv shell.Alternatively, run a command inside the virtualenv with pipenv run.Installing cdktf~=0.15.0.dev59...Adding cdktf to Pipfile's [packages]...✔ Installation SucceededPipfile.lock (c0c5a6) out of date, updating to (c5a054)...Locking [packages] dependencies...Building requirements...Resolving dependencies...✔ Success!Locking [dev-packages] dependencies...Updated Pipfile.lock (c5a054)!Installing dependencies from Pipfile.lock (c5a054)...To activate this project's virtualenv, run pipenv shell.Alternatively, run a command inside the virtualenv with pipenv run.Installing pytest...Adding pytest to Pipfile's [packages]...✔ Installation SucceededPipfile.lock (c5a054) out of date, updating to (e26e1d)...Locking [packages] dependencies...Building requirements...Resolving dependencies...✔ Success!Locking [dev-packages] dependencies...Updated Pipfile.lock (e26e1d)!Installing dependencies from Pipfile.lock (e26e1d)...To activate this project's virtualenv, run pipenv shell.Alternatively, run a command inside the virtualenv with pipenv run.======================================================================================================== Your cdktf Python project is ready! cat help Prints this message Compile: pipenv run ./main.py Compile and run the python code. Synthesize: cdktf synth [stack] Synthesize Terraform resources to cdktf.out/ Diff: cdktf diff [stack] Perform a diff (terraform plan) for the given stack Deploy: cdktf deploy [stack] Deploy the given stack Destroy: cdktf destroy [stack] Destroy the given stack Learn more about using modules and providers https://cdk.tf/modules-and-providers Use Providers: You can add prebuilt providers (if available) or locally generated ones using the add command: cdktf provider add "aws@~>3.0" null kreuzwerker/docker You can find all prebuilt providers on PyPI: https://pypi.org/user/cdktf-team/ You can also install these providers directly through pipenv: pipenv install cdktf-cdktf-provider-aws pipenv install cdktf-cdktf-provider-google pipenv install cdktf-cdktf-provider-azurerm pipenv install cdktf-cdktf-provider-docker pipenv install cdktf-cdktf-provider-github pipenv install cdktf-cdktf-provider-null You can also build any module or provider locally. Learn more: https://cdk.tf/modules-and-providers ========================================================================================================Checking whether pre-built provider exists for the following constraints: provider: kreuzwerker/docker version : latest language: python cdktf : 0.15.0 Found pre-built provider.Package installed.Edit the code
Update your project's code to create a Docker container from the latest NGINX image.
Delete the contents of main.py and paste the following Python code into
it.
main.py
#!/usr/bin/env python from constructs import Constructfrom cdktf import App, TerraformStackfrom cdktf_cdktf_provider_docker.image import Imagefrom cdktf_cdktf_provider_docker.container import Containerfrom cdktf_cdktf_provider_docker.provider import DockerProvider class MyStack(TerraformStack): def __init__(self, scope: Construct, ns: str): super().__init__(scope, ns) DockerProvider(self, 'docker') docker_image = Image(self, 'nginxImage', name='nginx:latest', keep_locally=False) Container(self, 'nginxContainer', name='tutorial', image=docker_image.name, ports=[{ 'internal': 80, 'external': 8000 }]) app = App()MyStack(app, "learn-cdktf-docker") app.synth()The CDKTF code above is equivalent to the following HCL configuration.
resource "docker_image" "nginx" { name = "nginx:latest" keep_locally = false} resource "docker_container" "nginx" { image = docker_image.nginx.name name = "tutorial" ports { internal = 80 external = 8000 }}Deploy container
Now run cdktf deploy to compile the code and provision the NGINX Docker
container. CDKTF will print out a report of the changes that Terraform will make
to your infrastructure. Choose Approve to apply these changes.
$ cdktf deploylearn-cdktf-docker Initializing the backend...learn-cdktf-docker Successfully configured the backend "local"! Terraform will automatically use this backend unless the backend configuration changes.learn-cdktf-docker Initializing provider plugins... Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary.typescript-docker Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions:typescript-docker # docker_container.nginxContainer (nginxContainer) will be created + resource "docker_container" "nginxContainer" { + attach = false##... } # docker_image.nginxImage (nginxImage) will be created + resource "docker_image" "nginxImage" { + id = (known after apply) + keep_locally = false + latest = (known after apply) + name = "nginx:latest" + output = (known after apply) + repo_digest = (known after apply) } Plan: 2 to add, 0 to change, 0 to destroy. ───────────────────────────────────────────────────────────────────────────── Saved the plan to: plan To perform exactly these actions, run the following command to apply: terraform apply "plan" Please review the diff output above for typescript-docker❯ Approve Applies the changes outlined in the plan. Dismiss StopVerify the NGINX container exists by visiting
localhost:8000 in your web browser or running docker
ps to find the container.
$ docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES86ff19f506f4 c316d5a335a5 "/docker-entrypoint.…" 16 seconds ago Up 15 seconds 0.0.0.0:8000->80/tcp tutorialDestroy the container
To remove the container and image, run cdktf destroy. Select Approve to
approve the removal of your container.
$ cdktf destroytypescript-docker Initializing the backend...typescript-docker Initializing provider plugins... - Reusing previous version of kreuzwerker/docker from the dependency lock filetypescript-docker - Using previously-installed kreuzwerker/docker v2.16.0typescript-docker Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary.typescript-docker docker_image.nginxImage (nginxImage): Refreshing state... [id=sha256:c316d5a335a5cf324b0dc83b3da82d7608724769f6454f6d9a621f3ec2534a5anginx:latest]typescript-docker docker_container.nginxContainer (nginxContainer): Refreshing state... [id=86ff19f506f470a0ddead8d77d2dc8e6cc8eaeca34358cd1a2df7372567caea3]typescript-docker Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: - destroy Terraform will perform the following actions:typescript-docker # docker_container.nginxContainer (nginxContainer) will be destroyed - resource "docker_container" "nginxContainer" { - attach = false -> null - command = [##... } # docker_image.nginxImage (nginxImage) will be destroyed - resource "docker_image" "nginxImage" { - id = "sha256:c316d5a335a5cf324b0dc83b3da82d7608724769f6454f6d9a621f3ec2534a5anginx:latest" -> null - keep_locally = false -> null - latest = "sha256:c316d5a335a5cf324b0dc83b3da82d7608724769f6454f6d9a621f3ec2534a5a" -> null - name = "nginx:latest" -> null - repo_digest = "nginx@sha256:2834dc507516af02784808c5f48b7cbe38b8ed5d0f4837f16e78d00deb7e7767" -> null } Plan: 0 to add, 0 to change, 2 to destroy. ───────────────────────────────────────────────────────────────────────────── Saved the plan to: plan To perform exactly these actions, run the following command to apply: terraform apply "plan" Please review the diff output above for typescript-docker❯ Approve Applies the changes outlined in the plan. Dismiss StopYou have now provisioned and destroyed an NGINX webserver with CDKTF.
Next steps
Now that you have installed CDKTF, learn how to use it to manage your resources in your preferred programming language.
- Follow our AWS tutorial with TypeScript, Python, Go, C#, and Java.
- Read the CDKTF Documentation.