RDS fees: Billable items - ApsaraDB RDS - Alibaba Cloud Documentation Center

The billable items for ApsaraDB RDS include RDS instance fees, value-added service fees, and fees for other related Alibaba Cloud services. This topic describes the definitions, billing formulas, and billing methods for these items.

RDS instances

Based on the billing method, RDS instances are available in the following types:

Subscription or pay-as-you-go RDS instances. When you purchase this type of RDS instance, you must specify the computing resource specifications 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 a specified range based on your workloads. The storage capacity of the serverless RDS instance automatically expands 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, disaster recovery instances, and DuckDB analytic 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	RDS Basic Edition, RDS High-availability Edition: RDS instance type fee = Unit price of the instance type for the instance × Duration MySQL, PostgreSQL Cluster Edition: RDS instance type fee = Unit price of the instance type for a single node × Number of nodes × Duration SQL Server Cluster Edition: RDS instance type fee = RDS primary instance type fee + RDS read-only instance type fee 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	RDS MySQL, PostgreSQL: RCU fee = Unit price of RCUs on a single node × Number of RCUs used by a single node × Number of nodes × Duration RDS SQL Server: RCU fee = Unit price of RCUs × Number of used RCUs × Duration 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, disaster recovery instances, and DuckDB analytic 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	Subscription or pay-as-you-go RDS instances on RDS Basic Edition and RDS High-availability Edition: Storage capacity fee = Unit price of the storage capacity for the instance × Storage used by the instance × Duration Subscription or pay-as-you-go RDS instances on RDS Cluster Edition: Storage capacity fee = Unit price of the storage capacity for a single node × Storage used by a single node × Number of nodes × Duration Serverless ApsaraDB RDS for MySQL instances and serverless ApsaraDB RDS for PostgreSQL instances: Storage capacity fee = Unit price of the storage capacity for a single node × Storage used by a single node × Number of nodes × Duration Serverless ApsaraDB RDS for SQL Server instances: Storage capacity fee = Unit price of the storage capacity for the instance × Storage used by the instance × Duration 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. Subscription instances: The duration indicates the subscription duration of the instances. Pay-as-you-go or serverless instances: The duration indicates the billable hours. The billing cycle is 1 hour.
Billing method	Subscription, pay-as-you-go, and serverless.

Value-added features of ApsaraDB RDS

ApsaraDB RDS provides paid, value-added features. When you enable or use a value-added feature, ApsaraDB RDS charges a fee for that feature.

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. When a disk instance automatically scales out its performance, it will be changed to other RDS specifications. The system will charge the RDS instance type fee based on the new specifications. The fee change rules are the same as those for changing configurations. For more information, see Change configurations. If your RDS instance uses local SSDs, the auto scaling feature automatically increases the number of CPU cores. A new billable item named Elastic Computing Resources (CPU+IOPS) with the code cpu_cores_flexible is generated.
Billing formula	Fee for the elastic computing resources of an RDS instance that uses local SSDs = Unit price of CPU cores × Number of increased CPU cores × Duration Fee for the new instance type of an RDS instance with cloud disks = Unit price of the instance type × Duration Note For more information about the unit price of CPU cores for the auto scaling feature of an RDS instance that uses local SSDs, see Configure auto scaling. The unit price of the instance type for an RDS instance that uses cloud disks is the same as that displayed on the ApsaraDB RDS buy page.
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 and Billing of I/O burst for ApsaraDB RDS for MySQL, 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 instance.
Billable product	Relational database.
Billing formula	Backup storage fee = (Total storage of backup files - Free quota) × Unit price of backup storage × Duration Note Free quota for backup storage : The free quota for RDS instances that use cloud disks is 200% of the storage capacity. The free quota for RDS instances that use local SSDs is 50% of the storage capacity. For more information about the unit price of backup storage, see , Backup fees for ApsaraDB RDS for MySQL, Backup fees for ApsaraDB RDS for PostgreSQL, Backup fees for ApsaraDB RDS for SQL Server, and Backup fees for ApsaraDB RDS for MariaDB. For information about how to reduce backup costs and size, see , Reduce RDS MySQL backup costs, Reduce RDS SQL Server backup costs, Reduce RDS PostgreSQL backup costs, and Increase the free quota of MariaDB by scaling out storage space.
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.
Billable 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.

