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.

Architecture
Figure. MySQL (DBaaS) Architecture

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.

serviceProvided versionEOS Date (Samsung Cloud Platform new creation stop date)EoTS Date (Community Technical Support End Date)
MySQL (Community)8.0.282026-03-192026-04-30
8.0.302026-03-192026-04-30
8.0.322026-03-192026-04-30
8.0.332026-03-192026-04-30
8.0.342026-03-192026-04-30
8.0.352026-03-192026-04-30
8.0.362026-03-192026-04-30
8.0.372026-03-192026-04-30
8.0.412026-03-192026-04-30
8.0.422026-03-192026-04-30
8.4.52031-12 (planned)2032-04-30
Table. MySQL (DBaaS) engine versions provided
information

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
CategoryExampleDetailed description
Server typeStandardProvided server types
  • Standard: Standard configuration (vCPU, Memory) commonly used
  • High Capacity: Large server specifications of 24 vCores or more
Server specificationsdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) commonly used
  • dbH2: Large-capacity server specifications
    • Provides servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory 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. Please refer to the guide provided for each service and prepare in advance.

Service CategoryserviceDetailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
Table. MySQL (DBaaS) pre-service

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
exampleDetailed description
Server typeStandardProvided server type classifications
  • Standard: Configured with the commonly used standard specifications (vCPU, Memory)
  • High Capacity: Large-capacity server specifications exceeding Standard
Server specificationsdb1Provided server type classification and generation
  • db1: indicates a standard specification, and 1 denotes the generation
  • dbh2: h indicates a high-capacity server specification, and 2 denotes the generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory 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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. MySQL (DBaaS) server type specifications - db1 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb2v2m42 vCore4 GBUp to 10 Gbps
Standarddb2v2m82 vCore8 GBUp to 10 Gbps
Standarddb2v2m162 vCore16 GBUp to 10 Gbps
Standarddb2v2m242 vCore24 GBUp to 10 Gbps
Standarddb2v2m322 vCore32 GBUp to 10 Gbps
Standarddb2v4m84 vCore8 GBUp to 10 Gbps
Standarddb2v4m164 vCore16 GBUp to 10 Gbps
Standarddb2v4m324 vCore32 GBUp to 10 Gbps
Standarddb2v4m484 vCore48 GBUp to 10 Gbps
Standarddb2v4m644 vCore64 GBUp to 10 Gbps
Standarddb2v6m126 vCore12 GBUp to 10 Gbps
Standarddb2v6m246 vCore24 GBUp to 10 Gbps
Standarddb2v6m486 vCore48 GBUp to 10 Gbps
Standarddb2v726 vCore72 GBUp to 10 Gbps
Standarddb2v6m966 vCore96 GBUp to 10 Gbps
Standarddb2v8m168 vCore16 GBUp to 10 Gbps
Standarddb2v8m328 vCore32 GBUp to 10 Gbps
Standarddb2v8m648 vCore64 GBUp to 10 Gbps
Standarddb2v8m968 vCore96 GBUp to 10 Gbps
Standarddb2v8m1288 vCore128 GBUp to 10 Gbps
Standarddb2v10m2010 vCore20 GBUp to 10 Gbps
Standarddb2v10m4010 vCore40 GBUp to 10 Gbps
Standarddb2v10m8010 vCore80 GBUp to 10 Gbps
Standarddb2v10m12010 vCore120 GBUp to 10 Gbps
Standarddb2v10m16010 vCore160 GBUp to 10 Gbps
Standarddb2v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb2v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb2v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb2v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb2v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb2v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb2v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb2v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb2v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb2v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb2v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb2v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb2v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb2v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb2v16m25616 vCore256 GBUp 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
  • Networking speed up to 25 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBMaximum 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBMaximum 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBMaximum 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBMaximum 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBUp to 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBMaximum 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBMaximum 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBMaximum 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBMaximum 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBMaximum 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBMaximum 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBMaximum 25 Gbps
