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 where MySQL installation is automated through a web-based Console and management functions for operation can be performed.

MySQL(DBaaS) is designed with a high availability architecture that considers storage-based data replication and minimization of failover time. To prevent data loss, when content in the Active server is changed, it is synchronously replicated to the Standby server, and up to 5 read-only servers called Replicas are provided for read load distribution and disaster recovery (DR). Additionally, to prepare for problems with the DB server or data, it provides automatic backup at a user-specified time, enabling data recovery at a desired point in time.

Architecture
Figure. MySQL(DBaaS) Architecture

Provided Features

MySQL(DBaaS) provides the following features.

  • Auto Provisioning: Database (DB) installation and configuration is possible through UI, and Active-standby redundancy configuration based on storage replication is provided. When the Active server fails, it automatically fails over to Standby.
  • Operation Control Management: Provides functionality to control the status of running servers. In addition to start and stop, restart is possible when there is an issue with the DB or to reflect configuration values. When configured with high availability (HA), users can directly switch between Active-Standby nodes through Switch-over.
  • Backup and Recovery: Provides data backup functionality based on its own backup commands. Backup time and retention period can be set by the user, and additional charges occur according to backup capacity. Additionally, it provides recovery functionality for backed-up data, and when the user performs recovery, a separate DB is created and recovery proceeds to the point in time selected by the user (backup storage 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 ago based on stored backup files and archive files.
  • Version Management: Provides version upgrade (Minor) functionality for some feature improvements and security patches. Users can select whether to perform backup according to version upgrade, and if backup is performed, the data is backed up before patching and then the DB engine is updated.
  • Replica Configuration: Up to 5 Read Replicas can be configured in the same/different region for read load distribution and disaster recovery (DR).
  • Parameter Management: DB configuration parameters for performance improvement and security can be modified.
  • Service Status Check: Checks the final status of the current DB service.
  • Monitoring: CPU, memory, and performance monitoring information can be checked through Cloud Monitoring and Servicewatch.
  • DB User Management: Manages by checking DB account (user) information registered in the DB.
  • DB Access Control Management: Access allowed IP registration and cancellation based on DB accounts registered in the DB is possible.
  • Archive Management: Archive file retention period (1 day ~ 35 days) in the DB server and Archive mode (On/Off) can be set.
  • DB Log Export: Logs stored through Audit settings can be exported to the user’s Object Storage.
  • Migration: Supports migration using Replication method by synchronizing data in real-time with the operating database without service interruption.
  • OS Kernel Upgrade: OS Kernel can be upgraded for some feature improvements and security patch application.

Components

MySQL(DBaaS) provides pre-verified 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 stops is set to 6 months before the EoTS date.

According to the supplier’s policy, EOS and EoTS dates may change, so 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 (Scheduled)2032-04-30
Table. MySQL(DBaaS) Provided Engine Versions

Server Type

The server type supported by MySQL(DBaaS) is in the following format.

For details on the server types provided by MySQL(DBaaS), refer to MySQL(DBaaS) Server Types.

Standard db1v2m4
ClassificationExampleDetailed Description
Server TypeStandardProvided server types
  • Standard: Standard specifications (vCPU, Memory) generally used
  • High Capacity: Large capacity server specifications with 24 vCore or more
Server Specificationdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) generally used
  • dbH2: Large capacity server specifications
    • Provides servers with 24 vCore or more
Server Specificationv2Number of vCores
  • v2: 2 virtual cores
Server Specificationm4Memory capacity
  • m4: 4GB Memory
Table. MySQL(DBaaS) Server Type Components

Prerequisite Services

This is a list of services that must be configured in advance before creating this service. Please prepare in advance by referring to the guide provided for each service.

Service CategoryServiceDetailed Description
NetworkingVPCService that provides an independent virtual network in a cloud environment
Table. MySQL(DBaaS) Prerequisite Services
Release Note
Server Type