Tencent Cloud EdgeOne
- Release Notes and Announcements
- Security Announcement
- Announcements
- Product Introduction
- Purchase Guide
- Billing Items
- Basic Service Fees
- Value-added Service Fees
- Instructions for overdue and refunds
- Getting Started
- Domain Service&Origin Configuration
- Domain Service
- Hosting DNS Records
- Domain Connection
- Traffic Scheduling
- HTTPS Certificate
- HTTPS Configuration
- SSL/TLS Security Configuration
- Origin Configuration
- Load Balancing
- Related References
- Origin-pull configuration
- Related References
- Site Acceleration
- Access Control
- Cache Configuration
- EdgeOne Cache Rules
- Cache Configuration
- Clear and Preheat Cach
- File Optimization
- Network Optimization
- HTTP/3(QUIC)
- QUIC SDK
- Modifying Header
- Modify the response content
- Rule Engine
- Related References
- Request and Response Actions
- DDoS & Web Protection
- DDoS Protection
- Configuration of Exclusive DDoS protection Rules
- Related References
- Web Protection
- Rate Limiting
- Bot Management
- Related References
- Related References
- Image&Video Processing
- Edge Functions
- Runtime APIs
- Streams
- Images
- Sample Functions
- Best Practices
- L4 Proxy
- Obtaining Real Client IPs
- Obtaining Real Client IPs Through Protocol V1/V2
- Data Analysis&Log Service
- Log Service
- Real-time Logs
- Data Analysis
- Related References
- Legacy Console Relevant Documentation
- Security Analysis
- Alarm Service
- Version Management
- Site and Billing Management
- Site Management
- General Policy
- Terraform
- Practical Tutorial
- Automatic Warm-up/Cache Purge
- Resource Abuse/hotlinking Protection Practical
- HTTPS Related Practices
- Acceleration Optimization
- Scheduling Traffic
- Origin-pull Based On User IP/geolocation
- APK Dynamic Packaging
- Data Analysis and Alerting
- API Documentation
- Making API Requests
- Site APIs
- Acceleration Domain Management APIs
- Site Acceleration Configuration APIs
- Edge Function APIs
- Alias Domain APIs
- Security Configuration APIs
- Layer 4 Application Proxy APIs
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- DNS Record APIs
- Content Identifier APIs
- Old Version APIs
- Version Management APIs
- Common Guidelines
- FAQs
- Troubleshooting
- Tool Guide
- Speed Test Tools
- Diagnostic Tool
- Agreements
DocumentationTencent Cloud EdgeOneData Analysis&Log ServiceLog ServiceReal-time LogsPush to AWS S3-Compatible COS
Push to AWS S3-Compatible COS
Last updated: 2025-01-24 14:57:43
EdgeOne Real-time Log Push can be configured through the console or API to push logs to AWS S3 Signature Version 4 Authentication Algorithm compatible COS, such as:
AWS S3
Operation step
1. Access the EdgeOne console, locate the left-hand menu, and select the Site List. Within this listing, click on the Site requiring configuration to enter its detailed page.
2. On the Site Details Page, click Log Service > Real-time Logs.
3. On the Real-time Logs page, click Create shipping task.
4. On Select the log source Page, fill in the Task name, select the Log type Service area, the Domain name/Layer 4 Proxy Instance/edge function instance for which the logs need to be pushed, and click Next.
Note:
Currently, only Site Acceleration Logs、L4 Proxy Logs and edge function runtime logs (in beta) are supported to be pushed to S3 Compatible COS.
5. On the Define delivery content page:
(Required) Check the log fields to be pushed from the Predefined field list;
(Optional) Add a Custom Log Field, supporting the extraction of specified field names from the Request Header, Response Header, and Cookie Header;
(Optional) Configure the Push Log Filter Criteria, the default is to push full logs;
(Optional) In advanced configuration, set the sampling ratio. By default, sampling is not enabled, and 100% of logs are pushed to the destination.
(Optional) In advanced configuration, set the log output format. The default format is JSON Lines.
6. On the Select a destination address page, select S3 compatible , click Next .
7. On the Destination Information Page, enter the related destination and parameter information.
Parameter name | Description |
Endpoint URL | URL without bucket name or path, e.g.: https://cos.ap-nanjing.myqcloud.com. |
bucket region | Region where the bucket is located, for example: ap-nanjing. |
Bucket | Bucket name and log storage directory, for example: your_bucket_name/EO-logs/. Whether or not you end the directory with /, it will be correctly parsed and processed. |
File compression | After checking, gzip will be used to compress log files. |
Secret ID | Access Key ID used to access the bucket. |
Secret key | Secret key used to access the bucket. |
8. Click Ship.
9. After issuing the real-time log push task, EdgeOne will push a test file to the target bucket directory to verify connectivity, for example,
1699874755_edgeone_push_test.txt, with the file content being the fixed string "test".File Name Description
Logs will be stored in the specified bucket directory in the format
{{UploadTime}}_{{Random}}.log, and will be archived by date (UTC+00:00) into folders. For example: 20230331/20230331T185917Z_2aadf5ce.log. When gzip compression is enabled, the file name will be 20230331/20230331T185917Z_2aadf5ce.log.gz.UploadTime: The upload time of the log file, using ISO-8601 Format, UTC+00:00 Time Zone.
Random: Random characters used to identify different files when there are multiple log files for the same upload time due to large log volume.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No