The regional internal proxy Network Load Balancer is a proxy-based regional Layer 4 load balancer that
enables you to run and scale your TCP service traffic behind an internal IP
address that is accessible only to clients in the same Virtual Private Cloud (VPC)
network or clients connected to your VPC
network. If you want to make the service available to clients in other
VPC networks, you can [use Private Service Connect
to publish the service](https://docs.cloud.google.com/vpc/docs/configure-private-service-connect-producer).

This page describes how to configure a regional internal proxy Network Load Balancer to load balance
traffic to backends on-premises or in other cloud
environments that are connected by using [hybrid
connectivity](https://cloud.google.com/hybrid-connectivity). Configuring hybrid connectivity
to connect your networks to Google Cloud is not in scope for this page.

## Overview

In this example, we'll use the load balancer to distribute TCP traffic across
backend VMs located on-premises or in other cloud environments.

In this example, you configure the following deployment:
[![Regional internal proxy Network Load Balancer example configuration with hybrid NEG backends.](https://docs.cloud.google.com/static/load-balancing/images/int-tcp-proxy-hybrid-only.svg)](https://docs.cloud.google.com/static/load-balancing/images/int-tcp-proxy-hybrid-only.svg) Regional internal proxy Network Load Balancer example configuration with hybrid NEG backends (click to enlarge).

The regional internal proxy Network Load Balancer is a regional load balancer. All load balancer components
(backend instance groups, backend service, target proxy, and forwarding rule)
must be in the same region.

## Permissions

To set up hybrid load balancing, you must have the following permissions:

- **On Google Cloud**

  - Permissions to establish hybrid connectivity between Google Cloud and your on-premises environment or other cloud environments. For the list of permissions needed, see the relevant [Network Connectivity product
    documentation](https://docs.cloud.google.com/network-connectivity/docs).
  - Permissions to create a hybrid connectivity NEG and the load balancer. The [Compute Load Balancer Admin
    role](https://docs.cloud.google.com/compute/docs/access/iam#compute.loadBalancerAdmin) (`roles/compute.loadBalancerAdmin`) contains the permissions required to perform the tasks described in this guide.
- **On your on-premises environment or other non-Google Cloud cloud
  environment**

  - Permissions to configure network endpoints that allow services on your on-premises environment or other cloud environments to be reachable from Google Cloud by using an `IP:Port` combination. For more information, contact your environment's network administrator.
  - Permissions to create firewall rules on your on-premises environment or other cloud environments to allow Google's health check probes to reach the endpoints.

Additionally, to complete the instructions on this page, you need to create a
hybrid connectivity NEG, a load balancer, and zonal NEGs (and their endpoints)
to serve as Google Cloud-based backends for the load balancer.

You should be either a project [Owner
or Editor](https://docs.cloud.google.com/iam/docs/roles-overview#basic), or you should have the
following [Compute Engine IAM
roles](https://docs.cloud.google.com/compute/docs/access/iam).

| Task | Required role |
|---|---|
| Create networks, subnets, and load balancer components | [Compute Network Admin](https://docs.cloud.google.com/compute/docs/access/iam.md.txt#compute.networkAdmin) (`roles/compute.networkAdmin`) |
| Add and remove firewall rules | [Compute Security Admin](https://docs.cloud.google.com/compute/docs/access/iam.md.txt#compute.securityAdmin) (`roles/compute.securityAdmin`) |
| Create instances | [Compute Instance Admin](https://docs.cloud.google.com/compute/docs/access/iam.md.txt#compute.instanceAdmin) (`roles/compute.instanceAdmin`) |

## Establish hybrid connectivity

Your Google Cloud and on-premises environment or other cloud environments
must be connected through [hybrid connectivity](https://cloud.google.com/hybrid-connectivity) by using
either Cloud Interconnect VLAN attachments or Cloud VPN
tunnels with Cloud Router or Router appliance VMs. We recommend that you
use a high availability connection.

A Cloud Router enabled with [global dynamic
routing](https://docs.cloud.google.com/network-connectivity/docs/router/concepts/advertised-routes#overview-am-default)
learns about the specific endpoint through Border Gateway Protocol (BGP) and
programs it into your Google Cloud VPC network. Regional
dynamic routing is not supported. Static routes are also not supported.

You can use either the same network or a different VPC network
within the same project to configure both hybrid networking
(Cloud Interconnect or Cloud VPN or a Router appliance VM) and the load balancer. Note
the following:

- If you use different VPC networks, the two networks must be
  connected using either VPC Network Peering or they must be
  [VPC
  spokes](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/vpc-spokes-overview)
  on the same [NCC
  hub](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/overview).

- If you use the same VPC network, ensure that your
  VPC network's subnet CIDR ranges don't conflict with your
  remote CIDR ranges. When IP addresses overlap, subnet routes are prioritized
  over remote connectivity.

For instructions, see the following documentation:

- [Cloud VPN](https://docs.cloud.google.com/network-connectivity/docs/vpn/concepts/overview.md.txt)
- [Cloud Interconnect](https://docs.cloud.google.com/network-connectivity/docs/interconnect/concepts/overview.md.txt)

> [!IMPORTANT]
> **Important:** Don't proceed with the instructions on this page until you set up hybrid connectivity between your environments.

## Set up your environment that is outside Google Cloud

Perform the following steps to set up your on-premises environment or other cloud
environment for hybrid load balancing:

- Configure network endpoints to expose on-premises services to Google Cloud (`IP:Port`).
- Configure firewall rules on your on-premises environment or other cloud environment.
- Configure Cloud Router to advertise certain required routes to your private environment.

### Set up network endpoints

After you set up hybrid connectivity, you configure one or more network
endpoints within your on-premises environment or other cloud environments that
are reachable through Cloud Interconnect or Cloud VPN or
Router appliance by using an `IP:port` combination. This `IP:port`
combination is configured as one or more endpoints for the hybrid connectivity
NEG that is created in Google Cloud later on in this process.

If there are multiple paths to the IP endpoint, routing
follows the behavior described in the [Cloud Router
overview](https://docs.cloud.google.com/network-connectivity/docs/router/concepts/overview).

### Set up firewall rules

The following firewall rules must be created on your on-premises environment
or other cloud environment:

- Create an ingress allow firewall rule in on-premises or other cloud environments to allow traffic from the region's [proxy-only subnet](https://docs.cloud.google.com/load-balancing/docs/proxy-only-subnets.md.txt) to reach the endpoints.
-
  Allowing traffic from Google's health check probe ranges isn't required for hybrid
  NEGs. However, if you're using a combination of hybrid and zonal NEGs in
  a single backend service, you need to allow traffic from the [Google
  health check probe ranges](https://docs.cloud.google.com/load-balancing/docs/health-check-concepts#ip-ranges) for the zonal NEGs.

<br />

### Advertise routes

Configure Cloud Router to
[advertise the following custom IP
ranges](https://docs.cloud.google.com/network-connectivity/docs/router/how-to/advertising-custom-ip) to your
on-premises environment or other cloud environment:

<br />

- The range of the region's proxy-only subnet.

<br />

## Set up your Google Cloud environment

For the following steps, make sure you use the same VPC network
(called <var scope="NETWORK" class="edit" translate="no">NETWORK</var> in this procedure) that
was used to configure hybrid connectivity between the environments. You can
select any subnet from this network to reserve the load balancer's IP address
and create the load balancer. This subnet is referred to as <var scope="LB_SUBNET" class="edit" translate="no">LB_SUBNET</var> in this procedure.

Additionally, make sure the region used (called
<var scope="REGION" class="edit" translate="no">REGION</var> in this
procedure) is the same as that used to create the Cloud VPN tunnel or
Cloud Interconnect VLAN attachment.

### Configure the proxy-only subnet

A [proxy-only subnet](https://docs.cloud.google.com/load-balancing/docs/proxy-only-subnets.md.txt) provides a
set of IP addresses that Google uses to run Envoy proxies on your behalf. The
proxies terminate connections from the client and create new connections to the
backends.

The proxy-only subnet is used by all [Envoy-based regional load
balancers](https://docs.cloud.google.com/load-balancing/docs/proxy-only-subnets) in the <var scope="REGION" class="edit" translate="no">REGION</var> region of the <var scope="NETWORK" class="edit" translate="no">NETWORK</var> VPC network.

There can only be one active proxy-only subnet per region, per
VPC network. You can skip this step if there's already a
proxy-only subnet in this region.

### Console

If you're using the Google Cloud console, you can wait and create the
proxy-only subnet later on the **Load balancing** page.

If you want to create the proxy-only subnet now, use the following steps:

1. In the Google Cloud console, go to the **VPC networks** page.

   [Go to VPC networks](https://console.cloud.google.com/networking/networks/list)
2. Go to the network that was used to configure
   hybrid connectivity between the environments.

3. Click **Add subnet**.

4. Enter a **Name** : <var scope="PROXY_ONLY_SUBNET_NAME" class="edit" translate="no">PROXY_ONLY_SUBNET_NAME</var>.

5. Select a **Region** : <var scope="REGION" class="edit" translate="no">REGION</var>.

6. Set **Purpose** to **Regional Managed Proxy**.

7. Enter an **IP address range** : <var scope="PROXY_ONLY_SUBNET_RANGE" class="edit" translate="no">PROXY_ONLY_SUBNET_RANGE</var>.

8. Click **Add**.

### gcloud

Create the proxy-only subnet with the [`gcloud compute networks subnets
create`](https://docs.cloud.google.com/sdk/gcloud/reference/compute/networks/subnets/create) command.

```
gcloud compute networks subnets create PROXY_ONLY_SUBNET_NAME \
    --purpose=REGIONAL_MANAGED_PROXY \
    --role=ACTIVE \
    --region=REGION \
    --network=NETWORK \
    --range=PROXY_ONLY_SUBNET_RANGE
```

### Reserve the load balancer's IP address

By default, one IP address is used for each forwarding rule. You can
reserve a *shared* IPv4 address, which lets you use the same IPv4 address
with multiple forwarding rules. However, if you want to
[use Private Service Connect to publish the load
balancer](https://docs.cloud.google.com/vpc/docs/configure-private-service-connect-producer),
then do not use a shared IPv4 address for the forwarding rule.

To reserve a static internal IPv4 address for your load balancer, see
[Reserve a new static internal IPv4 or IPv6
address](https://docs.cloud.google.com/vpc/docs/reserve-static-internal-ip-address#reservenewip).

> [!NOTE]
> **Note:** You cannot reserve a *shared* static internal IPv6 address.

### Set up the hybrid connectivity NEG

When creating the NEG, use a <var class="edit" translate="no">ZONE</var> that minimizes the
geographic distance between Google Cloud and your on-premises or other
cloud environment. For example, if you are hosting a service in an on-premises
environment in Frankfurt, Germany, you can specify the `europe-west3-a`
Google Cloud zone when you create the NEG.

Moreover, the <var class="edit" translate="no">ZONE</var> used
to create the NEG should be in the same region where the Cloud VPN
tunnel or Cloud Interconnect VLAN attachment were configured for
hybrid connectivity.

For the available regions and zones, see the [Compute Engine
documentation: Available regions and
zones](https://docs.cloud.google.com/compute/docs/regions-zones#available).

### Console

> [!NOTE]
> **Note:** You can either create the hybrid connectivity NEG now, or you can wait to create it while configuring the load balancer's backend.

To create a hybrid connectivity NEG:

1. In the Google Cloud console, go to the **Network endpoint groups** page.

   [Go to Network endpoint groups](https://console.cloud.google.com/compute/networkendpointgroups/list)  
2. Click **Create network endpoint group**.

3. Enter a **Name** for the hybrid NEG. Referred to as
   <var scope="HYBRID_NEG_NAME" class="edit" translate="no">HYBRID_NEG_NAME</var> in this
   procedure.

4. Select the **Network endpoint group type** : **Hybrid connectivity network
   endpoint group (Zonal)**.

5. Select the **Network** : **<var scope="NETWORK" class="edit" translate="no">NETWORK</var>**

6. Select the **Subnet** : **<var scope="LB_SUBNET" class="edit" translate="no">LB_SUBNET</var>**

7. Select the **Zone** : **<var scope="HYBRID_NEG_ZONE" class="edit" translate="no">HYBRID_NEG_ZONE</var>**

8. Enter the **Default port**.

9. Click **Create**

Add endpoints to the hybrid connectivity NEG:

1. In the Google Cloud console, go to the **Network endpoint groups** page.

   [Go to Network endpoint groups](https://console.cloud.google.com/compute/networkendpointgroups/list)  
2. Click the **Name** of the network endpoint group created in the previous
   step (**<var scope="HYBRID_NEG_NAME" class="edit" translate="no">HYBRID_NEG_NAME</var>** ). You
   see the **Network endpoint group details** page.

3. In the **Network endpoints in this group** section, click **Add network
   endpoint** . You see the **Add network endpoint** page.

4. Enter the **IP address** of the new network endpoint.

5. Select the **Port type**.

   1. If you select **Default**, the endpoint uses the default port for all endpoints in the network endpoint group.
   2. If you select **Custom** , you can enter a different **Port number** for the endpoint to use.
6. To add more endpoints, click **Add network endpoint** and repeat the
   previous steps.

7. After you add all the non-Google Cloud endpoints,
   click **Create**.

### gcloud

1. Create a hybrid connectivity NEG using the
   [`gcloud compute network-endpoint-groups
   create`](https://docs.cloud.google.com/sdk/gcloud/reference/compute/network-endpoint-groups/create)
   command.

   ```
   gcloud compute network-endpoint-groups create HYBRID_NEG_NAME \
      --network-endpoint-type=NON_GCP_PRIVATE_IP_PORT \
      --zone=HYBRID_NEG_ZONE \
      --network=NETWORK
   ```
2. Add the on-premises IP:Port endpoint to the hybrid NEG:

   ```
   gcloud compute network-endpoint-groups update HYBRID_NEG_NAME \
       --zone=HYBRID_NEG_ZONE \
       --add-endpoint="ip=ENDPOINT_IP_ADDRESS,port=ENDPOINT_PORT"
   ```

You can use this command to add the network endpoints you [previously
configured on-premises or in your cloud environment](https://docs.cloud.google.com/load-balancing/docs/tcp/set-up-int-tcp-proxy-hybrid#on-prem-endpoint).
Repeat `--add-endpoint` as many times as needed.

You can repeat these steps to create multiple hybrid NEGs if needed.

## Configure the load balancer

### Console

#### Start your configuration

1. In the Google Cloud console, go to the **Load balancing** page.

   [Go to Load balancing](https://console.cloud.google.com/net-services/loadbalancing/list)
2. Click **Create load balancer**.
3. For **Type of load balancer** , select **Network Load Balancer
   (TCP/UDP/SSL)** and click **Next**.
4. For **Proxy or passthrough** , select **Proxy load balancer** and click **Next**.
5. For **Public facing or internal** , select **Internal** and click **Next**.
6. For **Cross-region or single region deployment** , select **Best for
   regional workloads** and click **Next**.
7. Click **Configure**.

#### Basic configuration

1. Enter a **Name** for the load balancer.
2. Select the **Region** : **<var scope="REGION" class="edit" translate="no">REGION</var>**.
3. Select the **Network** : **<var scope="NETWORK" class="edit" translate="no">NETWORK</var>**.

#### Reserve a proxy-only subnet

> [!NOTE]
> **Note:** If you already [created the proxy-only subnet](https://docs.cloud.google.com/load-balancing/docs/tcp/set-up-int-tcp-proxy-hybrid.md.txt#create-proxy-only-subnet), the **Reserve subnet** button isn't displayed. You can skip this section and continue with the steps in the **Backend configuration** section.

To reserve a proxy-only subnet:

1. Click **Reserve subnet**.
2. Enter the **Name** : <var scope="PROXY_ONLY_SUBNET_NAME" class="edit" translate="no">PROXY_ONLY_SUBNET_NAME</var>.
3. Enter an **IP address range** : <var scope="PROXY_ONLY_SUBNET_RANGE" class="edit" translate="no">PROXY_ONLY_SUBNET_RANGE</var>.
4. Click **Add**.

#### Backend configuration

1. Click **Backend configuration**.
2. For **Backend type** , select **Hybrid connectivity network endpoint
   group (Zonal)**.
3. For **Protocol** , select **TCP**.
4. In the **Health check** list, click **Create a health check** , and then enter the following information:
   1. In the **Name** field, enter a name for the health check.
   2. In the **Protocol** list, select **TCP**.
   3. In the **Port** field, enter `80`.
5. Click **Create**.
6. Under **New backend** , select the hybrid NEG created previously: **<var scope="HYBRID_NEG_NAME" class="edit" translate="no">HYBRID_NEG_NAME</var>** . Or, you can click **Create a network endpoint group** to create the hybrid NEG now. For guidance on configuring the NEG, see [Set up the hybrid
   NEG](https://docs.cloud.google.com/load-balancing/docs/tcp/set-up-int-tcp-proxy-hybrid#create-hybrid-neg).
7. Retain the remaining default values and click **Done**.
8. In the Google Cloud console, verify that there is a check mark next to **Backend configuration**. If not, double-check that you have completed all of the steps.

#### Frontend configuration

1. Click **Frontend configuration**.
2. Enter a **Name** for the forwarding rule.
3. For **Subnetwork** , select **<var scope="LB_SUBNET" class="edit" translate="no">LB_SUBNET</var>**.
4. For **IP address** , select **<var scope="LB_IP_ADDRESS" class="edit" translate="no">LB_IP_ADDRESS</var>**.
5. For **Port number**, enter any port number from 1-65535. The forwarding rule only forwards packets with a matching destination port.
6. Enable **Proxy Protocol** only if it works with the service running on your on-premise or other cloud endpoints. For example, PROXY protocol doesn't work with the Apache HTTP Server software. For more information, see [Proxy protocol](https://docs.cloud.google.com/load-balancing/docs/tcp/set-up-int-tcp-proxy-hybrid.md.txt#proxy-protocol).
7. Click **Done**.
8. In the Google Cloud console, verify that there is a check mark next to **Frontend configuration**. If not, double-check that you have completed all the previous steps.

#### Review and finalize

1. Click **Review and finalize**.
2. Double-check your settings.
3. Click **Create**.

### gcloud

1. Create a regional health check for the backends.

   ```
   gcloud compute health-checks create tcp TCP_HEALTH_CHECK_NAME \
       --region=REGION \
       --use-serving-port
   ```

   Health check probes for hybrid NEG backends originate from Envoy proxies
   in the proxy-only subnet.
2. Create a backend service.

   ```
   gcloud compute backend-services create BACKEND_SERVICE_NAME \
      --load-balancing-scheme=INTERNAL_MANAGED \
      --protocol=TCP \
      --region=REGION \
      --health-checks=TCP_HEALTH_CHECK_NAME \
      --health-checks-region=REGION
   ```
3. Add the hybrid NEG backend to the backend service.

   ```
   gcloud compute backend-services add-backend BACKEND_SERVICE_NAME \
      --network-endpoint-group=HYBRID_NEG_NAME \
      --network-endpoint-group-zone=HYBRID_NEG_ZONE \
      --region=REGION \
      --balancing-mode=CONNECTION \
      --max-connections=MAX_CONNECTIONS
   ```

   For `MAX_CONNECTIONS`, enter the maximum concurrent
   connections that the backend should handle.
4. Create the target TCP proxy.

   ```
   gcloud compute target-tcp-proxies create TARGET_TCP_PROXY_NAME \
      --backend-service=BACKEND_SERVICE_NAME \
      --region=REGION
   ```
5. Create the forwarding rule.

   Create the forwarding rule using the
   [`gcloud compute forwarding-rules
   create`](https://docs.cloud.google.com/sdk/gcloud/reference/compute/forwarding-rules/create)
   command.

   Replace <var translate="no">FWD_RULE_PORT</var> with a single port number from 1-65535.
   The forwarding rule only forwards packets with a matching destination
   port.

   ```
   gcloud compute forwarding-rules create FORWARDING_RULE \
      --load-balancing-scheme=INTERNAL_MANAGED \
      --network=NETWORK \
      --subnet=LB_SUBNET \
      --address=LB_IP_ADDRESS \
      --ports=FWD_RULE_PORT \
      --region=REGION \
      --target-tcp-proxy=TARGET_TCP_PROXY_NAME \
      --target-tcp-proxy-region=REGION
   ```

## Test the load balancer

To test the load balancer, create a client VM in the same region as the
load balancer. Then send traffic from the client to the load balancer.

### Create a client VM

Create a client VM (`client-vm`) in the same region as the load balancer.

### Console

1. In the Google Cloud console, go to the **VM instances** page.

   [Go to VM instances](https://console.cloud.google.com/compute/instances)
2. Click **Create instance**.

3. Set **Name** to `client-vm`.

4. Set **Zone** to <var scope="CLIENT_VM_ZONE" class="edit" translate="no">CLIENT_VM_ZONE</var>.

5. Click **Advanced options**.

6. Click **Networking** and configure the following fields:

   1. For **Network tags** , enter `allow-ssh`.
   2. For **Network interfaces** , select the following:
      - **Network** : <var scope="NETWORK" class="edit" translate="no">NETWORK</var>
      - **Subnet** : <var scope="LB_SUBNET" class="edit" translate="no">LB_SUBNET</var>
7. Click **Create**.

### gcloud

The client VM must be in the same VPC network and region as
the load balancer. It doesn't need to be in the same subnet or zone. The
client uses the same subnet as the backend VMs.

```
gcloud compute instances create client-vm \
    --zone=CLIENT_VM_ZONE \
    --image-family=debian-12 \
    --image-project=debian-cloud \
    --tags=allow-ssh \
    --subnet=LB_SUBNET
```

### Allow SSH traffic to the test VM

In this example, you create the following firewall rule:

- `fw-allow-ssh`: An ingress rule that allows incoming SSH connectivity on TCP
  port 22 from any address. You can choose a more restrictive source IP range
  for this rule; for example, you can specify just the IP ranges of the systems
  from which you will initiate SSH sessions. This example uses the target tag
  `allow-ssh` to identify the test client VM to which it should apply.

### Console

1. In the Google Cloud console, go to the **Firewall policies** page. [Go to Firewall policies](https://console.cloud.google.com/net-security/firewall-manager/firewall-policies/list)
2. Click **Create firewall rule** to create the rule to allow incoming SSH connections:
   1. **Name** : `fw-allow-ssh`
   2. **Network** : <var scope="NETWORK" class="edit" translate="no">NETWORK</var>
   3. **Priority** : `1000`
   4. **Direction of traffic**: ingress
   5. **Action on match**: allow
   6. **Targets**: Specified target tags
   7. **Target tags** : `allow-ssh`
   8. **Source filter** : **IPv4 ranges**
   9. **Source IPv4 ranges** : `0.0.0.0/0`
   10. **Protocols and ports** : Choose **Specified protocols and ports** , and then enter `tcp:22`.
   11. Click **Create**.

### gcloud

1. Create the `fw-allow-ssh` firewall rule to allow SSH connectivity to
   VMs with the network tag `allow-ssh`.

   ```
   gcloud compute firewall-rules create fw-allow-ssh \
       --network=NETWORK \
       --action=allow \
       --direction=ingress \
       --target-tags=allow-ssh \
       --rules=tcp:22
   ```

### Send traffic to the load balancer

> [!NOTE]
> **Note:** It might take a few minutes for the load balancer configuration to propagate globally after you first deploy it.

Now that you have configured your load balancer, you can test sending
traffic to the load balancer's IP address.

1. Connect via SSH to the client instance.

   ```
   gcloud compute ssh client-vm \
     --zone=CLIENT_VM_ZONE
   ```
2. Verify that the load balancer is serving backend hostnames as expected.

   1. Use the [`compute addresses describe`
      command](https://docs.cloud.google.com/sdk/gcloud/reference/compute/addresses/describe)
      to view the load balancer's IP address:

      ```
      gcloud compute addresses describe LB_IP_ADDRESS \
        --region=REGION
      ```

      Make a note of the IP address.
   2. Send traffic to the load balancer on the IP address and port specified
      when creating the load balancer forwarding rule. Testing whether the
      hybrid NEG backends are responding to requests depends on the service
      running on the non-Google Cloud endpoints.

## Optional: Publish the service by using Private Service Connect

A regional internal proxy Network Load Balancer with hybrid connectivity lets you make a service that is
hosted in on-premises or other cloud environments available to clients in your
VPC network.

If you want to make the hybrid service available in other VPC
networks, you can use Private Service Connect to
[publish the service](https://docs.cloud.google.com/vpc/docs/configure-private-service-connect-producer.md.txt).
By placing a service attachment in front of your regional internal proxy Network Load Balancer, you can let
clients in other VPC networks reach the hybrid services running
in on-premises or other cloud environments.
[![Using Private Service Connect to publish a hybrid service.](https://docs.cloud.google.com/static/vpc/images/private-service-connect-hybrid.svg)](https://docs.cloud.google.com/static/vpc/images/private-service-connect-hybrid.svg) Using Private Service Connect to publish a hybrid service (click to enlarge).

## What's next

- To set up monitoring for your regional internal proxy Network Load Balancer, see [Using
  monitoring](https://docs.cloud.google.com/load-balancing/docs/tcp/tcp-ssl-proxy-logging-monitoring).
- To learn how a regional internal proxy Network Load Balancer works, see the [Regional internal proxy Network Load Balancer
  overview](https://docs.cloud.google.com/load-balancing/docs/tcp/internal-proxy).
- [Clean up the load balancer setup](https://docs.cloud.google.com/load-balancing/docs/cleaning-up-lb-setup.md.txt).