Load Balancer
Load Balancer
Load Balancer
Document
Announcement
Network Load Balancer (NLB)
What's New
Product Description
Quick Start
User Guide
NLB instances
Server Group
Listeners
Projects and Tags
Best Practices
Cross-VPC Backend Server
API
NLB Instance
Listener
Server group
TLS Security Policy
SDK Reference
Application Load Balancer (ALB)
Updates and Announcements
Overview
Getting Started
User Guide
Instance
Listeners
Creating a listener
Forwarding rules
Server groups
Manage certificates
Security management
Logs and monitoring
Application of ALB in VKE
Resource management
Project-based management
Tag-based management
API Reference
ALB Instance
Availability Zone
Listener
server group
Health Check Template
forwarding rules
certificate
access log interface
Health Check Log
access control
personalized configuration
Best Practices
FAQs
Classic Load Balancer (CLB)
Overview
Product billing
Quick Start
User Guide
CLB instances
Backend Server Group
Listener
Creating a listener
Configuring a forwarding rule
Certificate management
Logs and monitoring
Identity and Access Management
Projects and Tags
Best Practices
Creating a static page
Configuration practice of a forwarding rule
Disaster Recovery Best Practices
Obtaining the client source IP address
API reference
CLB instances
Listener
Backend server group
ACL
Forwarding rule
Certificate
Access log (Layer-7)
Health check log
SDK Reference
- Documentation
Load BalancerClassic Load Balancer (CLB)Quick StartLayer-4 CLBQuick start
Copy page
Download PDFLayer-4 CLB
Quick start
Copy pageDownload PDFQuick start
Scenario examples
This topic describes how to quickly configure a Layer-4 Classic Load Balancer (CLB) instance with access request distribution capabilities. After configuration, the CLB instance listens to requests on TCP port 80, and the Elastic Compute Service instances in the backend server group provide services through TCP port 80.
Layer-4 CLB is applicable for scenarios with a large amount of application access requests. Access requests can be distributed to multiple backend servers for processing through CLB. After the health check feature is enabled, CLB can automatically identify abnormal backend servers and distribute access requests to normal backend servers, avoiding single points of failure (SPOFs) and improving application availability.
Preparations
Before configuring the CLB instance, you need to prepare the following:
- Prepare a VPC environment: The CLB instance should be in the same VPC as the backend servers providing services. When creating a VPC, it is recommended to select a region geographically closest to the source clients to reduce latency and improve download speed. You can see Building an IPv4 VPC to create a new VPC.
- Build your backend server environment within the VPC: create two Elastic Compute Service instances and deploy the services for external access. For detailed steps, see Purchasing Elastic Compute Service and Deploying Backend Services.
- Complete the CLB instance Type and specification planning: It is recommended to see Product Type and specification selection based on the actual business scenario and business volume.Product
- Ensure that the security group attached to the ECS instance has opened the service ports (TCP port 80) and allowed the CLB health check CIDR block: see Configuring backend server security group.
Configuration procedures
The configuration process for Layer-4 CLB services is as follows.
- Create CLB instance: Create a CLB instance based on the actual business scenario and business volume.
- Configure the backend server group: create the backend server group and add backend servers that provide the actual services.
- Create listener: add a listener to the CLB instance and associate it with the backend server group.
- Verification: Verify that the configured CLB can correctly forward access requests to the backend server.
Last updated: 2026.06.17 14:16:05
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
