All Products
Search
Document Center

ApsaraDB RDS:Billable items

Last Updated:Mar 01, 2024

This topic describes the billable items of ApsaraDB RDS and the billing methods and pricing of each billable item.

Instance type

Note

When you purchase a subscription RDS instance, the subscription billing method is used only for its instance type and storage capacity. If you use features that use the pay-as-you-go billing method, bills for relevant billable items are generated on a pay-as-you-go basis. For example, you may create pay-as-you-go read-only RDS instances, use the SQL Explorer feature or the performance monitoring feature, or use more backup storage than the free quota. The billing methods of all billable items are listed in this topic.

Nodes in an ApsaraDB RDS for MySQL cluster

  • Definition: An RDS cluster is billed based on the nodes in the RDS cluster. For more information about an RDS cluster, see Add a node to an ApsaraDB RDS for MySQL cluster.

  • Billing: Subscription and pay-as-you-go.

  • Pricing: The price varies based on the nodes that you add to the RDS cluster. After you select specifications for a node during the cluster creation, the price of the node is displayed in the Pricing column of the table on the ApsaraDB RDS buy page. For more information about the pricing of a single node, visit the ApsaraDB RDS buy page.

    Formula: Total price of the RDS cluster = Price per node × Number of nodes. If you add a new node to the RDS cluster, you need to pay for the new node.

RCU

  • Definition: A serverless RDS instance is billed based on RDS Capacity Units (RCUs). For more information about serverless RDS instances, see Overview of serverless ApsaraDB RDS for MySQL instances, Overview of serverless ApsaraDB RDS for SQL Server instances, and Overview of serverless ApsaraDB RDS for PostgreSQL instances.

  • Billing: The system issues bills for the RCUs that are used by a serverless RDS instance on an hourly basis.

  • Pricing:

    ApsaraDB RDS for MySQL

    ApsaraDB RDS for PostgreSQL

    Billable item

    Region

    Unit price

    RCU

    China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), and China (Chengdu)

    USD 0.0497 per RCU-hour

    US (Silicon Valley) and US (Virginia)

    USD 0.0672 per RCU-hour

    Philippines (Manila) and Thailand (Bangkok)

    USD 0.0746 per RCU-hour

    Singapore, Malaysia (Kuala Lumpur), and UK (London)

    USD 0.0796 per RCU-hour

    Indonesia (Jakarta)

    USD 0.0821 per RCU-hour

    Germany (Frankfurt)

    USD 0.0836 per RCU-hour

    Australia (Sydney)

    USD 0.0847 per RCU-hour

    China (Hong Kong)

    USD 0.0867 per RCU-hour

    Korea (Seoul)

    USD 0.0895 per RCU-hour

    Japan (Tokyo)

    USD 0.0995 per RCU-hour

    Storage capacity

    China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Shenzhen), China (Heyuan), China (Guangzhou), and China (Chengdu)

    USD 0.00024 per GB-hour

    Philippines (Manila) and Thailand (Bangkok)

    USD 0.00032 per GB-hour

    China (Hong Kong), Japan (Tokyo), South Korea (Seoul), Singapore, Australia (Sydney), Malaysia (Kuala Lumpur), Indonesia (Jakarta), Germany (Frankfurt), UK (London), US (Silicon Valley), and US (Virginia)

    USD 0.0004 per GB-hour

    ApsaraDB RDS for SQL Server

    Billable item

    Unit price

    RCU

    • China (Hong Kong): USD 0.312 per RCU-hour

    • Singapore: USD 0.288 per RCU-hour

    Storage capacity

    ESSD PL1: USD 0.0008 per GB-hour

Storage capacity

Read-only RDS instance (optional)

Data restoration to new RDS instances (optional)

Backup (optional)

Backup storage

