Transit Gateway Hub with Explicit Routing
Hub-and-spoke Transit Gateway with its own route tables, VPC attachments, static and blackhole routes, and RAM sharing. Default route table association and propagation are off, so an attachment joins a routing domain because you said so rather than by default.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- Security scan pending (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live test pending (no cloud run yet)
Last verified 2026-09-12 · how we verify
Use it from the registry
terraform · opentofumodule "transit_gateway" {
source = "www.iac-bazaar.com/iac-bazaar/aws-transit-gateway/aws"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
aws-transit-gateway
Transit Gateway hub with explicit route tables, VPC attachments, static and
blackhole routes, and optional RAM sharing across an AWS Organization. Works
with Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
The gotcha this module exists to remove: a Transit Gateway created with its default route table association and propagation left on puts every attachment into one routing domain, so any VPC can reach any other the moment it attaches. Nothing errors when that happens - routes simply appear - which is why it ships to production so often. Here the defaults are off and every association is something you wrote down.
Secure defaults:
- Default route table association and propagation disabled, on the gateway and again on each attachment
- Attachment requests from shared accounts are not auto-accepted: an attachment is a route into your network
- RAM shares refuse external principals; sharing reaches your organization or an OU, not the internet
- Association and propagation are separate inputs, because what an attachment can REACH and who can reach IT are different decisions
Verification
Static validation runs tofu fmt, init, validate, tflint and checkov.
This module has not yet had a live test: creating a Transit Gateway and
attaching VPCs bills per attachment-hour, so it is published as statically
validated with its live test pending, and the catalog says exactly that. It
does not carry the live-tested mark and will not until a real
apply -> verify -> destroy has run with confirmed teardown.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Routing model
- Inputs, outputs
Related modules
aws-client-vpn
Remote-access VPN endpoint with certificate or SAML authentication, split tunnelling, per-group authorization rules and connection logging. There is no allow-all shortcut: an endpoint with no rule reaches nothing.
aws-cloud-map
Private DNS, public DNS or API-only namespaces and the services registered in them. Documents the health-check trap: a private namespace gets a custom check that something else must update, and one nobody updates reports healthy forever.
aws-cloud-wan
A global network whose segments, routing and attachment placement live in one policy document rather than per-region route tables. The policy VERSION is executed as a second step, so a change cannot report success while the network still runs the previous one.
aws-vpc
Battle-tested multi-AZ VPC with public/private/database subnets, NAT, endpoints, and flow logs.
aws-site-to-site-vpn
Customer gateway, IPsec connection and routes, attached to a VPN gateway or a Transit Gateway. IKEv2 only, DH group 14 and above, AES-256 and SHA-2 - the API still permits DH 2, AES-128 and SHA-1.
aws-vpc-endpoints
Free gateway endpoints for S3 and DynamoDB, interface endpoints for everything else, and a security group that opens 443 to the VPC rather than the world. Interface endpoints are listed explicitly because each bills per hour per availability zone.