Step 2: Configure a Load Balancer for WAF

Prerequisites

• You have added a website to a dedicated WAF instance.
• You have created a load balancer.
• Related ports have been enabled in the security group to which the dedicated WAF instance belongs.
  You can configure your security group as follows:

  • Inbound rules

    Add an inbound rule to allow incoming network traffic to pass through over a specified port based on your service requirements. For example, if you want to allow access from port 80, add a rule that allows TCP and port 80.

  • Outbound rules

    Retain the default settings. All outgoing network traffic is allowed by default.

Constraints

• If Health Check is configured, the health check result of the dedicated instance must be Healthy, or the website requests cannot be pointed to WAF.
• The Backend Port for the backend server must be the same as the service port protected by the dedicated WAF instance. The service port is the protected port set in Step 1: Add a Website to WAF.
• WAF works as a layer-7 proxy. When configuring a listener, you can only select HTTP or HTTPS as the frontend protocol.

Impact on the System

If you select Weighted round robin for Load Balancing Algorithm, disable Sticky Session. If you enable Sticky Session, the same requests will be forwarded to the same dedicated WAF instance. If this instance becomes faulty, an error will occur when the requests come to it next time.

Adding a Listener

If Health Check is configured, the health check result of the dedicated instance must be Healthy, or the website requests cannot be pointed to WAF.

1. Log in to the management console.
2. Click in the upper left corner of the management console and select a region or project.
3. Click in the upper left corner of the page and choose Elastic Load Balance under Network to go to the Load Balancers page.
4. Click the name of the load balancer you want in the Name column to go to the Listeners page.
5. Then, click Add Listener and configure the listener information.
   • Frontend Port: the port that will be used by the load balancer to receive requests from clients. You can set this parameter to any port. The origin server port configured in WAF is recommended.
   • Frontend Protocol: Select HTTP or HTTPS.
   Figure 1 Configuring a listener
   

6. Click Next: Configure Request Routing Policy.
   Figure 2 Configuring a backend server group
   
   

   If you select Weighted round robin for Load Balancing Algorithm, disable Sticky Session. If you enable Sticky Session, the same requests will be forwarded to the same dedicated WAF instance. If this instance becomes faulty, an error will occur when the requests come to it next time.

7. Click Next: Add Backend Server and configure a health check.
   

   • If Health Check is configured, the health check result must be Healthy, or the website requests cannot be pointed to WAF.

8. Click Next: Confirm.
9. Click Submit.

Adding WAF Instances to an ELB Load Balancer

1. Log in to the management console.
2. Click in the upper left corner of the management console and select a region or project.
3. Click in the upper left corner and choose Web Application Firewall (Dedicated) under Security.
4. In the navigation pane on the left, choose Instance Management > Dedicated Engine to go to the dedicated WAF instance page.
   Figure 3 Dedicated engine list
   

5. In the row containing the instance you want to upgrade, click More > Add to ELB in the Operation column.
6. In the Add to ELB dialog box, specify ELB (Load Balancer), ELB Listener, and Backend Server Group based on Adding a Listener.
   Figure 4 Add to ELB
   
   

   The Health Check result must be Healthy, or the website requests cannot be pointed to WAF.

7. Click Confirm. Then, configure service port for the WAF instance, and Backend Port must be set to the port configured in Step 1: Add a Website to WAF.
   Figure 5 Configuring Backend Port
   

Verification

If the Health Check Result is Healthy, the load balancer is configured.