Google Compute Engine Network

google_compute_network (Terraform)

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

Example Usage from GitHub

wwce/terraform

resource "google_compute_network" "management_network" {
  project                 = google_project.blue_team_project.project_id
  name                    = "management"
  auto_create_subnetworks = false
}

netfryer/terraform

resource "google_compute_network" "management_network" {
  project                 = google_project.globalprotect.number
  name                    = "management"
  auto_create_subnetworks = false
}
resource "google_compute_network" "untrust_network" {

Parameters

• auto_create_subnetworks optional - bool

When set to 'true', the network is created in "auto subnet mode" and it will create a subnet for each region automatically across the '10.128.0.0/9' address range. When set to 'false', the network is created in "custom subnet mode" so the user can explicitly connect subnetwork resources.

• delete_default_routes_on_create optional - bool
• description optional - string

An optional description of this resource. The resource must be recreated to modify this field.

• gateway_ipv4 optional computed - string

The gateway address for default routing out of the network. This value is selected by GCP.

• id optional computed - string
• mtu optional computed - number

Maximum Transmission Unit in bytes. The minimum value for this field is 1460 and the maximum value is 1500 bytes.

• 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.

• project optional computed - string
• routing_mode optional computed - string

The network-wide routing mode to use. If set to 'REGIONAL', this network's cloud routers will only advertise routes with subnetworks of this network in the same region as the router. If set to 'GLOBAL', this network's cloud routers will advertise routes with all subnetworks of this network, across regions. Possible values: ["REGIONAL", "GLOBAL"]

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

Explanation in Terraform Registry

Manages a VPC network or legacy network resource on GCP. To get more information about Network, 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.