DevOps & Infra Skill
Bash Defensive Patterns
Master defensive Bash programming techniques for production-grade scripts.
$15
Terraform Module Library
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following…
Production-ready, reusable Terraform module patterns for AWS, Azure and GCP that turn one-off infrastructure scripts into a maintainable component library. Each module follows the standard main/variables/outputs/versions layout with input validation, examples and Terratest coverage, so teams provision VPCs, databases and clusters the same way every time across clouds. Standardize your IaC instead of copy-pasting HCL between projects.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category DevOps & Infra
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Copy-pasted Terraform is debt with a blast radius. The library approach scaffolds every module in a standard layout, validates inputs at plan time, splits state by domain, and refuses to ship anything Terratest has not proven.
- Scaffold every module in the standard layout: main.tf, variables.tf, outputs.tf, versions.tf with pinned providers, an examples directory and Terratest files, so each module is documented and provable.
- Validate inputs at the variable level: CIDR regex checks, allowed-value lists for instance types, numeric bounds. Bad values die at plan time, not after a half-applied infrastructure change.
- Compose instead of copying: modules expose outputs like vpc_id and subnet_ids, root modules wire them together, and environment differences live only in tfvars files while module code stays identical.
- Limit blast radius structurally: state split by domain (network, compute, database), 5 to 15 resources per module, prevent_destroy on critical resources like databases and buckets.
- Enforce policy as code in CI: terraform validate and plan on every PR, tflint plus tfsec or checkov gates, and any plan that shows a destroy fails the pipeline by default.
- Version modules semantically and prove them with Terratest (apply the example, assert outputs, destroy) before they enter the shared registry.
One power source. 6 lines out.
terraform-module-library · core
core active · 6 lines
- ✓ reusable vpc, rds, eks and
Reusable VPC, RDS, EKS and storage modules
- ✓ standardizing multi-clou…
Standardizing multi-cloud resource provisioning
- ✓ composing root modules f…
Composing root modules from building blocks
- ✓ enforcing organizational…
Enforcing organizational Terraform standards
- ✓ input validation and ver…
Input validation and version pinning
- ✓ terratest-backed module…
Terratest-backed module testing
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Stop repeating infrastructure code with a single DRY source of truth
license: perpetual -
Shrink blast radius by splitting state along network, compute and data domains
license: perpetual -
Catch misconfigurations at plan time, where fixes cost far less than at apply
license: perpetual -
Provision identically across AWS, Azure and GCP with one interface contract
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Standard module structure (main/variables/outputs/versions/examples/tests)
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Platform and DevOps engineers building standardized, multi-cloud infrastructure-as-code that the whole team can reuse safely.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
We are AWS-only, is the multi-cloud angle wasted on us?
No, the core of the library is the standard main/variables/outputs/versions layout, input validation and Terratest coverage, which pay off on a single cloud just as much. The included worked example is in fact an AWS VPC module wired into RDS; Azure and GCP are the same interface contract applied elsewhere.
-
How does it catch misconfigurations before anything is provisioned?
Variable validation blocks reject bad input at plan time: CIDR regex checks, allowed-value lists and numeric bounds, and lifecycle guards like prevent_destroy protect stateful resources. Terratest then runs real apply/destroy cycles in CI, so what reaches production has been exercised.
-
Does it ship a finished module for every resource I might need?
No. You get the structure, the validation patterns, a complete VPC example, composition recipes and a Terratest scaffold: not a registry covering every AWS, Azure and GCP service. Modules beyond the examples you build yourself, following the same layout.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.