tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Overview

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-10-29 16:13:02
The global acceleration feature provided by Tencent Cloud Object Storage (COS) utilizes a load balancing system based on Tencent's global traffic scheduling to intelligently route and parse user requests and select the optimal network linkage for nearby access. Backed by globally deployed Tencent Cloud data centers, it allows users across the world to quickly access buckets and improves application access success rate, allowing for greater business stability and a smoother user experience. In addition, COS's global acceleration also speeds up uploads and downloads.
Note:
Global acceleration supports COS public cloud regions. However, it is not supported in finance cloud regions due to network isolation.
Using this feature incurs fees as request data transfers are accelerated via Direct Connect lines in the Tencent Cloud private network. For more pricing information, see Product Pricing.

Directions

You can enable global acceleration on the COS Console or through APIs.

Using the COS console

1. Log in to the COS Console.
2. In the left sidebar, click Bucket List to go to the bucket list page.
3. Locate the bucket that requires global acceleration configuration, click its bucket name to enter the bucket details page.
4. In the left navigation bar, select Domains and Transfer > Global Acceleration, then click Edit in the Global Acceleration section to enable the current status.
5. After confirming that everything is correct, click Save to enable the bucket's global acceleration.
Global acceleration domain name: When uploading objects via this domain, public network global acceleration effect is achievable. The domain name format is <BucketName-APPID>.cos.accelerate.myqcloud.com.
6. After enabling global acceleration, you only need to access the bucket via the global acceleration domain name to achieve quick data access.
Note:
Note: Enabling global acceleration will not affect the original default bucket domain name. You can still use it normally.

Using RESTful APIs

You can directly use the following APIs to enable global acceleration:

Access Endpoint Domain Names

After enabling global acceleration, you can access your COS files through two types of endpoint domain names:
Default bucket endpoint domain name: Format: <BucketName-APPID>.cos.<Region>.myqcloud.com. For more information, see Regions and Access Endpoints.
Global acceleration endpoint domain name: Format: <BucketName-APPID>.cos.accelerate.myqcloud.com.
Take the bucket examplebucket-1250000000 in Guangzhou as an example. If you have enabled global acceleration for it, when you need to upload the file exampleObject.txt from Beijing to it, you can do so in the following two ways:
Use the global acceleration endpoint domain name for access: when uploading the object, you need to set the endpoint domain name to examplebucket-1250000000.cos.accelerate.myqcloud.com. When you upload the object through this endpoint domain name, COS will intelligently parse your request based on your network conditions and implement nearby access. For example, it will forward your request to the Beijing access layer and then transmit it to the Guangzhou storage layer via a private network Direct Connect line to accelerate data transfer.
Use the default bucket endpoint domain name for access: when uploading the object, you need to set the endpoint domain name to examplebucket-1250000000.cos.ap-guangzhou.myqcloud.com. When you upload the object through this endpoint domain name, your request will be directly forwarded to the Guangzhou access layer and then the Guangzhou storage layer. In this case, long public network linkage may lead to unstable transfer.
Note:
If you use global acceleration, fees will be incurred. Therefore, we recommend that you carefully evaluate whether to use this feature with your actual business needs in mind:
If your business has more writes (e.g., PUT Object, POST Object, and Multipart Upload) than reads and uploads data to Tencent Cloud data centers from a remote region, we recommend using a global acceleration endpoint domain name.
If your business has more reads (e.g., GET Object) than writes and mainly involves file download, we recommend that you perform a comprehensive evaluation of the CDN-based access acceleration solution and select the option with the best cost performance.
If your business mainly involves configuration operations or file extraction, we recommend using the default bucket endpoint domain name.
If your business needs to access buckets over a private network or through a Direct Connect line within the same region, we recommend using the default bucket endpoint domain name.

Configuring DNS Intelligent Resolution

