Google Compute Engine Ha VPN Gateway

google_compute_ha_vpn_gateway (Terraform)

The Ha VPN Gateway in Compute Engine can be configured in Terraform with the resource name google_compute_ha_vpn_gateway. The following sections describe 3 examples of how to use the resource and its parameters.

Example Usage from GitHub

PacketBeta/gcve-cloudvpn-transit-vpc

resource "google_compute_ha_vpn_gateway" "gcve_gateway" {
  region   = var.region
  name     = var.gcve["gateway_name"]
  network  = data.google_compute_network.gcve.id
}

TanAlex/gcp-terraform-sample

resource "google_compute_ha_vpn_gateway" "ha_gateway1" {
  region   = "us-central1"
  name     = "ha-vpn-1"
  network  = google_compute_network.network1.id
}

kaysal/cloud-networking

resource "google_compute_ha_vpn_gateway" "vpc_alamos_vpngw" {
  provider = google-beta
  region   = "europe-west2"
  name     = "vpc-alamos-vpngw"
  network  = "default"
}

Parameters

• description optional - string

An optional description of this resource.

• id optional computed - string
• name required - string

Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression 'a-z?' which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.

• network required - string

The network this VPN gateway is accepting traffic for.

• project optional computed - string
• region optional computed - string

The region this gateway should sit in.

• self_link optional computed - string
• vpn_interfaces optional computed - list of object

A list of interfaces on this VPN gateway.

• id - number
• ip_address - string
• timeouts single block
  • create optional - string
  • delete optional - string

Explanation in Terraform Registry

Represents a VPN gateway running in GCP. This virtual device is managed by Google, but used only by you. This type of VPN Gateway allows for the creation of VPN solutions with higher availability than classic Target VPN Gateways. To get more information about HaVpnGateway, see:

• API documentation
• How-to Guides
  • Choosing a VPN
    • Cloud VPN Overview

Tips: Best Practices for The Other Google Compute Engine Resources

In addition to the google_compute_disk, Google Compute Engine has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.

google_compute_disk

Ensure the encryption key for your GCE disk is stored securely

It is better to store the encryption key for your GCE disk securely. Secret Manager could be used instead.

google_compute_firewall

Ensure your VPC firewall blocks unwanted outbound traffic

It is better to block unwanted outbound traffic not to expose resources in the VPC to unwanted attacks.

google_compute_instance

Ensure appropriate service account is assigned to your GCE instance

It is better to create a custom service account for the instance and assign it.

google_compute_project_metadata

Ensure OS login for your GCE instances is enabled at project level

It is better to enable OS login for your GCE instances. Enabling OS login ensures that SSH keys used to connect to instances are mapped with IAM users, allowing centralized and automated SSH key management.

google_compute_ssl_policy

Ensure to use modern TLS protocols

It's better to adopt TLS v1.2+ instead of outdated TLS protocols.

google_compute_subnetwork

Ensure VPC flow logging is enabled

It is better to enable VPC flow logging. VPC flow logging allows us to audit traffic in your network.