Google Compute Engine Region Network Endpoint Group

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

google_compute_region_network_endpoint_group (Terraform)

The Region Network Endpoint Group in Compute Engine can be configured in Terraform with the resource name google_compute_region_network_endpoint_group. The following sections describe 5 examples of how to use the resource and its parameters.

Example Usage from GitHub

main.tf#L50
resource "google_compute_region_network_endpoint_group" "serverless_neg_tw" {
  provider              = google-beta
  name                  = "serverless-neg-tw-20210928-001"
  network_endpoint_type = "SERVERLESS"
  region                = "asia-east1"
  cloud_run {
lb.tf#L25
resource "google_compute_region_network_endpoint_group" "frontend" {
  depends_on = [
    google_project_service.compute
  ]
  project = var.project
  region  = var.region
lb.tf#L68
resource "google_compute_region_network_endpoint_group" "news_api_us" {
  provider = google-beta

  project               = var.project
  name                  = "news-api-us"
  network_endpoint_type = "SERVERLESS"
template.tf#L164
resource "google_compute_region_network_endpoint_group" "templatee_neg_fe" {
  provider              = google-beta
  name                  = "templatee-neg-frontend"
  network_endpoint_type = "SERVERLESS"
  region                = var.region
  cloud_run {
network_endpoint_group.tf#L2
resource "google_compute_region_network_endpoint_group" "prd" {
  name                  = local.NEG_NAME
  network_endpoint_type = "SERVERLESS"
  region                = var.GCP_DEPLOYMENT_REGION
  project               = data.google_project.primary.number
  cloud_run {

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

Parameters

An optional description of this resource. Provide this property when you create the resource.

  • id optional computed - string
  • 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.

Type of network endpoints in this network endpoint group. Defaults to SERVERLESS Default value: "SERVERLESS" Possible values: ["SERVERLESS"]

A reference to the region where the Serverless NEGs Reside.

  • self_link optional computed - string
  • app_engine list block

    Optional serving service. The service name must be 1-63 characters long, and comply with RFC1035. Example value: "default", "my-service".

    A template to parse service and version fields from a request URL. URL mask allows for routing to multiple App Engine services without having to create multiple Network Endpoint Groups and backend services. For example, the request URLs "foo1-dot-appname.appspot.com/v1" and "foo1-dot-appname.appspot.com/v2" can be backed by the same Serverless NEG with URL mask "-dot-appname.appspot.com/". The URL mask will parse them to [ service = "foo1", version = "v1" ] and [ service = "foo1", version = "v2" ] respectively.

    Optional serving version. The version must be 1-63 characters long, and comply with RFC1035. Example value: "v1", "v2".

  • cloud_function list block

    A user-defined name of the Cloud Function. The function name is case-sensitive and must be 1-63 characters long. Example value: "func1".

    A template to parse function field from a request URL. URL mask allows for routing to multiple Cloud Functions without having to create multiple Network Endpoint Groups and backend services. For example, request URLs "mydomain.com/function1" and "mydomain.com/function2" can be backed by the same Serverless NEG with URL mask "/". The URL mask will parse them to [ function = "function1" ] and [ function = "function2" ] respectively.

  • cloud_run list block

    Cloud Run service is the main resource of Cloud Run. The service must be 1-63 characters long, and comply with RFC1035. Example value: "run-service".

    • tag optional - string

    Cloud Run tag represents the "named-revision" to provide additional fine-grained traffic routing information. The tag must be 1-63 characters long, and comply with RFC1035. Example value: "revision-0010".

    A template to parse service and tag fields from a request URL. URL mask allows for routing to multiple Run services without having to create multiple network endpoint groups and backend services. For example, request URLs "foo1.domain.com/bar1" and "foo1.domain.com/bar2" an be backed by the same Serverless Network Endpoint Group (NEG) with URL mask ".domain.com/". The URL mask will parse them to [ service="bar1", tag="foo1" ] and [ service="bar2", tag="foo2" ] respectively.

  • timeouts single block

Explanation in Terraform Registry

A regional NEG that can support Serverless Products. Recreating a region network endpoint group that's in use by another resource will give a resourceInUseByAnotherResource error. Use lifecycle.create_before_destroy to avoid this type of error. To get more information about RegionNetworkEndpointGroup, 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.

risk-label

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.

risk-label

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.

risk-label

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.

risk-label

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.

risk-label

google_compute_ssl_policy

Ensure to use modern TLS protocols

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

risk-label

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.

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 Region Network Endpoint Group?

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

For Terraform, the michael-chi/terraform-gcp, grpcoin/grpcoin and mwarzynski/uw_irio source code examples are useful. See the Terraform Example section for further details.