Google Compute Engine Network Endpoint

google_compute_network_endpoint (Terraform)

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

Example Usage from GitHub

niveklabs/google

resource "google_compute_network_endpoint" "this" {
  instance               = var.instance
  ip_address             = var.ip_address
  network_endpoint_group = var.network_endpoint_group
  port                   = var.port
  project                = var.project

sthamma/cloud-foundations

resource "google_compute_network_endpoint" "endpoint" {
  for_each               = { for endpoint in var.endpoints : endpoint.instance => endpoint }
  project                = var.project_id
  network_endpoint_group = google_compute_network_endpoint_group.group.name
  instance               = each.value.instance
  port                   = each.value.port

Rpb1980/cloud-foundation-fabric

resource "google_compute_network_endpoint" "endpoint" {
  for_each               = { for endpoint in var.endpoints : endpoint.instance => endpoint }
  project                = var.project_id
  network_endpoint_group = google_compute_network_endpoint_group.group.name
  instance               = each.value.instance
  port                   = each.value.port

koichiroes/hobby

resource "google_compute_network_endpoint" "kubeadm" {
  network_endpoint_group = google_compute_network_endpoint_group.kubeadm.name

  instance   = google_compute_instance.kubeadm.name
  port       = google_compute_network_endpoint_group.kubeadm.default_port
  ip_address = google_compute_instance.kubeadm.network_interface[0].network_ip

terraform-google-modules/cloud-foundation-fabric

resource "google_compute_network_endpoint" "endpoint" {
  for_each               = { for endpoint in var.endpoints : endpoint.instance => endpoint }
  project                = var.project_id
  network_endpoint_group = google_compute_network_endpoint_group.group.name
  instance               = each.value.instance
  port                   = each.value.port

Parameters

• id optional computed - string
• instance required - string

The name for a specific VM instance that the IP address belongs to. This is required for network endpoints of type GCE_VM_IP_PORT. The instance must be in the same zone of network endpoint group.

• ip_address required - string

IPv4 address of network endpoint. The IP address must belong to a VM in GCE (either the primary IP or as part of an aliased IP range).

• network_endpoint_group required - string

The network endpoint group this endpoint is part of.

• port required - number

Port number of network endpoint.

• project optional computed - string
• zone optional computed - string

Zone where the containing network endpoint group is located.

• timeouts single block
  • create optional - string
  • delete optional - string

Explanation in Terraform Registry

A Network endpoint represents a IP address and port combination that is part of a specific network endpoint group (NEG). NEGs are zonal collections of these endpoints for GCP resources within a single subnet. NOTE: Network endpoints cannot be created outside of a network endpoint group. To get more information about NetworkEndpoint, 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.