You create a load balancer in your application by configuring and connecting distinct Cloud Load Balancing frontend and backend components. The separate components help you apply distinct controls for external and internal traffic, and prevent direct access to data.
The regional Cloud Load Balancing frontend component helps you configure the public-facing elements of a load balancer. The frontend handles incoming traffic, defines routing rules, and directs requests to the appropriate backend. You can configure the following:
- Target Proxy: Terminates client connections and forwards requests.
- URL Map: Defines routing rules based on hostnames and URL paths.
- Forwarding Rule: Assigns an IP address and port to the load balancer, making it accessible.
For more information, see Cloud Load Balancing overview .
This document describes the connections and parameters you can configure when using App Design Center to create a regional Cloud Load Balancing frontend. The configuration parameters are based on the terraform-google-regional-lb-http Terraform module.
Component connections
To create a complete Cloud Load Balancing component, you must connect your regional Cloud Load Balancing frontend to at least one regional Cloud Load Balancing backend. Connected Cloud Load Balancing components are displayed as a group in the design canvas.
The following table includes the components that you can connect to a regional Cloud Load Balancing frontend, and the resulting updates to your application and its generated Terraform code.
Connected component
Application updates
Background information
- The Compute Engine instances can redirect traffic to the regional Cloud Load Balancing frontend.
- The Cloud Load Balancing address is added to the Compute Engine instance template.
- The HTTP and HTTPS IP addresses of the load balancer are available to the application running in the Cloud Run container.
- The Cloud Load Balancing address metadata is added to the Cloud Run environment variables.
Regional Cloud Load Balancing backend (required)
- The Cloud Load Balancing frontend, which handles incoming requests, is linked to the Cloud Load Balancing backend, which processes the requests.
- The backend service information is added to the frontend URL map input.
- Incoming traffic is served based on the host path mappings you configure in the regional Cloud Load Balancing backend URL maps.
Required configuration parameters
If your template includes a regional Cloud Load Balancing frontend component, you must configure the following parameters before you deploy.
| Parameter name |
Description and constraints |
Background information |
|---|---|---|
| Project ID |
The project where you want to deploy the Cloud Load Balancing frontend. |
Configure components |
| Region |
region | Forwarding rules overview |
| Name |
name | Forwarding rules overview |
| Network |
network | Forwarding rules overview |
Optional configuration parameters
The following parameters are optional. To display advanced parameters, in the Configurationarea, select Show advanced fields.
Feature
Parameter name
Description and constraint information
Background information
- Enable Create SSL Certificateand enter Private Keyand Certificate.
- Enter SSL Certificates.
- Enter Managed SSL Certificate Domains.
What's next
You must connect your frontend component to a backend component. To configure the backend component, see Configure a regional Cloud Load Balancing backend service in Application Design Center .
