- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- CLB Listener Overview
- Configuring TCP Listener
- Configuring UDP Listener
- Configuring TCP SSL Listener
- Configuring QUIC Listener
- Configuring 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
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practices
- Enabling Gzip Configuration & Testing
- HTTPS Forwarding Configurations
- Obtaining Real Client IPs
- Notes on SNAT and Non-SNAT Types for Private Network CLB
- Implementing HA Across Multiple AZs
- Load Balancing Algorithm Selection and Weight Configuration Examples
- Configuring WAF protection for CLB listening domain names
- Troubleshooting
- 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
- 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 TCP Listener
- Configuring UDP Listener
- Configuring TCP SSL Listener
- Configuring QUIC Listener
- Configuring 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
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practices
- Enabling Gzip Configuration & Testing
- HTTPS Forwarding Configurations
- Obtaining Real Client IPs
- Notes on SNAT and Non-SNAT Types for Private Network CLB
- Implementing HA Across Multiple AZs
- Load Balancing Algorithm Selection and Weight Configuration Examples
- Configuring WAF protection for CLB listening domain names
- Troubleshooting
- 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
- Cloud Load Balancer APIs
- Classic CLB APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
Private network CLB is used to distribute requests from Tencent Cloud's private network. It doesn't have a public IP and cannot communicate with the public network. If you need to use a private network CLB instance and want it to communicate with the public network, you can bind it to an EIP for public network access.
Note：The feature of binding private network CLB with EIP is currently in beta test. To try it out, submit a ticket.
Use Limits
- This feature is supported only for standard accounts but not traditional accounts.
- This feature is supported only for CLB but not classic CLB.
- This feature is supported only for private network CLB instances in VPCs but not in the classic network.
- There are no private network CLB instances in Ji'nan, Hangzhou, Fuzhou, Shijiazhuang, Wuhan, and Changsha regions, so this feature is not supported in these regions.
- After a private network CLB instance is bound to an EIP, the security group of the instance takes effect for traffic from the instance but not from the EIP. After the "Allow by Default" feature is enabled in the security group, it will take effect for both types of traffic.
- Currently, private network CLB doesn't support port ranges.
- A private network CLB instance can only be bound to an EIP that is in the same region and not bound to other resources.
- Each private network CLB instance can only be bound to one EIP.
- After a private network CLB instance is bound to an EIP, its features will be similar to those of a public network CLB instance, but public network CLB cannot be split into private network CLB and EIP.
Directions
Method : choose EIP when purchasing CLB
展开&收起- Log in to the CLB purchase page.
- Select the following CLB configuration items as needed. For other configuration details, see Purchase Methods.
Parameter Description Billing Mode Select the Pay-as-You-Go mode. Region Select a region. For more information on the regions supported by CLB, see Region List. Instance Type Only CLB instance type is supported. Network Type Select the Public Network type. EIP Select EIP. Tencent Cloud will assign you an EIP and a private network CLB instance. Supported EIP types include general IP, accelerated IP, and static single-line IP.
Method 2: bind private network CLB to EIP
展开&收起- Log in to the CLB console and click Instance Management on the left sidebar.
- Select a region in the top-left corner of the Instance Management page, select the target private network CLB instance in the instance list, and click More > Bind EIP in the Operation column on the right.
- In the Bind EIP pop-up window, select the EIP to be bound and click Submit to bind the EIP to the instance.
- (Optional) Select the target private network CLB instance in the instance list and click More > Unbind EIP in the Operation column on the right to unbind the instance from the EIP.
Yes
No
Was this page helpful?