This is the multi-page printable view of this section. Click here to print.
MySQL(DBaaS)
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 the read‑only server called Replica, used for read load balancing and disaster recovery (DR), is provided up to five instances. Additionally, it provides an automatic backup feature at user-specified times to prepare for issues with the DB server or data, enabling recovery of data at the desired point in time.
Provided Features
MySQL(DBaaS) provides the following features.
- Auto Provisioning (Auto Provisioning): Allows installation and configuration of Database(DB) via UI, and provides an Active-standby redundancy configuration based 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, you can restart if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, the user can manually perform node switching between Active and Standby via a switch‑over.
- Backup and Recovery: Provides data backup functionality based on its own backup commands. * The backup schedule and retention policy can be set by the user, and additional fees apply based on the backup size. * It also provides a recovery function for backed‑up data, so when the user performs a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user (the backup save point or a 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 earlier, based on the stored backup and archive files.
- Version Management: Provides a version upgrade (Minor) feature based on certain feature enhancements and security patches. * Whether to perform a backup for a version upgrade can be selected by the user, and if a backup is performed, the data is backed up before applying the patch, after which the DB engine is updated.
- Replica configuration: Up to five Read Replicas can be configured in the same or different regions for read load balancing and disaster recovery (DR).
- Parameter management: Performance improvements and security-related DB configuration parameters can be modified.
- Service Status Query: Retrieves the current DB service’s final status.
- Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
- DB User Management: Query 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 IPs 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: Synchronize data in real time with the live database and support migration using replication without service interruption.
- OS Kernel Upgrade: The OS kernel can be upgraded to apply certain feature improvements and security patches.
Component
MySQL(DBaaS) provides pre‑validated engine versions and a variety of server types in accordance with the open‑source support policy. Users can select 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 stopped 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 |
The next version of MySQL is scheduled to be released after July 2026. The actual service delivery schedule is subject to change.
- MySQL 8.4.7
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
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
Preceding Service
This is a list of services that must be pre-configured before creating the service. 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 |
1.1 - Server Types
MySQL (DBaaS) server type
MySQL(DBaaS) offers server types composed of various combinations of CPU, Memory, and Network Bandwidth. When creating a MySQL(DBaaS), the Database Engine is installed based on the server type selected for the intended use.
The server types supported by MySQL (DBaaS) are as follows.
Standard db1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classifications
|
| Server specifications | db1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
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 | Up to 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 |
db2 server type
The db2 server type of MySQL (DBaaS) is provided 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 | db2v2m32 | 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 | Up to 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 | Up to 10 Gbps |
| Standard | db2v72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db2v6m96 | 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 |
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
- Networking speed up to 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 | Up to 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 |
1.2 - Monitoring metrics
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service, which was released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
- New Resources: Resources created after the service improvement work in March 2026 are monitored by default using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide monitoring in parallel using the Cloud Monitoring service and the ServiceWatch service.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e. You need to verify the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete the process.
Cloud Monitoring Service Phased Termination Schedule Notice
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch: see the ServiceWatch 개요.
MySQL(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics for MySQL (DBaaS) that can be viewed through Cloud Monitoring. For detailed Cloud Monitoring usage, refer to the Cloud Monitoring guide.
For MySQL (DBaaS) server monitoring metrics, please refer to the Virtual Server Monitoring Metrics guide.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Sessions | Number of Active Sessions | cnt |
| Binary Log Used [MB] | binary log usage | MB |
| Connection Usage [Total] | DB connection session usage | % |
| Connections | Number of connections | cnt |
| Connections [MAX] | Connection count | cnt |
| Connections | max connected threads count | cnt |
| Data Directory Used [MB] | data directory usage | MB |
| Instance Status [PID] | mysqld process pid | pid |
| Open Files | Number of open DB files | cnt |
| Open Files [MAX] | Number of DB files that can be opened | cnt |
| Open Files Usage | DB file maximum count usage rate | % |
| Relay Log Used [MB] | relay log usage (MB) | MB |
| Running Threads | running thread count | cnt |
| Safe PID | safe program pid | pid |
| Slave Behind Master seconds | Time difference with the master node | sec |
| Slowqueries | Number of SQL queries running for a long time (over 5 minutes) (by DB) | cnt |
| Slowqueries [Total] | Number of long-running (over 5 minutes) SQL queries (total) | cnt |
| Tablespace Used | Tablespace usage | MB |
| Tablespace Used [Total] | Total tablespace usage | MB |
| Transaction Time [Long] | Maximum transaction execution time | sec |
| Wait Locks | Number of sessions blocked for more than 60 seconds by lock | cnt |
1.3 - ServiceWatch Metrics
MySQL sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1‑minute interval.
Basic Metrics
The following are the basic metrics for the namespace MySQL(DBaaS).
The indicators whose names are displayed in bold below are the key indicators selected from the basic metrics provided by MySQL(DBaaS). Key metrics are used to build service dashboards that are automatically created for each service in ServiceWatch.
Each metric guides users via the user guide on which statistical values are meaningful when viewing that metric, and among the meaningful statistics, the values displayed in bold are the primary statistics. In the service dashboard, you can view key metrics using the primary statistical values.
OS Basic Metrics
Category | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| CPU | CPU Usage | Percent | CPU usage |
|
| Disk | Disk Usage | Percent | Disk usage |
|
| Disk | Disk Write Bytes | Bytes/Second | Write throughput (bytes/second) on block device |
|
| Disk | Disk Read Bytes | Bytes/Second | Read capacity (bytes/second) from block device |
|
| Disk | Disk Write Requests | Count/Second | Number of write requests on block device (requests per second) |
|
| Disk | Disk Read Requests | Count/Second | Number of read requests on block device (requests per second) |
|
| Disk | Average Disk I/O Queue Size | None | Average queue length of requests issued to the block device |
|
| Disk | Disk I/O Utilization | Percent | The proportion of time the block device actually spent handling I/O operations |
|
| Memory | Memory Usage | Percent | Memory usage |
|
| Network | Network In Bytes | Bytes/Second | Received data rate (bytes/second) on the network interface |
|
| Network | Network Out Bytes | Bytes/Second | Transmitted capacity (bytes/second) on the network interface |
|
| Network | TCP Connections | Count/Second | Current total number of successfully established TCP connections |
|
| Network | Network In Packets | Count | Number of packets received on the network interface |
|
| Network | Network Out Packets | Count | Number of packets transmitted on the network interface |
|
| Network | Network In Dropped | Count | Number of packet drops received on the network interface |
|
| Network | Network Out Dropped | Count | Number of packet drops transmitted from the network interface |
|
| Network | Network In Errors | Count | Number of packet errors received on the network interface |
|
| Network | Network Out Errors | Count | Number of packet errors transmitted on the network interface |
|
MySQL Basic Metrics
Classification | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| Activelock | Active locks | Count | Number of transactions in lock wait (Lock Wait) state for 1 minute (60 seconds) or longer in the InnoDB storage engine |
|
| Activesession | Active sessions | Count | Number of active sessions |
|
| Activesession | Connection usage | Percent | Database connection session utilization |
|
| Activesession | Connections | Count | DB connection session |
|
| Datafile | Current open files | Count | Number of file descriptors opened by the DB |
|
| Datafile | Max open files | Count | Maximum number of file descriptors the DB can open |
|
| Datafile | Open files usage | Percent | DB file maximum count utilization |
|
| InnoDB | InnoDB buffer pool hit ratio | Percent | The proportion of data read directly from memory without accessing the disk |
|
| InnoDB | Innodb row lock wait transactions | Count | Current number of InnoDB transactions waiting for a row lock |
|
| InnoDB | InnoDB row lock time | Milliseconds | Total time waited due to InnoDB row locks (in milliseconds) |
|
| InnoDB | InnoDB deadlocks | Count/Minute | Number of deadlock occurrences |
|
| InnoDB | Table lock waits | Count/Minute | Number of waits that occurred to acquire a table lock |
|
| InnoDB | Temp disk tables | Count | Number of Temp Tables created on disk |
|
| InnoDB | Innodb log waits | Count | Number of times waited to write the redo log to disk |
|
| State | Instance state | None | Check MySQL DB Process status up/down
| - |
| State | Slave behind master seconds(8.0) (Replica Only) | Seconds | Replica latency (unit: seconds) |
|
| State | Slave io thread running(8.0) (Replica Only) | None | I/O Thread status
| - |
| State | Slave SQL thread running(8.0) (Replica Only) | None | SQL Thread status
| - |
| State | Replica behind master seconds(8.4+) (Replica Only) | Seconds | Replica latency (unit: seconds) |
|
| State | Replica io thread running(8.4+) (Replica Only) | None | I/O Thread status
| - |
| State | Replica SQL thread running(8.4+) (Replica Only) | None | SQL Thread status
| - |
| Tablespace | Tablespace used | Megabytes | Tablespace usage |
|
| Tablespace | Tablespace used(TOTAL) | Megabytes | Tablespace usage (total) |
|
| Transactions | Slow queries | Count | Number of queries that run for more than 10 seconds |
|
| Transactions | Long transaction time | Seconds | Long Transaction time |
|
| Transactions | Wait locks | Count | Number of sessions waiting for lock |
|
| Transactions | SQL Queries/Minute | Count/Minute | Queries executed per minute |
|
2 - How-to guides
Users can create the service by entering the required information for MySQL (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service per Resource
- New Resources: Resources created after the service improvement work in March 2026 are monitored by default using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, you must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e.g. You must review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Notice of the phased termination schedule for Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
Create MySQL (DBaaS)
You can create and use a MySQL (DBaaS) service from the Samsung Cloud Platform Console.
- Before creating the service, configure the VPC’s subnet type as General.
- If the subnet type is Local, the corresponding Database service cannot be created.
- When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to a statistical collection environment.
To create a MySQL (DBaaS), follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the Create MySQL(DBaaS) button. 2. Go to the MySQL(DBaaS) Creation page.
- MySQL (DBaaS) Creation page: enter the information required to create the service and select detailed options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version Essential Provide a list of MySQL (DBaaS) versions Table. MySQL (DBaaS) Image and version selection options - In the Service Information Input area, enter or select the required information.
Category required statusDetailed description Server name Prefix Required The server name where the DB will be installed - starts with a lowercase English letter and uses lowercase letters, numbers, and the special character (
-) to enter 3 to 13 characters
- A postfix such as 001, 002 is appended based on the server name, creating the actual server name
Cluster name Essential Cluster name of DB servers - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for DB installation - Standard: standard specifications commonly used
- High Capacity: large‑capacity server with 24 vCores or more
- For detailed information about the server types provided by MySQL (DBaaS), refer to MySQL(DBaaS) 서버 타입
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 request page
- For more details, see Planned Compute Apply
Service Type > Block Storage Required Block Storage configuration used by the DB according to its purpose - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
- SSD: High‑performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes that use Samsung Cloud Platform KMS (Key Management System) encryption keys
- The configured storage type is applied identically to additional storage
- Capacity must be entered as a multiple of 8 within the range 16 to 5,120
- Since executing SQL or monthly batch jobs can cause large sorts that may interrupt service, a separate TEMP storage must be allocated and used
- Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
- Add: Storage areas for DATA, Archive, TEMP, Backup data
- After selecting Use, enter the storage’s purpose and capacity
- The storage type is applied the same as the type set for DATA, and capacity can be entered as a multiple of 8 within the range 16 to 5,120
- To add storage, click the Add button; to delete, click the x button. Up to 9 can be added.
- Temporarily store backup data in BACKUP storage before transmitting it
- If the data to be backed up exceeds 100 GB and undergoes frequent changes, it is recommended to add a separate BACKUP storage for reliable backup. Set the backup capacity to about 60 % of the DATA capacity.
- If a BACKUP storage is not added, the
/tmparea is used, and backup will fail if capacity is insufficient
- For each service, only one Block Storage is allocated for Archive, TEMP, and BACKUP
Redundant configuration Select Redundancy configuration - When redundancy is used, the DB instance is configured as separate Active DB and Standby DB
Network > Common Settings Required Network settings for servers created by the service - Select when you want to apply the same settings to all installed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be auto‑generated
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use is checked, you can select from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select from reserved IPs in the VPC product’s Public IP. For more information, see Public IP 생성하기
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
- 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 interruption
- If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.
Table. MySQL (DBaaS) Service Configuration Items - starts with a lowercase English letter and uses lowercase letters, numbers, and the special character (
- Enter required database configuration information In this section, enter or select the required information.
Category Required statusDetailed description Database name Required Server name applied during DB installation - must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
Database username Required Database user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Restricted database user names can be viewed in the Console
Database password required Password to use when accessing the DB - Enter 8 to 30 characters, including letters, numbers, and special characters (excluding
“‘)
Database password verification Required Re-enter the same password to use for DB access Database Port number Essential Port number required for DB connection - Enter DB port within the range 1200 ~ 65535
Backup > Use Select Backup usage - Use to select and set backup file retention period, backup start time, and Archive backup interval
Backup > Retention period Select Backup 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 Period Select Backup start time - Select backup start time
- The minutes during which the backup runs (minutes) are set randomly, and the backup end time cannot be set
Backup > Archive backup cycle Selection Archive backup frequency - Select the archive backup frequency
- The archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Parameter Required Parameters to be used in the DB - Click the View button to view the parameter’s detailed information
- Parameters can be modified after the DB creation is complete, and after modification the DB must be restarted
DB character set Required Character encoding to use for the database Table case sensitivity Select DB Table case sensitivity time zone Required Standard time zone for the database ServiceWatch log collection Selection Whether to collect ServiceWatch logs - Select Use to enable the ServiceWatch log collection feature
- For details about the collected logs, see ServiceWatch metrics
- Up to 5 GB is provided free of charge for all services within the account, and charges apply based on storage size for usage exceeding 5 GB
- When collecting, log groups and log streams are created automatically, and they cannot be deleted until the resource is removed
- To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
Table. MySQL (DBaaS) Database configuration items - Additional Information Input area, please enter or select the required information.
Category required statusDetailed description Tag Select Add Tag - Up to 50 per resource can be added
- After clicking the Add Tag button, enter or select Key, Value values
Table. MySQL (DBaaS) additional information input fields
- Select the required information in the Image and version selection area.
- Check the detailed information and estimated billing amount generated in the Summary panel, and click the Create button.
- When creation is complete, check the created resources on the Resource List page.
View MySQL (DBaaS) detailed information
The MySQL (DBaaS) service allows you to view and edit the full list of resources and detailed information. MySQL(DBaaS) Details page consists of Details, Tags, Operation History tabs, and when the DB has a Replica configured, a Replica Information tab is added.
To view detailed information about the MySQL (DBaaS) service, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
- On the MySQL(DBaaS) List page, click the resource to view detailed information. 3. MySQL(DBaaS) Details Go to the page.
- MySQL(DBaaS) Details At the top of the page, status information and additional feature details are displayed.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Cluster is being created
- Editing: Cluster is transitioning to an operational state
- Error: Cluster encountered a failure while performing a task
- If this persists, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Cluster is being restarted
- 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 this persists, 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
More features Cluster management buttons - Service status synchronization: Real-time DB service status lookup
- Backup history: When backup is configured, verify whether backups run correctly and view the history
- Database recovery: Recover the DB based on a specific point in time
- Parameter management: View and modify DB configuration parameters
- Replica configuration: Set up a read‑only Replica cluster
- Replica configuration (Other-Region): Set up 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
- OS (Kernel) upgrade: Upgrade the OS kernel version
Service termination Cancel service button Table. MySQL (DBaaS) status information and additional features
- MySQL(DBaaS) Details At the top of the page, status information and additional feature details are displayed.
Detailed information
MySQL (DBaaS) List page lets you view detailed information of the selected resource and edit the information if needed.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster type | Cluster types (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster name | Cluster name of the DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied during DB installation |
| Database username | DB user name |
| Planned Compute | Resources with Planned Compute configured
|
| maintenance period | DB Maintenance Period Status
|
| Backup | Backup configuration status
|
| ServiceWatch log collection | ServiceWatch Log Collection Configuration Status
|
| DB character set | Encoding method to be used for the DB |
| Table case sensitivity | DB Table case sensitivity |
| time zone | Standard time zone for the database |
| VIP | Virtual IP information
|
| Network | Network information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP access control | Service access policy configuration
|
| Active & Standby | Active/Standby server type, base OS, additional Disk information
|
Replica information
Replica Information tab is enabled only when a Replica is configured in the cluster. Replica information tab allows you to view the Master cluster name, replica count, and Replica status.
| Category | Detailed description |
|---|---|
| Master information | Name of the Master cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status in the Master cluster
|
tag
MySQL(DBaaS) List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Work History
MySQL(DBaaS) List page allows you to view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Managing MySQL(DBaaS) Resources
If you need to change or restore the existing configuration options of a provisioned MySQL (DBaaS) resource, or set up a replica, you can perform the tasks on the MySQL(DBaaS) Detailed Information page.
Control operation
If changes occur to a running MySQL (DBaaS) resource, you can start, stop, or restart it. Additionally, when HA is configured, you can switch the Active‑Standby servers using a switch‑over.
To control the operation of MySQL (DBaaS), follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page, click the resource to control its operation. 3. MySQL(DBaaS) Details Go to the page.
- Check the MySQL (DBaaS) status and complete the change using the control button below.
- Start: DB service is installed on the server and the DB service is running (Running).
- Stop: The server where the DB service is installed and the DB service are stopped (Stopped).
- Restart: Only the DB service will be restarted.
- Switch Over: You can switch the DB’s Active server and Standby server.
Synchronize Service Status
You can synchronize the real-time service status of MySQL (DBaaS).
To check the service status of MySQL (DBaaS), follow the steps below.
- Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- MySQL (DBaaS) List page, click the resource to view its service status. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.
Change server type
You can change the configured server type.
To change the server type, follow these steps.
- If you modify the server type, a server restart is required. * Please separately verify any software license modifications or software settings and their implementation due to specification changes.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page: click the resource for which you want to change the server type. 3. Navigate to the MySQL (DBaaS) Details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Server Type Edit After selecting the server type in the popup window, click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. For a redundant DB configuration, all redundant servers are added simultaneously.
- It is applied in the same way as the Storage type selected when creating the service.
- In a high‑availability configured database, adding storage is applied simultaneously to the storage of both the active and standby databases.
- If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. * Please expand the Replica storage first, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to add storage. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.
Expanding storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To expand storage capacity, follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- MySQL(DBaaS) List page, click the resource whose server type you want to change. 3. MySQL(DBaaS) Details Go to the page.
- Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
- Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.
Cancel MySQL (DBaaS)
You can cancel unused MySQL (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact that may occur when the service is discontinued.
- For a DB with a Replica configured, terminating the Master DB does not delete the Replica. * If you also delete the replica, please cancel it separately from the resource list.
- If you terminate the DB, all stored data and any configured backup data will be deleted.
To cancel MySQL (DBaaS), follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- On the MySQL(DBaaS) List page, select the resource to cancel and click the Cancel Service button.
- After termination is complete, check on the MySQL(DBaaS) list page whether the resource has been terminated.
2.1 - DB Service Manage
Users can manage MySQL (DBaaS) through the Samsung Cloud Platform Console.
Parameter Management
Provides a feature that allows easy viewing and modification of database configuration parameters.
View Parameter
To view configuration parameters, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- Click the resource you want to view or modify parameters for on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management popup window, click the Search button. The Search Notification popup window opens.
- Lookup Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
Modify Parameter
To modify the configuration parameters, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- Click the resource you want to view or modify parameters for on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management in the popup window, click the Search button. The Search Notification popup opens.
- Lookup Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
- If a modification is needed, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
- When the input is complete, click the Complete button.
If you change the character_set_server value, first verify the collation that matches the character set using the command below.
SQL> SHOW COLLATION WHERE Charset = 'character set name';
Set the parameter values for character-set-server, collation-server, and init_connect with the confirmed collation.
| Item | Detailed description | Whether to restart |
|---|---|---|
character-set-server | Specify the default character set | Restart required |
collation-server | Specify default collation (Collation) | Restart required |
init_connect | SQL statements executed when the client connects to the database | No restart required |
Managing DB Users
Provides management functions to retrieve DB user information and modify status information.
Query DB users
To retrieve DB users, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource for which you want to view DB users. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
- On the DB User Management page, click the Search button. Retrieving the data may take a moment.
Changing DB User Status
Follow these steps to change the status of the retrieved DB user.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the MySQL(DBaaS) Service Home page.
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) list page.
- On the MySQL(DBaaS) List page, click the resource for which you want to modify the DB user. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the DB User Management button. You will be directed to the DB User Management page.
- On the DB User Management page, click the Search button. The query may take a short time.
- If modification is needed, click the Edit button, and change the status field value or enter remarks.
- When the input is complete, click the Complete button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IPs that can access the database, configuring it so that only authorized IPs are allowed access.
Query DB Access Control
Follow these steps to query DB users with IP access control enabled.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page, click the resource you want to manage access control for. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a moment.
Add DB access control
To add IP access control, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Navigate to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource for which you want to add IP access control. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- DB Access Control Management page, click the Search button. Retrieving the data may take a moment.
- After the query completes, click the Add button. The Add DB Access Control popup window opens.
- Add DB Access Control In the popup window, select the DB username and enter the IP address.
- When the input is complete, click the Complete button.
Delete DB access control
To delete IP access control, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource for which you want to delete IP access control. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the View button. Retrieving the data may take a short while.
- When the query is complete, click the Delete button. The Delete popup window opens.
- In the Delete popup window, click the Confirm button.
Manage Archive
Provides the ability to configure Archive mode and set the retention period for Archive logs, allowing users to flexibly configure Archive log management policies to suit their operational environment. Additionally, it provides a feature to manually delete Archive logs, allowing you to clean up unnecessary log data and manage system resources effectively.
Configure Archive mode
To set Archive mode, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- Click the resource you want to set Archive mode for on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Detail page.
- Click the More button and click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- On the Archive Settings Management page, click the Search button. Retrieval may take a short time.
- Click the Edit button and select the usage status and retention period.
- When the edit is complete, click the Done button.
Delete Archive file
To delete the Archive file, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource for which you want to set Archive mode. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- On the Archive Settings Management page, if you want to delete all Archive files, click Delete All Archives; if you only want to delete the backed‑up Archive files, click the Delete Backed‑up Archive button.
DB Log Export
Supports exporting log data that requires long-term retention among audit logs to Object Storage. Users can directly configure the log types to be stored, the target bucket for export, and the export interval. Based on the configured criteria, logs are copied to the specified Object Storage for retention. Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for long-term storage.
- To use the DB Log export function, you need to create an Object Storage. For creating Object Storage, please refer to the Object Storage User Guide.
- Please be sure to check the expiration date and time of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
- Please ensure that authentication key information is not exposed externally.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the MySQL(DBaaS) Service Home page.
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page, click the resource you want to export the DB Log from. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the Export DB Log button. You will be taken to the Export DB Log page.
- On the DB Log Export page, click the Register button. You will be taken to the DB Log Export Register page.
- After entering the required information on the DB Log Export Registration page, click the Complete button.
Category Required Detailed descriptionLog type Required Log type to be saved Save bucket name Required Object Storage bucket name to be saved Authentication key > Access key Required Access key to access the Object Storage you want to store Authentication key > Secret key Required Secret key to access the Object Storage you want to store File creation cycle Required File creation interval in Object Storage Whether to delete the original log Selection Whether to delete the original logs when exporting to Object Storage Table. MySQL (DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource you want to manage DB Log export for. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the Export DB Log button. You will be taken to the Export DB Log page.
- On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, Cancel buttons.
- Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
- Edit: Modify the DB Log export mode setting.
- Cancel: Disables the DB Log export mode setting.
Minor Version Upgrade
We provide version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades within the same Major version are supported.
- First retrieve the service status by synchronizing it, then perform the version upgrade.
- Please perform the version upgrade after configuring a backup. If you do not set up a backup, you may be unable to recover some data if a problem occurs during the update.
- In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. Please check the Replica version first and, if necessary, perform a version upgrade.
- The backed-up data will be automatically deleted after the version upgrade is completed.
To upgrade the version, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- Click the resource to upgrade the version on the MySQL(DBaaS) List page. It navigates to the MySQL(DBaaS) Details page.
- Click the Edit button of the Image version item. The Version Upgrade popup window opens.
- Version Upgrade In the popup, select the updated version and backup setting, then click the Confirm button.
- Click the Confirm button in the Version Upgrade Notification popup.
Configure Migration
Provides a Migration feature that synchronizes in real time with the live database and replicates using a Replication method without service interruption.
To configure Migration, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to migrate. You will be taken to the MySQL(DBaaS) Detail page.
- Click the More button and then click the Migration Configuration button. The Migration Configuration popup window opens.
- In the popup window, review the instructions and click the Confirm button. You will be taken to the Migration configuration page.
- On the Migration configuration page, after entering the required information, click the Check connection button.
- When the connection is complete, click the Complete button.
Category Required Detailed descriptionSource 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 User name of the Source DB to be migrated Source DB password Required Password of the source DB that is the migration target Table. MySQL (DBaaS) migration configuration items
Promote Migration Cluster to Master Cluster
You can promote a configured Migration Cluster to a Master Cluster.
To promote the Migration Cluster to Master, follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to promote to Master. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the Master promotion button. The Master promotion notification popup opens.
- In the Master Promotion Notification popup, click the Confirm button.
Upgrade OS Kernel
The OS kernel can be upgraded to improve the functionality of the running database and apply security patches.
- The service will be unavailable while the OS upgrade is in progress.
- The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
- After the upgrade is complete, you cannot revert to the previous OS.
To upgrade the OS Kernel, follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to upgrade the OS Kernel. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup opens.
- OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.
2.2 - Backing up and restoring the database
Users can configure backups for MySQL (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Backing up MySQL (DBaaS)
PostgreSQL (DBaaS) provides data backup functionality based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.
Configure Backup
For instructions on configuring backups for MySQL(DBaaS), see MySQL(DBaaS) Creating.
To modify the backup settings of the created resource, follow the steps below.
- For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity. * Especially when the backup data exceeds 100 GB and undergoes frequent changes, please secure additional storage amounting to about 60 % of the data size. * For instructions on adding and expanding storage, please refer to the MySQL(DBaaS) Add Storage, MySQL(DBaaS) Expand Storage guides.
- If a backup is configured, it will run at the designated time after the set time, and additional fees will be incurred based on the backup size.
- If you change the backup setting to unset, backup execution stops immediately, and the stored backup data is deleted and can no longer be used.
To set up a backup, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page, click the resource for which you want to configure backup. 3. MySQL(DBaaS) Details Go to the page.
- Click the Edit button of the backup item. 4. Backup Settings popup window opens.
- When configuring a backup, click Enable in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
- If you wish to stop the backup configuration, deselect Backup Settings in the Use popup and authenticate via the logged-in user’s mobile phone.
When user authentication is complete, the backup configuration is disabled and backup execution stops.
- If you wish to stop the backup configuration, deselect Backup Settings in the Use popup and authenticate via the logged-in user’s mobile phone.
Check backup history
To view the backup history, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL (DBaaS) List Navigate to the page.
- MySQL(DBaaS) List On the page, click the resource for which you want to view the backup history. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup files
To delete the backup history, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Go to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List On the page, click the resource to view the backup history. 3. MySQL(DBaaS) Details Go to the page.
- Click the Backup History button. 4. Backup History popup window opens.
- Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
- When user authentication is completed, the backup file is deleted.
MySQL(DBaaS) Recover
When a failure or data loss requires restoration from a backup file, the recovery feature enables point‑in‑time restoration. When performing a MySQL (DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the DB is installed with the version from the backup point, and the recovery proceeds with the DB’s configuration information and data.
To recover MySQL (DBaaS), follow these steps.
- Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
- MySQL(DBaaS) resource On the list page, click the resource you want to restore. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Database Recovery button. 4. Go to the Database Recovery page.
- Database Recovery Configuration after entering the relevant information in the area, click the Complete button.
Category required statusDetailed description Recovery Type Required Set the point in time the user wants to recover - Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
- Custom point: Recover to a user-specified point within the range of recoverable backup times. The recoverable period depends on the Archive backup cycle setting, allowing recovery from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the desired date and time for the backup
Server name prefix Required Server name of the recovery DB - 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 24 vCores or more (to be provided later)
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute 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 Planned Compute Apply
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 source 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 source cluster
- In the recovery DB, only DATA, TEMP, and Archive purposes can be added
- After selecting Use, enter the storage purpose and capacity
- To add storage, click the Add button; to delete, click the x button
- Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created ___HTML_MARKER***
Database username Required Database username configured in the source DB Database Port number Required Database port number configured in the source DB IP access control Select IP address for accessing the recovery DB - Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.1/32,192.168.10.1/32), then 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, 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 interruption
- If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
tag Select Add Tag - Add Tag button after clicking, enter or select Key, Value values
Table. MySQL (DBaaS) recovery configuration items
2.3 - Configure Read Replica
Users can enter the required information for a Read Replica through the Samsung Cloud Platform Console and create the service using detailed options.
Configure Replica
You can create replica servers for read‑only or disaster‑recovery purposes through replica configuration. You can create up to 5 replicas per database.
To configure a Replica, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- On the MySQL(DBaaS) List page, click the resource to configure a Replica. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Replica configuration button. 4. Go to the Replica configuration page.
- After entering information in the Replica configuration area, click the Done button.
Category required statusDetailed 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
Table. MySQL (DBaaS) Replica configuration items
Reconfigure Replica
If a network outage or replication delay with the Master Cluster occurs, you can use the Replica reconstruction function to replicate the Master Cluster’s data again.
To reconfigure the Replica, follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- On the MySQL(DBaaS) List page, click the resource to reconfigure the Replica. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Replica reconstruction button. 4. Replica Reconfiguration Notification A popup window opens.
- Replica Reconfiguration Notification In the popup window, click the Confirm button.
Promoting a Replica Cluster to a Master Cluster
You can promote a configured Replica Cluster to a Master Cluster.
To promote a Replica Cluster to Master, follow these steps.
- Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
- MySQL(DBaaS) List On the page, click the resource to promote to Master. 3. MySQL(DBaaS) Details Go to the page.
- Click the More button and then click the Promote to Master button. 4. Master Promotion Notification The popup window opens.
- In the Master Promotion Notification popup, click the Confirm button.
2.4 - MySQL(DBaaS) Server Connection
Scenario Overview
MySQL(DBaaS) Server Connection scenario involves creating a Bastion host (Virtual Server) and a Database service, and accessing the DB service through the Bastion host. To reliably connect to MySQL (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, it is recommended to configure the Database service in a Private Subnet environment and place the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and a Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Scenario components
You can build the scenario using the following services.
| Service group | service | Detailed description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that lets users subdivide the network within a VPC to match their purpose and scale. | |
| Networking | VPC > Public IP | A service that reserves a public IP and allocates and releases it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the Internet | |
| Networking | Security Group | Virtual firewall that controls server traffic | |
| Database | MySQL(DBaaS) | A service that easily creates and manages MySQL in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- Since the default policy of a Security Group is Deny All, you must register only the allowed IPs.
- The All Open (Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
- By specifying the required IP and port and setting a policy, you can strengthen security.
Scenario configuration method
Create the services needed to build the scenario by following the steps below.
Set up the network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
1-1. Create VPC
- Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
- Click the VPC Creation button on the Service Home page. You will be taken to the VPC Creation page.
- On the VPC Creation page, enter the information required to create the service.
- Enter the IP range as
192.168.x.0/16.
- Enter the IP range as
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resources on the VPC List page.
1-2. Create Subnet
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
- Click the Create Subnet button. You will be taken to the Create Subnet page.
- On the Subnet Creation page, enter the information required to create the service.
- Select the Subnet type as General.
- Select a pre‑created VPC.
- Enter the IP range as
192.168.x.0/24.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, verify the created resources on the Subnet list page.
1-3. Create Internet Gateway
- Click the All Services > Networking > VPC menu. Go to the VPC’s Service Home page.
- On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
- Click the Create Internet Gateway button. You will be taken to the Create Internet Gateway page.
- On the Internet Gateway Creation page, enter the required information to create the service.
- Select a pre‑created VPC.
- In the Firewall usage option, select Use.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resource on the Internet Gateway List page.
1-4. Create Public IP
- Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Public IP menu. You will be taken to the Public IP List page.
- Click the Public IP Reservation button. You will be taken to the Public IP Reservation page.
- On the Public IP reservation page, enter the required information to reserve the service.
- In the Summary panel, verify the detailed information and estimated billing amount you generated, and click the Complete button.
- When creation is complete, check the created resources on the Public IP List page.
1-5. Create Security Group
- Click the All Services > Networking > Security Group menu. You will be taken to the Service Home page of the Security Group.
- Click the Create Security Group button on the Service Home page. You will be taken to the Create Security Group page.
- On the Security Group creation page, enter the required information for creating the service.
- Check the input information and click the Complete button.
- When creation is complete, verify the created resource on the Security Group List page.
Create Bastion host
This explains the process of configuring a Bastion Host where the Database access client must be installed.
2-1. Create Server Keypair
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
- Click the Create Keypair button. You will be taken to the Create Keypair page.
- Enter the required information needed to create a service on the Keypair creation page.
- Check the creation information and click the Complete button.
- The key can be downloaded only on the first attempt, and reissuance is not available.
- Please store the downloaded key in a secure location.
2-2. Create Bastion host
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Create Virtual Server button. You will be taken to the Create Virtual Server page.
- On the Virtual Server Creation page, enter the required information to create the service.
- Select Windows for the image.
- Select the pre-created VPC and Subnet.
- Click Use NAT, then select the reserved Public IP from 1-4. Create Public IP.
- Connect the Keypair created in 2-1. 서버 Keypair 생성하기.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resources on the Virtual Server List page.
2-3. Bastion host Check login ID and PW
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
- On the Virtual Serve List page, click the resource you created in [2-2. Bastion host creation]. You will be taken to the detailed information page of that resource.
- On the detail page, click the RDP password view button in the Keypair name field. The RDP password view popup will open.
- In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
- After attaching, click the Password Check button. The ID and Password for accessing the resource are displayed.
- The ID and password will later be used as credentials to access the Bastion host in 5-1. Bastion host Connecting.
Create Database
Explains the process of creating a Database service.
3-1. Create MySQL(DBaaS) Service
- Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) Create button. You will be taken to the MySQL(DBaaS) Create page.
- On the MySQL(DBaaS) Creation page, enter the required information needed to create the service.
- Select the pre‑created VPC and Subnet and connect them.
- Enter the database-related creation details on the required information input screen.
- Add the Bastion host IP in the IP access control settings.
- The Database Port defaults to 2866, but the user can also specify it.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resource on the MySQL(DBaaS) list page.
Configure Rules
It explains the process of configuring rules for a user to connect to the Bastion host and rules for connecting to the Database from the Bastion host.
4-1. Adding security rules to Security Group
- Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
- Click the Security Group menu on the Service Home page. You will be taken to the Security Group List page.
- Select the Security Group resource created in 1-5. Create Security Group. Navigate to the detailed information page for that resource.
- Click the Rules tab on the detail page. You will be taken to the Rules tab.
- On the Rules tab, click the Add Rule button. The Add Rule popup will appear.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
direction remote Target address Protocol Port Explanation Inbound CIDR User PC IP TCP 3389 (RDP) Bastion client PC → Bastion host Outbound CIDR DB IP TCP Database Port (manual entry) Bastion host → Database Table. Security Group rules that need to be added
4-2. Adding IGW Firewall Rule
- All Services > Networking > Firewall Click the menu. Go to the Service Home page of the Firewall.
- On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
- On the Firewall List page, select the Internet Gateway resource name created in 1-3. Create Internet Gateway. You will be taken to the detailed information page of that resource.
- Click the Rules tab on the detail page. You will be taken to the Rules tab.
- Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
origin address Destination address Protocol Port operation direction Explanation Bastion connection PC IP Bastion host IP TCP 3389(RDP) Allow Inbound User PC → Bastion host Table. Internet Gateway Firewall rules that should be added
Connect to Database
Describes the process of a user accessing the database via a DB client program.
This guide explains how to connect using MySQL Workbench. Since there are various database client programs and CLI utilities, you may install and use the tool that best fits your needs.
5-1. Connecting to Bastion host
- In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
- When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password verified in 2-3. Check the Bastion host access ID and PW and click the Confirm button.
5-2. Install DB access client program (MySQL Workbench) on the Bastion host
- Visit the official MySQL page and download the MySQL Workbench program.
- MySQL Workbench program download URL: https://dev.mysql.com/downloads/workbench
- Connect the user’s PC hard drive to upload the file to the Bastion host.
- In the Local Resources tab of the Remote Desktop Connection, click the Details button of the Local Devices and Resources item.
- Select the local disk where the file was downloaded on the drive, and click the OK button.
- Copy the downloaded file, upload it to the Bastion Host, and click the MySQL Workbench installer to install.
5-3. Connect to the Database using the DB client program (MySQL Workbench)
- Launch MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup appears.
- Manage Server Connection In the popup window, click the New button at the lower left, enter the Database server information created in 3-1. MySQL(DBaaS) 서비스 생성하기, and click the Test Connection button. A Password popup will appear.
Required input field input value Connection Name Custom (ex. service name) Host name Database server IP Port Database Port Username Database username Table.DB connection client program input fields - In the Password popup, enter the password you set in 3-1. MySQL(DBaaS) Create Service and click the OK button. When the operation completes successfully, click the OK button in the Manage Server Connection popup.
- Click Database > Connect to Database. The Connect to Database popup appears.
- Select the Connection Name registered in Stored Connection to perform a Database connection. After connecting, you can try simple Query, etc.
3 - API Reference
4 - CLI Reference
5 - Release Note
MySQL(DBaaS)
- You can set up a disaster-recovery Replica using the Replica configuration (Other Region) feature.
- Strengthen the latest security patches and stability through the OS (Kernel) upgrade feature.
- You can monitor metrics and logs by integrating with Servicewatch.
- Add MySQL (DBaaS) feature
- Add Second-Generation Server Type
- Add a 2nd‑generation (db2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, refer to MySQL(DBaaS) 서버 타입.
- DB user and access control management and Archive configuration feature added
- For detailed information, see DB User Management, DB Access Control Management, Archive Management
- DB Audit Log Export feature added
- For more details, refer to DB Log 내보내기
- Backup notification feature provided
- Provides notification functionality for backup success and failure. For more details, see Create Notification Policy.
- Add Migration feature
- Provides replication-based zero-downtime data migration functionality. For more details, see Configuring Migration.
- Block Storage type HDD, HDD_KMS type addition
- Add Second-Generation Server Type
- MySQL (DBaaS) feature change
- Add second-generation server type
- Add a 2nd‑generation (dbh2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, see mysql(DBaaS) 서버 타입.
- After the service is created, you can expand the configured Block Storage capacity.
- Server-specific network IP configuration feature added allows common or server-specific settings depending on the usage purpose.
- Add second-generation server type
- Samsung Cloud Platform common feature changes
- Account, IAM, Service Home, tags, and other common CX changes have been applied.
- A MySQL (DBaaS) service that enables easy creation and management of MariaDB in a web environment has been released.

