Google Compute Engine Network Peering Routes Config

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

rajecloud/DevOps

resource "google_compute_network_peering_routes_config" "peering" {
    peering                 = google_compute_network_peering.first_network_peering.name
    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"]

niveklabs/google

resource "google_compute_network_peering_routes_config" "this" {
  export_custom_routes = var.export_custom_routes
  import_custom_routes = var.import_custom_routes
  network              = var.network
  peering              = var.peering
  project              = var.project

Parameters

• export_custom_routes required - bool

Whether to export the custom routes to the peer network.

• id optional computed - string
• import_custom_routes required - bool

Whether to import the custom routes to the peer network.

• network required - string

The name of the primary network for the peering.

• peering required - string

Name of the peering.

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

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:

• API documentation
• How-to Guides
  • Official Documentation

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.