Resource plans
Alibaba Cloud DCDN resource plans offer significant savings over pay-as-you-go pricing. Learn about the available plan types and their deduction rules.
-
For billing details of services associated with resource plans, see the DCDN Pricing page.
-
Resource plans for outbound traffic, static HTTPS requests, and Edge WAF can be shared between Alibaba Cloud CDN and DCDN.
|
Resource plan |
Description |
Purchase URL |
|
Offsets DCDN outbound traffic. WebSocket traffic is excluded. Important
To use this resource plan to offset outbound traffic costs, your metering method must be |
||
|
Offsets static HTTPS requests for all domain names with HTTPS acceleration enabled.What is HTTPS acceleration? |
||
|
Offsets dynamic HTTP requests for all accelerated domain names and dynamic HTTPS requests for all domain names with HTTPS acceleration enabled. |
||
|
Offsets outbound traffic generated by IP application acceleration.What is IP application acceleration? Important
IP application acceleration supports both |
||
|
Offsets outbound traffic generated by the WebSocket service.Configure WebSocket Important
The WebSocket service supports both |
||
|
To enable Anti-DDoS, you must purchase a protection plan of a specific edition (Insurance or Unlimited).DDoS mitigation Important
After you enable the protection service and add a domain name, an additional pay-as-you-go fee for scrubbed traffic applies. This fee is based on the DCDN outbound traffic generated by the domain name. For pricing details on scrubbed traffic, see Billing of DDoS mitigation. |
||
|
Offsets WAF requests for all accelerated domain names with the WAF feature enabled.Edge WAF protection (old version) |
||
|
Offsets SeCUs consumed by the new edition of Edge WAF.Overview of WAF (new edition) |
Outbound traffic
You can purchase multiple outbound traffic resource plans. If you have multiple plans, the one expiring soonest is deducted first. The system calculates outbound traffic usage every hour. Usage within the quota is deducted from the remaining balance. Overage is billed on a pay-as-you-go basis.
DCDN provides eight outbound traffic resource plans based on acceleration region. Each plan offsets usage only within its specified region; cross-region deductions are not supported.
|
Acceleration region |
Description |
|
Chinese mainland |
For acceleration in the Chinese mainland. |
|
Asia Pacific 1 |
For acceleration in Hong Kong (China), Macao (China), Taiwan (China), Japan, and Southeast Asian countries and regions excluding Vietnam and Indonesia. |
|
Asia Pacific 2 |
For acceleration in India, Indonesia, South Korea, and Vietnam. |
|
Asia Pacific 3 |
For acceleration in Australia and New Zealand. |
|
North America |
For acceleration in North America. |
|
Europe |
For acceleration in Europe. |
|
Middle East and Africa |
For acceleration in the Middle East and Africa. |
|
South America |
For acceleration in South America. |
Static HTTPS requests
You can purchase multiple resource plans for static HTTPS requests. If you have multiple plans, the one that expires soonest is deducted first. The system calculates static HTTPS request usage every hour. Usage within the quota is deducted from the remaining balance. Overage is billed based on the number of static HTTPS requests.
Dynamic requests
A dynamic requests resource plan offsets both dynamic HTTP and dynamic HTTPS requests. You can purchase multiple plans. If you have multiple plans, the one expiring soonest is deducted first. The system calculates dynamic request usage every hour. Usage within the quota is deducted from the remaining balance. Overage is billed based on the number of dynamic HTTP and HTTPS requests.
IP application acceleration (TCP/UDP) traffic
This resource plan covers outbound traffic for IP application acceleration and currently supports deductions only in the Chinese mainland region. You can purchase multiple plans, and the one that expires soonest is deducted first.
The system calculates IP application acceleration (TCP/UDP) traffic usage every hour. Usage within the quota is deducted from the remaining balance. Overage is billed based on a tiered pricing model.
WebSocket traffic
This resource plan covers WebSocket outbound traffic. Like standard outbound traffic plans, WebSocket traffic plans are region-specific and available for eight acceleration regions. Each plan offsets usage only within its specified region. You can purchase multiple plans, and the one that expires soonest is deducted first.
The system calculates WebSocket traffic usage every hour. Usage within the quota is deducted from the remaining balance. Overage is billed based on a tiered pricing model.
Edge WAF requests plan (old version)
After you enable the WAF feature, Edge WAF inspects all requests to the specified domain name and aggregates the request count at the account level. The system calculates WAF request usage every hour. Usage within the quota is deducted from the remaining balance. Overage is billed based on the number of Edge WAF requests.
The Edge WAF requests plan (old version) currently supports deduction only in the Chinese mainland region. You can purchase multiple plans, and the one that expires soonest is deducted first.
Edge WAF SeCU plan (new edition)
The new edition of Edge WAF is a pay-as-you-go service billed by Security Capacity Units (SeCUs). All billable items are converted into SeCUs.
You can purchase multiple Edge WAF SeCU plans. If you have multiple plans, the one that expires soonest is deducted first. The system calculates SeCU consumption every hour. Usage within the quota is deducted from the remaining balance. Overage is billed based on the number of consumed SeCUs.
DDoS mitigation plan
DDoS protection helps defend your accelerated domain names against DDoS attacks. To enable Anti-DDoS, you must purchase a protection plan of a specific edition (Insurance or Unlimited).
After you enable the protection service and add a domain name, an additional pay-as-you-go fee for scrubbed traffic applies. This fee is based on the DCDN outbound traffic generated by the domain name. For pricing details on scrubbed traffic, see Billing of DDoS mitigation.