What's New

1

Exporting the details of a load balancer

You can export the basic load balancer and listener information by default. You can also export forwarding policies, backend server group details, backend server details, and certificate names or IDs.

Exporting Dedicated Load Balancers

1

Forward to Same Port

You can enable Forward to Same Port for Layer 4 backend server groups that are associated with dedicated load balancers.

Creating a Backend Server Group

2

Forwarding by Port Ranges

You can enable Forwarding by Port Ranges for Layer 4 listeners of a dedicated load balancer.

Adding a TCP Listener

1

This feature is only available for backend server groups that are associated with dedicated load balancers.

Creating a Backend Server Group

2

In the same VPC and enterprise project, the backend server group of a dedicated load balancer can be associated with multiple load balancers or different listeners of a load balancer.

Creating a Backend Server Group

3

SCM certificates

You can add certificates provided by CCM.

Commercial use

Adding a Certificate

1

Replacing the Certificate Bound to Different Listeners

2

You can flexibly change the specifications of a dedicated load balancer as required.

Modifying the Basic Configurations of a Dedicated Load Balancer

1

Dedicated load balancers

You get exclusive access to load balancer resources. The performance of a dedicated load balancer is never affected by the loads on other load balancers. In addition, there are a wide range of specifications available for you to choose from.

Dedicated load balancers support cross-AZ deployment for higher reliability.

Commercial use

Creating a Dedicated Load Balancer

2

Hybrid load balancing

For dedicated load balancers, you can associate servers in a peer VPC, in a VPC connected through a cloud connection, or in an on-premises data center at the other end of a Direct Connect or VPN connection, by using the server IP addresses. In this way, incoming traffic can be flexibly distributed to cloud servers and on-premises servers for hybrid load balancing.

Commercial use

Adding Backend Servers in a Different VPC from a Load Balancer

3

QUIC

If you add a UDP listener to a dedicated load balancer, you can select QUIC for the associated backend server group and use the connection ID algorithm to route requests with the same connection ID to the same backend server.

Commercial use

Adding a UDP Listener (with a QUIC Backend Server Group Associated)

4

HTTPS support

You can select HTTPS for both your listener and the associated backend server group to verify the validity of requests on your load balancer and backend servers and improve service security. This allows you to enable mutual authentication on the load balancer and backend servers.

Commercial use

Adding an HTTPS Listener

5

Advanced forwarding

After you enable advanced forwarding, you can sort the forwarding policies and set forwarding rules including wildcard domain name, HTTP request method, URL, HTTP header, query string, and CIDR block. You can also choose to redirect the requests to another URL and make backend servers return a fixed message body.

Commercial use

Advanced Forwarding Policy

6

Slow start

You can enable slow start for HTTP and HTTPS listeners. After it is enabled, the load balancer linearly increases the proportion of requests to backend servers in this mode. When the slow start duration elapses, the load balancer sends full share of requests to backend servers and exits the slow start mode. Slow start ensures that applications start smoothly and can respond to requests with optimal performance.

Commercial use

Configuring Slow Start

7

Security policy

Supported TLS protocol versions:

• TLS-1-0-WITH-1-3: TLS 1.3, TLS 1.2, TLS 1.1, and TLS 1.0
• TLS-1-2-FS-WITH-1-3: TLS 1.3 and TLS 1.2
• TLS-1-2-FS: TLS 1.3 and TLS 1.2

Commercial use

TLS Security Policy

8

Access control

You can add IP addresses to a whitelist or blacklist to control access to a listener.

Commercial use

What Is Access Control?