- Release Notes and Announcements
- CLB Release Notes
- [April 15, 2024] Domain Name Upgrade for Domain Name-based Public Network CLB
- [July 25, 2023] Adding Rate Limits on Shared CLB Instances
- [July 3, 2023] CLB API Authentication Upgrade
- [June 9, 2023] Adjusting the Grace Period for Pay-as-you-go CLB Instances
- [March 6, 2023] Launching Domain Name-Based Public CLBs
- [Feb. 24, 2023] Changing Health Check Source IP to 100.64.0.0/10 IP Range
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- Directions for Upgrading to Domain Name-Based CLB
- Creating CLB Instances
- Creating an IPv6 CLB Instance
- Creating IPv6 NAT64 CLB Instances
- Configure CLB Forwarding Domain Name
- Configuring CLB Security Group
- Binding Private Network CLB to EIP
- Enabling or Disabling a CLB Instance
- Cloning CLB Instances
- Exporting CLB Instances
- Upgrade to a LCU-supported instances
- Adjusting Specification of LCU-supported CLBs
- Deleting CLB Instances
- Releasing Idle CLB Instances
- Configuring Deletion Protection
- Adjusting Instance Public Network Configurations
- CLB Listener
- CLB Listener Overview
- Configuring TCP Listener
- Configuring a UDP Listener
- Configuring TCP SSL Listener
- Configuring a QUIC Listener
- Configuring an HTTP Listener
- Configuring HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Layer-7 Redirection Configuration
- Layer-7 Custom Configuration
- Layer-7 Domain Name Forwarding and URL Rules
- Using QUIC Protocol on CLB
- SNI Support for Binding Multiple Certificates to a CLB Instance
- Configuring gRPC Support for Layer-7 Protocols
- Real Server
- Health Check
- Certificate Management
- Log Management
- Monitoring and Alarm
- Cloud Access Management
- Classic CLB
- CLB Instance
- Practical Tutorial
- Enabling Gzip Compression & Testing
- HTTPS Forwarding Configurations
- Obtaining Real Client IPs
- Best Practices for Configuring Load Balancing Monitoring Alerts
- Implementing HA Across Multiple AZs
- Load Balancing Algorithm Selection and Weight Configuration Examples
- Configuring WAF protection for CLB listening domain names
- Configure IAP to authenticate web access to the CLB domain and path
- Configure IAP to authenticate programmatic access to CLB's domain and path
- Ops Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Instance APIs
- Listener APIs
- Backend Service APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- DescribeClsLogSet
- CreateLoadBalancerSnatIps
- DeleteLoadBalancerSnatIps
- DescribeLoadBalancerListByCertId
- DescribeQuota
- ModifyLoadBalancersProject
- ReplaceCertForLoadBalancers
- SetLoadBalancerClsLog
- SetLoadBalancerSecurityGroups
- SetLoadBalancerStartStatus
- SetSecurityGroupForLoadbalancers
- CreateClsLogSet
- CreateTopic
- DescribeLoadBalancerTraffic
- DescribeResources
- DescribeTaskStatus
- InquiryPriceCreateLoadBalancer
- InquiryPriceModifyLoadBalancer
- InquiryPriceRenewLoadBalancer
- Classic CLB APIs
- Making API Requests
- Load Balancing APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- CLB Release Notes
- [April 15, 2024] Domain Name Upgrade for Domain Name-based Public Network CLB
- [July 25, 2023] Adding Rate Limits on Shared CLB Instances
- [July 3, 2023] CLB API Authentication Upgrade
- [June 9, 2023] Adjusting the Grace Period for Pay-as-you-go CLB Instances
- [March 6, 2023] Launching Domain Name-Based Public CLBs
- [Feb. 24, 2023] Changing Health Check Source IP to 100.64.0.0/10 IP Range
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- Directions for Upgrading to Domain Name-Based CLB
- Creating CLB Instances
- Creating an IPv6 CLB Instance
- Creating IPv6 NAT64 CLB Instances
- Configure CLB Forwarding Domain Name
- Configuring CLB Security Group
- Binding Private Network CLB to EIP
- Enabling or Disabling a CLB Instance
- Cloning CLB Instances
- Exporting CLB Instances
- Upgrade to a LCU-supported instances
- Adjusting Specification of LCU-supported CLBs
- Deleting CLB Instances
- Releasing Idle CLB Instances
- Configuring Deletion Protection
- Adjusting Instance Public Network Configurations
- CLB Listener
- CLB Listener Overview
- Configuring TCP Listener
- Configuring a UDP Listener
- Configuring TCP SSL Listener
- Configuring a QUIC Listener
- Configuring an HTTP Listener
- Configuring HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Layer-7 Redirection Configuration
- Layer-7 Custom Configuration
- Layer-7 Domain Name Forwarding and URL Rules
- Using QUIC Protocol on CLB
- SNI Support for Binding Multiple Certificates to a CLB Instance
- Configuring gRPC Support for Layer-7 Protocols
- Real Server
- Health Check
- Certificate Management
- Log Management
- Monitoring and Alarm
- Cloud Access Management
- Classic CLB
- CLB Instance
- Practical Tutorial
- Enabling Gzip Compression & Testing
- HTTPS Forwarding Configurations
- Obtaining Real Client IPs
- Best Practices for Configuring Load Balancing Monitoring Alerts
- Implementing HA Across Multiple AZs
- Load Balancing Algorithm Selection and Weight Configuration Examples
- Configuring WAF protection for CLB listening domain names
- Configure IAP to authenticate web access to the CLB domain and path
- Configure IAP to authenticate programmatic access to CLB's domain and path
- Ops Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Instance APIs
- Listener APIs
- Backend Service APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- DescribeClsLogSet
- CreateLoadBalancerSnatIps
- DeleteLoadBalancerSnatIps
- DescribeLoadBalancerListByCertId
- DescribeQuota
- ModifyLoadBalancersProject
- ReplaceCertForLoadBalancers
- SetLoadBalancerClsLog
- SetLoadBalancerSecurityGroups
- SetLoadBalancerStartStatus
- SetSecurityGroupForLoadbalancers
- CreateClsLogSet
- CreateTopic
- DescribeLoadBalancerTraffic
- DescribeResources
- DescribeTaskStatus
- InquiryPriceCreateLoadBalancer
- InquiryPriceModifyLoadBalancer
- InquiryPriceRenewLoadBalancer
- Classic CLB APIs
- Making API Requests
- Load Balancing APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
On CLB purchase page, you can select CLB instances of different attributes. This document describes how to purchase instances based on business scenarios.
Regions
We recommend selecting the region closest to your client to reduce delay and accelerate the download speed.
CLB can only forward traffic to CVM instances in the same region. Please select the region where your CVM instance is located before creating a CLB instance.
CLB can forward traffic to CVM instances in multiple availability zones in the same region. For example, a CLB instance in Beijing can forward traffic to CVM instances in Beijing Zone 1, Beijing Zone 2, and Beijing Zone 3.
A public network CLB (formerly "application CLB") instance supports cross-region binding of CVM. You can select the region of real servers and bind them across VPCs or regions. For example, you can bind a CLB instance in Beijing to a CVM instance in Shanghai to forward the client traffic to the latter. For more information, please see CLB Instance Cross-Region Binding.
Instance Types
CLB instances can be classified into two types: CLB (formerly "application CLB") and classic CLB. CLB covers all features of classic CLB. Based on product features and performance, we recommend CLB. For a detailed comparison, please see Instance Types.
Network Types
Public network CLB
If you need to use CLB to distribute requests from the public network, please select "Public Network".
Public network CLB instances obtain requests from the client via the internet and distribute them to the bound real servers. After you create a public network CLB instance, Tencent Cloud will assign it a VIP address to be resolved by DNS server. Public network CLB allows users to add CNAME and A records, and map them to custom domain names. VIPs of public network CLB instances are fixed public IPs. They can receive HTTP, HTTPS, TCP, UDP, and other requests from the client.
Use Cases
A server cluster is used to provide services to public networks. A unified entry is required, while requests from users of public networks should be assigned to server clusters.
Users of different ISPs are connected to networks closest to them to accelerate network access.
Public VIP types
Regular IP: Regular BGP IP, which is suitable for users want to balance the network quality and cost.
Single-line IP: Accessing the public network via a single ISP, which is low-cost and convenient for self-scheduling.
Billing
For a bill-by-CVM account, only the instance fee is charged for purchasing a public network CLB instance. The service fees incurred by public network bandwidth and traffic are charged on its real server. For more information, please see Bill-by-CVM Account Billing Description.
For a bill-by-IP account, the instance fee and public network fee are charged for purchasing a public network CLB instance. For more information, please see Bill-by-EIP/CLB Account Billing Description.
Private network CLB
If you need to use CLB to distribute requests from private networks, please select "Private Network".
Both the client and server of private network CLB are in Tencent Cloud and can only be accessed within Tencent Cloud. Access via the internet is not allowed (no public network IP address). Tencent Cloud will assign a private IP to CLB from the network you have selected (such as a VPC). The request traffic will be routed to the backend CVM instance via this IP address.
If your application has multiple layers, such as web servers that can communicate over the internet or database servers that can only communicate over the private network, you can create a framework with both public and private network CLB instances. You can then connect all web servers to the public network CLB instance and database servers to the private network CLB instance. The public network CLB instance receives requests from the internet and sends them to the backend web servers. After being processed, requests to database will be sent to the private network CLB instance, which will then route the requests to database servers.
Use Cases
Tencent Cloud has more than one internal servers. Requests from the client need to be allocated to servers properly.
Fault tolerance and restoration are needed for the internal server cluster.
The service provider wants to block their own physical IP addresses and provide imperceptible services to the client.
Billing
The usage of private network CLB instances incur charges. But you don't need to pay the related public network fee.
IP Versions
The IP version of a CLB instance. Available versions: IPv4, IPv6, and IPv6 NAT64.
Enabling Anycast
If you enable Anycast during the CLB instance creation, an Anycast CLB instance will be created. Anycast CLB is a load balancing service that supports dynamic acceleration across regions. CLB VIP is published in multiple regions. The client connects to the nearest POP, and the traffic will be forwarded to a CVM instance through the high-speed internet of Tencent Cloud IDC. For more information, please see Creating an Anycast Instance.
Instance Name
CLB instance name, which can contain 1 to 60 characters.
Purchase Quantity
Number of purchased CLB instances.
Yes
No
Was this page helpful?