This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

MySQL(DBaaS)

1: Overview

1.1: Server type
1.2: Monitoring metrics
1.3: ServiceWatch metric

2: How-to guides

2.1: Managing DB Services
2.2: Backing up and restoring the DB
2.3: Configure Read Replica
2.4: MySQL (DBaaS) server connection

3: API Reference

4: CLI Reference

5: Release Note

1 - Overview

Service Overview

MySQL(DBaaS) is an open-source relational database management system (RDBMS). Samsung Cloud Platform provides an environment that can automate MySQL installation and perform management functions for operation through a web-based Console.

MySQL (DBaaS) is designed as a high‑availability architecture that performs storage‑based data replication and minimizes failover time. To prevent data loss, when the contents of the Active server change, they are synchronously replicated to the Standby server, and up to five read‑only Replica servers for read load balancing and disaster recovery (DR) are provided. Additionally, it offers an automatic backup feature at user-specified times to prepare for issues with the DB server or data, allowing recovery of data at the desired point in time.

Provided features

MySQL (DBaaS) provides the following features.

Auto Provisioning (Auto Provisioning): UI allows installation and configuration of Database (DB), and provides an Active‑standby redundancy configuration built on storage replication. * When the active server fails, it automatically fails over to standby.
Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, a switch-over allows the user to directly perform the Active-Standby node transition.
Backup and Recovery: Provides data backup functionality based on its own backup commands. * Backup time windows and storage locations can be set by the user, and additional fees may apply based on backup size. * It also provides a recovery function for backed-up data, and when the user performs a recovery, a separate database is created, and the recovery proceeds to the point in time selected by the user (backup save point, user-specified point). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour before the stored backup and archive files.
Version Management: Provides Major and Minor version upgrade functionality based on certain feature improvements and security patches.
Replica configuration: For read load balancing and disaster recovery (DR), up to five Read Replicas can be configured in the same or different regions.
Parameter Management: You can modify DB configuration parameters related to performance improvement and security.
Service Status Query: Retrieves the final status of the current DB service.
Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
DB User Management: View and manage the DB account (user) information registered in the DB.
DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IP addresses for access.
Archive Management: You can set the retention period (1~35 days) for Archive files on the DB server and configure the Archive mode (On/Off).
Export DB Log: You can export stored logs to the user’s Object Storage through Audit settings.
Migration: Synchronizes data in real time with the operational database and supports migration using replication without service interruption.
OS Kernel Upgrade: You can upgrade the OS Kernel to apply some feature improvements and security patches.

Components

MySQL(DBaaS) provides pre‑validated engine versions and various server types according to the open‑source support policy. Users can choose and use it based on the scale of the service they wish to configure.

Engine version

The engine versions supported by MySQL (DBaaS) are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.

Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.

MySQL (Community): https://www.mysql.com/support/eol-notice.html

service	Provided version	EOS Date (Samsung Cloud Platform new creation stop date)	EoTS Date(Community Technical Support End Date)
MySQL (Community)	8.0.28	2026-03-19	2026-04-30
	8.0.30	2026-03-19	2026-04-30
	8.0.32	2026-03-19	2026-04-30
	8.0.33	2026-03-19	2026-04-30
	8.0.34	2026-03-19	2026-04-30
	8.0.35	2026-03-19	2026-04-30
	8.0.36	2026-03-19	2026-04-30
	8.0.37	2026-03-19	2026-04-30
	8.0.41	2026-03-19	2026-04-30
	8.0.42	2026-03-19	2026-04-30
	8.4.5	2031-12 (planned)	2032-04-30
	8.4.7	2031-12 (planned)	2032-04-30

Table. MySQL (DBaaS) provided engine versions

Information

The next version of MySQL is expected to be released after September 2026. The actual service delivery schedule is subject to change.

MySQL 8.4.8

Server type

The server types supported by MySQL (DBaaS) are as follows.

For detailed information about the server types provided by MySQL(DBaaS), see MySQL(DBaaS) 서버 타입.

Standard db1v2m4

