Connect Terraform Modules

6min
Overview
Now that there is a test workspace to work with, it's time to connect Terraform modules and define the configuration elements that will be needed to generate the wizard form display elements in the next step.
Connect KMS Terraform Module
To deploy our AWS KMS Key module, use the CloudPosse KMS Key Module. In main.tf, add the module resource block to the file:
Terraform
####
# Module Resources
#
# Connect to the Terraform modules that will be used to create this blueprint


####
# KMS Key
#
resource "autocloud_module" "kms_key" {
  name   = "cpkmskey"
  source  = "cloudposse/kms-key/aws"
  version = "0.12.1"
}
####
# Module Resources
#
# Connect to the Terraform modules that will be used to create this blueprint


####
# KMS Key
#
resource "autocloud_module" "kms_key" {
  name   = "cpkmskey"
  source  = "cloudposse/kms-key/aws"
  version = "0.12.1"
}
﻿
In this section, we've set two important identifiers. First, we've chosen the Terraform resource identifier kms_key, which will be used to refer to the Terraform properties such as variables, outputs, etc at plan and apply time. Second, we've chosen the AutoCloud identifier cpkmskey which will be used to dynamically configure relationships between modules and templates for assets such as pull requests and ticket contents.
Create Form Configuration for the KMS Module
Add an empty blueprint configuration below the autocloud_module definition for the KMS key. This will be used to configure the KMS key variables for display and code generation:
Terraform
data "autocloud_blueprint_config" "kms_key_processor" {
  source = {
    kms = autocloud_module.kms_key.blueprint_config
  }

  omit_variables = [
    # Use defaults in the module (don't collect)
    # Global values
    # Hard Coded values
  ]
}
data "autocloud_blueprint_config" "kms_key_processor" {
  source = {
    kms = autocloud_module.kms_key.blueprint_config
  }

  omit_variables = [
    # Use defaults in the module (don't collect)
    # Global values
    # Hard Coded values
  ]
}
﻿
The variable configurations will be configured in future steps.
Connect S3 Terraform Module & Create Form Configuration
To deploy our AWS S3 Bucket module, use the CloudPosse S3 Bucket Module. In main.tf, add the module resource and form configuration data resource blocks the file below the KMS key module assets:
Terraform
####
# S3 Bucket
#
resource "autocloud_module" "s3_bucket" {
  name    = "cps3bucket"
  source  = "cloudposse/s3-bucket/aws"
  version = "3.1.0"
}

data "autocloud_blueprint_config" "s3_bucket_processor" {
  source = {
    s3 = autocloud_module.s3_bucket.blueprint_config
  }

  omit_variables = [
    # Use defaults in the module (don't collect)
    # Global values
    # Hard Coded values
  ]
}

####
# S3 Bucket
#
resource "autocloud_module" "s3_bucket" {
  name    = "cps3bucket"
  source  = "cloudposse/s3-bucket/aws"
  version = "3.1.0"
}

data "autocloud_blueprint_config" "s3_bucket_processor" {
  source = {
    s3 = autocloud_module.s3_bucket.blueprint_config
  }

  omit_variables = [
    # Use defaults in the module (don't collect)
    # Global values
    # Hard Coded values
  ]
}
﻿
Create Global Form Configuration
Below the other resources in the main.tffile, add a global form configuration to consolidate variable definitions, collect global values, and define the final form configuration to display to the user:
Terraform
####
# Create Blueprint Config
#
# Combine resources into the final config
data "autocloud_blueprint_config" "global" {
  source = {
    kms = data.autocloud_blueprint_config.kms_key_processor.blueprint_config,
    s3 = data.autocloud_blueprint_config.s3_bucket_processor.blueprint_config
  }

  ###
  # Hide variables from user
  omit_variables = [
    # Use defaults in the module (don't collect)
    # Global values
    # Hard Coded values
  ]
}
####
# Create Blueprint Config
#
# Combine resources into the final config
data "autocloud_blueprint_config" "global" {
  source = {
    kms = data.autocloud_blueprint_config.kms_key_processor.blueprint_config,
    s3 = data.autocloud_blueprint_config.s3_bucket_processor.blueprint_config
  }

  ###
  # Hide variables from user
  omit_variables = [
    # Use defaults in the module (don't collect)
    # Global values
    # Hard Coded values
  ]
}
﻿
Apply Progress
Run terraform apply to deploy progress so far:
Terraform
❯ tf apply
data.autocloud_github_repos.repos: Reading...
data.autocloud_github_repos.repos: Read complete after 1s [id=1676056689]

Terraform used the selected providers to generate the following execution plan. 
Resource actions are indicated with the following symbols:
  + create
 <= read (data resources)

