Via CDN Console

Last updated: 2021-09-29 15:53:28

    This document describes how to accelerate access to CVM instances through CDN console.


    1. You have signed up for a Tencent Cloud account and verified your identity.
    2. You have activated the CVM service. For more information, please see Getting started with CVM.


    Creating a Distribution

    Log in to the CDN console, click Domain Management in the left sidebar to enter the domain name management page, and click Create a Distribution.

    Part 1: Domain name configuration

    Enter your service domain name in the domain field and select the project, region, and service type:

    Configuration description:

    Configuration Description
    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 or and wildcard domain names in the format of * or * are supported.
    4. If the domain name is a wildcard domain or has been configured by another user, you need to verify the domain name ownership to access or retrieve it.

    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 format of * and *` cannot be configured at the same time.
    Project Project is a set of resources shared by all Tencent Cloud products. You can manage it on the Project Management page.
    Region the Chinese mainland: access requests of global users will be scheduled to cache nodes in the Chinese mainland for acceleration.
    Outside the Chinese mainland: access requests of global users will be scheduled to cache nodes outside the Chinese mainland for acceleration.
    Global: access requests of global users will be scheduled to the nearest optimal node for acceleration.

    Acceleration services in and outside the Chinese mainland are billed separately. For more information on billing policies, please see Billing Overview.
    Service Type CDN optimizes acceleration performance based on service type.
    For the best acceleration result, we recommend selecting the service type similar to that of your actual business.

    Static acceleration: suitable for small-scale resource acceleration scenarios such as ecommerce, websites, and game images.
    Download acceleration: suitable for download scenarios such as game installation, source audio/video file download, and mobile phone firmware distribution.
    Streaming VOD acceleration: suitable for scenarios such as online education and VOD.
    Internet Protocol IPv4: nodes can be accessed only through IPv4 addresses.
    IPv4+IPv6: nodes can be accessed through both IPv4 and IPv6 addresses. Only when this option is selected can an IPv6 origin server be configured.

    IPv6 is only supported in the Chinese mainland.

    Part 2: Origin server 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.

    Configuration description:

    Configuration Description
    Origin Server Type External: select this if you already have your own business server. (i.e., origin server).
    COS origin: if resources are stored in COS, the bucket can be directly selected as the origin server.
    Origin Server Address External origin server:
    1. Multiple IPs can be configured as the origin server, which will be polled during origin-pull.
    2. If multiple IPs are used, you can configure weighted origin-pull in the format of IP:port:weight(1 - 100). The port can be omitted and the format becomes IP::weight.
    3. You can configure one domain name as the origin server, which should be different from the business acceleration domain name.

    COS origin:
    1. Select from the drop-down list the bucket to be configured as the origin server.
    2. If the bucket is private read/write, first grant CDN access to the bucket. Otherwise, origin-pull will fail.
    Origin-pull Protocol This can be selected based on the protocols supported by the origin server:
    HTTP: HTTP/HTTPS access requests use HTTP origin-pull.
    HTTPS: HTTP/HTTPS access requests use HTTPS origin-pull (the origin server must support HTTPS access).
    Follow protocol: HTTP access requests use HTTP origin-pull, while HTTPS access requests use HTTPS origin-pull (the origin server must support HTTPS access).
    Origin Domain This refers to the domain name accessed on the origin server by a CDN node during origin-pull.
    If a subdomain name is connected, it will be the same as the acceleration domain name by default and can be customized.
    If a wildcard domain name is connected, it will be the actual access subdomain name by default and can be customized.

    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.
    Otherwise, Key will be a complete resource URL.
    This feature is disabled for static acceleration and enabled for download and streaming media VOD acceleration by default. For more information, see Cache Key Rule Configuration.
    Range GETs This specifies whether to process partial requests during origin-pull. It can be enabled only if the origin server supports Range GETs. For more information, see Range GETs Configuration.
    This feature is enabled for COS origin by default
    Cache Configuration This specifies node cache validity configuration. The cache expiration time for all files is 30 days by default.
    The configured cache validity is the longest possible time, the actual cache validity is related to the resources on nodes. For more information, see Node Cache Validity Configuration (Legacy)

    Completing the configuration

    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 a CNAME record for the domain name through your DNS service provider (such as DNSPod). Acceleration services will become available after the DNS configuration takes effect. For more information, please see CNAME Configuration.


    According to regulations, if the origin server is at an accelerated domain name of Tencent Cloud CVM, the domain name configured for the host header should obtain an ICP filing through Tencent Cloud. For more information, please see Host header configuration.