Skip to main content

GCP Compute Region Backend Service

A regional backend service represents the collection of back-end instances or endpoints that receive traffic from a Google Cloud regional load balancer (Internal TCP/UDP or Regional external HTTP(S)). It defines how traffic is distributed, health-checked and secured across these back-ends, and contains settings such as session affinity, connection draining and Cloud Armor security policies. See the official Google documentation for full details: https://cloud.google.com/load-balancing/docs/backend-service

Terrafrom Mappings:

  • google_compute_region_backend_service.name

Supported Methods​

  • GET: Get GCP Compute Region Backend Service by "gcp-compute-region-backend-service-name"
  • LIST: List all GCP Compute Region Backend Service items
  • SEARCH

gcp-compute-instance-group​

A backend service targets one or more instance groups (managed or unmanaged). These instance groups supply the actual VM instances that serve traffic, and are referenced in the backend service’s backend blocks.

gcp-compute-network​

For internal load balancers, the backend service is bound to a specific VPC network; traffic from the load balancer to the back-ends stays within this network. The link shows which network the backend service operates in.

gcp-compute-security-policy​

A backend service can have an optional Cloud Armor security policy attached. The policy defines layer-7 rules that allow, deny or rate-limit requests before they reach the back-ends.