We provide a service that easily creates and manages relational, unstructured, and analytical databases in a web environment.
This is the multi-page printable view of this section. Click here to print.
Database
- 1: EPAS(DBaaS)
- 1.1: Overview
- 1.1.1: Server Types
- 1.1.2: Monitoring metrics
- 1.2: How-to guides
- 1.2.1: DB Service Manage
- 1.2.2: Backing up and restoring the database
- 1.2.3: Configure Read Replica
- 1.2.4: EPAS(DBaaS) Server Connection
- 1.2.5: Extension Usage
- 1.3: API Reference
- 1.4: CLI Reference
- 1.5: Release Note
- 2: PostgreSQL(DBaaS)
- 2.1: Overview
- 2.1.1: Server Types
- 2.1.2: Monitoring metrics
- 2.2: How-to guides
- 2.2.1: DB Service Manage
- 2.2.2: Backing up and restoring the DB
- 2.2.3: Configure Read Replica
- 2.2.4: DB Server Connection
- 2.2.5: Extension Use
- 2.3: API Reference
- 2.4: CLI Reference
- 2.5: Release Note
- 3: MariaDB(DBaaS)
- 3.1: Overview
- 3.1.1: Server Types
- 3.1.2: Monitoring Metrics
- 3.1.3: ServiceWatch Metrics
- 3.2: How-to guides
- 3.2.1: DB Service Manage
- 3.2.2: Backing up and restoring the database
- 3.2.3: Configure Read Replica
- 3.2.4: MariaDB(DBaaS) Server Connection
- 3.3: API Reference
- 3.4: CLI Reference
- 3.5: Release Note
- 4: MySQL(DBaaS)
- 4.1: Overview
- 4.1.1: Server Types
- 4.1.2: Monitoring metrics
- 4.1.3: ServiceWatch Metrics
- 4.2: How-to guides
- 4.2.1: DB Service Manage
- 4.2.2: Backing up and restoring the database
- 4.2.3: Configure Read Replica
- 4.2.4: MySQL(DBaaS) Server Connection
- 4.3: API Reference
- 4.4: CLI Reference
- 4.5: Release Note
- 5: Microsoft SQL Server(DBaaS)
- 5.1: Overview
- 5.1.1: Server Types
- 5.1.2: Monitoring metrics
- 5.2: How-to guides
- 5.2.1: DB Service Manage
- 5.2.2: Backing up and restoring the DB
- 5.2.3: Secondary Add
- 5.2.4: Microsoft SQL Server(DBaaS) Server Connection
- 5.3: API Reference
- 5.4: CLI Reference
- 5.5: Release Note
- 6: CacheStore(DBaaS)
- 6.1: Overview
- 6.1.1: Server Types
- 6.1.2: Monitoring metrics
- 6.2: How-to guides
- 6.2.1: CacheStore Service Manage
- 6.2.2: CacheStore Backup and Restore
- 6.2.3: CacheStore(DBaaS) Server Connection
- 6.3: API Reference
- 6.4: CLI Reference
- 6.5: Release Note
- 7: Scalable DB(DBaaS)
- 7.1: Overview
- 7.1.1: Server Types
- 7.1.2: ServiceWatch Metrics
- 7.2: How-to guides
- 7.2.1: Read Node Manage
- 7.2.2: Backup DB
- 7.3: Release Note
1 - EPAS(DBaaS)
1.1 - Overview
Service Overview
EPAS(DBaaS) is a relational database management system (RDBMS) with high compatibility with Oracle databases. Samsung Cloud Platform provides an environment that automates EPAS installation and performs management functions for operation through a web-based console.
EPAS(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 up to five read‑only Replica servers for read load balancing and disaster recovery (DR) are provided. Additionally, to prepare for potential issues with the DB server or data, we provide a feature that automatically backs up at a user-specified time, enabling data recovery at the desired point.
Provided Features
EPAS(DBaaS) provides the following features.
- Auto Provisioning: UI allows installation and configuration of Database (DB), and provides an Active‑standby redundancy configuration built 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).
- Audit configuration: Provides an Audit configuration feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
- Parameter management: You can modify DB configuration parameters related to performance improvement and security.
- Service Status Query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, DB performance monitoring information can be viewed through the Cloud Monitoring service.
- 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 Archive file retention period (1~35 days) 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 operational database and support migration using replication without service interruption.
- OS Kernel Upgrade: You can upgrade the OS Kernel to apply some feature improvements and security patches.
Component
EPAS (DBaaS) provides pre‑validated engine versions and a variety of server types. Users can select and use it based on the scale of the service they wish to configure.
Engine version
The engine versions supported by EPAS (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.
| Provided version | EOS Date (Samsung Cloud Platform new creation stop date) | EoTS Date (Community technical support end date) |
|---|---|---|
| 14.17 | 2026-05-20 | 2026-12-01 |
| 14.18 | 2026-05-20 | 2026-12-01 |
| 14.19 | 2026-05-20 | 2026-12-01 |
| 15.12 | 2027-09 (planned) | 2028-02-13 |
| 15.13 | 2027-09 (planned) | 2028-02-13 |
| 15.14 | 2027-09 (planned) | 2028-02-13 |
| 16.8 | 2028-06 (planned) | 2028-11-09 |
| 16.9 | 2028-06 (planned) | 2028-11-09 |
| 16.10 | 2028-06 (planned) | 2028-11-09 |
| 17.6 | 2029-06 (planned) | 2029-11-08 |
The next version of EPAS is expected to be offered after July 2026. The actual service delivery schedule is subject to change.
- EPAS 15.15
- EPAS 16.11
- EPAS 17.17
Server type
The server types supported by EPAS (DBaaS) are as follows.
For detailed information about the server types provided by EPAS (DBaaS), see EPAS(DBaaS) Server Types.
Standard db1v2m4
| Category | Example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server types
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
Preceding Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
1.1.1 - Server Types
EPAS(DBaaS) server type
EPAS (DBaaS) offers server types configured with various combinations of CPU, memory, and network bandwidth. When creating an EPAS (DBaaS), the Database Engine is installed based on the server type selected for the intended purpose.
The server types supported by EPAS (DBaaS) are as follows.
Standard db1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classifications
|
| Server specifications | db1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
db1 server type
The db1 server type of EPAS (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db1v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
db2 server type
The db2 server type of PostgreSQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor, up to 3.2 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db2v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db2v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db2v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db2v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db2v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db2v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db2v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db2v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db2v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db2v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db2v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db2v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db2v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db2v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db2v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db2v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db2v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db2v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db2v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db2v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db2v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db2v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
dbh2 server type
The dbh2 server type of EPAS(DBaaS) is provided with high‑capacity server specifications and is suitable for database workloads that require large‑scale data processing.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 128 vCPUs and 1,536 GB of memory
- Networking speed up to 25 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Maximum 25 Gbps |
1.1.2 - Monitoring metrics
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, which was released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
- New Resources: Resources created after the service improvement work in July 2026 are monitored by default using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide monitoring concurrently via Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings linked with existing Cloud Monitoring (e.g. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Notice of the phased termination schedule for the Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, Cloud Monitoring data cannot be accessed. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
EPAS(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics of EPAS (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
For EPAS (DBaaS) server monitoring metrics, refer to the Virtual Server Monitoring Metrics guide.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Locks [Access Exclusive] | Number of Access Exclusive Locks | cnt |
| Active Locks [Access Share] | Number of Access Share Locks | cnt |
| Active Locks | Number of Active Locks | cnt |
| Active Locks [Total] | Total number of active locks | cnt |
| Active Sessions | Number of Sessions in Active state | cnt |
| Active Sessions [Total] | Total number of Sessions in Active state | cnt |
| Apply Lag Time | Apply lag time | min |
| Check No Replication | Check No Replication value | cnt |
| Check Replication | Check Replication Status value | status |
| Connection Usage | DB connection usage rate (%) | % |
| Connection Usage [Total] | DB connection usage rate (%) | % |
| DB Age Max | Database age (frozen XID) value | age |
| Exclusive Locks | Number of Exclusive Locks | cnt |
| Idle In Transaction Sessions | Number of sessions in Idle in transaction state | cnt |
| Idle In Transaction Sessions [Total] | Total number of sessions in idle in transaction state | cnt |
| Idle Sessions | Number of idle sessions | cnt |
| Idle Sessions [Total] | Total number of idle sessions | cnt |
| Row Exclusive Locks | Number of Row Exclusive Locks | cnt |
| Row Share Locks | Row Share Locks count | cnt |
| Share Locks | Number of Share Locks | cnt |
| Share Row Exclusive Locks | Number of Share Row Exclusive Locks | cnt |
| Share Update Exclusive Locks | Number of Share Update Exclusive Locks | cnt |
| Slowqueries | Number of SQL queries running for a long time (over 5 minutes) | cnt |
| Tablespace Used | Table space size | bytes |
| Tablespace Used [Total] | Table space size | bytes |
| Tablespace Used Bytes [MB] | File system directory usage (MB) | MB |
| Tablespaces [Total] | File system directory usage (MB) | MB |
| Transaction Time Max [Long] | Long-running Transaction time (minutes) | min |
| Transaction Time Max Total [Long] | Long-running Transaction time (minutes) | min |
| Wait Locks | Number of lock-waiting sessions (by DB) | cnt |
| Wait Locks [Long Total] | Number of lock-waiting sessions (300 seconds) | cnt |
| Wait Locks [Long] | Number of sessions waiting due to a lock | cnt |
| Wait Locks [Total] | Total number of sessions waiting due to lock occurrence | cnt |
| Waiting Sessions | Number of Sessions in Waiting state | cnt |
| Waiting Sessions [Total] | Total number of Sessions in Waiting state | cnt |
1.2 - How-to guides
Users can create the service by entering the required information for EPAS (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service per Resource
- New Resources: Resources created after the July 2026 service improvement work are provided with default monitoring 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, we must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings linked with existing Cloud Monitoring (ex. You must check the event policies, etc., and perform tasks such as resetting the ServiceWatch service, then complete them.
Notice of the phased termination schedule for Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch is available in the ServiceWatch 개요.
Create EPAS (DBaaS)
You can create and use the EPAS (DBaaS) service in the Samsung Cloud Platform Console.
- Before creating the service, configure the VPC’s subnet type as General.
- If the subnet type is Local, the creation of the corresponding Database service is not possible.
- 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 the statistical collection environment.
To create EPAS (DBaaS), follow these steps.
All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
On the Service Home page, click the Create EPAS (DBaaS) button. 2. Go to the EPAS(DBaaS) Create page.
On the Create EPAS (DBaaS) page, enter the information required to create the service and select detailed options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version Required Provide EPAS (DBaaS) version list Table. EPAS (DBaaS) Image and version selection items - In the Service Information Input area, enter or select the required information.
Category required statusDetailed description Server name Prefix Required Server name where the DB will be installed - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
-) with a length of 3 to 13 characters
- A postfix such as 001, 002 is appended to the base server name to generate the actual server name
Cluster name required Cluster name composed of DB servers - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for DB installation - Standard: Standard specification commonly used
- High Capacity: Large-capacity server with 24 vCores or more
- For detailed information about the server types provided by EPAS (DBaaS), refer to EPAS(DBaaS) 서버 타입
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, refer to Planned Compute Application
Service Type > Block Storage Required Block Storage settings used by the DB according to purpose - Base 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.(For details on each Block Storage type, refer to Block Storage 생성하기)
- SSD: High‑performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volume that uses 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
- Because executing SQL or monthly batch jobs can cause service interruption due to large sorts, a separate TEMP storage must be allocated and used
- Add: DATA, Archive, TEMP, Backup data storage areas
- Use after selecting, 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
- Before transmitting backup data, temporarily store the backup data in the BACKUP storage
- 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; the backup capacity is advised to be set at about 60 % of the DATA capacity
- If a BACKUP storage is not added, the
/tmparea is used, and backup fails if capacity is insufficient
- For each service, Archive, TEMP, and BACKUP storages are allocated only one Block Storage each
- Select a storage type and then enter the capacity.(For details on each Block Storage type, refer to Block Storage 생성하기)
Redundancy configuration Selection Redundancy configuration status - When redundancy configuration is used, the DB instance is set up as an Active DB and a Standby DB
Network > Common Settings Essential Network settings for servers created by the service - Select when you want to apply the same settings to all installed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be generated automatically
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use it by checking the box, allowing selection from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Checking Use makes it possible to select a reserved IP from the VPC product’s Public IP pool. For more details, see Public IP 생성하기.
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of the 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. EPAS (DBaaS) Service Information Input Items - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
- Enter required database configuration information Enter or select the required information in this area.
Category required statusDetailed description Database name Required Server name applied during DB installation - must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
Database username Required Database user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Restricted database user names can be viewed in the Console
Database password Required Password to use when accessing the DB - Enter 8 to 30 characters, including letters, numbers, and special characters (excluding
“‘)
Database password verification Essential Re-enter the same password to use for DB access Database Port number Required Port number required for DB connection - Enter DB port within the range 1200 ~ 65535
Backup > Use Select Backup usage - Select Use to set backup file retention period, backup start time, and Archive backup interval
Backup > Retention Period Select Backup retention period - Select the backup retention period. Set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Period Selection Backup start time - Select backup start time
- The minute(s) at which the backup runs is set randomly, and the backup end time cannot be set
Backup > Archive backup cycle Select Archive backup interval - Select the archive backup interval
- The archive backup interval is recommended to be 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
Audit Log Settings Select Whether to store Audit Log - Select Use to configure the Audit Log feature
- DDL, DML, SELECT, and user connection information records are stored
- The user can specify the types of SQL statements to audit via the
edb_audit_statementparameter, and can modify it through the Parameter screen
- Refer to the EDB documentation for detailed information about this parameter
- The user can specify the types of SQL statements to audit via the
- Enabling Audit may degrade database performance
Parameter Essential DB configuration parameters - Click the Query button to view detailed information of the parameters
- Parameters can be modified after the service creation is complete, and the DB must be restarted after modification
Database Encoding Required Character encoding method to be used for the DB - Character set used when storing text data
- The DB is created with the selected encoding as the default setting
DB Locale Required Locale to be used for the DB - settings related to string handling, number/currency/date/time display formats, etc.
- The DB is created with the selected Locale as the default setting
time zone Required Standard time zone for the database License Required EPAS License verification status - Verification item for license usage; if you do not click Confirm, you cannot proceed to the next step
Table. EPAS (DBaaS) Database configuration items - In the Additional Information Input area, enter or select the required information.
Category Required statusDetailed description Tag Select Add Tag - Up to 50 per resource can be added
- Add Tag button, then input or select Key, Value values
Table. EPAS (DBaaS) Additional Information Input Items
- Select the required information in the Image and version selection area.
Check the detailed information and estimated billing amount generated in the Summary panel, and click the Create button.
- Once creation is complete, check the created resource on the Resource List page.
View detailed information of EPAS (DBaaS)
The EPAS (DBaaS) service allows you to view and edit the full list of resources and detailed information. EPAS(DBaaS) Details page consists of Details, Tags, Activity History tabs, and when the DB has a Replica configured, a Replica Information tab is added.
To view detailed information about the EPAS (DBaaS) service, follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource to view detailed information. 3. EPAS(DBaaS) Details Go to the page.
- EPAS(DBaaS) Details The top of the page displays status information and additional feature details.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Creating cluster
- Editing: Cluster is changing to a state of performing an operation
- Error: Cluster encountered an error while performing tasks
- If it occurs continuously, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Restarting the cluster
- Running: Cluster is operating normally
- Starting: Starting the cluster
- Stopped: Cluster is stopped
- Stopping: Cluster is in the process of stopping
- Synchronizing: Synchronizing the cluster
- Terminating: Terminating the cluster
- Unknown: Cluster status is unknown
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is changing to a state of performing an upgrade
Cluster control Button to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to active
More features Cluster Management Buttons - Service Status Synchronization: Real-time DB service status lookup
- Backup History: When backup is configured, verify successful execution and view 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 Settings Management: Configure archive file retention period and enable archive mode
- Export DB Log: Export stored logs to the user’s Object Storage via Audit settings
- Migration Configuration: Provides migration functionality using replication
- OS (Kernel) Upgrade: Upgrade the OS kernel version
Service termination Cancel service button Table. EPAS (DBaaS) status information and additional features
- EPAS(DBaaS) Details The top of the page displays status information and additional feature details.
Detailed information
On the EPAS (DBaaS) List page, you can view detailed information of the selected resource and edit the information if needed.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| Service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster type | Cluster types (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster name | Cluster name of the DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied during DB installation |
| Database username | DB user name |
| Planned Compute | Resource status with Planned Compute configured
|
| maintenance period | DB Maintenance Period Status
|
| Backup | Backup configuration status
|
| Audit Log Settings | Audit Log configuration status
|
| time zone | Standard time zone for the database |
| DB Locale | Locale to use in the DB |
| Database Encoding | Character encoding to use for the DB |
| VIP | Virtual IP information
|
| Network | Network information of the DB installation (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP access control | Service access policy configuration
|
| Active & Standby | Active/Standby server type, base OS, additional Disk information
|
Replica information
The Replica Information tab is enabled only when a Replica is configured in the cluster. Through the Replica Information tab, you can check the Master cluster name, number of replicas, and Replica status.
| Category | Detailed description |
|---|---|
| Master information | Name of the Master cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status created in the Master cluster
|
tag
EPAS (DBaaS) List page lets you view, add, modify, or delete tag information for the selected resource.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Work History
EPAS (DBaaS) List page allows you to view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Managing EPAS (DBaaS) Resources
If you need to change or restore the existing configuration options of a created EPAS (DBaaS) resource, or require a Replica configuration, you can perform the task on the EPAS(DBaaS) Details page.
Control operation
If changes occur to a running EPAS (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 EPAS (DBaaS), follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource you want to control. 3. EPAS(DBaaS) Details Navigate to the page.
- Check the EPAS (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 EPAS (DBaaS).
To check the service status of EPAS (DBaaS), follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource for which you want to view the service status. 3. EPAS(DBaaS) Details Go to the page.
- Service Status Synchronization Click the button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.
Change server type
You can change the configured server type.
To change the server type, follow these steps.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS(DBaaS) List page.
- EPAS(DBaaS) List page, click the resource whose server type you want to change. 3. Go to the EPAS(DBaaS) Details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Edit Server Type 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.
To add storage, follow these steps.
- It is applied in the same way as the Storage type selected when creating the service.
- For a DB configured with redundancy, adding storage is applied simultaneously to the storage of both the Active DB and the Standby DB.
- If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. * First expand the Replica storage, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to EPAS(DBaaS) List page.
- On the EPAS (DBaaS) List page, click the resource to add storage. 3. EPAS(DBaaS) Details Navigate to the page.
- Click the Disk Add button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.
Expand storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To expand storage capacity, follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- EPAS(DBaaS) List page, click the resource for which you want to change the server type. 3. EPAS(DBaaS) Details Navigate to the page.
- Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
- Edit Additional Storage In the popup window, after entering the expanded capacity, click the Confirm button.
Cancel EPAS (DBaaS)
You can cancel unused EPAS(DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact that may occur when the service is discontinued.
- For a DB with a Replica configured, terminating the Master DB does not delete the Replica. * If you also delete the replica, 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 EPAS (DBaaS), follow the steps below.
- All Services > Database > EPAS(DBaaS) menu, click it. 1. Navigate to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- EPAS(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
- After termination is complete, check on the EPAS(DBaaS) list page whether the resource has been terminated.
1.2.1 - DB Service Manage
Users can manage EPAS (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
Provides a feature that enables easy viewing and modification of database configuration parameters.
Viewing Parameters
To view configuration parameters, follow these steps.
- Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the EPAS(DBaaS) Service Home page.
- On the Service Home page, click the EPAS(DBaaS) menu. You will be taken to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource whose parameters you want to view or modify. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
- In the Parameter Management popup, click the Search button. The Search Notification popup opens.
- Lookup Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
Parameter Modify
To modify the configuration parameters, follow the steps below.
- Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. You will be taken to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource whose parameters you want to view or modify. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
- In the Parameter Management popup, click the Search button. The Search Notification popup opens.
- Lookup Notification When the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
- If editing is required, click the Edit button and enter the changes in the custom value area of the Parameter to be edited.
- When the input is complete, click the Complete button.
DB User Management
Provides management features that allow viewing DB user information and changing status information.
Query DB users
To retrieve DB users, follow these steps.
- Click the All Services > Database > EPAS(DBaaS) menu. Go to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource whose DB users you want to view. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button, then click the DB User Management button. You will be directed to the DB User Management page.
- Click the Search button on the DB User Management page. Retrieving may take a short while.
Changing DB User Status
To change the status of the retrieved DB user, follow these steps.
- Click the All Services > Database > EPAS(DBaaS) menu. Go to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- EPAS(DBaaS) List page, click the resource whose DB user you want to modify. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button, then click the DB User Management button. You will be directed to the DB User Management page.
- On the DB User Management page, click the Search button. Retrieving may take a short time.
- If modification is needed, click the Edit button, and change the status field value or enter remarks.
- When the input is complete, click the Complete button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IPs that can access the database, configuring it so that only authorized IPs are allowed access.
View DB Access Control
Follow these steps to query DB users with IP access control enabled.
- Click the All Services > Database > EPAS(DBaaS) menu. Proceed to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- Click the resource you want to manage access control for on the EPAS(DBaaS) List page. You will be taken to the EPAS(DBaaS) Detail page.
- Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a moment.
Add DB access control
To add IP access control, follow these steps.
- Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. You will be taken to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource for which you want to add IP access control. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. The query may take a moment.
- After the query completes, click the Add button. The Add DB Access Control popup window opens.
- Add DB Access Control In the popup window, select the DB username and enter the IP address.
- When the input is complete, click the Save button.
Delete DB access control
To delete IP access control, follow these steps.
- Click the All Services > Database > EPAS(DBaaS) menu. Go to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. Navigate to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource for which you want to delete IP access control. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a moment.
- When the query is complete, click the Delete button. The Delete popup window opens.
- In the Delete popup, click the Confirm button.
Managing Archive
Provides the ability to configure Archive mode and set the retention period for Archive logs, allowing users to flexibly configure Archive log management policies to suit their operational environment. Additionally, it provides a feature to manually delete archive logs, allowing you to clean up unnecessary log data and manage system resources effectively.
Configure Archive mode
To set the Archive mode, follow these steps.
- Click the All Services > Database > EPAS(DBaaS) menu. Go to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. Navigate to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource for which you want to set Archive mode. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- On the Archive Settings Management page, click the Search button. The query may take a short time.
- Click the Edit button and select the usage status and retention period.
- When the edit is complete, click the Complete button.
Delete Archive file
To delete the Archive file, follow these steps.
- Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. You will be taken to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource you want to set to Archive mode. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button, then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- Archive Settings Management page, if you want to delete all Archive files, click the Delete All Archives button; if you only want to delete the backed‑up Archive files, click the Delete Backed‑up Archives button.
Modify Audit Settings
You can modify the Audit log storage settings for EPAS (DBaaS).
To change the Audit log storage settings of EPAS (DBaaS), follow the steps below.
- Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the EPAS(DBaaS) Service Home page.
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- EPAS(DBaaS) List page, click the resource whose service status you want to view. You will be taken to the EPAS(DBaaS) Details page.
- Click the Edit icon of Audit Settings at the bottom of the detailed information. The Edit Audit Settings popup window opens.
- Modify Audit Settings After changing the usage in the popup window, click the Confirm button.
- When Enable is selected, the Audit log feature is configured. Enabling the Audit log may degrade DB performance.
- If you disable use, the Audit log storage file will be deleted. Before disabling use, back up the Audit log file separately.
DB Log Export
Supports exporting log data that requires long-term retention among audit logs to Object Storage. Users can directly configure the log types to be stored, the target bucket for export, and the export interval. Based on the configured criteria, logs are copied to the specified Object Storage for retention. Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for long-term storage.
- To use the DB Log export feature, you must create an Object Storage. For creating an 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 take care to prevent the authentication key information from being exposed externally.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps.
- Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource for which you want to export the DB Log. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
- On the DB Log Export page, click the Register button. You will be taken to the DB Log Export Register page.
- After entering the required information on the DB Log Export Registration page, click the Complete button.
Category Required Detailed descriptionLog type Required Log type to be saved Save bucket name Required Object Storage bucket name to be saved Authentication key > Access key Required Access key for accessing the Object Storage you want to store Authentication key > Secret key Required Secret key for accessing the Object Storage you want to store File creation cycle Required File creation frequency in Object Storage Whether to delete the original log Selection Whether to delete the original logs when exporting to Object Storage Table. EPAS (DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow these steps.
- All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. Navigate to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource you want to manage DB Log export for. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button and then click the DB Log Export button. You will be taken to the DB Log Export page.
- DB Log Export On the page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, Terminate 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: Cancel the DB Log export mode setting.
Minor Version Upgrade
We provide version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades within the same Major version are supported.
- First retrieve the service status by synchronizing it, then perform the version upgrade.
- Please perform the version upgrade after configuring a backup. If you do not set up a backup, you may be unable to recover some data if a problem occurs during the upgrade.
- In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. Please check the Replica’s 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 Minor Version, follow the steps below.
- Click the All Services > Database > EPAS(DBaaS) menu. Go to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource you want to upgrade the version for. You will be taken to the EPAS(DBaaS) Detail page.
- Click the Edit button in the Image version item. The Version Upgrade popup window opens.
- Version Upgrade In the popup window, select the updated version and backup setting, then click the Confirm button.
- Version Upgrade Notification Click the Confirm button in the popup window.
Configuring Migration
Provides a Migration feature that synchronizes in real time with the live database and replicates using a Replication method without service interruption.
To configure Migration, follow these steps.
- All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- EPAS(DBaaS) List page: click the resource you want to migrate. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button, then click the Migration configuration button. Migration configuration popup window opens.
- Migration configuration In the popup window, review the instructions and click the Confirm button. You will be taken to the Migration configuration page.
- On the Migration configuration page, enter the required information, then click the Check connection button.
- When the connection is complete, click the Complete button.
Category Required Detailed descriptionSource DB Database name Required Database name of the source DB to be migrated Source DB IP Required IP of the Source DB that is the migration target Source DB Port Required Port of the Source DB to be migrated Source DB username Required Username of the source DB that is the migration target Source DB password Required Password of the source DB for migration Table. EPAS(DBaaS) migration configuration items
Promote Migration Cluster to Master Cluster
You can promote a configured Migration Cluster to a Master Cluster.
To promote the Migration Cluster to Master, follow these steps.
- Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. Navigate to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource to promote to Master. You will be taken to the EPAS(DBaaS) Details page.
- Click the More button, then click the Master Promotion button. The Master Promotion Notification popup window opens.
- Master Promotion Notification in the popup window, click the Confirm button.
Upgrade OS Kernel
The OS Kernel can be upgraded to improve the functionality of the running database and apply security patches.
- The service will be unavailable while the OS upgrade is in progress.
- The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
- After the upgrade is complete, you cannot revert to the previous OS.
To upgrade the OS Kernel, follow the steps below.
- Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the EPAS(DBaaS) Service Home page.
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource to upgrade the OS Kernel. You will be taken to the EPAS(DBaaS) Detail page.
- Click the More button, then click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup opens.
- OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.
1.2.2 - Backing up and restoring the database
Users can configure backups of EPAS (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
EPAS(DBaaS) Backup
To ensure that users’ data can be stored safely, EPAS (DBaaS) provides a data backup feature based on its own backup commands. Additionally, you can verify whether the backup was successful using the backup history feature, and you can also delete backed‑up files.
Configure Backup
For instructions on configuring backups for EPAS (DBaaS), see Create EPAS (DBaaS).
To modify the backup settings of the created resource, follow the steps below.
- For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity. * Especially when the backup data exceeds 100 GB and undergoes frequent changes, please provision additional storage amounting to approximately 60 % of the data size. * For storage addition and expansion methods, refer to the EPAS(DBaaS) Add Storage and EPAS(DBaaS) Expand Storage guides.
- If a backup is configured, it will be performed 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 will stop immediately, and the stored backup data will be deleted and can no longer be used.
To set up a backup, follow these steps.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- EPAS(DBaaS) List page: click the resource for which you want to configure a backup. 3. EPAS(DBaaS) Details page is accessed.
- Click the Edit button of the backup item. 4. Backup Settings popup window opens.
- When configuring a backup, click Enable in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
- If you stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Once user authentication is completed, the backup configuration is disabled and backup execution stops.
- If you stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Check backup history
To view the backup history, follow these steps.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- EPAS(DBaaS) List page, click the resource to view the backup history. 3. Go to the EPAS(DBaaS) Details page.
- Click the Backup History button. 4. The Backup History popup opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
- All Services > Database > EPAS(DBaaS) menu, click it. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource to view its backup history. 3. Go to the EPAS(DBaaS) Details page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
- When user authentication is completed, the backup file is deleted.
EPAS(DBaaS) Recover
If recovery is needed from a backup file due to a failure or data loss, the restore function can recover based on a specific point in time. When you perform an EPAS (DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds with the database’s configuration information and data.
To restore EPAS (DBaaS), follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- EPAS(DBaaS) resources On the list page, click the resource you want to restore. 3. Navigate to the EPAS(DBaaS) Details page.
- Click the Database Recovery button. 4. Database Recovery Navigate to the page.
- After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
Category required statusDetailed description Recovery Type Required Set the point in time the user wants to recover - Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
- Custom point: Recover to a user‑desired point within the range of recoverable backup points. The recoverable period depends on the Archive backup interval setting, allowing recovery to any point from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the date and time to recover
Server name prefix Required Recovery DB server name - Start with a lowercase English letter and use lowercase letters, numbers, and special characters (
-) to enter 3 to 16 characters
- Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name Required Recovery DB cluster name - Enter using English letters, 3 to 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Essential Recovery DB server type - Standard: Standard specification commonly used
- High Capacity: Large-capacity server with 24 vCores or more
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, refer to Planned Compute 신청하기
Service Type > Block Storage Required Block Storage settings used by the recovery DB - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Applied identically with the storage type set in the original 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 original 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, and 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
Database username Required Database username - Apply the same username set in the original cluster
Database Port number Required Database Port number - Apply the same Port number configured in the original cluster
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of week, start time, and duration
- It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
- If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
tag Select Add Tag - Add Tag after clicking the Add Tag button Enter or select Key, Value values
Table. EPAS (DBaaS) recovery configuration items
1.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 the detailed options.
Configure Replica
You can create replica servers for read‑only or disaster‑recovery purposes through replica configuration. You can create up to 5 replicas per database.
To configure a Replica, follow these steps.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource to configure the Replica. 3. Navigate to the EPAS(DBaaS) Details page.
- Click the Replica configuration button. 4. Go to the Replica configuration page.
- After entering information in the Replica configuration area, click the Complete button.
Category required statusDetailed description Region Required Region to configure the Replica - Replica configuration (Other Region)exposed only when selected
Replica count Required Number of Replicas to configure - Up to 5 can be configured per cluster
- If you select more than one value, additionally enter the Replica name and service type information
Replica name Required Replica server name - Start with a lowercase English letter, and use lowercase letters, numbers, and special characters (
-) to enter 3 to 19 characters
- The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type Required Replica server type - Standard: standard specification commonly used
- High Capacity: large-capacity server with 24 vCore or more
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute Apply
IP access control Selection Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Selection Database maintenance window - If you select Use, set the day, start time, and duration
- It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruption
- If set to unused, we are not responsible for any issues arising from patches not being applied.
Tag Select Add Tag - Add Tag after clicking the button Enter or select Key, Value values
Table. EPAS (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 these steps.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource to reconfigure the Replica. 3. EPAS(DBaaS) Details Navigate to the page.
- Click the Reconstruct Replica button. 4. Replica Reconfiguration Notification A popup window opens.
- Replica Reconfiguration Notification popup window, click the Confirm button.
Promoting a Replica Cluster to a Master Cluster
You can promote a configured Replica Cluster to a Master Cluster.
To promote a Replica Cluster to Master, follow these steps.
- All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS(DBaaS) List go to the page.
- On the EPAS(DBaaS) List page, click the resource to promote to Master. 3. Go to the EPAS(DBaaS) Details page.
- Click the More button, then click the Promote to Master button. 4. Master Promotion Notification The popup window opens.
- In the Master Promotion Notification popup, click the Confirm button.
1.2.4 - EPAS(DBaaS) Server Connection
Scenario Overview
EPAS(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 EPAS (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 set up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and a Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Scenario components
You can build the scenario using the following services.
| service group | service | Detailed description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that lets users segment the network within a VPC to match their purpose and scale. | |
| Networking | VPC > Public IP | Service that reserves a public IP and allocates and releases it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the Internet | |
| Networking | Security Group | Virtual firewall that controls server traffic | |
| Database | EPAS(DBaaS) | A service that easily creates and manages EPAS in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- Since the default policy of a Security Group is Deny All, you must register only the IPs that are allowed.
- 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 setup method
Create the services needed to build the scenario by following the steps below.
Configure the network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
1-1. Create VPC
- Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
- Click the Create VPC button on the Service Home page. You will be taken to the Create VPC page.
- On the VPC Creation page, enter the information required to create the service.
- Enter the IP range as
192.168.x.0/16
- Enter the IP range as
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resources on the VPC List page.
1-2. Create Subnet
- Click the All Services > Networking > VPC menu. Navigate to the VPC Service Home page.
- On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
- Click the Subnet Create button. You will be taken to the Subnet Create page.
- On the Subnet Creation page, enter the information required to create the service.
- Select the Subnet type as General.
- Select a pre‑created VPC.
- Enter the IP range as
192.168.x.0/24.
- In the Summary panel, verify the detailed information and estimated billing amount, then click the Complete button.
- When creation is complete, check the created resources on the Subnet list page.
1-3. Create Internet Gateway
- Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
- On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
- Click the Create Internet Gateway button. You will be taken to the Create Internet Gateway page.
- On the Internet Gateway Creation page, enter the required information needed to create the service.
- Select a pre‑created VPC.
- In the Firewall usage item, select Use.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, verify the created resource on the Internet Gateway list page.
1-4. Create Public IP
- Click the All Services > Networking > VPC menu. Navigate to the VPC Service Home page.
- On the Service Home page, click the Public IP menu. You will be taken to the Public IP List page.
- Click the Public IP Reservation button. You will be taken to the Public IP Reservation page.
- On the Public IP reservation page, enter the required information needed to reserve the service.
- In the Summary panel, verify the detailed information and estimated billing amount, then click the Complete button.
- Once creation is complete, check the created resources on the Public IP List page.
1-5. Create Security Group
- Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
- Click the Create Security Group button on the Service Home page. Navigate to the Create Security Group page.
- On the Security Group creation page, enter the required information needed to create the service.
- Check the input information and click the Complete button.
- Once creation is complete, check the created resources on the Security Group List page.
Create bastion host
Describes the process of configuring a Bastion Host that requires the Database access client to be installed.
2-1. Create Server Keypair
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
- Click the Keypair creation button. You will be taken to the Keypair creation page.
- Enter the required information needed to create a service on the Keypair creation page.
- Check the creation information and click the Complete button.
- The key can be downloaded only once, and reissuance is not available.
- Please store the downloaded key in a secure location.
2-2. Create Bastion host
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Virtual Server Create button. It navigates to the Virtual Server Create page.
- Virtual Server Creation page, enter the required information to create the service.
- Select Windows for the image.
- Select the pre-created VPC and Subnet.
- Click Use NAT, then in 1-4. Create Public IP select the reserved Public IP.
- Connect the Keypair you created in 2-1. Create Server Keypair.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, verify the created resources on the Virtual Server list page.
2-3. Bastion host Check login ID and PW
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- Click the Virtual Server menu on the Service Home page. You will be taken to the Virtual Server List page.
- On the Virtual Serve List page, click the resource you created in 2-2. Create Bastion host. You will be taken to the detailed information page of that resource.
- On the detail information page, click the RDP password View button in the Keypair name field. The RDP password View popup window will open.
- In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
- After attaching, click the Password Check button. The ID and Password for accessing the resource are displayed.
- The ID and Password are used later as credentials to access the Bastion host in 5-1. Bastion host 접속하기.
Create Database
Describes the process of creating a Database service.
3-1. EPAS(DBaaS) Service Creation
- Click the All Services > Database > EPAS(DBaaS) menu. Go to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) Create button on the Service Home page. You will be taken to the EPAS(DBaaS) Create page.
- Create EPAS (DBaaS) Enter the required information needed to create the service on this page.
- Select the pre‑created VPC and Subnet and connect them.
- Enter the database-related creation details on the required information input screen.
- Add the Bastion host IP in the IP access control settings.
- The Database Port defaults to 2866, but the user can also specify it.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, verify the created resource on the EPAS(DBaaS) list page.
Configuring 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. Add Security Group Rules
- Click the All Services > Networking > Security Group menu. Navigate to the Service Home page of the Security Group.
- From the Service Home page, click the Security Group menu. You will be taken to the Security Group List page.
- Select the Security Group resource created in 1-5. Create Security Group. Navigate to the detailed information page of that resource.
- On the detail information page, click the Rules tab. You will be taken to the Rules tab.
- On the Rules tab, click the Add Rule button. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
direction Remote target address Protocol port Explanation Inbound CIDR User PC IP TCP 3389 (RDP) Bastion client PC → Bastion host Outbound CIDR DB IP TCP Database Port (manual entry) Bastion host → Database Table. Security Group rules that need to be added
4-2. Add IGW Firewall Rule
- All Services > Networking > Firewall Click the menu. Go to the Service Home page of the Firewall.
- On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
- On the Firewall List page, select the Internet Gateway Resource Name created in 1-3. Internet Gateway 생성하기. You will be taken to the detailed information page for that resource.
- Click the Rules tab on the detail information page. You will be taken to the Rules tab.
- On the Rules tab, click the Add Rule button. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
origin address Destination address Protocol Port Operation direction Explanation Bastion connection PC IP Bastion host IP TCP 3389(RDP) Allow Inbound User PC → Bastion host Table. Internet Gateway Firewall rules that need to 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 pgAdmin. Since there are various database client programs and CLI utilities, you may install and use the tool that best fits your needs.
5-1. Connecting to Bastion host
- In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
- When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password verified in 2-3. Bastion host Access ID and PW Check and click the Confirm button.
5-2. Install DB client program (pgAdmin) on the Bastion host
- Go to the official pgAdmin page and download the pgAdmin program.
- pgAdmin program download URL: https://www.pgadmin.org/download/
- Connect the user’s PC hard drive to upload the file to the Bastion host.
- In the Remote Desktop Connection Local Resources tab, click the Details button for the Local Devices and Resources entry.
- Select the local disk of the location where the file was downloaded on the drive, and click the OK button.
- Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install.
5-3. Connect to the database using the DB client program (pgAdmin)
- Run pgAdmin and click the Add New Server button.
- Register - Server popup window, enter the Database server information created in 3-1. EPAS(DBaaS) Create Service into the General and Connection tabs, and click the Save button.
Screen (tab) Required input field input value General Name Custom (ex. service name) Connection Host name/address Database server IP Connection Port Database Port Connection Maintenance database Database name Connection Password Database password Table: DB connection client program input fields - Click the name of the database created in pgAdmin to connect.
- After connecting, you can perform simple queries, among other tasks.
1.2.5 - Extension Usage
Using EPAS(DBaaS) Extension
You can view the list of extensions that can be installed in the current database with the SQL statement below.
SQL> select * from pg_available_extensions;
In EPAS(DBaaS), the items installed in addition to the default extensions included per version are as follows.
| Extension name | Explanation |
|---|---|
| pg_cron | A scheduler that can schedule jobs using cron syntax within the database. |
| pgvector | Provides AI vector operation features such as vector data types and similarity search. |
| postgis | Provides GIS (Geographic Information System) spatial object storage and spatial query functionality |
If you need to install additional extensions beyond the items above, refer to Support Center > Inquiry and contact us.
- After a request is received, we will review it and proceed with installation. Please note that some extensions may not function properly during replica configuration and recovery.
1.3 - API Reference
1.4 - CLI Reference
1.5 - Release Note
EPAS(DBaaS)
- You can set up a disaster-recovery Replica using the Replica configuration (Other Region) feature.
- Strengthen the latest security patches and stability through the OS (Kernel) upgrade feature.
- EPAS(DBaaS) feature addition
- Add Second-Generation Server Type
- Add a 2nd‑generation (db2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, see EPAS(DBaaS) 서버 타입.
- DB user and access control management and Archive configuration feature added
- For more details, refer to DB User Management, DB Access Control Management, Archive Management.
- DB Audit Log Export feature added
- For more details, refer to DB Log Export.
- Backup Notification Feature provided
- Provides notification functionality for backup success and failure. For more details, refer to Create Notification Policy.
- Add Migration feature
- Provides replication-based zero-downtime data migration functionality. For more details, see Migration Configuration.
- Add HDD, HDD_KMS types to Block Storage type
- Add Second-Generation Server Type
- A web-based EPAS (DBaaS) service that allows easy creation and management of EPAS has been launched.
2 - PostgreSQL(DBaaS)
2.1 - Overview
Service Overview
PostgreSQL (DBaaS) is an open-source relational database management system (RDBMS). Samsung Cloud Platform provides an environment that automates PostgreSQL installation through a web-based console and performs management functions for operation.
PostgreSQL (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 up to five read‑only Replica servers for read load balancing and disaster recovery (DR) are provided. Additionally, to prepare for potential issues with the DB server or data, we provide a feature that automatically backs up at a user-specified time, enabling recovery of data at the desired point.
Provided Features
PostgreSQL (DBaaS) provides the following features.
- Auto Provisioning: UI allows installation and configuration of Database (DB), and provides an Active‑standby redundancy configuration built 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 files and archive files.
- Version Management: Provides version upgrade (Minor) functionality due to certain feature improvements 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: For load balancing reads and disaster recovery (DR), up to five Read Replicas can be configured in the same or different regions.
- Audit Settings: Supports audit (Audit) functionality for key activities within the database.
- Parameter management: You can modify DB configuration parameters related to performance improvement and security.
- Service Status Query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, and DB performance monitoring information can be accessed through the Cloud Monitoring service.
- 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 to 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 operational 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
PostgreSQL(DBaaS) provides pre‑validated engine versions and various server types in accordance with the open‑source support policy. Users can select and use it according to the scale of the service they wish to configure.
Engine version
The engine versions supported by PostgreSQL (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.
- PostgreSQL: https://www.postgresql.org/support/versioning/
| Provided version | EOS Date (Samsung Cloud Platform new creation stop date) | EoTS Date (Community Technical Support End Date) |
|---|---|---|
| 14.17 | 2026-05-20 | 2026-11-12 |
| 14.18 | 2026-05-20 | 2026-11-12 |
| 14.19 | 2026-05-20 | 2026-11-12 |
| 15.12 | 2027-06 (planned) | 2027-11-11 |
| 15.13 | 2027-06 (planned) | 2027-11-11 |
| 15.14 | 2027-06 (planned) | 2027-11-11 |
| 16.8 | 2028-06 (planned) | 2028-11-09 |
| 16.9 | 2028-06 (planned) | 2028-11-09 |
| 16.10 | 2028-06 (planned) | 2028-11-09 |
| 17.6 | 2029-06 (planned) | 2029-11-08 |
The next version of PostgreSQL is scheduled to be available after July 2026. The actual service delivery schedule is subject to change.
- PostgreSQL 15.15
- PostgreSQL 16.11
- PostgreSQL 17.17
Server type
The server types supported by PostgreSQL (DBaaS) are as follows.
For detailed information about the server types offered by PostgreSQL(DBaaS), see PostgreSQL(DBaaS) Server Types.
Standard db1v2m4
| Category | Example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server types
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
Preceding Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
2.1.1 - Server Types
PostgreSQL(DBaaS) server type
PostgreSQL (DBaaS) offers server types composed of various combinations of CPU, Memory, and Network Bandwidth. When creating PostgreSQL(DBaaS), the Database Engine is installed based on the server type chosen for the intended use.
The server types supported by PostgreSQL (DBaaS) are as follows.
Standard db1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classifications
|
| Server specifications | db1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
db1 server type
The db1 server type of PostgreSQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db1v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
db2 server type
The db2 server type of PostgreSQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db2v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db2v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db2v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db2v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db2v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db2v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db2v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db2v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db2v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db2v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db2v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db2v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db2v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db2v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db2v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db2v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db2v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db2v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db2v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db2v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db2v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db2v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
dbh2 server type
The dbh2 server type of PostgreSQL (DBaaS) is provided with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 128 vCPUs and 1,536 GB of memory
- Networking speed up to 25 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Maximum 25 Gbps |
2.1.2 - Monitoring metrics
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service per Resource
- New Resources: Resources created after the service improvement work in July 2026 are monitored by default using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring via Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings linked with existing Cloud Monitoring (e.g. You must verify items such as event policies and perform tasks such as resetting the ServiceWatch service, then complete them.
Cloud Monitoring Service Phased Termination Schedule Notice
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period.**
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
PostgreSQL(DBaaS) Monitoring Metrics
The table below shows performance monitoring metrics for PostgreSQL (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
For PostgreSQL (DBaaS), refer to the Virtual Server Monitoring Metrics guide.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Locks [Access Exclusive] | Number of Access Exclusive Locks | cnt |
| Active Locks [Access Share] | Number of Access Share Locks | cnt |
| Active Locks [Total] | Total number of active locks | cnt |
| Active Sessions | Number of Sessions in Active state | cnt |
| Active Sessions [Total] | Total number of Sessions in Active state | cnt |
| Apply Lag Time | Apply lag time | min |
| Check No Replication | Check No Replication value | cnt |
| Check Replication | Check Replication Status value | status |
| Connection Usage | DB connection usage rate (%) | % |
| Connection Usage [Total] | DB connection usage rate (%) | % |
| DB Age Max | Database age (frozen XID) value | age |
| Exclusive Locks | Number of Exclusive Locks | cnt |
| Idle In Transaction Sessions | Number of sessions in idle-in-transaction state | cnt |
| Idle In Transaction Sessions [Total] | Total number of sessions in Idle in transaction state | cnt |
| Idle Sessions | Number of idle sessions | cnt |
| Idle Sessions [Total] | Total number of sessions in Idle state | cnt |
| Row Exclusive Locks | Number of Row Exclusive Locks | cnt |
| Row Share Locks | Row Share Locks count | cnt |
| Share Locks | Number of Share Locks | cnt |
| Share Row Exclusive Locks | Number of Share Row Exclusive Locks | cnt |
| Share Update Exclusive Locks | Number of Share Update Exclusive Locks | cnt |
| Slowqueries | Number of SQL queries running for a long time (over 5 minutes) | cnt |
| Tablespace Used | Table space size | bytes |
| Tablespace Used [Total] | Table space size | bytes |
| Tablespace Used Bytes [MB] | File system directory usage (MB) | MB |
| Tablespaces [Total] | File system directory usage (MB) | MB |
| Transaction Time Max [Long] | Long-running Transaction time (minutes) | min |
| Transaction Time Max Total [Long] | Long-running Transaction time (minutes) | min |
| Wait Locks | Number of lock-waiting sessions (by DB) | cnt |
| Wait Locks [Long Total] | Number of lock‑waiting sessions lasting 300 seconds | cnt |
| Wait Locks [Long] | Number of sessions waiting due to lock occurrence | cnt |
| Wait Locks [Total] | Total number of sessions waiting due to lock occurrence | cnt |
| Waiting Sessions | Number of Sessions in Waiting state | cnt |
| Waiting Sessions [Total] | Total number of Sessions in Waiting state | cnt |
2.2 - How-to guides
Users can create the service by entering the required information for PostgreSQL (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be 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 released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
- New Resources: Resources created after the service improvement work in July 2026 are provided with monitoring using the ServiceWatch service by default.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring via Cloud Monitoring and ServiceWatch services.
- 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.g. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Notice of the phased termination schedule for Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration work within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
Create PostgreSQL (DBaaS)
You can create and use a PostgreSQL (DBaaS) service from the Samsung Cloud Platform Console.
- Before creating the service, configure the VPC’s subnet type as General.
- If the subnet type is Local, the creation of the corresponding Database service is not possible.
- 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 PostgreSQL(DBaaS), follow the steps below.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) Create button. 2. Navigate to the Create PostgreSQL (DBaaS) page.
Create PostgreSQL (DBaaS) page, enter the information required to create the service and select advanced options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version required Provide a list of PostgreSQL (DBaaS) versions Table. PostgreSQL (DBaaS) Image and version selection options - In the Service Information Input area, enter or select the required information.
Category required statusDetailed description Server name Prefix Required Server name where the DB will be installed - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
-) with a length of 3 to 13 characters
- A postfix such as 001, 002 is appended to the base server name to generate the actual server name
Cluster name Required Cluster name of DB servers - Enter using English letters, 3 to 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for DB installation - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server with 24 vCores or more
- For detailed information about the server types provided by PostgreSQL (DBaaS), refer to PostgreSQL(DBaaS) Server Type
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute Apply
Service Type > Block Storage Required Block Storage configuration used by the DB according to its purpose - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Select a storage type and then enter the capacity (refer to Create 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
- Enter capacity as a multiple of 8 within the range 16–5,120
- Because executing SQL or monthly batch jobs can cause large sorts that may interrupt service, a separate TEMP storage must be allocated and used
- Add: DATA, Archive, TEMP, Backup data storage areas
- 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–5,120
- To add storage, click the Add button; to delete, click the x button. Up to 9 can be added
- Backup data is temporarily stored in the BACKUP storage before transmission
- If the data to be backed up exceeds 100 GB and changes frequently, it is recommended to add a separate BACKUP storage for reliable backup; set the backup capacity to about 60 % of the DATA capacity
- If a BACKUP storage is not added, the
/tmparea is used, and backup will fail if capacity is insufficient
- For each service, Archive, TEMP, and BACKUP storages are allocated only one Block Storage each
- Select a storage type and then enter the capacity (refer to Create Block Storage for details on each Block Storage type)
Redundant configuration Select Redundancy configuration status - When redundancy configuration is used, the DB instance is set up as an Active DB and a Standby DB
Network > Common Settings Required Network settings for servers created by the service - Select when you want to apply the same settings to all installed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be generated automatically
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway; when Use is checked, you can select a reserved IP from the VPC product’s Public IP pool. For more information, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select a reserved IP from the VPC product’s Public IP. For more details, refer to Public IP 생성하기
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day, start time, and duration
- It is recommended to set a maintenance window for stable management of the database. 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.
Table. PostgreSQL (DBaaS) Service Information Input Items - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
- Enter or select the required information in the Database Configuration Required Information Input area.
Category required statusDetailed description Database name Required Server name applied during DB installation - must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
Database username Required DB user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Restricted database user names can be viewed in the Console
Database password Required Password to use when accessing the DB - Enter 8 to 30 characters, including letters, numbers, and special characters (excluding
“‘)
Database password verification Required Re-enter the same password to be used for DB access Database Port number Required Port number required for DB connection - Enter the DB port within the range 1200 ~ 65535
Backup > Use Select Backup usage - Select Use to set the backup file retention period, backup start time, and Archive backup interval
Backup > Retention period Select Backup retention period - Select the backup retention period, set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Period Selection Backup start time - Select backup start time
- The minutes (minutes) during which the backup runs are set randomly, and the backup end time cannot be set
Backup > Archive backup cycle Select Archive backup frequency - Select the archive backup frequency
- The archive backup frequency is recommended to be 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
Audit Log Settings Select Whether to store Audit Log - Select Enable to configure the Audit Log feature
- DDL, DML, and user connection information records are stored
- Users can specify the type of SQL statements to audit via the
log_statementparameter, and can modify it through the Parameter screen
- For detailed information about this parameter, refer to the PostgreSQL documentation
- Users can specify the type of SQL statements to audit via the
- Enabling Audit may degrade database performance
- DDL, DML, and user connection information records are stored
Parameter Required Parameters to be used in the DB - Lookup button can be clicked to view detailed information of the parameter
- Parameters can be modified after the DB creation is complete, and the DB must be restarted after any modifications
Database Encoding Essential Character encoding method to be used for the DB - Character set used when storing text data
- The DB is created with the selected encoding as the default setting
DB Locale Required Locale to be used for the DB - settings related to string handling, number/currency/date/time formatting, etc.
- The DB is created with default settings using the selected Locale
time zone Required Standard time zone for the database Table. PostgreSQL (DBaaS) Database configuration items - In the Additional Information Input area, enter or select the required information.
Category required statusDetailed description Tag Select Add Tag - Up to 50 per resource can be added
- After clicking the Add Tag button, enter or select Key, Value values
Table. PostgreSQL (DBaaS) Additional Information Input Fields
- Select the required information in the Image and version selection area.
Summary Review the detailed information and estimated charges generated in the panel, then click the Create button.
- Once creation is complete, check the created resource on the Resource List page.
View PostgreSQL (DBaaS) details
The PostgreSQL (DBaaS) service allows you to view and edit the full list of resources and detailed information. PostgreSQL(DBaaS) Details page consists of Details, Tags, Activity History tabs, and when the DB has a Replica configured, a Replica Information tab is added.
To view detailed information about the PostgreSQL (DBaaS) service, follow the steps below.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List Click the resource on the page to view detailed information. 3. PostgreSQL(DBaaS) Details Go to the page.
- PostgreSQL(DBaaS) Details The top of the page displays status information and additional feature details.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Creating cluster
- Editing: Cluster is transitioning to an operational state
- Error: Cluster encountered an error during operation
- If it occurs continuously, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Restarting cluster
- Running: Cluster is running normally
- Starting: Starting cluster
- Stopped: Cluster is stopped
- Stopping: Cluster is stopping
- Synchronizing: Synchronizing cluster
- Terminating: Terminating cluster
- Unknown: Unknown cluster status
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is transitioning to an upgrading state
Cluster control Button 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
View more features Cluster-related management buttons - Service status synchronization: Retrieve real-time DB service status
- Backup history: When backup is configured, verify successful execution 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; if the account has no region to configure, the button is disabled
- 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 settings management: Set archive file retention period and enable archive mode
- Export DB logs: Export logs stored via audit settings to the user’s Object Storage
- Migration configuration: Provide migration functionality using replication method
- OS (Kernel) upgrade: Upgrade the OS kernel version
Service termination Button to cancel the service Table. PostgreSQL (DBaaS) status information and additional features
- PostgreSQL(DBaaS) Details The top of the page displays status information and additional feature details.
Detailed information
PostgreSQL (DBaaS) List page allows you to view detailed information of the selected resource and, if needed, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster type | Cluster types (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster name | Cluster name of the DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied during DB installation |
| Database username | DB user name |
| Planned Compute | Resources with Planned Compute configured
|
| maintenance period | DB patch work period setting status
|
| Backup | Backup Configuration Status
|
| Audit Log Settings | Audit Log configuration status
|
| time zone | Standard time zone for the database |
| DB Locale | Locale to use for the DB |
| Database Encoding | Character encoding to use for the DB |
| VIP | Virtual IP information
|
| Network | Network information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP access control | Service access policy configuration
|
| Active & Standby | Active/Standby server type, default OS, additional Disk information
|
Replica information
Replica information tab is enabled only when a Replica is configured in the cluster. Through the Replica information tab, you can view the Master cluster name, the number of replicas, and the replication status of the Replica.
| Category | Detailed description |
|---|---|
| Master information | Name of the Master cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status in the Master cluster
|
tag
On the PostgreSQL (DBaaS) List page, you can view the tag information of the selected resource and add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Work History
On the PostgreSQL (DBaaS) List page, you can view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Managing PostgreSQL (DBaaS) Resources
If you need to change or restore the existing configuration options of a created PostgreSQL (DBaaS) resource, or require a Replica configuration, you can perform the operation on the PostgreSQL(DBaaS) Details page.
Control operation
If changes occur to a running PostgreSQL (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Active‑Standby servers via a switch‑over.
To control the operation of PostgreSQL(DBaaS), follow the steps below.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL (DBaaS) List On the page, click the resource you want to control. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Check the PostgreSQL (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 hosting the DB service and the DB service itself are 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 PostgreSQL (DBaaS).
To check the service status of PostgreSQL (DBaaS), follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List Click the resource on the page to view the service status. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Service Status Synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.
Change server type
You can change the configured server type.
To change the server type, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL (DBaaS) List page, click the resource whose server type you want to change. 3. PostgreSQL(DBaaS) Details Go to the page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Edit Server Type 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 DB configured with redundancy, all redundant servers are added simultaneously.
- It is applied in the same way as the Storage type selected when creating the service.
- In a redundant DB setup, adding storage is applied simultaneously to the storage of both the Active and Standby DBs.
- If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. * First expand the Replica storage, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Go to the page.
- On the PostgreSQL (DBaaS) List page, click the resource to add storage. 3. PostgreSQL(DBaaS) Details Go to the page.
- Click the Add Disk button at the bottom of the details. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.
Expand storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In a redundant DB configuration, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL(DBaaS) List page, click the resource you want to change the server type for. 3. PostgreSQL(DBaaS) Details Go to the page.
- Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
- Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.
Cancel PostgreSQL (DBaaS)
You can cancel unused PostgreSQL (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact that may occur when the service is discontinued.
- For a DB with a Replica configured, terminating the Master DB does not delete the Replica. * If you also delete the replica, 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 PostgreSQL (DBaaS), follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL (DBaaS) List page, select the resource to cancel and click the Cancel Service button.
- After termination is complete, check on the PostgreSQL(DBaaS) list page whether the resource has been terminated.
2.2.1 - DB Service Manage
Users can manage PostgreSQL (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
Provides a feature that allows you to easily view and modify database configuration parameters.
Query Parameters
To retrieve configuration parameters, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource whose parameters you want to view or modify. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management in the popup window, click the Search button. The Search Notification popup window opens.
- Lookup Notification when the popup window opens, click the Confirm button. The lookup may take a short amount of time.
Modify Parameter
To modify the configuration parameters, follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource whose parameters you want to view or modify. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management popup window, click the Search button. Search Notification popup window opens.
- Lookup Notification When the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
- If a modification is needed, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
- When the input is complete, click the Complete button.
DB User Management
Provides management functions to retrieve DB user information and modify status information.
Query DB Users
To retrieve DB users, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Click the Service Home page’s PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource you want to view DB users for. PostgreSQL(DBaaS) Details page will be opened.
- Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
- DB User Management page, click the Search button. Retrieving the data may take a short time.
Changing DB User Status
Follow these steps to change the status of the retrieved DB user.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List On the page, click the resource whose DB user you want to modify. PostgreSQL(DBaaS) Details You will be taken to the page.
- Click the More button, then click the DB User Management button. You will be taken to the DB User Management page.
- On the DB User Management page, click the Search button. The query may take a short time.
- If modification is needed, click the Edit button, and change the status field value or enter remarks.
- When the input is complete, click the Complete button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IPs that can access the database, configuring it so that only authorized IPs are allowed access.
Query DB Access Control
Follow these steps to query DB users with IP access control enabled.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource you want to manage access control for. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a short time.
Add DB access control
To add IP access control, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. You will be taken to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource for which you want to add IP access control. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a short time.
- When the query is complete, click the Add button. The Add DB Access Control popup window opens.
- Add DB Access Control In the popup window, select the DB username and enter the IP address.
- When the input is complete, click the Complete button.
Delete DB access control
To delete IP access control, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Go to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource for which you want to delete IP access control. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a short time.
- When the query is complete, click the Delete button. The Delete popup window will open.
- Click the Confirm button on the Delete popup.
Manage Archive
Provides the ability to configure Archive mode and set the retention period for Archive logs, allowing users to flexibly configure Archive log management policies to suit their operational environment. Additionally, it provides a feature to manually delete Archive logs, allowing you to clean up unnecessary log data and manage system resources effectively.
Configure Archive mode
To set the Archive mode, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page: click the resource for which you want to set Archive mode. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- On the Archive Settings Management page, click the Search button. Retrieval may take a short time.
- Click the Edit button and select the usage status and retention period.
- When the edit is complete, click the Done button.
Delete Archive file
To delete the Archive file, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource for which you want to set Archive mode. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- Archive Settings Management page, if you want to delete all Archive files, click the Delete All Archives button; if you only want to delete backed-up Archive files, click the Delete Backed-up Archives button.
Modify Audit Settings
You can change the Audit log storage settings for PostgreSQL (DBaaS).
Follow these steps to change the Audit log storage settings for PostgreSQL (DBaaS).
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. You will be taken to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page: click the resource to view the service status. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the Edit icon of Audit Settings at the bottom of the detailed information. The Edit Audit Settings popup window opens.
- Edit Audit Settings After modifying the usage in the popup window, click the Confirm button.
- When Enable is selected, the Audit log feature is configured. Enabling the Audit log may degrade DB performance.
- If you turn off Use, the Audit log storage file will be deleted. Before turning it off, back up the Audit log file separately.
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 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 archiving.
- To use the DB Log export feature, you must create an Object Storage. For creating an Object Storage, please refer to the Object Storage User Guide.
- Please be sure to check the expiration date and time of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
- Please ensure that authentication key information is not exposed externally.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource you want to export the DB Log from. PostgreSQL(DBaaS) Details page will open.
- Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
- On the DB Log Export page, click the Register button. You will be taken to the DB Log Export Register page.
- On the DB Log Export Registration page, after entering the required information, click the Complete button.
Category Required Detailed descriptionLog type Required Log type to be saved Save bucket name Required Object Storage bucket name to be saved Authentication key > Access key Required Access key for accessing the Object Storage you want to store Authentication key > Secret key Required Secret key for accessing the Object Storage you want to store File creation cycle Required File creation frequency in Object Storage Whether to delete original logs Selection Whether to delete the original logs when exporting to Object Storage Table. PostgreSQL (DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the Service Home page’s PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- Click the resource you want to manage DB Log export for on the PostgreSQL(DBaaS) List page. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
- On the DB Log Export page, click the More button for the log type you want to manage, then click Export Now, Edit, or Cancel.
- 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: Cancel the DB Log export mode setting.
Minor Version Upgrade
We provide version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades within the same Major version are supported.
- First retrieve the service status by synchronizing it, then perform the version upgrade.
- Please perform the version upgrade after configuring a backup. If you do not set up a backup, you may be unable to recover some data if a problem occurs during the update.
- In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. Please check the Replica version first and, if necessary, perform a version upgrade.
- The backed-up data will be automatically deleted after the version upgrade is completed.
To upgrade the Minor Version, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource to upgrade the version. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the Edit button in the Image version item. The Version Upgrade popup window opens.
- Version Upgrade In the popup, select the updated version and backup setting, then click the Confirm button.
- Version Upgrade Notification Click the Confirm button in the popup window.
Configure Migration
Provides a Migration feature that synchronizes in real time with the live database and replicates using a Replication method without service interruption.
To configure Migration, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- From the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource to migrate. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button, then click the Migration configuration button. The Migration configuration popup opens.
- In the popup window, review the instructions and click the Confirm button. You will be taken to the Migration configuration page.
- Migration Configuration page, after entering the required information, click the Check Connection button.
- When the connection is complete, click the Complete button.
Category Required Detailed descriptionSource DB Database name Required Database name of the source DB to be migrated Source DB IP Required IP of the Source DB that is the migration target Source DB Port Required Port of the Source DB to be migrated Source DB username Required Username of the source DB that is the migration target Source DB password Required Password of the source DB that is the migration target Table. PostgreSQL (DBaaS) migration configuration items
Promote Migration Cluster to Master Cluster
You can promote a configured Migration Cluster to a Master Cluster.
To promote the Migration Cluster to Master, follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- From the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource to promote to Master. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Master Promotion button. The Master Promotion Notification popup window opens.
- In the Master Promotion Notification popup, click the Confirm button.
Upgrade OS Kernel
The OS kernel can be upgraded to improve the functionality of the running database and apply security patches.
- The service will be unavailable while the OS upgrade is in progress.
- The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
- After the upgrade is complete, you cannot revert to the previous OS.
To upgrade the OS kernel, follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- From the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) list page.
- PostgreSQL(DBaaS) List page, click the resource to upgrade the OS Kernel. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button, then click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup window opens.
- OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.
2.2.2 - Backing up and restoring the DB
Users can configure backups of PostgreSQL (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Backing up PostgreSQL(DBaaS)
PostgreSQL (DBaaS) provides a data backup feature 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 backup configuration of PostgreSQL(DBaaS), refer to PostgreSQL(DBaaS) 생성하기.
To modify the backup settings of the created resource, follow the steps below.
For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity.
Especially when the backup data exceeds 100 GB and undergoes frequent changes, please provision additional storage amounting to about 60 % of the data size.
For instructions on adding and expanding storage, refer to the PostgreSQL(DBaaS) Add Storage and PostgreSQL(DBaaS) Expand Storage guides.
If a backup is configured, it will run at the designated time after the set schedule, and additional fees will be incurred based on the backup size.
If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
To set up a backup, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List page, click the resource you want to configure backup for. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Edit button of the backup item. 4. Backup Settings popup window opens.
- When setting up a backup, click Enable in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, and then click the Confirm button.
- If you stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Once user authentication is complete, the backup configuration is disabled and backup execution stops.
- If you stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Check Backup History
To view the backup history, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List page, click the resource to view the backup history. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. Navigate to the PostgreSQL (DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource to view the backup history. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
- When user authentication is completed, the backup file is deleted.
PostgreSQL(DBaaS) Recover
If a failure or data loss requires restoration from a backup file, you can recover using the recovery feature based on a specific point in time. When performing a PostgreSQL (DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds with the database’s configuration information and data.
To recover PostgreSQL (DBaaS), follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) resource Click the resource you want to restore on the list page. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Database Recovery button. 4. Go to the Database Recovery page.
- After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
Category required statusDetailed description Recovery Type Required Set the point in time the user wants to recover - Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
- Custom point: Recover to a user-specified point within the range of recoverable backup times. The recoverable period depends on the Archive backup cycle setting, allowing recovery from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the desired date and time for the backup
server name prefix Essential Recovery DB server name - must start with a lowercase English letter and use lowercase letters, numbers, and special characters (
-) to input 3 to 16 characters
- A postfix such as 001, 002 is appended to the base server name, generating the actual server name
Cluster name Required Cluster name of the recovery DB - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for the recovery DB installation - Standard: standard specifications commonly used
- High Capacity: large-capacity server with 24 vCores or more
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service request page
- For more details, see Planned Compute 신청하기
Service Type > Block Storage Required Block Storage settings used by the recovery DB - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Same as the storage type set in the original cluster
- Enter capacity as a multiple of 8 within the range 16 to 5,120
- Additional: Storage area for DATA, Archive, TEMP, Backup data
- Same as the storage type set in the original 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
Database username Required Database username configured in the source DB Database Port number Required Database port number configured in the source DB IP access control Select IP address for accessing the recovery DB - Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.1/32,192.168.10.1/32), then click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of week, start time, and duration
- It is recommended to set a maintenance window for stable DB management. 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.
Tag Select Add Tag - Add Tag after clicking the button Enter or select Key, Value values
Table. PostgreSQL (DBaaS) recovery configuration items
2.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
Through replica configuration, you can create replica servers for read-only or disaster recovery purposes. You can create up to 5 replicas per database.
To configure a Replica, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL(DBaaS) List page, click the resource to configure a Replica. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Replica configuration button. 4. Go to the Replica configuration page.
- After entering the information in the Replica configuration area, click the Complete button.
Category required statusDetailed description Region Required Region to configure the Replica - Replica configuration (Other Region)is displayed only when selected
Replica count Required Number of Replicas to configure - Up to 5 can be configured per cluster
- If you select more than one value, additionally enter the Replica name and service type information
Replica name Required Replica server name - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters(
-) enter 3 to 19 characters
- The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type Essential Replica server type - Standard: standard specification commonly used
- High Capacity: large-capacity server with 24 vCores or more
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute 신청하기
Service Type > Block Storage Required Block Storage configuration for using a replica DB - Basic OS: Area used on the server where the DB is installed
- Applied identically according to the storage type set in the source DB
- Capacity cannot be set
- DATA: Storage area for table data, archive files, etc.
- Applied identically according to the storage type set in the source DB
- Capacity cannot be set
- Additional: Storage area for DATA, Archive, TEMP, Backup data
- Applied identically according to the storage type set in the source DB
- In a replica, only DATA and TEMP purposes can be added
- After selecting Use, enter the storage purpose and capacity. Capacity must be 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.
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - Select Use to set the day, start time, and duration
- It is recommended to configure a maintenance window for stable database management. Patch operations will be performed at the scheduled time, causing service interruption
- If set to unused, we are not responsible for issues arising from patches not being applied.
tag Selection Add Tag - Add Tag After clicking the Add Tag button, enter or select Key and Value
Table. PostgreSQL (DBaaS) Replica configuration items
Reconfigure Replica
If a network failure or replication delay with the Master Cluster occurs, you can re-replicate the Master Cluster’s data using the Replica reconstruction feature.
To reconfigure the Replica, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL(DBaaS) List page, click the resource to reconfigure the replica. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Replica Reconstruction Click the button. 4. Replica Reconfiguration Notification A popup window opens.
- Replica Reconfiguration Notification popup window, click the Confirm button.
Promoting a Replica Cluster to a Master Cluster
You can promote a fully configured Replica Cluster to a Master Cluster.
To promote a Replica Cluster to Master, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List page, click the resource to promote to Master. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the More button, then click the Master Promotion button. 4. Master Promotion Notification The popup window opens.
- Master Promotion Notification In the popup window, click the Confirm button.
2.2.4 - DB Server Connection
Scenario Overview
PostgreSQL(DBaaS) Server Connection The 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 PostgreSQL (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish network connectivity using it. It is recommended to configure the Database service in a Private Subnet environment and the Bastion host in a restricted Public Subnet environment to maintain stability and a high level of security.
This scenario primarily describes creating a Bastion host and a Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Scenario components
You can build the scenario using the following services.
| Service group | service | Detailed description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that lets users subdivide the network within a VPC to match their purpose and scale. | |
| Networking | VPC > Public IP | A service that reserves a public IP and allocates and releases it to Compute resources. | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the Internet | |
| Networking | Security Group | Virtual firewall that controls server traffic | |
| Database | PostgreSQL(DBaaS) | A service that easily creates and manages EPAS in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- Since the default policy of a Security Group is Deny All, you must register only the allowed IPs.
- The All Open (Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
- By specifying the required IP and port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the steps below.
Set up the network
This explains the process of configuring the network environment for accessing the Bastion Host and Database services.
1-1. Create VPC
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- Click the VPC Creation button on the Service Home page. You will be taken to the VPC Creation page.
- On the VPC Creation page, enter the information required to create the service.
- Enter the IP range as
192.168.x.0/16.
- Enter the IP range as
- Summary panel, verify the detailed information and estimated billing amount generated there, and click the Complete button.
- After creation is complete, check the created resources on the VPC List page.
1-2. Create Subnet
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
- Click the Create Subnet button. You will be taken to the Create Subnet page.
- On the Subnet Creation page, enter the information required to create the service.
- Select the Subnet type as General.
- Select a pre‑created VPC.
- Enter the IP range as
192.168.x.0/24.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, check the created resources on the Subnet List page.
1-3. Create Internet Gateway
- Click the All Services > Networking > VPC menu. Go to the VPC’s Service Home page.
- On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
- Click the Create Internet Gateway button. You will be taken to the Create Internet Gateway page.
- On the Internet Gateway Creation page, enter the required information to create the service.
- Select a pre‑created VPC.
- In the Firewall usage option, select Use.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resource on the Internet Gateway list page.
1-4. Create Public IP
- Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Public IP menu. You will be taken to the Public IP List page.
- Click the Public IP Reservation button. You will be taken to the Public IP Reservation page.
- On the Public IP reservation page, enter the required information needed to reserve the service.
- 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 Public IP List page.
1-5. Create Security Group
- Click the All Services > Networking > Security Group menu. Navigate to the Service Home page of Security Group.
- Click the Create Security Group button on the Service Home page. You will be taken to the Create Security Group page.
- Security Group creation Enter the required information needed to create the service on the page.
- Check the input information and click the Complete button.
- When creation is complete, check the created resources on the Security Group List page.
Create bastion host
Describes the process of configuring a Bastion Host that requires the database client to be installed.
2-1. Create Server Keypair
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
- Click the Create Keypair button. You will be taken to the Create Keypair page.
- On the Keypair Creation page, enter the required information needed to create the service.
- Verify the creation information and click the Complete button.
- The key can be downloaded only on the first attempt, and reissuance is not available.
- Please store the downloaded key in a secure location.
2-2. Create Bastion host
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Virtual Server Creation button. You will be taken to the Virtual Server Creation page.
- On the Virtual Server Creation page, enter the required information to create the service.
- Select Windows for the image.
- Select the pre‑created VPC and Subnet.
- Click Use NAT, and select the reserved Public IP from 1-4. Create Public IP.
- 2-1. Create Server Keypair Connect the Keypair created there.
- 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 Virtual Server List page.
2-3. Verify Bastion host login ID and password
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- Click the Virtual Server menu on the Service Home page. You will be taken to the Virtual Server List page.
- On the Virtual Serve List page, click the resource you created in 2-2. Bastion host Create. You will be taken to that resource’s detailed information page.
- On the detail page, click the RDP password view button in the Keypair name field. The RDP password view popup window will open.
- In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
- After attaching, click the Password Check button. The ID and Password required to access the resource are displayed.
- The ID and password will later be used as credentials to access the Bastion host in 5-1. Bastion host Connecting.
Create Database
Describes the process of creating a Database service.
3-1. Create PostgreSQL (DBaaS) Service
- Click the All Services > Database > PostgreSQL(DBaaS) menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) Create button on the Service Home page. You will be taken to the PostgreSQL(DBaaS) Create page.
- PostgreSQL(DBaaS) Creation On the page, enter the required information to create the service.
- Select the pre‑created VPC and Subnet and connect them.
- Enter the database-related creation information on the required information input screen.
- Add the Bastion host IP in the IP access control section.
- The Database Port defaults to 2866, but the user can also specify it.
- In the Summary panel, verify the detailed information and estimated billing amount, then click the Complete button.
- After creation is complete, verify the created resource on the PostgreSQL(DBaaS) list page.
Configuring 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. Security Group Add Security Rules
- Click the All Services > Networking > Security Group menu. Navigate to the Service Home page of Security Group.
- From the Service Home page, click the Security Group menu. You will be taken to the Security Group List page.
- Select the Security Group resource created in 1-5. Create Security Group. Navigate to the detailed information page of that resource.
- Click the Rules tab on the detail page. You will be taken to the Rules tab.
- On the Rules tab, click the Add Rule button. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
direction remote Target address Protocol Port Explanation Inbound CIDR User PC IP TCP 3389 (RDP) Bastion client PC → Bastion host Outbound CIDR DB IP TCP Database Port (manual entry) Bastion host → Database Table: Security Group rules that need to be added
4-2. Add IGW Firewall Rule
- All Services > Networking > Firewall Click the menu. Go to the Service Home page of the Firewall.
- On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
- On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway Creation. You will be taken to the detailed information page of that resource.
- Click the Rules tab on the detail information page. You will be taken to the Rules tab.
- Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
origin address Destination address Protocol Port Operation direction Explanation Bastion connection PC IP Bastion host IP TCP 3389(RDP) Allow Inbound User PC → Bastion host Table. Internet Gateway Firewall rules that need to 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 pgAdmin. Since there are various database client programs and CLI utilities, you may install and use the tool that best fits your needs.
5-1. Connecting to Bastion host
- In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
- When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password you verified in 2-3. Bastion host access ID and PW verification and click the Confirm button.
5-2. Install DB connection client program (pgAdmin) on the Bastion host
- Go to the official pgAdmin page and download the pgAdmin program.
- pgAdmin program download URL: https://www.pgadmin.org/download/
- Connect the user’s PC hard drive to upload the file to the Bastion host.
- In the Local Resources tab of the Remote Desktop Connection, click the Details button for the Local Devices and Resources item.
- Select the local disk of the location where the file was downloaded on the drive, and click the OK button.
- Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install.
5-3. Connect to the database using the DB client program (pgAdmin)
- Run pgAdmin and click the Add New Server button.
- In the Register - Server popup window, enter the Database server information created in 3-1. PostgreSQL(DBaaS) 서비스 생성하기 into the General and Connection tabs, and click the Save button.
Screen (tab) Required input field input value General Name Custom (ex. service name) Connection Host name/address Database server IP Connection Port Database Port Connection Maintenance database Database name Connection Password Database password Table.DB connection client program input fields - Click the name of the database created in pgAdmin to connect.
- After connecting, you can perform simple queries, among other tasks.
2.2.5 - Extension Use
PostgreSQL(DBaaS) Extension usage
You can view the list of extensions that can be installed in the current database with the SQL statement below.
SQL> select * from pg_available_extensions;
PostgreSQL (DBaaS) includes the following items in addition to the default extensions for each version.
| Extension name | Explanation |
|---|---|
| pgaudit | Provides detailed audit logging at the session and object level |
| pg_cron | A scheduler that can schedule jobs using cron syntax within the database. |
| pg_hint_plan | Provides a feature to apply hint clauses to SQL execution plans. |
| pgvector | Provides vector data types and AI vector operation features such as similarity search. |
| postgis | GIS (Geographic Information System) provides spatial object storage and spatial query functionality |
If you need to install additional extensions beyond the items above, refer to Support Center > Inquiry and contact us.
- After a request is received, we will review it and proceed with installation. Please note that some extensions may not function properly during replica configuration and recovery.
2.3 - API Reference
2.4 - CLI Reference
2.5 - Release Note
PostgreSQL(DBaaS)
- The OS (Kernel) upgrade feature enhances the latest security patches and stability.
- You can set up a disaster-recovery Replica using the Replica configuration (Other Region) feature.
- Add PostgreSQL (DBaaS) feature
- Add Second-Generation Server Type
- Add a second‑generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) processor. For more details, see PostgreSQL(DBaaS) 서버 타입.
- DB user and access control management and Archive configuration feature added
- For more details, see DB User Management, DB Access Control Management, Archive Management.
- DB Audit Log Export feature added
- For more details, refer to DB Log Export.
- Backup Notification Feature provided
- Provides notification functionality for backup success and failure. For detailed information, refer to Create Notification Policy.
- Add Migration feature
- Provides replication-based zero-downtime data migration functionality. For more details, see Configuring Migration.
- Add HDD, HDD_KMS types to Block Storage type
- Add Second-Generation Server Type
- PostgreSQL(DBaaS) feature change
- Add new PostgreSQL versions: 13.16, 14.13, 15.8
- Add second-generation server type
- Add a 2nd‑generation (dbh2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, see PostgreSQL(DBaaS) server type.
- After creating the service, Block Storage capacity expansion is possible.
- Server-specific network IP configuration feature has been added allowing either a common configuration or a server-specific configuration depending on the intended use.
- Samsung Cloud Platform common feature changes
- Account, IAM, Service Home, tags, and other common CX changes have been applied.
- A volume-encrypted storage selection option has been added to the Block Storage type.
- A Role Switch (Active ↔ Standby) feature has been added for the Active DB and Standby DB configured with redundancy.
- It is linked with the cloud monitoring service, enabling performance and log monitoring of DB instances.
- Based on the server type selected by the customer, Planned Compute policy can be set.
- A PostgreSQL (DBaaS) service that enables easy creation and management of PostgreSQL in a web environment has been launched.
3 - MariaDB(DBaaS)
3.1 - 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 contents of the Active server change, they are synchronously replicated to the Standby server, and up to five read‑only Replica servers for read load balancing and disaster recovery (DR) are provided. Additionally, it provides an automatic backup feature at user-specified times to prepare for issues with the DB server or data, enabling recovery of data at the desired point in time.
Provided Features
MariaDB (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. * Backup time windows and storage locations can be set by the user, and additional fees are incurred 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 some functionality improvements 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).
- Audit configuration: Provides an Audit configuration feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
- Parameter management: Performance improvements and security-related DB configuration parameters can be modified.
- Service Status Query: Retrieves the final status of the current DB service.
- 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 Archive file retention period (1 to 35 days) on 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 operational database and support migration using replication without service interruption.
- OS Kernel Upgrade: You can upgrade the OS Kernel to apply some feature improvements and security patches.
Component
MariaDB(DBaaS) provides pre‑validated engine versions and various server types in accordance with its 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 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 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.
- 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-19 | 2026-07-06 |
| 10.6.9 | 2026-03-19 | 2026-07-06 | |
| 10.6.10 | 2026-03-19 | 2026-07-06 | |
| 10.6.12 | 2026-03-19 | 2026-07-06 | |
| 10.6.14 | 2026-03-19 | 2026-07-06 | |
| 10.6.15 | 2026-03-19 | 2026-07-06 | |
| 10.6.16 | 2026-03-19 | 2026-07-06 | |
| 10.6.17 | 2026-03-19 | 2026-07-06 | |
| 10.6.19 | 2026-03-19 | 2026-07-06 | |
| 10.6.22 | 2026-03-19 | 2026-07-06 | |
| 10.11.8 | 2027-09 (planned) | 2028-02-16 | |
| 10.11.9 | 2027-09 (planned) | 2028-02-16 | |
| 10.11.13 | 2027-09 (planned) | 2028-02-16 | |
| 11.4.7 | 2028-12 (planned) | 2029-05-29 |
The next version of MariaDB is scheduled to be available after July 2026. The actual service delivery schedule is subject to change.
- MariaDB 10.11.15
- MariaDB 11.4.10
Server type
The server types supported by MariaDB (DBaaS) are as follows.
For detailed information about the server types offered by MariaDB (DBaaS), refer to MariaDB(DBaaS) Server Types.
Standard db1v2m4
| Category | Example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server types
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | vCore count
|
| Server specifications | m4 | Memory capacity
|
Preceding Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
3.1.1 - Server Types
MariaDB(DBaaS) server type
MariaDB(DBaaS) provides server types composed of various combinations of CPU, memory, and network bandwidth. When creating a MariaDB(DBaaS), the Database Engine is installed according to the server type selected for the intended use.
The server types supported by MariaDB (DBaaS) are as follows.
Standard db1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classifications
|
| Server specifications | db1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
db1 server type
The db1 server type of MariaDB(DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db1v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | db1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db1v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
db2 server type
The db2 server type of MariaDB (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db2v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | db2v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db2v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db2v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db2v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db2v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db2v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db2v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db2v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db2v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db2v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db2v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db2v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db2v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db2v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db2v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db2v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db2v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db2v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db2v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db2v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db2v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db2v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
dbh2 server type
The dbh2 server type of MariaDB (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 128 vCPUs and 1,536 GB of memory
- Networking speed up to 25 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Maximum 25 Gbps |
3.1.2 - Monitoring Metrics
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service 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 concurrent monitoring through Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (ex. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Notice of the phased termination schedule for the Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
* Service termination (November 2026 service improvement work)
* All services of Cloud Monitoring, including the API, will be permanently discontinued.
* **After the service ends in November, Cloud Monitoring data cannot be accessed.** * Be sure to complete the ServiceWatch migration within the parallel operation period**.
Detailed information about ServiceWatch can be found in the ServiceWatch Overview.
MariaDB(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics for MariaDB (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
The server monitoring metrics for MariaDB (DBaaS) can be found in the Virtual Server Monitoring Metrics guide.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Sessions | Number of Active Sessions | cnt |
| Connection Usage [Total] | DB connection session usage rate | % |
| Connections | Number of connections | cnt |
| Connections [MAX] | max connected threads count | cnt |
| Binary Log Used [MB] | binary log usage | MB |
| Data Directory Used [MB] | data directory usage | MB |
| Open Files | Number of open DB files | cnt |
| Open Files [MAX] | Number of DB files that can be opened | cnt |
| Open Files Usage | DB file maximum count usage rate | % |
| Relay Log Used [MB] | relay log usage | MB |
| Instance Status [PID] | mariadbd process | pid |
| Safe PID | mariadbd_safe process | pid |
| Slave Behind Master seconds | Data time difference between Master and Slave (run only on slave) | sec |
| Tablespace Used | Tablespace usage | MB |
| Tablespace Used [Total] | Total tablespace usage | MB |
| Running Threads | running thread count | cnt |
| Slowqueries | Number of SQL queries running for a long time (over 5 minutes) (by DB) | cnt |
| Slowqueries [Total] | Number of long-running (5 minutes or more) SQL queries (total) | cnt |
| Transaction Time [Long] | Maximum transaction execution time | sec |
| Wait Locks | Number of sessions blocked for more than 60 seconds by lock | cnt |
3.1.3 - ServiceWatch Metrics
MariaDB sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1‑minute interval.
Basic Metrics
The following are the basic metrics for the namespace MariaDB(DBaaS).
The indicators whose names are shown in bold below are the key indicators selected among the basic metrics provided by MariaDB(DBaaS). The key metrics are used to configure the service dashboards that are automatically built for each service in ServiceWatch.
Each metric guides users, through the user guide, on which statistical values are meaningful when querying 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 these primary statistical values.
OS Basic Metrics
Category | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| CPU | CPU Usage | Percent | CPU usage |
|
| Disk | Disk Usage | Percent | Disk usage |
|
| Disk | Disk Write Bytes | Bytes/Second | Write bandwidth (bytes/second) on block device |
|
| Disk | Disk Read Bytes | Bytes/Second | Read throughput from block device (bytes/second) |
|
| Disk | Disk Write Requests | Count/Second | Number of write requests on block device (requests per second) |
|
| Disk | Disk Read Requests | Count/Second | Number of read requests on block device (requests per second) |
|
| Disk | Average Disk I/O Queue Size | None | Average queue length of requests issued to the block device |
|
| Disk | Disk I/O Utilization | Percent | The proportion of time the block device actually spent handling I/O operations |
|
| Memory | Memory Usage | Percent | Memory usage |
|
| Network | Network In Bytes | Bytes/Second | Received data rate (bytes/second) on the network interface |
|
| Network | Network Out Bytes | Bytes/Second | Transmitted capacity (bytes/second) on the network interface |
|
| Network | TCP Connections | Count/Second | Current total number of successfully established TCP connections |
|
| Network | Network In Packets | Count | Number of packets received on the network interface |
|
| Network | Network Out Packets | Count | Number of packets transmitted on the network interface |
|
| Network | Network In Dropped | Count | Number of packet drops received on the network interface |
|
| Network | Network Out Dropped | Count | Number of packet drops transmitted from the network interface |
|
| Network | Network In Errors | Count | Number of packet errors received on the network interface |
|
| Network | Network Out Errors | Count | Number of packet errors transmitted on the network interface |
|
MariaDB basic metrics
Category | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| Activelock | Active locks | Count | Number of transactions in the InnoDB storage engine that have been in lock wait state for 1 minute (60 seconds) or longer. |
|
| Activesession | Active sessions | Count | Number of active sessions |
|
| Activesession | Connection usage | Percent | DB connection session usage rate |
|
| Activesession | Connections | Count | DB connection session |
|
| Activesession | Aborted Connections | Count/Minute | Number of abnormal terminated connections |
|
| Datafile | Current open files | Count | Number of file descriptors opened by the DB |
|
| Datafile | Max open files | Count | Maximum number of file descriptors the DB can open |
|
| Datafile | Open files usage | Percent | DB file maximum count utilization |
|
| InnoDB | InnoDB buffer pool hit ratio | Percent | The ratio of data read directly from memory without accessing the disk |
|
| InnoDB | Innodb row lock wait transactions | Count | Current number of InnoDB transactions waiting for a row lock |
|
| InnoDB | InnoDB row lock time | Milliseconds | Total time waited due to InnoDB row locks (in milliseconds) |
|
| InnoDB | InnoDB deadlocks | Count/Minute | Number of transactions rolled back due to deadlock |
|
| InnoDB | Table lock waits | Count/Minute | Number of waits that occurred to acquire a table lock |
|
| InnoDB | Temp disk tables | Count/Minute | Number of Temp Tables created on disk |
|
| InnoDB | Innodb log waits | Count | Number of times waited to write the redo log to disk |
|
| State | Instance state | None | Check Scalable DB up/down status
| - |
| State | Slave behind master seconds | Seconds | Replica latency (unit: seconds) |
|
| State | Slave io thread running (Replica Only) | None | I/O Thread status
| - |
| State | Slave SQL thread running (Replica Only) | None | SQL Thread status
| - |
| Tablespace | Tablespace used | Megabytes | Tablespace usage |
|
| Tablespace | Tablespace used(TOTAL) | Megabytes | Tablespace usage (total) |
|
| Transactions | Slow queries | Count | Number of queries running longer than 10 seconds |
|
| Transactions | Long transaction time | Seconds | Long Transaction time |
|
| Transactions | Wait locks | Count | Number of sessions waiting for lock |
|
| Transactions | SQL Queries/Minute | Count/Minute | Queries executed per minute |
|
3.2 - How-to guides
Users can create the service by entering the required information for MariaDB (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service per Resource
- New Resources: Resources created after the March 2026 service improvement work are provided with default monitoring 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, we must prepare for the Servicewatch transition. *
Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (e. You must review the event policies, etc., and perform tasks such as resetting the ServiceWatch service, then complete them.
Notice of the phased termination schedule for the Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
Create MariaDB (DBaaS)
You can create and use a MariaDB (DBaaS) service from the Samsung Cloud Platform Console.
- Before creating the service, configure the VPC’s subnet type as General.
- If the subnet type is Local, the corresponding Database service cannot be created.
- When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to the statistical collection environment.
To create a MariaDB (DBaaS), follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the Create MariaDB (DBaaS) button. 2. Go to the Create MariaDB (DBaaS) page.
- Create MariaDB (DBaaS) on the page, enter the information required to create the service, and select detailed options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version Required Provide a list of MariaDB (DBaaS) versions Table. MariaDB (DBaaS) Image and version selection options - In the Service Information Input area, enter or select the required information.
Category required statusDetailed description Server name Prefix Required The server name where the DB will be installed - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
-) with a length of 3 to 13 characters
- a postfix such as 001, 002 is appended to the base server name to generate the actual server name
Cluster name required Cluster name composed of DB servers - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for DB installation - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server with 24 vCores or more
- For detailed information about the server types provided by MariaDB (DBaaS), refer to MariaDB(DBaaS) 서버 타입.
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, refer to Planned Compute Apply
Service Type > Block Storage required Block Storage settings used by the DB according to purpose - Base 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. (For details on each Block Storage type, refer to Block Storage 생성하기)
- 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 service interruptions due to large sorts, a separate TEMP storage must be allocated and used
- Select a storage type and then enter the capacity. (For details on each Block Storage type, refer to Block Storage 생성하기)
- 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 the BACKUP storage before transmitting it
- If the data to be backed up exceeds 100 GB and undergoes frequent changes, it is recommended to add a separate BACKUP storage for reliable backup. Set the backup capacity to about 60 % of the DATA capacity.
- If a BACKUP storage is not added, the
/tmparea is used, and backup fails if capacity is insufficient
- For each service, only one Block Storage is allocated for Archive, TEMP, and BACKUP
Redundancy configuration Select Redundancy configuration - When redundancy is enabled, the DB instance is configured as an Active DB and a Standby DB
Network > Common Settings Required Network settings for servers created by the service - Select when you want to apply the same settings to all installed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be generated automatically
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select a reserved IP from the VPC product’s Public IP. For more information, see Public IP 생성하기
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of week, start time, and duration
- It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
- If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.
Table. MariaDB (DBaaS) Service Information Input Items - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
- Enter required database configuration information Enter or select the required information in this area.
Category required statusDetailed description Database name Required Server name applied during DB installation - must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
Database username Required DB user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Database user names that are restricted can be viewed in the Console
Database password Required Password to use when accessing the DB - Include English letters, numbers, and special characters (
“‘excluded) and enter 8~30 characters
Database password verification Required Re-enter the same password to use for DB access Database Port number Required Port number required for DB connection - Enter the DB port within the range 1200 ~ 65535
Backup > Use Select Backup usage - Select Use to set the backup file retention period, backup start time, and Archive backup interval
Backup > Retention period Select Backup retention period - Select the backup retention period. Set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Period Selection Backup start time - Select backup start time
- The minutes (minutes) at which the backup runs are set randomly, and the backup end time cannot be set
Backup > Archive backup cycle Select Archive backup interval - Select the archive backup interval
- The archive backup interval is recommended to be 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Audit Log Settings Selection Whether to store Audit Log - Select Use to configure the Audit Log feature
- User connection information records are stored
- Users can specify the types of events to audit via the
server_audit_eventsparameter, and can modify it through the Parameter screen
- For detailed information about this parameter, refer to the MariaDB documentation
- Users can specify the types of events to audit via the
- Enabling Audit may degrade database performance
- User connection information records are stored
ServiceWatch log collection Selection Whether to collect ServiceWatch logs - Select Use to configure the ServiceWatch log collection feature
- For details about the collected logs, see ServiceWatch 지표
- Up to 5 GB per account is provided free of charge for all services, and charges apply based on storage usage for amounts exceeding 5 GB
- When collecting, log groups and log streams are created automatically and cannot be deleted until the resources are removed
- To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
Parameter Required Parameters to be used in the DB - Query button can be clicked to view detailed information of the parameters
- Parameters can be modified after the DB creation is complete, and the DB must be restarted after any modifications
DB character set Required Character encoding method to be used for the DB - The character set used when storing text data, set as the default with the selected encoding when the DB is created
time zone Required Standard time zone for the database Table. MariaDB (DBaaS) Database configuration items - In the Additional Information Input area, enter or select the required information.
Category Required statusDetailed description tag Selection Add Tag - Up to 50 per resource can be added
- After clicking the Add Tag button, input or select Key, Value values
Table. MariaDB (DBaaS) additional information input fields
- Select the required information in the Image and version selection area.
- Summary Check the detailed information and estimated charges generated in the panel, and click the Create button.
- Once creation is complete, check the created resource on the Resource List page.
View detailed information for MariaDB (DBaaS)
The MariaDB (DBaaS) service allows you to view and edit the full list of resources and detailed information. MariaDB(DBaaS) Details page consists of Details, Tags, Activity History tabs, and when the DB has a Replica configured, a Replica Information tab is added.
To view detailed information about the MariaDB (DBaaS) service, follow these steps.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List page is accessed.
- On the MariaDB(DBaaS) List page, click the resource to view detailed information. 3. MariaDB(DBaaS) Details Go to the page.
- MariaDB(DBaaS) Details The top of the page displays status information and additional feature details.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Cluster is being created
- Editing: Cluster is transitioning to an operation execution 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 transitioning to an upgrade execution state
Cluster control Buttons to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to Active
More features Cluster management button - Service status synchronization: Real-time DB service status lookup
- Backup history: When backup is configured, verify successful execution and view 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; if the target account has no region to configure, the button is disabled
- 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 settings management: Set archive file retention period and enable archive mode
- DB Log export: Export logs stored via Audit settings to the user’s Object Storage
- Migration configuration: Provide migration functionality using replication
- OS (Kernel) upgrade: Upgrade OS kernel version
Service cancellation Cancel service button Table. MariaDB (DBaaS) status information and additional features
- MariaDB(DBaaS) Details The top of the page displays status information and additional feature details.
Detailed information
On the MariaDB (DBaaS) List page, you can view detailed information of the selected resource and, if necessary, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster type | Cluster types (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster name | Cluster name of the DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied during DB installation |
| Database username | DB user name |
| Planned Compute | Resource status with Planned Compute configured
|
| maintenance period | DB Maintenance Period Status
|
| Backup | Backup Configuration Status
|
| Audit Log Settings | Audit Log configuration status
|
| ServiceWatch log collection | ServiceWatch Log Collection Configuration Status
|
| DB character set | Character encoding to use for the DB |
| time zone | Standard time zone for the database |
| VIP | Virtual IP information
|
| Network | Network information where the DB is installed(VPC, Subnet, VIP, NAT IP(VIP)) |
| IP access control | Service access policy configuration
|
| Active & Standby | Active/Standby server type, base OS, additional Disk information
|
Replica information
Replica information tab is enabled only when a Replica is configured in the cluster. Replica information tab allows you to view the Master cluster name, replica count, and Replica status.
| Category | Detailed description |
|---|---|
| Master information | Name of the Master cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status in the Master cluster
|
tag
MariaDB(DBaaS) List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Work History
MariaDB(DBaaS) List page lets you view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Managing MariaDB (DBaaS) Resources
If you need to change or restore the existing configuration options of a created MariaDB (DBaaS) resource, or require a Replica configuration, you can perform the operation on the MariaDB(DBaaS) Details page.
Control operation
If changes occur to a running MariaDB (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 MariaDB (DBaaS), follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Go to the MariaDB(DBaaS) List page.
- MariaDB (DBaaS) List page, click the resource to control its operation. 3. MariaDB(DBaaS) Details Go to the page.
- Check the MariaDB (DBaaS) status and complete the change using the control button below.
- Start: The 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 MariaDB (DBaaS).
To check the service status of MariaDB (DBaaS), follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource to view the service status. 3. MariaDB(DBaaS) Details Go to the page.
- Click the Service Status Synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.
Change server type
You can change the configured server type.
To change the server type, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Go to the MariaDB(DBaaS) List page.
- On the MariaDB (DBaaS) List page, click the resource to change the server type. 3. MariaDB(DBaaS) Details Go to the page.
- Click the Edit icon for the server type you want to change at the bottom of the detailed information. 4. Edit Server Type popup window opens.
- Server Type Edit In the popup window, select the server type, then click the Confirm button.
Add storage
If you need more than 5 TB of data storage space, you can add additional storage. For a DB configured with redundancy, all redundant servers are added simultaneously.
- It is applied in the same way as the Storage type selected when creating the service.
- For a DB configured with redundancy, adding storage is applied simultaneously to the storage of both the Active DB and the Standby DB.
- If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. * First expand the Replica storage, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow these steps.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB (DBaaS) List page, click the resource to add storage. 3. MariaDB(DBaaS) Details Go to the page.
- Click the Add Disk button at the bottom of the details. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.
Expand storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To expand storage capacity, follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
- Click the resource to change the server type on the MariaDB (DBaaS) List page. 3. MariaDB(DBaaS) Details Go to the page.
- Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
- Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.
Cancel MariaDB(DBaaS)
You can cancel unused MariaDB (DBaaS) to reduce operating costs. Note that terminating the service may cause the currently operating service to stop immediately, so you should proceed with the termination only after fully considering the impact of a service interruption.
- 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 backup data that has been configured will be deleted.
To cancel MariaDB (DBaaS), follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, select the resource to cancel, and click the Terminate Service button.
- After termination is complete, check on the MariaDB(DBaaS) list page whether the resource has been terminated.
3.2.1 - DB Service Manage
Users can manage MariaDB (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
Provides a feature that enables easy viewing and modification of database configuration parameters.
Query Parameter
To view configuration parameters, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- Click the resource whose parameters you want to view or modify on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button, then click the Parameter Management button. The Parameter Management popup opens.
- In the Parameter Management popup, click the Search button. The Search Notification popup opens.
- Lookup Notification When the popup window opens, click the Confirm button. Retrieval may take a short amount of time.
Modify Parameter
To modify the configuration parameters, follow the steps below.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- Click the resource whose parameters you want to view or modify on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button, then click the Parameter Management button. The Parameter Management popup window opens.
- Parameter Management in the popup window, click the Search button. The Search Notification popup window opens.
- Lookup Notification When the popup window opens, click the Confirm button. Retrieving the data may take a short time.
- If a modification is needed, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
- When the input is complete, click the Complete button.
If you change the character_set_server value, first verify the collation that matches the character set using the command below.
SQL> SHOW COLLATION WHERE Charset = 'character set name';
Set the parameter values for character-set-server, collation-server, and init_connect using the verified collation.
| Item | Detailed description | Restart option |
|---|---|---|
character-set-server | Specify the default character set | Restart required |
collation-server | Specify default collation | Restart required |
init_connect | SQL statements executed when the client connects to the database | No restart required |
Managing DB Users
Provides management functions to retrieve DB user information and modify status information.
Query DB users
To view DB users, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource for which you want to view the DB user. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button, then click the DB User Management button. You will be taken to the DB User Management page.
- DB User Management page, click the Search button. It may take a short time to retrieve the data.
Changing DB User Status
To change the status of the retrieved DB user, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- Click the MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource whose DB user you want to modify. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
- DB User Management page, click the Search button. Retrieving the data may take a short while.
- If a correction is needed, click the Edit button, then change the status field value or enter remarks.
- When the input is complete, click the Complete button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IPs that may access the database, configuring it so that only authorized IPs are allowed.
Query DB Access Control
Follow these steps to query DB users with IP access control enabled.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- Click the resource you want to manage access control for on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. The query may take a moment.
Add DB access control
To add IP access control, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource for which you want to add IP access control. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a moment.
- After the query completes, click the Add button. The Add DB Access Control popup opens.
- Add DB Access Control In the popup window, select the DB username and enter the IP address.
- When the input is complete, click the Complete button.
Delete DB access control
To delete IP access control, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. You will be taken to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- MariaDB(DBaaS) List page, click the resource for which you want to delete IP access control. MariaDB(DBaaS) Details page will be opened.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- DB Access Control Management page, click the Search button. Retrieving the data may take a short time.
- When the query is complete, click the Delete button. The Delete popup window opens.
- Delete Click the Confirm button in the popup window.
Managing Archives
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, we provide a feature that allows manual deletion of Archive logs, enabling you to clean up unnecessary log data and manage system resources effectively.
Configure Archive mode
To set the Archive mode, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- MariaDB(DBaaS) List page, click the resource you want to set Archive mode for. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- On the Archive Settings Management page, click the Search button. The query may take a short time.
- Click the Edit button and select the usage status and retention period.
- When the edit is complete, click the Done button.
Delete Archive file
To delete the Archive file, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- MariaDB(DBaaS) List page, click the resource you want to set Archive mode for. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button, then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- On the Archive Settings Management page, if you want to delete all Archive files, click the Delete All Archives button; if you only want to delete the backed‑up Archive files, click the Delete Backed-up Archive button.
Modify Audit Settings
You can change the Audit log storage settings of MariaDB (DBaaS).
To change the Audit log storage settings of MariaDB(DBaaS), follow the steps below.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Go to the MariaDB(DBaaS) List page.
- MariaDB(DBaaS) List page, click the resource to view the service status. You will be taken to the MariaDB(DBaaS) Details page.
- Click the Edit icon of Audit Settings at the bottom of the detailed information. The Edit Audit Settings popup window opens.
- Modify Audit Settings After changing the usage in the popup window, click the Confirm button.
- When Use is selected, the Audit log feature is enabled. Enabling the Audit log may degrade DB performance.
- If you disable it, the Audit log storage file will be deleted. Back up the Audit log file separately before disabling.
Export DB Log
Supports exporting log data that requires long-term retention among audit logs to Object Storage. Users can directly configure the log types to be stored, the target bucket for export, and the export interval. Based on the configured criteria, logs are copied to the specified Object Storage for retention. Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for long-term storage.
- To use the DB Log export function, you need to create an Object Storage. For creating Object Storage, please refer to the Object Storage User Guide.
- Please be sure to check the expiration date and time of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
- Please ensure that authentication key information is not exposed externally.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource you want to export the DB Log from. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
- On the DB Log Export page, click the Register button. You will be taken to the DB Log Export Register page.
- After entering the required information on the DB Log Export Registration page, click the Complete button.
Category Required Detailed descriptionLog type Required Log type to be saved Save bucket name Required Object Storage bucket name to be saved Authentication key > Access key Required Access key for accessing the Object Storage you want to store Authentication key > Secret key Required Secret key for accessing the Object Storage you want to store File creation cycle Required File creation interval in Object Storage Whether to delete the original log Selection Whether to delete the original logs when exporting to Object Storage Table. MariaDB (DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Go to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource you want to manage DB Log export for. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
- On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, or Cancel button.
- Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
- Edit: Modify the DB Log export mode setting.
- Cancel: Disables the DB Log export mode setting.
Minor Version Upgrade
We provide version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades within the same Major version are supported.
- First retrieve the service status by synchronizing it, then perform the version upgrade.
- Please perform the version upgrade after configuring a backup. If you do not set up a backup, you may be unable to recover some data if a problem occurs during the upgrade.
- 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 Minor Version, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. You will be taken to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource to upgrade the version. Navigate to the MariaDB(DBaaS) Details page.
- Click the Edit icon of the Image version item. The Version Upgrade popup window opens.
- Version Upgrade In the popup, select the updated version and whether to enable backup, then click the Confirm button.
- Version Upgrade Notification Click the Confirm button in the popup window.
Configure Migration
Provides a Migration feature that synchronizes in real time with the live database and replicates using a Replication method without service interruption.
To configure Migration, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. You will be taken to the MariaDB(DBaaS) List page.
- MariaDB(DBaaS) List page, click the resource to migrate. MariaDB(DBaaS) Details page will be opened.
- Click the More button, then click the Migration configuration button. The Migration configuration popup opens.
- Migration configuration In the popup window, check the instructions and click the Confirm button. You will be taken to the Migration configuration page.
- On the Migration configuration page, after entering the required information, click the Check connection button.
- When the connection is complete, click the Complete button.
Category Required Detailed descriptionSource DB Database name Required Database name of the source DB to be migrated Source DB IP Required IP of the Source DB that is the migration target Source DB Port Required Port of the Source DB to be migrated Source DB username Required User name of the source DB for migration Source DB password Required Password of the source DB that is the migration target Table. MariaDB (DBaaS) migration configuration items
Promote Migration Cluster to Master Cluster
You can promote a fully configured Migration Cluster to a Master Cluster.
To promote the Migration Cluster to Master, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource to promote to Master. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button, then click the Master Promotion button. The Master Promotion Notification popup opens.
- In the Master Promotion Notification popup, click the Confirm button.
Upgrade OS Kernel
The OS Kernel can be upgraded to improve the functionality of the running database and apply security patches.
- The service will be unavailable while the OS upgrade is in progress.
- The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
- After the upgrade is complete, you cannot revert to the previous OS.
To upgrade the OS Kernel, follow these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource to upgrade the OS Kernel. You will be taken to the MariaDB(DBaaS) Details page.
- Click the More button, then click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup window opens.
- OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.
3.2.2 - Backing up and restoring the database
Users can set up backups for MariaDB (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Backing up MariaDB (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
Refer to MariaDB(DBaaS) Creating for how to configure backups for MariaDB (DBaaS).
To modify the backup settings of the created resource, follow the steps below.
For reliable backups, we recommend adding separate BACKUP storage or sufficiently expanding 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, refer to the MariaDB(DBaaS) Add Storage and MariaDB(DBaaS) Expand Storage guides.
If a backup is configured, it will be performed 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.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
- MariaDB(DBaaS) List page: click the resource you want to configure a backup for. 3. MariaDB(DBaaS) Details Go to the page.
- Click the Edit button of the backup item. 4. Backup Settings The popup window opens.
- When setting up a backup, click Use in the Backup Settings popup, select retention period, backup start time, and Archive backup interval, then click the Confirm button.
- If you want to stop the backup configuration, deselect Use in the Backup Settings popup and authenticate via the logged-in user’s mobile phone.
Once user authentication is completed, the backup configuration is disabled and backup execution stops.
- If you want to stop the backup configuration, deselect Use in the Backup Settings popup and authenticate via the logged-in user’s mobile phone.
Check backup history
To check the backup history, follow these steps.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
- MariaDB (DBaaS) List page: click the resource to view the backup history. 3. MariaDB(DBaaS) Details Go to the page.
- Click the Backup History button. 4. Backup History the popup window opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup files
To delete the backup file, follow these steps.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
- MariaDB (DBaaS) List page: click the resource to view the backup history. 3. MariaDB(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History popup opens.
- Backup History In the popup window, check the files you want to delete, then authenticate via the logged-in user’s mobile phone.
- When user authentication is completed, the backup file is deleted.
Recover MariaDB(DBaaS)
If a backup file must be restored due to a failure or data loss, you can recover to a specific point in time using the recovery feature. When performing a MariaDB(DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the DB is installed with the version from the backup point, and the recovery proceeds with the DB’s configuration information and data.
To recover MariaDB (DBaaS), follow these steps.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB (DBaaS) List Go to the page.
- On the MariaDB (DBaaS) List page, click the resource you want to recover. 3. MariaDB(DBaaS) Details Go to the page.
- Click the Database Recovery button. 4. Go to the Database Recovery page.
- After entering information in the Database recovery configuration area, click the Complete button.
Category required statusDetailed description Recovery Type Required Set the point in time the user wants to recover - Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
- Custom point: Recover to a user‑desired point within the range where backup is possible. 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 date and time to back up
Server name prefix Required Server name of the recovery DB - Start with a lowercase English letter and use lowercase letters, numbers, and special characters (
-) to input 3 to 16 characters
- Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name Required Cluster name of the recovery DB - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Essential Server type for the recovery DB installation - Standard: commonly used standard specification
- High Capacity: large-capacity server with 24vCore or more (to be provided later)
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute 신청하기
Service Type > Block Storage Required Block Storage settings used by the recovery DB - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Applied identically with the storage type set in the source cluster
- Enter capacity as a multiple of 8 within the range 16 to 5,120
- Additional: Storage area for DATA, Archive, TEMP, Backup data
- Applied identically with the storage type set in the source cluster
- In the recovery DB, only DATA, TEMP, and Archive purposes can be added
- After selecting Use, enter the storage purpose and capacity
- To add storage, click the Add button; to delete, click the x button
- Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Database username Required Database username configured in the source DB Database Port number Required Database port number set in the source DB IP access control Selection IP address for accessing the recovery DB - IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.1/32,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of week, start time, and duration
- It is recommended to set a maintenance window for stable DB management. 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.
tag Select Add Tag - After clicking the Add Tag button, enter or select Key, Value values
Table. MariaDB (DBaaS) recovery configuration items
3.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
Through replica configuration, you can create replica servers for read-only or disaster recovery purposes. You can create up to 5 replicas per database.
To configure a Replica, follow these steps.
- All Services > Database > MariaDB (DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB (DBaaS) List page is accessed.
- On the MariaDB (DBaaS) List page, click the resource to configure a Replica. 3. MariaDB(DBaaS) Details Go to the page.
- Click the Replica configuration button. 4. Replica configuration Navigate to the page.
- After entering information in the Replica configuration area, click the Complete button.
Category required statusDetailed description Region Required Region to configure the Replica - Replica configuration (Other Region) is displayed only when selected
Replica count Required Number of Replicas to configure - Up to 5 can be configured per cluster
- If you select more than one value, additionally enter the Replica name and service type information
Replica name Required Replica server name - must start with a lowercase English letter, and use lowercase letters, numbers, and special characters (
-) to enter 3 to 19 characters
- The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type Essential Replica server type - Standard: standard specification commonly used
- High Capacity: large-capacity server with 24vCore or more (to be provided later)
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute 신청하기
Service Type > Block Storage Required Block Storage configuration using Replica 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
- Capacity cannot be set
- Additional: DATA, Archive, TEMP, Backup data storage area
- Applied identically with the storage type set in the source cluster
- In a Replica, only DATA and TEMP can be added
- After selecting Use, input the storage purpose and capacity
- To add storage, click the Add button, and to delete, click the x button
- Capacity can be entered in multiples of 8 within the range 16–5,120, and up to a maximum of 9 can be created, including the number set in the source cluster
IP access control Selection Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of week, start time, and duration
- It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
- If set to unused, we are not responsible for issues arising from patches not being applied.
tag Select Add Tag - after clicking the Add Tag button, Key, Value enter or select
Table. MariaDB (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 these steps.
- Click the All Services > Database > MariaDB(DBaaS) menu. 1. Go to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource to reconfigure the Replica. 3. MariaDB(DBaaS) Details Go to the page.
- Click the Replica Reconstruction button. 4. Replica Reconfiguration Notice A popup window opens.
- Replica Reconfiguration Notification In the popup window, click the OK button.
Promote Replica Cluster to Master Cluster
You can promote a fully configured Replica Cluster to a Master Cluster.
To promote a Replica Cluster to Master, follow these steps.
- All Services > Database > MariaDB(DBaaS) Click the menu. 1. Navigate to the Service Home page of MariaDB (DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
- On the MariaDB(DBaaS) List page, click the resource to promote to Master. 3. MariaDB(DBaaS) Details Go to the page.
- Click the More button and then click the Master Promotion button. 4. Master Promotion Notification The popup window opens.
- Master Promotion Notification in the popup window, click the Confirm button.
3.2.4 - MariaDB(DBaaS) Server Connection
Scenario Overview
MariaDB(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 MariaDB(DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish network connectivity 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 set up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and a Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Scenario components
You can build the scenario using the following services.
| service group | service | Detailed description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that lets users segment the network within a VPC to match their purpose and scale. | |
| Networking | VPC > Public IP | A service that reserves a public IP and allocates and deallocates it to Compute resources. | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the Internet | |
| Networking | Security Group | Virtual firewall that controls server traffic | |
| Database | MariaDB(DBaaS) | A service that easily creates and manages MariaDB in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- Since the default policy of a Security Group is Deny All, you must register only the IPs that are allowed.
- In/Outbound’s All Open(Any IP, Any Port) policy can expose cloud resources directly to external threats.
- By specifying the required IP and port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the steps below.
Configure Network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
1-1. Create VPC
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- Click the Create VPC button on the Service Home page. You will be taken to the Create VPC page.
- On the VPC creation page, enter the information required to create the service.
- Enter the IP range as
192.168.x.0/16.
- Enter the IP range as
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resources on the VPC List page.
1-2. Create Subnet
- Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
- Click the Create Subnet button. You will be taken to the Create Subnet page.
- On the Subnet Creation page, enter the information required to create the service.
- Select the Subnet type as General.
- Select a pre‑created VPC.
- Enter the IP range as
192.168.x.0/24.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resources on the Subnet list page.
1-3. Create Internet Gateway
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
- Click the Create Internet Gateway button. Navigate to the Create Internet Gateway page.
- On the Internet Gateway Creation page, enter the required information needed to create the service.
- Select a pre‑created VPC.
- In the Firewall usage item, select Use.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, verify the created resource on the Internet Gateway List page.
1-4. Create Public IP
- Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
- Click the Public IP menu on the Service Home page. You will be taken to the Public IP List page.
- Click the Public IP reservation button. You will be taken to the Public IP reservation page.
- Public IP reservation page, enter the required information needed to reserve the service.
- In the Summary panel, verify the detailed information and estimated billing amount, and click the Complete button.
- After creation is complete, check the created resources on the Public IP List page.
1-5. Create Security Group
- Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
- Click the Create Security Group button on the Service Home page. You will be taken to the Create Security Group page.
- On the Security Group creation page, enter the required information needed to create the service.
- Check the input information and click the Complete button.
- Once creation is complete, check the created resources on the Security Group List page.
Create bastion host
Describes the process of configuring a Bastion Host where the Database access client must be installed.
2-1. Create Server Keypair
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
- Click the Create Keypair button. You will be taken to the Create Keypair page.
- Enter the required information needed to create a service on the Keypair creation page.
- Check the creation information and click the Complete button.
- The key can be downloaded only once, and reissuance is not available.
- Please store the downloaded key in a secure location.
2-2. Create Bastion host
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Virtual Server Creation button. You will be taken to the Virtual Server Creation page.
- On the Virtual Server Creation page, enter the required information to create the service.
- Select Windows for the image.
- Select the pre‑created VPC and Subnet.
- Click Use NAT, and select the Public IP you reserved from 1-4. Create Public IP.
- Connect the Keypair created in 2-1. 서버 Keypair 생성하기.
- In the Summary panel, verify the detailed information and estimated billing amount, then click the Complete button.
- When creation is complete, check the created resources on the Virtual Server List page.
2-3. Verify Bastion host login ID and password
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
- On the Virtual Serve List page, click the resource you created in [2-2. Bastion host Creation]. You will be taken to the detailed information page for that resource.
- On the detail information page, click the RDP password view button in the Keypair name field. The RDP password view popup window will open.
- In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
- After attaching, click the Password Check button. The ID and Password required to access the resource are displayed.
- The ID and password will be used later as credentials to connect to the Bastion host in 5-1. Bastion host Connecting.
Create Database
Describes the process of creating a Database service.
3-1. MariaDB(DBaaS) Create Service
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the Create MariaDB (DBaaS) button. You will be taken to the Create MariaDB (DBaaS) page.
- MariaDB(DBaaS) Creation page: enter the required information for service creation.
- Connect by selecting the pre‑created VPC and Subnet.
- Enter the database-related creation details on the required information input screen.
- Add the Bastion host IP in the IP access control settings.
- The Database Port defaults to 2866, but the user can also specify it.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resource on the MariaDB(DBaaS) list page.
Configuring Rules
It describes the process of configuring rules for users to access the Bastion host and rules for accessing the Database from the Bastion host.
4-1. Add security rules to Security Group
- Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
- Click the Security Group menu on the Service Home page. You will be taken to the Security Group List page.
- Select the Security Group resource created in 1-5. Creating a Security Group. Navigate to the detailed information page for that resource.
- Click the Rules tab on the detail information page. You will be taken to the Rules tab.
- Click the Add Rule button on the Rules tab. It navigates to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
direction Remote Target address Protocol Port Explanation Inbound CIDR User PC IP TCP 3389 (RDP) Bastion access PC → Bastion host Outbound CIDR DB IP TCP Database Port (manual entry) Bastion host → Database Table: Security Group rules that need to be added
4-2. Adding IGW Firewall Rules
- Click the All Services > Networking > Firewall menu. Navigate to the Service Home page of Firewall.
- On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
- On the Firewall List page, select the Internet Gateway Resource Name created in 1-3. Internet Gateway 생성하기. You will be taken to the detailed information page for that resource.
- Click the Rules tab on the detail information page. You will be taken to the Rules tab.
- Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
origin address Destination address Protocol Port Operation direction Explanation Bastion connection PC IP Bastion host IP TCP 3389(RDP) Allow Inbound User PC → Bastion host Table. Internet Gateway Firewall rules that need to be added
Connect to Database
Describes the process of a user accessing the database via a DB client program.
This guide explains how to connect using MySQL Workbench. Since there are various database client programs and CLI utilities, you may install and use the tool that best fits your needs.
5-1. Connecting to Bastion host
- In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
- When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password verified in 2-3. Bastion host Access ID and PW Verification and click the Confirm button.
5-2. Install DB connection client program (MySQL Workbench) on the Bastion host
- Visit the official MySQL page and download the MySQL Workbench program.
- MySQL Workbench program download path: https://dev.mysql.com/downloads/workbench
- Connect the user’s PC hard drive to upload the file to the Bastion host.
- In the Local Resources tab of the Remote Desktop Connection, click the Details button of the Local Devices and Resources item.
- Select the local disk of the location where the file was downloaded on the drive, and click the OK button.
- Copy the downloaded file, upload it to the Bastion Host, and click the MySQL Workbench installer to install.
5-3. Connect to the Database using the DB client program (MySQL Workbench)
- Launch MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup appears.
- In the Manage Server Connection popup, click the New button at the lower left, enter the Database server information created in 3-1. MariaDB(DBaaS) 서비스 생성하기, and click the Test Connection button. A Password popup will appear.
Required input field input value Connection Name Custom (e.g., service name) Host name Database server IP Port Database Port Username Database username Table. DB connection client program input fields - In the Password popup window, enter the password you set in 3-1. MariaDB(DBaaS) Service Creation and click the OK button. When the operation succeeds, click the OK button in the Manage Server Connection popup window.
- Click Database > Connect to Database. The Connect to Database popup window appears.
- Select the Connection Name registered in Stored Connection to connect to the Database. After connecting, you can try simple queries, etc.
3.3 - API Reference
3.4 - CLI Reference
3.5 - Release Note
MariaDB(DBaaS)
- You can set up a disaster-recovery Replica using the Replica configuration (Other Region) feature.
- Strengthen the latest security patches and stability through the OS(Kernel) upgrade feature.
- You can monitor metrics and logs by integrating with Servicewatch.
- Add MariaDB (DBaaS) feature
- Add Second-Generation Server Type
- Add a second‑generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) processor. For more details, see MariaDB(DBaaS) Server Type.
- DB user and access control management and Archive configuration feature added
- For detailed information, refer to DB User Management, DB Access Control Management, Archive Management.
- DB Audit Log Export feature added
- For detailed information, refer to DB Log Export.
- Backup Notification Feature provided
- Provides notification functionality for backup success and failure. For more details, see Create Notification Policy.
- Add Migration feature
- Provides replication-based zero-downtime data migration functionality. For more details, see Migration Configuration.
- Add HDD, HDD_KMS types to Block Storage
- Add Second-Generation Server Type
- MariaDB (DBaaS) feature change
- Add second-generation server type
- Added a 2nd‑generation (dbh2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, see MariaDB(DBaaS) Server Type.
- After the service is created, you can expand the configured Block Storage capacity.
- Server-specific network IP configuration feature added allows either common or server-specific configuration depending on the usage purpose.
- Add second-generation server type
- Samsung Cloud Platform Common Feature Changes
- Account, IAM, Service Home, tags, and other common CX changes have been reflected.
- A volume-encrypted storage selection option has been added to the Block Storage type.
- A function to switch the Role (Active ↔ Standby) for the Active DB and Standby DB configured with redundancy has been added.
- It is linked with the cloud monitoring service, enabling performance and log monitoring of DB instances.
- Depending on the server type selected by the customer, Planned Compute policy can be set.
- A MariaDB (DBaaS) service that enables easy creation and management of MariaDB in a web environment has been launched.
4 - MySQL(DBaaS)
4.1 - Overview
Service Overview
MySQL(DBaaS) is an open-source relational database management system (RDBMS). Samsung Cloud Platform provides an environment that can automate MySQL installation and perform management functions for operation through a web-based Console.
MySQL (DBaaS) is designed as a high‑availability architecture that performs storage‑based data replication and minimizes failover time. To prevent data loss, when the contents of the Active server change, they are synchronously replicated to the Standby server, and the read‑only server called Replica, used for read load balancing and disaster recovery (DR), is provided up to five instances. Additionally, it provides an automatic backup feature at user-specified times to prepare for issues with the DB server or data, enabling recovery of data at the desired point in time.
Provided Features
MySQL(DBaaS) provides the following features.
- Auto Provisioning (Auto Provisioning): Allows installation and configuration of Database(DB) via UI, and provides an Active-standby redundancy configuration based on storage replication. * When the active server fails, it automatically fails over to standby.
- Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, you can restart if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, the user can manually perform node switching between Active and Standby via a switch‑over.
- Backup and Recovery: Provides data backup functionality based on its own backup commands. * The backup schedule and retention policy can be set by the user, and additional fees apply based on the backup size. * It also provides a recovery function for backed‑up data, so when the user performs a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user (the backup save point or a user‑specified point). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour earlier, based on the stored backup and archive files.
- Version Management: Provides a version upgrade (Minor) feature based on certain feature enhancements and security patches. * Whether to perform a backup for a version upgrade can be selected by the user, and if a backup is performed, the data is backed up before applying the patch, after which the DB engine is updated.
- Replica configuration: Up to five Read Replicas can be configured in the same or different regions for read load balancing and disaster recovery (DR).
- Parameter management: Performance improvements and security-related DB configuration parameters can be modified.
- Service Status Query: Retrieves the current DB service’s final status.
- Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
- DB User Management: Query and manage the DB account (user) information registered in the DB.
- DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
- Archive Management: You can set the retention period (1~35 days) for Archive files on the DB server and configure the Archive mode (On/Off).
- Export DB Log: You can export stored logs to the user’s Object Storage through Audit settings.
- Migration: Synchronize data in real time with the live database and support migration using replication without service interruption.
- OS Kernel Upgrade: The OS kernel can be upgraded to apply certain feature improvements and security patches.
Component
MySQL(DBaaS) provides pre‑validated engine versions and a variety of server types in accordance with the open‑source support policy. Users can select and use it based on the scale of the service they wish to configure.
Engine version
The engine versions supported by MySQL (DBaaS) are as follows.
Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
- MySQL (Community): https://www.mysql.com/support/eol-notice.html
| service | Provided version | EOS Date (Samsung Cloud Platform new creation stop date) | EoTS Date (Community Technical Support End Date) |
|---|---|---|---|
| MySQL (Community) | 8.0.28 | 2026-03-19 | 2026-04-30 |
| 8.0.30 | 2026-03-19 | 2026-04-30 | |
| 8.0.32 | 2026-03-19 | 2026-04-30 | |
| 8.0.33 | 2026-03-19 | 2026-04-30 | |
| 8.0.34 | 2026-03-19 | 2026-04-30 | |
| 8.0.35 | 2026-03-19 | 2026-04-30 | |
| 8.0.36 | 2026-03-19 | 2026-04-30 | |
| 8.0.37 | 2026-03-19 | 2026-04-30 | |
| 8.0.41 | 2026-03-19 | 2026-04-30 | |
| 8.0.42 | 2026-03-19 | 2026-04-30 | |
| 8.4.5 | 2031-12 (planned) | 2032-04-30 |
The next version of MySQL is scheduled to be released after July 2026. The actual service delivery schedule is subject to change.
- MySQL 8.4.7
Server type
The server types supported by MySQL (DBaaS) are as follows.
For detailed information about the server types provided by MySQL(DBaaS), see MySQL(DBaaS) 서버 타입.
Standard db1v2m4
| Category | Example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server types
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
Preceding Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
4.1.1 - Server Types
MySQL (DBaaS) server type
MySQL(DBaaS) offers server types composed of various combinations of CPU, Memory, and Network Bandwidth. When creating a MySQL(DBaaS), the Database Engine is installed based on the server type selected for the intended use.
The server types supported by MySQL (DBaaS) are as follows.
Standard db1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classifications
|
| Server specifications | db1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
db1 server type
The db1 server type of MySQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db1v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
db2 server type
The db2 server type of MySQL (DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db2v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db2v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db2v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db2v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db2v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db2v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db2v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db2v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db2v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db2v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db2v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db2v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db2v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db2v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db2v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db2v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db2v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db2v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db2v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db2v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db2v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db2v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
dbh2 server type
The dbh2 server type of MySQL (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 128 vCPUs and 1,536 GB of memory
- Networking speed up to 25 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Maximum 25 Gbps |
4.1.2 - Monitoring metrics
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service, which was released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
- New Resources: Resources created after the service improvement work in March 2026 are monitored by default using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide monitoring in parallel using the Cloud Monitoring service and the ServiceWatch service.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e. You need to verify the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete the process.
Cloud Monitoring Service Phased Termination Schedule Notice
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch: see the ServiceWatch 개요.
MySQL(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics for MySQL (DBaaS) that can be viewed through Cloud Monitoring. For detailed Cloud Monitoring usage, refer to the Cloud Monitoring guide.
For MySQL (DBaaS) server monitoring metrics, please refer to the Virtual Server Monitoring Metrics guide.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Sessions | Number of Active Sessions | cnt |
| Binary Log Used [MB] | binary log usage | MB |
| Connection Usage [Total] | DB connection session usage | % |
| Connections | Number of connections | cnt |
| Connections [MAX] | Connection count | cnt |
| Connections | max connected threads count | cnt |
| Data Directory Used [MB] | data directory usage | MB |
| Instance Status [PID] | mysqld process pid | pid |
| Open Files | Number of open DB files | cnt |
| Open Files [MAX] | Number of DB files that can be opened | cnt |
| Open Files Usage | DB file maximum count usage rate | % |
| Relay Log Used [MB] | relay log usage (MB) | MB |
| Running Threads | running thread count | cnt |
| Safe PID | safe program pid | pid |
| Slave Behind Master seconds | Time difference with the master node | sec |
| Slowqueries | Number of SQL queries running for a long time (over 5 minutes) (by DB) | cnt |
| Slowqueries [Total] | Number of long-running (over 5 minutes) SQL queries (total) | cnt |
| Tablespace Used | Tablespace usage | MB |
| Tablespace Used [Total] | Total tablespace usage | MB |
| Transaction Time [Long] | Maximum transaction execution time | sec |
| Wait Locks | Number of sessions blocked for more than 60 seconds by lock | cnt |
4.1.3 - ServiceWatch Metrics
MySQL sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1‑minute interval.
Basic Metrics
The following are the basic metrics for the namespace MySQL(DBaaS).
The indicators whose names are displayed in bold below are the key indicators selected from the basic metrics provided by MySQL(DBaaS). Key metrics are used to build service dashboards that are automatically created for each service in ServiceWatch.
Each metric guides users via the user guide on which statistical values are meaningful when viewing that metric, and among the meaningful statistics, the values displayed in bold are the primary statistics. In the service dashboard, you can view key metrics using the primary statistical values.
OS Basic Metrics
Category | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| CPU | CPU Usage | Percent | CPU usage |
|
| Disk | Disk Usage | Percent | Disk usage |
|
| Disk | Disk Write Bytes | Bytes/Second | Write throughput (bytes/second) on block device |
|
| Disk | Disk Read Bytes | Bytes/Second | Read capacity (bytes/second) from block device |
|
| Disk | Disk Write Requests | Count/Second | Number of write requests on block device (requests per second) |
|
| Disk | Disk Read Requests | Count/Second | Number of read requests on block device (requests per second) |
|
| Disk | Average Disk I/O Queue Size | None | Average queue length of requests issued to the block device |
|
| Disk | Disk I/O Utilization | Percent | The proportion of time the block device actually spent handling I/O operations |
|
| Memory | Memory Usage | Percent | Memory usage |
|
| Network | Network In Bytes | Bytes/Second | Received data rate (bytes/second) on the network interface |
|
| Network | Network Out Bytes | Bytes/Second | Transmitted capacity (bytes/second) on the network interface |
|
| Network | TCP Connections | Count/Second | Current total number of successfully established TCP connections |
|
| Network | Network In Packets | Count | Number of packets received on the network interface |
|
| Network | Network Out Packets | Count | Number of packets transmitted on the network interface |
|
| Network | Network In Dropped | Count | Number of packet drops received on the network interface |
|
| Network | Network Out Dropped | Count | Number of packet drops transmitted from the network interface |
|
| Network | Network In Errors | Count | Number of packet errors received on the network interface |
|
| Network | Network Out Errors | Count | Number of packet errors transmitted on the network interface |
|
MySQL Basic Metrics
Classification | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| Activelock | Active locks | Count | Number of transactions in lock wait (Lock Wait) state for 1 minute (60 seconds) or longer in the InnoDB storage engine |
|
| Activesession | Active sessions | Count | Number of active sessions |
|
| Activesession | Connection usage | Percent | Database connection session utilization |
|
| Activesession | Connections | Count | DB connection session |
|
| Datafile | Current open files | Count | Number of file descriptors opened by the DB |
|
| Datafile | Max open files | Count | Maximum number of file descriptors the DB can open |
|
| Datafile | Open files usage | Percent | DB file maximum count utilization |
|
| InnoDB | InnoDB buffer pool hit ratio | Percent | The proportion of data read directly from memory without accessing the disk |
|
| InnoDB | Innodb row lock wait transactions | Count | Current number of InnoDB transactions waiting for a row lock |
|
| InnoDB | InnoDB row lock time | Milliseconds | Total time waited due to InnoDB row locks (in milliseconds) |
|
| InnoDB | InnoDB deadlocks | Count/Minute | Number of deadlock occurrences |
|
| InnoDB | Table lock waits | Count/Minute | Number of waits that occurred to acquire a table lock |
|
| InnoDB | Temp disk tables | Count | Number of Temp Tables created on disk |
|
| InnoDB | Innodb log waits | Count | Number of times waited to write the redo log to disk |
|
| State | Instance state | None | Check MySQL DB Process status up/down
| - |
| State | Slave behind master seconds(8.0) (Replica Only) | Seconds | Replica latency (unit: seconds) |
|
| State | Slave io thread running(8.0) (Replica Only) | None | I/O Thread status
| - |
| State | Slave SQL thread running(8.0) (Replica Only) | None | SQL Thread status
| - |
| State | Replica behind master seconds(8.4+) (Replica Only) | Seconds | Replica latency (unit: seconds) |
|
| State | Replica io thread running(8.4+) (Replica Only) | None | I/O Thread status
| - |
| State | Replica SQL thread running(8.4+) (Replica Only) | None | SQL Thread status
| - |
| Tablespace | Tablespace used | Megabytes | Tablespace usage |
|
| Tablespace | Tablespace used(TOTAL) | Megabytes | Tablespace usage (total) |
|
| Transactions | Slow queries | Count | Number of queries that run for more than 10 seconds |
|
| Transactions | Long transaction time | Seconds | Long Transaction time |
|
| Transactions | Wait locks | Count | Number of sessions waiting for lock |
|
| Transactions | SQL Queries/Minute | Count/Minute | Queries executed per minute |
|
4.2 - How-to guides
Users can create the service by entering the required information for MySQL (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service per Resource
- New Resources: Resources created after the service improvement work in March 2026 are monitored by default using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, you must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e.g. You must review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Notice of the phased termination schedule for Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
Create MySQL (DBaaS)
You can create and use a MySQL (DBaaS) service from the Samsung Cloud Platform Console.
- Before creating the service, configure the VPC’s subnet type as General.
- If the subnet type is Local, the corresponding Database service cannot be created.
- When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to a statistical collection environment.
To create a MySQL (DBaaS), follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the Create MySQL(DBaaS) button. 2. Go to the MySQL(DBaaS) Creation page.
- MySQL (DBaaS) Creation page: enter the information required to create the service and select detailed options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version Essential Provide a list of MySQL (DBaaS) versions Table. MySQL (DBaaS) Image and version selection options - In the Service Information Input area, enter or select the required information.
Category required statusDetailed description Server name Prefix Required The server name where the DB will be installed - starts with a lowercase English letter and uses lowercase letters, numbers, and the special character (
-) to enter 3 to 13 characters
- A postfix such as 001, 002 is appended based on the server name, creating the actual server name
Cluster name Essential Cluster name of DB servers - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for DB installation - Standard: standard specifications commonly used
- High Capacity: large‑capacity server with 24 vCores or more
- For detailed information about the server types provided by MySQL (DBaaS), refer to MySQL(DBaaS) 서버 타입
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service request page
- For more details, see Planned Compute Apply
Service Type > Block Storage Required Block Storage configuration used by the DB according to its purpose - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
- SSD: High‑performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes that use Samsung Cloud Platform KMS (Key Management System) encryption keys
- The configured storage type is applied identically to additional storage
- Capacity must be entered as a multiple of 8 within the range 16 to 5,120
- Since executing SQL or monthly batch jobs can cause large sorts that may interrupt service, a separate TEMP storage must be allocated and used
- Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
- Add: Storage areas for DATA, Archive, TEMP, Backup data
- After selecting Use, enter the storage’s purpose and capacity
- The storage type is applied the same as the type set for DATA, and capacity can be entered as a multiple of 8 within the range 16 to 5,120
- To add storage, click the Add button; to delete, click the x button. Up to 9 can be added.
- Temporarily store backup data in BACKUP storage before transmitting it
- If the data to be backed up exceeds 100 GB and undergoes frequent changes, it is recommended to add a separate BACKUP storage for reliable backup. Set the backup capacity to about 60 % of the DATA capacity.
- If a BACKUP storage is not added, the
/tmparea is used, and backup will fail if capacity is insufficient
- For each service, only one Block Storage is allocated for Archive, TEMP, and BACKUP
Redundant configuration Select Redundancy configuration - When redundancy is used, the DB instance is configured as separate Active DB and Standby DB
Network > Common Settings Required Network settings for servers created by the service - Select when you want to apply the same settings to all installed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be auto‑generated
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use is checked, you can select from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select from reserved IPs in the VPC product’s Public IP. For more information, see Public IP 생성하기
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of week, start time, and duration
- It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruption
- If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.
Table. MySQL (DBaaS) Service Configuration Items - starts with a lowercase English letter and uses lowercase letters, numbers, and the special character (
- Enter required database configuration information In this section, enter or select the required information.
Category Required statusDetailed description Database name Required Server name applied during DB installation - must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
Database username Required Database user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Restricted database user names can be viewed in the Console
Database password required Password to use when accessing the DB - Enter 8 to 30 characters, including letters, numbers, and special characters (excluding
“‘)
Database password verification Required Re-enter the same password to use for DB access Database Port number Essential Port number required for DB connection - Enter DB port within the range 1200 ~ 65535
Backup > Use Select Backup usage - Use to select and set backup file retention period, backup start time, and Archive backup interval
Backup > Retention period Select Backup retention period - Select the backup retention period. Set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Period Select Backup start time - Select backup start time
- The minutes during which the backup runs (minutes) are set randomly, and the backup end time cannot be set
Backup > Archive backup cycle Selection Archive backup frequency - Select the archive backup frequency
- The archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Parameter Required Parameters to be used in the DB - Click the View button to view the parameter’s detailed information
- Parameters can be modified after the DB creation is complete, and after modification the DB must be restarted
DB character set Required Character encoding to use for the database Table case sensitivity Select DB Table case sensitivity time zone Required Standard time zone for the database ServiceWatch log collection Selection Whether to collect ServiceWatch logs - Select Use to enable the ServiceWatch log collection feature
- For details about the collected logs, see ServiceWatch metrics
- Up to 5 GB is provided free of charge for all services within the account, and charges apply based on storage size for usage exceeding 5 GB
- When collecting, log groups and log streams are created automatically, and they cannot be deleted until the resource is removed
- To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
Table. MySQL (DBaaS) Database configuration items - Additional Information Input area, please enter or select the required information.
Category required statusDetailed description Tag Select Add Tag - Up to 50 per resource can be added
- After clicking the Add Tag button, enter or select Key, Value values
Table. MySQL (DBaaS) additional information input fields
- Select the required information in the Image and version selection area.
- Check the detailed information and estimated billing amount generated in the Summary panel, and click the Create button.
- When creation is complete, check the created resources on the Resource List page.
View MySQL (DBaaS) detailed information
The MySQL (DBaaS) service allows you to view and edit the full list of resources and detailed information. MySQL(DBaaS) Details page consists of Details, Tags, Operation History tabs, and when the DB has a Replica configured, a Replica Information tab is added.
To view detailed information about the MySQL (DBaaS) service, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
- On the MySQL(DBaaS) List page, click the resource to view detailed information. 3. MySQL(DBaaS) Details Go to the page.
- MySQL(DBaaS) Details At the top of the page, status information and additional feature details are displayed.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Cluster is being created
- Editing: Cluster is transitioning to an operational state
- Error: Cluster encountered a failure while performing a task
- If this persists, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Cluster is being restarted
- Running: Cluster is operating normally
- Starting: Cluster is starting
- Stopped: Cluster is stopped
- Stopping: Cluster is being stopped
- Synchronizing: Cluster is synchronizing
- Terminating: Cluster is being terminated
- Unknown: Cluster status is unknown
- If this persists, contact the administrator
- Upgrading: Cluster is being upgraded
Cluster control Buttons to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to active
More features Cluster management buttons - Service status synchronization: Real-time DB service status lookup
- Backup history: When backup is configured, verify whether backups run correctly and view the history
- Database recovery: Recover the DB based on a specific point in time
- Parameter management: View and modify DB configuration parameters
- Replica configuration: Set up a read‑only Replica cluster
- Replica configuration (Other-Region): Set up a disaster‑recovery Replica in another region; the button is disabled if the account has no region to configure
- DB user management: View and manage DB account (user) information registered in the DB
- DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB
- Archive management: Set archive file retention periods and configure archive mode
- DB Log export: Export stored logs to the user’s Object Storage via audit settings
- Migration configuration: Provides migration functionality using replication
- OS (Kernel) upgrade: Upgrade the OS kernel version
Service termination Cancel service button Table. MySQL (DBaaS) status information and additional features
- MySQL(DBaaS) Details At the top of the page, status information and additional feature details are displayed.
Detailed information
MySQL (DBaaS) List page lets you view detailed information of the selected resource and edit the information if needed.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster type | Cluster types (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster name | Cluster name of the DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied during DB installation |
| Database username | DB user name |
| Planned Compute | Resources with Planned Compute configured
|
| maintenance period | DB Maintenance Period Status
|
| Backup | Backup configuration status
|
| ServiceWatch log collection | ServiceWatch Log Collection Configuration Status
|
| DB character set | Encoding method to be used for the DB |
| Table case sensitivity | DB Table case sensitivity |
| time zone | Standard time zone for the database |
| VIP | Virtual IP information
|
| Network | Network information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP access control | Service access policy configuration
|
| Active & Standby | Active/Standby server type, base OS, additional Disk information
|
Replica information
Replica Information tab is enabled only when a Replica is configured in the cluster. Replica information tab allows you to view the Master cluster name, replica count, and Replica status.
| Category | Detailed description |
|---|---|
| Master information | Name of the Master cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status in the Master cluster
|
tag
MySQL(DBaaS) List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Work History
MySQL(DBaaS) List page allows you to view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Managing MySQL(DBaaS) Resources
If you need to change or restore the existing configuration options of a provisioned MySQL (DBaaS) resource, or set up a replica, you can perform the tasks on the MySQL(DBaaS) Detailed Information page.
Control operation
If changes occur to a running MySQL (DBaaS) resource, you can start, stop, or restart it. Additionally, when HA is configured, you can switch the Active‑Standby servers using a switch‑over.
To control the operation of MySQL (DBaaS), follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page, click the resource to control its operation. 3. MySQL(DBaaS) Details Go to the page.
- Check the MySQL (DBaaS) status and complete the change using the control button below.
- Start: DB service is installed on the server and the DB service is running (Running).
- Stop: The server where the DB service is installed and the DB service are stopped (Stopped).
- Restart: Only the DB service will be restarted.
- Switch Over: You can switch the DB’s Active server and Standby server.
Synchronize Service Status
You can synchronize the real-time service status of MySQL (DBaaS).
To check the service status of MySQL (DBaaS), follow the steps below.
- Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- MySQL (DBaaS) List page, click the resource to view its service status. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.
Change server type
You can change the configured server type.
To change the server type, follow these steps.
- If you modify the server type, a server restart is required. * Please separately verify any software license modifications or software settings and their implementation due to specification changes.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page: click the resource for which you want to change the server type. 3. Navigate to the MySQL (DBaaS) Details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Server Type Edit After selecting the server type in the popup window, click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. For a redundant DB configuration, all redundant servers are added simultaneously.
- It is applied in the same way as the Storage type selected when creating the service.
- In a high‑availability configured database, adding storage is applied simultaneously to the storage of both the active and standby databases.
- If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. * Please expand the Replica storage first, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to add storage. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.
Expanding storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To expand storage capacity, follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- MySQL(DBaaS) List page, click the resource whose server type you want to change. 3. MySQL(DBaaS) Details Go to the page.
- Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
- Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.
Cancel MySQL (DBaaS)
You can cancel unused MySQL (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact that may occur when the service is discontinued.
- For a DB with a Replica configured, terminating the Master DB does not delete the Replica. * If you also delete the replica, please cancel it separately from the resource list.
- If you terminate the DB, all stored data and any configured backup data will be deleted.
To cancel MySQL (DBaaS), follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- On the MySQL(DBaaS) List page, select the resource to cancel and click the Cancel Service button.
- After termination is complete, check on the MySQL(DBaaS) list page whether the resource has been terminated.
4.2.1 - DB Service Manage
Users can manage MySQL (DBaaS) through the Samsung Cloud Platform Console.
Parameter Management
Provides a feature that allows easy viewing and modification of database configuration parameters.
View Parameter
To view configuration parameters, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- Click the resource you want to view or modify parameters for on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management popup window, click the Search button. The Search Notification popup window opens.
- Lookup Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
Modify Parameter
To modify the configuration parameters, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- Click the resource you want to view or modify parameters for on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management in the popup window, click the Search button. The Search Notification popup opens.
- Lookup Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
- If a modification is needed, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
- When the input is complete, click the Complete button.
If you change the character_set_server value, first verify the collation that matches the character set using the command below.
SQL> SHOW COLLATION WHERE Charset = 'character set name';
Set the parameter values for character-set-server, collation-server, and init_connect with the confirmed collation.
| Item | Detailed description | Whether to restart |
|---|---|---|
character-set-server | Specify the default character set | Restart required |
collation-server | Specify default collation (Collation) | Restart required |
init_connect | SQL statements executed when the client connects to the database | No restart required |
Managing DB Users
Provides management functions to retrieve DB user information and modify status information.
Query DB users
To retrieve DB users, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource for which you want to view DB users. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
- On the DB User Management page, click the Search button. Retrieving the data may take a moment.
Changing DB User Status
Follow these steps to change the status of the retrieved DB user.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the MySQL(DBaaS) Service Home page.
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) list page.
- On the MySQL(DBaaS) List page, click the resource for which you want to modify the DB user. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the DB User Management button. You will be directed to the DB User Management page.
- On the DB User Management page, click the Search button. The query may take a short time.
- If modification is needed, click the Edit button, and change the status field value or enter remarks.
- When the input is complete, click the Complete button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IPs that can access the database, configuring it so that only authorized IPs are allowed access.
Query DB Access Control
Follow these steps to query DB users with IP access control enabled.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page, click the resource you want to manage access control for. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a moment.
Add DB access control
To add IP access control, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Navigate to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource for which you want to add IP access control. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- DB Access Control Management page, click the Search button. Retrieving the data may take a moment.
- After the query completes, click the Add button. The Add DB Access Control popup window opens.
- Add DB Access Control In the popup window, select the DB username and enter the IP address.
- When the input is complete, click the Complete button.
Delete DB access control
To delete IP access control, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource for which you want to delete IP access control. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the View button. Retrieving the data may take a short while.
- When the query is complete, click the Delete button. The Delete popup window opens.
- In the Delete popup window, click the Confirm button.
Manage Archive
Provides the ability to configure Archive mode and set the retention period for Archive logs, allowing users to flexibly configure Archive log management policies to suit their operational environment. Additionally, it provides a feature to manually delete Archive logs, allowing you to clean up unnecessary log data and manage system resources effectively.
Configure Archive mode
To set Archive mode, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- Click the resource you want to set Archive mode for on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Detail page.
- Click the More button and click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- On the Archive Settings Management page, click the Search button. Retrieval may take a short time.
- Click the Edit button and select the usage status and retention period.
- When the edit is complete, click the Done button.
Delete Archive file
To delete the Archive file, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource for which you want to set Archive mode. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- On the Archive Settings Management page, if you want to delete all Archive files, click Delete All Archives; if you only want to delete the backed‑up Archive files, click the Delete Backed‑up Archive button.
DB Log Export
Supports exporting log data that requires long-term retention among audit logs to Object Storage. Users can directly configure the log types to be stored, the target bucket for export, and the export interval. Based on the configured criteria, logs are copied to the specified Object Storage for retention. Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for long-term storage.
- To use the DB Log export function, you need to create an Object Storage. For creating Object Storage, please refer to the Object Storage User Guide.
- Please be sure to check the expiration date and time of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
- Please ensure that authentication key information is not exposed externally.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the MySQL(DBaaS) Service Home page.
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page, click the resource you want to export the DB Log from. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the Export DB Log button. You will be taken to the Export DB Log page.
- On the DB Log Export page, click the Register button. You will be taken to the DB Log Export Register page.
- After entering the required information on the DB Log Export Registration page, click the Complete button.
Category Required Detailed descriptionLog type Required Log type to be saved Save bucket name Required Object Storage bucket name to be saved Authentication key > Access key Required Access key to access the Object Storage you want to store Authentication key > Secret key Required Secret key to access the Object Storage you want to store File creation cycle Required File creation interval in Object Storage Whether to delete the original log Selection Whether to delete the original logs when exporting to Object Storage Table. MySQL (DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource you want to manage DB Log export for. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button and then click the Export DB Log button. You will be taken to the Export DB Log page.
- On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, Cancel buttons.
- Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
- Edit: Modify the DB Log export mode setting.
- Cancel: Disables the DB Log export mode setting.
Minor Version Upgrade
We provide version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades within the same Major version are supported.
- First retrieve the service status by synchronizing it, then perform the version upgrade.
- Please perform the version upgrade after configuring a backup. If you do not set up a backup, you may be unable to recover some data if a problem occurs during the update.
- In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. Please check the Replica version first and, if necessary, perform a version upgrade.
- The backed-up data will be automatically deleted after the version upgrade is completed.
To upgrade the version, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- Click the resource to upgrade the version on the MySQL(DBaaS) List page. It navigates to the MySQL(DBaaS) Details page.
- Click the Edit button of the Image version item. The Version Upgrade popup window opens.
- Version Upgrade In the popup, select the updated version and backup setting, then click the Confirm button.
- Click the Confirm button in the Version Upgrade Notification popup.
Configure Migration
Provides a Migration feature that synchronizes in real time with the live database and replicates using a Replication method without service interruption.
To configure Migration, follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to migrate. You will be taken to the MySQL(DBaaS) Detail page.
- Click the More button and then click the Migration Configuration button. The Migration Configuration popup window opens.
- In the popup window, review the instructions and click the Confirm button. You will be taken to the Migration configuration page.
- On the Migration configuration page, after entering the required information, click the Check connection button.
- When the connection is complete, click the Complete button.
Category Required Detailed descriptionSource DB Database name Required Database name of the source DB to be migrated Source DB IP Required IP of the Source DB that is the migration target Source DB Port Required Port of the Source DB to be migrated Source DB username Required User name of the Source DB to be migrated Source DB password Required Password of the source DB that is the migration target Table. MySQL (DBaaS) migration configuration items
Promote Migration Cluster to Master Cluster
You can promote a configured Migration Cluster to a Master Cluster.
To promote the Migration Cluster to Master, follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to promote to Master. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the Master promotion button. The Master promotion notification popup opens.
- In the Master Promotion Notification popup, click the Confirm button.
Upgrade OS Kernel
The OS kernel can be upgraded to improve the functionality of the running database and apply security patches.
- The service will be unavailable while the OS upgrade is in progress.
- The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
- After the upgrade is complete, you cannot revert to the previous OS.
To upgrade the OS Kernel, follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to upgrade the OS Kernel. You will be taken to the MySQL(DBaaS) Details page.
- Click the More button, then click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup opens.
- OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.
4.2.2 - Backing up and restoring the database
Users can configure backups for MySQL (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Backing up MySQL (DBaaS)
PostgreSQL (DBaaS) provides data backup functionality based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.
Configure Backup
For instructions on configuring backups for MySQL(DBaaS), see MySQL(DBaaS) Creating.
To modify the backup settings of the created resource, follow the steps below.
- For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity. * Especially when the backup data exceeds 100 GB and undergoes frequent changes, please secure additional storage amounting to about 60 % of the data size. * For instructions on adding and expanding storage, please refer to the MySQL(DBaaS) Add Storage, MySQL(DBaaS) Expand Storage guides.
- If a backup is configured, it will run at the designated time after the set time, and additional fees will be incurred based on the backup size.
- If you change the backup setting to unset, backup execution stops immediately, and the stored backup data is deleted and can no longer be used.
To set up a backup, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List page, click the resource for which you want to configure backup. 3. MySQL(DBaaS) Details Go to the page.
- Click the Edit button of the backup item. 4. Backup Settings popup window opens.
- When configuring a backup, click Enable in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
- If you wish to stop the backup configuration, deselect Backup Settings in the Use popup and authenticate via the logged-in user’s mobile phone.
When user authentication is complete, the backup configuration is disabled and backup execution stops.
- If you wish to stop the backup configuration, deselect Backup Settings in the Use popup and authenticate via the logged-in user’s mobile phone.
Check backup history
To view the backup history, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL (DBaaS) List Navigate to the page.
- MySQL(DBaaS) List On the page, click the resource for which you want to view the backup history. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup files
To delete the backup history, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. Go to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List On the page, click the resource to view the backup history. 3. MySQL(DBaaS) Details Go to the page.
- Click the Backup History button. 4. Backup History popup window opens.
- Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
- When user authentication is completed, the backup file is deleted.
MySQL(DBaaS) Recover
When a failure or data loss requires restoration from a backup file, the recovery feature enables point‑in‑time restoration. When performing a MySQL (DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the DB is installed with the version from the backup point, and the recovery proceeds with the DB’s configuration information and data.
To recover MySQL (DBaaS), follow these steps.
- Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
- MySQL(DBaaS) resource On the list page, click the resource you want to restore. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Database Recovery button. 4. Go to the Database Recovery page.
- Database Recovery Configuration after entering the relevant information in the area, click the Complete button.
Category required statusDetailed description Recovery Type Required Set the point in time the user wants to recover - Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
- Custom point: Recover to a user-specified point within the range of recoverable backup times. The recoverable period depends on the Archive backup cycle setting, allowing recovery from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the desired date and time for the backup
Server name prefix Required Server name of the recovery DB - Start with a lowercase English letter and use lowercase letters, numbers, and special characters (
-) to enter 3 to 16 characters
- Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name Required Cluster name of the recovery DB - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for the recovery DB installation - Standard: Standard specification commonly used
- High Capacity: Large-capacity server with 24 vCores or more (to be provided later)
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute Apply
Service Type > Block Storage Required Block Storage settings used by the recovery DB - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Applied identically with the storage type set in the source cluster
- Enter capacity as a multiple of 8 within the range 16 to 5,120
- Additional: Storage area for DATA, Archive, TEMP, Backup data
- Applied identically with the storage type set in the source cluster
- In the recovery DB, only DATA, TEMP, and Archive purposes can be added
- After selecting Use, enter the storage purpose and capacity
- To add storage, click the Add button; to delete, click the x button
- Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created ___HTML_MARKER***
Database username Required Database username configured in the source DB Database Port number Required Database port number configured in the source DB IP access control Select IP address for accessing the recovery DB - Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.1/32,192.168.10.1/32), then click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day, start time, and duration
- It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruption
- If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
tag Select Add Tag - Add Tag button after clicking, enter or select Key, Value values
Table. MySQL (DBaaS) recovery configuration items
4.2.3 - Configure Read Replica
Users can enter the required information for a Read Replica through the Samsung Cloud Platform Console and create the service using detailed options.
Configure Replica
You can create replica servers for read‑only or disaster‑recovery purposes through replica configuration. You can create up to 5 replicas per database.
To configure a Replica, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- On the MySQL(DBaaS) List page, click the resource to configure a Replica. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Replica configuration button. 4. Go to the Replica configuration page.
- After entering information in the Replica configuration area, click the Done button.
Category required statusDetailed description Region required Region to configure the Replica - Replica configuration (Other Region) is displayed only when selected
Replica count Required Number of Replicas to configure - Up to 5 can be configured per cluster
- If you select more than one value, additionally enter the Replica name and service type information
Replica name Required Replica server name - Start with a lowercase English letter, and use lowercase letters, numbers, and special characters (
-) to enter 3 to 19 characters
- The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type Required Replica server type - Standard: standard specification commonly used
- High Capacity: large-capacity server with 24 vCores or more
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Apply for Planned Compute
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of week, start time, and duration
- It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
- If set to unused, we are not responsible for issues arising from patches not being applied.
Tag Select Add Tag - Add Tag after clicking the button, enter or select Key, Value values
Table. MySQL (DBaaS) Replica configuration items
Reconfigure Replica
If a network outage or replication delay with the Master Cluster occurs, you can use the Replica reconstruction function to replicate the Master Cluster’s data again.
To reconfigure the Replica, follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- On the MySQL(DBaaS) List page, click the resource to reconfigure the Replica. 3. MySQL(DBaaS) Details Navigate to the page.
- Click the Replica reconstruction button. 4. Replica Reconfiguration Notification A popup window opens.
- Replica Reconfiguration Notification In the popup window, click the Confirm button.
Promoting a Replica Cluster to a Master Cluster
You can promote a configured Replica Cluster to a Master Cluster.
To promote a Replica Cluster to Master, follow these steps.
- Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
- MySQL(DBaaS) List On the page, click the resource to promote to Master. 3. MySQL(DBaaS) Details Go to the page.
- Click the More button and then click the Promote to Master button. 4. Master Promotion Notification The popup window opens.
- In the Master Promotion Notification popup, click the Confirm button.
4.2.4 - MySQL(DBaaS) Server Connection
Scenario Overview
MySQL(DBaaS) Server Connection scenario involves creating a Bastion host (Virtual Server) and a Database service, and accessing the DB service through the Bastion host. To reliably connect to MySQL (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, it is recommended to configure the Database service in a Private Subnet environment and place the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and a Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Scenario components
You can build the scenario using the following services.
| Service group | service | Detailed description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that lets users subdivide the network within a VPC to match their purpose and scale. | |
| Networking | VPC > Public IP | A service that reserves a public IP and allocates and releases it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the Internet | |
| Networking | Security Group | Virtual firewall that controls server traffic | |
| Database | MySQL(DBaaS) | A service that easily creates and manages MySQL in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- Since the default policy of a Security Group is Deny All, you must register only the allowed IPs.
- The All Open (Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
- By specifying the required IP and port and setting a policy, you can strengthen security.
Scenario configuration method
Create the services needed to build the scenario by following the steps below.
Set up the network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
1-1. Create VPC
- Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
- Click the VPC Creation button on the Service Home page. You will be taken to the VPC Creation page.
- On the VPC Creation page, enter the information required to create the service.
- Enter the IP range as
192.168.x.0/16.
- Enter the IP range as
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resources on the VPC List page.
1-2. Create Subnet
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
- Click the Create Subnet button. You will be taken to the Create Subnet page.
- On the Subnet Creation page, enter the information required to create the service.
- Select the Subnet type as General.
- Select a pre‑created VPC.
- Enter the IP range as
192.168.x.0/24.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, verify the created resources on the Subnet list page.
1-3. Create Internet Gateway
- Click the All Services > Networking > VPC menu. Go to the VPC’s Service Home page.
- On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
- Click the Create Internet Gateway button. You will be taken to the Create Internet Gateway page.
- On the Internet Gateway Creation page, enter the required information to create the service.
- Select a pre‑created VPC.
- In the Firewall usage option, select Use.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resource on the Internet Gateway List page.
1-4. Create Public IP
- Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Public IP menu. You will be taken to the Public IP List page.
- Click the Public IP Reservation button. You will be taken to the Public IP Reservation page.
- On the Public IP reservation page, enter the required information to reserve the service.
- In the Summary panel, verify the detailed information and estimated billing amount you generated, and click the Complete button.
- When creation is complete, check the created resources on the Public IP List page.
1-5. Create Security Group
- Click the All Services > Networking > Security Group menu. You will be taken to the Service Home page of the Security Group.
- Click the Create Security Group button on the Service Home page. You will be taken to the Create Security Group page.
- On the Security Group creation page, enter the required information for creating the service.
- Check the input information and click the Complete button.
- When creation is complete, verify the created resource on the Security Group List page.
Create Bastion host
This explains the process of configuring a Bastion Host where the Database access client must be installed.
2-1. Create Server Keypair
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
- Click the Create Keypair button. You will be taken to the Create Keypair page.
- Enter the required information needed to create a service on the Keypair creation page.
- Check the creation information and click the Complete button.
- The key can be downloaded only on the first attempt, and reissuance is not available.
- Please store the downloaded key in a secure location.
2-2. Create Bastion host
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Create Virtual Server button. You will be taken to the Create Virtual Server page.
- On the Virtual Server Creation page, enter the required information to create the service.
- Select Windows for the image.
- Select the pre-created VPC and Subnet.
- Click Use NAT, then select the reserved Public IP from 1-4. Create Public IP.
- Connect the Keypair created in 2-1. 서버 Keypair 생성하기.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resources on the Virtual Server List page.
2-3. Bastion host Check login ID and PW
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
- On the Virtual Serve List page, click the resource you created in [2-2. Bastion host creation]. You will be taken to the detailed information page of that resource.
- On the detail page, click the RDP password view button in the Keypair name field. The RDP password view popup will open.
- In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
- After attaching, click the Password Check button. The ID and Password for accessing the resource are displayed.
- The ID and password will later be used as credentials to access the Bastion host in 5-1. Bastion host Connecting.
Create Database
Explains the process of creating a Database service.
3-1. Create MySQL(DBaaS) Service
- Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) Create button. You will be taken to the MySQL(DBaaS) Create page.
- On the MySQL(DBaaS) Creation page, enter the required information needed to create the service.
- Select the pre‑created VPC and Subnet and connect them.
- Enter the database-related creation details on the required information input screen.
- Add the Bastion host IP in the IP access control settings.
- The Database Port defaults to 2866, but the user can also specify it.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resource on the MySQL(DBaaS) list page.
Configure Rules
It explains the process of configuring rules for a user to connect to the Bastion host and rules for connecting to the Database from the Bastion host.
4-1. Adding security rules to Security Group
- Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
- Click the Security Group menu on the Service Home page. You will be taken to the Security Group List page.
- Select the Security Group resource created in 1-5. Create Security Group. Navigate to the detailed information page for that resource.
- Click the Rules tab on the detail page. You will be taken to the Rules tab.
- On the Rules tab, click the Add Rule button. The Add Rule popup will appear.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
direction remote Target address Protocol Port Explanation Inbound CIDR User PC IP TCP 3389 (RDP) Bastion client PC → Bastion host Outbound CIDR DB IP TCP Database Port (manual entry) Bastion host → Database Table. Security Group rules that need to be added
4-2. Adding IGW Firewall Rule
- All Services > Networking > Firewall Click the menu. Go to the Service Home page of the Firewall.
- On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
- On the Firewall List page, select the Internet Gateway resource name created in 1-3. Create Internet Gateway. You will be taken to the detailed information page of that resource.
- Click the Rules tab on the detail page. You will be taken to the Rules tab.
- Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
origin address Destination address Protocol Port operation direction Explanation Bastion connection PC IP Bastion host IP TCP 3389(RDP) Allow Inbound User PC → Bastion host Table. Internet Gateway Firewall rules that should be added
Connect to Database
Describes the process of a user accessing the database via a DB client program.
This guide explains how to connect using MySQL Workbench. Since there are various database client programs and CLI utilities, you may install and use the tool that best fits your needs.
5-1. Connecting to Bastion host
- In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
- When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password verified in 2-3. Check the Bastion host access ID and PW and click the Confirm button.
5-2. Install DB access client program (MySQL Workbench) on the Bastion host
- Visit the official MySQL page and download the MySQL Workbench program.
- MySQL Workbench program download URL: https://dev.mysql.com/downloads/workbench
- Connect the user’s PC hard drive to upload the file to the Bastion host.
- In the Local Resources tab of the Remote Desktop Connection, click the Details button of the Local Devices and Resources item.
- Select the local disk where the file was downloaded on the drive, and click the OK button.
- Copy the downloaded file, upload it to the Bastion Host, and click the MySQL Workbench installer to install.
5-3. Connect to the Database using the DB client program (MySQL Workbench)
- Launch MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup appears.
- Manage Server Connection In the popup window, click the New button at the lower left, enter the Database server information created in 3-1. MySQL(DBaaS) 서비스 생성하기, and click the Test Connection button. A Password popup will appear.
Required input field input value Connection Name Custom (ex. service name) Host name Database server IP Port Database Port Username Database username Table.DB connection client program input fields - In the Password popup, enter the password you set in 3-1. MySQL(DBaaS) Create Service and click the OK button. When the operation completes successfully, click the OK button in the Manage Server Connection popup.
- Click Database > Connect to Database. The Connect to Database popup appears.
- Select the Connection Name registered in Stored Connection to perform a Database connection. After connecting, you can try simple Query, etc.
4.3 - API Reference
4.4 - CLI Reference
4.5 - Release Note
MySQL(DBaaS)
- You can set up a disaster-recovery Replica using the Replica configuration (Other Region) feature.
- Strengthen the latest security patches and stability through the OS (Kernel) upgrade feature.
- You can monitor metrics and logs by integrating with Servicewatch.
- Add MySQL (DBaaS) feature
- Add Second-Generation Server Type
- Add a 2nd‑generation (db2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, refer to MySQL(DBaaS) 서버 타입.
- DB user and access control management and Archive configuration feature added
- For detailed information, see DB User Management, DB Access Control Management, Archive Management
- DB Audit Log Export feature added
- For more details, refer to DB Log 내보내기
- Backup notification feature provided
- Provides notification functionality for backup success and failure. For more details, see Create Notification Policy.
- Add Migration feature
- Provides replication-based zero-downtime data migration functionality. For more details, see Configuring Migration.
- Block Storage type HDD, HDD_KMS type addition
- Add Second-Generation Server Type
- MySQL (DBaaS) feature change
- Add second-generation server type
- Add a 2nd‑generation (dbh2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, see mysql(DBaaS) 서버 타입.
- After the service is created, you can expand the configured Block Storage capacity.
- Server-specific network IP configuration feature added allows common or server-specific settings depending on the usage purpose.
- Add second-generation server type
- Samsung Cloud Platform common feature changes
- Account, IAM, Service Home, tags, and other common CX changes have been applied.
- A MySQL (DBaaS) service that enables easy creation and management of MariaDB in a web environment has been released.
5 - Microsoft SQL Server(DBaaS)
5.1 - Overview
Service Overview
Microsoft SQL Server (DBaaS) is a representative relational database management system (RDBMS) used in various applications. Samsung Cloud Platform provides an environment that automates Microsoft SQL Server installation and offers management functions for operation through a web-based console.
Microsoft SQL Server (DBaaS) is designed with an Always On-based availability architecture, so when the Primary server’s content changes, it is synchronously replicated to the Secondary server. 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 a desired point in time.
Provided features
Microsoft SQL Server (DBaaS) provides the following features.
- Auto Provisioning: UI allows installation and configuration of Database(DB), and provides a Primary-Secondary redundancy configuration based on Always On. When the Primary server fails, it automatically fails over to the Secondary.
- Operation Control Management: Provides functionality to control the state of running servers. In addition to start and stop, restart is possible when there is a DB issue or to apply configuration changes. When configured for high availability (HA), users can manually perform node switching between Primary and Secondary via a switch‑over.
- Backup and Recovery: Provides data backup functionality based on its own backup commands. Users can set the backup time window, retention organization, and Full backup day, and additional fees apply based on backup volume. It also offers a recovery function for backed‑up data, creating a separate DB when the user performs a recovery and restoring to the point in time selected by the user (backup save point, custom point). When restoring to a user‑specified point, the restore time 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 for certain feature improvements and security patches. Users can choose whether to perform a backup for the version upgrade, and if a backup is performed, data is backed up before applying the patch, then the DB engine is updated.
- Secondary configuration: You can add a read‑only Read Replica (Secondary Replica), which expands read performance and distributes load.
- Audit Settings: Provides an audit configuration feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
- Parameter management: Modification of DB configuration parameters related to performance improvement and security is possible.
- Service Status Query: Retrieves the latest status of the current DB service.
- Monitoring: CPU, memory, DB performance monitoring information can be viewed through the Cloud Monitoring service.
- DB User Management: View and manage DB account (user) information registered in the DB.
- Export DB Log: You can export stored logs to the user’s Object Storage through Audit settings.
Component
Microsoft SQL Server(DBaaS) provides pre-validated engine versions and various server types. Users can select and use them according to the scale of the service they wish to configure.
Engine version
The engine versions supported by Microsoft SQL Server(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 halted is set to six months before the EoTS date.
Because the supplier’s policy may cause the EOS and EoTS dates to change, please refer to the supplier’s license management policy page for details.
- Microsoft SQL Server: https://learn.microsoft.com/ko-kr/lifecycle/products/?terms=sql%20server
| Provided version | EOS Date (Samsung Cloud Platform new creation stop date) | EoTS Date (Community technical support end date) |
|---|---|---|
| Microsoft SQL Server 2019 Enterprise | 2029-06 (planned) | 2030-01-08(Extended Support) 2025-02-28(Standard Support) |
| Microsoft SQL Server 2019 Standard | 2029-06 (planned) | 2030-01-08(Extended Support) 2025-02-28(Standard Support) |
| Microsoft SQL Server 2022 Enterprise | 2032-06 (planned) | 2033-01-11(Extended Support) 2028-01-11(Standard Support) |
| Microsoft SQL Server 2022 Standard | 2032-06 (planned) | 2033-01-11(Extended Support) 2028-01-11(Standard Support) |
Server type
The server types supported by Microsoft SQL Server (DBaaS) are as follows.
For detailed information about the server types offered by Microsoft SQL Server (DBaaS), refer to Microsoft SQL Server(DBaaS) Server Types.
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. Please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
5.1.1 - Server Types
Microsoft SQL Server(DBaaS) server type
Microsoft SQL Server(DBaaS) provides server types composed of various combinations of CPU, memory, and network bandwidth. When creating a Microsoft SQL Server (DBaaS), the Database Engine is installed according to the server type selected for the intended use.
The server types supported by Microsoft SQL Server (DBaaS) are as follows.
Standard db1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classifications
|
| Server specifications | db1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
db1 server type
The db1 server type of Microsoft SQL Server(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db1v12m24 | 12 vCore | 24 GB | Maximum 12.5 Gbps |
| Standard | db1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
db2 server type
The db2 server type of Microsoft SQL Server (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db2v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db2v8m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db2v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db2v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db2v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db2v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db2v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db2v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db2v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db2v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db2v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db2v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db2v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db2v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db2v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db2v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db2v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db2v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db2v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db2v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db2v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db2v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
dbh2 server type
The dbh2 server type of Microsoft SQL Server (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 128 vCPUs and 1,536 GB of memory
- Networking speed up to 25 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Maximum 25 Gbps |
5.1.2 - Monitoring metrics
According to the policy of Samsung Cloud Platform, 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 released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
- New Resources: Resources created after the service improvement work in July 2026 are provided with monitoring using the ServiceWatch service by default.
- 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, we must prepare for the Servicewatch transition. *
Performance and log data backup, the settings configured by users linked with existing Cloud Monitoring (e. You must verify items such as event policies and perform tasks such as resetting the ServiceWatch service, then complete them.
Notice of the phased termination schedule for the Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch is available in the ServiceWatch Overview.
Microsoft SQL Server(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics for Microsoft SQL Server (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
Please refer to the Virtual Server Monitoring Metrics guide for Microsoft SQL Server(DBaaS) server monitoring metrics.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Sessions | Number of Sessions in Active state | cnt |
| Active Transactions [Total] | Number of active transactions | cnt |
| Blocking Session ID | Long-running query (slow query) | ID |
| Connected Users | Number of users connected to the system | cnt |
| Datavolume Size [Free] | Available space | bytes |
| DBFiles [Not Online] | Run a query to verify that all data files are ONLINE. | cnt |
| Instance State [Cluster] | Status during MSSQL cluster configuration | state |
| Instance State [PID] | sqlservr.exe process pid | PID |
| Lock Processes [Blocked] | Number of SQL processes blocked by other processes | cnt |
| Lock Waits [Per Second] | Lock wait count per second | cnt |
| Page IO Latch Wait Time | Page IO latch waits average wait time | ms |
| Slowqueries | Number of SQL queries running for a long time (over 5 minutes) | cnt |
| Slowquery CPU Time | CPU time spent executing SQL that runs for a long time (over 5 minutes) | ms |
| Slowquery Execute Context ID | Context ID linked to the execution task of a SQL that has been running for a long time (over 5 minutes) | ID |
| Slowquery Memory Usage | Memory usage incurred by the execution of SQL that runs for a long time (over 5 minutes) | bytes |
| Slowquery Session ID | Session ID of SQL queries running for a long time (over 5 minutes) | ID |
| Slowquery Wait Duration Time | Total wait time for wait type | ms |
| Tablespace Used | Data volume size | bytes |
| Transaction Time [MAX] | Long-running transaction | cnt |
5.2 - How-to guides
Users can create the service by entering the required information for Microsoft SQL Server (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service per Resource
- New Resources: Resources created after the service improvement work in July 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, settings configured by users linked with existing Cloud Monitoring (e.g. You must review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Notice of the phased termination schedule for Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (November 2026 service improvement work)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, Cloud Monitoring data cannot be accessed. * Be sure to complete the ServiceWatch transition work within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
Create Microsoft SQL Server (DBaaS)
You can create and use the Microsoft SQL Server (DBaaS) service from the Samsung Cloud Platform Console.
Before creating the service, configure the VPC’s subnet type as General.
- If the subnet type is Local, the corresponding Database service cannot be created.
To create a Microsoft SQL Server (DBaaS), follow the steps below.
- Click the All Services > Database > Microsoft SQL Server (DBaaS) menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) Create button. 2. Go to the Microsoft SQL Server(DBaaS) Create page.
- On the Microsoft SQL Server(DBaaS) Creation page, enter the information required to create the service and select detailed options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version Required Provide a list of Microsoft SQL Server (DBaaS) versions Table. Microsoft SQL Server (DBaaS) Image and version selection options - In the Service Information Input area, enter or select the required information.
Category required statusDetailed description Server name Prefix Required Server name where the DB will be installed - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
-) with a length of 3 to 13 characters
- A postfix such as 001, 002 is appended based on the server name to generate the actual server name
Cluster name Required Cluster name of DB servers - Enter in English using 3 to 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for DB installation - Standard: Standard specification commonly used
- High Capacity: Large-capacity server with 24 vCores or more
- For detailed information about the server types provided by Microsoft SQL Server (DBaaS), refer to Microsoft SQL Server(DBaaS) 서버 타입
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, refer to Planned Compute Apply
Service Type > Block Storage required Block Storage settings used by the DB according to 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 also applied to additional storage
- Capacity must be entered as a multiple of 8 within the range 16 to 5,120
- After selecting Use, enter the storage’s purpose and capacity
- Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
- Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Redundant configuration Select Redundancy configuration status - When redundancy configuration is used, the DB instance is set up as an Active DB and a Standby DB
Network > Common Settings Required Network settings where servers generated by the service are installed - 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 generated automatically
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
Network > Server-specific Settings Required Network settings for servers created by the service - 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 a reserved IP from the VPC product’s Public IP. For more details, see Public IP 생성하기
IP access control Selection Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of week, start time, and duration
- It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruption
- If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.
Table. Microsoft SQL Server(DBaaS) Service Configuration Items - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
- Please enter or select the required information in the Enter required database configuration information area.
Category required statusDetailed description Database service name Required Database management unit name - Starts with an uppercase English letter and uses English characters, input 1 ~ 15
Database name > default Required Server name applied during DB installation - must start with an English letter and consist of English letters, numbers, and special characters (
.,_) with a length of 3 to 20 characters
Database name > Add Required Server name applied during DB installation - After selecting use, enter the Database name to install. It must start with an English letter, and using English letters, numbers, and special characters (
.,_), enter 3 - 20 characters
- For each Database, the drive where data is stored can be selected from the drives added in Service Type > Block Storage
- Adding Databases is only possible in the Enterprise edition, and up to 100 can be added
Database username Required DB user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- The following names cannot be used as Database user names
- root, user, sdscmpif, hacluster, adm, games, nobody, sshd, system, mail, postfix, sa, maxigent_cl
Database password Required Database connection password - English letters, numbers, and special characters (
“‘excluding) including, enter 8-30 characters
Database password verification Required Check DB connection password - Re-enter the DB connection password identically
Database Port number Required DB connection port number - Enter DB port within the range 1200 - 65535
License Required SQL Server License Key - Enter the issued license key
- If the entered license key is not valid, the service may not be created
Backup > Use Select Backup usage - Select Use to set the backup file retention period, backup start time, Full backup schedule (day of week), and Archive backup interval
Backup > Retention Period Selection Backup retention period - Select the backup retention period. Set the file retention period to 7 days ~ 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Period Selection Backup start time - Select backup start time
- The minutes during which the backup runs (minutes) are set randomly, and the backup end time cannot be set
Backup > Full backup schedule (day of week) Select Full backup schedule - Select the day of the week for full backup execution
- Full backup is performed on a weekly basis
Backup > Archive backup cycle Selection Archive backup frequency - Select the archive backup frequency
- The archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Audit Log Settings Selection Audit Log storage option - Use to enable the Audit Log feature
- DDL and user connection information records are stored
- Enabling Audit may degrade DB performance
Parameter Required DB configuration parameters - Click the View button to view detailed parameter information
- Parameters can be modified after the service creation is completed, and a DB restart is required after modification
DB Collation Selection Data sorting method - A command that specifies the data sorting and comparison method, which can produce different results depending on the settings.
time zone Required Standard time zone for the database Table. Microsoft SQL Server (DBaaS) Database configuration items - Additional Information Input area, please enter or select the required information.
Category required statusDetailed description tag Select Add Tag - Up to 50 per resource can be added
- After clicking the Add Tag button, enter or select Key, Value values
Table. Microsoft SQL Server (DBaaS) additional information input fields
- Select the required information in the Image and version selection area.
- Summary Check the detailed information and estimated charges generated in the panel, and click the Create button.
- Once creation is complete, check the created resource on the Resource List page.
View detailed information of Microsoft SQL Server (DBaaS)
The Microsoft SQL Server (DBaaS) service allows you to view and edit the full resource list and detailed information. Microsoft SQL Server (DBaaS) Details page consists of Details, Tags, Activity History tabs, and when the DB has a Replica configured, a Replica Information tab is added.
To view detailed information about the Microsoft SQL Server (DBaaS) service, follow these steps.
- Click the All Services > Database > Microsoft SQL Server (DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- From the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List Click the resource to view detailed information on the page. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Microsoft SQL Server(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Cluster is being created
- Editing: Cluster is transitioning to an operational state
- Error: Cluster encountered a failure while performing a task
- If this persists, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Cluster is being restarted
- Running: Cluster is operating normally
- Starting: Cluster is starting
- Stopped: Cluster is stopped
- Stopping: Cluster is being stopped
- Synchronizing: Cluster is synchronizing
- Terminating: Cluster is being terminated
- Unknown: Cluster status is unknown
- If this persists, contact the administrator
- Upgrading: Cluster is being upgraded
Cluster control Buttons that can change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to Active
More features Cluster management buttons - Service Status Synchronization: Query real-time DB service status
- Backup History: Verify successful backup execution and view backup history when backup is configured
- Database Recovery: Recover the DB based on a specific point in time
- Parameter Management: View and modify DB configuration parameters
- Add Secondary: Configure a read‑only replica cluster
- DB User Management: View and manage DB accounts (users) registered in the DB
- Export DB Log: Export logs stored through audit settings to the user’s Object Storage
Service cancellation Service cancellation button Table. Microsoft SQL Server(DBaaS) status information and additional features
- Microsoft SQL Server(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
Detailed information
You can view the detailed information of the selected resource on the Microsoft SQL Server (DBaaS) List page and, if necessary, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster name | Cluster name of the configured servers |
| Databse service name | Database Management Unit Name |
| Database username | DB user name |
| Database name > Default Database | Server name applied during DB installation |
| Database name > Add Database | Server name applied during DB installation
|
| Planned Compute | Resource status with Planned Compute configured
|
| maintenance period | DB Maintenance Period Status
|
| Backup | Backup configuration status
|
| Audit Log Settings | Audit Log configuration status
|
| time zone | Standard time zone for the database |
| DB Collation | Data sorting method |
| VIP | Virtual IP information
|
| Network | Network information (VPC, Subnet) where the DB is installed |
| IP access control | Service access policy configuration
|
| Primary & Secondary | Primary/Secondary server type, default OS, additional Disk information
|
tag
Microsoft SQL Server (DBaaS) List You can view the tag information of the selected resource on the page, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Work History
Microsoft SQL Server(DBaaS) List page allows you to view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Managing Microsoft SQL Server (DBaaS) Resources
If you need to change the existing configuration options of a provisioned Microsoft SQL Server (DBaaS) resource, or perform recovery, parameter management, etc., you can perform the tasks on the Microsoft SQL Server(DBaaS) Details page.
Control operation
If changes occur to a running Microsoft SQL Server (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Primary-Secondary servers via a switch-over.
To control the operation of Microsoft SQL Server (DBaaS), follow the steps below.
- Click the All Services > Database > Microsoft SQL Server (DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Navigate to the Microsoft SQL Server(DBaaS) List page.
- Microsoft SQL Server(DBaaS) List On the page, click the resource to control its operation. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Check the Microsoft SQL Server(DBaaS) status and complete the change using the control button below.
- Start: the server where the DB service is installed and the DB service is running (Running).
- Stop: The server hosting the DB service and the DB service itself are stopped.
- Restart: Only the DB service will be restarted.
- Switch Over: You can switch the Primary and Secondary servers of the DB.
Synchronize service status
You can synchronize the real-time service status of Microsoft SQL Server (DBaaS).
To check the service status of Microsoft SQL Server (DBaaS), follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) menu, please click. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server(DBaaS) List Click the resource on the page to view the service status. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Service Status Synchronization button. 4. During the query, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.
Change server type
You can change the configured server type.
To change the server type, follow these steps.
- If you modify the server type, a server restart is required. * Please separately verify any software license modifications or software settings and their implementation resulting from server specification changes.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Navigate to the Microsoft SQL Server(DBaaS) List page.
- Microsoft SQL Server(DBaaS) List Click the resource on the page for which you want to change the server type. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Edit Server Type 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.
To add storage capacity, follow the steps below.
- It is applied in the same way as the Storage type selected when creating the service.
- For a high‑availability configured DB, adding storage is applied simultaneously to the storage of the Primary DB and the Secondary DB.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Navigate to the Microsoft SQL Server(DBaaS) List page.
- Microsoft SQL Server(DBaaS) List page, click the resource to add storage. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Add Disk button at the bottom of the details. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.
Expand storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In a redundant DB configuration, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List On the page, click the resource to change the server type. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
- Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.
Cancel Microsoft SQL Server (DBaaS)
You can reduce operating costs by terminating the unused Microsoft SQL Server (DBaaS). However, if you terminate the service, the running service may be stopped immediately, so you should thoroughly consider the impact of service interruption before proceeding with the termination.
To cancel Microsoft SQL Server(DBaaS), follow the steps below.
- Click the All Services > Database > Microsoft SQL Server (DBaaS) menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List on the page, select the resource to cancel, and click the Cancel Service button.
- After termination is complete, check on the Microsoft SQL Server(DBaaS) list page whether the resource has been terminated.
5.2.1 - DB Service Manage
Users can manage Microsoft SQL Server (DBaaS) through the Samsung Cloud Platform Console.
Managing the Database
For the Microsoft SQL Server Enterprise edition, you can add a new database. Up to 100 can be added per cluster.
Add Database
To add a Database, follow these steps.
- Click the All Services > Database > Microsoft SQL Server (DBaaS) menu. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource to add storage. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Click the Add button in the Database name field. The Add Database popup window opens.
- In the Add Database popup window, click the + button to enter the Database name and select a drive, then click the Confirm button.
Delete Database
To delete the database, follow these steps.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. Navigate to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource to add storage. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Click the Edit button for the Database name field. The Add Database Delete popup window opens.
- Additional Database Deletion In the request popup, check the Database you want to delete and click the Delete button. The Database Deletion popup opens.
- Delete Database In the popup window, enter the name of the Database you want to delete, then click the Confirm button.
Managing Parameters
Provides a feature that enables easy viewing and modification of database configuration parameters.
Query Parameter
To view configuration parameters, follow these steps.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. You will be taken to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. Navigate to the Microsoft SQL Server(DBaaS) List page.
- Microsoft SQL Server(DBaaS) List page, click the resource whose parameters you want to view or modify. Microsoft SQL Server(DBaaS) Details page will open.
- Click the More button, then click the Parameter Management button. The Parameter Management popup window opens.
- Parameter Management popup window, click the Search button. Search Notification popup window opens.
- Lookup Notification When the popup window opens, click the Confirm button. The lookup may take a short amount of time.
Modify Parameter
To modify the configuration parameters, follow these steps.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Go to the Service Home page of Microsoft SQL Server(DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource whose parameters you want to view or modify. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Click the More button, then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management popup window, click the Search button. Search Notification popup window opens.
- Lookup Notification When the popup window opens, click the Confirm button. Retrieving the data may take a short time.
- If modification is needed, click the Edit button and enter the changes in the custom value area of the Parameter to be edited.
- When the input is complete, click the Complete button.
Managing DB Users
Provides functionality to query and manage DB user information.
Query DB Users
To retrieve DB users, follow the steps below.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource for which you want to view DB users. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Click the More button, then click the DB User Management button. You will be taken to the DB User Management page.
- DB User Management page, click the Search button. The search may take a short amount of time.
Change DB User Status
Follow these steps to change the status of the retrieved DB user.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. You will be taken to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource whose DB user you want to modify. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Click the More button, then click the DB User Management button. You will be taken to the DB User Management page.
- On the DB User Management page, click the Search button. Retrieving may take a short time.
- If a correction is needed, click the Edit button, then change the status field value or enter remarks.
- When the input is complete, click the Complete button.
Modify Audit Settings
You can modify the Audit log storage settings for Microsoft SQL Server (DBaaS).
To change the Audit log storage settings of Microsoft SQL Server(DBaaS), follow the steps below.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Go to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource to view the service status. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Click the Edit icon of Audit Settings at the bottom of the detailed information. The Edit Audit Settings popup window opens.
- Edit Audit Settings After changing the usage in the popup window, click the Confirm button.
- Use selected, the Audit log feature is enabled. Enabling the Audit log may degrade DB performance.
- Disabling use will delete the Audit log storage file. Back up the Audit log file separately before disabling.
DB Log Export
Supports exporting log data that requires long-term retention among audit logs to Object Storage. Users can directly set the log types to be stored, the target Bucket for export, and the export interval. Based on the configured criteria, logs are copied to the specified Object Storage for retention. Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for long-term storage.
- To use the DB Log export feature, you must create an Object Storage. For creating an Object Storage, please refer to the Object Storage User Guide.
- Please be sure to check the expiration date and time of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
- Please ensure that authentication key information is not exposed externally.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. You will be taken to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource whose DB Log you want to export. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
- On the DB Log Export page, click the Register button. You will be taken to the DB Log Export Register page.
- On the DB Log Export Registration page, after entering the required information, click the Complete button.
Category Required Detailed descriptionLog type Required Log type to be saved Save bucket name Required Object Storage bucket name to be saved Authentication key > Access key Required Access key to access the Object Storage you want to store Authentication key > Secret key Required Secret key for accessing the Object Storage you want to store File creation interval Required File creation frequency in Object Storage Whether to delete the original log Selection Whether to delete the original logs when exporting to Object Storage Table. Microsoft SQL Server (DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow the steps below.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource you want to manage DB Log export for. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
- On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, or 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 settings.
- Cancel: Cancel the DB Log export mode setting.
Minor Version Upgrade
We provide version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades within the same Major version are supported.
- First retrieve the service status by synchronizing it, then perform the version upgrade.
- Please perform the version upgrade after setting up a backup. If you do not set up a backup, you may be unable to recover some data if a problem occurs during the upgrade.
- The backed-up data will be automatically deleted after the version upgrade is completed.
To upgrade the Minor Version, follow the steps below.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- Microsoft SQL Server(DBaaS) List page, click the resource to upgrade the version. Navigate to the Microsoft SQL Server(DBaaS) Details page.
- Click the Edit button of the Image version item. The Version Upgrade popup window opens.
- Version Upgrade In the popup, select the updated version and backup setting, then click the Confirm button.
- Version Upgrade Notification Click the Confirm button in the popup window.
5.2.2 - Backing up and restoring the DB
Users can configure backups of Microsoft SQL Server (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Microsoft SQL Server(DBaaS) Backup
Microsoft SQL Server (DBaaS) provides a data backup feature 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 backup configuration of Microsoft SQL Server (DBaaS), see the Microsoft SQL Server(DBaaS) Creating guide.
To modify the backup settings of the created resource, follow the steps below.
If a backup is configured, it will run at the designated time after the set schedule, and additional fees will be incurred based on the backup size.
- If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server(DBaaS) List Click the resource on the page to configure backup. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Edit button for the backup item. 4. Backup Settings popup opens.
- When setting up a backup, click Use in the Backup Settings popup, select retention period, backup start time, and Archive backup interval, then click the Confirm button.
- If you stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Once user authentication is complete, the backup configuration is disabled and backup execution stops.
- If you stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Check backup history
To view the backup history, follow these steps.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List page, click the resource to view the backup history. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server(DBaaS) List Click the resource on the page to view the backup history. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup, check the files you want to delete, then authenticate via the logged-in user’s mobile phone.
- When user authentication is completed, the backup file is deleted.
Microsoft SQL Server(DBaaS) Recovery
If a backup file needs to be restored due to a failure or data loss, the recovery feature allows restoration based on a specific point in time. When you perform a Microsoft SQL Server(DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds using the database’s configuration information and data.
To recover Microsoft SQL Server (DBaaS), follow the steps below.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server (DBaaS) resource On the list page, click the resource you want to recover. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Database Recovery button. 4. Go to the Database Recovery page.
- After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
Category required statusDetailed description Recovery Type required Set the point in time the user wants to recover - Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
- Custom point: Recover to a user‑desired point within the range of recoverable backup times. The recoverable period depends on the Archive backup cycle setting, allowing recovery from the initial backup start time up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the date and time to back up
Server name prefix Required Recovery DB server name - Start with a lowercase English letter and use lowercase letters, numbers, and special characters (
-) to enter 3 to 16 characters
- Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name Essential Recovery DB cluster name - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Recovery DB Server Type - Standard: Standard specification commonly used
- High Capacity: Large-capacity server with 24 vCores or more
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute Apply
Service Type > Block Storage Required Block Storage settings used by the recovery DB - Base OS: Area where the DB engine is installed
- DATA: Data storage area
- 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: Data storage area
- Applied identically with the storage type set in the source cluster
- In the recovery DB, only DATA and TEMP purposes can be added
- After selecting Use, enter the storage purpose and capacity
- To add storage, click the Add button, and 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
Database username Required Database username - Apply the same username set in the original cluster
Database Port number Essential Database Port number - Apply the same Port number as set in the original cluster
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day, start time, and duration
- It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruption
- If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
tag Selection Add Tag - After clicking the Add Tag button, enter or select Key, Value
Table. Microsoft SQL Server (DBaaS) recovery configuration items
5.2.3 - Secondary Add
The user can enter the required information for Secondary through the Samsung Cloud Platform Console and create the service using detailed options.
Add Secondary
You can create a read‑only replica server by configuring a Secondary. To add additional Secondaries, they must be created with a high‑availability (HA) configuration and Enterprise Edition, and the backup feature must be enabled.
To configure Secondary, follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource to configure Secondary. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Click the Secondary Add button. Navigate to the Secondary Add page.
- After entering information in the Secondary configuration area, click the Create button.
Category Required statusDetailed description Secondary number Required Number of Secondary to configure - Only one can be configured per cluster
Secondary name Required Secondary server name - must start with a lowercase English letter, and use lowercase letters, numbers, and special characters(
-) to enter 3 to 15 characters
- The entered Secondary name is displayed as the cluster name in the list
Service Type > Server Type Required Secondary server type - Apply the same as the server type set in the source DB
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Go to the Planned Compute service request page
- For more details, refer to Apply for Planned Compute
Network > Common Settings Required Network settings where servers generated by the service are installed - Applied identically to the network settings configured in the original DB
Network > Server-specific Settings Required Network settings for servers deployed by the service - Select when you want to apply different settings per installed server
- Apply the same network settings as configured in the source DB
- When configuring per server
10.10.10.0/24Enter an IP address within the range
License Required SQL Server License Key - Enter the issued license key
- If the entered license key is not valid, the service may not be created
Table. Microsoft SQL Server (DBaaS) Secondary configuration items
5.2.4 - Microsoft SQL Server(DBaaS) Server Connection
Scenario Overview
Microsoft SQL Server(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 Microsoft SQL Server(DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish network connectivity through it. To maintain stability and a high level of security, it is recommended to configure the Database service in a Private Subnet environment and place the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and a Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Scenario components
You can build the scenario using the following services.
| Service group | service | Detailed description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that lets users subdivide the network within a VPC to match their purpose and scale. | |
| Networking | VPC > Public IP | Service that reserves a public IP and allocates and releases it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the Internet | |
| Networking | Security Group | Virtual firewall that controls server traffic | |
| Database | Microsoft SQL Server(DBaaS) | A service that easily creates and manages Microsoft SQL Server in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- Since the default policy of a Security Group is Deny All, you must register only the IPs that are allowed.
- In/Outbound’s All Open(Any IP, Any Port) policy can expose cloud resources directly to external threats.
- By specifying the required IP and port and setting a policy, you can strengthen security.
Scenario setup method
Create the services required to compose the scenario by following the steps below.
Set up the network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
1-1. Create VPC
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- Click the VPC Creation button on the Service Home page. You will be taken to the VPC Creation page.
- On the VPC Creation page, enter the information required to create the service.
- Enter the IP range as
192.168.x.0/16.
- Enter the IP range as
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, check the created resources on the VPC List page.
1-2. Create Subnet
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
- Click the Create Subnet button. You will be taken to the Create Subnet page.
- On the Subnet Creation page, enter the information required to create the service.
- Select the Subnet type as General.
- Select a pre‑created VPC.
- Enter the IP range as
192.168.x.0/24.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resources on the Subnet list page.
1-3. Create Internet Gateway
- Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
- Click the Create Internet Gateway button. Navigate to the Create Internet Gateway page.
- Internet Gateway Creation page, enter the required information for creating the service.
- Select a pre‑created VPC.
- In the Firewall usage option, select Use.
- In the Summary panel, verify the detailed information and estimated billing amount, and click the Complete button.
- Once creation is complete, verify the created resource on the Internet Gateway List page.
1-4. Create Public IP
- Click the All Services > Networking > VPC menu. Navigate to the VPC Service Home page.
- Click the Public IP menu on the Service Home page. You will be taken to the Public IP List page.
- Click the Public IP Reservation button. You will be taken to the Public IP Reservation page.
- On the Public IP reservation page, enter the required information needed to reserve the service.
- In the Summary panel, verify the detailed information and estimated billing amount, then click the Complete button.
- When creation is complete, check the created resources on the Public IP list page.
1-5. Create Security Group
- Click the All Services > Networking > Security Group menu. Navigate to the Service Home page of Security Group.
- Click the Create Security Group button on the Service Home page. You will be taken to the Create Security Group page.
- On the Security Group creation page, enter the required information needed to create the service.
- Check the input information and click the Complete button.
- When creation is complete, check the created resources on the Security Group list page.
Create Bastion host
Describes the process of configuring a Bastion Host that requires the database client to be installed.
2-1. Create Server Keypair
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
- Click the Create Keypair button. You will be taken to the Create Keypair page.
- Enter the required information for creating a service on the Keypair creation page.
- Verify the creation information and click the Complete button.
- The key can be downloaded only on the first attempt, and reissuance is not available.
- Please store the downloaded key in a secure location.
2-2. Create Bastion host
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Create Virtual Server button. You will be taken to the Create Virtual Server page.
- On the Virtual Server Creation page, enter the required information to create the service.
- Select Windows for the image.
- Select the pre-created VPC and Subnet.
- Click Use NAT, then select the reserved Public IP from 1-4. Create Public IP.
- Connect the Keypair created in 2-1. 서버 Keypair 생성하기.
- In the Summary panel, verify the detailed information and estimated billing amount, then click the Complete button.
- When creation is complete, check the created resources on the Virtual Server List page.
2-3. Verify Bastion host login ID and PW
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
- On the Virtual Serve List page, click the resource you created in 2-2. Bastion host Create. You will be taken to the detailed information page for that resource.
- On the detail information page, click the RDP password view button in the Keypair name field. The RDP password view popup window opens.
- In the popup window, perform RDP password lookup, and attach the keypair file downloaded from 2-1. Create Server Keypair.
- After attaching, click the Password Check button. The ID and Password for accessing the resource are displayed.
- The ID and password will later be used as credentials to connect to the Bastion host in 5-1. Bastion host Connecting.
Create Database
Describes the process of creating a Database service.
3-1. Microsoft SQL Server(DBaaS) Create Service
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Go to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Create Microsoft SQL Server (DBaaS) button. Navigate to the Create Microsoft SQL Server (DBaaS) page.
- On the Microsoft SQL Server(DBaaS) Creation page, enter the required information to create the service.
- Select the pre‑created VPC and Subnet and connect them.
- Enter 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 users can also specify it.
- 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 resource on the Microsoft SQL Server(DBaaS) list page.
Configuring Rules
It explains the process of configuring rules for a user to connect to the Bastion host and rules for connecting to the Database from the Bastion host.
4-1. Adding security rules to Security Group
- Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
- Click the Security Group menu on the Service Home page. You will be taken to the Security Group List page.
- 1-5. Creating a Security Group Select the Security Group resource you created. Navigate to the detailed information page for that resource.
- Click the Rules tab on the detail page. You will be taken to the Rules tab.
- On the Rules tab, click the Add Rule button. It takes you to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
direction remote target address Protocol Port Explanation Inbound CIDR User PC IP TCP 3389 (RDP) Bastion client PC → Bastion host Outbound CIDR DB IP TCP Database Port (manual entry) Bastion host → Database Table. Security Group rules that need to be added
4-2. Add IGW Firewall rule
- All Services > Networking > Firewall Click the menu. Then navigate to the Service Home page of Firewall.
- From the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
- On the Firewall List page, select the Internet Gateway resource name created in 1-3. Create Internet Gateway. You will be taken to the detailed information page of that resource.
- Click the Rules tab on the detail information page. You will be taken to the Rules tab.
- Click the Add Rule button on the Rules tab. It navigates to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
origin address Destination address Protocol Port operation direction Explanation Bastion connection PC IP Bastion host IP TCP 3389(RDP) Allow Inbound User PC → Bastion host Table. Internet Gateway Firewall rules that need to 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 SSMS(Microsoft SQL Server Management Studio). Since there are various database client programs and CLI utilities, you may install and use the tool that best fits your needs.
5-1. Connect to Bastion host
- In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
- When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password verified in 2-3. Check Bastion host login ID and PW and click the Confirm button.
5-2. Install the DB client program (SSMS) on the Bastion host
- Go to the official Microsoft SQL Server page and download the SSMS program.
- SSMS program download URL: https://learn.microsoft.com/en-us/ssms/download-sql-server-management-studio-ssms
- Connect the user’s PC hard drive to upload the file to the Bastion host.
- In the Remote Desktop Connection’s Local Resources tab, click the Details button for the Local Devices and Resources item.
- Select the local disk of the location where the file was downloaded on the drive, and click the OK button.
- Copy the downloaded file, upload it to the Bastion Host, and click the SSMS (Microsoft SQL Server Management Studio) installation file to install.
5-3. Connect to the Database using the DB client program (SSMS)
- Run SSMS (Microsoft SQL Server Management Studio). A Connect to Server popup will appear.
- Connect to Server In the popup window, enter the Database server information created in 3-1. Microsoft SQL Server(DBaaS) 서비스 생성하기 and click the Connect button.
Required input field input value Server type Database Engine Server name Database server IP, Database Port (ex. 192.168.10.1,2866) Authentication SQL Server Authentication Login Database username Password Database password Encryption Optional Table.DB connection client program input fields - Once the connection is established, the database will be accessed. After connecting, you can execute simple queries, among other tasks.
5.3 - API Reference
5.4 - CLI Reference
5.5 - Release Note
Microsoft SQL Server(DBaaS)
- Add Microsoft SQL Server (DBaaS) feature
- Add 2nd‑generation server type
- Add a 2nd‑generation (db2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, see Microsoft SQL Server(DBaaS) 서버 타입.
- DB User and Access Control Management Add
- For more details, refer to DB User Management, DB Access Control Management
- Add DB Audit Log Export feature
- For detailed information, refer to DB Log Export.
- Backup Notification Feature provided
- Provides notification functionality for backup success and failure. For more details, see Create Notification Policy.
- Add HDD, HDD_KMS types to Block Storage type
- Add 2nd‑generation server type
- A Microsoft SQL Server(DBaaS) service that enables easy creation and management of Microsoft SQL Server in a web environment has been launched.
6 - CacheStore(DBaaS)
6.1 - Overview
Service Overview
CacheStore(DBaaS) is a service that provides the in-memory data stores Redis OSS and Valkey. Samsung Cloud Platform provides an environment that automates the installation of Redis OSS and valkey through a web-based console and performs management functions for operation.
CacheStore (DBaaS) provides a Sentinel architecture consisting of a Master server that performs read/write operations and read‑only Replica servers that replicate the Master data. Sentinel checks the status of DB servers with the engine installed, and when a failure occurs on the Master server, it automatically fails over the Replica servers to the Master server. Additionally, to prepare for potential issues with the DB server or data, we provide a feature that automatically backs up at a user-specified time, enabling data recovery based on the backup point.
Provided Features
CacheStore(DBaaS) provides the following features.
- Auto Provisioning(Auto Provisioning): It is possible to install and configure the Database (DB) via the UI, and a redundant configuration can be set up with a Sentinel-based Single Master server and Replica servers (1 or 2).
- Operation Control Feature: 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 configured for high availability (HA), you can switch the Active-Standby servers via a switch-over.
- Backup and Recovery: Provides data backup functionality based on its own backup commands. * Backup time windows and storage locations can be set by the user, and additional fees apply based on 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.
- Parameter Management: Performance improvement and security-related DB configuration parameters can be modified.
- Service Status Query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, and DB performance monitoring information can be viewed through the Cloud Monitoring service.
- Minor version upgrade: To apply some feature improvements and security patches, you can perform a Minor version upgrade within the same Major version.
Component
CacheStore (DBaaS) provides pre‑validated engine versions and various server types in accordance with its open‑source support policy. Users can select and use it according to the scale of the service they wish to configure.
Engine version
The engine versions supported by CacheStore (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.
- Redis: https://redis.io/docs/latest/operate/oss_and_stack/install/version-mgmt/
- Valkey: https://valkey.io/topics/releases/
| image | Provided version | EoS Date | EoTS Date |
|---|---|---|---|
| Redis OSS Sentinel | 7.2.11 | 2029-06 (planned) | 2029-12-01 |
| valkey Sentinel | 8.1.4 | TBD | TBD |
The next version of CacehStore is scheduled to be offered after July 2026. The actual service delivery schedule is subject to change.
- Redis OSS Sentienl 7.2.14
- Valkey Sentienl 8.1.7
Server type
The server types supported by CacheStore (DBaaS) are as follows.
For detailed information about the server types provided by CacheStore(DBaaS), see CacheStore(DBaaS) Server Types.
Standard redis1v2m4
| Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type
|
| Server specifications | redis1 | Provided server specifications
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
Preceding Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
6.1.1 - Server Types
CacheStore(DBaaS) server type
CacheStore(DBaaS) offers server types composed of various combinations such as CPU, Memory, and Network Bandwidth. When creating a CacheStore (DBaaS), Redis is installed according to the server type selected for the intended use.
The server types supported by CacheStore(DBaaS) are as follows.
Standard redis1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classification
|
| Server specifications | redis1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
redis1 server type
The redis1 server type of CacheStore (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | redis1v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | redis1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | redis1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | redis1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | redis1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | redis1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | redis1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | redis1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | redis1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | redis1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | redis1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | redis1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | redis1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | redis1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | redis1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | redis1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | redis1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
css1 server type
The css1 server type of CacheStore (DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | css1v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | css1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | css1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | css1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | css1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | css1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | css1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | css1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | css1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | css1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | css1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | css1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | css1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | css1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | css1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | css1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | css1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
6.1.2 - Monitoring metrics
According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
- New Resources: Resources created after the service improvement work in July 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, we must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Cloud Monitoring Service Phased Termination Schedule Notice
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, Cloud Monitoring data cannot be accessed. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
CacheStore(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics for CacheStore (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
For CacheStore (DBaaS) server monitoring metrics, refer to the Virtual Server Monitoring Metrics guide.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Defragmentation Keys [Hits] | Number of keys after defragmentation | cnt |
| Active Defragmentation Keys [Miss] | Number of keys skipped in the active defragmentation removal process | cnt |
| Active Defragmentationd [Hits] | Number of value reallocations performed by the active defragmentation removal process | cnt |
| Active Defragmentations [Miss] | Count of value reallocations interrupted by the active defragmentation removal process | cnt |
| Allocated Bytes [OS] | Number of bytes allocated by CacheStore (DBaaS) and recognized by the operating system (resident set size) | bytes |
| Allocated Bytes [Redis] | Total bytes allocated by CacheStore (DBaaS) | bytes |
| AOF Buffer Size | AOF buffer size | bytes |
| AOF File Size [Current] | AOF current file size | bytes |
| AOF File Size [Lastest Startup] | AOF file size on recent start or rewrite | bytes |
| AOF Rewrite Buffer Size | AOF rewrite buffer size | bytes |
| AOF Rewrite Current Time | If applicable, the time of the ongoing AOF rewrite operation | sec |
| AOF Rewrite Last Time | Final AOF rewrite time | sec |
| Calls | Number of calls that reached command execution (not rejected) | cnt |
| Changes [Last Saved] | Number of changes after the final dump | cnt |
| Client Output Buffer [MAX] | Longest output list among current client connections | cnt |
| Clients [Sentinel] | Number of client connections (Sentinel) | cnt |
| Connected Slaves | Number of connected slaves | cnt |
| Connections [Blocked] | Number of clients pending on blocking calls (BLPOP, BRPOP, BRPOPLPUSH) | cnt |
| Connections [Current] | Number of client connections (excluding slave connections) | cnt |
| Copy On Write Allocated Size [AOF] | COW allocation size during final RBD save operation | bytes |
| Copy On Write Allocated Size [RDB] | COW allocation size during the final RBD save operation | bytes |
| CPU Time [Average] | Average CPU time used per command execution | cnt |
| CPU Time [Total] | Total CPU time used by these commands | usec |
| CPU Usage [System Process] | System CPU usage by background processes | % |
| CPU Usage [System] | System CPU usage on the CacheStore (DBaaS) server | % |
| CPU Usage [User Process] | User CPU usage used by background processes | % |
| CPU Usage [User] | System CPU usage by background processes | % |
| Dataset Used | Dataset size | bytes |
| Disk Used | datadir usage | MB |
| Evicted Keys | Number of evicted keys caused by the maxmemory limit | cnt |
| Fsyncs [Delayed] | Delayed fsync counter | cnt |
| Fsyncs [Pending] | Number of pending fsync operations in the background I/O queue | cnt |
| Full Resyncs | Number of full resynchronizations with the slave | cnt |
| Keys [Expired] | Total number of key expiration events | cnt |
| Keys [Keyspace] | Number of keys in the key space | cnt |
| Lastest Fork Duration Time | Recent fork (fork) operation time | usec |
| Lookup Keys [Hit] | Number of successful key lookups in the dictionary | cnt |
| Lookup Keys [Miss] | Number of failed key lookups in the main dictionary | cnt |
| Lua Engine Memory Used | Memory used by the Lua engine | bytes |
| Master Last Interaction Time Ago | Time elapsed since the final interaction with the master | sec |
| Master Last Interaction Time Ago [Sync] | Time elapsed since the final interaction with the master | sec |
| Master Offset | Current replication offset of the server | pid |
| Master Second Offset | Offset until the replication ID is accepted | pid |
| Master Sync Left Bytes | Remaining bytes before synchronization completes | bytes |
| Memory Fragmentation Rate | Ratio of used_memory_rss to used_memory | % |
| Memory Fragmentation Rate [Allocator] | Fragmentation ratio | % |
| Memory Fragmentation Used | Bytes between used_memory_rss and used_memory | bytes |
| Memory Fragmentation Used [Allocator] | resident byte | bytes |
| Memory Max Value | Memory limit | bytes |
| Memory Resident [Allocator] | resident memory | bytes |
| Memory RSS Rate [Allocator] | Resident ratio | % |
| Memory Used [Active] | Active memory | bytes |
| Memory Used [Allocated] | Allocated memory | bytes |
| Memory Used [Resident] | Resident byte | bytes |
| Network In Bytes [Total] | Total network input (bytes) | bytes |
| Network Out Bytes [Total] | Total network output (bytes) | bytes |
| Network Read Rate | Network read speed (KB/sec) | cnt |
| Network Write Rate | Network write speed (KB/sec) | cnt |
| Partial Resync Requests [Accepted] | Number of accepted partial resynchronization requests | cnt |
| Partial Resync Requests [Denied] | Number of rejected partial resynchronization requests | cnt |
| Peak Memory Consumed | Maximum memory used by CacheStore (DBaaS) | bytes |
| Processed Commands | Number of commands processed per second | cnt |
| Processed Commands [Total] | Total number of processed commands | cnt |
| Pub/Sub Channels | Global count of pub/sub channels with client subscriptions | cnt |
| Pub/Sub Patterns | Global count of publish/subscribe patterns with client subscriptions | cnt |
| RDB Saved Duration Time [Current] | If applicable, the time of the ongoing RDB save operation | sec |
| RDB Saved Duration Time [Last] | Final RDB save operation time | sec |
| Received Connections [Total] | Total number of received connections | cnt |
| Rejected Connections [Total] | Total number of rejected connections | cnt |
| Replication Backlog Actove Count | Replication backlog activation flag | cnt |
| Replication Backlog Master Offset | Master offset of the replication backlog buffer | cnt |
| Replication Backlog Size | Data size of the replication backlog buffer | bytes |
| Replication Backlog Size [Total] | Total size of the replication backlog buffer | bytes |
| Slave Priority | Server priority as a fault remediation target | cnt |
| Slave Replication Offset | Replication offset of the slave server | pid |
| Slow Operations | Number of slow tasks | cnt |
| Sockets [MIGRATE] | Number of sockets opened for migration | cnt |
| Tracked Keys [Expiry] | Number of keys tracked for expiration (applicable only to writable slaves) | cnt |
| Instance Status [PID] | redis-server process PID | pid |
| Sentinel Status [PID] | sentinel process PID | pid |
6.2 - How-to guides
Users can create the service by entering the required information for CacheStore (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be 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 released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service per Resource
- New Resources: Resources created after the July 2026 service improvement work are provided with default monitoring 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, we must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings linked with existing Cloud Monitoring (ex. You must review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Notice of the phased termination schedule for Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
Create CacheStore (DBaaS)
You can create and use the CacheStore (DBaaS) service from the Samsung Cloud Platform Console.
Before creating the service, configure the VPC’s subnet type as General.
- If the subnet type is Local, the corresponding Database service cannot be created.
To create a CacheStore (DBaaS), follow the steps below.
- All Services > Database > CacheStore(DBaaS) Click the menu. 1. Go to the Service Home page of CacheStore (DBaaS).
- On the Service Home page, click the Create CacheStore (DBaaS) button. 2. Create CacheStore (DBaaS) Go to the page.
- On the Create CacheStore (DBaaS) page, enter the information required to create the service and select detailed options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version Essential Provide version list for CacheStore (DBaaS) Table. CacheStore (DBaaS) Image and version selection items - Enter or select the required information in the Service Information Input area.
Category required statusDetailed description Server name Prefix Required Server name where Redis/Valkey will be installed - must start with a lowercase English letter, and using lowercase letters, numbers, and the special character (
-) input 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is appended to create the actual server name
Cluster name Required Cluster name where Redis/Valkey is installed - Enter using English letters, 3 to 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for installing Redis/Valkey - Standard: Standard specification commonly used
- For detailed information about the server types provided by CacheStore (DBaaS), refer to CacheStore(DBaaS) 서버 타입.
Service Type > Planned Compute Required Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage preview: Amount applied per resource by Planned Compute
- Create Planned Compute service: Navigate to the Planned Compute service request page
- For more details, see Apply for Planned Compute
Service Type > Block Storage Required Block Storage settings used by the DB according to purpose - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Select the storage type and then enter the capacity (refer to 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 also applied to additional storage
- Enter the capacity as a multiple of 8 within the range 16 to 5,120
- Select the storage type and then enter the capacity (refer to Block Storage 생성하기 for details on each Block Storage type)
high availability Select High Availability (HA) configuration option - When High Availability (HA) is enabled, it is provided as a Master-Replica setup, and the Replica can be configured with 1 or 2 instances
- Sentinel Port number: The port used for connecting to Sentinel
- Enter a port for Master-Replica communication within the range 1200 to 65535
- Replica count: Number of Replicas to configure
- If 1 is selected, it is configured as Master-Replica-Sentinel
- If 2 is selected, it is configured as Master-Replica-Replica, and Sentinel is automatically installed on the server where Redis is installed
- Set the server type for Sentinel to the minimum specification
Network Required The network where CacheStore (DBaaS) is installed - Select a pre‑created VPC and Subnet to connect
- IP can only be auto‑generated
Network > Common Settings Required Network settings for servers created by the service - Select when you want to apply the same settings to all installed servers
- Select a pre‑created VPC and Subnet
- IP can only be auto‑generated
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings per 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 details, see Public IP 생성하기
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32) and click the Add button.
- To delete an entered IP, click the x button next to the entered IP.
maintenance period Select CacheStore(DBaaS) maintenance period - If you select Use, set the day, start time, and duration
- It is recommended to set a maintenance period for stable DB management. 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. CacheStore (DBaaS) Service Configuration Items - must start with a lowercase English letter, and using lowercase letters, numbers, and the special character (
- Enter or select the required information in the Database Configuration Required Information Input area.
Category required statusDetailed description Backup Select Backup usage - If you select Use, you can set the backup file retention period and backup start time
- Backup files incur additional charges based on their size
- The file retention period can be set from 7 to 35 days
- The minute at which the backup runs (minutes) is set randomly, and the backup end time cannot be configured
Redis/Valkey Port number Required Port number required for Redis/Valkey connection - Enter a port within the range 1200 ~ 65535
Redis/Valkey password Essential Password required when connecting to Redis/Valkey - include letters, numbers, and special characters (excluding
$“‘) and enter 8 to 30 characters
Check Redis/Valkey password Required Re-enter the same password Parameter Required Parameters to use with Redis/Valkey - View button can be clicked to view detailed parameter information
- Parameters can be modified after creation is complete, and a DB restart is required after modification
time zone Required The time zone where the database will be used Table. CacheStore (DBaaS) Database configuration items - Additional Information Input area, enter or select the required information.
Category required statusDetailed description Tag Select Add Tag - Up to 50 per resource can be added
- After clicking the Add Tag button, enter or select Key, Value values
Table. CacheStore (DBaaS) additional information input fields
- Select the required information in the Image and version selection area.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Create button.
- Once creation is complete, check the created resource on the Resource List page.
View CacheStore (DBaaS) detailed information
The CacheStore (DBaaS) service allows you to view and edit the full list of resources and detailed information. CacheStore(DBaaS) Details page consists of Details, Tags, Activity History tabs.
To view detailed information about the CacheStore (DBaaS) service, follow these steps.
- All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. 2. Go to the CacheStore(DBaaS) List page.
- CacheStore(DBaaS) List page, click the resource to view its detailed information. 3. CacheStore(DBaaS) Details Go to the page.
- CacheStore(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
Category Detailed description Cluster status Cluster status with Redis installed - Creating: Cluster is being created
- Editing: Cluster is changing to an operational state
- Error: Cluster encountered an error while performing tasks
- 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
Cluster control Buttons to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Promote a replica cluster to Master
View more add-ons Cluster-related management buttons - Service status synchronization: Real-time Redis/Valkey service status lookup
- Backup history: When backup is configured, verify successful execution and view history
- Database recovery: Recover the DB based on a specific point in time
- Parameter management: View and modify Redis/Valkey configuration parameters
- Rename-Command: Change the name of a Redis/Valkey command
Service termination Button to cancel the service Table. CacheStore(DBaaS) status information and additional features
- CacheStore(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
Detailed Information
CacheStore(DBaaS) List page allows you to view detailed information of the selected resource and, if needed, modify the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Image version | Installed Redis/Valkey image and version information
|
| Cluster name | Cluster name of the configured Redis/Valkey servers |
| Planned Compute | Resource status with Planned Compute configured
|
| maintenance period | DB patch work period setting status
|
| Backup | Backup Configuration Status
|
| Redis/Valkey Port number | Port number required for connecting to Redis/Valkey |
| time zone | Redis/Valkey time zone |
| Sentinel Port number | Port number for communication between Master and Replica |
| VIP | Virtual IP information
|
| Network | Network information (VPC, Subnet) where CacheStore (DBaaS) is installed |
| IP access control | Service access policy configuration
|
| Master & Replica | Master, Replica server type, base OS, additional Disk information
|
| Sentinel | Sentinel server type, basic OS information
|
Tag
CacheStore(DBaaS) List page lets you view the tag information of the selected resource, and you can add, change, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Work History
On the CacheStore(DBaaS) List page, you can view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource change history
|
Managing CacheStore (DBaaS) Resources
If you need to change or restore the existing configuration options of a created CacheStore (DBaaS) resource, or modify commands, you can perform the tasks on the CacheStore(DBaaS) Details page.
Control operation
If changes occur to a running CacheStore (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Master-Replica servers via a switch‑over.
To control the operation of CacheStore (DBaaS), follow these steps.
- Click the All Services > Database > CacheStore(DBaaS) menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Navigate to the page.
- CacheStore(DBaaS) List page, click the resource you want to control. 3. CacheStore(DBaaS) Details Go to the page.
- Check the CacheStore status and complete the change using the control button below.
- Start: the server where the CacheStore service is installed and the CacheStore service is running (Running).
- Stop: The server where the CacheStore service is installed and the CacheStore service can be stopped (Stopped).
- Restart: Only the CacheStore service can be restarted.
- Switch Over: You can switch the Master server and the Replica server.
Synchronize service status
You can synchronize the real-time service status of CacheStore (DBaaS).
To check the service status of CacheStore (DBaaS), follow the steps below.
- Click the All Services > Database > CacheStore(DBaaS) menu. 1. Go to the Service Home page of CacheStore (DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. 2. Navigate to the CacheStore(DBaaS) List page.
- CacheStore(DBaaS) List page, click the resource to view the service status. 3. CacheStore(DBaaS) Details Go to the page.
- Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.
Change server type
You can change the configured server type.
To change the server type, follow these steps.
- All Services > Database > CacheStore(DBaaS) Click the menu. 1. Go to the Service Home page of CacheStore (DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. 2. Go to the CacheStore(DBaaS) List page.
- On the CacheStore(DBaaS) List page, click the resource to change the server type. 3. Go to the CacheStore(DBaaS) Details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Edit Server Type After selecting the server type in the popup window, click the Confirm button.
Cancel CacheStore (DBaaS)
You can reduce operating costs by terminating unused CacheStore (DBaaS). 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.
To cancel CacheStore(DBaaS), follow the steps below.
- All Services > Database > CacheStore(DBaaS) Click the menu. 1. Navigate to the Service Home page of CacheStore (DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. 2. CacheStore(DBaaS) List Go to the page.
- On the CacheStore(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
- After termination is complete, check whether the resource has been terminated on the CacheStore(DBaaS) list page.
6.2.1 - CacheStore Service Manage
Users can manage CacheStore (DBaaS) through the Samsung Cloud Platform Console.
Parameter Management
Provides a feature that allows you to easily view and edit database configuration parameters.
View Parameters
To view configuration parameters, follow these steps.
- Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. You will be taken to the CacheStore(DBaaS) List page.
- On the CacheStore(DBaaS) List page, click the resource whose parameters you want to view or edit. You will be taken to the CacheStore(DBaaS) Details page.
- Click the More button, then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management in the popup window, click the Search button. The Search Notification popup window opens.
- View 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 the steps below.
- Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. You will be taken to the CacheStore(DBaaS) List page.
- On the CacheStore(DBaaS) List page, click the resource whose parameters you want to view or edit. You will be taken to the CacheStore(DBaaS) Details page.
- Click the More button, then click the Parameter Management button. The Parameter Management popup opens.
- In the Parameter Management popup, click the Query button. The Query Notification popup opens.
- Lookup Notification When the popup window opens, click the Confirm button. The lookup may take a short amount of time.
- If a modification is needed, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
- When the input is complete, click the Complete button.
Rename Command
Provides Redis OSS/Valkey command lookup and command name editing functionality. To look up commands and edit command names, follow these steps.
- Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. You will be taken to the CacheStore(DBaaS) List page.
- On the CacheStore(DBaaS) List page, click the resource whose Command name you want to edit. You will be taken to the CacheStore(DBaaS) Detail page.
- Click the More button, then click the Rename-Command button. You will be taken to the Rename-Command page.
- On the Rename-Command page, click the Lookup button. The Lookup notification popup opens.
- View Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
- If a modification is needed, click the Edit button and enter the changes in the custom value field of the Command you want to modify.
- When the input is complete, click the Complete button.
Minor Version Upgrade
We provide version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades are supported within the same Major version.
To upgrade the Minor Version, follow the steps below.
- Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. You will be taken to the CacheStore(DBaaS) List page.
- CacheStore(DBaaS) List page, click the resource to upgrade the version. You will be taken to the CacheStore(DBaaS) Details page.
- Click the Edit icon of the Image version item. The Version Upgrade popup window opens.
- Version Upgrade In the popup window, select the revised version, then click the Confirm button.
- Version Upgrade Notification Click the Confirm button in the popup window.
6.2.2 - CacheStore Backup and Restore
Users can configure backups of CacheStore (DBaaS) through the Samsung Cloud Platform Console and restore from the backed-up files.
CacheStore(DBaaS) Backup
CacheStore (DBaaS) provides data backup functionality based on its own backup commands. Additionally, it offers a backup environment optimized for data protection and management through backup history verification and backup file deletion features.
Configure backup
For instructions on configuring backups for CacheStore(DBaaS), see CacheStore(DBaaS) Create.
To modify the backup settings of the created resource, follow the steps below.
If a backup is configured, it runs at the specified time after the set schedule, and additional fees apply based on the backup size.
- If you change the backup setting to unset, backup execution stops immediately, and any stored backup data is deleted and can no longer be used.
- Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
- Click the CacheStore(DBaaS) menu on the Service Home page. You will be taken to the CacheStore(DBaaS) List page.
- On the CacheStore(DBaaS) List page, click the resource for which you want to set up a backup. You will be taken to the CacheStore(DBaaS) Details page.
- Click the Edit icon of the backup item. The Backup Settings popup window opens.
- When configuring a backup, click Use in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
- If you stop the backup configuration, deselect Use in the Backup Settings popup window and click the Confirm button.
Check backup history
To check the backup history, follow these steps.
- Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
- Click the CacheStore(DBaaS) menu on the Service Home page. You will be taken to the CacheStore(DBaaS) List page.
- CacheStore(DBaaS) List page, click the resource for which you want to view the backup history. You will be taken to the CacheStore(DBaaS) Details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
- Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
- Click the CacheStore(DBaaS) menu on the Service Home page. You will be taken to the CacheStore(DBaaS) List page.
- CacheStore(DBaaS) List Click the resource whose backup history you want to view. You will be taken to the CacheStore(DBaaS) Details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window, check the files you want to delete, then click the Delete button.
CachStore(DBaaS) Recover
If a failure or data loss requires restoration from a backup file, recovery can be performed based on a specific point in time using the recovery feature.
To restore CacheStore(DBaaS), follow the steps below.
- Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. You will be taken to the CacheStore(DBaaS) List page.
- On the CacheStore(DBaaS) List page, click the resource you want to recover. You will be taken to the CacheStore(DBaaS) Details page.
- Click the Database Recovery button. You will be taken to the Database Recovery page.
- After entering information in the Database recovery configuration area, click the Complete button.
Category RequiredDetailed description Recovery type Required User sets the desired recovery point - Recover based on the backup file, selecting a point in time from the list displayed for backup files
Server name prefix Required Server name of the recovery DB - Start with a lowercase English letter and use lowercase letters, numbers, and special characters (
-) to enter 3 to 16 characters
- A postfix such as 001, 002 is appended to the base server name to create the actual server name
Cluster name Required Cluster name of the recovery DB - Enter using English letters, 3 to 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for the recovery DB - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server with 24 vCores or more (to be provided later)
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied by Planned Compute per resource
- Create Planned Compute Service: Go to the Planned Compute service request page
Service Type > Block Storage Required Block Storage settings used by the recovery DB - Base OS: Area where the DB engine is installed
- DATA: Area where AOF (Append Only File) and RDB (Redis Database) files, etc., are stored
- Apply the same Storage type as configured in the original cluster
- Capacity can be entered as a multiple of 8 within the range 56 to 5,120
Redis/Valkey Port number Required Redis/Valkey port number configured in the source DB IP access control Selection Service Access Policy Settings - 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 the IP in jIP format (e.g.,
192.168.10.1) or CIDR format (e.g.,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 IP
maintenance period Selection CacheStore(DBaaS) DB 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 DB management. Patch operations will be performed at the scheduled time, causing service interruption
- If set to not use, Samsung SDS is not responsible for any issues arising from unapplied patches.
tag Selection Add Tag - Add Tag After clicking the Add Tag button, enter or select Key, Value values
Table. CacheStore (DBaaS) recovery configuration items
6.2.3 - CacheStore(DBaaS) Server Connection
Scenario Overview
Connecting to CacheStore (DBaaS) The 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 CacheStore (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 set up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and a Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Scenario components
You can build the scenario using the following services.
| Service group | service | Detailed description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that lets users subdivide the network within a VPC to match their purpose and scale. | |
| Networking | VPC > Public IP | A service that reserves a public IP and allocates and releases it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the Internet | |
| Networking | Security Group | Virtual firewall that controls server traffic | |
| Database | CacheStore(DBaaS) | A service that easily creates and manages CacheStore in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- Since the default policy of a Security Group is Deny All, you must register only the IPs that are allowed.
- The All Open(Any IP, Any Port) policy of 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 setup method
Create the services needed to construct the scenario by following the steps below.
Set up the network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
1-1. Create VPC
- Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
- Click the Create VPC button on the Service Home page. Navigate to the Create VPC page.
- On the VPC Creation page, enter the information required to create the service.
- Enter the IP range as
192.168.x.0/16
- Enter the IP range as
- Summary panel, verify the detailed information and estimated billing amount generated, and click the Complete button.
- After creation is complete, check the created resources on the VPC List page.
1-2. Create Subnet
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
- Click the Subnet Create button. You will be taken to the Subnet Create page.
- On the Subnet Creation page, enter the information required to create the service.
- Select the Subnet type as General.
- Select a pre‑created VPC.
- Enter the IP range as
192.168.x.0/24.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resources on the Subnet List page.
1-3. Create Internet Gateway
- Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
- On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
- Click the Create Internet Gateway button. Navigate to the Create Internet Gateway page.
- Internet Gateway Creation page, enter the required information needed to create the service.
- Select a pre‑created VPC.
- In the Firewall usage item, select Use.
- 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 resource on the Internet Gateway list page.
1-4. Create Public IP
- Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
- Click the Public IP menu on the Service Home page. You will be taken to the Public IP List page.
- Click the Public IP reservation button. You will be taken to the Public IP reservation page.
- On the Public IP reservation page, enter the required information needed to reserve the service.
- 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 Public IP List page.
1-5. Create Security Group
- Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
- Click the Create Security Group button on the Service Home page. You will be taken to the Create Security Group page.
- On the Security Group creation page, enter the required information needed to create the service.
- Check the input information and click the Complete button.
- Once creation is complete, check the created resources on the Security Group List page.
Create bastion host
Describes the process of configuring a Bastion Host that requires the database client to be installed.
2-1. Create Server Keypair
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
- Click the Create Keypair button. You will be taken to the Create Keypair page.
- On the Keypair creation page, enter the required information for creating the service.
- Check the creation information and click the Complete button.
- The key can be downloaded only once, and reissuance is not available.
- Please store the downloaded key in a secure location.
2-2. Create Bastion host
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Create Virtual Server button. It navigates to the Create Virtual Server page.
- On the Virtual Server Creation page, enter the required information needed to create the service.
- Select Windows for the image.
- Select the pre‑created VPC and Subnet.
- Click Use NAT, and select the reserved Public IP from 1-4. Create Public IP.
- Connect the Keypair created in 2-1. 서버 Keypair 생성하기.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, check the created resources on the Virtual Server List page.
2-3. Check Bastion host login ID and PW
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
- On the Virtual Serve List page, click the resource you created in 2-2. Bastion host Create. You will be taken to the detailed information page for that resource.
- On the detail page, click the RDP password view button in the Keypair name field. The RDP password view popup window will open.
- In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
- After attaching, click the Password verification button. The ID and Password for accessing the resource are displayed.
- This ID and password will be used later as credentials to access the Bastion host in 5-1. Bastion host Connecting.
Create Database
Describes the process of creating a Database service.
3-1. Create CacheStore(DBaaS) Service
- Click the All Services > Database > CacheStore(DBaaS) menu. Go to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) Create button. You will be taken to the CacheStore(DBaaS) Create page.
- Enter the required information for creating the service on the CacheStore(DBaaS) Creation page.
- 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 section.
- The Database Port defaults to 2866, but the user can also specify it.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, verify the created resource on the CacheStore(DBaaS) list page.
Configuring 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. Security Group Add Security Rules
- Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
- On the Service Home page, click the Security Group menu. You will be taken to the Security Group List page.
- Select the Security Group resource created in 1-5. Create Security Group. Go to the detailed information page of that resource.
- Click the Rules tab on the detail information page. You will be taken to the Rules tab.
- Click the Add Rule button in the Rules tab. It navigates to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
direction Remote Target address Protocol Port Explanation Inbound CIDR User PC IP TCP 3389 (RDP) Bastion client PC → Bastion host Outbound CIDR DB IP TCP Database Port (manual entry) Bastion host → Database Table. Security Group rules that need to be added
4-2. Add IGW Firewall rule
- All Services > Networking > Firewall Click the menu. Go to the Service Home page of Firewall.
- From the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
- On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. You will be taken to the detailed information page for that resource.
- Click the Rules tab on the detail page. You will be taken to the Rules tab.
- Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below and click the Confirm button.
origin address Destination address Protocol Port Operation direction Explanation Bastion connection PC IP Bastion host IP TCP 3389(RDP) Allow Inbound User PC → Bastion host Table. Internet Gateway Firewall rules that need to be added
Connect to Database
Describes the process of a user connecting to a database via a DB client program.
This guide explains how to connect using Another Redis Desktop Manager. Since there are various database client programs and CLI utilities, you may install and use the tool that best fits your needs.
5-1. Connecting to Bastion host
- In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
- When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password you verified in 2-3. Bastion host 접속 ID 및 PW 확인하기 and click the Confirm button.
5-2. Install DB connection client program(Another Redis Desktop Manager) on the Bastion host
- Please download the Another Redis Desktop Manager program.
- Another Redis Desktop Manager program download URL: https://github.com/qishibo/AnotherRedisDesktopManager/releases
- Connect the user’s PC hard drive to upload the file to the Bastion host.
- In the Local Resources tab of the Remote Desktop Connection, click the Details button for the Local Devices and Resources item.
- Select the local disk where the file was downloaded on the drive, and click the OK button.
- Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install.
5-3. Connect to the database using the DB client program (Another Redis Desktop Manager)
- Run Another Redis Desktop Manager and click New Connection. The New Connection popup will appear.
- New Connection in the popup window, enter the Database server information created from 3-1. CacheStore(DBaaS) 서비스 생성하기 and click the OK button.
Required input field input value Host Database server IP Port Database Port Password Database password Connection Name Custom (ex. service name) Table.DB connection client program input fields - After connecting, you can check basic Redis information, manage data, and perform CRUD operations on keys.
6.3 - API Reference
6.4 - CLI Reference
6.5 - Release Note
CacheStore(DBaaS)
- We ensure stable service continuity through the Minor version upgrade feature.
- Add CacheStore (DBaaS) feature
- CacheStore(DBaaS) Add new image
- Support for the open-source Valkey image, developed by forking Redis OSS
- 2nd Generation Server Type Add
- Add a second-generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) processor. For details, see CacheStore(DBaaS) Server Type.
- Backup Notification Feature provided
- Provides notification functionality for backup success and failure. For more details, see Create Notification Policy.
- Add HDD, HDD_KMS types to Block Storage type
- CacheStore(DBaaS) Add new image
- Samsung Cloud Platform Common Feature Changes
- Account, IAM, Service Home, tags, and other common CX changes have been applied.
- Change the service name to CacheStore(DBaaS).
- A volume-encrypted storage selection option has been added to the Block Storage type.
- A Role Switch (Active ↔ Standby) feature for the Active DB and Standby DB configured with redundancy has been added.
- It is linked with the cloud monitoring service, enabling performance and log monitoring of DB instances.
- The Planned Compute policy can be configured according to the server type selected by the customer.
- A Redis (DBaaS) service that enables easy creation and management of Redis OSS in a web environment has been launched.
7 - Scalable DB(DBaaS)
7.1 - Overview
Service Overview
Scalable DB(DBaaS) is a database service designed to efficiently manage rapidly increasing data processing demands and user load.
Scalable DB (DBaaS) automatically scales resources up or down in response to traffic changes, maintaining optimal performance and availability. This maximizes resource efficiency and provides cost savings.
Additionally, the Proxy Endpoint configuration feature not only distributes database load by separating read/write and read‑only roles, but also enables more efficient independent connection management per application.
By combining these features, users can reduce the complexity of service operations and build a cost‑effective, scalable database environment.
Service Diagram
Provided features
Scalable DB(DBaaS) provides the following features.
- Auto Provisioning: Allows installation and configuration of the Database (DB) via UI, and provides an Active‑standby redundancy configuration built on storage replication. In case of an Active server failure, it automatically fails over to the Standby.
- Operation Control Management: Provides functionality to control the status of running servers. Offers start and stop functions for the entire cluster and restart buttons for each node, supporting a flexible cluster and node management environment for users.
- Scaling feature: Through the automatic scaling feature, read nodes are automatically expanded and contracted according to the policy set by the user. Additionally, users can manually adjust the number of nodes as needed.
- Proxy Endpoint configuration: By using the Proxy Endpoint feature that separates read/write and read‑only connections, it supports database connection optimization and traffic distribution.
- Backup: Provides data backup functionality based on its own backup command. Users can set the backup time window and storage repository, and additional fees are incurred based on backup size.
- Read Node status view: Provides real-time Read Node status view functionality, allowing monitoring of replication lag time (Replication Lag Time) to accurately determine data synchronization status.
- Service Status Query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, performance monitoring information can be viewed through Servicewatch.
Component
Scalable DB (DBaaS) provides pre‑validated engine versions and various server types in accordance with its open‑source support policy. Users can select and use them based on the scale of the service they wish to configure.
Engine version
The engine versions supported by Scalable DB (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.
The EOS and EoTS dates may change according to the supplier’s policy, so please refer to the supplier’s license management policy page for details.
- MariaDB(Commuity): https://mariadb.org/about/#maintenance-policy
| Provided version | EOS Date (Samsung Cloud Platform new creation stop date) | EoTS Date (Community technical support end date) |
|---|---|---|
| 10.11.13 | 2027-06 (planned) | 2028-02-16 |
Server Type
The server types supported by Scalable DB(DBaaS) are as follows.
For detailed information about the server types provided by Scalable DB (DBaaS), refer to Scalable DB(DBaaS) Server Types.
High Capacity sdbh2v24m48
Category | example | Detailed description |
|---|---|---|
| Server type | High Capacity | Provided server type classification |
| Server specifications | sdbh2 | Provided server type classification and generation
|
| Server specifications | v24 | Number of vCores
|
| Server specifications | m48 | Memory Capacity
|
Provision status by region
Scalable DB(DBaaS) is available in the following environments.
| region | Provision status |
|---|---|
| Korea West (kr-west1) | Provide |
| Korea East (kr-east1) | Not provided |
| South Korea 1 (kr-south1) | Provide |
| South Korea South 2 (kr-south2) | Not provided |
| South Korea 3 (kr-south3) | Not provided |
Preliminary Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
7.1.1 - Server Types
Scalable DB(DBaaS) server type
Scalable DB (DBaaS) offers server types configured with various combinations of CPU, memory, and network bandwidth. When creating a Scalable DB(DBaaS), the Database Engine is installed according to the server type selected for the intended use.
The server types supported by Scalable DB (DBaaS) are as follows.
High Capacity sdbh2v24m48
Category | example | Detailed description |
|---|---|---|
| Server type | High Capacity | Provided server type classification |
| Server specifications | sdbh2 | Provided server type classification and generation
|
| Server specifications | v24 | Number of vCores
|
| Server specifications | m48 | Memory Capacity
|
sdbh2 server type
The dbh2 server type of Scalable DB (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 128 vCPUs and 1,536 GB of memory
- Networking speed up to 25 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | sdbh2v24m48 | 24 vCore | 48 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v24m96 | 24 vCore | 96 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v24m192 | 24 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v24m288 | 24 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v32m64 | 32 vCore | 64 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v32m128 | 32 vCore | 128 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v32m256 | 32 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v32m384 | 32 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v48m192 | 48 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v48m576 | 48 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v64m256 | 64 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | sdbh2v64m768 | 64 vCore | 768 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v72m288 | 72 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v72m864 | 72 vCore | 864 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v96m384 | 96 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | sdbh2v96m1152 | 96 vCore | 1152 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v128m512 | 128 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | sdbh2v128m1536 | 128 vCore | 1536 GB | Maximum 25 Gbps |
7.1.2 - ServiceWatch Metrics
Scalable DB sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at a 1‑minute interval.
Basic Metrics
The following are the basic metrics for the namespace Scalable DB(DBaaS).
The indicators whose names are shown in bold below are the indicators selected as major indicators among the basic indicators provided by Scalable DB(DBaaS). Key metrics are used to build service dashboards that are automatically created for each service in ServiceWatch.
Each metric indicates through the user guide which statistical value is 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 these primary statistical values.
OS Basic Metrics
Category | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| CPU | CPU Usage | Percent | CPU usage |
|
| Disk | Disk Usage | Percent | Disk usage |
|
| Disk | Disk Write Bytes | Bytes/Second | Write bandwidth (bytes/second) on block device |
|
| Disk | Disk Read Bytes | Bytes/Second | Read capacity (bytes/second) from block device |
|
| Disk | Disk Write Requests | Count/Second | Number of write requests on block device (requests per second) |
|
| Disk | Disk Read Requests | Count/Second | Number of read requests on block device (requests per second) |
|
| Disk | Average Disk I/O Queue Size | None | Average queue length of requests issued to the block device |
|
| Disk | Disk I/O Utilization | Percent | Proportion of time the block device actually handled I/O operations |
|
| Memory | Memory Usage | Percent | Memory usage |
|
| Network | Network In Bytes | Bytes/Second | Received capacity (bytes/second) on the network interface |
|
| Network | Network Out Bytes | Bytes/Second | Transmitted capacity (bytes/second) on the network interface |
|
| Network | TCP Connections | Count/Second | Current total number of successfully established TCP connections |
|
| Network | Network In Packets | Count | Number of packets received on the network interface |
|
| Network | Network Out Packets | Count | Number of packets transmitted on the network interface |
|
| Network | Network In Dropped | Count | Number of packet drops received on the network interface |
|
| Network | Network Out Dropped | Count | Number of packet drops transmitted on the network interface |
|
| Network | Network In Errors | Count | Number of packet errors received on the network interface |
|
| Network | Network Out Errors | Count | Number of packet errors transmitted on the network interface |
|
Scalable DB Basic Metrics
Category | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| Activelock | Active locks | Count | Number of transactions in lock wait (Lock Wait) state for 1 minute (60 seconds) or longer in the InnoDB storage engine |
|
| Activesession | Active sessions | Count | Number of active sessions |
|
| Activesession | Connection usage | Percent | DB connection session usage rate |
|
| Activesession | Connections | Count | DB connection session |
|
| Activesession | Aborted Connections | Count/Minute | Number of abnormal terminated connections |
|
| Datafile | Current open files | Count | Number of file descriptors opened by the DB |
|
| Datafile | Max open files | Count | Maximum number of file descriptors the DB can open |
|
| Datafile | Open files usage | Percent | DB file maximum count utilization |
|
| InnoDB | InnoDB buffer pool hit ratio | Percent | The proportion of data read directly from memory without accessing the disk |
|
| InnoDB | Innodb row lock wait transactions | Count | Current number of InnoDB transactions waiting for a row lock |
|
| InnoDB | InnoDB row lock time | Milliseconds | Total time waited due to InnoDB row locks (in milliseconds) |
|
| InnoDB | InnoDB deadlocks | Count/Minute | Number of transactions rolled back due to deadlock |
|
| InnoDB | Table lock waits | Count/Minute | Number of waits that occurred to acquire a table lock |
|
| InnoDB | Temp disk tables | Count/Minute | Number of Temp Tables created on disk |
|
| InnoDB | Innodb log waits | Count | Number of times waited to write the redo log to disk |
|
| ProxySQL | Proxy Uptime | Seconds | Express the proxy’s uptime in seconds |
|
| ProxySQL | Backend connections(CONNECTED) | Count | Number of sessions connected to the Proxy server |
|
| ProxySQL | Client connections connected | Count | Number of client sessions currently connected to the proxy |
|
| ProxySQL | Queries routed | Count | Number of queries routed to the backend server |
|
| ProxySQL | Backend connections(ACTIVE, IDLE) | Count | Active / idle connection count per endpoint |
|
| ProxySQL | Backend server status | None | Backend server status
|
|
| ProxySQL | Backend conneciton check | Count | Backend server connection success/failure count | - |
| State | Instance state | None | Check Scalable DB status up/down
| - |
| State | Slave behind master seconds | Seconds | Replica latency (unit: seconds) |
|
| State | Slave io thread running (Replica Only) | None | I/O Thread status
| - |
| State | Slave SQL thread running (Replica Only) | None | SQL Thread status
| - |
| Tablespace | Tablespace used | Megabytes | Tablespace usage |
|
| Tablespace | Tablespace used(TOTAL) | Megabytes | Tablespace usage (total) |
|
| Transactions | Slow queries | Count | Number of queries running longer than 10 seconds |
|
| Transactions | Long transaction time | Seconds | Long Transaction time |
|
| Transactions | Wait locks | Count | Number of sessions waiting for lock |
|
| Transactions | SQL Queries/Minute | Count/Minute | Queries executed per minute |
|
7.2 - How-to guides
Users can create the service by entering the required information for Scalable DB (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
Create Scalable DB(DBaaS)
You can create and use the Scalable DB (DBaaS) service in the Samsung Cloud Platform Console.
Before creating the service, configure the VPC’s subnet type as General.
- If the subnet type is Local, the corresponding Database service cannot be created.
To create a Scalable DB (DBaaS), follow the steps below.
All Services > Database > Scalable DB(DBaaS) Click the menu. 1. Go to the Service Home page of Scalable DB (DBaaS).
On the Service Home page, click the Create Scalable DB (DBaaS) button. 2. Create Scalable DB (DBaaS) Navigate to the page.
On the Scalable DB(DBaaS) Creation page, enter the information required to create the service and select detailed options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version Required Provide version list of Scalable DB (DBaaS) Table. Scalable DB (DBaaS) Image and version selection items - Service Information Input (Primary Node) Enter or select the required information.
Category required statusDetailed description Server name Prefix Required Server name where the DB will be installed - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (
-) enter 3 - 13 characters
- Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name Required Cluster name of DB servers - Enter using English letters, 3 - 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type on which the DB will be installed - High Capacity: Large-capacity server with 24 vCores or more
- For detailed information about the server types provided by Scalable DB (DBaaS), refer to Scalable DB(DBaaS) 서버 타입.
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute Request
Service Type > Block Storage Required Block Storage settings used by the DB according to purpose - Base 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–5,120
- Because large sorts during SQL execution or monthly batch jobs can cause service interruptions, 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–5,120
- To add storage, click the Add button; to delete, click the x button. Up to 9 can be added
- Before transmitting backup data, temporarily store it in the BACKUP storage
- 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; the backup capacity is advised to be set at about 60 % of the DATA capacity
- If BACKUP storage is not added, using the
/tmparea is recommended
- For each service, Archive, TEMP, and BACKUP storages are allocated only one Block Storage each
- Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
Network > Common Settings Required Network settings for servers created by the service - Select when you want to apply the same settings to all installed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be generated automatically
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway; checking use allows you to select from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- When Use is checked, you can select a reserved IP from the VPC product’s Public IP. For more information, refer to Public IP 생성하기
IP access control Selection Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button.
- To delete an entered IP, click the x button next to the entered IP.
maintenance period Select Database maintenance window - If you select Use, set the day, 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.
Table. Scalable DB(DBaaS) Primary Node Service Information Input Items - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (
- Service Information Input (Read Node) Enter or select the required information in this area.
Category required statusDetailed description Read Node count Required Select the number of Read Nodes to create within the range 1 - 5 - The Host name is automatically assigned as a combination of the server name prefix + r + a three‑digit number (001 - 999) for each Node
Service Type > Server Type Required Server type on which the DB will be installed - High Capacity: large-capacity server with 24 vCores or more
- For detailed information about the server types provided by Scalable DB (DBaaS), refer to Scalable DB(DBaaS) 서버 타입.
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute 신청하기
Service Type > Block Storage Required Block Storage settings used by the DB according to purpose - Base 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–5,120
- Because large sorts during SQL execution or monthly batch jobs can cause service interruptions, 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 the capacity can be entered as a multiple of 8 within the range 16–5,120
- To add storage, click the Add button; to delete, click the x button. Up to 9 can be added
- Before transmitting backup data, temporarily store it in the BACKUP storage
- 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; the backup capacity is advised to be set at about 60 % of the DATA capacity.
- If a BACKUP storage is not added, using the
/tmparea is recommended
- For each service, Archive, TEMP, and BACKUP storages are allocated only one Block Storage each
- Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
Network > Common Settings Required Network settings for servers created by the service - Select when you want to apply the same configuration to all installed servers
- Automatically apply the same as the Primary Node configuration items
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Automatically applied same as the Primary Node configuration items, IP information can be entered manually
Scaling Policy Settings > Node Count Required Enter the number of Read Nodes referenced commonly by both Auto Scaling and Manual Scaling - Min: Enter the minimum number of nodes to maintain based on the scaling policy, within the range 1 - 5
- Max: Enter the maximum number of nodes to maintain based on the scaling policy, within the range 1 - 5
Scaling policy configuration > Auto Scale-out policy option Auto Scale-out policy detailed settings - Use after selecting, set the detailed items of the execution condition of the Auto Scale-out policy
- Enter the wait time for the Cooldown item, after the scaling operation by the policy is completed, before restarting the scaling operation, enter the wait time within the range 60 – 3,600
Scaling Policy Settings > Auto Scale-in Policy option Auto Scale-in policy detailed settings - After selecting Use, configure the detailed items of the execution condition of the Auto Scale-out policy
- Enter the wait time for the Cooldown item; after the scaling operation by the policy is completed, input the wait time within the range of 60 – 3,600 before restarting the scaling operation
Table. Scalable DB (DBaaS) Read Node Service Information Input Items - Enter or select the required information in the Proxy Service Information Input area.
Category required statusDetailed description Proxy Endpoint Settings > Read Endpoint Port Required Set the port to connect to the Read Node that handles read requests - The port cannot be the same as the Database Port and must be entered within the range 1200 - 65535
Proxy Endpoint Settings > Write Endpoint Port Required Set the Port to connect to the Primary Node that will handle write requests - The port cannot be the same as the Database Port and must be entered within the range 1200 - 65535
Proxy Endpoint Settings > Connection Idle Time Required Enter the idle time in milliseconds (ms) before automatically terminating a client connection with no request - Enter a value within the range 0 - 1,728,000,000
Proxy Endpoint Settings > Read Connection Count Required Set the maximum number of connections that a Proxy can create simultaneously with a Read Node - Enter within the range 10 - 100,000
Proxy Endpoint Settings > Write Connection Count Required Set the maximum number of connections that a Proxy can create simultaneously with the Primary Node - Enter within the range 10 - 100,000
Proxy Endpoint Settings > Lagging Time Required Set the Replication delay time allowed for the Read Node - Enter a value in the range 0 - 126,144,000
Table. Scalable DB (DBaaS) Proxy Service Information Input Items - In the Enter required database configuration information area, enter or select the necessary information.
Category required statusDetailed description Database name Required Server name applied during DB installation - must start with an English letter and be entered using English letters and numbers, 3 - 20 characters long
Database username Required DB user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Restricted database user names can be viewed in the Console
Database password Required Password to use when accessing the DB - Enter 8 - 30 characters including letters, numbers, and special characters (excluding
“‘)
Database password verification Required Re-enter the same password to use for DB access Database Port number Required Port number required for DB connection - Enter the DB port within the range 1200 ~ 65535
Backup > Use Selection Backup usage - Select Use to set backup file retention period, backup start time, and Archive backup interval
Backup > Retention Period Selection Backup retention period - Select the backup retention period, set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Time Selection Backup start time - Select backup start time
- The minutes during which the backup runs (minutes) are set randomly, and the backup end time cannot be set
Backup > Archive backup cycle Selection Archive backup interval - Select the archive backup interval
- The archive backup interval is recommended to be 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
Parameter Required Parameters to be used in the DB - Query button can be clicked to view detailed information of the parameters
DB character set Required Set the DB character set appropriate for the characters (language) to be used in the DB - The DB is created with the selected character set as the default
time zone Required Standard time zone for the database ServiceWatch log collection Selection ServiceWatch log collection status - use to enable the ServiceWatch log collection feature
- For detailed information about the collected logs, see ServiceWatch 지표
- 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 cannot be deleted until the resources are removed
- To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
Table. Essential items for configuring a Scalable DB (DBaaS) database - In the Additional Information Input area, enter or select the required information.
Category required statusDetailed description tag Selection Add Tag - Up to 50 per resource can be added
- After clicking the Add Tag button, enter or select Key, Value values
Table. Scalable DB (DBaaS) additional information input fields
- Select the required information in the Image and version selection area.
Summary panel, check the detailed information and estimated charges generated, and click the Create button.
- Once creation is complete, check the created resource on the Resource List page.
Scalable DB(DBaaS) View detailed information
The Scalable DB (DBaaS) service allows you to view and edit the full list of resources and detailed information. Scalable DB (DBaaS) Details page consists of Details, Read Node Status View, Auto Scaling Policy, Tags, Operation History tabs.
To view detailed information about the Scalable DB (DBaaS) service, follow these steps.
- All Services > Database > Scalable DB(DBaaS) Click the menu. 1. Go to the Service Home page of Scalable DB (DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Navigate to the Scalable DB(DBaaS) List page.
- On the Scalable DB(DBaaS) List page, click the resource to view detailed information. 3. Scalable DB(DBaaS) Details Navigate to the page.
- Scalable DB(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Creating cluster
- Editing: Cluster is transitioning to an operational state
- Error: Cluster encountered an error during operation
- If it occurs continuously, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Restarting cluster
- Running: Cluster is running normally
- Starting: Starting cluster
- Stopped: Cluster is stopped
- Stopping: Cluster is stopping
- Synchronizing: Synchronizing cluster
- Terminating: Terminating cluster
- Unknown: Unknown cluster status
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is upgrading
Cluster control Button to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
View more features Cluster-related management buttons - Service status synchronization: Retrieve real-time DB service status
- Backup history: When backup is configured, verify successful execution and view the history
- Add node: Add a Read Node to the DB; for detailed instructions on adding nodes, see 노드 추가하기
- Delete node: Delete a Read Node from the DB; for detailed instructions on deleting nodes, see 노드 삭제하기
- Proxy Endpoint configuration management: View and modify Proxy Endpoint settings; for detailed instructions on node deletion, see Proxy Endpoint 설정 관리하기
Service termination Button to cancel the service Table. Scalable DB (DBaaS) status information and additional features
- Scalable DB(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
Detailed Information
Scalable DB (DBaaS) List page allows you to view detailed information of the selected resource and edit the information if needed.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster name | Cluster name of the DB servers |
| Read Endpoint Port | Port connected to the Read Node that handles read requests |
| Write Endpoint Port | Port connected to the Primary Node that handles write requests |
| Database name | Server name applied during DB installation |
| Database username | DB user name |
| Planned Compute | Resources with Planned Compute configured
|
| maintenance period | DB patch work period setting status
|
| Backup | Backup configuration status
|
| DB character set | Character set to use for the DB |
| ServiceWatch log collection | ServiceWatch Log Collection Configuration Status
|
| Scailing policy node count | Scailing policy node count configuration status
|
| time zone | Standard time zone for the database |
| Network | Network information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP access control | Service access policy configuration
|
| Resource Management (Primary) | Primary Node configuration information for the DB server |
| Resource Management (Read Node) | Read Node configuration information for the DB server |
Read Node status query
Read Node Status View tab allows the user to view the server status and replication status of the configured Read Node. For detailed information, please refer to Read Node Status Query.
Auto Scaling policy
The Auto Scaling policy tab lets you add, modify, and delete Auto Scaling policies to manage the automatic scaling and shrinking of Read Nodes. For more details, please refer to Auto Scaling 정책 설정하기.
Tag
Scalable DB (DBaaS) List page allows you to view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Job History
Scalable DB(DBaaS) List page lets you view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Managing Scalable DB (DBaaS) Resources
If you need to manage the created Scalable DB (DBaaS) resources, you can perform the tasks on the Scalable DB(DBaaS) Details page.
Control Operation
If a change occurs to a running Scalable DB (DBaaS) resource, you can start or stop it.
To control the operation of Scalable DB(DBaaS), follow the steps below.
- Click the All Services > Database > Scalable DB(DBaaS) menu. 1. Go to the Service Home page of Scalable DB (DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Scalable DB(DBaaS) List Go to the page.
- Scalable DB(DBaaS) List Click the resource you want to control on the page. 3. Scalable DB(DBaaS) Details Navigate to the page.
- Check the status of Scalable DB (DBaaS) 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.
Synchronize Service Status
You can synchronize the real-time service status of Scalable DB (DBaaS).
To view and synchronize the service status of Scalable DB (DBaaS), follow the steps below.
- All Services > Database > Scalable DB (DBaaS) Click the menu. 1. Navigate to the Service Home page of Scalable DB (DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Scalable DB(DBaaS) List Navigate to the page.
- Scalable DB(DBaaS) List Click the resource on the page to view the service status. 3. Scalable DB(DBaaS) Details Navigate to the page.
- Service Status Sync Click the button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.
Managing Proxy Endpoint Settings
You can modify the Proxy Endpoint settings of Scalable DB (DBaaS).
To modify the Proxy Endpoint settings of Scalable DB (DBaaS), follow the steps below.
- All Services > Database > Scalable DB(DBaaS) Click the menu. 1. Navigate to the Service Home page of Scalable DB (DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Go to the Scalable DB (DBaaS) List page.
- Scalable DB(DBaaS) List Click the resource on the page to view the service status. 3. Scalable DB(DBaaS) Details Navigate to the page.
- In the add-on menu, click the Proxy Endpoint Settings Management button. 4. Proxy Endpoint Settings Management Navigate to the page.
- On the Proxy Endpoint Settings Management page, click the Search button. 5. Next, when the query alert appears, click the Confirm button.
- On the Proxy Endpoint Settings Management page, click the Edit button. 6. Go to the Proxy Endpoint Settings Edit page.
- On the Edit Proxy Endpoint Settings page, after modifying the desired items, click the Done button.
Scalable DB(DBaaS) Terminate
You can reduce operating costs by terminating unused Scalable DB (DBaaS). Note that terminating the service may cause the currently operating service to stop immediately, so you should proceed with the termination only after fully considering the impact of a service interruption.
- For a DB with a Replica configured, terminating the Master DB does not delete the Replica. * If you delete the replica as well, 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 Scalable DB(DBaaS), follow the steps below.
- Click the All Services > Database > Scalable DB(DBaaS) menu. 1. Go to the Service Home page of Scalable DB (DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Scalable DB(DBaaS) List Navigate to the page.
- On the Scalable DB(DBaaS) List page, select the resource to cancel and click the Cancel Service button.
- After termination is complete, check whether the resource has been terminated on the Scalable DB(DBaaS) list page.
7.2.1 - Read Node Manage
Users can manage Read Node through the Samsung Cloud Platform Console.
Read Node status query
Users can view the server status and replication status of the Read Node via the Read Node Status View tab.
To view the Read Node status of the Scalable DB (DBaaS) service, follow these steps.
- Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. You will be taken to the Scalable DB(DBaaS) List page.
- Click the resource to view detailed information on the Scalable DB(DBaaS) List page. You will be taken to the Scalable DB(DBaaS) Details page.
- On the Scalable DB(DBaaS) Details page, click the Read Node Status tab.
- On the Read Node status query page, click the Status Query button.
- When the alert window appears, click the Confirm button. The query results will be displayed in the Read Node status list.
| Category | Detailed description |
|---|---|
| Read Node status | Read Node server status
|
Configure Auto Scaling Policy
Users can add, modify, and delete Auto Scaling policies through the Auto Scalinng policy tab to manage the automatic scaling and shrinking of Read Nodes. Based on CPU utilization metrics, you can set the minimum and maximum number of Read Nodes, allowing flexible adjustment according to workload changes.
Add Auto Scaling policy
The Scailing policy allows only one policy each for Scale In and Scale Out.
- If a pre‑created policy already exists, it cannot be added.
To add an Auto Scaling policy to the Scalable DB (DBaaS) service, follow these steps.
- Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. You will be taken to the Scalable DB(DBaaS) List page.
- Scalable DB(DBaaS) List Click the resource on the page to view detailed information. Scalable DB(DBaaS) Details You will be taken to the page.
- On the Scalable DB(DBaaS) Detail page, click the Auto Scaling Policy tab.
- On the Auto Scaling policy page, click the Add Policy button.
- When the policy addition window appears, click the Scale policy tab to create it.
- If a pre‑created Scale policy exists, that tab is disabled and cannot be selected.
- Set the detailed items of the selected Scale policy and click the Confirm button.
- The added Scale policy is displayed in the list.
Modify Auto Scaling policy
Follow these steps to modify the Auto Scaling policy of the Scalable DB(DBaaS) service.
- Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. You will be taken to the Scalable DB(DBaaS) List page.
- Click the resource to view detailed information on the Scalable DB(DBaaS) List page. You will be taken to the Scalable DB(DBaaS) Details page.
- On the Scalable DB(DBaaS) Details page, click the Auto Scaling Policy tab.
- On the Auto Scaling policy page, click the Edit button for the policy you want to modify.
- When the policy edit window appears, modify the desired information and click the Confirm button.
Delete Auto Scaling policy
To delete the Auto Scaling policy of the Scalable DB (DBaaS) service, follow the steps below.
- Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
- Click the Scalable DB(DBaaS) menu on the Service Home page. You will be taken to the Scalable DB(DBaaS) List page.
- Click the resource to view detailed information on the Scalable DB(DBaaS) List page. You will be taken to the Scalable DB(DBaaS) Details page.
- On the Scalable DB(DBaaS) Details page, click the Auto Scaling Policy tab.
- On the Auto Scaling policy page, select the policy to delete and click the Delete button.
- When the policy deletion is complete, it disappears from the list.
Add Read Node
When creating a Scalable DB(DBaaS) service, you can add a Read Node under the same conditions as the Primary Node settings you configured.
- You can add nodes only when the cluster status is Running.
- When creating a Scalable DB (DBaaS) service, you cannot add nodes if the configured maximum number of nodes has been reached.
- If there is a Failed Node among the existing Read Nodes, you cannot add a node. Delete the Failed Node and then add the node again.
To add a Read Node to the Scalable DB (DBaaS) service, follow the steps below.
- Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
- Click the Scalable DB(DBaaS) menu on the Service Home page. You will be taken to the Scalable DB(DBaaS) List page.
- Click the resource to view detailed information on the Scalable DB(DBaaS) List page. You will be taken to the Scalable DB(DBaaS) Details page.
- On the Scalable DB(DBaaS) Details page, click Additional Functions > Add Node. You will be taken to the Add Read Node page.
- Add Read Node Check the specifications on the page and click the Complete button.
- If you need to assign an IP for the Read Node, please enter the IP in the Network > Server-specific Settings > IP field.
Delete Read Node
You can delete the Read Node of the Scalable DB (DBaaS) service.
- Nodes can be deleted only when the cluster status is Running.
- If you delete a node and the remaining number of nodes is less than the configured minimum, you cannot delete the node.
To delete the Read Node of the Scalable DB (DBaaS) service, follow the steps below.
- Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
- Click the Scalable DB(DBaaS) menu on the Service Home page. Navigate to the Scalable DB(DBaaS) List page.
- Scalable DB(DBaaS) List Click the resource to view detailed information. Scalable DB(DBaaS) Details You will be taken to the page.
- Scalable DB(DBaaS) Details on the page, click Additional Functions > Delete Node.
- When the Delete dialog for Read Node appears, select the items to delete and click the Delete button.
- When the alert window appears, enter the name of the node to delete and click the Confirm button.
- Read Node In the delete dialog, verify that the selected node has been removed from the node list, and click the Confirm button.
7.2.2 - Backup DB
Users can configure backups of Scalable DB (DBaaS) through the Samsung Cloud Platform Console.
Scalable DB(DBaaS) Backup
Scalable DB (DBaaS) provides data backup functionality based on its own backup commands. Additionally, it provides a backup environment optimized for data protection and management through backup history verification and backup file deletion functions.
Configure backup
Refer to Scalable DB(DBaaS) 생성하기 for backup configuration of Scalable DB (DBaaS).
To modify the backup settings of the created resource, follow the steps below.
- For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity.
- Especially when the backup data exceeds 100 GB and undergoes frequent changes, please provision additional storage amounting to approximately 60 % of the data size.
- If a backup is configured, it will run at the designated time after the set time, and additional fees will apply based on the backup size.
- If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
To set up a backup, follow these steps.
- All Services > Database > Scalable DB(DBaaS) Click the menu. 1. Go to the Service Home page of Scalable DB (DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Scalable DB(DBaaS) List Navigate to the page.
- Scalable DB(DBaaS) List On the page, click the resource to configure backup. 3. Scalable DB(DBaaS) Details Navigate to the page.
- Click the Edit button for the backup item. 4. Backup Settings popup window opens.
- When configuring a backup, click Use in the Backup Settings popup, select the retention period, backup start time, and Archive backup cycle, then click the Confirm button.
- If you wish to stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Once user authentication is complete, the backup configuration is disabled and backup execution stops.
- If you wish to stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Check backup history
To view the backup history, follow these steps.
- Click the All Services > Database > Scalable DB(DBaaS) menu. 1. Navigate to the Service Home page of Scalable DB (DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Scalable DB(DBaaS) List Go to the page.
- Scalable DB(DBaaS) List page: click the resource to view the backup history. 3. Scalable DB(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
- Click the All Services > Database > Scalable DB (DBaaS) menu. 1. Navigate to the Service Home page of Scalable DB (DBaaS).
- On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Scalable DB (DBaaS) List Go to the page.
- Scalable DB(DBaaS) List On the page, click the resource to view the backup history. 3. Scalable DB(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, check the files you want to delete, then authenticate via the logged-in user’s mobile phone.
- When user authentication is completed, the backup file is deleted.
7.3 - Release Note
Scalable DB(DBaaS)
- You can monitor logs by integrating with Servicewatch.
- The fully managed Database service, Scalable DB (DBaaS), which flexibly adjusts resources according to traffic changes, has been launched.











