Cloud WAN Global Network and Segments
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.
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 "cloud_wan" {
source = "www.iac-bazaar.com/iac-bazaar/aws-cloud-wan/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-cloud-wan
Cloud WAN: a global network whose segments, routing and attachment placement
live in one policy document rather than in per-region route tables. Works with
Terraform and OpenTofu (>= 1.6), AWS provider >= 6.0, < 7.0.
The trap this module closes. Cloud WAN does not apply a policy when you
write it - it creates a new policy version, and that version has to be
executed separately. A module that wrote the document and stopped would leave
the network running the previous policy while Terraform reported success. The
aws_networkmanager_core_network_policy_attachment resource here is that second
step, and attachments depend on it.
Defaults worth knowing:
- Nothing crosses a segment boundary unless a
segment_actionsays so. A segment is a routing domain; shared services reach the spokes because an action shares it, and the spokes do not reach each other isolate_attachmentsgoes further and stops attachments inside the same segment reaching each other - what a segment of mutually untrusting tenants wantsrequire_attachment_acceptancedefaults to true: an attachment is a route into your global network- Each edge location bills per hour, so the list is the regions you actually route through rather than everywhere you might one day
Verification
Static validation runs tofu fmt, init, validate, tflint and checkov.
This module has not yet had a live test, so it is published as statically
validated with its live test pending and does not carry the live-tested mark.
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
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-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-transit-gateway
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.
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.