Category	Example	Detailed description
Server type	Standard	Provided server types Standard: Standard configuration (vCPU, Memory) commonly used High Capacity: Large server specifications of 24 vCores or more
Server specifications	db1	Provided server specifications db1: Standard configuration (vCPU, Memory) commonly used dbH2: Large-capacity server specifications Provides servers with 24 vCores or more
Server specifications	v2	Number of vCores v2: 2 virtual cores
Server specifications	m4	Memory capacity m4: 4GB Memory

Table. MySQL(DBaaS) server type components

Preceding Service

This is a list of services that must be pre‑configured before creating the service. For detailed information, please refer to the guide provided for each service and prepare in advance.

Service Category	service	Detailed description
Networking	VPC	A service that provides an isolated virtual network in a cloud environment

Table. MySQL (DBaaS) pre-service

1.1 - Server type

MySQL(DBaaS) server type

MySQL(DBaaS) provides server types composed of various combinations such as CPU, Memory, and Network Bandwidth. When creating MySQL(DBaaS), the Database Engine is installed based on the server type chosen for the intended use.

Reference

The server types offered may vary depending on the region and AZ.

The server types supported by MySQL (DBaaS) are as follows.

Standard db1v2m4

Category	Example	Detailed description
Server type	Standard	Provided server type categories Standard: Configured with the commonly used standard specifications (vCPU, Memory) High Capacity: Large-capacity server specifications exceeding Standard
Server specifications	db1	Provided server type classification and generation db1: means a standard specification, and 1 indicates the generation dbh2: h indicates a large-capacity server specification, and 2 indicates the generation
Server specifications	v2	Number of vCores v2: 2 virtual cores
Server specifications	m4	Memory capacity m4: 4GB Memory

Table. MySQL (DBaaS) server type format

db1 server type

The db1 server type of MySQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps

Category	Server type	vCPU	Memory	Network Bandwidth
Standard	db1v2m4	2 vCore	4 GB	Up to 10 Gbps
Standard	db1v2m8	2 vCore	8 GB	Up to 10 Gbps
Standard	db1v2m16	2 vCore	16 GB	Up to 10 Gbps
Standard	db1v2m24	2 vCore	24 GB	Up to 10 Gbps
Standard	db1v2m32	2 vCore	32 GB	Up to 10 Gbps
Standard	db1v4m8	4 vCore	8 GB	Up to 10 Gbps
Standard	db1v4m16	4 vCore	16 GB	Up to 10 Gbps
Standard	db1v4m32	4 vCore	32 GB	Up to 10 Gbps
Standard	db1v4m48	4 vCore	48 GB	Up to 10 Gbps
Standard	db1v4m64	4 vCore	64 GB	Up to 10 Gbps
Standard	db1v6m12	6 vCore	12 GB	Up to 10 Gbps
Standard	db1v6m24	6 vCore	24 GB	Up to 10 Gbps
Standard	db1v6m48	6 vCore	48 GB	Up to 10 Gbps
Standard	db1v6m72	6 vCore	72 GB	Up to 10 Gbps
Standard	db1v6m96	6 vCore	96 GB	Up to 10 Gbps
Standard	db1v8m16	8 vCore	16 GB	Up to 10 Gbps
Standard	db1v8m32	8 vCore	32 GB	Up to 10 Gbps
Standard	db1v8m64	8 vCore	64 GB	Up to 10 Gbps
Standard	db1v8m96	8 vCore	96 GB	Up to 10 Gbps
Standard	db1v8m128	8 vCore	128 GB	Up to 10 Gbps
Standard	db1v10m20	10 vCore	20 GB	Up to 10 Gbps
Standard	db1v10m40	10 vCore	40 GB	Up to 10 Gbps
Standard	db1v10m80	10 vCore	80 GB	Maximum 10 Gbps
Standard	db1v10m120	10 vCore	120 GB	Up to 10 Gbps
Standard	db1v10m160	10 vCore	160 GB	Up to 10 Gbps
Standard	db1v12m24	12 vCore	24 GB	Up to 12.5 Gbps
Standard	db1v12m48	12 vCore	48 GB	Up to 12.5 Gbps
Standard	db1v12m96	12 vCore	96 GB	Up to 12.5 Gbps
Standard	db1v12m144	12 vCore	144 GB	Up to 12.5 Gbps
Standard	db1v12m192	12 vCore	192 GB	Up to 12.5 Gbps
Standard	db1v14m28	14 vCore	28 GB	Up to 12.5 Gbps
Standard	db1v14m56	14 vCore	56 GB	Up to 12.5 Gbps
Standard	db1v14m112	14 vCore	112 GB	Up to 12.5 Gbps
Standard	db1v14m168	14 vCore	168 GB	Up to 12.5 Gbps
Standard	db1v14m224	14 vCore	224 GB	Up to 12.5 Gbps
Standard	db1v16m32	16 vCore	32 GB	Up to 12.5 Gbps
Standard	db1v16m64	16 vCore	64 GB	Up to 12.5 Gbps
Standard	db1v16m128	16 vCore	128 GB	Up to 12.5 Gbps
Standard	db1v16m192	16 vCore	192 GB	Up to 12.5 Gbps
Standard	db1v16m256	16 vCore	256 GB	Up to 12.5 Gbps

