Google Compute Engine Global Network Endpoint

This page shows how to write Terraform for Compute Engine Global Network Endpoint and write them securely.

google_compute_global_network_endpoint (Terraform)

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

Example Usage from GitHub
resource "google_compute_global_network_endpoint" "this" {
  fqdn                          = var.fqdn
  global_network_endpoint_group = var.global_network_endpoint_group
  ip_address                    = var.ip_address
  port                          = var.port
  project                       = var.project
resource "google_compute_global_network_endpoint" "proxy" {
  global_network_endpoint_group =
  fqdn                          = ""
  port                          = google_compute_global_network_endpoint_group.external_proxy.default_port

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


Fully qualified domain name of network endpoint. This can only be specified when network_endpoint_type of the NEG is INTERNET_FQDN_PORT.

The global network endpoint group this endpoint is part of.

IPv4 address external endpoint.

Port number of the external endpoint.

Explanation in Terraform Registry

A Global Network endpoint represents a IP address and port combination that exists outside of GCP. NOTE: Global network endpoints cannot be created outside of a global network endpoint group. To get more information about GlobalNetworkEndpoint, 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 Global Network Endpoint?

Google Compute Engine Global Network Endpoint 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 Global Network Endpoint?

For Terraform, the niveklabs/google and sanjeevgopinath/gcp-cdn-tf source code examples are useful. See the Terraform Example section for further details.