Yes. By default, the bandwidth limit on each account is 15 Gbit/s in each public cloud region in the Chinese mainland, and 10 Gbit/s in any other regions. If this threshold is exceeded, traffic throttling will be triggered for requests. To increase the threshold, please submit a ticket.
Bucket endpoints in the format of
<BucketName-APPID>.cos.<Region>.myqcloud.com are in XML format. You can directly preview file types supported by your browser by accessing the object URL using this endpoint format.
Take the picture.jpg file in the root directory of the bucket
examplebucket-1250000000 in the Beijing region as an example:
If the object endpoint is in the format of
https://examplebucket-1250000000.cos.ap-beijing.myqcloud.com/picture.jpg, you can directly access it to preview the picture.jpg file via your browser.
You can also set the value of the request parameter
response-content-disposition in the GET Object API to
attachment so that your browser can pop up a window for the file to be downloaded. For more information, please see GET Object.
To use the
response-*parameter in a request, the request must be signed.
The access endpoints of COS use intelligent DNS resolution. For COS access via the Internet (including different ISPs), we will detect and select the optimal linkage for you to access COS. If you have deployed a service in Tencent Cloud to access COS, access within the same region will be automatically directed to a private network address. Cross-region access is not supported in a private network and the COS endpoint is resolved to a public network address by default.
Tencent Cloud products within the same region access each other over a private network by default, incurring no traffic fees. Therefore, we recommend choosing the same region when you purchase different Tencent Cloud products to save on costs.
The following shows how to determine access over a private network:
For example, when a CVM accesses COS, to determine whether a private network is used for access, use the
nslookup command on the CVM to resolve the COS endpoint. If a private network IP is returned, access between the CVM and COS is over a private network; otherwise, it is over a public network.
Generally, a private IP address takes the form of
100.*.*.*, and a VPC IP address takes the form of
examplebucket-1250000000.cos.ap-guangzhou.myqcloud.com is the address of the destination bucket; the
Address: 10.148.214.13 below indicates access is over a private network.
nslookup examplebucket-1250000000.cos.ap-guangzhou.myqcloud.com Server: 10.138.224.65 Address: 10.138.224.65 #53 Name: examplebucket-1250000000.cos.ap-guangzhou.myqcloud.com Address: 10.148.214.13 Name: examplebucket-1250000000.cos.ap-guangzhou.myqcloud.com Address: 10.148.214.14
For more information about private and public network access and connectivity testing, please see COS Access via Private Network and Public Network.
For the private DNS server addresses of CVM, please see Private Network DNS.
There are differences between the private IP address of a CPM (common format:
9.*.*.*) and the IP address of a CVM (common format:
10.*.*.*). If you have any questions, please submit a ticket for assistance.
You can log in to COSBrowser, select the folder to be downloaded, and click Download to download the folder or files in batches. You can also download a folder using the COSCMD tool. For more information, please see COSCMD.
Troubleshoot the problems by following the steps below:
COS allows you to upload or download multiple files through various methods such as the console, APIs/SDKs, and tools.
The versioning feature is now available in COS. If versioning is not enabled for the bucket, when you upload a new file to a bucket in which another file of the same name already exists, the older one will be directly overwritten; if versioning is enabled, multiple versions of the object will co-exist.
1 MB. For more information, please see Specifications and Limits.
This error may occur due to an unstable local network environment. You can try the upload again in a different network environment.
You can set your bucket permission to private read/write. For more information, please see Setting Access Permission. You can also configure a hotlink protection allowlist on your bucket to block any access from endpoints that are not in the list. For more information, please see Setting Hotlink Protection.
COS allows each root account to have up to 1,000 bucket ACLs. If more bucket ACLs have been configured, this error will occur. Therefore, you can delete unnecessary bucket ACLs.
You are not advised to use object-level ACLs or policies. When calling APIs or SDKs, if you do not need ACL control over a file, we recommend leaving the ACL-related parameters (such as x-cos-acl and ACL) empty to inherit the bucket permissions.