The global resource plan is a resource service that uses both Alibaba Cloud and global partner points of presence (POPs) to provide acceleration for domain names. Enabling this plan helps your domain name benefit from more POP resources in regions outside the Chinese mainland, optimizing access experience.
POP distribution
The global resource plan covers more than 200 POPs worldwide. The following table shows the specific distribution:
Billable region | Distribution |
North America | United States, Canada, and Mexico |
South America | Brazil, Argentina, Colombia, Chile, and Peru |
Europe | United Kingdom, Germany, Italy, Netherlands, France, Sweden, Austria, Spain, Poland, Belgium, Switzerland, Portugal, Bulgaria, Croatia, Czech, Denmark, Finland, Greece, Hungary, Ireland, Norway, and Romania |
Asia Pacific 1 | Hong Kong (China), Taiwan (China), Japan, Singapore, Philippines, Malaysia, and Thailand |
Asia Pacific 2 | Republic of Korea, India, Vietnam, and Indonesia |
Asia Pacific 3 | Australia and New Zealand |
Middle East and Africa | Israel, United Arab Emirates, South Africa, Oman, Nigeria, Bahrain, and Kenya |
The billing policies remain unchanged whether the global resource plan is enabled or not.
Before you begin
Only domain names with acceleration region set to Global (Excluding the Chinese Mainland) are supported.
After enabling the global resource plan, only certain features are supported.
Once enabled, the global resource plan cannot be directly disabled. To disable this feature, you need to delete the domain name and add it again to CDN.
Supported features after enabling the global resource plan
POST requests are not supported.
Category | Feature | Description | |
Domain names | Basic settings | CDN supports the following types of origin servers: Object Storage Service (OSS) domain names, IP addresses of origin servers, domain names of origin servers, and Function Compute domain names. Specify one or more origin servers of each type and primary and secondary origin servers to balance loads. | |
Enable IPv6 to allow IPv6-capable clients to send requests to CDN over IPv6. CDN also carries the IPv6 information of the clients to access your origin server. | |||
Origin fetch settings Note By default, the range origin fetch feature is enabled and cannot be disabled in the console. If you need to disable it, please submit a ticket. | Configure the default origin host if multiple websites are configured as your origin and the origin differs from the website associated to the accelerated domain name. Alibaba Cloud CDN redirects requests based on the HOST information to retrieve resources from the corresponding website. | ||
If an accelerated domain name is configured with multiple origin servers, and you want to retrieve resources from different virtual sites based on the value of the HOST header, you can specify the origin host for each origin server. | |||
CDN uses the protocol that is specified by the origin protocol policy to retrieve resources from an origin server. After you configure the origin protocol policy, CDN redirects HTTP requests to port 80 or HTTPS requests to port 443. | |||
If you configure a private OSS bucket as your origin server, we recommend that you enable the private bucket access feature and grant CDN permissions to access the OSS bucket. This feature can be used for access authentication to protect origin servers from unauthorized access. You can also include the authentication information in user requests to access private OSS buckets. | |||
You can configure a timeout period for HTTP origin requests to efficiently manage the connections between POPs and your origin server. If the timeout period for origin requests is too short, origin requests may fail when network connections are unstable. If the timeout period for origin requests is too long, failed requests will continue to occupy connections until they expire. This may cause normal requests to fail when the maximum number of connections to the origin server is reached. We recommend that you configure the timeout period based on your network connectivity and the maximum number of connections that your origin server can handle to ensure that requests can be redirected to the origin server as expected. | |||
Cache settings | Time-to-live (TTL) is the amount of time that a resource is cached on CDN POPs. When the TTL of a cached resource ends, the resource on the POPs expires. Requests that attempt to access expired resources are redirected to the origin server. The retrieved resources are returned to the clients and cached on the POPs. You can create a cache rule for resources based on file directories or file name extensions. | ||
HTTPS settings Note By default, TLS 1.2 is supported. You cannot modify the settings. To use TLS 1.0 or TLS 1.1, submit a ticket. | Note Only 2048- and 3072-bit RSA keys are supported. | CDN supports HTTPS secure acceleration. You can upload a custom SSL certificate or select an SSL certificate from Certificate Management Service in the CDN console. If you want to enable HTTPS to ensure the security of data transmission, SSL certificates are required. | |
HTTP/2, originally named HTTP/2.0, is another revision of the HTTP network protocol after HTTP/1.1. HTTP/2 supports binary framing, multiplexing, and header compression. HTTP/2 greatly improves web performance and reduces network latency. | |||
Note Only the default redirection type and HTTP to HTTPS are supported. | You can configure the URL redirection feature to forcibly redirect requests from clients to POPs to HTTPS. | ||
Refresh and prefetch | Note Only cache purge is supported. | The purge cache feature marks all resources that are cached on CDN POPs as expired. When a user requests the resource again, CDN retrieves the resource directly from the origin server, returns it to the user, and caches it again on the CDN POP. The feature reduces the cache hit ratio. | |
Tools and services | You can use this feature to query whether an IP address belongs to a POP, and the region and Internet service provider (ISP) to which an IP address belongs. | ||
Security protection | Certificate service | CDN supports HTTPS secure acceleration. You can deploy a certificate purchased from Alibaba Cloud Certificate Management Service for multiple domain names in the Alibaba Cloud CDN console. | |
You can query SSL certificates that are configured for your domain names, and check the status of the certificates. | |||
Usage query | You can query resource usage of specified domain names. You can set different filter conditions to query specific usage information, including bandwidth values, network traffic, and the number of HTTPS or QUIC requests. You can query information by accelerated domain name, time range, and billable region. | ||
CDN allows you to query the details of resource plans that you have purchased on the Resource Plans page, such as the total capacity, remaining capacity, and expiration time. | |||
Setup
Log on to the CDN console.
In the left-side navigation pane, click Domain Names.
Click Add Domain Name. On the Specify Domain Name Information page, configure Region and select Global (Excluding the Chinese Mainland).
Turn on Global Resource Plan.