Cross-region backup

  • Definition: Fees for the storage of backup files that are generated by the cross-region backup feature. For more information, see Use the cross-region backup feature for an ApsaraDB RDS for MySQL instance, Use the cross-region backup feature for an ApsaraDB RDS for SQL Server instance, and Use the cross-region backup feature for an ApsaraDB RDS for PostgreSQL instance.

  • Billing: Pay-as-you-go. You are charged based on the size and storage duration of backup files.

  • Pricing:

    ApsaraDB RDS for MySQL

    • Cloud disk

      The following table describes the fees that are generated if you perform cross-region backups on an RDS instance that uses cloud disks in the ApsaraDB RDS console.

      Item

      Region

      Unit price

      Cross-region storage fee

      China (Beijing), China (Hohhot), China (Ulanqab), China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Chengdu), China (Qingdao), China (Guangzhou), and China (Zhangjiakou)

      USD 0.0009375 per GB-day

      China (Hong Kong), US (Silicon Valley), US (Virginia), Singapore, Japan (Tokyo), Germany (Frankfurt), Australia (Sydney), Malaysia (Kuala Lumpur), Indonesia (Jakarta), India (Mumbai), Philippines (Manila), UK (London), South Korea (Seoul), and Thailand (Bangkok)

      USD 0.001125 per GB-day

      Network traffic fee

      For more information about the billing rules for each region, see Network traffic fees.

      Note
      • You can use DBS storage plans to offset the fee generated for the cross-region backup storage when you perform cross-region backups on your RDS instance that uses cloud disks in the ApsaraDB RDS console. For more information, see Storage fees.

      • If your RDS instance contains a large amount of data, we recommend that you use DBS network plans to offset the network traffic fees. For more information, see Use network plans.

    • Local disk

      The following table describes the fees that are generated if you perform cross-region backups on an RDS instance that uses local disks in the ApsaraDB RDS console.

      Item

      Unit price

      Cross-region storage fee

      USD 0.0002 per GB-hour

      Network traffic fee

      For more information about the billing rules for each region, see Network traffic fees.

      Note

      If your RDS instance contains a large amount of data, we recommend that you use DBS network plans to offset the network traffic fees. For more information, see Use network plans.

    ApsaraDB RDS for PostgreSQL

    The following fees are generated if you perform cross-region backups on an RDS instance in the ApsaraDB RDS console:

    • Cross-region storage fee: USD 0.0002 per GB-hour

    • Network traffic fee. For more information, see Network traffic fees.

    Note

    If your RDS instance contains a large amount of data, we recommend that your use DBS storage plans to offset the network traffic fees. For more information, see Storage fees.

    ApsaraDB RDS for SQL Server

    The following fees are generated if you perform cross-region backups on an RDS instance in the ApsaraDB RDS console:

    • Cross-region storage fee: USD 0.0002 per GB per hour

    • Network traffic fee. For more information, see Network traffic fees.

    Note

    If your RDS instance contains a large amount of data, we recommend that your use DBS storage plans to offset the network traffic fees. For more information, see Storage fees.

Backup sets of deleted RDS instances

  • Definition: If the backup sets of an ApsaraDB RDS for MySQL instance are retained more than seven days after the RDS instance is deleted, you are charged for the storage of the backup sets. For more information, see Method 2: Configure the backup retention policy after the instance is released.

  • Billing: Pay-as-you-go. You are charged based on the size and storage duration of backup sets.

  • Pricing:

    Type

    Region

    Unit price (USD per GB-day)

    Public cloud

    China (Hangzhou), China (Beijing), China (Shanghai), China (Shenzhen), China (Qingdao), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Heyuan), China (Ulanqab), and China (Guangzhou)

    0.00058

    China (Hong Kong), Singapore, US (Silicon Valley), Germany (Frankfurt), Indonesia (Jakarta), Philippines (Manila), and Thailand (Bangkok)

    0.00067

    Japan (Tokyo), South Korea (Seoul), and Australia (Sydney)

    0.0007

    US (Virginia)

    0.00062

    India (Mumbai)

    0.00063

    Malaysia (Kuala Lumpur)

    0.00064

    UK (London)

    0.00065

    UAE (Dubai)

    0.00072

Backup download (optional)

  • Definition: If you download the backup files of an RDS instance, you are charged for the traffic generated during the download. For more information, see Download backup files of an ApsaraDB RDS for MySQL instance, Download backup files of an ApsaraDB RDS for SQL Server instance, Download backup files of an ApsaraDB RDS for PostgreSQL instance, and Download backup files of an ApsaraDB RDS for MariaDB instance.

  • Billing: You are charged based on the download traffic. If you use the advanced download feature to download backup files, you are also charged for the conversion of the backup sets.

    Note

    The advanced download feature is supported for RDS instances that run MySQL and PostgreSQL and use cloud disks.

  • Pricing:

    Download traffic fee

    • Downloads over an internal network: You are not charged for the traffic that you consume.

    • Downloads over the Internet: After the free quota of 500 GB per instance-month is exhausted, you are charged for the excess traffic that you consume based on the pay-as-you-go billing method. Fees are deducted from your account on a daily basis. For more information, see Network traffic fees.

    Note
    • When you start a task to download the snapshot backup file of an RDS instance that uses cloud disks, the system converts the backup file and generates a download task. If the task is not complete, the download URL cannot be obtained. In this case, you are not charged for Internet traffic. In-progress tasks and failed tasks are considered not complete. After the task is complete, you are charged for the traffic generated when you download the backup file by using the URL.

    • When you download the physical backup file of an RDS instance that uses local disks, the system does not convert the backup file and directly provides you with the download URL. You are charged for the traffic generated when you download the backup file by using the URL.

    • To view the volume of traffic that you consumed to download backup files over the Internet, you can log on to the ApsaraDB RDS console, find your RDS instance, and then click the ID of the instance to go to the Basic Information page of the RDS instance. Then, you can view the Backup Downloads parameter in the Usage Statistics section of the page.

    • We recommend that you purchase a subscription network plan to offset the fee for the Internet traffic that is used to download the backup files. A large capacity of a network plan indicates a high discount. For more information, see Use network plans.

    Backup set conversion fee

    If you use the advanced download feature, the snapshot backup files are converted into CSV, SQL, or Parquet files, and you are charged for backup set conversions. No free quota is provided for backup set conversion. The following table describes the unit prices for backup set conversion in different regions.

    Region

    Unit price (USD per GB)

    Public cloud

    0.03125

    Note

    When you start a task to download the snapshot backup file of an RDS instance that uses cloud disks, the system generates a task to convert the backup file. If the conversion task fails, you are not charged for backup set conversion.

