The page has been translated by Gen AI.

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 content of the Active server changes, it is synchronously replicated to the Standby server, and up to five read-only servers called Replicas for read load balancing and disaster recovery (DR) are provided. Additionally, to prepare for issues with the DB server or data, it offers an automatic backup function at user-specified times, supporting data recovery at the desired point in time.

Architecture
Figure. MySQL(DBaaS) Architecture

Provided Features

MySQL(DBaaS) provides the following features.

  • Auto Provisioning (Auto Provisioning): Installation and configuration of Database (DB) is possible via UI, and it provides an Active-standby redundancy configuration based on storage replication. In case of an Active server failure, automatic failover to Standby occurs.
  • Operation Control Management: Provides functionality to control the status of running servers. In addition to start and stop, restart is possible if there is a DB issue or to apply configuration values. When configured for high availability (HA), users can directly perform node switching between Active-Standby via Switch-over.
  • Backup and Recovery: Provides a data backup function based on its own backup commands. The backup time window and storage agency can be set by the user, and additional fees are incurred based on backup size. It also provides a recovery function for backed-up data, creating a separate DB when the user performs a recovery, and the recovery proceeds to the point in time selected by the user (backup save point, user-specified point). When recovering to a user-specified point, the recovery point can be set up to 5 minutes/10 minutes/30 minutes/1 hour before the stored backup file and archive file.
  • Version Management: Provides version upgrade (Minor) functionality for some feature improvements and security patches. Whether to perform a backup for the version upgrade can be selected by the user, and if a backup is performed, the data is backed up before applying the patch, then the DB engine is updated.
  • Replica configuration: You can add up to 5 read-only Read Replicas, enabling read performance scaling and load balancing.
  • Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
  • Service Status Query: Retrieves the final status of the current DB service.
  • Monitoring: CPU, memory, DB performance monitoring information can be checked via the Cloud Monitoring service.
  • DB User Management: View and manage 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.
  • Archive Management: You can set the Archive file retention period (1 day~35 days) within the DB server and configure the Archive mode (On/Off).
  • DB Log Export: You can export stored logs to the user’s Object Storage through Audit settings.
  • Migration: Synchronize data in real time with the operating database, and support migration using the Replication method without service interruption.

Components

MySQL (DBaaS) provides pre-validated engine versions and various server types according to the open-source support policy. Users can select and use them according to the scale of the service they want 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 (scheduled)2026-04-30
8.0.302026-03 (scheduled)2026-04-30
8.0.322026-03 (scheduled)2026-04-30
8.0.332026-03 (scheduled)2026-04-30
8.0.342026-03 (scheduled)2026-04-30
8.0.352026-03 (scheduled)2026-04-30
8.0.362026-03 (scheduled)2026-04-30
8.0.372026-03 (scheduled)2026-04-30
8.0.412026-03 (scheduled)2026-04-30
8.0.422026-03 (scheduled)2026-04-30
8.4.52031-12 (planned)2032-04-30
Table. MySQL(DBaaS) Engine Versions Provided

Server Type

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

For detailed information about the server types provided by MySQL(DBaaS), please refer to MySQL(DBaaS) Server Types.

Standard db1v2m4









  




Category
Example
Detailed Description






Server Type
Standard
Provided Server Types
  • Standard: Standard specifications (vCPU, Memory) configuration commonly used
  • High Capacity: Large server specifications of 24 vCores or more





Server Specifications
db1
Provided Server Specifications
  • db1: Standard specifications (vCPU, Memory) configuration commonly used
  • dbH2: Large-scale server specifications
    • Provides servers with 24 vCores or more





Server specifications
v2
Number of vCores
  • v2: 2 virtual cores





Server specifications
m4
Memory capacity
  • m4: 4GB Memory








  Table. MySQL(DBaaS) server type components







# Pre-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 for details and prepare in advance.<br>








  




Service Category
Service
Detailed Description






Networking
VPC
A service that provides an independent virtual network in a cloud environment







  Table. MySQL (DBaaS) Pre-service
Release Note
Server Type