Google Compute Engine Network Peering

google_compute_network_peering (Terraform)

The Network Peering in Compute Engine can be configured in Terraform with the resource name google_compute_network_peering. The following sections describe 3 examples of how to use the resource and its parameters.

Example Usage from GitHub

GoogleCloudPlatform/gcp-token-broker

resource "google_compute_network_peering" "origin_broker_peering1" {
  name         = "origin-broker-peering1"
  network      = google_compute_network.origin.self_link
  peer_network = google_compute_network.broker.self_link
  depends_on = [
    google_compute_subnetwork.broker_cluster_subnet,

simenkrantz/terraform_2S

resource "google_compute_network_peering" "peering_1" {
  name         = var.peering_1_name
  network      = google_compute_network.vpc_network_1.id
  peer_network = google_compute_network.vpc_network_2.id
}

kaysal/cloud-networking

resource "google_compute_network_peering" "vpc2_to_spoke" {
  provider     = google-beta
  name         = "vpc2-to-spoke"
  network      = local.vpc2.self_link
  peer_network = local.spoke.self_link

Parameters

• export_custom_routes optional - bool

Whether to export the custom routes to the peer network. Defaults to false.

• export_subnet_routes_with_public_ip optional - bool
• id optional computed - string
• import_custom_routes optional - bool

Whether to export the custom routes from the peer network. Defaults to false.

• import_subnet_routes_with_public_ip optional - bool
• name required - string

Name of the peering.

• network required - string

The primary network of the peering.

• peer_network required - string

The peer network in the peering. The peer network may belong to a different project.

• state optional computed - string

State for the peering, either ACTIVE or INACTIVE. The peering is ACTIVE when there's a matching configuration in the peer network.

• state_details optional computed - string

Details about the current state of the peering.

• timeouts single block
  • create optional - string
  • delete optional - string
  • update optional - string

Explanation in Terraform Registry

Manages a network peering within GCE. For more information see the official documentation and API. -> Both network must create a peering with each other for the peering to be functional.

Subnets IP ranges across peered VPC networks cannot overlap.

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.