← All writing

Building Enterprise Terraform Modules: Golden Paths & DRY Architecture

· Sourabh G Kulkarni

How platform teams build reusable, bulletproof Terraform modules using strict input validation, semantic versioning, and golden paths.

Building Enterprise Terraform Modules: Golden Paths & DRY Architecture

In the early stages of adopting Infrastructure as Code (IaC), teams inevitably fall into the copy-paste trap. A developer wants an S3 bucket or an EKS node pool, so they duplicate 150 lines of raw HCL from another repository, tweak the name, and hit terraform apply.

Six months later, the company has 40 unmaintained copies of the same infrastructure block, security groups have drifted wildly, and compliance patches require a manual multi-week audit.

Platform engineering solves this by establishing Golden Paths: creating version-controlled, production-grade Terraform modules that encode security defaults, compliance rules, and sensible configurations out of the box.

flowchart TD
    subgraph Registry["Internal Module Registry / Git Releases"]
        V1["terraform-aws-microservice (v1.2.0)"]
        V2["terraform-aws-microservice (v2.0.0)"]
    end

    subgraph Teams["Product Engineering Repositories (Consumers)"]
        P1["Billing Service (pinned v1.2.0)"]
        P2["Checkout Service (pinned v2.0.0)"]
        P3["Catalog Service (pinned v2.0.0)"]
    end

    V1 -.->|Strict SemVer| P1
    V2 -.->|Paved Road Defaults| P2
    V2 -.->|Automated Validation| P3

1. Structure of an Enterprise Module

A robust module isolates responsibilities into dedicated files:

modules/aws-microservice/
├── main.tf          # Core resource declarations (ECS/EKS, Security Groups, IAM)
├── variables.tf     # Strictly typed inputs with descriptions and validation blocks
├── outputs.tf       # Clean export of resource IDs, ARNs, and connection endpoints
├── versions.tf      # Pinned provider and terraform core minimum versions
└── README.md        # Autogenerated documentation (via terraform-docs)

2. Guardrails with Input Validation Blocks

Never trust raw string inputs. Use custom validation to catch misconfigurations at terraform plan time before cloud resources are touched.

variable "environment" {
  type        = string
  description = "Target deployment tier (dev, staging, prod)."

  validation {
    condition     = contains(["dev", "staging", "prod"], var.environment)
    error_message = "The environment must be one of: dev, staging, or prod."
  }
}

variable "instance_type" {
  type        = string
  default     = "t3.medium"
  description = "EC2 instance size for node allocation."

  validation {
    condition     = can(regex("^[t|m|c][3-6][a-z]?\\.", var.instance_type))
    error_message = "Only modern general purpose (t, m, c) instance families are permitted."
  }
}

3. Preconditions & Postconditions

Terraform 1.2+ introduced lifecycle assertions that enforce guarantees at resource evaluation time:

resource "aws_ebs_volume" "app_data" {
  availability_zone = var.az
  size              = var.disk_size_gb
  encrypted         = true
  kms_key_id        = var.kms_key_arn

  lifecycle {
    # Ensure disks in production are never smaller than standard minimums
    precondition {
      condition     = var.environment != "prod" || var.disk_size_gb >= 100
      error_message = "Production persistent volumes must be at least 100 GB."
    }

    # Ensure AWS assigned encryption properly
    postcondition {
      condition     = self.encrypted == true
      error_message = "The provisioned EBS volume failed encryption verification."
    }
  }
}

4. Semantic Versioning: The Contract Between Platform & Product

A Terraform module is a software product. Product teams consume it as a dependency:

module "payment_service_infra" {
  source = "git::https://github.com/sourabhkulkarni/terraform-aws-service.git?ref=v2.1.0"

  service_name   = "payment-processor"
  environment    = "prod"
  container_port = 8080
}

The SemVer Rules for IaC:

  • PATCH (v2.1.1): Documentation tweaks, internal refactoring, non-breaking bug fixes that produce no plan changes.
  • MINOR (v2.2.0): New optional variables, additional outputs, or new optional resources.
  • MAJOR (v3.0.0): Breaking variable changes, deleted resources, or changes that force resource recreation (e.g. changing subnets or disk keys).

By building opinionated modules with strict input assertions and SemVer tagging, platform engineers give product teams self-service velocity without sacrificing enterprise security standards.