Skip to main content
A Terraform module is a single directory that contains one or more configuration files. Modules let you reuse configurations across projects and teams, saving time, enforcing consistency, and reducing errors. For example, you could create a module to describe the configuration for all of your organization’s public website buckets. When you package and share this module, other users can incorporate it into their configurations. As requirements evolve, you can make changes to your module once, release a new version, and apply those changes everywhere that module is used. You can specify any existing public or private module in your cdktf.json file, and CDK Terrain (CDKTN) generates the necessary code bindings for you to use in your application.

​
Install Modules

You can use modules from the Terraform Registry (or OpenTofu Registry) and other sources like GitHub in your application. For example, the following TypeScript project has a main.ts file that defines AWS resources and uses the AWS VPC module. 
import { Construct } from "constructs";
import { TerraformStack } from "cdktn";
import { AwsProvider } from "@cdktn/provider-aws/lib/aws-provider";
import { Vpc } from "./.gen/modules/terraform-aws-modules/aws/vpc";

export class ModulesStack extends TerraformStack {
  constructor(scope: Construct, id: string) {
    super(scope, id);

    const provider = new AwsProvider(this, "aws", {
      region: "us-west-2",
    });

    new Vpc(this, "MyVpc", {
      name: "my-vpc",
      cidr: "10.0.0.0/16",
      azs: ["us-west-2a", "us-west-2b", "us-west-2c"],
      privateSubnets: ["10.0.1.0/24", "10.0.2.0/24", "10.0.3.0/24"],
      publicSubnets: ["10.0.101.0/24", "10.0.102.0/24", "10.0.103.0/24"],
      enableNatGateway: true,
    });
  }
}

​
Add Module to cdktf.json

To use a module in your application, you must first add it to the terraformModules array in the cdktf.json configuration file. To add a module from the Terraform Registry or a private registry, provide a fully qualified name: registry-namespace/module-name. 
{
  "language": "typescript",
  "app": "npm run --silent compile && node main.js",
  "terraformProviders": [],
  "terraformModules": [
    {
      "name": "vpc",
      "source": "terraform-aws-modules/vpc/aws",
      "version": "~> 3.0"
    }
  ]
}
For local modules, use the object format. 
{
  "language": "typescript",
  "app": "npm run --silent compile && node main.js",
  "terraformProviders": [],
  "terraformModules": [
    {
      "name": "my-local-module",
      "source": "./path/to/local/terraform/module"
    }
  ]
}
For performance reasons, we don’t automatically generate bindings for submodules. To generate bindings for submodules, specify the module source as terraform-aws-modules/vpc/aws//submodules/vpc-endpoints, where after the // is the path to the submodule in the modules repository. Refer to the Terraform source specification for more details. When you are using local modules that reference other local modules you need to add all referenced modules to the terraformModules array.

​
Generate Module Bindings

Go to the working directory and run cdktn get. CDKTN automatically creates the appropriate module bindings in the ./.gen directory for you to use in your application.

​
Configure Modules

You can configure modules in the same way as resources, with one exception. For module inputs that use the map type, like map(string) or list(map(string)), you must specify the map values as strings. You must also ensure that the keys follow the required format listed in the module’s documentation. For example, the module may specify that the keys must be in snake case.

​
Work with Module Outputs

Modules often return data that you can use as inputs to other modules or resources. When this data is only available after Terraform (or OpenTofu) applies the configuration, you must use Terraform Outputs.

​
Examples

The following example uses a local module and references its output as a Terraform output. 
import { Construct } from "constructs";
import { TerraformStack } from "cdktn";
import { AwsProvider } from "@cdktn/provider-aws/lib/aws-provider";
import { TerraformOutput } from "cdktn";

// This module can come from a registry or through a local / remote reference
import { MyLocalModule } from "./.gen/modules/my-local-module";

export class ModulesStack extends TerraformStack {
  constructor(scope: Construct, id: string) {
    super(scope, id);

    const provider = new AwsProvider(this, "aws", {
      region: "us-west-2",
    });

    const localModule = new MyLocalModule(this, "local-module", {
      ipAddress: "127.0.0.1",
    });

    new TerraformOutput(this, "dns-server", {
      value: localModule.dnsServerOutput,
    });
  }
}

​
Create Modules

While we generally recommend generating code bindings for modules, you can also use the TerraformHclModule class to reference any module that Terraform supports. Both methods create identical synthesized Terraform configuration files, but using TerraformHclModule does not generate any types or type-safe inputs or outputs. The following example uses TerraformHclModule to import an AWS module. 
import { Construct } from "constructs";
import { TerraformStack } from "cdktn";
import { AwsProvider } from "@cdktn/provider-aws/lib/aws-provider";
import { TerraformHclModule } from "cdktn";

export class ModulesStack extends TerraformStack {
  constructor(scope: Construct, id: string) {
    super(scope, id);

    const provider = new AwsProvider(this, "aws", {
      region: "us-west-2",
    });

    new TerraformHclModule(this, "Vpc", {
      source: "terraform-aws-modules/vpc/aws",
      // Note: variables has no types for its inputs.
      // When using this for other modules consult the docs of the module
      // to ensure the arguments are correct.
      variables: {
        name: "my-vpc",
        cidr: "10.0.0.0/16",
        azs: ["us-west-2a", "us-west-2b", "us-west-2c"],
        private_subnets: ["10.0.1.0/24", "10.0.2.0/24", "10.0.3.0/24"],
        public_subnets: ["10.0.101.0/24", "10.0.102.0/24", "10.0.103.0/24"],
        enable_nat_gateway: true,
      },
      providers: [provider],
    });
  }
}