Overview
Service Overview
MariaDB (DBaaS) is an open source relational database (RDBMS) with high compatibility with MySQL. Samsung Cloud Platform provides an environment that can automate MariaDB installation and perform management functions for operation through a web-based console.
MariaDB (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 are provided for read load balancing and disaster recovery (DR). Additionally, to prepare for issues with the DB server or data, it offers a feature that automatically backs up at a user-specified time, supporting data recovery at the desired point in time.
Provided Features
MariaDB (DBaaS) provides the following features.
- Auto Provisioning (Auto Provisioning): Installation and configuration of Database (DB) via UI is possible, and it provides an Active-standby redundancy configuration built on storage replication. In case of an Active server failure, 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, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), the user can directly perform node switching between Active-Standby via Switch-over.
- Backup and Recovery: Provides data backup functionality based on its own backup command. The backup time window and storage organization can be set by the user, and additional fees may be incurred depending on backup volume. It also provides a recovery function for backed-up data, so when the user performs recovery, a separate DB is created and recovery proceeds to the point in time selected by the user (backup save point, user-defined point). When recovering to a user-specified point, the recovery point can be set to 5 minutes/10 minutes/30 minutes/1 hour before the stored backup file and archive file.
- Version Management: Provides version upgrade (Minor) functionality due to 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, 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.
- Audit setting: Provides an Audit setting feature that can monitor the user’s DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) execution.
- 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 through 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 for access.
- 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: Through Audit settings, you can export stored logs to the user’s Object Storage.
- Migration: Synchronize data in real time with the operating database, and support migration using replication method without service interruption.
Components
MariaDB (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 MariaDB (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 6 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.
- MariaDB (Community): https://mariadb.org/about/#maintenance-policy
| Service | Provided Version | EOS Date(Samsung Cloud Platform New Creation Stop Date) | EoTS Date(Community Technical Support End Date) |
|---|---|---|---|
| MariaDB (Community) | 10.6.5 | 2026-03 (planned) | 2026-07-06 |
| 10.6.9 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.10 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.12 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.14 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.15 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.16 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.17 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.19 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.22 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.11.8 | 2027-09 (scheduled) | 2028-02-16 | |
| 10.11.9 | 2027-09 (scheduled) | 2028-02-16 | |
| 10.11.13 | 2027-09 (scheduled) | 2028-02-16 | |
| 11.4 | 2029-09 (scheduled) | 2030-01-16 |
Server Type
The server types supported by MariaDB (DBaaS) are as follows.
For detailed information about the server types provided by MariaDB(DBaaS), see MariaDB(DBaaS) Server Type.
Standard db1v2m4
| Category | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Provided Server Types
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | Number of vCores
|
| Server Specifications | m4 | Memory Capacity
|
Preliminary Service
This is a list of services that must be pre-configured before creating the service. For details, please refer to the guide provided for each service and prepare in advance.
| Service Category | Service | Detailed Description |
|---|---|---|
| Networking | VPC | A service that provides an independent virtual network in a cloud environment |