Note

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 the 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 from the original instance to restore data 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, and Restore MariaDB data.

Regular database and table restoration

When you restore specific databases or tables to a new instance from a backup set or to a specific 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, and 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 billable item is named SQL Audit (sql_collected). For more information, see , RDS MySQL SQL Explorer and Audit, RDS SQL Server SQL Explorer and Audit, and RDS PostgreSQL SQL Explorer and Audit.
Billable 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, and SQL Server SQL Explorer billing.
Billing method	Pay-as-you-go.

Note

For the SQL Explorer and Audit feature provided by DAS Enterprise Edition V3, V2, and 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 billable 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, and 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, and PostgreSQL dedicated proxy pricing.
Billing method	Pay-as-you-go.

Public endpoint traffic

If you request a public endpoint for your RDS instance, connecting to the instance through this endpoint consumes internet traffic. Currently, you are not charged for inbound or outbound internet traffic consumed when connecting to your RDS instance through 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, and 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 fees are generated.

Data Disaster Recovery: cross-region backup, backup storage for deleted instances, and download of backup files

Cross-region backup

Category	Description
Definition	Fees for cross-region backups include charges for consumed traffic and the storage of backup files. The bill is based on the following billable items: Geo-Redundant Storage (DdrOssStorageSize) and Cross-Region Backup Network Traffic (NetworkOutDuplicationSize). ApsaraDB RDS for MySQL with local SSDs, ApsaraDB RDS for PostgreSQL, and ApsaraDB RDS for SQL Server: Geo-redundancy storage (DdrOssStorageSize) and Cross-region backup network traffic (NetworkOutDuplicationSize). ApsaraDB RDS for MySQL with standard SSDs: Database backup storage (BackupStorageSize) and Cross-region backup network traffic (NetworkOutDuplicationSize). For more information, see Cross-region backup for MySQL, Cross-region backup for PostgreSQL, and Cross-region backup for SQL Server.
Billable product	Geo-redundancy storage (DdrOssStorageSize): relational database. Database backup storage (BackupStorageSize): Database Backup. Cross-region backup network traffic (NetworkOutDuplicationSize): Database Backup.
Billing formula	Fee for cross-region backup storage = Unit price of cross-region backup storage × Size of cross-region backup files × Duration Fee for instance backup storage = Unit price of instance backup storage × Size of instance backup files × Duration Fee for traffic that is consumed by cross-region backups = Unit price of traffic × Amount of traffic that is consumed Note For information about geo-redundancy storage pricing, see Cross-region backup for MySQL with local SSDs, Cross-region backup for PostgreSQL, and Cross-region backup for SQL Server. For more information about database backup storage pricing, see Cross-region backup for MySQL with standard SSDs. For the unit price of traffic, see Network fees.
Billing method	Pay-as-you-go.
Can savings plans or resource plans be used for deduction?	A DBS network plan can be used to offset the cross-region backup network traffic (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: ApsaraDB RDS for MySQL with local SSDs: Standard storage (StandardStorageSize) ApsaraDB RDS for MySQL with standard SSDs: Database backup storage (BackupStorageSize) For more information, see Configure the backup retention policy after instance release.
Billable 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, and Download the backup files of an ApsaraDB RDS for PostgreSQL instance.
Billable product	Database Backup.
Billing formula	Backup compute data volume fee = Unit price × Backup compute data volume Fee for outbound Internet traffic = Unit price × (Amount of traffic - Free quota) 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) and emergency recovery

Fast restoration of individual databases and tables and fast restoration of individual databases and tables within 5 minutes

