Google Compute Engine Node Template

This page shows how to write Terraform for Compute Engine Node Template and write them securely.

google_compute_node_template (Terraform)

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

Example Usage from GitHub
resource "google_compute_node_template" "soletenant_tmpl" {
  name      = "soletenant-template"
  region    = "us-central1"
  node_type = "n1-node-96-624"
resource "google_compute_node_template" "this" {
  description          = var.description
  name                 =
  node_affinity_labels = var.node_affinity_labels
  node_type            = var.node_type
  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).


CPU overcommit. Default value: "NONE" Possible values: ["ENABLED", "NONE"]

Creation timestamp in RFC3339 text format.

An optional textual description of the resource.

  • id optional computed - string
  • name optional - string

Name of the resource.

Labels to use for node affinity, which will be used in instance scheduling.

Node type to use for nodes group that are created from this template. Only one of nodeTypeFlexibility and nodeType can be specified.

Region where nodes using the node template will be created. If it is not provided, the provider region is used.

  • self_link optional computed - string
  • node_type_flexibility list block

    Number of virtual CPUs to use.

    Use local SSD

    Physical memory available to the node, defined in MB.

  • server_binding list block

    Type of server binding policy. If 'RESTART_NODE_ON_ANY_SERVER', nodes using this template will restart on any physical server following a maintenance event. If 'RESTART_NODE_ON_MINIMAL_SERVER', nodes using this template will restart on the same physical server following a maintenance event, instead of being live migrated to or restarted on a new physical server. This option may be useful if you are using software licenses tied to the underlying server characteristics such as physical sockets or cores, to avoid the need for additional licenses when maintenance occurs. However, VMs on such nodes will experience outages while maintenance is applied. Possible values: ["RESTART_NODE_ON_ANY_SERVER", "RESTART_NODE_ON_MINIMAL_SERVERS"]

  • timeouts single block

Explanation in Terraform Registry

Represents a NodeTemplate resource. Node templates specify properties for creating sole-tenant nodes, such as node type, vCPU and memory requirements, node affinity labels, and region. To get more information about NodeTemplate, 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 Node Template?

Google Compute Engine Node Template 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 Node Template?

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


Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.