What should I use for team-wide reusable infrastructure modules?

For team-wide reusable infrastructure modules, the best default is usually:

Use Terraform modules for standard reusable infrastructure

They’re the most common choice when:

• your team already uses Terraform
• you want reusable, versioned building blocks
• you need a balance of flexibility and standardization
• multiple teams or projects will consume the same patterns

Good examples

• VPC / networking
• IAM roles/policies
• Kubernetes cluster components
• RDS / databases
• S3 buckets with standard controls
• monitoring/logging setup

When to consider other options

1) Internal platform service / IaC abstraction

Use this if you want to hide cloud complexity from app teams and provide higher-level self-service.

• Good for large orgs
• More opinionated
• Often built on top of Terraform, Pulumi, or cloud APIs

2) Terraform + module registry

If you want governance and versioning, publish modules to:

• Terraform Registry
• private registry
• Git tags/releases

This works well for team-wide reuse with clear version pinning.

3) Pulumi components

Consider Pulumi if:

• your team prefers real programming languages
• you need more complex logic and abstractions
• Terraform modules feel too limited

4) Cloud-native templates

Like:

• AWS CDK constructs
• CloudFormation modules/macros
• Azure Bicep modules

Use these if you are strongly tied to a single cloud and want native tooling.

Practical recommendation

If you’re asking generally, I’d recommend:

Start with Terraform modules + versioned releases + a shared module registry.

That gives you:

• reuse
• consistency
• upgrade control
• low operational overhead

Good module design rules

• Make modules small and composable
• Keep interfaces stable and minimal
• Version modules semantically
• Avoid embedding environment-specific values
• Add examples and docs
• Enforce standards via CI/testing

If you want, I can also suggest a repo structure and module design pattern for team-wide Terraform modules.