View DB Cluster

Available in VPC

While operating the DB cluster, situations where you need to change the options related to the DB set upon creation may occur. Cloud DB Serverless supports changes of related settings simply through a few clicks, even for clusters that have already been created.

To manage DB Cluster that has been created and is in operation:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > All Services > Database > Cloud DB Serverless.
2. Click the DB Cluster menu.
3. In the DB cluster list, click the cluster you want to manage, and then click [DB Management].
4. Click the necessary management tab on the DB Cluster details menu.

Manage Database

You can add a DB to the selected DB cluster or delete a DB you created. Up to 1,000 DB can be added or viewed, and the addition or deletion tasks can be performed for up to 10 DB at a time.

To perform a DB addition or creation task, click [Add Database] to add database, or click [Delete] in the same row as the created DB to delete the DB.

Manage DB Config

Various settings can be changed while the DB cluster is in the Running state. The changed settings are applied to the entire DB Cluster, and some config variables are applied after an automatic restart of the DB Cluster upon the change. To change:

1. On the DB Config Management tab, view or enter the required information.
   • Config Name: Name of the config variable
   • Config Value: Variable value
2. Click [Add].
   • When editing the added config variable, click [Edit].
   • When deleting the added config variable (setting it to default): Click [Delete].
3. Click [Save].
4. View the status with the modified config from the DB Cluster list.
   • Configuring: Status in which the DB Cluster is being configured based on user input data.
   • Running: Status in which the DB cluster's configuration has been completed with the information you entered.

Config variable list

The following are descriptions of config variables:

Manage DB user

When creating a DB cluster, the ID and password for the account to access are created by default. However, while operating the DB cluster, you may need to add users or reset the passwords of existing user accounts. You may also need to delete user accounts. Cloud DB Serverless provides an DB User management feature that enables you to conveniently add, edit, and delete user accounts that use the DB cluster. The results of the user account change through the DB User management feature are applied to the entire DB Service. Up to 1,000 user accounts can be added.

To add or delete user accounts or change the password of the existing admin account:

1. On the Manage DB User tab, perform the required tasks for the user account.

   • Add user account: Enter the information for USER_ID, DB permissions, and password, and then click [Add DB User]
     • All DB permissions include the execute permission of the system DB.
     • The CRUD permission includes the READ permission, and the DDL permission includes the READ and CRUD permissions.
     • View procedure can be performed by any account regardless of permissions. For more information, see Official MySQL document (English).
   • Delete user account: Click [Delete] in the same row as the user account to be deleted.
   • Edit user account password: Click [Edit] in the same row as the user account to be edited, and click [Save] after editing.

2. Click [Save].

3. Check the status of a DB cluster for which you've set users from the list in the DB cluster interface.

   • Configuring: Status in which the DB Cluster is being configured based on user input data.
   • Running: Status in which the DB cluster's configuration has been completed with the information you entered.

Manage Audit settings

You can make a log file that records connection activity and query execution history within a DB cluster for auditing purposes. Audit settings management: You can configure whether to enable Audit Logs, the scope of events to record, and the log format. Any changes you make are applied to the entire DB cluster. To change:

1. On the Manage Audit settings tab, see the following to change the settings:
   • Audit Log usage: Select whether to enable Audit Logs (default: Disabled).
   • Audit Policy: Define the events to be recorded in the Audit Log (default: ALL).
     • LOGINS: Records only the login and logout of DB accounts accessing the DB.
     • QUERIES: Logs queries, including DDL statements, executed in the DB.
     • ALL: LOGINS + QUERIES
   • Log Format: Select the format used to record Audit Log files (JSON or XML, default: JSON).
2. Click [Save].
3. If a restart notification popup appears, review the information and click [OK].
4. In the DB Cluster interface, check the Status of the target for which Audit is configured.
   • Configuring: Status in which the DB Cluster is being configured based on user input data.
   • Running: Status in which the DB cluster's configuration has been completed with the information you entered.

• Whether a restart is required when the setting is changed.

• List of audit log fields

The information recorded in the Audit Log is the same, but the field names and structure differ depending on the Log Format (JSON or XML).

• JSON: Recorded as an array of records. Each record consists of common fields and an event-specific data object.

• XML: Recorded as child elements of <AUDIT_RECORD>, and all items use uppercase element names.

  • Field mapping table

Client information (connection_attributes) records _pid, _platform, _os, _client_name, _client_version,
program_name, os_user, etc. Items may vary depending on the connector used for connection.

* Event type mapping table

* Record example

JSON

{
  "timestamp": "2026-07-31 17:23:37",
  "id": 62,
  "class": "connection",
  "event": "connect",
  "connection_id": 10,
  "account": { "user": "app_user", "host": "" },
  "login": { "user": "app_user", "os": "", "ip": "127.0.0.1", "proxy": "" },
  "connection_data": { "connection_type": "tcp/ip", "status": 0, "db": "fmtdb" }
}

XML

<AUDIT_RECORD>
  <NAME>Connect</NAME>
  <RECORD_ID>5_2026-07-31T17:23:37</RECORD_ID>
  <TIMESTAMP>2026-07-31T17:23:37</TIMESTAMP>
  <COMMAND_CLASS>Connection</COMMAND_CLASS>
  <CONNECTION_ID>10</CONNECTION_ID>
  <HOST>localhost</HOST>
  <IP>127.0.0.1</IP>
  <USER>app_user</USER>
  <OS_LOGIN></OS_LOGIN>
  <PRIV_USER>app_user</PRIV_USER>
  <PROXY_USER></PROXY_USER>
  <DB>fmtdb</DB>
  <STATUS>0</STATUS>
  <CONNECTION_TYPE>TCP/IP</CONNECTION_TYPE>
</AUDIT_RECORD>

If a login attempt fails, the error number is recorded in the status result value of the connection event (JSON connection/connect, XML Connect).
For example, if the password is incorrect, 1045 is recorded.

DB Log setting management

You can change the log rotation and storage settings for the DB cluster you created. Changed settings are applied to the entire DB Cluster. To change:

1. On the Manage DB Log settings tab, see the following to change the settings:
   • Log: Check log name (select from Error Log, Slow Query Log, or General Log).
   • Log rotate: Set the log rotation to be performed daily or by size
     • When selecting by size, choose between 10 MB and 100 MB
   • Log file: Number of log files to be stored (select between 3 and 7)
2. Click [Save].
3. In the DB Cluster interface, check the Status of the target with Log enabled in the DB cluster list.
   • Configuring: Status in which the DB Cluster is being configured based on user input data.
   • Running: Status in which the DB cluster's configuration has been completed with the information you entered.

Manage Backup settings

You can change the backup file retention period and backup time for the selected DB cluster. To change:

1. On the Manage Backup settings tab, see the following to change the settings:
   • Backup settings: Select whether to use the backup settings of Cloud DB Serverless (currently the option cannot be changed).
   • Backup file retention period: Enter a value between 1 and 30.
   • Backup time: Configuring backup time is performed within 15 minutes from the selected time.
     • Automatic: Backup is automatically started every day.
     • User-defined: Backup is started every day within +15 minutes from the time you selected.
2. Click [Save].