A Site-to-Site VPN with Modern Crypto, BGP, and a Connection

A connection with no ipsec_policy negotiates from a built-in list that still offers 1024-bit Diffie-Hellman and SHA-1, so a peer that proposes them gets them and the tunnel comes up looking healthy. Always writes an explicit policy and refuses the weak groups. A gateway with no connection bills by the hour for nothing, so the sites come with the gateway; BGP is on, Basic is refused.

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.

terraformAzureNetworking & VPCv1.0.0static-validated

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.

A Virtual WAN Hub with Connections and Encrypted Branches An ExpressRoute Circuit with Peering and No Illusion of Encryption Azure Private Endpoint (Private Link)Azure Virtual Network (hub-ready)Egress with Enough SNAT Ports to Survive the Afternoon

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.

A Site-to-Site VPN on IKEv2 with Both Tunnels ConfiguredOracle Cloud HA VPN (Site-to-Site)Google Cloud Site-to-Site VPN with Modern CryptoAWS

Installing it

module "azure_vpn_gateway" {
  source  = "www.iac-bazaar.com/iac-bazaar/azure-vpn-gateway/azure"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.