- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Directions
- CLB Instance
- Creating CLB Instances
- Creating an IPv6 CLB Instance
- Creating IPv6 NAT64 CLB Instances
- Creating an Anycast CLB Instance
- Configuring CLB Security Group
- Binding Private Network CLB to EIP
- Cloning CLB Instances
- Exporting CLB Instances
- Upgrading CLB Instance
- Deleting CLB Instances
- Releasing Idle CLB Instances
- 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 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
- CLB Instance
- 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 Guide
- 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
- Directions
- CLB Instance
- Creating CLB Instances
- Creating an IPv6 CLB Instance
- Creating IPv6 NAT64 CLB Instances
- Creating an Anycast CLB Instance
- Configuring CLB Security Group
- Binding Private Network CLB to EIP
- Cloning CLB Instances
- Exporting CLB Instances
- Upgrading CLB Instance
- Deleting CLB Instances
- Releasing Idle CLB Instances
- 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 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
- CLB Instance
- 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 Guide
- 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
Announcement on the Deactivation of the Feature of Storing CLB Access Logs in COS
Last updated: 2020-07-28 16:58:25
This document is currently invalid. Please refer to the documentation page of the product.
Dear Tencent Cloud User,
The feature of storing Cloud Load Balancer (CLB) access logs in Cloud Object Storage (COS) will be deactivated as per the following schedule.
| Time | Deactivation plan |
|---|---|
| 00:00:00, April 26, 2020 | The feature of storing access logs in COS will stop accepting new enablement requests in Guangzhou, while existing logs stored in COS will not be affected. |
| 00:00:00, May 15, 2020 | The feature of storing access logs in COS will stop accepting new enablement requests in Beijing, Shanghai, and Hong Kong (China), while existing logs stored in COS will not be affected. |
| 00:00:00, June 30, 2020 | The feature of storing access logs in COS will be officially deactivated in all regions, and all CLB instances will no longer provide this feature. |
The feature of storing access logs in Cloud Log Service (CLS), an upgrade version of storing access logs in COS, has been officially available. Compared to storing access logs in COS, the feature of storing access logs in CLS provides the following benefits:
- Real-time logging at a minute-level granularity and diversified online search based on full-text, key-value, and fuzzy keywords
- Multi-region coverage and other capabilities, making it more suitable for large-scale use in production environments
- On-demand shipping of logs from CLS to COS
As COS and CLS have different service modes, we cannot directly modify the configuration for you. We recommend that you change the access log storage from COS to CLS before 00:00:00, June 30, 2020. Please configure access log storage in CLS first and then disable access log storage in COS.
Tencent Cloud does not store any access logs by default. If you need such logs for your business, please configure access log storage in CLS on your own. We are very sorry for any inconvenience caused.
If you have already modified the configuration, please ignore this announcement. Thank you again for your always support and trust.
Sincerely,
Tencent Cloud Team
Yes
No
Was this page helpful?