Updated on 2026-07-13 GMT+08:00

Downloading SQL Audit Logs

Scenarios

If you enable SQL audit, the system records all SQL operations and saves them in logs every half an hour or when they reach 100 MB in size. You can download the logs to view details. Audit logs record data with precision up to 1 second. By default, SQL audit is disabled. Enabling this function may affect database performance.

Constraints

You are advised to download no more than six audit log files at a time. Too many files can fail to be downloaded completely due to the limit on the number of concurrent requests of the browser.

Procedure

  1. Log in to the RDS console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, click the target instance name.
  4. In the navigation pane on the left, choose Logs. On the displayed page, click the SQL Audit Logs tab.
  5. On the displayed page, select a time range in the upper right corner, select SQL audit logs to be downloaded in the list, and click Download above the list to download SQL audit logs in batches.

    Alternatively, select an audit log and click Download in the Operation column to download an individual SQL audit log.

  6. Check the SQL audit log content. For field descriptions, see Table 1.

    Figure 1 RDS for MySQL audit logs
    Table 1 Audit log field description

    Parameter

    Description

    record_id

    ID of a record, which is the unique global ID of each SQL statement recorded in the audit log.

    connection_id

    ID of the session executed for the record, which is the same as the ID in the show processlist command output.

    connection_status

    Session status, which is usually the returned error code of a statement. If a statement is successfully executed, the value 0 is returned.

    name

    Name of the record type. Generally, DML and DDL operations are QUERY, connection and disconnection operations are CONNECT and QUIT, respectively.

    timestamp

    UTC time when the SQL statement is executed.

    command_class

    SQL command type. The value is the parsed SQL type, for example, select or update. (This field does not exist if the connection is disconnected.)

    sqltext

    Executed SQL statement content. (This field does not exist if the connection is disconnected.)

    user

    Login account.

    host

    Login host. The value is localhost for local login and is empty for remote login.

    external_user

    External username.

    ip

    IP address of the remotely-connected client. For local connection, the field is empty.

    default_db

    Default database on which SQL statements are executed.

    trx_id

    ID of the transaction in which the SQL statement is executed.

    execute_time

    Time required for executing the SQL statement, in milliseconds.

FAQ

Q: Why is the default_db field in SQL audit logs displayed as A when I connect to database A and insert data into database B?

A: The default_db field in SQL audit logs displays the current database, which is irrelevant to the SQL statement for inserting data. For example, if you execute use db1; or a SQL statement for connecting to database db1, the value of default_db is db1. If no database is specified, default_db is empty.