Restoration (optional)

Data restoration

Restoration of individual databases and tables

  • Definition: Fees for using the paid version of the fast restoration feature for individual databases and tables to restore specific databases or tables to the original RDS instance or a new RDS instance by using backup sets or to a point in time. For more information, see Restore individual databases and tables of an ApsaraDB RDS for MySQL instance and Restore individual databases and tables of an ApsaraDB RDS for PostgreSQL instance.

    Note

    The fast restoration feature for individual databases and tables is supported for RDS instances that run MySQL and PostgreSQL. Some capabilities of the feature are in public review.

  • Billing: Subscription and pay-as-you-go.

  • Pricing:

    ApsaraDB RDS for MySQL

    Standard restoration feature for individual databases and tables

    Local disk

    By default, the standard restoration feature for individual databases and tables is enabled and is provided free of charge. If you use the standard restoration feature to restore individual databases or tables to a new RDS instance, you are charged for the new RDS instance. You can view the price details when you create the RDS instance.

    Note

    Cloud disk

    Starting December 1, 2023, if you enable the restoration feature for individual databases and tables for an RDS instance that uses cloud disks, the backup architecture is upgraded, and the amount of backup data is increased by 30% to 80%. If the total amount of backup data does not exceed the free quota, no fees are generated. If the total amount exceeds the free quota, you are charged for the excess backup storage that you use. For more information, see View and manage the size of backup files. For more information about billing rules, see Backup storage fees.

    Fast restoration feature for individual databases and tables

    The fast restoration feature for individual databases and tables is not supported for RDS instances that use cloud disks. The feature is supported for RDS instances that use local disks and supports free and paid editions.

    • Free edition: If you enable and use the fast restoration feature for individual databases and tables of this edition, no fees are generated.

    • Paid edition: If you enable and use the fast restoration feature for individual databases and tables of this edition, you are charged based on the actual data volume by using the pay-as-you-go billing method. Unit price: USD 0.008 per GB-day

    Note
    • Free edition: You can restore data from backup sets or to the point in time at which the last full data backup is performed.

    • Paid edition: You can restore data from backup sets or to a specific point in time.

    ApsaraDB RDS for PostgreSQL

    The fast restoration feature for individual databases and tables is in public preview. You can use the feature free of charge.

Performance monitoring (optional)

  • Definition: Fees for using the performance monitoring feature.

  • Billing:

    • The performance monitoring feature is provided free of charge for RDS instances that run PostgreSQL, SQL Server, and MariaDB.

    • For RDS instances that run MySQL, if you select the 5-second monitoring frequency, you are charged an hourly fee for the feature. However, if you select the 60-second or 300-second monitoring frequency, you are not charged fees for the feature. For more information, see Configure a monitoring frequency.

  • Pricing: USD 0.012 per hour.