f businesses need worldwide access, they can configure DNS intelligent resolution to determine if a user is in domestic or outside Chinese mainland for faster response to user access. Go to the appropriate DNS service provider to configure the CNAME resolution record. Main directions:
1. Add domain: Add a custom domain name that requires intelligent parsing, then go to its record management page.
2. Add record: Create 2 CNAME records (for example, set the host record to accelerate). Set the resolution record type of the first entry to domestic and the record value to the bucket's default domain name examplebucket-1250000000.cos.ap-guangzhou.myqcloud.com. Set the resolution record type of the second entry to default and the record value to the global acceleration domain name examplebucket-1250000000.cos.accelerate.myqcloud.com.
3. Log in to the COS console and configure a custom domain name for the bucket, selecting the global acceleration origin site as the origin server. A red exclamation mark may appear next to the custom domain name, indicating a domain resolution issue, which can be ignored.
4. After configuration as per the aforementioned method, access your custom domain name to achieve the effect:
If your local DNS egress IP originates from outside Chinese mainland, the domain names or IP addresses queried and retrieved will be the global acceleration domain.
If your local DNS egress IP comes from domestic, the domain names or IP addresses queried and retrieved will be the bucket's default domain.
5. If you use the COS SDK, you can initialize the client with a custom domain name to achieve the desired effect. Take JS SDK as an example:
import COS from 'cos-js-sdk-v5';

const cos = new COS({
SecretId: 'your_tmpSecretId', // temporary secretId issued by the sts service
SecretKey: 'your_tmpSecretKey', // temporary secretKey issued by the sts service
SecurityToken: 'your_sessionToken', // temporary SessionToken issued by the sts service
Domain: 'your.custom.domain' //input custom domain name
});

Notes

We have outlined below some important factors to note when using a global acceleration endpoint domain name:
The global acceleration domain name will take effect 15 minutes after being enabled.
After the global acceleration domain name is enabled, the maximum bandwidth for a bucket will be allocated based on the business volume of the entire network.
After the global acceleration domain name is enabled, only requests using that domain name will be accelerated. However, the default bucket domain name can still be used.
When using a global acceleration domain name, fees will be incurred only for requests for which linkage is accelerated. For example, if you use a global acceleration domain name to upload data from Beijing to a bucket in Beijing, the request will not incur acceleration fees as the linkage was not accelerated.
When using a global acceleration domain name, you can specify the HTTP or HTTPS transfer protocol. However, if the request is transmitted via a private network Direct Connect line, COS will choose to use the HTTPS protocol to guarantee data transfer security.

Billing Example

Uploading data or accessing a bucket by using a global acceleration endpoint domain name will incur fees calculated by the day. For more information, see Billing Overview and Product Pricing. The following example compares billing between a global acceleration endpoint domain name and a default endpoint domain name:
Business scenario 1
A user uses COS mainly to upload video files which require a high transmission success rate. If he/she uploads 1 GB of video data daily from his/her offices in Xinjiang and Singapore to his/her bucket in Guangzhou, then 30-day fees will be charged as follows:
Upload traffic fees for using an acceleration endpoint domain name: 30 x 1 GB x (0.07 USD/GB + 0.18 USD/GB) = 7.5 USD
Upload traffic fees for using a default bucket endpoint domain name: 30 x 1 GB x (0 USD/GB) = 0 USD
Note:
Upload traffic fees within the Chinese mainland are charged at 0.07 USD/GB, while those outside the Chinese mainland are charged at 0.18 USD/GB when an acceleration endpoint domain name is used. Uploads with a default bucket endpoint domain name do not incur fees.
Business scenario 2
A user uses COS mainly to download video files that require a high transmission success rate. If he/she downloads 1 GB of video data daily from his/her office in Singapore to his/her bucket in Guangzhou, then 30-day fees will be charged as follows:
Download traffic fees for using an acceleration domain name: 30 x 1 GB x 0.18 USD/GB = 5.4 USD
Public downstream traffic fees for using an acceleration domain name: 30 x 1 GB x 0.1 USD/GB = 3 USD
To sum up, the total download traffic fee is 8.4 USD (5.4 + 3 = 8.4).
Note:
The unit price for cross-border download acceleration is 0.18 USD/GB. If you use a global acceleration domain name to download files, public downstream traffic fees and global acceleration downstream traffic fees will be charged.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan