Domain and origin
Add an acceleration domain, configure the origin and origin protocol, and review its status.
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.
Configure origin and access rules for each domain, then maintain the service using cache tasks, access statistics and bills.
Add an acceleration domain, configure the origin and origin protocol, and review its status.
Configure a certificate and check its domain coverage, validity and actual HTTPS access.
Purge changed content, or prefetch content in advance, then check the task results.
Monitor domain status, bandwidth, requests and cache hit rates. Reconcile usage and charges in the billing center.
Review alerts and use console notification settings to receive actionable updates.
Configure download protection for your integration and check which domains and requests it covers.
Choose the workflow that fits your business.
Serve images, styles and scripts through an acceleration domain. Configure caching and purge content after updates.
Connect a file origin to a domain, verify origin fetches and downloads, and review traffic by domain.
Use a bucket as an origin following the setup guide. Configure storage permissions, the CDN domain and billing items separately.
Prepare the required information, then verify actual access after setup.
Confirm origin access, prepare a test resource and check the service region and origin requirements.
Enter the domain, origin and service settings, then complete the required ownership verification.
Follow the DNS instructions. For HTTPS, install a valid certificate matching the domain.
Allow DNS and configuration changes to take effect, then check domain status, response content and origin access.
Purge or prefetch as needed, check task results and review access statistics and bills.
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.
What to know about setup, usage and billing.
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.
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.
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.
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.
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.
Yes, following the current integration guide. Check permissions, origins, domains and billing items separately, then verify the configuration.