ApsaraDB for OceanBase:Prerequisite operations

Enable SQL audit for an RDS for MySQL instance

1. Log on to ApsaraDB for RDS, and go to the Instance List page.

2. Specify the region at the top of the page and click the ID of the destination instance to go to the details page of the instance.

   Important

   To enable the SQL audit feature of an RDS for MySQL instance, the following prerequisites must be met:

   • The RDS for MySQL instance must be of the High Availability Edition or Enterprise Edition.

   • If you log on as a RAM user, you must have the read and write privileges on the RDS for MySQL instance, such as the AliyunRDSFullAccess privilege.

3. In the left-side navigation pane, click SQL Explorer, and choose Autonomy Service > SQL Explorer and Audit

4. For more information about how to enable the SQL Explorer feature, see SQL Explorer.

   • If the RDS for MySQL instance is located in any of the following regions, you can click Enable to enable the SQL Explorer and audit features: China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Shenzhen), China (Zhangjiakou), China (Hohhot), China (Chengdu), China (Guangzhou), China (Heyuan), China (Ulanqab), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), and Indonesia (Jakarta).

   • If the RDS for MySQL instance is located in a region other than the preceding regions, click Official Version to specify the retention period of the SQL audit logs, and click OK to enable the SQL Explorer feature.

Import traffic data to SLS

1. Log on to the SLS console and enable the SLS feature as prompted.

2. In the Import Data section, choose Cloud Products > RDS SQL Audit - Cloud Products to go to the RDS SQL Audit page.

3. At the Specify Logstore step, respectively select the created project and Logstore from the Project and Logstore drop-down lists. Then, click Next.

   You can also click Create Now next to the Project or Logstore drop-down list to create a new project or Logstore. For more information, see Create a project and a Logstore.

4. At the Specify Data Source step, complete the RAM authorization. Then, find the ID of the RDS for MySQL instance for which you have enabled the SQL Explorer feature, and enable file delivery.

5. Click Next.

Prerequisites

• You have enabled the SLS feature.

• You have created a database on the PolarDB-X instance.

Enable SQL audit for a PolarDB-X instance

The operations for PolarDB-X 1.0 and PolarDB-X 2.0 may vary. The following procedure takes PolarDB-X 2.0 as an example.

1. Log on to the PolarDB-X console.

2. On top of the page, select the region where the destination instance resides.

3. On the Instance List page, click the PolarDB-X 2.0 tab.

4. Find the destination instance and click the instance ID to go to the instance details page.

5. In the left-side navigation pane, choose Diagnostics and Optimization > SQL Audit and Analysis.

6. In the upper-right corner of the SQL Audit and Analysis page, enable Current Database SQL Audit Log Status.

   In the dialog box for configuring the log retention period, choose whether to import historical data as needed.

7. After the SQL audit feature is enabled, audit logs of the PolarDB-X databases in the same region are automatically written to the Logstores of the same log service. Then, you can export traffic files to an OSS bucket.