Hybrid Module Approach

​

Why Adopt a Hybrid Module Model?

• Rapid adoption of reusable, well-supported modules for standard services
• Ability to extend or fine-tune modules to meet project-specific needs
• Consistent versioning of your own modules alongside community offerings

​

Comparing Module Sources

​

Best Practices for Hybrid Modules

1. Version Control
   • Use semantic versioning for both community and custom modules.
   • Tag releases in Git and reference stable versions.
2. Module Registry
   • Mirror public modules internally for audit and compliance.
   • Store custom modules in a private Terraform Registry or Nexus.
3. Security and Compliance
   • Scan community modules for vulnerabilities before adoption.
   • Enforce organizational standards via pre-commit hooks or CI pipelines.

​

Example: Hybrid Module Configuration

terraform {
  required_version = ">= 1.0"
}

provider "aws" {
  region = "us-east-1"
}

module "network" {
  source  = "terraform-aws-modules/vpc/aws"
  version = "3.14.0"

  name = "hybrid-vpc"
  cidr = "10.0.0.0/16"
}

module "app_infrastructure" {
  source = "git@github.com:your-org/app-infra-module.git"
  version = "v2.1.0"

  env        = "production"
  vpc_id     = module.network.vpc_id
  subnet_ids = module.network.private_subnets
}

​

Links and References

• Terraform Registry
• Official Terraform Documentation
• Git Best Practices
• Terraform AWS Modules