Connecting ELB to a Cloud Mode WAF Instance on the ELB Console

Overview

In cloud load balancer access mode, WAF is integrated into the load balancer gateway through an SDK modular. After your website is connected to WAF, the load balancer mirrors the website traffic to WAF. WAF checks the mirrored traffic and sends the check result to the load balancer. The load balancer then determines whether to forward client requests to the origin server based on these check results. In this process, WAF does not forward traffic. This eliminates compatibility and stability issues that might be caused by additional-layer of traffic forwarding.

Figure 1 shows how a website is accessed after being connected to WAF. For details, see Connecting Your Website to WAF (Cloud Mode - Load Balancer Access).

Figure 1 Website access diagram

Prerequisites

• You have purchased a cloud WAF instance and learned about the details about how to connect a website to WAF.
  NOTE:

  To use cloud load balancer WAF, you need to submit a service ticket to enable it.

• You have purchased a dedicated load balancer with Specifications set to Application load balancing (HTTP/HTTPS) and have added an HTTP or HTTPS listener by referring to Adding an HTTP Listener or Adding an HTTPS Listener. You have added the web servers to be protected to the backend server group associated with the load balancer's listener and verified that the load balancer can forward traffic properly.

Procedure

1. Go to the load balancer list page.
2. On the load balancer list page, click the name of the load balancer you want to connect to the cloud WAF instance.
3. Switch to the Associated Services tab and click Add WAF Policy.
   Table 1 describes the parameters.

   Table 1 Parameters for adding a WAF policy

   Parameter	Setting	Example Value
   Domain Name	Set this parameter to the domain name or IP address (public or private IP address) you want to protect. Make sure that the domain name has been resolved to the EIP of the load balancer. Domain name: Single domain names or wildcard domain names are supported. Single domain name: Enter a single domain name, for example, www.example.com. Wildcard domain name If the server IP addresses of each subdomain name are the same, enter a wildcard domain name to be protected. For example, if the subdomain names a.example.com, b.example.com, and c.example.com have the same server IP address, you can directly add the wildcard domain name *.example.com. If the server IP addresses of subdomain names are different, add each subdomain name as a single domain name one by one. Wildcard domain name * can be added. NOTE: WAF can protect both public and private IP addresses. If a private IP address is used, ensure that the corresponding network path is accessible so that WAF can correctly monitor and filter traffic.	Single domain name: www.example.com Wildcard domain name: *.example.com IP address: XXX.XXX.1.1
   Listeners	Select a listener to be protected. All listeners Specific listener	All listeners
   WAF Policy	The system-generated policy is selected by default. You can select a policy you configured before, or customize rules after the domain name is connected to WAF. System-generated policies Basic web protection (Log only mode and common checks) The basic web protection defends against attacks such as SQL injections, XSS, remote overflow vulnerabilities, file inclusions, Bash vulnerabilities, remote command execution, directory traversal, sensitive file access, and command/code injections. Anti-crawler (Log only mode and Scanner feature) WAF only logs web scanning tasks, such as vulnerability scanning, virus scanning, and crawling behavior of OpenVAS and Nmap. NOTE: Log only: WAF only logs detected attacks instead of blocking them. Only the professional and platinum editions allow you to specify a custom policy for Policy.	System-generated policy

   1. Click OK.

      You can view the added websites in the protected website list on the WAF console.

Reference

• Buying a Cloud WAF Instance
• Connecting Your Website to WAF (Cloud Mode - Load Balancer Access)
• Adding an HTTP Listener
• Adding an HTTPS Listener
• Adding a QUIC Listener