Terraform Module Library

VerifiedSafe

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices.

Sby Skills Guide Bot
DevOpsIntermediate
7/26/2026
Claude CodeCursorWindsurfCopilotCodex
#terraform#infrastructure-as-code#cloud-provisioning#multi-cloud#reusable-modules

Recommended for

Automated summary

This skill provides patterns and best practices for building reusable Terraform modules for AWS, Azure, and GCP infrastructure.

Strengths

  • Offers a standard module layout with main.tf, variables.tf, outputs.tf, versions.tf, examples, and tests.
  • Includes a concrete AWS VPC module example with variable validation and useful outputs.
  • Supports multi-cloud organization and standardization of infrastructure provisioning with infrastructure-as-code.

Limitations

  • Does not deeply cover state management, backends, CI/CD, or security scanning.
  • Testing is only mentioned via Terratest, with no full test template provided.
  • Assumes prior familiarity with Terraform and the relevant cloud resources.
When to use it

Use this skill when you need to design or standardize reusable Terraform modules for AWS, Azure, or GCP infrastructure.

When not to use it

Avoid it for highly specific Terraform tasks outside module creation, or for cloud topics unrelated to infrastructure-as-code.

Security analysis

Safe
Quality score82/100

The skill provides Terraform module authoring guidance and examples only. It does not instruct agents to run shell commands, access secrets, modify systems destructively, or exfiltrate data.

No concerns found

How this analysis is made

Examples

Create an AWS VPC module
Create a reusable Terraform module for an AWS VPC with variables for CIDR block, availability zones, private subnet CIDRs, tags, and outputs for VPC ID and subnet IDs. Include an examples/complete usage.
Standardize Azure modules
Refactor our Azure VNet and AKS Terraform configuration into standard reusable modules with versions.tf, documented variables, outputs, and README files.
Design a multi-cloud module library
Design a Terraform module library layout for AWS, Azure, and GCP that standardizes module structure, examples, versioning, and documentation.

name: terraform-module-library description: "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, ..." risk: unknown source: community date_added: "2026-02-27"

Terraform Module Library

Production-ready Terraform module patterns for AWS, Azure, and GCP infrastructure.

Do not use this skill when

  • The task is unrelated to terraform module library
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Purpose

Create reusable, well-tested Terraform modules for common cloud infrastructure patterns across multiple cloud providers.

Use this skill when

  • Build reusable infrastructure components
  • Standardize cloud resource provisioning
  • Implement infrastructure as code best practices
  • Create multi-cloud compatible modules
  • Establish organizational Terraform standards

Module Structure

terraform-modules/
├── aws/
│   ├── vpc/
│   ├── eks/
│   ├── rds/
│   └── s3/
├── azure/
│   ├── vnet/
│   ├── aks/
│   └── storage/
└── gcp/
    ├── vpc/
    ├── gke/
    └── cloud-sql/

Standard Module Pattern

module-name/
├── main.tf          # Main resources
├── variables.tf     # Input variables
├── outputs.tf       # Output values
├── versions.tf      # Provider versions
├── README.md        # Documentation
├── examples/        # Usage examples
│   └── complete/
│       ├── main.tf
│       └── variables.tf
└── tests/           # Terratest files
    └── module_test.go

AWS VPC Module Example

main.tf:

resource "aws_vpc" "main" {
  cidr_block           = var.cidr_block
  enable_dns_hostnames = var.enable_dns_hostnames
  enable_dns_support   = var.enable_dns_support

  tags = merge(
    {
      Name = var.name
    },
    var.tags
  )
}

resource "aws_subnet" "private" {
  count             = length(var.private_subnet_cidrs)
  vpc_id            = aws_vpc.main.id
  cidr_block        = var.private_subnet_cidrs[count.index]
  availability_zone = var.availability_zones[count.index]

  tags = merge(
    {
      Name = "${var.name}-private-${count.index + 1}"
      Tier = "private"
    },
    var.tags
  )
}

resource "aws_internet_gateway" "main" {
  count  = var.create_internet_gateway ? 1 : 0
  vpc_id = aws_vpc.main.id

  tags = merge(
    {
      Name = "${var.name}-igw"
    },
    var.tags
  )
}

variables.tf:

