- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- CLB Listener Overview
- Configuring a TCP Listener
- Configuring a UDP Listener
- Configuring a TCP SSL Listener
- Configuring an HTTP Listener
- Configuring an HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Configuring Layer-7 Redirection
- 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
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practices
- OPS Guidelines
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Listener APIs
- Real Server APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Queries CLB instances with high traffic under the current account
- DescribeTaskStatus
- Gets the CLB exclusive logset
- CreateClsLogSet
- CreateTopic
- CreateLoadBalancerSnatIps
- DeleteLoadBalancerSnatIps
- SetLoadBalancerSecurityGroups
- SetSecurityGroupForLoadbalancers
- ReplaceCertForLoadBalancers
- DescribeLoadBalancerListByCertId
- SetLoadBalancerClsLog
- DescribeQuota
- Cloud Load Balancer APIs
- Classic CLB APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- CLB Listener Overview
- Configuring a TCP Listener
- Configuring a UDP Listener
- Configuring a TCP SSL Listener
- Configuring an HTTP Listener
- Configuring an HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Configuring Layer-7 Redirection
- 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
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practices
- OPS Guidelines
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Listener APIs
- Real Server APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Queries CLB instances with high traffic under the current account
- DescribeTaskStatus
- Gets the CLB exclusive logset
- CreateClsLogSet
- CreateTopic
- CreateLoadBalancerSnatIps
- DeleteLoadBalancerSnatIps
- SetLoadBalancerSecurityGroups
- SetSecurityGroupForLoadbalancers
- ReplaceCertForLoadBalancers
- DescribeLoadBalancerListByCertId
- SetLoadBalancerClsLog
- DescribeQuota
- Cloud Load Balancer APIs
- Classic CLB APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
The use of Tencent Cloud CLB has certain restrictions, and different types of CLB instances have their own use limits. For more information on CLB instance types, please see Instance Types.
| Instance Type | Resource | Default Restriction |
|---|---|---|
| General restrictions for all instances | Number of public network instances can be created under one account in a single region | 100 |
| Number of private network instances can be created under one account in a single region | 100 | |
| Number of listeners can be added to an instance | 50 | |
| Ports that can be selected by a listener in an instance | An integer between 1 - 65535 | |
| CLB (formerly "application CLB") |
Number of domain name and URL forwarding rules can be configured for an HTTP/HTTPS listener in a CLB instance | 50 |
| Number of servers can be bound to a forwarding rule in a CLB instance | 100 | |
| Number of backend ports that can correspond to a frontend port of a CLB instance | Multiple ports | |
| Classic CLB | Number of servers can be bound to a listener in a classic CLB instance | 100 |
| Number of backend ports that can correspond to a frontend port of a classic CLB instance | 1 port |
A CLB instance will not unbind itself from the CVM instance. After a CVM instance becomes isolated (pay-as-you-go CVM instance has been in arrears for more than 2 hours), it will not unbind itself from the CLB instance either.
Yes
No
Was this page helpful?