All Products
Search
Document Center

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

Last Updated:May 31, 2024

If you use the multi-account management feature to connect the database assets of a member to Data Security Center (DSC), the member pays the fees for reading data and storing audit logs in specific database services. This topic describes the fees that must be paid by members when the multi-account management feature is used.

Asset type

Data identification

Data audit

ApsaraDB RDS

Members do not pay the fee.

If the message in the following figure is displayed when you enable the cloud-native audit log collection feature for an ApsaraDB RDS instance of a member, the member must pay the fee. Take note of the following billing information:

  • Fee for the SQL Explorer and Audit feature: If the cloud-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 that 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.

image

If you enable the cloud-native audit log collection feature for an ApsaraDB RDS instance of a member and no fee-related notifications are sent, the member does not pay the fee.

PolarDB

Members do not pay the fee.

PolarDB-X

Members do not pay the fee.

If the cloud-native audit log collection feature is enabled for a PolarDB-X cluster, a project named drds-audit-Region ID-Member UID 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.

Members pay the data storage fee. The fee is included in the bills of Simple Log Service. For more information about the billing details, see Billing overview.

PolarDB-X 2.0

Members do not pay the fee.

You cannot enable the security audit feature for this type of assets of a member.

ApsaraDB for Redis

You cannot use the data insight feature for this type of assets of a member.

You cannot enable the security audit feature for this type of assets of a member.

ApsaraDB for MongoDB

Members do not pay the fee.

If you enable the security audit feature for ApsaraDB for MongoDB instances of a member in the DSC console, DSC automatically enables the audit log feature for the ApsaraDB for MongoDB instances. The member pays the fee for the audit log feature. The fee is included in the bills of ApsaraDB for MongoDB. For more information, see Enable the audit log feature.

ApsaraDB for MongoDB

Members do not pay the fee.

Members do not pay the fee.

Self-managed database

Members do not pay the fee.

You cannot enable the security audit feature for this type of assets of a member.

Object Storage Service (OSS)

DSC needs to send one or two GET requests to identify an OSS file. Members pay 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.

If the cloud-native audit log collection feature is enabled for an OSS bucket, a project named oss-log-Member UID-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. Members pay the fees. The fees are included in the bills of Simple Log Service. For more information, see Real-time log query.

Tablestore

If you read data in Tablestore of a member, the member pays the fee. The fee is included in the bills of Tablestore. For more information, see Billing overview.

If the cloud-native audit log collection feature is enabled for a Tablestore instance, a project named tablestore-log--Member UID-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.

Members pay 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 of a member, computing fees and data transmission fees are generated when you download data over the Internet. The member pays the fees. The fees are included in the bills of MaxCompute. For more information about billing, see Overview.

Members do not pay the fee.

AnalyticDB for MySQL

Members do not pay the fee.

Members do not pay the fee.

AnalyticDB for PostgreSQL

You cannot use the data insight feature for this type of assets of a member.

You cannot enable the security audit feature for this type of assets of a member.