All Products
Search
Document Center

Data Security Center:Additional fees for data assets connected to DSC

Last Updated:Nov 28, 2024

If you connect the data assets within your Alibaba Cloud account to Data Security Center (DSC) and use the multi-account management feature to connect the data assets of a member to DSC, the Alibaba Cloud account and the member to which data assets belong must pay the fees for reading data and storing audit logs in specific data assets. This topic describes the additional fees that must be paid by the Alibaba Cloud account and members to which data assets belong.

The billing logic for the additional fees is the same regardless of whether an Alibaba Cloud account or a member is used. The following table describes the details.

Asset type

Data identification

Data audit

RDS

The account to which data assets belong does not need to pay additional fees.

Starting April 17, 2024, the native audit log collection feature is enabled for ApsaraDB RDS instances within the account. The account to which data assets belong does not need to pay additional fees.

If the native audit log collection feature is enabled before April 17, 2024, the Alibaba Cloud account and members to which data assets belong must pay the fee for using the SQL Explorer and Audit feature and pay the log storage fee. You must disable the native audit log collection feature for data assets and re-enable the feature. After you enable the feature, the Alibaba Cloud account and members to which data assets belong do not need to pay additional fees.

Note

Take note of the following billing information for the account for which the native audit log collection feature is enabled before April 17, 2024:

  • Fee for the SQL Explorer and Audit feature: If the native audit log collection feature is enabled for an ApsaraDB RDS instance, DSC automatically enables the SQL Explorer and Audit feature for the instance. Members pay the fee for using the SQL Explorer and Audit feature. The fee is included in the bills of ApsaraDB RDS. For more information, see Billable items.

  • Log storage fee: The SQL Explorer and Audit feature creates a Simple Log Service Logstore that is used to store the logs. The logs are generated by the feature. By default, the data in the Logstore is stored for three days. Members pay the log storage fee. The fee is included in the bills of Simple Log Service. For more information, see Billing overview.

PolarDB

The account to which data assets belong does not need to pay additional fees.

Starting April 17, 2024, the native audit log collection feature is enabled for PolarDB instances within the account. The account to which data assets belong does not need to pay additional fees.

If the native audit log collection feature is enabled before April 17, 2024, the Alibaba Cloud account and members to which data assets belong must pay the fee for using the SQL Explorer and Audit feature and pay the log storage fee. You must disable the native audit log collection feature for data assets and re-enable the feature. After you enable the feature, the Alibaba Cloud account and members to which data assets belong do not need to pay additional fees.

PolarDB-X

The account to which data assets belong does not need to pay additional fees.

If the native audit log collection feature is enabled for a PolarDB-X cluster, a project named drds-audit-Region ID-UID of the account to which data assets belong is created in the Simple Log Service console. A Logstore named drds-audit-log is created in the project. By default, the data in the Logstore is stored for 45 days.

The account to which data assets belong pays the data storage fee. The fee is included in the bills of Simple Log Service. For more information, see Billing overview.

PolarDB-X 2.0

The account to which data assets belong does not need to pay additional fees.

You cannot enable the security audit feature for this type of data assets. The account to which data assets belong does not need to pay additional fees.

Redis

You cannot use the data insight feature for this type of data assets. The account to which data assets belong does not need to pay additional fees.

You cannot enable the security audit feature for this type of data assets. The account to which data assets belong does not need to pay additional fees.

MongoDB

The account to which data assets belong does not need to pay additional fees.

If you enable the security audit feature for ApsaraDB for MongoDB instances in the DSC console, DSC automatically enables the audit log feature for the ApsaraDB for MongoDB instances. The account to which data assets belong pays the fee for using the audit log feature. The fee is included in the bills of ApsaraDB for MongoDB. For more information, see Enable the audit log feature.

OceanBase

The account to which data assets belong does not need to pay additional fees.

The account to which data assets belong does not need to pay additional fees.

Self-managed database

The account to which data assets belong does not need to pay additional fees.

You cannot enable the security audit feature for this type of data assets. The account to which data assets belong does not need to pay additional fees.

OSS

  • DSC needs to send one or two GET requests to identify an Object Storage Service (OSS) bucket. The account to which data assets belong pays the fee based on the billing method that is used. For example, if a member uses the pay-as-you-go billing method, the fee is included in the pay-as-you-go OSS bills of the member. For more information, see Billing overview.

  • You must enable the OSS synchronization feature in DSC. All operations performed in OSS are implemented by calling OSS API operations. Fees are calculated based on the number of API requests. If you synchronize tags to OSS, the process involves adding or modifying tags by using PUT requests. Fees are calculated based on the number of PUT requests. For more information, see API operation calling fees.

If the native audit log collection feature is enabled for an OSS bucket, a project named oss-log-UID of the account to which data assets belong-Region ID is created in the Simple Log Service console. A Logstore named oss-log-store is created in the project. By default, the data in the Logstore is stored for 7 days.

  • If the data in the Logstore is stored for no more than 7 days and does not exceed 900 GB in size, no fees are generated.

  • If the data in the Logstore is stored for more than 7 days or exceeds 900 GB in size, storage fees are generated. The account to which data assets belong pays the fees. The fees are included in the bills of Simple Log Service. For more information, see Billing overview.

Tablestore

If you read data in Tablestore, fees are generated for data reads. The account to which data assets belong pays the fees. The fees are included in the bills of Tablestore. For more information, see Billing overview.

If the native audit log collection feature is enabled for a Tablestore instance, a project named tablestore-log--UID of the account to which data assets belong-Region ID is created in the Simple Log Service console. A Logstore named tablestore-auditlog-store is created in the project. By default, the data in the Logstore is stored for 7 days.

The account to which data assets belong pays the data storage fee. The fee is included in the bills of Simple Log Service. For more information, see Billing overview.

MaxCompute

If you read data in a MaxCompute project, computing fees and data transmission fees are generated for data downloads over the Internet. The account to which data assets belong pays the fees. The fees are included in the bills of MaxCompute. For more information about billing, see Overview.

The account to which data assets belong does not need to pay additional fees.

ADB-MYSQL

The account to which data assets belong does not need to pay additional fees.

The account to which data assets belong does not need to pay additional fees.

ADB-PG

You cannot use the data insight feature for this type of data assets. The account to which data assets belong does not need to pay additional fees.

You cannot enable the security audit feature for this type of data assets. The account to which data assets belong does not need to pay additional fees.

References

DSC uses the subscription billing method. For more information, see Billing overview.