Cloud DB for MySQL resource management

Prev Next

Available in Classic and VPC

Check the resource information of Cloud DB for MySQL. All activities that you can perform in Cloud DB for MySQL are mapped with the resource type and task history by resource type (action) defined in Resource Manager. Based on the value mapped, the task history actually performed by users is collected in Cloud Activity Tracer, and the admin can use it when monitoring the users' activities or creating audit reports. In addition, the resource type is used as a standard for usage permissions by user in Sub Account.
The following describes the resource and task history by resource type:

  • Resource
    • Unit of key information managed by each service
    • Object that can be created, changed, and deleted by the user
    • Unique value by each service of NAVER Cloud Platform
  • Task history by resource type (action)
    • History of tasks performed by the user through the console and API
    • Act of creating, changing, or deleting resources

The following describes Cloud DB for MySQL's resource type and task history information by resource type:

Service name (product code) Resource type Task history by resource type
Cloud DB for MySQL(CloudDBforMySQL) Server ADD Recovery DB Server
ADD Slave DB Server
Change DB Server Spec
Change Server Name
Change To High Availability
Change To Stand Alone
Create DB Server
Create DB Server(Stanby Master)
Create Master DB Server
Create New DB Server
DB Server Failover
Delete DB Server
Delete Failed DB Server
Export Backup To Object Storage
Export DB Log to Object Storage
Restart DB Server
Shutdown DB Server
Start DB Server
Stop DB Server
Service Change DB Server Spec
Change DB Version
Change Log Rotate
Change Server Name
Change Service Name
Change To High Availability
Change To Stand Alone
Create Cloud DB Service
Create DB Server
Create New DB Server
Create Public Domain
Create Public Ip
Create Recovery Server
Create Slave DB Server
Create Standby Master DB
DB Server Failover
DB Server auto fail-over
Delete Cloud DB Server
Delete Cloud DB Service
Delete Failed DB Server
Delete Log
Delete Public Domain
Delete Public Ip
Delete Service
Destroy Server
Export To Object Storage
Failover Master DB
Init DB Service
Reinstall Slaver DB Server
Restart DB Server
Skip Replication Error
Start DB Server
Stop DB Server
Swap Memory
Upgrade Cloud DB Service
Cloud DB for MySQL(VPCCloudDBforMySQL) Server Add Recovery DB Server
Attach Public Domain To Server
Change DB Server Name
Change DB Server Spec
Change Data Storage Size
Change Server To High Availability
Change Server To Stand Alone
Create DB Server
Create Standby Master DB Server Due to Change of Multi Zone
DB Server Failover
Delete DB Server
Delete Standby Master DB Server Due to Change of Multi Zone
Detach Public Domain To Server
Export DB Log to Object Storage
Kill Multiple Session
Kill Session
Reinstall Slave DB Server
Reinstall Standby Master DB Server
Restart DB Server
Skip Replication Error of DB Server
Switch to Master DB Server Due to Failover
Switch to Standby Master DB Server Due to Failover
Take Over Server
Service Add Slave Server To Service
Change Backup Setting
Change DB Service Spec
Change Log Rotate
Change Lower Case Table Names
Change Multi Zone
Change Service Name
Change Service To High Availability
Change Service To Stand Alone
Change Swap Memory
Configure DB Plugin
Create Cloud DB Service
Create Public Domain
DB Service Auto Failover
DB Service Manual Failover
Delete Cloud DB Service
Delete Log
Delete Public Domain
Export Backup to Object Storage
Save DB Config
Set System Config
Sync Acl Console
Upgrade Cloud DB Service
Note
  • Resource Manager: it is a service provided by NAVER Cloud Platform for free. For more information on how to use the service, see the Resource Manager user guide.
  • Cloud Activity Tracer: it is a service provided by NAVER Cloud Platform for free. For more information on how to use the service, see the Cloud Activity Tracer user guide.
  • Sub Account: it is a service provided by NAVER Cloud Platform for free. The permissions are designed based on the resource type defined in Resource Manager. However, because the resource type group and the action by resource type are configured in Sub Account, they differ from the group and action values defined in Resource Manager.