Table. MySQL(DBaaS) server type specifications - db1 server type

db2 server type

The db2 server type of MySQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps

Category	Server type	vCPU	Memory	Network Bandwidth
Standard	db2v2m4	2 vCore	4 GB	Up to 10 Gbps
Standard	db2v2m8	2 vCore	8 GB	Up to 10 Gbps
Standard	db2v2m16	2 vCore	16 GB	Up to 10 Gbps
Standard	db2v2m24	2 vCore	24 GB	Up to 10 Gbps
Standard	db2v32m32	2 vCore	32 GB	Up to 10 Gbps
Standard	db2v4m8	4 vCore	8 GB	Up to 10 Gbps
Standard	db2v4m16	4 vCore	16 GB	Up to 10 Gbps
Standard	db2v4m32	4 vCore	32 GB	Up to 10 Gbps
Standard	db2v4m48	4 vCore	48 GB	Maximum 10 Gbps
Standard	db2v4m64	4 vCore	64 GB	Up to 10 Gbps
Standard	db2v6m12	6 vCore	12 GB	Up to 10 Gbps
Standard	db2v6m24	6 vCore	24 GB	Up to 10 Gbps
Standard	db2v6m48	6 vCore	48 GB	Maximum 10 Gbps
Standard	db2v6m72	6 vCore	72 GB	Up to 10 Gbps
Standard	db2v96m6	6 vCore	96 GB	Up to 10 Gbps
Standard	db2v8m16	8 vCore	16 GB	Up to 10 Gbps
Standard	db2v8m32	8 vCore	32 GB	Up to 10 Gbps
Standard	db2v8m64	8 vCore	64 GB	Up to 10 Gbps
Standard	db2v8m96	8 vCore	96 GB	Up to 10 Gbps
Standard	db2v8m128	8 vCore	128 GB	Up to 10 Gbps
Standard	db2v10m20	10 vCore	20 GB	Up to 10 Gbps
Standard	db2v10m40	10 vCore	40 GB	Up to 10 Gbps
Standard	db2v10m80	10 vCore	80 GB	Up to 10 Gbps
Standard	db2v10m120	10 vCore	120 GB	Up to 10 Gbps
Standard	db2v10m160	10 vCore	160 GB	Up to 10 Gbps
Standard	db2v12m24	12 vCore	24 GB	Up to 12.5 Gbps
Standard	db2v12m48	12 vCore	48 GB	Up to 12.5 Gbps
Standard	db2v12m96	12 vCore	96 GB	Up to 12.5 Gbps
Standard	db2v12m144	12 vCore	144 GB	Up to 12.5 Gbps
Standard	db2v12m192	12 vCore	192 GB	Up to 12.5 Gbps
Standard	db2v14m28	14 vCore	28 GB	Up to 12.5 Gbps
Standard	db2v14m56	14 vCore	56 GB	Up to 12.5 Gbps
Standard	db2v14m112	14 vCore	112 GB	Up to 12.5 Gbps
Standard	db2v14m168	14 vCore	168 GB	Up to 12.5 Gbps
Standard	db2v14m224	14 vCore	224 GB	Up to 12.5 Gbps
Standard	db2v16m32	16 vCore	32 GB	Up to 12.5 Gbps
Standard	db2v16m64	16 vCore	64 GB	Up to 12.5 Gbps
Standard	db2v16m128	16 vCore	128 GB	Up to 12.5 Gbps
Standard	db2v16m192	16 vCore	192 GB	Up to 12.5 Gbps
Standard	db2v16m256	16 vCore	256 GB	Up to 12.5 Gbps

