GCP VPC Network Foundation
Production VPC with subnets, secondary ranges, firewall rules, Cloud Router and Cloud NAT - the network base every GCP workload sits on.
Compare Virtual Private Cloud (VPC) across clouds →
Part of: GCP Production Landing Zone, GCP Kubernetes Platform
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o gcp-vpc-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-vpc/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-vpc-1.0.0.sigstore.json \
gcp-vpc-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "15bfa5784d0ed0c3587749edaa4b1cc04bf318773b76f8f8601ce834ff19513f gcp-vpc-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "vpc" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-vpc/gcp"
version = "1.0.0"
}Paid module — needs a purchase (or a subscription that covers it) plus a registry token from /account/tokens. 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 Free module. This one is Professional, so its contract unlocks when you buy it.
Documentation
gcp-vpc
Production VPC with subnets, secondary ranges, firewall rules, Cloud Router
and Cloud NAT — the network base every GCP workload sits on. Works with
Terraform and OpenTofu (>= 1.6), Google provider >= 7.0, < 8.0.
Secure defaults:
- Custom-mode network (no auto subnets), Private Google Access on per subnet
- VPC flow logs on by default (5-min aggregation, 50% sampling, all metadata)
- No public SSH: baseline rule allows SSH only from Google's IAP range
(
35.235.240.0/20); pair withgcloud compute ssh --tunnel-through-iap - Allow-internal baseline covers secondary ranges, so GKE pod-to-pod works
- Cloud NAT (auto-allocated IPs, error logging) per region — private instances get egress without external IPs
- Firewall rule logging on by default; every rule must be explicitly allow XOR deny
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/google>= 7.0, < 8.0
Notes for integrators:
subnet_secondary_rangesis shaped to feed straight into GKE (cluster_secondary_range_name/services_secondary_range_name).- Cloud NAT here uses
AUTO_ONLYIP allocation and NATs all subnet ranges in the region; bring static NAT IPs in a wrapper if you need allowlisting. - If you set
delete_default_routes_on_create = true, nothing in the VPC can reach the internet (even via NAT) until you add a default route back.
License
Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).
Usage code & full reference unlock after purchase
The complete copy-paste usage, the full input/output reference, and operational notes ship with your licence - shown here and bundled in the download.
- Usage
- Inputs
- Outputs
Related modules
Cloud NAT Gateway
A regional Cloud Router and Cloud NAT gateway giving private, external-IP-less instances outbound internet access, with auto-allocated NAT IPs, all-subnet coverage, and logging on by default.
HA VPN (Site-to-Site)
99.99% SLA HA VPN gateway pair with BGP-dynamic routing - GCP-to-on-prem or GCP-to-AWS/Azure.
Alibaba Cloud VPC Foundation
Multi-AZ VPC with vSwitches, NAT gateway, SNAT, security groups, and flow logs.
Azure Virtual Network (hub-ready)
Production VNet with subnets, NSGs, route tables, peering and optional NAT Gateway - the network backbone every Azure deployment starts with.
Hetzner Private Network + NAT
Private network with subnets, routes, and a NAT gateway server for egress-only fleets.
IBM Cloud VPC Landing Zone (Lite)
VPC with subnets, public gateways, ACLs, and security groups following IBM SLZ patterns.