AgenticFor DevelopersDevOps & CI/CD

Terraform Module Builder.

When provisioning the same infrastructure pattern across multiple environments or teams.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1650 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
terraform-module-builder-4.md Β· 1650 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: DevOps & CI/CD
- Use case: Terraform Module Builder
- Source task:
  - Build a reusable Terraform module for {{describe_infrastructure}}. The module must:
  - 1. accept all environment-specific values as input variables with descriptions and validations
  - 2. output all values consumers will need (endpoint, ARN, connection string format)
  - 3. follow module best practices (no hardcoded values, sensible defaults, tagging)
  - 4. include a README with usage example and variable reference
  - 5. implement least-privilege IAM permissions

# Goal
A complete Terraform module with variables, outputs, tagging, a README, and least-privilege IAM configuration.

# Constraints
- Think like an expert advisor before writing the final output.
- Ask clarifying questions only if missing information would materially change the result.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
A complete Terraform module with variables, outputs, tagging, a README, and least-privilege IAM configuration.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}RoleTerraform expert
{{use_case}}Your specific valueterraform module builder
{{describe_infrastructure}}Describe infrastructurean AWS RDS instance, a GCP GKE cluster, an Azure AKS deployment

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When provisioning the same infrastructure pattern across multiple environments or teams.

PRO TIP

Module inputs should have sensible defaults β€” a module that requires 30 required variables will never be reused.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’