Important

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: 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: After you enable and use the fast restoration feature for individual databases and tables of this edition, you are charged based on the data volume. The billable item is CDM local disk storage (CapacitySandboxStorageSize).
Billable 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: CDM local disk storage (CapacitySandboxStorageSize): After you enable the Data Disaster Recovery sandbox feature, each database instance corresponds to a sandbox storage. The system automatically synchronizes the data of the database instance to the sandbox storage and generates sandbox snapshots for the data. Data Disaster Recovery charges sandbox storage fees based on the data volume in the sandbox storage. CDM sandbox instance type (SandboxDatabaseSpec): After you restore data to a temporary sandbox instance, Data Disaster Recovery charges temporary sandbox instance fees based on the instance type and usage duration of the temporary sandbox instance. The fees are charged on an hourly basis. If you do not create a temporary sandbox instance for data restoration, you are not charged for the temporary sandbox instance. For more information, see Use the emergency recovery feature for an ApsaraDB RDS for MySQL instance.
Billable product	Database Backup.
Billing formula	Fee for the CDM local disk storage = Unit price of the CDM local disk storage × Duration × Amount of the CDM local disk storage Fee for the CDM sandbox instance type = Unit price of the sandbox instance type × Duration Note For the unit price of the CDM local disk storage, see Sandbox storage fees. For the unit price of the sandbox instance type, see Temporary sandbox instance fees.
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 for DAS Enterprise Edition V3, V2, and V1 belong to the Database Autonomy Service product.

Billing details

Enterprise Edition V3

Important

Enterprise Edition V3 breaks down billing items by the features used, making billing more flexible and significantly reducing costs.

After you enable DAS Enterprise Edition V3, log traffic fees are charged by default. Other fees are charged based on the usage of the corresponding features.
Free migration from Enterprise Edition V1 and V2 to Enterprise Edition V3 is supported. Before the migration is complete, billing will follow the current version's model. After completion, billing will follow the target version's model. For details, see How do I migrate data between different versions of DAS Enterprise Edition?

Billing of DAS Enterprise Edition V3

Billing examples

Depending on the service scenario and selected features, here are two use cases:

Operations and Maintenance (O&M)

This scenario supports full SQL log recording and cluster analysis, which can be used to quickly query, locate, and analyze problematic SQL, handle emergency responses for affected services, and perform subsequent in-depth optimization. For feature details, see SQL Explorer and Audit.

Optional features for this scenario:

Assume your instance has 10GB of write traffic per day, and you set SQL Log Storage to 30 days, with hot storage for Log Index set to 7 days.

Suppose that 10 GB of data is written to your instance per day, and you set SQL Log Storage to 30 days and the hot storage for Log Index to 7 days.

Note

The Storage Duration Of SQL Logs is your total storage time, which defaults to cold storage. For example, in the above scenario, after enabling log indexing, new logs will first be stored in hot storage for 7 days. After 7 days, the remaining 23 days of logs will be moved to cold storage.

Feature	Billable item	Daily unit price (Alibaba Cloud public cloud in the Chinese mainland)	Daily usage	Daily cost
SQL log	Log traffic (DataIngestion)	USD 0.24 per GB	10GB	USD 2.4
SQL log	Cold storage (SqlInsightColdDataSize)	USD 0.0005 per GB-day	After logs are transferred to cold storage 10 GB on the first day 20 GB on the second day ... 230 GB on the 23rd day	0 (Logs can be stored in cold storage free of charge for 30 days.)
Log indexing	Log indexing (RealTimeSearchAnalytics)	USD 0.24 per GB	10GB	USD 2.4
Log indexing	Hot storage (SqlInsightHotDataSize)	USD 0.01 per GB-day	After this feature is enabled, the daily usage is 10 GB on the first day, 20 GB on the second day, ... and 70 GB on the seventh day. (Data is dumped to cold storage after seven days.)	Stored for 7 days or longer 10 × (7 - 1) × 0.01 = 0.6 yuan (Logs are stored in hot storage free of charge on the first day)
SQL Explorer	SQL Explorer (InsightAnalysis)	USD 0.08 per GB	10GB	USD 0.8

Audit and compliance

This scenario supports bank-level security and compliance capabilities, as well as requirements for regulations in the Chinese Mainland. It provides long-term, transparent monitoring of database behavior with real-time alerts. For data security, it offers comprehensive detection of abnormal access, vulnerability attacks, data leakage, and baseline deviations to prevent impact on database services. For feature details, see Security audit (new version).

Optional features for this scenario:

Assume your instance has 10GB of write traffic per day, and you set SQL Log Storage to 180 days to meet the Chinese mainland compliance regulations.

