Google Compute Engine Network Peering Routes Config

This page shows how to write Terraform for Compute Engine Network Peering Routes Config and write them securely.

google_compute_network_peering_routes_config (Terraform)

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

Example Usage from GitHub
resource "google_compute_network_peering_routes_config" "peering" {
    peering                 =
    network                 = var.network_id
    import_custom_routes    = var.import_custom_routes
    export_custom_routes    = var.export_custom_routes
    depends_on              = ["google_compute_network_peering.first_network_peering"]
resource "google_compute_network_peering_routes_config" "this" {
  export_custom_routes = var.export_custom_routes
  import_custom_routes = var.import_custom_routes
  network              =
  peering              = var.peering
  project              = var.project

Review your Terraform file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).


Whether to export the custom routes to the peer network.

Whether to import the custom routes to the peer network.

The name of the primary network for the peering.

Name of the peering.

Explanation in Terraform Registry

Manage a network peering's route settings without managing the peering as a whole. This resource is primarily intended for use with GCP-generated peerings that shouldn't otherwise be managed by other tools. Deleting this resource is a no-op and the peering will not be modified. To get more information about NetworkPeeringRoutesConfig, see:

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.



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.



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.



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.



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.



Ensure to use modern TLS protocols

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



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.

Review your Google Compute Engine settings

In addition to the above, there are other security points you should be aware of making sure that your .tf files are protected in Shisho Cloud.

Frequently asked questions

What is Google Compute Engine Network Peering Routes Config?

Google Compute Engine Network Peering Routes Config 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 Network Peering Routes Config?

For Terraform, the rajecloud/DevOps and niveklabs/google source code examples are useful. See the Terraform Example section for further details.