Billing for related products - Data Security Center - Alibaba Cloud Documentation Center

When you connect data assets to Data Security Center (DSC), the account that owns the asset is charged for data reads and audit log storage. These charges apply to assets that belong to your main Alibaba Cloud account and any member accounts managed by DSC. This topic describes the fees for each type of data asset.

The billing logic is the same for both main Alibaba Cloud accounts and member accounts. The following table describes the billing details.

Asset Type	Data identification	Data audit
RDS	The account that owns the asset does not incur additional fees.	As of April 17, 2024, no additional fees are charged for enabling native log collection for RDS instances in the account. If native log collection was enabled before April 17, 2024, the account that owns the asset must pay for SQL Explorer and Audit and for log storage. You can disable the native log collection mode for the asset and then re-enable it. After you re-enable it, the account that owns the asset no longer incurs additional fees. Note Before April 17, 2024: Fees for asset-owning accounts: SQL Explorer and Audit: After native log collection is enabled for an RDS database, DSC automatically enables the SQL Explorer feature for the database. The account that owns the asset is charged for SQL Explorer. The fees are billed and collected by RDS. For more information, see Billable items. Log storage fees: The SQL Explorer feature creates a Simple Log Service (SLS) Logstore to store the raw logs from the RDS SQL Explorer service. By default, data in this Logstore is stored for 3 days. The account that owns the asset is charged for this storage. The fees are billed and collected by SLS. For more information, see Billing overview.
PolarDB	The account that owns the asset does not incur additional fees.	As of April 17, 2024, no additional fees are charged for enabling native log collection for PolarDB instances in the account. If native log collection was enabled before April 17, 2024, the account that owns the asset must pay for SQL Explorer and Audit and for log storage. You can disable the native log collection mode for the asset and then re-enable it. After you re-enable it, the account that owns the asset no longer incurs additional fees.
PolarDB-X	The account that owns the asset does not incur additional fees.	After you enable native log collection for a PolarDB-X asset, a project named `drds-audit-Region ID-UID of the account that owns the asset` is created in the SLS console. The Logstore in this project is named `drds-audit-log`. By default, data in this Logstore is stored for 45 days. The account that owns the asset is charged for data storage in this Logstore. The fees are collected by SLS. For more information, see Billing overview.
PolarDB-X 2.0	The account that owns the asset does not incur additional fees.	The security audit feature is not supported for this asset type. The account that owns the asset does not incur additional fees.
Redis	The data identification feature is not supported for this asset type. The account that owns the asset does not incur additional fees.	The security audit feature is not supported for this asset type. The account that owns the asset does not incur additional fees.
MongoDB	The account that owns the asset does not incur additional fees.	After you enable auditing for a MongoDB asset in the DSC console, DSC automatically enables the audit log feature for the MongoDB instance. The account that owns the asset is charged for the MongoDB audit log feature. These fees are collected by MongoDB. For more information, see Enable the audit log feature.
OceanBase	The account that owns the asset does not incur additional fees.	The account that owns the asset does not incur additional fees.
Self-managed database	The account that owns the asset does not incur additional fees.	The security audit feature is not supported for this asset type. The account that owns the asset does not incur additional fees.
OSS	To identify an OSS file, DSC sends one or two GET requests. The cost of these requests is charged to the account that owns the asset based on its billing method. For example, if an account uses the pay-as-you-go billing method, these costs appear in the pay-as-you-go orders for OSS for that account. For more information, see Billing overview. If you enable synchronization of sensitive data tags to OSS in DSC, OSS charges request fees based on the number of API calls. For example, synchronizing tags to OSS involves Put requests to add or modify tags, and charges are based on the number of Put requests. For more information, see Request fees.	After you enable native log collection for an OSS asset, a project named `oss-log-UID of the account that owns the asset-Region ID` is created in the SLS console. The Logstore in this project is named `oss-log-store`. By default, data in this Logstore is stored for 7 days. No fees are incurred if the data in the Logstore is stored for no more than 7 days and does not exceed 900 GB. Storage fees are incurred if the data is stored for more than 7 days or exceeds 900 GB. The account that owns the asset is charged for this storage. The fees are collected by SLS. For more information, see Billing.
Tablestore	Reading data from Tablestore incurs fees. These fees are charged to the account that owns the asset and are collected by Tablestore. For more information, see Billing overview.	After you enable native log collection for a Tablestore asset, a project named `tablestore-log-UID of the account that owns the asset-Region ID` is created in the SLS console. The Logstore in this project is named `tablestore-auditlog-store`. By default, data in this Logstore is stored for 7 days. The account that owns the asset is charged for data storage in this Logstore. The fees are collected by SLS. For more information, see Billing overview.
MaxCompute	Reading data from a MaxCompute project incurs computing fees. Data transmission fees are also incurred if data is downloaded over the public network. These fees are charged to the account that owns the asset and are collected by MaxCompute. For more information, see Billable items and billing methods.	The account that owns the asset does not incur additional fees.
AnalyticDB-MYSQL	The account that owns the asset does not incur additional fees.	The account that owns the asset does not incur additional fees.
AnalyticDB-PG	The data identification feature is not supported for this asset type. The account that owns the asset does not incur additional fees.	The security audit feature is not supported for this asset type. The account that owns the asset does not incur additional fees.

References

DSC uses a subscription (prepaid) billing method. For more information, see Billing.