SSH without a Bastion, a Public IP, or an Open Port

IAP TCP forwarding reaches an instance from one Google range after the user is authenticated and authorised, and a firewall rule that also admits 0.0.0.0/0 on port 22 has the bastion's problem back. The range is a literal, tunnel access is granted per instance rather than to every instance in the project, and OS Login is set so the SSH identity is the IAM identity rather than whoever holds a key.

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.

terraformGoogle CloudSecurity & Identityv1.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 Firewall Policy that Governs a Network and Leaves a Record A Perimeter that Enforces rather than Rehearses A reCAPTCHA Key that Is Scored, Scoped, and Not in Testing Mode An IDS Endpoint that Is Actually Looking at Traffic Cloud Armor Security Policy (WAF)Findings that Reach a Topic, Mutes that Say Why Keyless Access Scoped to Callers You Meant Only Images Somebody Vouched For Get to Run

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "gcp_iap_tunnel" {
  source  = "www.iac-bazaar.com/iac-bazaar/gcp-iap-tunnel/gcp"
  version = "1.0.0"
}

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