The billable items that may be involved when you use ApsaraDB RDS include the billable items for ApsaraDB RDS instances, billable items for value-added features, and billable items for other cloud services related to ApsaraDB RDS. This topic describes the definitions, billing formulas, and billing methods of the billable items.
RDS instances
RDS instances can be classified into two types based on the billing methods of the RDS instances. For more information, see Billing methods.
Subscription or pay-as-you-go RDS instances. When you purchase a subscription or pay-as-you-go RDS instance, you must specify the computing resources and storage capacity for the RDS instance. After you purchase an RDS instance, you are charged for the instance type and storage capacity.
Serverless RDS instances. When you purchase a serverless RDS instance, you must specify the range of computing resources. The computing resources of the 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. After you purchase a serverless RDS instance, you are charged for the RDS Capacity Units (RCUs) and storage capacity.
Instance type
Category | Description |
Definition | Fees for the computing resources of your subscription or pay-as-you-go RDS instance. The RDS instance can be a regular instance , disaster recovery (DR) instance, or read-only instance. The name of the billable item is RDS instance type or instance type. The code of the billable item is rds_class or ClassCode. After you create an RDS instance, fees are generated for the billable item. If you increase the computing resources or the number of nodes, the fees for the billable item 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. |
RCUs of serverless RDS instances
Category | Description |
Definition | Fees for the computing resources of a serverless RDS instance. The name of the billable item is RCU. The code of the billable item is 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 Pricing of serverless ApsaraDB RDS for MySQL instances, Pricing of serverless ApsaraDB RDS for PostgreSQL instances, and Pricing of serverless ApsaraDB RDS for SQL Server instances. |
Billing method | Serverless. |
Storage capacity
Category | Description |
Definition | Storage capacity fee of your subscription, serverless, or pay-as-you-go RDS instance. The RDS instance can be a regular instance, read-only instance, or DR instance. The name of the billable item is storage capacity. The code of the billable item is 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 The unit price of the storage capacity varies based on the region, RDS edition, storage type, and billing method. The actual price in the ApsaraDB RDS console shall prevail. The duration in the preceding formulas is calculated in different methods based on the billing method of the instance.
|
Billing method | Subscription, serverless, and pay-as-you-go. |
Value-added features
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.
Automatic performance scaling
Category | Description |
Definition | You are not charged for enabling the automatic performance scaling feature. For more information, see Configure the automatic performance scaling feature. 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. |
Regular backup storage and archived backup storage
Regular backup storage
Category | Description |
Definition | Fees for the storage of data backup files and log backup files. Alibaba Cloud provides a free quota on backup storage. If the backup storage exceeds the free quota, you are charged for excessive backup storage based on the pay-as-you-go billing method. The name of the billable item is regular backup storage. The code of the billable item is backup_charged. For more information, see Use the automatic backup feature, Back up an ApsaraDB RDS for PostgreSQL instance, Back up an ApsaraDB RDS for SQL Server instance, and Back up an ApsaraDB RDS for MariaDB instance. |
Fees charged by | ApsaraDB RDS. |
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 | Fees for the storage of archived backup files. Data backup files that are retained for more than 730 days are considered archived backup files. The name of the billable item is long-term backup. The code of the billable item is ArchivedBackupCharged. For more information, see Use the automatic backup feature. |
Fees charged by | ApsaraDB RDS. |
Billing formula | Fee for archived backup storage = Unit price of archived backup storage × Amount of archived backup storage × Duration Note For more information about the unit price of archived backup storage, see Backup storage fees. |
Billing method | Pay-as-you-go. |
Fees for the billable items that are generated for cross-region backups are charged by ApsaraDB RDS and Database Backup (DBS). For more information, see the DBS: cross-region backup, backup storage of deleted instances, and backup download section of this topic.
Fees for the billable items that are generated for backup storage for deleted instances and backup downloads are charged by DBS. For more information, see Billable items.
Full restoration and standard restoration of individual databases and tables
Full restoration (instance cloning)
Fees generated for the instance type and storage capacity of a new RDS instance when you use the data backup files and log backup files of the original RDS instance to restore the data to the new RDS instance. For more information, see the Instance type and Storage capacity sections of this topic.
For more information, see Restore full data of an ApsaraDB RDS for MySQL instance, Restore the data of an ApsaraDB RDS for SQL Server instance, Restore data of an ApsaraDB RDS for PostgreSQL instance, and Restore data of an ApsaraDB RDS for MariaDB instance.
Standard restoration of individual databases and tables
Fees generated for the instance type and storage capacity of a new RDS instance when you restore specific databases or tables to the new RDS instance by using backup sets or to a point in time. For more information, see the Instance type and Storage capacity sections of this topic. If you restore specific databases or tables to the original RDS instance, no fees are generated.
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.
Fees for the billable items that are generated for fast restoration of individual databases and tables, fast restoration of individual databases and tables within 5 minutes, and emergency recovery are charged by DBS. For more information, see the DBS: Fast restoration of individual databases and tables within 5 minutes and emergency recovery section of this topic.
SQL Audit (DAS Enterprise Edition 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 name of the billable item is SQL audit. The code of the billable item is sql_collected. For more information, see Use the SQL Explorer feature for an ApsaraDB RDS for MySQL instance, Use the SQL Explorer feature for an ApsaraDB RDS for SQL Server instance, and Use the SQL Explorer feature for an ApsaraDB RDS for PostgreSQL instance. |
Fees charged by | ApsaraDB RDS. |
Billing formula | SQL audit fee = Unit price × Storage used by SQL logs that are generated by the SQL Audit feature × Duration Note For more information about the unit price of SQL Audit, see Use the SQL Explorer feature for an ApsaraDB RDS for MySQL instance, Use the SQL Audit feature for an ApsaraDB RDS for PostgreSQL instance, and Use the SQL Audit feature for an ApsaraDB RDS for SQL Server instance. |
Billing method | Pay-as-you-go. |
The SQL Explorer and Audit feature is provided by DAS Enterprise Edition V3, DAS Enterprise Edition V2, or DAS Enterprise Edition V1. The fee for the feature is charged by Database Autonomy Service (DAS). For more information, see the DAS: SQL Audit and Explorer section of the topic.
Performance monitoring
Category | Description |
Definition | If you select the 5-second monitoring frequency for an ApsaraDB RDS for MySQL instance, you are charged an hourly fee for performance monitoring. The code of the billable item is advanced_monitor. 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, and MariaDB. For more information, see Set the monitoring frequency. |
Billing formula | Performance monitoring fee = Unit price of performance monitoring × Duration Note For more information about the unit price of performance monitoring, see Configure a monitoring frequency. |
Billing method | Pay-as-you-go. |
Database proxy
Category | Description |
Definition | Fees for the database proxy feature. If you enable the database proxy feature and dedicated database proxies, you are charged based on the proxy specifications and duration. The name of the billable item is the number of database proxy instance shards. The code of the billable item is MaxscaleChargedSliceNum. General-purpose database proxies are provided free of charge. For more information, see What are database proxies in ApsaraDB RDS for MySQL and What are database proxies in ApsaraDB RDS for PostgreSQL? |
Billing formula | Database proxy fee = Unit price of database proxies × Number of database proxies × Duration Note For more information about the unit price of database proxies, see What are database proxies in ApsaraDB RDS for MySQL? and What are database proxies in ApsaraDB RDS for PostgreSQL? |
Billing method | Pay-as-you-go. |
Traffic consumed to connect to an RDS instance by using the public endpoint
If you apply for and use a public endpoint to connect to your RDS instance, Internet traffic is consumed. 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 Apply for or release a public endpoint for an ApsaraDB RDS for MySQL instance, Apply for or release a public endpoint for an ApsaraDB RDS for SQL Server instance, Apply for or release a public endpoint for an ApsaraDB RDS for PostgreSQL instance, and Apply for or release a public endpoint for an ApsaraDB RDS for MariaDB instance.
Billing items for other cloud services
ApsaraDB RDS integrates with other Alibaba Cloud services. If you use the feature of the integrated services, additional billable items are generated.
DBS: cross-region backup, backup storage of deleted instances, and backup download
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 Use the cross-region backup feature for an ApsaraDB RDS for MySQL instance, Use the cross-region backup feature for an ApsaraDB RDS for PostgreSQL instance, and Use the cross-region backup feature for an ApsaraDB RDS for SQL Server instance. |
Fees charged by |
|
Billing formula |
Note
|
Billing method | Pay-as-you-go. |
Savings plans or resource plans | You can purchase DBS network plans to offset the fees that are generated for the traffic consumed by cross-region backups (NetworkOutDuplicationSize) of your subscription or pay-as-you-go RDS instance. For more information, see Use network plans. |
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 Use the backup for deleted instances feature. |
Fees charged by | DBS. |
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 more information about the unit price of the backup storage for a deleted instance, see Retain backup files for a long period of time. |
Billing method | Pay-as-you-go. |
Backup download
Category | Description |
Definition | Fees for the backup downloads of your RDS instance. The fees include the fee for outbound Internet traffic (NetworkOutSize) and fee for the traffic consumed for the backup set conversion (BackupAnalyticSize). 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, and Download backup files of an ApsaraDB RDS for PostgreSQL instance. |
Fees charged by | DBS. |
Billing formula |
Note For more information about the unit prices of backup set conversion and outbound Internet traffic, see Download backup files. |
Billing method | Pay-as-you-go. |
Savings plans or resource plans | You can purchase DBS network plans to offset the fees that are generated for the outbound Internet traffic (NetworkOutSize) of your subscription or pay-as-you-go RDS instance. For more information, see Use network plans. |
DBS: Fast restoration of individual databases and tables within 5 minutes and emergency recovery
Fast restoration of individual databases and tables and fast restoration of individual databases and tables within 5 minutes
Category | Description |
Definition | The fast restoration feature for individual databases and tables for RDS instances that use local disks provides free and paid editions.
For more information, see Restore individual databases and tables. |
Fees charged by | DBS. |
Billing formula | Fee = Unit price of the CDM local disk storage × Amount of the CDM local disk storage × Duration Note For more information about the unit price of the CDM local disk storage, see Restore individual databases and tables. |
Billing method | Pay-as-you-go. |
Savings plans or resource plans | You can purchase a CDM sandbox storage plan to offset the fees that are generated for the CDM local disk storage (CapacitySandboxStorageSize) of your subscription or pay-as-you-go ApsaraDB RDS for MySQL instance with local disks. For more information, see DBS sandbox fees. |
Emergency recovery
Category | Description |
Definition | Fees for the following billable items when you use the emergency recovery feature for your ApsaraDB RDS for MySQL instance with local disks:
For more information, see Use the emergency recovery feature for an ApsaraDB RDS for MySQL instance. |
Fees charged by | DBS. |
Billing formula |
Note
|
Billing method | Pay-as-you-go. |
Savings plans or resource plans | You can purchase a CDM sandbox storage plan to offset the fees that are generated for the CDM local disk storage (CapacitySandboxStorageSize) of your subscription or pay-as-you-go ApsaraDB RDS for MySQL instance with local disks. For more information, see DBS sandbox fees. |
DAS: SQL Audit and Explorer
The fees for the SQL Audit and Explorer feature that is provided by DAS Enterprise Edition V3, DAS Enterprise Edition V2, or DAS Enterprise Edition V1 are charged by DAS.