Table. MySQL (DBaaS) server type specifications - dbh2 server type

1.2 - Monitoring metrics

Cloud Monitoring Service Termination Notice

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.

  1. 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.
  2. 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.
  • 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**.

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 itemsDetailed descriptionunit
Active LocksNumber of Active Lockscnt
Active SessionsNumber of Active Sessionscnt
Binary Log Used [MB]binary log usageMB
Connection Usage [Total]DB connection session usage%
ConnectionsNumber of connectionscnt
Connections [MAX]Connection countcnt
Connectionsmax connected threads countcnt
Data Directory Used [MB]data directory usageMB
Instance Status [PID]mysqld process pidpid
Open FilesNumber of open DB filescnt
Open Files [MAX]Number of DB files that can be openedcnt
Open Files UsageDB file maximum count usage rate%
Relay Log Used [MB]relay log usage (MB)MB
Running Threadsrunning thread countcnt
Safe PIDsafe program pidpid
Slave Behind Master secondsTime difference with the master nodesec
SlowqueriesNumber 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 UsedTablespace usageMB
Tablespace Used [Total]Total tablespace usageMB
Transaction Time [Long]Maximum transaction execution timesec
Wait LocksNumber of sessions blocked for more than 60 seconds by lockcnt
Table. MySQL(DBaaS) Monitoring Metrics

1.3 - ServiceWatch Metrics

MySQL sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1‑minute interval.

Reference
For checking metrics in ServiceWatch, refer to the ServiceWatch guide.

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 itemsunitDetailed descriptionmeaningful statistics
CPUCPU UsagePercentCPU usage
  • maximum
DiskDisk UsagePercentDisk usage
  • Maximum
DiskDisk Write BytesBytes/SecondWrite throughput (bytes/second) on block device
  • average
  • maximum
  • minimum
DiskDisk Read BytesBytes/SecondRead capacity (bytes/second) from block device
  • average
  • maximum
  • minimum
DiskDisk Write RequestsCount/SecondNumber of write requests on block device (requests per second)
  • average
  • maximum
  • minimum
DiskDisk Read RequestsCount/SecondNumber of read requests on block device (requests per second)
  • average
  • maximum
  • minimum
DiskAverage Disk I/O Queue SizeNoneAverage queue length of requests issued to the block device
  • average
  • maximum
  • minimum
DiskDisk I/O UtilizationPercentThe proportion of time the block device actually spent handling I/O operations
  • average
  • maximum
  • minimum
MemoryMemory UsagePercentMemory usage
  • Maximum
NetworkNetwork In BytesBytes/SecondReceived data rate (bytes/second) on the network interface
  • average
  • maximum
  • minimum
NetworkNetwork Out BytesBytes/SecondTransmitted capacity (bytes/second) on the network interface
  • average
  • maximum
  • minimum
NetworkTCP ConnectionsCount/SecondCurrent total number of successfully established TCP connections
  • average
  • maximum
  • minimum
NetworkNetwork In PacketsCountNumber of packets received on the network interface
  • average
  • maximum
  • minimum
NetworkNetwork Out PacketsCountNumber of packets transmitted on the network interface
  • average
  • maximum
  • minimum
NetworkNetwork In DroppedCountNumber of packet drops received on the network interface
  • average
  • maximum
  • minimum
NetworkNetwork Out DroppedCountNumber of packet drops transmitted from the network interface
  • average
  • maximum
  • minimum
NetworkNetwork In ErrorsCountNumber of packet errors received on the network interface
  • average
  • maximum
  • minimum
NetworkNetwork Out ErrorsCountNumber of packet errors transmitted on the network interface
  • average
  • maximum
  • minimum
Table. OS basic metrics

MySQL Basic Metrics

