tencent cloud

Feedback

Cross-Region Binding 2.0 (New)

Last updated: 2022-09-23 19:02:45

    CLB supports binding CVM instances across regions through CCN, allowing you to select real servers of different regions and bind CLB instances to them across VPCs or regions.
    This feature is currently in beta test. To try it out, please submit an application.

    Note:

    • Cross-region CVM binding is currently not supported for classic CLB instances.
    • This feature is available only to bill-by-IP accounts. To check your account type, please see Checking Account Type.
    • Cross-region binding 2.0 and hybrid cloud deployment do not support Allow Traffic by Default in security groups, for which you need to allow the client IP 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 can well meet 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 them 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 can ensure 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

    Comparison Item Cross-region Binding 2.0 (New) Cross-region Binding 1.0 (Legacy)
    Whether binding to services in multiple regions at the same time is supported Yes:
    • On 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.
    No:
    • On 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.
    Whether intra-region binding can be switched back after cross-region binding is used Yes:
    • On the new version, the original intra-region binding can be switched back after cross-region binding is used.
    No:
    • On the legacy version, after the real server region attribute is modified for cross-region binding, if the new region is different from that of the CLB instance, you cannot change it back to the original intra-region binding.
    Supported CLB types Public network CLB and private network CLB. Public network CLB.
    Whether CLB is automatically unbound when a CVM instance 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 it.
    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 it, and you need to unbind them manually.
    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 it.
    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 it.
    Whether the price is favorable It is billed in CCN. The costs are controlled in a fine-grained manner, which leads to lower prices. Daily 95th percentile

    Limits

    • Cross-network CVM instance binding is currently not supported for classic CLB instances.
    • This feature is available only to bill-by-IP accounts. To check your account type, please see Checking Account Type.
    • This feature is only supported by VPC, not by classic networks.
    • This feature is supported on IPv4 and IPv6 NAT64 CLB instances. The IPv6 CLB instance needs to enable the dual-stack mixing binding, which allows the layer-7 listener to bind both IPv4 and IPv6 CVM instances. On this basis, the CLB instance supports cross-region binding 2.0 and hybrid cloud deployment.
    • Cross-region binding 2.0 and hybrid cloud deployment do not support Allow Traffic by Default in security groups, for which you need to allow the client IP 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 obtained on the backend CVM instance is the client IP. For layer-7 CLB, you can use the X-Forwarded-For or remote_addr field to directly get the client IP. For more information, see Obtaining Real Client IPs Over IPv4 CLBs.

    Prerequisites

    1. You have submitted the application for beta test eligibility. For cross-region binding in the Chinese mainland, submit a ticket for application. For cross-region binding outside the Chinese mainland, contact your Tencent Cloud rep.
    2. You have created a CLB instance. For more information, please see Creating CLB Instances.
    3. You have created a CCN instance. For more information, please see Creating a CCN Instance.
    4. Associate the target VPC with the created CCN instance. For more information, please see Associating Network Instances.

    Directions

    1. Log in to the CLB Console.
    2. On the Instance Management page, click the ID of the target CLB instance.
    3. On the Basic Info tab of the Real Server section, click Configure to bind a private IP of another VPC.
    4. Click Submit in the pop-up dialog box.
    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 in-cloud IPs can be bound to.
    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, please see Managing Real Servers.
    7. In the pop-up box, select Other VPC, click CVM, select one or multiple target CVM instances, enter the forwarding port and weight, and click Confirm. For more information on ports, please see Server Common Port.
    8. Now in the Bound Real Servers section, you can view the bound CVM instances of other regions.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support