variable "name" {
  description = "Name of the VPC"
  type        = string
}

variable "cidr_block" {
  description = "CIDR block for VPC"
  type        = string
  validation {
    condition     = can(regex("^([0-9]{1,3}\\.){3}[0-9]{1,3}/[0-9]{1,2}$", var.cidr_block))
    error_message = "CIDR block must be valid IPv4 CIDR notation."
  }
}

variable "availability_zones" {
  description = "List of availability zones"
  type        = list(string)
}

variable "private_subnet_cidrs" {
  description = "CIDR blocks for private subnets"
  type        = list(string)
  default     = []
}

variable "enable_dns_hostnames" {
  description = "Enable DNS hostnames in VPC"
  type        = bool
  default     = true
}

variable "tags" {
  description = "Additional tags"
  type        = map(string)
  default     = {}
}

outputs.tf:

output "vpc_id" {
  description = "ID of the VPC"
  value       = aws_vpc.main.id
}

output "private_subnet_ids" {
  description = "IDs of private subnets"
  value       = aws_subnet.private[*].id
}

output "vpc_cidr_block" {
  description = "CIDR block of VPC"
  value       = aws_vpc.main.cidr_block
}

Best Practices

  1. Use semantic versioning for modules
  2. Document all variables with descriptions
  3. Provide examples in examples/ directory
  4. Use validation blocks for input validation
  5. Output important attributes for module composition
  6. Pin provider versions in versions.tf
  7. Use locals for computed values
  8. Implement conditional resources with count/for_each
  9. Test modules with Terratest
  10. Tag all resources consistently

Module Composition

module "vpc" {
  source = "../../modules/aws/vpc"

  name               = "production"
  cidr_block         = "10.0.0.0/16"
  availability_zones = ["us-west-2a", "us-west-2b", "us-west-2c"]

  private_subnet_cidrs = [
    "10.0.1.0/24",
    "10.0.2.0/24",
    "10.0.3.0/24"
  ]

  tags = {
    Environment = "production"
    ManagedBy   = "terraform"
  }
}

module "rds" {
  source = "../../modules/aws/rds"

  identifier     = "production-db"
  engine         = "postgres"
  engine_version = "15.3"
  instance_class = "db.t3.large"

  vpc_id     = module.vpc.vpc_id
  subnet_ids = module.vpc.private_subnet_ids

  tags = {
    Environment = "production"
  }
}

Reference Files

  • assets/vpc-module/ - Complete VPC module example
  • assets/rds-module/ - RDS module example
  • references/aws-modules.md - AWS module patterns
  • references/azure-modules.md - Azure module patterns
  • references/gcp-modules.md - GCP module patterns

Testing

// tests/vpc_test.go
package test

import (
    "testing"
    "github.com/gruntwork-io/terratest/modules/terraform"
    "github.com/stretchr/testify/assert"
)

func TestVPCModule(t *testing.T) {
    terraformOptions := &terraform.Options{
        TerraformDir: "../examples/complete",
    }

    defer terraform.Destroy(t, terraformOptions)
    terraform.InitAndApply(t, terraformOptions)

    vpcID := terraform.Output(t, terraformOptions, "vpc_id")
    assert.NotEmpty(t, vpcID)
}

Related Skills

  • multi-cloud-architecture - For architectural decisions
  • cost-optimization - For cost-effective designs

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/terraform-module-library-ms1aw5cy' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/terraform-module-library-ms1aw5cy/download' --output '.skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md.part' && mv '.skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md.part' '.skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md' && test -s '.skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/terraform-module-library' && cp -R '.skill-downloads/terraform-module-library-ms1aw5cy' '.claude/skills/terraform-module-library'

Cursor
test -f '.skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md' && test -s '.skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/terraform-module-library' && cp -R '.skill-downloads/terraform-module-library-ms1aw5cy' '.cursor/skills/terraform-module-library'

Codex
test -f '.skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md' && test -s '.skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/terraform-module-library' && cp -R '.skill-downloads/terraform-module-library-ms1aw5cy' '.agents/skills/terraform-module-library'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/terraform-module-library-ms1aw5cy'

openskills read 'terraform-module-library-ms1aw5cy'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/terraform-module-library-ms1aw5cy/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills