What's New
The tables below describe the features released in each ELB version and corresponding documentation updates. New features will be successively launched in each region.
September 2022
No. |
Feature |
Description |
Phase |
Document |
---|---|---|---|---|
1 |
Dedicated load balancers |
This type of load balancer allows you to have exclusive use of resources, so that the performance of a load balancer is not affected by other load balancers. In addition, there are a wide range of specifications available for selection. Dedicated load balancers support cross-AZ deployment for higher reliability. |
Commercial use |
|
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 |
|
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 |
|
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 |
|
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 |
|
7 |
Security policy |
Supported TLS protocol versions:
|
Commercial use |
|
8 |
Access control |
You can add IP addresses to a whitelist or blacklist to control access to a listener. |
Commercial use |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.