Classification
Performance itemsunit
Detailed description
meaningful statistics
ActivelockActive locksCountNumber of transactions in lock wait (Lock Wait) state for 1 minute (60 seconds) or longer in the InnoDB storage engine
  • Total
  • Average
  • Maximum
  • Minimum
ActivesessionActive sessionsCountNumber of active sessions
  • Total
  • Average
  • Maximum
  • Minimum
ActivesessionConnection usagePercentDatabase connection session utilization
  • Total
  • Average
  • Maximum
  • Minimum
ActivesessionConnectionsCountDB connection session
  • Total
  • Average
  • Maximum
  • Minimum
DatafileCurrent open filesCountNumber of file descriptors opened by the DB
  • Total
  • Average
  • Maximum
  • Minimum
DatafileMax open filesCountMaximum number of file descriptors the DB can open
  • Total
  • Average
  • Maximum
  • Minimum
DatafileOpen files usagePercentDB file maximum count utilization
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnoDB buffer pool hit ratioPercentThe proportion of data read directly from memory without accessing the disk
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnodb row lock wait transactionsCountCurrent number of InnoDB transactions waiting for a row lock
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnoDB row lock timeMillisecondsTotal time waited due to InnoDB row locks (in milliseconds)
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnoDB deadlocksCount/MinuteNumber of deadlock occurrences
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBTable lock waitsCount/MinuteNumber of waits that occurred to acquire a table lock
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBTemp disk tablesCountNumber of Temp Tables created on disk
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnodb log waitsCountNumber of times waited to write the redo log to disk
  • Total
  • Average
  • Maximum
  • Minimum
StateInstance stateNoneCheck MySQL DB Process status up/down
  • 1 - Up
  • 0 - Down
-
StateSlave behind master seconds(8.0)
(Replica Only)
SecondsReplica latency (unit: seconds)
  • Total
  • Average
  • Maximum
  • Minimum
StateSlave io thread running(8.0)
(Replica Only)
NoneI/O Thread status
  • 1 - Running
  • 0 - Down
-
StateSlave SQL thread running(8.0)
(Replica Only)
NoneSQL Thread status
  • 1 - Running
  • 0 - Down
-
StateReplica behind master seconds(8.4+)
(Replica Only)
SecondsReplica latency (unit: seconds)
  • Total
  • Average
  • Maximum
  • Minimum
StateReplica io thread running(8.4+)
(Replica Only)
NoneI/O Thread status
  • 1 - Running
  • 0 - Down
-
StateReplica SQL thread running(8.4+)
(Replica Only)
NoneSQL Thread status
  • 1 - Running
  • 0 - Down
-
TablespaceTablespace usedMegabytesTablespace usage
  • Total
  • Average
  • Maximum
  • Minimum
TablespaceTablespace used(TOTAL)MegabytesTablespace usage (total)
  • Total
  • Average
  • Maximum
  • Minimum
TransactionsSlow queriesCountNumber of queries that run for more than 10 seconds
  • Total
  • Average
  • Maximum
  • Minimum
TransactionsLong transaction timeSecondsLong Transaction time
  • Total
  • Average
  • Maximum
  • Minimum
TransactionsWait locksCountNumber of sessions waiting for lock
  • Total
  • Average
  • Maximum
  • Minimum
TransactionsSQL Queries/MinuteCount/MinuteQueries executed per minute
  • Total
  • Average
  • Maximum
  • Minimum
Table. MySQL basic metrics

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.

Cloud Monitoring Service Termination Notice

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.

  1. 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.
  2. 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.
  • 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**.

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.

