- CDN Release Notes
- Getting Started
- Product Introduction
- Purchase Guide
- Getting Started
- Configuration Guide
- Permission Management
- Best Practice
- API Documentation
- FAQ
- Troubleshooting Methods
- Service Level Agreement
- Glossary
- CDN Release Notes
- Getting Started
- Product Introduction
- Purchase Guide
- Getting Started
- Configuration Guide
- Permission Management
- Best Practice
- API Documentation
- FAQ
- Troubleshooting Methods
- Service Level Agreement
- Glossary
This document describes how to accelerate access to resources in COS through CDN.
Prerequisites
- You have signed up for a Tencent Cloud account and verified your identity.
- A COS bucket has been created. For more information, see Creating Buckets.
Directions
Creating a Distribution
Log in to the CDN console and click Domain Management in the left sidebar to enter the domain name management page. Then click Create a Distribution. 
Selecting COS as origin server
Part 1: Domain name configuration
Enter your business domain name in the domain field, select a project and acceleration type, choose whether to enable IPv6 access, and set a tag:
Configuration description:
| Configuration | Description |
|---|---|
| Region | Chinese mainland: all requests are scheduled to cache nodes in the Chinese mainland. Outside the Chinese mainland: all requests are scheduled to cache nodes outside the Chinese mainland. Global: requests are scheduled to the nearest optimal node. Notes: Acceleration services in and outside the Chinese mainland are billed separately. For more information, see Billing Overview. |
| Domain | 1. The domain name can contain up to 81 characters. 2. The domain name should have obtained an ICP filing from the MIIT. 3. Subdomain names in the format of a.test.com or a.b.test.com and wildcard domain names in the format of *.test.com or *.a.test.com are supported. 4. If the domain name is a wildcard domain name or has been connected by another user, you need to verify the domain name ownership to connect or retrieve it. Notes: 1. After a wildcard domain name is configured, its subdomain names and second-level wildcard domain names cannot be connected to in another account. 2. Domain names in the formats of *.test.com and *.a.test.com cannot be configured at the same time. |
| Project | (Optional) Project is a set of resources shared by all Tencent Cloud products. You can manage it on the Project Management page. |
| Acceleration type | CDN optimizes acceleration performance based on service type. For better acceleration effect, we recommend selecting the acceleration type similar to that of your actual business. Static acceleration: applicable to small-scale resource acceleration scenarios such as e-commerce, website, and game photos. Download acceleration: applicable to downloading scenarios such as game installation packages, audio and video source file downloads, and mobile phone firmware distribution. On-demand video streaming acceleration: applicable to online education and on-demand video streaming. |
| IPv6 Access | (Optional) CDN nodes support IPv4 access by default. IPv6 access will be supported after it is enabled. Note: IPv6 access is only available in the Chinese mainland. |
| Tag | (Optional) A tag is used to manage resources by category from different dimensions. If the existing tags do not meet your requirements, please go to Tag. |
Part 2: Origin configuration
Configure business origin server information. If a CDN node has no resource cache, the node will pull the resource from the origin server and cache it.
- Select COS from the Origin Type drop-down list under Domain Configuration.
- Select an origin-pull protocol based on the support of the origin server.
- Select a bucket for the origin address.
- Enable Private Bucket Access. You should go to COS-bucket permission management to authorize the CDN service first. After the service authorization is confirmed, you can manually enable this feature.
- The default setting is used for Origin Domain. No modification is required.
Part 3: Service configuration
Configure the node acceleration service:
Configuration description:
| Configuration | Description |
|---|---|
| Ignore Parameter | A node caches resources by following the Key-Value mapping, where Key is the resource URL.If Ignore Query String is enabled, parameters after "?" in the URL will be ignored before mapping. Otherwise, Key will be a complete resource URL. By default, this feature is enabled for download and on-demand video streaming acceleration, but not for static acceleration. |
| Range GETs | This specifies whether to process partial requests during origin-pull. It can be enabled only if the origin server supports Range GETs. This feature is enabled for COS origin server by default. |
| Cache Configuration | This specifies the expiration period of the node cache, which is 30 days for all files by default. The cache validity period is the longest possible validity. The actual validity may be shorter as affected by the available storage capacity of the node. You can set the cache configuration based on origin type. |
After entering all configuration items on Create a Distribution page, click Submit to add a domain name and wait for the domain name configuration to be delivered over the entire network, which usually takes 5 to 10 minutes.
Configuring CNAME
After successfully adding a domain name, you can view the acceleration CNAME assigned by CDN on the Domain Management page.
You need to add the CNAME record for the domain name at your DNS service provider (such as DNSPod). Acceleration services will become available after the DNS configuration takes effect. For more details, see CNAME Configuration.
Recommended Configuration
- After completing all the settings, prefetch the static resource files in COS to CDN nodes in advance, which will reduce the strain on the origin server and accelerate response and downloading. For more details, see Prefetch Cache.
- Configure cross-origin access headers. For more details on cross-origin permissions of resources, see HTTP Response Header.
- If the resource has been modified on your origin server, you are recommended to purge cache before prefetch again. For more details, see Purge Cache.
Yes
No
Was this page helpful?