Table. MySQL (DBaaS) server type specifications - db2 server type

dbh2 server type

The dbh2 server type of MySQL (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.

Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
Supports up to 128 vCPUs and 1,536 GB of memory
Maximum networking speed of 25 Gbps

Category	Server type	vCPU	Memory	Network Bandwidth
High Capacity	dbh2v24m48	24 vCore	48 GB	Maximum 25 Gbps
High Capacity	dbh2v24m96	24 vCore	96 GB	Maximum 25 Gbps
High Capacity	dbh2v24m192	24 vCore	192 GB	Maximum 25 Gbps
High Capacity	dbh2v24m288	24 vCore	288 GB	Maximum 25 Gbps
High Capacity	dbh2v32m64	32 vCore	64 GB	Maximum 25 Gbps
High Capacity	dbh2v32m128	32 vCore	128 GB	Maximum 25 Gbps
High Capacity	dbh2v32m256	32 vCore	256 GB	Maximum 25 Gbps
High Capacity	dbh2v32m384	32 vCore	384 GB	Maximum 25 Gbps
High Capacity	dbh2v48m192	48 vCore	192 GB	Maximum 25 Gbps
High Capacity	dbh2v48m576	48 vCore	576 GB	Maximum 25 Gbps
High Capacity	dbh2v64m256	64 vCore	256 GB	Maximum 25 Gbps
High Capacity	dbh2v64m768	64 vCore	768 GB	Maximum 25 Gbps
High Capacity	dbh2v72m288	72 vCore	288 GB	Maximum 25 Gbps
High Capacity	dbh2v72m864	72 vCore	864 GB	Maximum 25 Gbps
High Capacity	dbh2v96m384	96 vCore	384 GB	Maximum 25 Gbps
High Capacity	dbh2v96m1152	96 vCore	1152 GB	Maximum 25 Gbps
High Capacity	dbh2v128m512	128 vCore	512 GB	Maximum 25 Gbps
High Capacity	dbh2v128m1536	128 vCore	1536 GB	Maximum 25 Gbps

Table. MySQL(DBaaS) server type specifications - dbh2 server type

db3 server type

The db3 server type of MySQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
Supports up to 16 vCPUs and 256 GB of memory
Maximum networking speed of 12.5 Gbps

Category	Server type	vCPU	Memory	Network Bandwidth
Standard	db3v2m4	2 vCore	4 GB	Up to 10 Gbps
Standard	db3v8m2	2 vCore	8 GB	Up to 10 Gbps
Standard	db3v2m16	2 vCore	16 GB	Up to 10 Gbps
Standard	db3v2m24	2 vCore	24 GB	Up to 10 Gbps
Standard	db3v2m32	2 vCore	32 GB	Up to 10 Gbps
Standard	db3v4m8	4 vCore	8 GB	Up to 10 Gbps
Standard	db3v4m16	4 vCore	16 GB	Up to 10 Gbps
Standard	db3v4m32	4 vCore	32 GB	Up to 10 Gbps
Standard	db3v4m48	4 vCore	48 GB	Up to 10 Gbps
Standard	db3v4m64	4 vCore	64 GB	Up to 10 Gbps
Standard	db3v6m12	6 vCore	12 GB	Up to 10 Gbps
Standard	db3v6m24	6 vCore	24 GB	Up to 10 Gbps
Standard	db3v6m48	6 vCore	48 GB	Up to 10 Gbps
Standard	db3v6m72	6 vCore	72 GB	Up to 10 Gbps
Standard	db3v6m96	6 vCore	96 GB	Up to 10 Gbps
Standard	db3v8m16	8 vCore	16 GB	Up to 10 Gbps
Standard	db3v8m32	8 vCore	32 GB	Up to 10 Gbps
Standard	db3v8m64	8 vCore	64 GB	Up to 10 Gbps
Standard	db3v8m96	8 vCore	96 GB	Up to 10 Gbps
Standard	db3v8m128	8 vCore	128 GB	Up to 10 Gbps
Standard	db3v10m20	10 vCore	20 GB	Up to 10 Gbps
Standard	db3v10m40	10 vCore	40 GB	Up to 10 Gbps
Standard	db3v10m80	10 vCore	80 GB	Up to 10 Gbps
Standard	db3v10m120	10 vCore	120 GB	Up to 10 Gbps
Standard	db3v10m160	10 vCore	160 GB	Up to 10 Gbps
Standard	db3v12m24	12 vCore	24 GB	Up to 12.5 Gbps
Standard	db3v12m48	12 vCore	48 GB	Up to 12.5 Gbps
Standard	db3v12m96	12 vCore	96 GB	Up to 12.5 Gbps
Standard	db3v12m144	12 vCore	144 GB	Up to 12.5 Gbps
Standard	db3v12m192	12 vCore	192 GB	Up to 12.5 Gbps
Standard	db3v14m28	14 vCore	28 GB	Up to 12.5 Gbps
Standard	db3v14m56	14 vCore	56 GB	Up to 12.5 Gbps
Standard	db3v14m112	14 vCore	112 GB	Up to 12.5 Gbps
Standard	db3v14m168	14 vCore	168 GB	Up to 12.5 Gbps
Standard	db3v14m224	14 vCore	224 GB	Up to 12.5 Gbps
Standard	db3v16m32	16 vCore	32 GB	Up to 12.5 Gbps
Standard	db3v16m64	16 vCore	64 GB	Up to 12.5 Gbps
Standard	db3v16m128	16 vCore	128 GB	Up to 12.5 Gbps
Standard	db3v16m192	16 vCore	192 GB	Up to 12.5 Gbps
Standard	db3v16m256	16 vCore	256 GB	Up to 12.5 Gbps

Table. MySQL(DBaaS) server type specifications - db3 server type

dbh3 server type

The dbh3 server type of MySQL (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.

Intel 6th‑generation (Granite Rapids) Xeon 6738P Processor up to 4.1 GHz
Supports up to 128 vCPUs and 1,536 GB of memory
Maximum networking speed of 25 Gbps

Category	Server type	vCPU	Memory	Network Bandwidth
High Capacity	dbh3v24m48	24 vCore	48 GB	Maximum 25 Gbps
High Capacity	dbh3v24m96	24 vCore	96 GB	Maximum 25 Gbps
High Capacity	dbh3v24m192	24 vCore	192 GB	Maximum 25 Gbps
High Capacity	dbh3v24m288	24 vCore	288 GB	Maximum 25 Gbps
High Capacity	dbh3v32m64	32 vCore	64 GB	Maximum 25 Gbps
High Capacity	dbh3v32m128	32 vCore	128 GB	Maximum 25 Gbps
High Capacity	dbh3v32m256	32 vCore	256 GB	Maximum 25 Gbps
High Capacity	dbh3v32m384	32 vCore	384 GB	Maximum 25 Gbps
High Capacity	dbh3v48m192	48 vCore	192 GB	Maximum 25 Gbps
High Capacity	dbh3v48m576	48 vCore	576 GB	Maximum 25 Gbps
High Capacity	dbh3v64m256	64 vCore	256 GB	Maximum 25 Gbps
High Capacity	dbh3v64m768	64 vCore	768 GB	Maximum 25 Gbps
High Capacity	dbh3v72m288	72 vCore	288 GB	Maximum 25 Gbps
High Capacity	dbh3v72m864	72 vCore	864 GB	Maximum 25 Gbps
High Capacity	dbh3v96m384	96 vCore	384 GB	Maximum 25 Gbps
High Capacity	dbh3v96m1152	96 vCore	1152 GB	Maximum 25 Gbps
High Capacity	dbh3v128m512	128 vCore	512 GB	Maximum 25 Gbps
High Capacity	dbh3v128m1536	128 vCore	1536 GB	Maximum 25 Gbps

Table. MySQL(DBaaS) server type specifications - dbh3 server type

Database passwordRequiredPassword to use when accessing the DB

Include English letters, numbers, and special characters (“ ‘ excluded) and enter 8~30 characters

Check database passwordRequiredRe-enter the same password to use for DB accessDatabase Port numberRequiredPort number required for DB connection

Enter DB port within the range 1200 ~ 65535

Backup > UseSelection:Backup usage

Select Use to set the backup file retention period, backup start time, and Archive backup interval

Backup > Retention PeriodSelectionBackup retention period

Select the backup retention period. Set the file retention period from 7 days to 35 days

Backup files incur additional charges based on size

Backup > Backup Start PeriodSelectionBackup start time

Select backup start time

The minute(s) (minutes) at which the backup runs is set randomly, and the backup end time cannot be set

Backup > Archive backup scheduleSelectionArchive backup interval

Select the Archive backup interval

The Archive backup interval is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance

ParameterRequiredParameters for the DB

View button can be clicked to view the parameter’s detailed information

Parameters can be modified after the DB creation is complete, and the DB must be restarted after modification

DB character setRequiredCharacter encoding to use for the DBTable case sensitivitySelectionCase sensitivity of DB tableTime zoneRequiredStandard time zone used by the databaseServiceWatch log collectionSelectionServiceWatch log collection status

Select Use to configure the ServiceWatch log collection feature

It is provided free of charge up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB.

When collected, log groups and log streams are created automatically, and they cannot be deleted until the resource is removed.

To prevent exceeding 5 GB, direct deletion of log data or shortening the retention period is recommended.

Table. MySQL(DBaaS) Database configuration items

Category	Detailed description
Cluster status	Cluster status with DB installed Creating: Cluster is being created Editing: Cluster is being changed to an operational state Error: Cluster encountered a failure while performing a task If it occurs continuously, contact the administrator Failed: Cluster failed during creation Restarting: Cluster is restarting Running: Cluster is operating normally Starting: Cluster is starting Stopped: Cluster is stopped Stopping: Cluster is being stopped Synchronizing: Cluster is synchronizing Terminating: Cluster is being terminated Unknown: Cluster status is unknown If it occurs continuously, contact the administrator Upgrading: Cluster is being upgraded
Cluster control	Buttons to change the cluster state Start: Start a stopped cluster Stop: Stop a running cluster Restart: Restart a running cluster Switch-Over: Switch a standby cluster to Active
View more features	Cluster-related management buttons Service status synchronization: Real-time DB service status lookup Backup history: If backup is configured, check whether it runs correctly and view its history Database recovery: Recover the DB based on a specific point in time Parameter management: Ability to view and modify DB configuration parameters Replica configuration: Set up a read‑only cluster as a Replica Replica configuration (Other-Region): Configure a disaster‑recovery Replica in another region; the button is disabled if the account has no region to configure DB user management: View and manage DB account (user) information registered in the DB DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB Archive management: Set archive file retention periods and configure archive mode DB Log export: Export stored logs to the user’s Object Storage via Audit settings Migration configuration: Provides migration functionality using replication Block Storage usage management: Provides usage query functionality per Block Storage type OS (Kernel) upgrade: Upgrade the OS kernel version
Service cancellation	Cancel service button

Category	Detailed description
Server Information	Server information configured in this cluster Category: Server type (Active, Standby, Replica) Server Name: Server name IP Port: Server IP and port Status: Server status
service	Service name
Resource Type	Resource Type
SRN	Unique resource ID in Samsung Cloud Platform In the DB service, it refers to the cluster SRN
Resource Name	Resource name In the DB service, it refers to the cluster name
Resource ID	Unique resource ID in the service
Constructor	User who created the service
Creation Date/Time	Service creation date and time
Modifier	User who edited the service information
Modification date and time	Date and time the service information was modified
Image version	Installed DB image and version information If a version upgrade is required, click the Edit icon to configure For details, refer to Minor 버전 업그레이드하기 and Major 버전 업그레이드하기
Cluster type	Cluster type (Master Cluster, Replica Cluster, Migration Cluster)
Cluster name	Cluster name of the DB servers
Master cluster name	Replica’s Master cluster name If it is the Replica’s detailed information, it can be confirmed
Database name	Server name applied during DB installation
Database username	DB user name
Planned Compute	Resource status with Planned Compute configured For more information, refer to Planned Compute 신청하기
Maintenance period	DB Maintenance Period Status If you need to set the maintenance period, click the Edit icon to configure
Backup	Backup Configuration Status If you need to configure backup, click the Edit icon to set it If you need an immediate backup, click the Immediate Backup button to set it For detailed information about backup, refer to MySQL(DBaas) 백업하기
ServiceWatch log collection	ServiceWatch Log Collection Configuration Status If log collection configuration is required, click the Edit icon next to Log Collection to configure
DB character set	Encoding method to be used for the DB
Table case sensitivity	Case sensitivity of DB table
Time zone	Standard time zone used by the database
VIP	Virtual IP information can be checked only when high availability is configured
Network	Network information of the DB installation (VPC, Subnet, VIP, NAT IP(VIP))

Item	Detailed description	Whether to restart
`character-set-server`	Specify default character set	Restart required
`collation-server`	Specify default collation (Collation)	Restart required
`init_connect`	SQL statement executed when the client connects to the database	No restart required

Category	Required	Detailed description
Log type	Required	Log type to be saved
Save bucket name	Essential	Object Storage bucket name to be saved
Authentication key > Access key	Required	Access key for accessing the Object Storage you want to store.
Authentication key > Secret key	Required	Secret key for accessing the Object Storage you want to store
File creation cycle	Required	File creation frequency in Object Storage
Whether to delete the original log	Selection	Whether to delete the original logs when exporting to Object Storage

Category	Required	Detailed description
Source DB Database name	Required	Database name of the source DB to be migrated
Source DB IP	Required	IP of the Source DB that is the migration target
Source DB Port	Required	Port of the Source DB to be migrated
Source DB username	Required	Username of the Source DB to be migrated
Source DB password	Required	Password of the source DB that is the migration target

Category	Required status	Detailed description
Recovery type	Required	Set the point in time the user wants to restore Backup point (recommended): Restore based on the backup file. Select from the list of backup points displayed in the list. Custom point: Restore to a user‑desired point within the range of recoverable backup times. The recoverable period depends on the Archive backup interval setting, allowing restoration from the initial backup start time up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the date and time to back up
Server name prefix	Required	Recovery DB server name Start with a lowercase English letter and use lowercase letters, numbers, and special characters (`-`) to enter 3 to 16 characters Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name	Required	Cluster name of the recovery DB Enter using English letters, 3 ~ 20 characters A cluster is a unit that groups multiple servers
Service Type > Server Type	Required	Server type for the recovery DB installation Standard: standard specification commonly used High Capacity: large-capacity server with 24vCore or more (to be provided later)
Service Type > Planned Compute	Selection	Planned Compute가 설정된 자원 현황 In Use: Number of resources with Planned Compute that are currently in use Configured: Number of resources with Planned Compute set Coverage Preview: Amount applied per resource by Planned Compute Create Planned Compute Service: Go to the Planned Compute service request page For more details, refer to Planned Compute 신청하기
Service Type > Block Storage	Required	Block Storage settings used by the recovery DB Basic OS: Area where the DB engine is installed DATA: Storage area for table data, archive files, etc. Applied identically with the storage type set in the original cluster Enter capacity as a multiple of 8 within the range 16 to 5,120 Additional: Storage area for DATA, Archive, TEMP, Backup data Applied identically with the storage type set in the original cluster In the recovery DB, only DATA, TEMP, and Archive purposes can be added After selecting Use, enter the storage purpose and capacity Click the Add button to add storage, or click the x button to delete Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Database username	Required	Database username set in the source DB
Database Port number	Required	Database Port number set in the source DB
IP access control	Selection	IP address for accessing the recovery DB Enter in IP format (example: `192.168.10.1`) or CIDR format (example: `192.168.10.1/32`, `192.168.10.1/32`), and click the Add button To delete an entered IP, click the x button next to the entered IP
Maintenance period	Selection	DB maintenance window If you select Use, set the day of the week, start time, and duration The maintenance window is a feature that lets the user define the time slot for performing patch operations, and any patch work within that period must be carried out by the user. We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
tag	Selection	Add tag After clicking the Add tag button, enter or select Key, Value values

Category	required status	Detailed description
Region	required	Region to configure the Replica Replica configuration (Other Region) is displayed only when selected
Replica count	Required	Number of Replicas to configure Up to 5 can be configured per cluster If you select more than one value, additionally enter the Replica name and service type information
Replica name	Required	Replica server name Start with a lowercase English letter, and use lowercase letters, numbers, and special characters (`-`) to enter 3 to 19 characters The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type	Required	Replica server type Standard: standard specification commonly used High Capacity: large-capacity server with 24 vCores or more
Service Type > Planned Compute	Selection	Status of resources with Planned Compute configured In Use: Number of resources with Planned Compute configured that are currently in use Configured: Number of resources with Planned Compute configured Coverage Preview: Amount applied per resource by Planned Compute Create Planned Compute Service: Navigate to the Planned Compute service application page For more details, see Apply for Planned Compute
IP access control	Select	Service Access Policy Configuration Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required Enter in IP format (example: `192.168.10.1`) or CIDR format (example: `192.168.10.0/24`, `192.168.10.1/32`) and click the Add button To delete an entered IP, click the x button next to the entered IP
maintenance period	Select	Database maintenance window If you select Use, set the day of week, start time, and duration It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions If set to unused, we are not responsible for issues arising from patches not being applied.
Tag	Select	Add Tag Add Tag after clicking the button, enter or select Key, Value values

Direction	Remote	Target address	Protocol	Port	Explanation
Inbound	CIDR	User PC IP	TCP	3389 (RDP)	Bastion access PC → Bastion host
Outbound	CIDR	DB IP	TCP	Database Port (manual entry)	Bastion host → Database

Required input element item	input value
Connection Name	Custom (ex. service name)
Host name	Database server IP
Port	Database Port
Username	Database username

MySQL(DBaaS)

1 - Overview

Service Overview

Provided features

Components

Engine version

Server type

Preceding Service

1.1 - Server type

MySQL(DBaaS) server type

db1 server type

db2 server type

dbh2 server type

db3 server type

dbh3 server type

Check MySQL(DBaaS) detailed information

Detailed Information

Replica information

tag

Job History

MySQL(DBaaS) Managing Resources

Operation Control

Synchronize service status

Change Server Type

Add storage

Expanding storage

Terminate MySQL(DBaaS)

2.1 - Managing DB Services

Parameter Management

Parameter lookup

Edit Parameter

Managing DB Users

Query DB users

Change DB user status

Managing DB Access Control

View DB access control

Add DB Access Control

Delete DB access control

Configure Archive mode

DB Log Export

Setting DB Log Export Mode

Managing DB Log Export

Upgrade version

Major version upgrade

Minor version upgrade

Configure Migration

Promote Migration Cluster to Master Cluster

Managing Block Storage Usage

OS Kernel Upgrade

2.2 - Backing up and restoring the DB

Backing up MySQL (DBaaS)

Configure Backup

Perform immediate backup

Check backup history

Delete backup file

MySQL(DBaaS) Recover

2.3 - Configure Read Replica

Configure Replica

Reconfigure Replica

Promoting a Replica Cluster to a Master Cluster

2.4 - MySQL (DBaaS) server connection

Scenario Overview

Scenario components

Scenario setup method

1. ## Configure Network

1-1. ### Create VPC

1-2. ### Create Subnet

1-3. ### Create Internet Gateway

1-4. ### Create Public IP

1-5. ### Create Security Group

2. ## Create Bastion host

2-1. ### Create Server Keypair

2-2. ### Create Bastion host

2-3. ### Check Bastion host login ID and PW

3. ## Create Database

3-1. ### MySQL(DBaaS) Create Service

4. ## Configure Rules

4-1. ### Security Group Add security rule

4-2. ### Add IGW Firewall rule

5. ## Database Connect