tencent cloud

Cloud Load Balancer

Release Notes and Announcements
CLB Release Notes
Product Announcements
Product Introduction
Overview
Strengths
Use Cases
Principles
Product Comparison
Use Limits
Service Regions and Service Providers
Purchase Guide
Billing Overview
Billing
CLB Resource Package
Purchase Methods
Payment Overdue
Product Attribute Selection
Getting Started
Getting Started with Domain Name-Based CLB
Getting Started with CLB
Getting Started with IPv6 CLB
Deploying Nginx on CentOS
Deploying Java Web on CentOS
Operation Guide
CLB Instance
CLB Listener
Real Server
Health Check
Certificate Management
Log Management
Monitoring and Alarm
Cloud Access Management
Classic CLB
Practical Tutorial
Deploy certificate to CLB (mutual authentication)
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
Solution to Excessive Clients in TIME_WAIT Status
Load Balancer HTTPS Service Performance Test
Stress Testing FAQ
CLB Certificate Operation Permissions
Troubleshooting
UDP Health Check Exception
API Documentation
History
Introduction
API Category
Instance APIs
Listener APIs
Backend Service APIs
Target Group APIs
Redirection APIs
Other APIs
Classic CLB APIs
Load Balancing APIs
Making API Requests
Data Types
Error Codes
CLB API 2017
FAQs
Billing
CLB Configuration
Troubleshooting Health Check Issues
HTTPS
WS/WSS Protocol Support
HTTP/2 Protocol Support
Default Domain Name Blocking Prompt
Service Level Agreement
Contact Us
Glossary

Introduction

PDF
Focus Mode
Font Size
Last updated: 2024-12-19 10:15:38
Welcome to Tencent Cloud Load Balancer. Cloud Load Balancer (CLB) sends the requests from client to multiple associated backend CVMs in the same region with the specified method by setting a virtual IP (VIP).
CLB virtualizes multiple CVMs into an available application service pool. It checks the health of the instances in the pool and automatically isolates the unhealthy ones, thus resolving single points of failure issues and improving the overall service capabilities of the applications. In addition, CLB provides a defense capability of more than 300 Gbit/sec against DDoS attacks.
CLB is a solution that serves multiple machines simultaneously, and it must be used together with CVM. The APIs in this document help you operate on CLB instances. Before using these APIs, please ensure that you are familiar with overview and use of CLB.

Glossary

Term
Full Name
Description
CLB
Cloud Load Balancer
Cloud Load Balancer sends the requests from client to the associated CVMs in the same region with specified method by setting a virtual IP (VIP). It can automatically isolate unhealthy CVMs, thus resolving single points of failure and massive concurrent access requests issues.
Listener
Load Balancer Listener
CLB listener provides users with customized listening port, request forwarding policy, health check configuration, etc.
backend
Real Server
A CLB instance sends requests to real servers which will provide service in a real sense.
VIP
Virtual IP
A CLB instance provides the virtual IP of service.

How to Use

Before using CLB through APIs, please make sure that a port is open on one or more CVMs, e.g. TCP port 80. Next, you need to perform the following steps:
1. Purchase a CLB instance. You can create a CLB instance using the CreateLoadBalancer API, and obtain the unique ID of this instance.
2. Create a CLB listener. After purchasing a CLB instance, you need to use the CreateLoadBalancerListeners API to create a listener that listens on a protocol and port. For example, you can create a TCP listener that listens on TCP port 80 and backend port 80.
3. Bind the real server to the CLB instance. Finally, you need to bind the CVM on which the service is deployed to the CLB instance through the RegisterInstancesWithLoadBalancer API.
After performing these three steps, you can access the service deployed on your CVM by accessing the VIP and port of the CLB instance.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback