A VPN Gateway and Policy-Based IPsec Connection on IKEv2 with Tencent's Weak Defaults Refused
A Tencent Cloud VPN gateway (pay-by-hour; prepaid by name) with a customer gateway and one policy-based IPsec connection on IKEv2 negotiating AES-CBC-256, SHA-256 and DH group 14 in both phases. Tencent's own defaults are 3DES, MD5 and group 1; the validations refuse them, IKEv1 is accepted only by name, and dead peer detection restarts a dead tunnel.
This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.
Provider drift
This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.
What depends on this
No reference architecture names this module, so changing it affects only configurations that reference it directly.
Nearest alternatives
Same cloud, same category. These are what you would weigh against it without changing provider.
The same job on other clouds
Site-to-Site VPN on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.
Installing it
module "tencent_vpn_gateway" {
source = "www.iac-bazaar.com/iac-bazaar/tencent-vpn-gateway/tencentcloud"
version = "1.0.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.