information
  • 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.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the Create MySQL(DBaaS) button. 2. Go to the MySQL(DBaaS) Creation page.
  3. 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 status
      Detailed description
      Image versionEssentialProvide 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 status
      Detailed description
      Server name PrefixRequiredThe 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 nameEssentialCluster name of DB servers
      • Enter using English letters, 3 ~ 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type for DB installation
      • Standard: standard specifications commonly used
      • High Capacity: large‑capacity server with 24 vCores or more
      Service Type > Planned ComputeSelectionStatus 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
      Service Type > Block StorageRequiredBlock 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
      • 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 /tmp area 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 configurationSelectRedundancy configuration
      • When redundancy is used, the DB instance is configured as separate Active DB and Standby DB
      Network > Common SettingsRequiredNetwork 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 SettingsRequiredNetwork 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 controlSelectService 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 periodSelectDatabase 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
    • Enter required database configuration information In this section, enter or select the required information.
      Category
      Required status
      Detailed description
      Database nameRequiredServer name applied during DB installation
      • must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
      Database usernameRequiredDatabase 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 passwordrequiredPassword to use when accessing the DB
      • Enter 8 to 30 characters, including letters, numbers, and special characters (excluding )
      Database password verificationRequiredRe-enter the same password to use for DB access
      Database Port numberEssentialPort number required for DB connection
      • Enter DB port within the range 1200 ~ 65535
      Backup > UseSelectBackup usage
      • Use to select and set backup file retention period, backup start time, and Archive backup interval
      Backup > Retention periodSelectBackup 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 PeriodSelectBackup 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 cycleSelectionArchive 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
      ParameterRequiredParameters 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 setRequiredCharacter encoding to use for the database
      Table case sensitivitySelectDB Table case sensitivity
      time zoneRequiredStandard time zone for the database
      ServiceWatch log collectionSelectionWhether to collect ServiceWatch logs
      • Select Use to enable the ServiceWatch log collection feature
      • 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 status
      Detailed description
      TagSelectAdd 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
  4. 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
  3. 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.
      CategoryDetailed description
      Cluster statusCluster 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 controlButtons 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 featuresCluster 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 terminationCancel service button
      Table. MySQL (DBaaS) status information and additional features

Detailed information

MySQL (DBaaS) List page lets you view detailed information of the selected resource and edit the information if needed.

CategoryDetailed description
Server InformationServer information configured in this cluster
  • Category: Server type (Active, Standby, Replica)
  • Server Name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the DB service, it refers to the cluster SRN
Resource nameResource name
  • In the DB service, it refers to the cluster name
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation date and timeService creation date and time
ModifierUser who edited the service information
Modification dateDate and time the service information was modified
Image versionInstalled DB image and version information
  • If a version upgrade is required, click the Edit icon to configure
Cluster typeCluster types (Master Cluster, Replica Cluster, Migration Cluster)
Cluster nameCluster name of the DB servers
Master cluster nameReplica’s Master cluster name
  • If it is the Replica’s detailed information, it can be confirmed
Database nameServer name applied during DB installation
Database usernameDB user name
Planned ComputeResources with Planned Compute configured
maintenance periodDB Maintenance Period Status
  • If you need to set the maintenance period, click the Edit icon to configure
BackupBackup configuration status
  • If backup configuration is required, click the Edit icon to set it
ServiceWatch log collectionServiceWatch Log Collection Configuration Status
  • If log collection configuration is required, click the Edit icon next to Log Collection to configure
DB character setEncoding method to be used for the DB
Table case sensitivityDB Table case sensitivity
time zoneStandard time zone for the database
VIPVirtual IP information
  • can be checked only when high availability is configured
NetworkNetwork information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP))
IP access controlService access policy configuration
  • If you need to add or remove IPs, click the Edit icon to configure
Active & StandbyActive/Standby server type, base OS, additional Disk information
  • If you need to modify the server type, click the Edit icon next to the server type to set it. See the server type modification procedure in Server Type Change
    • Modifying the server type requires a server reboot
  • If you need to expand storage, click the Edit icon next to the storage capacity to expand it. Refer to the storage expansion procedure in Storage Expansion
  • If you need to add storage, click the Add Disk button next to the additional Disk to add it. Refer to the storage addition procedure in Add Storage
Table. MySQL (DBaaS) Database detailed information items

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.

