The billable items for ApsaraDB RDS include RDS instance billable items, value-added service billable items, and billable items for other Alibaba Cloud services related to RDS. This topic describes the definitions, billing formulas, and billing methods of the billable items.
RDS instances
Based on the billing method, RDS instances can be classified into the following types:
Subscription or pay-as-you-go RDS instances. When you purchase such an RDS instance, you must specify the specifications of the computing resources and storage capacity. After you purchase the instance, you are charged RDS instance type fees and storage capacity fees.
Serverless instances. The computing resources of a serverless RDS instance are automatically scaled within the specified range based on your workloads. The storage capacity of the serverless RDS instance is automatically expanded based on the data volume. Serverless instances incur RCU fees and storage capacity fees.
RDS instance type
Category | Description |
Definition | Fees for the computing resource specifications of subscription or pay-as-you-go RDS instances (including regular instances, read-only instances, and disaster recovery instances). The billable item is named RDS Instance Type (rds_class) or Instance Type (ClassCode). After you create an RDS instance, fees are generated for the billable item. If the computing resource specifications or the number of nodes of the instance are increased or decreased, the fees for the billable item generally change. |
Billing formula |
Note The unit price of the instance type varies based on the region, database engine, and specifications. For more information, visit the ApsaraDB RDS buy page or check your bills. |
Billing method | Subscription or pay-as-you-go. |
RCU for serverless instances
Category | Description |
Definition | Fees for the computing resources of a serverless RDS instance. The billable item is named RCU (rds_serverless_rcu). After you create a serverless RDS instance, fees are generated for the billable item based on the actual usage of RCUs. If you suspend the serverless RDS instance, fees are no longer generated for the billable item. |
Billing formula |
Note For more information about the unit price of RCUs, see Serverless ApsaraDB RDS for MySQL fees, Serverless ApsaraDB RDS for PostgreSQL fees, and Serverless ApsaraDB RDS for SQL Server fees. |
Billing method | Serverless. |
Storage capacity
Category | Description |
Definition | Fees for the storage capacity of subscription, pay-as-you-go, or serverless RDS instances (including regular instances, read-only instances, and disaster recovery instances). The billable item is named Storage Capacity (rds_storage or Storage). After you create an RDS instance, fees are generated for the billable item. If you expand or reduce the storage capacity of your RDS instance, the fees for the billable item change. |
Billing formula |
Note
|
Billing method | Subscription, pay-as-you-go, and serverless. |
Value-added features of ApsaraDB RDS
The value-added features are the paid features that are provided by ApsaraDB RDS. After you enable or use a value-added feature, fees are generated for the feature. The fee for the value-added feature is charged by ApsaraDB RDS.
Auto scaling
Category | Description |
Definition | You are not charged for enabling the auto scaling feature. However, if you enable the feature and the CPU utilization reaches the threshold, the computing resources of the ApsaraDB RDS for MySQL instance are increased and fees are generated for the increased computing resources based on the pay-as-you-go billing method.
|
Billing formula |
Note
|
Billing method | Pay-as-you-go. |
I/O burst for premium performance disks
Category | Description |
Definition | Fees for the I/O burst of an RDS instance that uses premium performance disks. You are not charged for enabling the I/O burst feature for premium performance disks. However, if you enable the feature and the I/O burst exceeds the free quota, fees are generated for the billable item named I/O Burst (io_burst). For more information about the feature, see I/O burst for ApsaraDB RDS for MySQL, I/O burst for ApsaraDB RDS for PostgreSQL. |
Billing formula | I/O burst fee for premium performance disks = (Total I/O burst of all nodes in the instance - Free quota) × Unit price of I/O burst × Duration Note For more information about the total I/O burst of all nodes in the instance, free quota, and unit price of I/O burst, see Billing of I/O burst for ApsaraDB RDS for MySQL and Billing of I/O burst for ApsaraDB RDS for PostgreSQL. |
Billing method | Pay-as-you-go. |
Premium performance disk data archiving
Category | Description |
Definition | You are not charged for enabling the data archiving feature. However, if you enable the feature, fees are generated for the billable item named OSS Storage Capacity (rds_oss_storage) for the data that is archived to Object Storage Service (OSS). For more information about the feature, see Data archiving for ApsaraDB RDS for MySQL, Data archiving for ApsaraDB RDS for PostgreSQL, or Data archiving for ApsaraDB RDS for SQL Server. Note For ApsaraDB RDS for SQL Server, the data archiving feature is supported for both premium performance disks and ESSDs. The data archiving feature for premium performance disks must be manually enabled. The data archiving feature for ESSDs is enabled by default. |
Billing formula | Premium performance disk data archiving fee = Archived data volume × Unit price of data archiving × Duration Note For more information about the unit price of data archiving, see Billing of data archiving for ApsaraDB RDS for MySQL, Billing of data archiving for ApsaraDB RDS for PostgreSQL, and Billing of data archiving for ApsaraDB RDS for SQL Server. |
Billing method | Pay-as-you-go. |
Regular backup and archived backup
Regular backup storage
Category | Description |
Definition | Data backup files and log backup files are stored in the backup storage that is provided by Alibaba Cloud. Alibaba Cloud provides a free quota for backup storage. If the backup storage exceeds the free quota, you are charged for the excess backup storage on a pay-as-you-go basis. The billable item is named RDS Basic Backup Fee (backup_charged). For more information about the feature, see Back up an ApsaraDB RDS for MySQL instance, Back up an ApsaraDB RDS for PostgreSQL instance, Back up an ApsaraDB RDS for SQL Server instance, or Back up an ApsaraDB RDS for MariaDB TX instance. |
Billable product | Relational database. |
Billing formula | Backup storage fee = (Total storage of backup files - Free quota) × Unit price of backup storage × Duration Note
|
Billing method | Pay-as-you-go. |
Archived backup storage
Category | Description |
Definition | Data backups that are more than 730 days old are automatically converted to archived backups. The billable item is named Long-term Backup (ArchivedBackupCharged). For more information, see Automatic backup. |
Product | Relational database. |
Billing formula | Fee for archived backup storage = Unit price of archived backup storage × Amount of archived backup storage × Duration Note For the unit price of archived backup storage, see Backup fees. |
Billing method | Pay-as-you-go. |
The billing items generated by cross-region backup include relational database and Database Backup products on your bill. For more information, see Data Disaster Recovery: cross-region backup, backup storage for deleted instances, and download of backup files.
The billing items generated by backup storage for deleted instances and download of backup files are billed as Database Backup products. For more information, see Data Disaster Recovery: cross-region backup, backup storage for deleted instances, and download of backup files.
Full restoration and regular database and table restoration
Full restoration (instance cloning)
When you use data backups and log backups of the original instance for data restoration to a new instance, you are charged for the RDS instance type and storage of the new instance.
For more information, see Restore MySQL data, Restore SQL Server data, Restore PostgreSQL data, Restore MariaDB data.
Regular database and table restoration
When you restore specific databases or tables to a new instance by using backup sets or to a point in time, you are charged for the RDS instance type and storage of the new instance. If you restore to the original instance, no fees are generated.
For more information, see Restore MySQL databases and tables, Restore PostgreSQL databases and tables.
SQL Audit (DAS Enterprise V0)
Category | Description |
Definition | Fees for the storage of the SQL logs that are generated by the SQL Audit feature. If you enable the SQL Audit feature, you are charged based on the size of the SQL logs that are generated by the SQL Audit feature and storage duration of the logs. The billing item is named SQL Audit (sql_collected). For more information, see RDS MySQL SQL Explorer and Audit, RDS SQL Server SQL Explorer and Audit, RDS PostgreSQL SQL Explorer and Audit. |
Billing product | Relational database. |
Billing formula | SQL audit fee = Unit price × Storage used by SQL logs that are generated by the SQL Audit feature × Duration Note For the unit price of SQL Audit, see MySQL SQL Explorer billing, PostgreSQL SQL Explorer billing, SQL Server SQL Explorer billing. |
Billing method | Pay-as-you-go. |
For the SQL Explorer and Audit feature provided by DAS Enterprise V3/V2/V1, the billing product is Database Autonomy Service. For more information, see DAS: SQL Explorer and Audit.
Performance monitoring
Category | Description |
Definition | When you set the performance monitoring frequency of an RDS MySQL instance to once every 5 seconds, performance monitoring (advanced_monitor) fees are incurred. If you select the 60-second or 300-second monitoring frequency, you are not charged for performance monitoring. The performance monitoring feature is provided free of charge for RDS instances that run PostgreSQL, SQL Server, or MariaDB. For more information about this feature, see Set the frequency of the legacy monitoring. |
Billing formula | Performance monitoring fee = Unit price of performance monitoring × Duration Note For the unit price of performance monitoring, see Fees. |
Billing method | Pay-as-you-go. |
Database proxy
Category | Description |
Definition | Fees for the database proxy feature. When you enable the database proxy feature and select Dedicated proxy as the proxy type, you are charged based on the specifications of the proxy and the duration of use. The billing item is named Number of database proxy instance shards (MaxscaleChargedSliceNum). General-purpose database proxies are provided free of charge. For more information about this feature, see RDS MySQL database proxy, RDS PostgreSQL database proxy. |
Billing formula | Database proxy fee = Unit price × Number of database proxies × Duration Note For the unit price of database proxies, see MySQL dedicated proxy pricing, PostgreSQL dedicated proxy pricing. |
Billing method | Pay-as-you-go. |
Public endpoint traffic
If you apply for a public endpoint for your RDS instance and use the public endpoint to connect to your RDS instance, Internet traffic is consumed. Currently, you are not charged for the inbound or outbound Internet traffic that is consumed to connect to your RDS instance by using the public endpoint.
For more information, see Enable or disable the public endpoint for an RDS MySQL instance, Enable or disable the public endpoint for an RDS SQL Server instance, Enable or disable the public endpoint for an RDS PostgreSQL instance, Enable or disable the public endpoint for an RDS MariaDB instance.
Other cloud products providing services and billing
ApsaraDB RDS integrates with other Alibaba Cloud services. If you use the following features, additional billable items are generated.
Data Disaster Recovery: cross-region backup, backup storage for deleted instances, download of backup files
Cross-region backup
Category | Description |
Definition | Fee for traffic that is consumed by cross-region backups and fee for the storage of backup files that are generated by cross-region backups. The following billable items are used: Cross-region backup storage (DdrOssStorageSize) and Traffic consumed by cross-region backups (NetworkOutDuplicationSize).
For more information, see Cross-region backup for MySQL, Cross-region backup for PostgreSQL, Cross-region backup for SQL Server. |
Billing product |
|
Billing formula |
Note
|
Billing method | Pay-as-you-go. |
Whether savings plans or resource plans can be used for deduction | DBS network plan can be used to offset the traffic consumed by cross-region backups (NetworkOutDuplicationSize) fees for subscription or pay-as-you-go ApsaraDB RDS instances. |
Backup storage for deleted instances
Category | Description |
Definition | Fees for the storage of backup sets of deleted ApsaraDB RDS for MySQL instances. If an RDS instance is deleted, the backup sets of the RDS instance are retained free of charge within seven days. After the 7-day retention period elapses, you are charged for the storage of the backup sets based on the size of the backup sets and retention duration. The following billable items are used:
For more information, see Configure the backup retention policy after instance release. |
Billing product | Database Backup. |
Billing formula | Fee for the backup storage of a deleted instance = Unit price of the backup storage for a deleted instance × Size of the backup sets of the deleted instance × Duration Note For the unit price of the backup storage for a deleted instance, see Billing. |
Billing method | Pay-as-you-go. |
Download of backup files
Category | Description |
Definition | Fees that are generated when you download the backup files of an ApsaraDB RDS instance, including the outbound traffic over Internet (NetworkOutSize) fee and the traffic consumed for the backup set conversion (BackupAnalyticSize) fee that is generated when you use the advanced download feature. For more information, see Download the backup files of an ApsaraDB RDS for MySQL instance, Download the backup files of an ApsaraDB RDS for SQL Server instance, Download the backup files of an ApsaraDB RDS for PostgreSQL instance. |
Billing product | Database Backup. |
Billing formula |
Note For the unit price of backup calculation data volume (also called backup conversion fee unit price) and outbound traffic over Internet unit price generated by downloading backups, see Download backup. |
Billing method | Pay-as-you-go. |
Whether savings plans or resource plans can be used for deduction | DBS network plan can be used to offset the outbound traffic over Internet (NetworkOutSize) fees for subscription or pay-as-you-go ApsaraDB RDS instances. |
Data Disaster Recovery: fast restoration of individual databases and tables (within 5 minutes), emergency recovery
Fast restoration of individual databases and tables and fast restoration of individual databases and tables within 5 minutes
Fast restoration of individual databases and tables within 5 minutes can no longer be enabled.
Category | Description |
Definition | The fast restoration feature for individual databases and tables of ApsaraDB RDS for MySQL with local SSDs instances is available in two editions: free edition and paid edition. The details are as follows:
|
Billing product | Database Backup. |
Billing formula | Fee = Unit price of the CDM local disk storage × Amount of the CDM local disk storage × Duration Note For the unit price of the CDM local disk storage, see Restore individual databases and tables. |
Billing method | Pay-as-you-go. |
Whether savings plans or resource plans can be used for deduction | CDM sandbox storage plan can be used to offset the CDM local disk storage (CapacitySandboxStorageSize) fees for subscription or pay-as-you-go ApsaraDB RDS for MySQL with local SSDs instances. |
Emergency recovery
Category | Description |
Definition | The emergency recovery feature of ApsaraDB RDS for MySQL with local SSDs instances involves the following billable items:
For more information, see Use the emergency recovery feature for an ApsaraDB RDS for MySQL instance. |
Billing product | Database Backup. |
Billing formula |
Note
|
Billing method | Pay-as-you-go. |
Whether savings plans or resource plans can be used for deduction | CDM sandbox storage plan can be used to offset the CDM local disk storage (CapacitySandboxStorageSize) fees for subscription or pay-as-you-go ApsaraDB RDS for MySQL with local SSDs instances. |
DAS: SQL Explorer and Audit
The billable items of DAS Enterprise Edition V3, DAS Enterprise Edition V2, and DAS Enterprise Edition V1 belong to the Database Autonomy Service billing product.