Note

The Storage Duration Of SQL Logs is your total storage time, which defaults to cold storage.
To meet compliance regulations in China, the cold storage period must not be less than 180 days.

Feature	Billable item	Daily unit price (Alibaba Cloud public cloud in the Chinese mainland)	Daily usage	Daily fee
SQL log	Log traffic (DataIngestion)	USD 0.24 per GB	10GB	USD 2.4
SQL log	Cold storage (SqlInsightColdDataSize)	USD 0.0005 per GB-day	10 GB on the first day 20 GB on the second day ... and 1,800 GB on the 180th day	The daily fee is calculated by using the following formula: 10 × (180 - 30) × 0.003 = 4.5 Note Cold storage fees for the first 30 days have been waived. The fee of 4.5 is for the 150 days of storage after the 30-day free period.
Security audit	Security audit (SecurityAudit)	USD 0.48 per GB	10GB	USD 4.8

Alibaba Cloud public cloud

Billable item	Billing method	Unit price in the Chinese mainland	Unit price in China (Hong Kong) and regions outside China	Description
Log traffic (DataIngestion)	Pay-as-you-go	USD 0.04 per GB	USD 0.06 per GB	Default fee. You are charged for the traffic consumed for collecting, transferring, and writing logs to storage on a pay-as-you-go basis.
Log indexing (RealTimeSearchAnalytics)		USD 0.04 per GB	USD 0.06 per GB	You are charged fees after you enable the log indexing feature. Log indexes are stored as hot data. DAS dynamically adjusts and optimizes indexes to ensure rapid data retrieval. Log indexes can be stored in hot storage free of charge for one day after they are written to hot storage;
SQL Explorer (InsightAnalysis)		USD 0.0134 per GB	USD 0.02 per GB	You are charged for automatic data aggregation and analysis by using the SQL Explorer feature based on the log volume.
Hot storage (SqlInsightHotDataSize)		USD 0.00167 per GB-day	USD 0.0025 per GB-day	You are charged for hot storage based on the log volume and storage duration. Logs can be stored in hot storage for up to seven days. Logs can be stored in hot storage free of charge for one day after they are written to hot storage. If cold storage is enabled, the logs are automatically transferred to cold storage free of charge after the hot storage period expires.
Cold storage (SqlInsightColdDataSize)		USD 0.0005 per GB-day	USD 0.00075 per GB-day	Default fee. You are charged for cold storage based on the log volume and storage duration. If hot storage is not enabled, logs are stored only in cold storage, and you are not charged for the first 30 days. If hot storage is enabled: New logs are first stored in hot storage (free on the first day), and you are charged for hot storage during the storage period (`hot storage duration - first day`). After the hot storage period expires, logs are automatically transferred to cold storage for free, and you are not charged during the cold storage period (`30 days - hot storage duration`).
Cold query (SqlScanDataSize)		USD 0.0025 per GB	USD 0.00375 per GB	You are charged for querying logs in cold storage offline based on the log volume.
Download		USD 0.067 per GB	USD 0.1 per GB	You can export and dump logs free of charge.
Security audit (SecurityAudit)		USD 0.08 per GB	USD 0.12 per GB	Charged based on log volume when using the new Security Audit feature.

Enterprise Edition V2

Alibaba Cloud public cloud

Billable item	Billing method	Unit price in the Chinese mainland, Malaysia (Kuala Lumpur), and Indonesia (Jakarta)	Unit price in China (Hong Kong) and Singapore	Description
Hot storage (SqlInsightHotDataSize)	Pay-as-you-go	USD 0.00145 per GB-hour	USD 0.002175 per GB-hour	Data is stored in high-performance storage devices, providing query acceleration and SQL aggregation information capabilities. The SQL Explorer and Audit data generated in the previous seven days is stored in hot storage.
Cold storage (SqlInsightColdDataSize)		USD 0.00018 per GB-hour	USD 0.00027 per GB-hour	Data is stored on low-cost storage devices to reduce usage costs. SQL Explorer and audit data older than seven days is automatically transferred from hot storage to cold storage. The response time of a cold data query is longer than that of a hot data query.
Data query fee (SqlScanDataSize)		USD 0.029 per GB	USD 0.0435 per GB	You are charged for querying data that is stored in cold storage on a pay-as-you-go basis.
Security audit (SecurityAudit)		USD 0.08 per GB	USD 0.12 per GB	Optional. You can enable or disable the feature separately. You are charged for the new version of the security audit feature based on the log volume.

