Google Compute Engine VPN Gateway
This page shows how to write Terraform for Compute Engine VPN Gateway and write them securely.
google_compute_vpn_gateway (Terraform)
The VPN Gateway in Compute Engine can be configured in Terraform with the resource name google_compute_vpn_gateway
. The following sections describe 2 examples of how to use the resource and its parameters.
Example Usage from GitHub
resource "google_compute_vpn_gateway" "gateway-2-to-1" {
name = "gateway-2-to-1"
network = google_compute_network.network-2.self_link
}
resource "google_compute_address" "vpn-address-2-to-1" {
resource "google_compute_vpn_gateway" "this" {
description = var.description
name = var.name
network = var.network
project = var.project
region = var.region
Parameters
-
creation_timestamp
optional computed - string
Creation timestamp in RFC3339 text format.
-
description
optional - string
An optional description of this resource.
-
gateway_id
optional computed - number
The unique identifier for the resource.
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.
The region this gateway should sit in.
Explanation in Terraform Registry
Represents a VPN gateway running in GCP. This virtual device is managed by Google, but used only by you. To get more information about VpnGateway, see:
- API documentation
Warning: Classic VPN is deprecating certain functionality on October 31, 2021. For more information, see the Classic VPN partial deprecation page.
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.
Frequently asked questions
What is Google Compute Engine VPN Gateway?
Google Compute Engine VPN Gateway is a resource for Compute Engine of Google Cloud Platform. Settings can be wrote in Terraform.
Where can I find the example code for the Google Compute Engine VPN Gateway?
For Terraform, the davidheryanto/etc and niveklabs/google source code examples are useful. See the Terraform Example section for further details.