CategoryDetailed description
Master informationName of the Master cluster
Replica countNumber of Replicas created in the Master cluster
Replica statusReplica server status in the Master cluster
  • The server name, status query, status details, and status check time can be viewed
  • To view the Replica status, click the Status Query button
    • While the query is in progress, the cluster remains in Synchronizing state, and once the query completes, the cluster changes to Running state
Table. Detailed information items in the Replica Information tab

tag

MySQL(DBaaS) List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the list of previously created Keys and Values
Table. MySQL (DBaaS) Tag Tab Items

Work History

MySQL(DBaaS) List page allows you to view the operation history of the selected resource.

CategoryDetailed description
Task History ListResource Change History
  • Operation Timestamp, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, Operator Information Check
Table. Work History Tab Detailed Information Items

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.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List page, click the resource to control its operation. 3. MySQL(DBaaS) Details Go to the page.
  4. 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.

  1. Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
  3. MySQL (DBaaS) List page, click the resource to view its service status. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
  5. 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.

Caution
  • 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.
  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List page: click the resource for which you want to change the server type. 3. Navigate to the MySQL (DBaaS) Details page.
  4. 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.
  5. 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.

Caution
  • 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource to add storage. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
  5. 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.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
  3. MySQL(DBaaS) List page, click the resource whose server type you want to change. 3. MySQL(DBaaS) Details Go to the page.
  4. 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.
  5. 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.

Caution
  • 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
  3. On the MySQL(DBaaS) List page, select the resource to cancel and click the Cancel Service button.
  4. 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. 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.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
  5. Parameter Management popup window, click the Search button. The Search Notification popup window opens.
  6. 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. 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.
  4. Click the More button, then click the Parameter Management button. The Parameter Management popup opens.
  5. Parameter Management in the popup window, click the Search button. The Search Notification popup opens.
  6. Lookup Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
  7. If a modification is needed, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
  8. When the input is complete, click the Complete button.
Reference

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.

ItemDetailed descriptionWhether to restart
character-set-serverSpecify the default character setRestart required
collation-serverSpecify default collation (Collation)Restart required
init_connectSQL statements executed when the client connects to the databaseNo restart required
Table. Parameter configuration items

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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. 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.
  4. Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
  5. 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the MySQL(DBaaS) Service Home page.
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) list page.
  3. 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.
  4. Click the More button, then click the DB User Management button. You will be directed to the DB User Management page.
  5. On the DB User Management page, click the Search button. The query may take a short time.
  6. If modification is needed, click the Edit button, and change the status field value or enter remarks.
  7. 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.

information
Before setting DB access control, perform a DB user lookup. For DB user lookup, please refer to DB 사용자 관리하기.

Query DB Access Control

Follow these steps to query DB users with IP access control enabled.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List page, click the resource you want to manage access control for. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. Click the MySQL(DBaaS) menu on the Service Home page. Navigate to the MySQL(DBaaS) List page.
  3. 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.
  4. Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. DB Access Control Management page, click the Search button. Retrieving the data may take a moment.
  6. After the query completes, click the Add button. The Add DB Access Control popup window opens.
  7. Add DB Access Control In the popup window, select the DB username and enter the IP address.
  8. When the input is complete, click the Complete button.

Delete DB access control

To delete IP access control, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. 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.
  4. Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. On the DB Access Control Management page, click the View button. Retrieving the data may take a short while.
  6. When the query is complete, click the Delete button. The Delete popup window opens.
  7. 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.

Information
When creating a service, the default setting uses Archive mode, and the retention period is 3 days.

Configure Archive mode

To set Archive mode, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. 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.
  4. Click the More button and click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
  5. On the Archive Settings Management page, click the Search button. Retrieval may take a short time.
  6. Click the Edit button and select the usage status and retention period.
  7. When the edit is complete, click the Done button.

Delete Archive file

To delete the Archive file, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. 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.
  4. Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
  5. 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.

