What's New

1

SCM certificates

You can add certificates provided by SCM.

Commercial use

Creating a Certificate

1

Changing specifications

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

Commercial use

Changing the Specifications of a Dedicated Load Balancer

2

Replacing the certificate bound to different listeners

You can replace the certificates bound to different listeners.

Commercial use

Replacing the Certificate Bound to Different Listeners

1

Using advanced forwarding for application iteration

As the business grows, you may need to upgrade your application based on the users' feedback. Both the old and new versions are used. After the new version is ready, all the users are directed to the new version. In this process, you can use advanced forwarding to route requests to different versions.

Commercial use

Using Advanced Forwarding for Application Iteration

1

Routing traffic across cloud servers and on-premises servers

You can enable IP as a Backend when creating a dedicated load balancer and associate on-premises servers with this load balancer by using their IP addresses.

Commercial use

Routing Traffic Across Cloud Servers and On-Premises Servers

2

Transfer client IP address

Generally, shared load balancers use IP addresses in 100.125.0.0/16 to communicate with backend servers. If you want a load balancer to communicate with backend servers using the real IP addresses of the clients, you can enable Transfer Client IP Address.

Commercial use

Transfer Client IP Address

1

Querying ECS IDs using APIs

The device_id field is added to the Elastic Load Balance API Reference to allow you to query ECS IDs using APIs.

Commercial use

Querying Backend Servers

2

Dedicated load balancer APIs

ELB now provides APIs for creating and managing dedicated load balancers and associated resources.

Commercial use

Dedicated Load Balancer APIs

3

IP address group APIs

ELB provides IP address group APIs to allow you to configure a blacklist or whitelist by calling the APIs when you create an IP address group.

Commercial use

Creating an IP Address Group

1

Outline of the Elastic Load Balance API Reference.

• Shared Load Balancer APIs (Enterprise Project) is changed to Shared Load Balancer APIs.
• Shared Load Balancer APIs is changed to Shared Load Balancer APIs (OpenStack) and moved to Historical APIs.

Commercial use

Shared Load Balancer APIs

Shared Load Balancer APIs (OpenStack)

1

Security policy

ELB supports three more security policies, including TLS-1-0-WITH-1-3, TLS-1-2-FS-WITH-1-3, and TLS-1-2-FS.

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

Security Policy

1

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.

Open beta testing

Configuring Hybrid Load Balancing (for Dedicated Load Balancers)

2

Dedicated load balancer

ELB has launched dedicated load balancers that feature exclusive resources and guaranteed performance. Enhanced load balancers are renamed shared load balancers. ELB now provides the following types of load balancers.

Open beta testing

Differences Between Shared and Dedicated Load Balancers

3

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.

Open beta testing

Configuring Slow Start (for Dedicated Load Balancers)

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.

Open beta testing

Adding an HTTPS Listener

5

IPv4/IPv6 dual stack

Dedicated load balancers can work in both private and public networks and support IPv4/IPv6 dual stack.

Open beta testing

Creating a Dedicated Load Balancer

6

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.

Open beta testing

Adding a UDP Listener with a QUIC Backend Server Group Associated (for Dedicated Load Balancers)