Terraform will perform the following actions:

  # data.autocloud_blueprint_config.global will be read during apply
  # (config refers to values not yet known)
 <= data "autocloud_blueprint_config" "global" {
      + blueprint_config = (known after apply)
      + config           = (known after apply)
      + id               = (known after apply)
      + omit_variables   = [
          + "enabled",
        ]
      + source           = {
          + "kms" = (known after apply)
          + "s3"  = (known after apply)
        }
    }

  # data.autocloud_blueprint_config.kms_key_processor will be read during apply
  # (config refers to values not yet known)
 <= data "autocloud_blueprint_config" "kms_key_processor" {
      + blueprint_config = (known after apply)
      + config           = (known after apply)
      + id               = (known after apply)
      + omit_variables   = []
      + source           = {
          + "kms" = (known after apply)
        }
    }

  # data.autocloud_blueprint_config.s3_bucket_processor will be read during apply
  # (config refers to values not yet known)
 <= data "autocloud_blueprint_config" "s3_bucket_processor" {
      + blueprint_config = (known after apply)
      + config           = (known after apply)
      + id               = (known after apply)
      + omit_variables   = []
      + source           = {
          + "s3" = (known after apply)
        }
    }

  # autocloud_module.kms_key will be created
  + resource "autocloud_module" "kms_key" {
      + blueprint_config   = (known after apply)
      + blueprint_config_1 = (known after apply)
      + id                 = (known after apply)
      + name               = "cpkmskey"
      + outputs            = (known after apply)
      + source             = "cloudposse/kms-key/aws"
      + tags_variable      = "tags"
      + template           = (known after apply)
      + template_config    = (known after apply)
      + variables          = (known after apply)
      + version            = "0.12.1"
    }

  # autocloud_module.s3_bucket will be created
  + resource "autocloud_module" "s3_bucket" {
      + blueprint_config   = (known after apply)
      + blueprint_config_1 = (known after apply)
      + id                 = (known after apply)
      + name               = "cps3bucket"
      + outputs            = (known after apply)
      + source             = "cloudposse/s3-bucket/aws"
      + tags_variable      = "tags"
      + template           = (known after apply)
      + template_config    = (known after apply)
      + variables          = (known after apply)
      + version            = "3.0.0"
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

autocloud_module.kms_key: Creating...
autocloud_module.s3_bucket: Creating...
autocloud_module.kms_key: Creation complete after 3s [id=cldywvqam411808vacivfrrpz]
data.autocloud_blueprint_config.kms_key_processor: Reading...
data.autocloud_blueprint_config.kms_key_processor: Read complete after 0s [id=1676056694]
autocloud_module.s3_bucket: Creation complete after 3s [id=cldywvqdg433407vjj8w0wi91]
data.autocloud_blueprint_config.s3_bucket_processor: Reading...
data.autocloud_blueprint_config.s3_bucket_processor: Read complete after 0s [id=1676056694]
data.autocloud_blueprint_config.final: Reading...
data.autocloud_blueprint_config.final: Read complete after 0s [id=1676056694]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

❯ tf apply
data.autocloud_github_repos.repos: Reading...
data.autocloud_github_repos.repos: Read complete after 1s [id=1676056689]

Terraform used the selected providers to generate the following execution plan. 
Resource actions are indicated with the following symbols:
  + create
 <= read (data resources)

Terraform will perform the following actions:

  # data.autocloud_blueprint_config.global will be read during apply
  # (config refers to values not yet known)
 <= data "autocloud_blueprint_config" "global" {
      + blueprint_config = (known after apply)
      + config           = (known after apply)
      + id               = (known after apply)
      + omit_variables   = [
          + "enabled",
        ]
      + source           = {
          + "kms" = (known after apply)
          + "s3"  = (known after apply)
        }
    }

  # data.autocloud_blueprint_config.kms_key_processor will be read during apply
  # (config refers to values not yet known)
 <= data "autocloud_blueprint_config" "kms_key_processor" {
      + blueprint_config = (known after apply)
      + config           = (known after apply)
      + id               = (known after apply)
      + omit_variables   = []
      + source           = {
          + "kms" = (known after apply)
        }
    }

  # data.autocloud_blueprint_config.s3_bucket_processor will be read during apply
  # (config refers to values not yet known)
 <= data "autocloud_blueprint_config" "s3_bucket_processor" {
      + blueprint_config = (known after apply)
      + config           = (known after apply)
      + id               = (known after apply)
      + omit_variables   = []
      + source           = {
          + "s3" = (known after apply)
        }
    }

  # autocloud_module.kms_key will be created
  + resource "autocloud_module" "kms_key" {
      + blueprint_config   = (known after apply)
      + blueprint_config_1 = (known after apply)
      + id                 = (known after apply)
      + name               = "cpkmskey"
      + outputs            = (known after apply)
      + source             = "cloudposse/kms-key/aws"
      + tags_variable      = "tags"
      + template           = (known after apply)
      + template_config    = (known after apply)
      + variables          = (known after apply)
      + version            = "0.12.1"
    }

  # autocloud_module.s3_bucket will be created
  + resource "autocloud_module" "s3_bucket" {
      + blueprint_config   = (known after apply)
      + blueprint_config_1 = (known after apply)
      + id                 = (known after apply)
      + name               = "cps3bucket"
      + outputs            = (known after apply)
      + source             = "cloudposse/s3-bucket/aws"
      + tags_variable      = "tags"
      + template           = (known after apply)
      + template_config    = (known after apply)
      + variables          = (known after apply)
      + version            = "3.0.0"
    }

Plan: 2 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

autocloud_module.kms_key: Creating...
autocloud_module.s3_bucket: Creating...
autocloud_module.kms_key: Creation complete after 3s [id=cldywvqam411808vacivfrrpz]
data.autocloud_blueprint_config.kms_key_processor: Reading...
data.autocloud_blueprint_config.kms_key_processor: Read complete after 0s [id=1676056694]
autocloud_module.s3_bucket: Creation complete after 3s [id=cldywvqdg433407vjj8w0wi91]
data.autocloud_blueprint_config.s3_bucket_processor: Reading...
data.autocloud_blueprint_config.s3_bucket_processor: Read complete after 0s [id=1676056694]
data.autocloud_blueprint_config.final: Reading...
data.autocloud_blueprint_config.final: Read complete after 0s [id=1676056694]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.
﻿
CloudPosse's modules make use of their label module, and the module variables are stored in two files, context.tf and variables.tf. 
Updated 01 Jun 2023
Did this page help you?
Bootstrap Test Space
Configure Variables
Docs powered by Archbee
TABLE OF CONTENTS
Overview
Connect KMS Terraform Module
Create Form Configuration for the KMS Module
Connect S3 Terraform Module & Create Form Configuration
Create Global Form Configuration
Apply Progress