information
  • 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the MySQL(DBaaS) Service Home page.
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. 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.
  4. Click the More button, then click the Export DB Log button. You will be taken to the Export DB Log page.
  5. On the DB Log Export page, click the Register button. You will be taken to the DB Log Export Register page.
  6. After entering the required information on the DB Log Export Registration page, click the Complete button.
    CategoryRequired
    Detailed description
    Log typeRequiredLog type to be saved
    Save bucket nameRequiredObject Storage bucket name to be saved
    Authentication key > Access keyRequiredAccess key to access the Object Storage you want to store
    Authentication key > Secret keyRequiredSecret key to access the Object Storage you want to store
    File creation cycleRequiredFile creation interval in Object Storage
    Whether to delete the original logSelectionWhether 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. 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.
  4. Click the More button and then click the Export DB Log button. You will be taken to the Export DB Log page.
  5. 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.

Warning
  • 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. Click the resource to upgrade the version on the MySQL(DBaaS) List page. It navigates to the MySQL(DBaaS) Details page.
  4. Click the Edit button of the Image version item. The Version Upgrade popup window opens.
  5. Version Upgrade In the popup, select the updated version and backup setting, then click the Confirm button.
  6. 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.

Information
For detailed Migration configuration guide, please refer to Architecture Center > Migration Guide.

To configure Migration, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource to migrate. You will be taken to the MySQL(DBaaS) Detail page.
  4. Click the More button and then click the Migration Configuration button. The Migration Configuration popup window opens.
  5. In the popup window, review the instructions and click the Confirm button. You will be taken to the Migration configuration page.
  6. On the Migration configuration page, after entering the required information, click the Check connection button.
  7. When the connection is complete, click the Complete button.
    CategoryRequired
    Detailed description
    Source DB Database nameRequiredDatabase name of the source DB to be migrated
    Source DB IPRequiredIP of the Source DB that is the migration target
    Source DB PortRequiredPort of the Source DB to be migrated
    Source DB usernameRequiredUser name of the Source DB to be migrated
    Source DB passwordRequiredPassword 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.

Caution
When the master is promoted, synchronization with the source DB that is the migration target is halted.

To promote the Migration Cluster to Master, follow the steps below.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource to promote to Master. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button, then click the Master promotion button. The Master promotion notification popup opens.
  5. 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.

Caution
  • 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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource to upgrade the OS Kernel. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button, then click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup opens.
  5. 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.

Caution
  • 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.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List page, click the resource for which you want to configure backup. 3. MySQL(DBaaS) Details Go to the page.
  4. Click the Edit button of the backup item. 4. Backup Settings popup window opens.
  5. 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.

Check backup history

information
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on setting up notification policies, refer to 알림 정책 생성하기.

To view the backup history, follow these steps.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL (DBaaS) List Navigate to the page.
  3. 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.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.

Delete backup files

Caution
Backup files cannot be restored after deletion. Please be sure to verify whether the data is unnecessary before deleting it.

To delete the backup history, follow these steps.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Go to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List On the page, click the resource to view the backup history. 3. MySQL(DBaaS) Details Go to the page.
  4. Click the Backup History button. 4. Backup History popup window opens.
  5. 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.

Caution
Performing recovery requires at least twice the capacity of the Disk data type. If there is insufficient disk space, the recovery may fail.

To recover MySQL (DBaaS), follow these steps.

  1. Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
  3. MySQL(DBaaS) resource On the list page, click the resource you want to restore. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Database Recovery button. 4. Go to the Database Recovery page.
  5. Database Recovery Configuration after entering the relevant information in the area, click the Complete button.
    Category
    required status
    Detailed description
    Recovery TypeRequiredSet 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 prefixRequiredServer 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 nameRequiredCluster name of the recovery DB
    • Enter using English letters, 3 ~ 20 characters
    • A cluster is a unit that groups multiple servers
    Service Type > Server TypeRequiredServer 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 ComputeSelectionStatus 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
    Service Type > Block StorageRequiredBlock 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 usernameRequiredDatabase username configured in the source DB
    Database Port numberRequiredDatabase port number configured in the source DB
    IP access controlSelectIP 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 periodSelectDatabase 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.
    tagSelectAdd 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.

