> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/how-to/configure-load-balancing-when-using-cloud-guard-waf-as-a-reverse-proxy.md).

# Configure Load Balancing when Using Cloud Guard WAF as a Reverse Proxy

CloudGuard WAF can now act as a **reverse proxy with load balancing**, allowing you to distribute incoming traffic across multiple upstream servers. This improves availability, scalability, and fault tolerance of your applications.

### Prerequisites

* You already have a CloudGuard WAF asset configured in **reverse proxy mode**.
* Your backend applications are reachable from the WAF.

### **Instructions:**

#### Step 1 – Open Your Asset

1. Go to the **Assets** page in the CloudGuard WAF portal.
2. Select the asset you want to configure.
3. Enable load balancing

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2F0Ji4V45QxbuNu56sXnXU%2Fimage.png?alt=media&amp;token=a53896f5-f27a-4fb9-b5ec-5b2c3327068b" alt=""><figcaption></figcaption></figure>

#### Step 2 – Configure Upstreams

1. Click on the "Load balancer upstream setting.
2. Choose the Load Balancing Algorithm
   * Currently only "Round Robin" is supported
3. Provide the URL for each backend server
   * Make sure to include protocol and port if needed

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FlnrAgbqcuOSiUvMLFpXK%2Fimage.png?alt=media&amp;token=cc4accb2-56ae-4a12-8a20-c3619a3decbd" alt=""><figcaption></figcaption></figure>

#### Step 3  - Configure **Health Check** settings

provide the following details:

* Path (Defaults to /)
* Port (Defaults to 80)
* Timeout setting (Defaults to 5s)
* Interval setting (Defaults to 5s)
* Healthy threshold (Defaults to 5)
* Unhealthy threshold (Defaults to 5)
* Expected status code  (Defaults to 200)

<figure><img src="https://2760087783-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWA4nfgNrSRL8dA6Kap7%2Fuploads%2FNd0c0D36YlaL1jtF6wUX%2Fimage.png?alt=media&amp;token=9a808f32-52bf-401a-88f1-a716a8abcd89" alt="" width="193"><figcaption></figcaption></figure>

#### Step 4 - Save and Enforce


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://waf-doc.inext.checkpoint.com/how-to/configure-load-balancing-when-using-cloud-guard-waf-as-a-reverse-proxy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.