You must pay for ApsaraDB for Redis instances that you create based on the instance type. If the audit log feature is enabled or the bandwidth is upgraded during the instance runtime, corresponding fees are also incurred.
The following table describes how ApsaraDB for Redis instances are billed.
When you create an ApsaraDB for Redis or Tair instance, you are charged for the instance based on its instance type and subscription duration. The subscription and pay-as-you-go billing methods are supported. For more information about instance creation, see Step 1: Create an ApsaraDB for Redis instance. For more information about instance billing, see Billing methods.
Instance specification fees include disk fees that are fixed. The disks are used for system operation, such as storing logs, temporary backup files, and append-only files (AOFs).
If the audit log feature is enabled for an instance, you are charged for the storage and retention of logs. A bill is generated each hour. For more information, see Enable the new audit log feature.
The bandwidth of an instance varies based on the instance type. For more information, see Enable the new audit log feature. If the bandwidth of an instance is insufficient to handle traffic spikes (such as those generated during flash sales), you can increase the bandwidth by manually adjusting the bandwidth or enabling bandwidth auto scaling, without instance specification changes. For more information, see Adjust the bandwidth of an ApsaraDB for Redis instance and Enable bandwidth auto scaling.
You are charged based on the amount of purchased extra bandwidth and the duration for which the extra bandwidth is used. A bill is generated each day.
Instance type fees
For more information, see Pricing Calculator.
Audit log storage fees
Audit logs are billed hourly based on storage usage. For example, if an instance in the China (Hangzhou) region stores 100 GB of audit logs for 1 hour, you are charged USD 0.2.
|Area||Region||Region ID (used in API operations)||Unit price (USD per GB-hour)|
|Asia Pacific||China (Hangzhou)||cn-hangzhou||0.002|
|China (Hong Kong)||cn-hongkong||0.006|
|Malaysia (Kuala Lumpur)||ap-southeast-3||0.004|
|Europe & Americas||Germany (Frankfurt)||eu-central-1||0.006|
|US (Silicon Valley)||us-west-1||0.006|
|Middle East & India||India (Mumbai)||ap-south-1||0.004|
Extra bandwidth fees
For example, assume that you manually purchase an extra bandwidth of 10 Mbit/s for your instance located in the China (Hangzhou) region in the morning. In the afternoon, the bandwidth auto scaling feature purchases an extra bandwidth of 10 Mbit/s for the instance. On that day, a total extra bandwidth of 20 Mbit/s is purchased for the instance. In this case, you are charged based on the following formula: USD 0.15 × 20 MB = USD 3.0.
|Area||Region||Region ID (used in API operations)||Unit price (USD per MB-day)|
|Asia Pacific||China (Hangzhou)||cn-hangzhou||0.15|
|China (Hong Kong)||cn-hongkong||0.33|
|Malaysia (Kuala Lumpur)||ap-southeast-3||0.23|
|Europe & Americas||Germany (Frankfurt)||eu-central-1||0.33|
|US (Silicon Valley)||us-west-1||0.33|
|Middle East & India||India (Mumbai)||ap-south-1||0.23|