Information
To configure a disaster recovery Replica, please create it via Replica Setup (Other Region).

To configure a Replica, follow these steps.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
  3. On the MySQL(DBaaS) List page, click the resource to configure a Replica. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Replica configuration button. 4. Go to the Replica configuration page.
  5. After entering information in the Replica configuration area, click the Done button.
    Category
    required status
    Detailed description
    RegionrequiredRegion to configure the Replica
    • Replica configuration (Other Region) is displayed only when selected
    Replica countRequiredNumber 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 nameRequiredReplica 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 TypeRequiredReplica server type
    • Standard: standard specification commonly used
    • High Capacity: large-capacity server with 24 vCores or more
    Service Type > Planned ComputeSelectionStatus 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
    IP access controlSelectService 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 periodSelectDatabase 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.
    TagSelectAdd 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.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
  3. On the MySQL(DBaaS) List page, click the resource to reconfigure the Replica. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Replica reconstruction button. 4. Replica Reconfiguration Notification A popup window opens.
  5. 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.

Caution
When the Master is promoted, synchronization with the existing Master Cluster is stopped.

To promote a Replica Cluster to Master, follow these steps.

  1. Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
  3. MySQL(DBaaS) List On the page, click the resource to promote to Master. 3. MySQL(DBaaS) Details Go to the page.
  4. Click the More button and then click the Promote to Master button. 4. Master Promotion Notification The popup window opens.
  5. 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.

Architecture
Figure. MySQL (DBaaS) server connection architecture

Scenario components

You can build the scenario using the following services.

Service group
service
Detailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
NetworkingVPC > SubnetA service that lets users subdivide the network within a VPC to match their purpose and scale.
NetworkingVPC > Public IPA service that reserves a public IP and allocates and releases it to Compute resources
NetworkingVPC > Internet GatewayA service that connects VPC resources to the Internet
NetworkingSecurity GroupVirtual firewall that controls server traffic
DatabaseMySQL(DBaaS)A service that easily creates and manages MySQL in a web environment
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeVirtual Server > KeypairEncryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
  • 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

For detailed creation steps, refer to the Networking > VPC > How-to guides guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
  2. Click the VPC Creation button on the Service Home page. You will be taken to the VPC Creation page.
  3. On the VPC Creation page, enter the information required to create the service.
    • Enter the IP range as 192.168.x.0/16.
  4. 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

For detailed creation steps, refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
  2. On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
  3. Click the Create Subnet button. You will be taken to the Create Subnet page.
  4. 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.
  5. 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

For detailed creation steps, please refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click the All Services > Networking > VPC menu. Go to the VPC’s Service Home page.
  2. On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
  3. Click the Create Internet Gateway button. You will be taken to the Create Internet Gateway page.
  4. 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.
  5. 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

For detailed creation steps, refer to the Networking > VPC > How-to guides > Public IP guide.
  1. Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
  2. On the Service Home page, click the Public IP menu. You will be taken to the Public IP List page.
  3. Click the Public IP Reservation button. You will be taken to the Public IP Reservation page.
  4. On the Public IP reservation page, enter the required information to reserve the service.
  5. 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

For detailed creation instructions, refer to the Networking > Security Group > How-to guides guide.
  1. Click the All Services > Networking > Security Group menu. You will be taken to the Service Home page of the Security Group.
  2. Click the Create Security Group button on the Service Home page. You will be taken to the Create Security Group page.
  3. On the Security Group creation page, enter the required information for creating the service.
  4. 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

