---
title: "Deploying Web Access with GCP HTTPS Load Balancer"
slug: "deploying-web-access-with-gcp-https-load-balancer"
updated: 2025-12-12T20:42:47Z
published: 2025-12-12T20:42:47Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nasuni.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploying Web Access with GCP HTTPS Load Balancer

This guide is intended for IT infrastructure architects and DevOps professionals responsible for deploying or enabling Web Access on Google Cloud Platform (GCP).

This guide applies to Nasuni Edge Appliance 10.1 and later.

## Introduction

The Google HTTPS load balancer secures access to a Web Access instance. Benefits include certificate generation and renewal via the GCP platform.

> ***NOTE****: Google offers three types of load balancers: Classic, Regional, and Global. This document is for Global load balancers. Regional load balancers are not recommended.*

## Prerequisites

- Nasuni Support must set the Restrict Session IP account setting to False.
- Deploy an Edge Appliance to GCP and join the Edge Appliance to the NMC.
- A public FQDN for your instance and a corresponding SSL or TLS server certificate.
- Access to DNS to set up the FQDN.

### Creating an SSL Policy

Create an SSL policy. For details, see [SSL policies for HTTPS and SSL proxy load balancers](https://cloud.google.com/blog/products/gcp/announcing-ssl-policies-for-https-and-ssl-proxy-load-balancers).

To create an SSL policy, follow these steps:

1. On the Google Cloud Platform, navigate to **☰ Navigation menu → View all products → Networking → Network Services → SSL Policies.** ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-AKSJRPNS.png)
2. Click **Create policy**. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-O6TZYN1Z.png)
3. Enter a **Name** for the SSL policy.
4. From the “**Minimum TLS version**” drop-down list, select the minimum TLS version that the load balancer will negotiate TLS with. It is recommended that you use only the latest TLS versions.
5. From the **Profile** drop-down list, select the set of cipher suites that the load balancer can use. It is recommended that you use only the latest ciphers.
6. Click **Create**. The SSL policy is created and appears in the list of SSL policies.

### Creating an Instance Group

Create an instance group.

To create an instance group, follow these steps:

1. On the Google Cloud Platform, navigate to **☰ Navigation menu → Compute Engine → Instance groups.**
2. Click **Create Instance Group.** ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-u2bb4lso.png)
3. From the left menu panel, select **New unmanaged instance group.**
4. Enter a**Name** for****the instance group.
5. Select the same **Region, Zone, Network** and **Subnetwork** as the current Web Access instance.
6. From the **VM instances** dropdown, select the Web Access instance. Do not select more than one Web Access instance.
7. Click **Create.**

### Creating a Health Check

Create a health check to be used later:

1. On the Google Cloud Platform, navigate to **☰ Navigation menu → Compute Engine → Health Checks.**
2. Click “**Create** **a Health Check**”. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-39pfakfv.png)
3. Enter a**Name** for the health check.
4. For**Scope**, select **Global**.
5. For **Protocol**, select **HTTPS**.
6. For **Port**, select **443**.
7. For the**Source regions**, select the same region that the instances run in, plus two more.
8. For**Request path**, enter /fs/auth/login
9. For**Logs**, enter your organization’s preference.
10. For **Health criteria**, keep the defaults.

### Creating a HTTPS Load Balancer

Create an HTTPS load balancer.

To create an HTTPS load balancer, follow these steps:

1. On the Google Cloud Platform, navigate to **☰ Navigation menu → Network services → Load balancing**.
2. Click **Create Load Balancer**.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-89ykbo5g.png)

1. Under “**Type of load balancer**”, choose “**Application Load Balancer (HTTP/HTTPS)”**. Then click **Next**.

![A diagram of a network load balancer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-pz2kb1ux.png)

1. Under “**Public facing or internal**”, choose **Public facing (external)**. Then click **Next**.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-2k5v4j7t.png)

1. Under “**Global or single region deployment**”, choose **Best for global workloads.** Then click **Next**.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-sj5sdeqg.png)

1. Under “**Load balancer generation**”, choose **Global external Application Load Balancer**. Then click **Next**.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-20kbuo87.png)

1. Click **Configure** to move to the next phase .

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-g9yz016u.png)

### Configuring the Load Balancer

To configure the load balancer, follow these steps:

1. On the **Frontend configuration** page, enter the **Load Balancer name**.

![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-r0jnyoa0.png)

1. In the “**New Frontend IP and Port**” area, provide the following information: ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-4nxo4dbf.png)

1. Assign a **Name.**
2. For the protocol, choose “**HTTPS (includes HTTP/2 and HTTP/3)**”.
3. For the **IP version**, choose **IPv4**.
4. For the**IP address**, choose “**Create IP address**”. Then enter a name to reserve a static IP address. Do not select**Ephemeral**.
5. For the **Port**, choose **443**.
6. For the**Certificate**, either upload a certificate or select “**Create a new certificate**” and create a new certificate.
7. From the **SSL Policy** drop-down list, select the SSL policy you created in [Creating an SSL Policy](/v1/docs/deploying-web-access-with-gcp-https-load-balancer#creating-an-ssl-policy).
8. Select “**Enable HTTP to HTTPS redirect**”.
9. Click **Done**.

1. On the **Backend configuration** page, click in the “**Backend services & backend buckets**” area, and click “**Create a backend service**”. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-77ggxjwz.png)

Then provide the following information: ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/deploying-web-access-with-gcp-https-load-balancer-image-c3m7ufso.png)

1. Create a**Name** for the backend.
2. From the**Backend type** drop-down list, select **Instance Group**.
3. From the**Protocol** drop-down list, select **HTTPS**.
4. For the**Named port**, enter **https**.
5. For**Timeout**, enter **30** seconds.
6. From the “**IP address selection policy**” drop-down list, select **Only IPv4**.
7. From the**Health check** drop-down list,****select the previously created health check.
8. Under the **New Backend** section, provide this information:
9. For the**IP stack type**, select “**IPv4 (single stack)**”.
10. From the**Instance group** drop-down list, select the previously defined instance group.
11. For**Port numbers**, enter **443**.
12. For the**Balancing mode**, leave as the default. This is unused because it is a single instance only.
13. In the **Cloud CDN** area, it is recommended to unselect “**Enable Cloud CDN**”.
14. For **Cloud Armor**, it is recommended to retain the default security policy.
15. Click **Create**. The Backend is created.

1. To configure routing rules, click **Routing Rules**.

1. Select “**Simple host and path rule**”.
2. From the list of “**Host and path rules**”, select the backend defined above.
3. Click “**Review and Finalize**”. Review the **Frontend**, **Backend**, and **Routing Rules**.
4. Click **Create**.

The configured load balancer is created. This can take a few minutes.

## Testing the Load Balancer

After the Load Balancer is created, test that it is operating as expected:

1. Navigate to the static IP address of the Load Balancer.
2. The Web Access login page should load after you accept that the certificate does not match in the browser security.
3. Select the Load Balancer.
4. Copy the public IP address
5. Use the Load Balancer IP address to create an A record in the DNS host, mapping the proper FQDN.
6. After this is complete, the Web Access site should load without browser certificate warnings.