Skip to content

Content Delivery Network

Set up acceleration domains for static assets and files, with origin, cache and HTTPS controls. Manage purge and prefetch tasks, domain status and hit rates in one platform, and review costs in the billing center.

Origin options
Existing origin / Object Storage
Management unit
Acceleration domain
Cache tasks
Purge / Prefetch
CDN domainsConfiguration example
static.example.com
Enabled
OriginOriginal content
Edge cache
Node ANode BNode C
UsersReceive content
ProtocolHTTPS
Cache rulesBy file type
Content updatesPurge / Prefetch
Fictional example · Content access and configuration

Features

Configure origin and access rules for each domain, then maintain the service using cache tasks, access statistics and bills.

Domain and origin

Add an acceleration domain, configure the origin and origin protocol, and review its status.

HTTPS configuration

Configure a certificate and check its domain coverage, validity and actual HTTPS access.

Cache purge and prefetch

Purge changed content, or prefetch content in advance, then check the task results.

Monitoring

Monitor domain status, bandwidth, requests and cache hit rates. Reconcile usage and charges in the billing center.

Risk alerts and notifications

Review alerts and use console notification settings to receive actionable updates.

Download protection

Configure download protection for your integration and check which domains and requests it covers.

Use cases

Choose the workflow that fits your business.

Website static assets

Serve images, styles and scripts through an acceleration domain. Configure caching and purge content after updates.

File downloads

Connect a file origin to a domain, verify origin fetches and downloads, and review traffic by domain.

Access to stored objects

Use a bucket as an origin following the setup guide. Configure storage permissions, the CDN domain and billing items separately.

Quick start

Prepare the required information, then verify actual access after setup.

Read the setup guide
  1. 01

    Prepare the origin

    Confirm origin access, prepare a test resource and check the service region and origin requirements.

  2. 02

    Add a domain

    Enter the domain, origin and service settings, then complete the required ownership verification.

  3. 03

    Configure DNS and certificates

    Follow the DNS instructions. For HTTPS, install a valid certificate matching the domain.

  4. 04

    Verify access

    Allow DNS and configuration changes to take effect, then check domain status, response content and origin access.

  5. 05

    Maintain cache and usage

    Purge or prefetch as needed, check task results and review access statistics and bills.

Billing model

Charges follow applicable CDN usage rules. Review the region, billing item, period and actual bill. App download counts cannot be directly converted to CDN traffic.

View billing rules

FAQ

What to know about setup, usage and billing.

Help center
Can I use CDN with my own origin?

Yes, subject to the setup requirements. Object Storage is not required. Confirm that your origin is reachable and that its content and domain meet the service conditions.

Does a domain work immediately after I add it?

Complete the required ownership verification, origin, DNS and certificate configuration, then test actual access. Changes may take time; use console status and verification results to confirm readiness.

How do purge and prefetch differ?

Purging makes matching cached content eligible to be fetched again. Prefetching retrieves content in advance using supported methods. Check service documentation and task results for scope, limits and completion.

What are the roles of the CDN and origin?

The origin supplies the original content. The CDN handles requests according to cache and access rules and fetches from the origin when needed. Troubleshoot the origin, domain, DNS, certificate and cache separately.

Is CDN usage the same as app download counts?

No. CDN billing measures traffic and other applicable usage, while App Distribution records its own download events. Content sizes and cache behavior vary, so the two cannot be converted directly.

Can CDN be combined with Object Storage?

Yes, following the current integration guide. Check permissions, origins, domains and billing items separately, then verify the configuration.

Content Delivery NetworkReview current service settings and applicable prices in the console.
Open CDN