Cloud Load Balancer (CLB) supports binding real servers across regions through Cloud Connect Network (CCN). This allows you to select real servers in different regions and bind real servers across VPCs or regions.
This feature is currently in a beta test. To try it out, submit an application.
Note:
Cross-region binding 2.0 is unavailable for classic CLBs.
This feature is available only to bill-by-IP accounts. To check your account type, see Checking Account Type.
Cross-region binding 2.0 and hybrid cloud deployment do not support Allow by Default in security groups. You need to allow the client IP address and service port on the real server.
CLB instances cannot be bound with each other in cross-region binding 2.0 and hybrid cloud deployment scenarios.
Use Cases
1. The cross-region binding feature meets the needs in P2P gaming scenarios where the same server is shared by players from different regions. For example, if your real server cluster is deployed in Guangzhou, you can create CLB instances in Shanghai and Beijing and bind the instances to the same real server cluster in Guangzhou to achieve game acceleration and traffic convergence, ensuring the data transfer quality and reducing the latency.
2. This feature ensures the transfer quality and data consistency in key business transactions, meeting the stringent requirements of the financial industry and payment scenarios.
Differences from Legacy Cross-region Binding
Item
Cross-Region Binding 2.0 (New)
Cross-Region CVM Binding (Legacy)
Binding to services in multiple regions
Supported.
In the new version, a CLB instance can be bound to CVM instances in multiple regions at the same time.
For example, a CLB instance in the Beijing region can be bound to CVM instances in the Beijing and Shanghai regions at the same time.
Unsupported.
In the legacy version, a CLB instance can be bound to CVM instances in only one region.
For example, a CLB instance in the Beijing region can be bound to CVM instances in the Shanghai region, but cannot be bound to those in the Beijing and Shanghai regions at the same time.
Switching between cross-region binding and intra-region binding
Supported. In the new version, the original intra-region binding can be switched back after cross-region binding is used.
Unsupported. In the legacy version, after the region attribute of the real server is changed, if the new region is different from that of the CLB instance, you cannot switch back to the original intra-region binding.
Supported CLB types
Public network CLB instances and private network CLB instances
Public network CLB instances
Unbinding CLB automatically when the bound CVM is released
Intra-region binding:
If a CLB instance is bound to a CVM instance in the same region, when the CVM instance is released, the CLB instance will be automatically unbound from the CVM instance.
Cross-region binding:
If a CLB instance is bound to a CVM instance in another region, when the CVM instance is released, the CLB instance will not be automatically unbound from the CVM instance, and you need to manually unbind them.
Intra-region binding:
If a CLB instance is bound to a CVM instance in the same region, when the CVM instance is released, the CLB instance will be automatically unbound from the CVM instance.
Cross-region binding:
If a CLB instance is bound to a CVM instance in another region, when the CVM instance is released, the CLB instance will be automatically unbound from the CVM instance.
Price
Billed in CCN. The costs are controlled in a fine-grained manner, which leads to lower prices.
Billed by daily 95th percentile
Limits
Cross-network real server binding is currently unavailable for classic CLB instances.
This feature is available only to bill-by-IP accounts. To check your account type, see Checking Account Type.
This feature is only supported by VPC but not by classic networks.
This feature is supported on IPv4 and IPv6 NAT64 CLB instances. Dual-stack binding needs to be enabled for IPv6 CLB instances, so that the layer-7 listener can be bound to both IPv4 and IPv6 real servers. Cross-region binding 2.0 and hybrid cloud deployment are supported when the layer-7 listener is bound to an IPv4 IP address, but are not supported when the IPv6 CLB instance is bound to an IPv6 real server.
Cross-region binding 2.0 and hybrid cloud deployment do not support Allow by Default in security groups. You need to allow the client IP address and service port on the real server.
CLB instances cannot be bound with each other in cross-region binding 2.0 and hybrid cloud deployment scenarios.
Both layer-4 and layer-7 (HTTP/HTTPS) CLB services support getting a client IP. For layer-4 CLB, the source IP address obtained on the backend CVM instance is the client IP address. For layer-7 CLB, you can use the X-Forwarded-For or remote_addr field to directly get the client IP address. For more information, see Obtaining Real Client IPs Over IPv4 CLBs.
Prerequisites
1. You have submitted the application for beta test eligibility. For intra-country cross-region binding, submit a ticket for application. For cross-border binding, contact your Tencent Cloud rep.
2. On the Instance Management page, select a region from the top-left corner, and click the instance ID.
3. In the Real Server section on the Basic Info tab, click Configure to bind a private IP address of another VPC.
4. Click Submit in the pop-up window.
5. In the Real Server section on the Basic Info tab, you can see that Binding IP of Other VPCs is enabled, which indicates that you can bind in-cloud IP addresses.
6. On the instance details page, open the Listener Management tab, and bind a real server to the CLB instance in the listener configuration section. For more information, see Managing Real Servers.
7. In the pop-up window, select Other VPC for Network type, click CVM, select one or multiple CVM instances to be associated with, enter the forwarding port and weight, and click Confirm. For more information about ports, see Server Common Port.
8. Now in the Real Servers Bound section, you can view the bound CVM instances of other regions.
Yes
No
Was this page helpful?