Enterprise Edition V1 and DAS Enterprise Edition V0

Important

You are charged subscription fees only for DAS Enterprise Edition V1.

Billable item	Billing method	Pricing	Description
Subscription fee	Subscription	USD 6.2 per instance-month	You are charged based on the specified quota of DAS Enterprise Edition V1, which indicates the total number of database instances for which you can enable DAS Enterprise Edition V1. For example, if your account has a quota of 3 for DAS Enterprise Edition V1, and you have enabled DAS Enterprise Edition for 1 database instance, the subscription fee for your account is `USD 6.2 per month × 3 = USD 18.6 per month`. Important You are charged subscription fees only for DAS Enterprise Edition V1.
Storage fees for SQL Explorer data (sql_storage_used)	Pay-as-you-go	Free quota: 5 GB of free storage. Important Free storage is provided only for DAS Enterprise Edition V1. Unit price for excess storage: USD 0.0013 per GB-hour.	Applicable regions: regions in the Chinese mainland, Malaysia (Kuala Lumpur), and Indonesia (Jakarta).
Storage fees for SQL Explorer data (sql_storage_used)		Free quota: 3 GB of free storage. Important Free storage is provided only for DAS Enterprise Edition V1. Unit price for excess storage: USD 0.0019 per GB-hour.	Applicable regions: China (Hong Kong) and Singapore.
Security audit (SecurityAudit)		Chinese mainland: USD 0.08/GB. China (Hong Kong) and regions outside China: USD 0.12/GB.	Optional. You can enable or disable the feature separately. You are charged for the new version of the security audit feature based on the log volume.

Economy edition

Billable item	Billing method	Pricing	Description
Basic plan	Subscription	USD 15 per month	Up to 10 database instances can be connected.
Medium plan		USD 37.5 per month	Up to 50 database instances can be connected to DAS Economy Edition.
Advanced plan		USD 75 per month	The number of database instances that can be connected is not limited.

Basic Edition

You are not charged for DAS Basic Edition.

Security center

Billable item	Billing object	Specification	Pricing	Description
Sensitive data detection (DCG_Amount)	Number of database tables (X)	0 ≤ Z ≤ 50,000 sheets	USD 80 per month	When scanning tables in a detection job, each table scanned consumes 1 quota until all quotas are used up. Unused quotas are not carried over to the next month. Tiered pricing applies; the larger the volume, the lower the unit price. Note Sensitive data detection provides you with a free quota of 100 tables to enjoy a secure experience.
		60,000 ≤ Z ≤ 100,000	USD 60 per month
		110,000 ≤ Z ≤ 500,000 sheets	USD 40 per month
		5.1 million sheets <= Z <= 99,999,999,999,990 million sheets	USD 20 per month
Column encryption (CLE_Amount)	Number of database columns (Y)	5	USD 498 per month	To encrypt columns that contain sensitive data after detection, 1 quota is consumed when a column is encrypted, and this quota is recovered when encryption is canceled. Tiered pricing, the larger the volume, the lower the unit price.
		10	USD 598 per month
		15	USD 699 per month
		20	USD 798 per month
		25	USD 898 per month
		30	USD 996 per month
		35	USD 1,092 per month
		40	USD 1,198 per month
		45	USD 1,287 per month
		50	USD 1,398 per month
		50 < N <=100	USD 25 per month
		100 < N <=200	USD 20 per month
		200 < N <=300	USD 15 per month
		300 < N <=400	USD 12 per month
		400 < N <=500	USD 11 per month
		500 < N <=600	USD 10 per month
		600 < N <=700	USD 9 per month
		700 < N <=800	USD 8 per month
		800 < N <=900	USD 7 per month
		900 < N <=1000	USD 6 per month
		1000 < N <=9999999999999	USD 5 per month