During events such as sales promotions, your service traffic may spike. Your actual queries per second (QPS) might exceed your purchased limit. To handle this, you can enable burstable QPS. This feature bills you for the excess QPS on a pay-as-you-go basis. It prevents your instance from being sandboxed and protects your services. Burstable QPS is available only for subscription instances. This topic describes how to enable this feature.
For more information, see Sandbox overview.
Scenarios
In scenarios with temporary and unpredictable QPS spikes, such as during sales promotions, you can enable burstable QPS to avoid frequent instance upgrades or downgrades.
Billable items
Scenario 1: Daily peak QPS ≤ Purchased QPS (Base QPS + Extension QPS)
The instance is billed on a subscription basis. For more information, see Subscription.
Scenario 2: Daily peak QPS > Purchased QPS (Base QPS + Extension QPS), and burstable QPS is disabled (default)
The instance is handled based on the standard QPS overage and sandbox mechanism. For more information, see Sandbox overview.
Scenario 3: Daily peak QPS > Purchased QPS (Base QPS + Extension QPS), and burstable QPS is enabled
The QPS usage that exceeds the purchased limit is billed on a pay-as-you-go basis.
QPS overage
Billable item
Billing cycle
Billing rule (Unit: USD)
≤ Burstable QPS (The value set when you enable the feature)
QPS overage
Request processing fee:
Basic traffic:
The Chinese mainland: USD 0.02/QPS/day
Outside the Chinese mainland: USD 0.03/QPS/day
Bot management or API security enabled:
The Chinese mainland: USD 0.035/QPS/day
Outside the Chinese mainland: USD 0.045/QPS/day
Both bot management and API security enabled:
The Chinese mainland: USD 0.05/QPS/day
Outside the Chinese mainland: USD 0.06/QPS/day
Fees are settled once per day (UTC+8). A new settlement cycle begins after the settlement is complete.
Daily fee = (Daily peak QPS - Purchased QPS) × Request processing fee
> Burstable QPS, and the instance has not been sandboxed on the current day (three or fewer QPS overage events).
Burstable QPS
Request processing fee:
Basic traffic:
The Chinese mainland: USD 0.02/QPS/day
Outside the Chinese mainland: USD 0.03/QPS/day
Bot management or API security enabled:
The Chinese mainland: USD 0.035/QPS/day
Outside the Chinese mainland: USD 0.045/QPS/day
Both bot management and API security enabled:
The Chinese mainland: USD 0.05/QPS/day
Outside the Chinese mainland: USD 0.06/QPS/day
Daily fee = Burstable QPS × Request processing fee
NoteAn overage event is recorded if the peak QPS exceeds the WAF specification threshold for 5 consecutive minutes. Multiple QPS overage events within a day are counted as a single event. If the number of overage events exceeds three, the instance is sandboxed on the fourth overage.
> Burstable QPS, and the instance has been sandboxed on the current day.
The instance is handled based on the sandbox mechanism. The fee for the day is 0.
N/A
Billing examples
This example uses the billing standards for Chinese Mainland. Assume you have a subscription WAF 3.0 Ultimate instance that includes 10,000 QPS and have purchased a 50,000 QPS extension. You are also using the bot management feature. If the peak service traffic for the day is 64,000 QPS, the QPS overage is 4,000 QPS (64,000 - 10,000 - 50,000).
If you enable burstable QPS and set the specification to 5,000 QPS:
In this scenario, the QPS overage is less than the burstable QPS specification. The request processing fee with bot management enabled is USD 0.035/QPS/day. The total fee is USD 140 (4,000 × 0.035).
If you enable burstable QPS and set the specification to 1,250 QPS:
In this scenario, the QPS overage is greater than the burstable QPS specification. The request processing fee with bot management enabled is USD 0.05/QPS/day. The total fee is USD 43.75 (1,250 × 0.035).
ImportantAn overage event is recorded if the peak QPS exceeds the WAF specification threshold for 5 consecutive minutes. Multiple QPS overage events within a day are counted as a single event. If the number of overage events exceeds three, the instance is sandboxed on the fourth overage.
An instance in a sandbox is no longer guaranteed by the Service-Level Agreement (SLA). Traffic protected by the instance may experience service access issues. These issues include but are not limited to packet loss, rate limiting, connection limits, protection failures, abnormal log or report data, access timeouts, and traffic entering DDoS scrubbing or blackhole filtering.
You can upgrade the QPS specification to remove the instance from the sandbox. For more information, see Sandbox overview.
Enable Elastic Pay-as-you-go
Go to the Web Application Firewall 3.0 buy page.
Set Billing Method to Subscription, and set a value for Threshold of Burstable QPS (Pay-as-you-go).
The supported specifications for Threshold of Burstable QPS (Pay-as-you-go) vary based on the instance edition.
Edition
The Chinese mainland
Outside the Chinese mainland
Basic Edition
Threshold of Burstable QPS (Pay-as-you-go) is not supported.
Threshold of Burstable QPS (Pay-as-you-go) is not supported.
Pro
Up to 60,000 QPS is supported.
Up to 1,000 QPS is supported.
Enterprise Edition
Up to 60,000 QPS is supported. If your business needs exceed the maximum supported specification, contact your account manager or architect.
Up to 1,000 QPS is supported. If your business needs exceed the maximum supported specification, contact your account manager or architect.
Ultimate
NoteIf you set Threshold of Burstable QPS (Pay-as-you-go) to 0 QPS, the burstable QPS feature is not enabled.
After you confirm the configuration, click Buy Now and complete the payment.
Manage bills
Log on to the WAF 3.0 console. In the top navigation bar, select the resource group and region of the WAF instance. You can select Chinese Mainland or Outside Chinese Mainland.
In the navigation pane on the left, choose .
On the bill list, you can view daily information, such as the burstable billing type, burstable unit price, peak QPS, current specification (QPS), total fee, and instance status.