SQL Explorer and Audit (optional)

  • Definition: Fees for using the SQL Explorer and Audit feature. For more information, see Use the SQL Explorer feature on an ApsaraDB RDS for MySQL instance, Use the SQL Explorer feature on an ApsaraDB RDS for SQL Server instance, and Use the SQL Explorer feature on an ApsaraDB RDS for PostgreSQL instance.

  • Billing: Pay-as-you-go. This feature is disabled by default. If you enable it, you are charged an hourly fee for it. Fees are deducted from your Alibaba Cloud account on an hourly basis.

  • Pricing:

    ApsaraDB RDS for MySQL

    • SQL Explorer Trial Edition: Since August 20, 2020, new billing rules are applied to SQL Explorer Trial Edition in Alibaba Cloud regions in phases.

      SQL Explorer Trial Edition provides a 15-day free trial. After the 15-day free trial expires, the SQL Explorer feature becomes unavailable. If you want to continue using the SQL Explorer feature, we recommend that you purchase SQL Explorer Paid Edition before the free trial expires.

      Note You can enable SQL Explorer Trial Edition only once for each RDS instance.
    • SQL Explorer Paid Edition: You are charged on an hourly basis. The price varies based on the region of your RDS instance.
      • USD 0.0015 per GB per hour: China (Hong Kong), US (Silicon Valley), and US (Virginia)
      • USD 0.0018 per GB per hour: Singapore (Singapore), Japan (Tokyo), Germany (Frankfurt), UAE (Dubai), Australia (Sydney), Malaysia (Kuala Lumpur), India (Mumbai), Indonesia (Jakarta), and UK (London)
      • USD 0.0012 per GB per hour: all regions except the preceding regions

    ApsaraDB RDS for PostgreSQL

    • USD 0.15 per GB per hour: China (Hong Kong), US (Silicon Valley), and US (Virginia).

    • USD 0.18 per GB per hour: Singapore, Japan (Tokyo), Germany (Frankfurt), UAE (Dubai), Australia (Sydney), Malaysia (Kuala Lumpur), India (Mumbai), Indonesia (Jakarta), and UK (London).

    • USD 0.12 per GB per hour: all regions except the preceding regions.

    ApsaraDB RDS for SQL Server

    • USD 0.15 per GB-hour: China (Hong Kong), US (Silicon Valley), and US (Virginia).

    • USD 0.18 per GB-hour: Singapore, Japan (Tokyo), Germany (Frankfurt), UAE (Dubai), Australia (Sydney), Malaysia (Kuala Lumpur), India (Mumbai), Indonesia (Jakarta), and UK (London).

    • USD 0.12 per GB-hour: all regions except the preceding regions.

    Note

    For ApsaraDB RDS for MySQL instances that run RDS Enterprise Edition, this feature is enabled by default and is provided free of charge. However, if you disable and then enable this feature again, you will be charged fees for this feature by DAS.

Database proxy (optional)

  • Definition: Fees for using database proxies. Database proxies are used to implement read/write splitting. For more information, see What are database proxies in ApsaraDB RDS for MySQL and What are database proxies in ApsaraDB RDS for PostgreSQL?

    Note

    Database proxies are supported for RDS instances that run MySQL and PostgreSQL.

  • Billing: Pay-as-you-go. This feature is disabled by default. If you enable it, you are charged an hourly fee for it. Fees are deducted from your Alibaba Cloud account on an hourly basis.

  • Pricing:

    ApsaraDB RDS for MySQL

    Region

    Price

    Region name

    Region code

    USD per proxy-hour

    China (Hangzhou)

    cn-hangzhou

    0.173

    China (Shanghai)

    cn-shanghai

    0.173

    China (Qingdao)

    cn-qingdao

    0.173

    China (Beijing)

    cn-beijing

    0.173

    China (Zhangjiakou)

    cn-zhangjiakou

    0.120

    China (Hohhot)

    cn-huhehaote

    0.173

    China (Shenzhen)

    cn-shenzhen

    0.173

    China (Heyuan)

    cn-heyuan

    0.173

    China (Chengdu)

    cn-chengdu

    0.173

    China (Hong Kong)

    cn-hongkong

    0.297

    Japan (Tokyo)

    ap-northeast-1

    0.288

    India (Mumbai)

    ap-south-1

    0.231

    Singapore

    ap-southeast-1

    0.271

    Australia (Sydney)

    ap-southeast-2

    0.273

    Malaysia (Kuala Lumpur)

    ap-southeast-3

    0.253

    Indonesia (Jakarta)

    ap-southeast-5

    0.271

    Germany (Frankfurt)

    eu-central-1

    0.243

    UK (London)

    eu-west-1

    0.280

    UAE (Dubai)

    me-east-1

    0.377

    US (Virginia)

    us-east-1

    0.237

    US (Silicon Valley)

    us-west-1

    0.284

    ApsaraDB RDS for PostgreSQL

    Region

    Price (USD per proxy-hour)

    UAE (Dubai)

    0.377

    Australia (Sydney)

    0.273

    Germany (Frankfurt)

    0.243

    China (Zhangjiakou) and China (Ulanqab)

    0.120

    Malaysia (Kuala Lumpur)

    0.253

    US (Virginia)

    0.237

    US (Silicon Valley)

    0.284

    Japan (Tokyo)

    0.288

    Singapore and Indonesia (Jakarta)

    0.271

    India (Mumbai)

    0.231

    UK (London)

    0.280

    China (Hong Kong)

    0.297

    Other

    0.173

Automatic expansion (optional)

Internet-based connection