Tencent Cloud VPC Foundation
VPC with subnets, route tables, NAT, and security groups across AZs.
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 clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live test pending (no cloud run yet)
Last verified 2026-06-28 · 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 tencent-vpc-foundation-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/tencent-vpc-foundation/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle tencent-vpc-foundation-1.0.0.sigstore.json \
tencent-vpc-foundation-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "b339b22d63b8a363509719966d736f76293c4885ca51f23e3138cee3a9f8f06f tencent-vpc-foundation-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "vpc_foundation" {
source = "www.iac-bazaar.com/iac-bazaar/tencent-vpc-foundation/tencentcloud"
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
tencent-vpc-foundation
A production-ready Tencent Cloud network foundation: a multi-AZ VPC with subnets, a standard NAT gateway (EIP + per-subnet SNAT and a default route for outbound-only internet egress), and a least-privilege base security group. Subnets opt in to internet egress one at a time; everything else stays private with no public addressing.
Status: static-validated, live-test pending. Validated with
tofu validate+tflint+checkovagainst thetencentcloudstack/tencentcloudprovider. Not yet applied against a live Tencent Cloud account (no sandbox subscription), so it ships under live-test quarantine.
Design & secure defaults
- No inbound exposure by default. The base security group denies all
inbound traffic until you declare
ingress_rules; egress is allowed and (optionally) intra-VPC traffic is permitted viaallow_intra_security_group. - Outbound-only egress. Only subnets with
nat = trueget a default route to the NAT gateway and a matching SNAT entry. There is no internet gateway and no public IP on any instance, so workloads are never directly addressable. - Two route tables, explicit isolation. Private subnets attach to a route
table with only the implicit local route (no
0.0.0.0/0); NAT subnets attach to a separate table whose default route points at the NAT gateway. - Standard (v2) NAT gateway by default, with a traffic-billed EIP, so
nat_bandwidth_mbpsis a ceiling on the EIP's egress. Standard NAT fixes the gateway's own bandwidth and concurrency, sonat_bandwidth_mbps/nat_max_concurrentonly size the gateway when you opt into traditional NAT (nat_product_version = 1). Tencent accepts only fixed tiers, which the variables validate.
Provider
tencentcloudstack/tencentcloud >= 1.81.0, < 2.0. Requires Terraform/OpenTofu
>= 1.6.
License
Commercial — LicenseRef-IaCBazaar-Commercial. See the IaC Bazaar terms.
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
- Key inputs
- Outputs
Related modules
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.
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.
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.
Linode VPC with Subnets
Isolated VPC network with labeled subnets ready for instances, LKE, and NodeBalancer backends.