For detailed creation instructions, refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
  3. Click the Create Keypair button. You will be taken to the Create Keypair page.
  4. Enter the required information needed to create a service on the Keypair creation page.
  5. 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

For detailed creation instructions, see the Compute > Virtual Server > How-to guides guide.
  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Create Virtual Server button. You will be taken to the Create Virtual Server page.
  3. On the Virtual Server Creation page, enter the required information to create the service.
  4. 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

  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
  3. 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.
  4. On the detail page, click the RDP password view button in the Keypair name field. The RDP password view popup will open.
  5. In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
  6. After attaching, click the Password Check button. The ID and Password for accessing the resource are displayed.

Create Database

Explains the process of creating a Database service.

3-1. Create MySQL(DBaaS) Service

For detailed creation steps, refer to the Database > MySQL(DBaaS) > How-to guides guide.
  1. Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) Create button. You will be taken to the MySQL(DBaaS) Create page.
  3. 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.
  4. 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

For detailed creation instructions, refer to the Networking > Security Group > How-to guides guide.
  1. Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
  2. Click the Security Group menu on the Service Home page. You will be taken to the Security Group List page.
  3. Select the Security Group resource created in 1-5. Create Security Group. Navigate to the detailed information page for that resource.
  4. Click the Rules tab on the detail page. You will be taken to the Rules tab.
  5. On the Rules tab, click the Add Rule button. The Add Rule popup will appear.
  6. Add Rule In the popup window, enter the rule below, and click the Confirm button.
    directionremoteTarget addressProtocolPortExplanation
    InboundCIDRUser PC IPTCP3389 (RDP)Bastion client PC → Bastion host
    OutboundCIDRDB IPTCPDatabase Port (manual entry)Bastion host → Database
    Table. Security Group rules that need to be added

4-2. Adding IGW Firewall Rule

For detailed creation instructions, see the Networking > Firewall > How-to guides guide.
  1. All Services > Networking > Firewall Click the menu. Go to the Service Home page of the Firewall.
  2. On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
  3. 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.
  4. Click the Rules tab on the detail page. You will be taken to the Rules tab.
  5. Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
  6. Add Rule In the popup window, enter the rule below, and click the Confirm button.
    origin addressDestination addressProtocolPortoperationdirectionExplanation
    Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser 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

  1. 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.
  2. 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

  1. Visit the official MySQL page and download the MySQL Workbench program.
  2. Connect the user’s PC hard drive to upload the file to the Bastion host.
  3. In the Local Resources tab of the Remote Desktop Connection, click the Details button of the Local Devices and Resources item.
  4. Select the local disk where the file was downloaded on the drive, and click the OK button.
  5. 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)

  1. Launch MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup appears.
  2. 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 fieldinput value
    Connection NameCustom (ex. service name)
    Host nameDatabase server IP
    PortDatabase Port
    UsernameDatabase username
    Table.DB connection client program input fields
  3. 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.
  4. Click Database > Connect to Database. The Connect to Database popup appears.
  5. Select the Connection Name registered in Stored Connection to perform a Database connection. After connecting, you can try simple Query, etc.

3 - API Reference

API Reference

4 - CLI Reference

CLI Reference

5 - Release Note

MySQL(DBaaS)

2026.03.19
FEATURE Configure Replica for disaster recovery, add OS (Kernel) upgrade feature, provide Servicewatch integration feature
  • 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.
2025.07.01
FEATURE User (access control) management, Archive configuration feature, DB Audit Log export feature added, backup notification feature provided, migration feature added
  • Add MySQL (DBaaS) feature
2025.02.27
FEATURE Add server type and per‑server IP setting, add Block Storage capacity expansion feature
  • 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.
  • Samsung Cloud Platform common feature changes
    • Account, IAM, Service Home, tags, and other common CX changes have been applied.
2024.10.01
NEW MySQL(DBaaS) service official version release
  • A MySQL (DBaaS) service that enables easy creation and management of MariaDB in a web environment has been released.