This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Database

We provide a service that easily creates and manages relational, unstructured, and analytical databases in a web environment.

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.

Architecture
Figure. EPAS (DBaaS) Architecture

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 versionEOS Date (Samsung Cloud Platform new creation stop date)EoTS Date (Community technical support end date)
14.172026-05-202026-12-01
14.182026-05-202026-12-01
14.192026-05-202026-12-01
15.122027-09 (planned)2028-02-13
15.132027-09 (planned)2028-02-13
15.142027-09 (planned)2028-02-13
16.82028-06 (planned)2028-11-09
16.92028-06 (planned)2028-11-09
16.102028-06 (planned)2028-11-09
17.62029-06 (planned)2029-11-08
Table. Engine versions provided by EPAS (DBaaS)
information

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
CategoryExampleDetailed description
Server typeStandardProvided server types
  • Standard: Standard configuration (vCPU, Memory) commonly used
  • High Capacity: Large server specifications of 24 vCores or more
Server specificationsdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) commonly used
  • dbh2: Large-capacity server specifications
    • Provides servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. EPAS (DBaaS) server type components

Preceding Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

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

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
exampleDetailed description
Server typeStandardProvided server type classifications
  • Standard: Configured with the commonly used standard specifications (vCPU, Memory)
  • High Capacity: Large-capacity server specifications exceeding Standard
Server specificationsdb1Provided server type classification and generation
  • db1: indicates a standard specification, and 1 denotes the generation
  • dbh2: h indicates a high-capacity server specification, and 2 denotes the generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. EPAS (DBaaS) server type format

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. EPAS (DBaaS) server type specifications - db1 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb2v2m42 vCore4 GBUp to 10 Gbps
Standarddb2v2m82 vCore8 GBUp to 10 Gbps
Standarddb2v2m162 vCore16 GBUp to 10 Gbps
Standarddb2v2m242 vCore24 GBUp to 10 Gbps
Standarddb2v2m322 vCore32 GBUp to 10 Gbps
Standarddb2v4m84 vCore8 GBUp to 10 Gbps
Standarddb2v4m164 vCore16 GBUp to 10 Gbps
Standarddb2v4m324 vCore32 GBUp to 10 Gbps
Standarddb2v4m484 vCore48 GBUp to 10 Gbps
Standarddb2v4m644 vCore64 GBUp to 10 Gbps
Standarddb2v6m126 vCore12 GBUp to 10 Gbps
Standarddb2v6m246 vCore24 GBUp to 10 Gbps
Standarddb2v6m486 vCore48 GBUp to 10 Gbps
Standarddb2v6m726 vCore72 GBUp to 10 Gbps
Standarddb2v6m966 vCore96 GBUp to 10 Gbps
Standarddb2v8m168 vCore16 GBUp to 10 Gbps
Standarddb2v8m328 vCore32 GBUp to 10 Gbps
Standarddb2v8m648 vCore64 GBUp to 10 Gbps
Standarddb2v8m968 vCore96 GBUp to 10 Gbps
Standarddb2v8m1288 vCore128 GBUp to 10 Gbps
Standarddb2v10m2010 vCore20 GBUp to 10 Gbps
Standarddb2v10m4010 vCore40 GBUp to 10 Gbps
Standarddb2v10m8010 vCore80 GBUp to 10 Gbps
Standarddb2v10m12010 vCore120 GBUp to 10 Gbps
Standarddb2v10m16010 vCore160 GBUp to 10 Gbps
Standarddb2v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb2v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb2v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb2v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb2v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb2v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb2v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb2v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb2v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb2v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb2v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb2v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb2v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb2v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. EPAS (DBaaS) server type specifications - db2 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBMaximum 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBMaximum 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBUp to 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBMaximum 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBMaximum 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBMaximum 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBMaximum 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBMaximum 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBUp to 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBMaximum 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBMaximum 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBMaximum 25 Gbps
Table. EPAS (DBaaS) server type specifications - dbh2 server type

1.1.2 - Monitoring metrics

Cloud Monitoring Service Termination Notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service, which was released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Services by Resource

    • New Resources: Resources created after the service improvement work in 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.
  2. 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.
  • 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**.

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 itemsDetailed descriptionunit
Active Locks [Access Exclusive]Number of Access Exclusive Lockscnt
Active Locks [Access Share]Number of Access Share Lockscnt
Active LocksNumber of Active Lockscnt
Active Locks [Total]Total number of active lockscnt
Active SessionsNumber of Sessions in Active statecnt
Active Sessions [Total]Total number of Sessions in Active statecnt
Apply Lag TimeApply lag timemin
Check No ReplicationCheck No Replication valuecnt
Check ReplicationCheck Replication Status valuestatus
Connection UsageDB connection usage rate (%)%
Connection Usage [Total]DB connection usage rate (%)%
DB Age MaxDatabase age (frozen XID) valueage
Exclusive LocksNumber of Exclusive Lockscnt
Idle In Transaction SessionsNumber of sessions in Idle in transaction statecnt
Idle In Transaction Sessions [Total]Total number of sessions in idle in transaction statecnt
Idle SessionsNumber of idle sessionscnt
Idle Sessions [Total]Total number of idle sessionscnt
Row Exclusive LocksNumber of Row Exclusive Lockscnt
Row Share LocksRow Share Locks countcnt
Share LocksNumber of Share Lockscnt
Share Row Exclusive LocksNumber of Share Row Exclusive Lockscnt
Share Update Exclusive LocksNumber of Share Update Exclusive Lockscnt
SlowqueriesNumber of SQL queries running for a long time (over 5 minutes)cnt
Tablespace UsedTable space sizebytes
Tablespace Used [Total]Table space sizebytes
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 LocksNumber 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 lockcnt
Wait Locks [Total]Total number of sessions waiting due to lock occurrencecnt
Waiting SessionsNumber of Sessions in Waiting statecnt
Waiting Sessions [Total]Total number of Sessions in Waiting statecnt
Table. EPAS (DBaaS) Monitoring Metrics

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.

Cloud Monitoring Service Termination Notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Service per Resource

    • New Resources: Resources created after the 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.
  2. Notice of the phased termination schedule for Cloud Monitoring service

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch is available in the ServiceWatch 개요.

Create EPAS (DBaaS)

You can create and use the EPAS (DBaaS) service in the Samsung Cloud Platform Console.

Information
  • Before creating the service, configure the VPC’s subnet type as General.
    • If the subnet type is Local, the 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.

  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Navigate to the Service Home page of EPAS (DBaaS).

  2. On the Service Home page, click the Create EPAS (DBaaS) button. 2. Go to the EPAS(DBaaS) Create page.

  3. 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 status
      Detailed description
      Image versionRequiredProvide 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 status
      Detailed description
      Server name PrefixRequiredServer 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 namerequiredCluster name composed of DB servers
      • Enter using English letters, 3 ~ 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type for DB installation
      • Standard: Standard specification commonly used
      • High Capacity: Large-capacity server with 24 vCores or more
      Service Type > Planned ComputeSelectStatus 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
      Service Type > Block StorageRequiredBlock 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 /tmp area is used, and backup fails if capacity is insufficient
          • For each service, Archive, TEMP, and BACKUP storages are allocated only one Block Storage each
      Redundancy configurationSelectionRedundancy configuration status
      • When redundancy configuration is used, the DB instance is set up as an Active DB and a Standby DB
      Network > Common SettingsEssentialNetwork 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 SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select when you want to apply different settings for each installed server
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • Enter the IP for each server
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. 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 controlSelectService Access Policy Configuration
      • Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
      • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      maintenance periodSelectDatabase maintenance window
      • If you select Use, set the day of 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
    • Enter required database configuration information Enter or select the required information in this area.
      Category
      required status
      Detailed description
      Database nameRequiredServer name applied during DB installation
      • must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
      Database usernameRequiredDatabase user name
      • An account with the same name is also created on the OS
      • Enter using lowercase English letters, 2 to 20 characters
      • Restricted database user names can be viewed in the Console
      Database passwordRequiredPassword to use when accessing the DB
      • Enter 8 to 30 characters, including letters, numbers, and special characters (excluding )
      Database password verificationEssentialRe-enter the same password to use for DB access
      Database Port numberRequiredPort number required for DB connection
      • Enter DB port within the range 1200 ~ 65535
      Backup > UseSelectBackup usage
      • Select Use to set backup file retention period, backup start time, and Archive backup interval
      Backup > Retention PeriodSelectBackup retention period
      • Select the backup retention period. Set the file retention period from 7 days to 35 days
      • Backup files incur additional charges based on size
      Backup > Backup Start PeriodSelectionBackup 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 cycleSelectArchive 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 SettingsSelectWhether 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_statement parameter, and can modify it through the Parameter screen
      • Enabling Audit may degrade database performance
      ParameterEssentialDB 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 EncodingRequiredCharacter 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 LocaleRequiredLocale 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 zoneRequiredStandard time zone for the database
      LicenseRequiredEPAS 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 status
      Detailed description
      TagSelectAdd 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
  4. 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.

  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
  3. 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.
      CategoryDetailed description
      Cluster statusCluster 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 controlButton to change the cluster state
      • Start: Start a stopped cluster
      • Stop: Stop a running cluster
      • Restart: Restart a running cluster
      • Switch-Over: Switch a standby cluster to active
      More featuresCluster Management Buttons
      • Service Status Synchronization: Real-time DB service status lookup
      • Backup History: When backup is configured, verify 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 terminationCancel service button
      Table. EPAS (DBaaS) status information and additional features

Detailed information

On the EPAS (DBaaS) List page, you can view detailed information of the selected resource and edit the information if needed.

CategoryDetailed description
Server InformationServer information configured in this cluster
  • Category: Server type (Active, Standby, Replica)
  • Server Name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
ServiceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the DB service, it refers to the cluster SRN
Resource NameResource name
  • In the DB service, it refers to the cluster name
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation date and timeService creation date and time
ModifierUser who edited the service information
Modification dateDate and time the service information was modified
Image versionInstalled DB image and version information
  • If a version upgrade is required, click the Edit icon to configure
Cluster typeCluster types (Master Cluster, Replica Cluster, Migration Cluster)
Cluster nameCluster name of the DB servers
Master cluster nameReplica’s Master cluster name
  • If it is detailed information of the Replica, it can be confirmed
Database nameServer name applied during DB installation
Database usernameDB user name
Planned ComputeResource status with Planned Compute configured
maintenance periodDB Maintenance Period Status
  • If you need to set the maintenance period, click the Edit icon to configure
BackupBackup configuration status
  • If backup configuration is required, click the Edit icon to set it
Audit Log SettingsAudit Log configuration status
  • If you need to configure Audit Log, click the Edit icon to set it up
time zoneStandard time zone for the database
DB LocaleLocale to use in the DB
Database EncodingCharacter encoding to use for the DB
VIPVirtual IP information
  • can be checked only when high availability is configured
NetworkNetwork information of the DB installation (VPC, Subnet, VIP, NAT IP(VIP))
IP access controlService access policy configuration
  • If you need to add or delete an IP, click the Edit icon to configure
Active & StandbyActive/Standby server type, base OS, additional Disk information
  • If you need to modify the server type, click the Edit icon next to the server type to configure it. Refer to the server type modification procedure in 서버 타입 변경하기
    • Modifying the server type requires a server reboot
  • If you need to expand storage, click the Edit icon next to the storage capacity to expand it. Refer to the storage expansion procedure in 스토리지 증설하기
  • If you need to add storage, click the Add Disk button next to the additional Disk to add it. Refer to the storage addition procedure in 스토리지 추가하기
Table. EPAS (DBaaS) Database detailed information items

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.

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

tag

EPAS (DBaaS) List page lets you view, add, modify, or delete tag information for the selected resource.

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

Work History

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

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

Managing 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.

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

  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
  3. 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.
  4. Service Status Synchronization Click the button. 4. While it is being queried, the cluster changes to Synchronizing state.
  5. When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.

Change server type

You can change the configured server type.

To change the server type, follow these steps.

Caution
If you modify the server type, a server restart is required. Please separately verify any software license modifications or software settings and their implementation due to server specification changes.
  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. Navigate to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) List page, click the resource whose server type you want to change. 3. Go to the EPAS(DBaaS) Details page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
  5. 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.

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

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.

  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) List page, click the resource for which you want to change the server type. 3. EPAS(DBaaS) Details Navigate to the page.
  4. Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
  5. Edit Additional Storage In the popup window, after entering the 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.

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

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

  1. Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the EPAS(DBaaS) Service Home page.
  2. On the Service Home page, click the EPAS(DBaaS) menu. You will be taken to the EPAS(DBaaS) List page.
  3. 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.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
  5. In the Parameter Management popup, click the Search button. The Search Notification popup opens.
  6. Lookup Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.

Parameter Modify

To modify the configuration parameters, follow the steps below.

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

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

  1. Click the All Services > Database > EPAS(DBaaS) menu. Go to the Service Home page of EPAS(DBaaS).
  2. Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) List page, click the resource whose DB user you want to modify. You will be taken to the EPAS(DBaaS) Details page.
  4. Click the More button, then click the DB User Management button. You will be directed to the DB User Management page.
  5. On the DB User Management page, click the Search button. Retrieving may take a short time.
  6. If modification is needed, click the Edit button, and change the status field value or enter remarks.
  7. When the input is complete, click the Complete button.

Managing DB Access Control

Provides IP-based DB user access control management functionality. Users can directly specify the IPs that can access the database, configuring it so that only authorized IPs are allowed access.

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

View DB Access Control

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

  1. Click the All Services > Database > EPAS(DBaaS) menu. Proceed to the Service Home page of EPAS(DBaaS).
  2. Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
  3. 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.
  4. Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. On the DB Access Control Management page, click the Search button. Retrieving the data may take a moment.

Add DB access control

To add IP access control, follow these steps.

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

Delete DB access control

To delete IP access control, follow these steps.

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

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

Configure Archive mode

To set the Archive mode, follow these steps.

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

Delete Archive file

To delete the Archive file, follow these steps.

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

  1. Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the EPAS(DBaaS) Service Home page.
  2. Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) List page, click the resource whose service status you want to view. You will be taken to the EPAS(DBaaS) Details page.
  4. Click the Edit icon of Audit Settings at the bottom of the detailed information. The Edit Audit Settings popup window opens.
  5. 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.

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

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

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

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

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

information
For detailed Migration configuration guidance, please refer to Architecture Center > Migration Guide.

To configure Migration, follow these steps.

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

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

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

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

Caution
  • The service will be unavailable while the OS upgrade is in progress.
  • The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
  • After the upgrade is complete, you cannot revert to the previous OS.

To upgrade the OS Kernel, follow the steps below.

  1. Click the All Services > Database > EPAS(DBaaS) menu. Navigate to the EPAS(DBaaS) Service Home page.
  2. Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
  3. On the EPAS(DBaaS) List page, click the resource to upgrade the OS Kernel. You will be taken to the EPAS(DBaaS) Detail page.
  4. Click the More button, then click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup opens.
  5. OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.

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.

Caution
  • For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity. * Especially when the backup data exceeds 100 GB and undergoes frequent changes, please 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.

  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) List page: click the resource for which you want to configure a backup. 3. EPAS(DBaaS) Details page is accessed.
  4. Click the Edit button of the backup item. 4. Backup Settings popup window opens.
  5. When configuring a backup, click Enable in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
    • If you 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.

Check backup history

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

To view the backup history, follow these steps.

  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) List page, click the resource to view the backup history. 3. Go to the EPAS(DBaaS) Details page.
  4. Click the Backup History button. 4. The Backup History popup opens.
  5. Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.

Delete backup file

To delete the backup history, follow these steps.

Caution
Backup files cannot be restored after deletion. Please be sure to verify whether the data is unnecessary before deleting it.
  1. All Services > Database > EPAS(DBaaS) menu, click it. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
  3. On the EPAS(DBaaS) List page, click the resource to view its backup history. 3. Go to the EPAS(DBaaS) Details page.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
    • When user authentication is completed, the backup file is deleted.

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.

Caution
To perform recovery, you need at least a capacity equal to the Disk data type size. If there is insufficient disk space, the recovery may fail.

To restore EPAS (DBaaS), follow the steps below.

  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
  3. EPAS(DBaaS) resources On the list page, click the resource you want to restore. 3. Navigate to the EPAS(DBaaS) Details page.
  4. Click the Database Recovery button. 4. Database Recovery Navigate to the page.
  5. After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
    Category
    required status
    Detailed description
    Recovery TypeRequiredSet the point in time the user wants to recover
    • Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
    • Custom point: Recover to a user‑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 prefixRequiredRecovery 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 nameRequiredRecovery DB cluster name
    • Enter using English letters, 3 to 20 characters
    • A cluster is a unit that groups multiple servers
    Service Type > Server TypeEssentialRecovery DB server type
    • Standard: Standard specification commonly used
    • High Capacity: Large-capacity server with 24 vCores or more
    Service Type > Planned ComputeSelectionStatus of resources with Planned Compute configured
    • In Use: Number of resources with Planned Compute configured that are currently in use
    • Configured: Number of resources with Planned Compute configured
    • Coverage Preview: Amount applied per resource by Planned Compute
    • Create Planned Compute Service: Navigate to the Planned Compute service application page
    Service Type > Block StorageRequiredBlock Storage settings used by the recovery DB
    • Basic OS: Area where the DB engine is installed
    • DATA: Storage area for table data, archive files, etc.
      • Applied identically with the storage type set in the 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 usernameRequiredDatabase username
    • Apply the same username set in the original cluster
    Database Port numberRequiredDatabase Port number
    • Apply the same Port number configured in the original cluster
    IP access controlSelectService Access Policy Configuration
    • Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
    • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
    • To delete an entered IP, click the x button next to the entered IP
    maintenance periodSelectDatabase maintenance window
    • If you select Use, set the day of week, start time, and duration
    • It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
    • If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
    tagSelectAdd 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.

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

To configure a Replica, follow these steps.

  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. Go to the EPAS(DBaaS) List page.
  3. On the EPAS(DBaaS) List page, click the resource to configure the Replica. 3. Navigate to the EPAS(DBaaS) Details page.
  4. Click the Replica configuration button. 4. Go to the Replica configuration page.
  5. After entering information in the Replica configuration area, click the Complete button.
    Category
    required status
    Detailed description
    RegionRequiredRegion to configure the Replica
    • Replica configuration (Other Region)exposed only when selected
    Replica countRequiredNumber of Replicas to configure
    • Up to 5 can be configured per cluster
    • If you select more than one value, additionally enter the Replica name and service type information
    Replica nameRequiredReplica server name
    • Start with a lowercase English letter, and use lowercase letters, numbers, and special characters (-) to enter 3 to 19 characters
    • The entered Replica name is displayed as the cluster name in the list
    Service Type > Server TypeRequiredReplica server type
    • Standard: standard specification commonly used
    • High Capacity: large-capacity server with 24 vCore or more
    Service Type > Planned ComputeSelectionStatus of resources with Planned Compute configured
    • In Use: Number of resources with Planned Compute that are currently in use
    • Configured: Number of resources with Planned Compute configured
    • Coverage Preview: Amount applied per resource by Planned Compute
    • Create Planned Compute Service: Navigate to the Planned Compute service application page
    IP access controlSelectionService 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 periodSelectionDatabase 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.
    TagSelectAdd 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.

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

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

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

  1. All Services > Database > EPAS(DBaaS) Click the menu. 1. Go to the Service Home page of EPAS (DBaaS).
  2. On the Service Home page, click the EPAS(DBaaS) menu. 2. EPAS(DBaaS) List go to the page.
  3. On the EPAS(DBaaS) List page, click the resource to promote to Master. 3. Go to the EPAS(DBaaS) Details page.
  4. Click the More button, then click the Promote to Master button. 4. Master Promotion Notification The popup window opens.
  5. In the Master Promotion Notification popup, click the Confirm button.

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.

Architecture
Figure. EPAS(DBaaS) connection architecture

Scenario components

You can build the scenario using the following services.

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

For detailed creation steps, refer to the Networking > VPC > How-to guides guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
  2. Click the Create VPC button on the Service Home page. You will be taken to the Create VPC page.
  3. On the VPC Creation page, enter the information required to create the service.
    • Enter the IP range as 192.168.x.0/16
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resources on the VPC List page.

1-2. Create Subnet

For detailed creation instructions, refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click the All Services > Networking > VPC menu. Navigate to the VPC Service Home page.
  2. On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
  3. Click the Subnet Create button. You will be taken to the Subnet Create page.
  4. On the Subnet Creation page, enter the information required to create the service.
    • Select the Subnet type as General.
    • Select a pre‑created VPC.
    • Enter the IP range as 192.168.x.0/24.
  5. 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

For detailed creation steps, please refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
  2. On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
  3. Click the Create Internet Gateway button. You will be taken to the Create Internet Gateway page.
  4. On the Internet Gateway Creation page, enter the required information needed to create the service.
    • Select a pre‑created VPC.
    • In the Firewall usage item, select Use.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, verify the created resource on the Internet Gateway list page.

1-4. Create Public IP

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

For detailed creation steps, see the Networking > Security Group > How-to guides guide.
  1. Click the All Services > Networking > Security Group menu. Go to the Service Home page of Security Group.
  2. Click the Create Security Group button on the Service Home page. Navigate to the Create Security Group page.
  3. On the Security Group creation page, enter the required information needed to create the service.
  4. 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

For detailed creation steps, refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
  3. Click the Keypair creation button. You will be taken to the Keypair creation page.
  4. Enter the required information needed to create a service on the Keypair creation page.
  5. Check the creation information and click the Complete button.
    • The key can be downloaded only once, and reissuance is not available.
    • Please store the downloaded key in a secure location.

2-2. Create Bastion host

For detailed creation steps, refer to the Compute > Virtual Server > How-to guides guide.
  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Virtual Server Create button. It navigates to the Virtual Server Create page.
  3. Virtual Server Creation page, enter the required information to create the service.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, verify the created resources on the Virtual Server list page.

2-3. Bastion host Check login ID and PW

  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. Click the Virtual Server menu on the Service Home page. You will be taken to the Virtual Server List page.
  3. On the Virtual Serve List page, click the resource you created in 2-2. Create Bastion host. You will be taken to the detailed information page of that resource.
  4. On the detail information page, click the RDP password View button in the Keypair name field. The RDP password View popup window will open.
  5. In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
  6. After attaching, click the Password Check button. The ID and Password for accessing the resource are displayed.

Create Database

Describes the process of creating a Database service.

3-1. EPAS(DBaaS) Service Creation

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

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

4-2. Add IGW Firewall Rule

For detailed creation instructions, refer to the Networking > Firewall > How-to guides guide.
  1. All Services > Networking > Firewall Click the menu. Go to the Service Home page of the Firewall.
  2. On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
  3. On the Firewall List page, select the Internet Gateway Resource Name created in 1-3. Internet Gateway 생성하기. You will be taken to the detailed information page for that resource.
  4. Click the Rules tab on the detail information page. You will be taken to the Rules tab.
  5. On the Rules tab, click the Add Rule button. You will be taken to the Add Rule popup.
  6. Add Rule In the popup window, enter the rule below, and click the Confirm button.
    origin addressDestination addressProtocolPortOperationdirectionExplanation
    Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
    Table. Internet Gateway Firewall rules that 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

  1. In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
  2. When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password verified in 2-3. Bastion host Access ID and PW Check and click the Confirm button.

5-2. Install DB client program (pgAdmin) on the Bastion host

  1. Go to the official pgAdmin page and download the pgAdmin program.
  2. Connect the user’s PC hard drive to upload the file to the Bastion host.
  3. In the Remote Desktop Connection Local Resources tab, click the Details button for the Local Devices and Resources entry.
  4. Select the local disk of the location where the file was downloaded on the drive, and click the OK button.
  5. Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install.

5-3. Connect to the database using the DB client program (pgAdmin)

  1. Run pgAdmin and click the Add New Server button.
  2. 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 fieldinput value
    GeneralNameCustom (ex. service name)
    ConnectionHost name/addressDatabase server IP
    ConnectionPortDatabase Port
    ConnectionMaintenance databaseDatabase name
    ConnectionPasswordDatabase password
    Table: DB connection client program input fields
  3. 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

Reference
You can view the list of extensions included in each EPAS version on the PostgreSQL official page.

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 nameExplanation
pg_cronA scheduler that can schedule jobs using cron syntax within the database.
pgvectorProvides AI vector operation features such as vector data types and similarity search.
postgisProvides GIS (Geographic Information System) spatial object storage and spatial query functionality
Table. EPAS (DBaaS) Extension basic installation items

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

API Reference

1.4 - CLI Reference

CLI Reference

1.5 - Release Note

EPAS(DBaaS)

2026.03.19
FEATURE Disaster recovery Replica configuration, OS(Kernel) upgrade feature added
  • 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.
2025.07.01
FEATURE User (access control) management, Archive configuration feature, DB Audit Log export feature added, backup notification feature provided, migration feature added
  • 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
    • DB Audit Log Export feature added
    • Backup Notification Feature provided
    • 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
2025.02.27
NEW EPAS(DBaaS) service official version release
  • 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.

Architecture
Figure. PostgreSQL (DBaaS) Architecture

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.

Provided versionEOS Date (Samsung Cloud Platform new creation stop date)EoTS Date (Community Technical Support End Date)
14.172026-05-202026-11-12
14.182026-05-202026-11-12
14.192026-05-202026-11-12
15.122027-06 (planned)2027-11-11
15.132027-06 (planned)2027-11-11
15.142027-06 (planned)2027-11-11
16.82028-06 (planned)2028-11-09
16.92028-06 (planned)2028-11-09
16.102028-06 (planned)2028-11-09
17.62029-06 (planned)2029-11-08
Table. PostgreSQL (DBaaS) engine versions offered
information

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
CategoryExampleDetailed description
Server typeStandardProvided server types
  • Standard: Commonly used standard specifications (vCPU, Memory) configuration
  • High Capacity: Large server specifications of 24 vCores or more
Server specificationsdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) commonly used
  • dbh2: Large-scale server specifications
    • Provides servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. PostgreSQL (DBaaS) server type components

Preceding Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

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

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
exampleDetailed description
Server typeStandardProvided server type classifications
  • Standard: Configured with the commonly used standard specifications (vCPU, Memory)
  • High Capacity: Large-capacity server specifications exceeding Standard
Server specificationsdb1Provided server type classification and generation
  • db: denotes a standard specification, and 1 indicates the generation
  • dbh: h denotes a high-capacity server specification, and 2 indicates the generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. PostgreSQL (DBaaS) server type format

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. PostgreSQL (DBaaS) server type specifications - db1 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb2v2m42 vCore4 GBUp to 10 Gbps
Standarddb2v2m82 vCore8 GBUp to 10 Gbps
Standarddb2v2m162 vCore16 GBUp to 10 Gbps
Standarddb2v2m242 vCore24 GBUp to 10 Gbps
Standarddb2v2m322 vCore32 GBUp to 10 Gbps
Standarddb2v4m84 vCore8 GBUp to 10 Gbps
Standarddb2v4m164 vCore16 GBUp to 10 Gbps
Standarddb2v4m324 vCore32 GBUp to 10 Gbps
Standarddb2v4m484 vCore48 GBUp to 10 Gbps
Standarddb2v4m644 vCore64 GBUp to 10 Gbps
Standarddb2v6m126 vCore12 GBUp to 10 Gbps
Standarddb2v6m246 vCore24 GBUp to 10 Gbps
Standarddb2v6m486 vCore48 GBUp to 10 Gbps
Standarddb2v6m726 vCore72 GBUp to 10 Gbps
Standarddb2v6m966 vCore96 GBUp to 10 Gbps
Standarddb2v8m168 vCore16 GBUp to 10 Gbps
Standarddb2v8m328 vCore32 GBUp to 10 Gbps
Standarddb2v8m648 vCore64 GBUp to 10 Gbps
Standarddb2v8m968 vCore96 GBUp to 10 Gbps
Standarddb2v8m1288 vCore128 GBUp to 10 Gbps
Standarddb2v10m2010 vCore20 GBUp to 10 Gbps
Standarddb2v10m4010 vCore40 GBUp to 10 Gbps
Standarddb2v10m8010 vCore80 GBUp to 10 Gbps
Standarddb2v10m12010 vCore120 GBUp to 10 Gbps
Standarddb2v10m16010 vCore160 GBUp to 10 Gbps
Standarddb2v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb2v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb2v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb2v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb2v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb2v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb2v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb2v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb2v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb2v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb2v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb2v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb2v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb2v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. PostgreSQL (DBaaS) server type specifications - db2 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBUp to 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBMaximum 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBMaximum 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBMaximum 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBUp to 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBUp to 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBMaximum 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBMaximum 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBMaximum 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBMaximum 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBMaximum 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBMaximum 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBMaximum 25 Gbps
Table. PostgreSQL (DBaaS) server type specifications - dbh2 server type

2.1.2 - Monitoring metrics

Cloud Monitoring Service Termination Notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Service per Resource

    • New Resources: Resources created after the service improvement work in 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.
  2. Cloud Monitoring Service Phased Termination Schedule Notice

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period.**

Detailed information about ServiceWatch 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 itemsDetailed descriptionunit
Active LocksNumber of Active Lockscnt
Active Locks [Access Exclusive]Number of Access Exclusive Lockscnt
Active Locks [Access Share]Number of Access Share Lockscnt
Active Locks [Total]Total number of active lockscnt
Active SessionsNumber of Sessions in Active statecnt
Active Sessions [Total]Total number of Sessions in Active statecnt
Apply Lag TimeApply lag timemin
Check No ReplicationCheck No Replication valuecnt
Check ReplicationCheck Replication Status valuestatus
Connection UsageDB connection usage rate (%)%
Connection Usage [Total]DB connection usage rate (%)%
DB Age MaxDatabase age (frozen XID) valueage
Exclusive LocksNumber of Exclusive Lockscnt
Idle In Transaction SessionsNumber of sessions in idle-in-transaction statecnt
Idle In Transaction Sessions [Total]Total number of sessions in Idle in transaction statecnt
Idle SessionsNumber of idle sessionscnt
Idle Sessions [Total]Total number of sessions in Idle statecnt
Row Exclusive LocksNumber of Row Exclusive Lockscnt
Row Share LocksRow Share Locks countcnt
Share LocksNumber of Share Lockscnt
Share Row Exclusive LocksNumber of Share Row Exclusive Lockscnt
Share Update Exclusive LocksNumber of Share Update Exclusive Lockscnt
SlowqueriesNumber of SQL queries running for a long time (over 5 minutes)cnt
Tablespace UsedTable space sizebytes
Tablespace Used [Total]Table space sizebytes
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 LocksNumber of lock-waiting sessions (by DB)cnt
Wait Locks [Long Total]Number of lock‑waiting sessions lasting 300 secondscnt
Wait Locks [Long]Number of sessions waiting due to lock occurrencecnt
Wait Locks [Total]Total number of sessions waiting due to lock occurrencecnt
Waiting SessionsNumber of Sessions in Waiting statecnt
Waiting Sessions [Total]Total number of Sessions in Waiting statecnt
Table. PostgreSQL (DBaaS) Monitoring Metrics

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.

Cloud Monitoring service termination notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Services by Resource

    • New Resources: Resources created after the service improvement work in 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.
  2. Notice of the phased termination schedule for Cloud Monitoring service

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration work within the parallel operation period**.

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.

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

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).

  2. On the Service Home page, click the PostgreSQL(DBaaS) Create button. 2. Navigate to the Create PostgreSQL (DBaaS) page.

  3. 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 status
      Detailed description
      Image versionrequiredProvide 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 status
      Detailed description
      Server name PrefixRequiredServer 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 nameRequiredCluster name of DB servers
      • Enter using English letters, 3 to 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type for DB installation
      • Standard: Standard specifications commonly used
      • High Capacity: Large-capacity server with 24 vCores or more
      Service Type > Planned ComputeSelectionStatus of resources with Planned Compute configured
      • In Use: Number of resources with Planned Compute configured that are currently in use
      • Configured: Number of resources with Planned Compute configured
      • Coverage Preview: Amount applied per resource by Planned Compute
      • Create Planned Compute Service: Navigate to the Planned Compute service application page
      Service Type > Block StorageRequiredBlock Storage configuration used by the DB according to its purpose
      • Basic OS: Area where the DB engine is installed
      • DATA: Storage area for table data, archive files, etc.
        • Select a storage type and then enter the capacity (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 /tmp area 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
      Redundant configurationSelectRedundancy configuration status
      • When redundancy configuration is used, the DB instance is set up as an Active DB and a Standby DB
      Network > Common SettingsRequiredNetwork settings for servers created by the service
      • Select when you want to apply the same settings to all installed servers
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • IP can only be 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 SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select when you want to apply different settings for each installed server
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • Enter the IP for each server
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. 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 controlSelectService Access Policy Configuration
      • Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
      • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      maintenance periodSelectDatabase maintenance window
      • If you select Use, set the day, 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
    • Enter or select the required information in the Database Configuration Required Information Input area.
      Category
      required status
      Detailed description
      Database nameRequiredServer name applied during DB installation
      • must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
      Database usernameRequiredDB user name
      • An account with the same name is also created on the OS
      • Enter using lowercase English letters, 2 to 20 characters
      • Restricted database user names can be viewed in the Console
      Database passwordRequiredPassword to use when accessing the DB
      • Enter 8 to 30 characters, including letters, numbers, and special characters (excluding )
      Database password verificationRequiredRe-enter the same password to be used for DB access
      Database Port numberRequiredPort number required for DB connection
      • Enter the DB port within the range 1200 ~ 65535
      Backup > UseSelectBackup usage
      • Select Use to set the backup file retention period, backup start time, and Archive backup interval
      Backup > Retention periodSelectBackup retention period
      • Select the backup retention period, set the file retention period from 7 days to 35 days
      • Backup files incur additional charges based on size
      Backup > Backup Start PeriodSelectionBackup 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 cycleSelectArchive 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 SettingsSelectWhether 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_statement parameter, and can modify it through the Parameter screen
        • Enabling Audit may degrade database performance
      ParameterRequiredParameters 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 EncodingEssentialCharacter 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 LocaleRequiredLocale 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 zoneRequiredStandard 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 status
      Detailed description
      TagSelectAdd Tag
      • Up to 50 per resource can be added
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. PostgreSQL (DBaaS) Additional Information Input Fields
  4. 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.

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

Detailed information

PostgreSQL (DBaaS) List page allows you to view detailed information of the selected resource and, if needed, edit the information.

CategoryDetailed description
Server InformationServer information configured in this cluster
  • Category: Server type (Active, Standby, Replica)
  • Server Name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the DB service, it refers to the cluster SRN
Resource NameResource name
  • In the DB service, it refers to the cluster name
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation date and timeService creation date and time
ModifierUser who edited the service information
Modification dateDate and time the service information was modified
Image versionInstalled DB image and version information
  • If a version upgrade is required, click the Edit icon to configure
Cluster typeCluster types (Master Cluster, Replica Cluster, Migration Cluster)
Cluster nameCluster name of the DB servers
Master cluster nameReplica’s Master cluster name
  • If it is the detailed information of the Replica, you can verify it.
Database nameServer name applied during DB installation
Database usernameDB user name
Planned ComputeResources with Planned Compute configured
maintenance periodDB patch work period setting status
  • If you need to set the maintenance period, click the Edit icon to configure
BackupBackup Configuration Status
  • If backup configuration is required, click the Edit icon to set it
Audit Log SettingsAudit Log configuration status
  • If Audit Log configuration is required, click the Edit icon to set it
time zoneStandard time zone for the database
DB LocaleLocale to use for the DB
Database EncodingCharacter encoding to use for the DB
VIPVirtual IP information
  • can be checked only when redundancy is configured
NetworkNetwork information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP))
IP access controlService access policy configuration
  • If you need to add or remove IPs, click the Edit icon to configure
Active & StandbyActive/Standby server type, default OS, additional Disk information
  • If you need to modify the server type, click the Edit icon next to the server type to set it. See the server type modification procedure in 서버 타입 변경하기.
    • Modifying the server type requires a server reboot.
  • If you need to expand storage, click the Edit icon next to the storage capacity to expand it. See the storage expansion procedure at 스토리지 증설하기.
  • If you need to add storage, click the Add Disk button next to the additional Disk to add it. See the storage addition procedure at 스토리지 추가하기.
Table. PostgreSQL (DBaaS) Database detailed information items

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.

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

tag

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

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

Work History

On the PostgreSQL (DBaaS) List page, you can view the operation history of the selected resource.

CategoryDetailed description
Task History ListResource Change History
  • Operation timestamp, resource ID, resource name, operation details, event topic, operation result, operator information verification
Table. Work History Tab Detailed Information Items

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.

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

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
  3. PostgreSQL(DBaaS) List Click the resource on the page to view the service status. 3. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Click the Service Status Synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
  5. When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.

Change server type

You can change the configured server type.

Caution
If you modify the server type, a server restart is required. Please separately verify any software license modifications or software settings and their implementation due to server specification changes.

To change the server type, follow these steps.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
  3. On the PostgreSQL (DBaaS) List page, click the resource whose server type you want to change. 3. PostgreSQL(DBaaS) Details Go to the page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
  5. 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.

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

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Go to the page.
  3. On the PostgreSQL (DBaaS) List page, click the resource to add storage. 3. PostgreSQL(DBaaS) Details Go to the page.
  4. Click the Add Disk button at the bottom of the details. 4. Additional Storage Request The popup window opens.
  5. Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.

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.

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
  3. 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.
  4. Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
  5. Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.

Cancel 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.

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

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

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

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

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.

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
  2. Click the Service Home page’s PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
  3. PostgreSQL(DBaaS) List page, click the resource you want to view DB users for. PostgreSQL(DBaaS) Details page will be opened.
  4. Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
  5. 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.

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

Managing DB Access Control

Provides IP-based DB user access control management functionality. Users can directly specify the IPs that can access the database, configuring it so that only authorized IPs are allowed access.

Information
Before setting DB access control, perform a DB user lookup. Please refer to DB 사용자 관리하기 for DB user lookup.

Query DB Access Control

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

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
  3. 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.
  4. Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. On the DB Access Control Management page, click the Search button. Retrieving the data may take a short time.

Add DB access control

To add IP access control, follow these steps.

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

Delete DB access control

To delete IP access control, follow these steps.

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

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

Configure Archive mode

To set the Archive mode, follow these steps.

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

Delete Archive file

To delete the Archive file, follow these steps.

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

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
  2. Click the PostgreSQL(DBaaS) menu on the Service Home page. You will be taken to the PostgreSQL(DBaaS) List page.
  3. PostgreSQL(DBaaS) List page: click the resource to view the service status. You will be taken to the PostgreSQL(DBaaS) Details page.
  4. Click the Edit icon of Audit Settings at the bottom of the detailed information. The Edit Audit Settings popup window opens.
  5. 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.

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

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

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

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

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

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

To configure Migration, follow these steps.

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

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

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

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
  2. From the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
  3. On the PostgreSQL(DBaaS) List page, click the resource to promote to Master. You will be taken to the PostgreSQL(DBaaS) Details page.
  4. Click the More button and then click the Master Promotion button. The Master Promotion Notification popup window opens.
  5. In the Master Promotion Notification popup, click the Confirm button.

Upgrade OS Kernel

The OS kernel can be upgraded to improve the functionality of the running database and apply security patches.

Caution
  • The service will be unavailable while the OS upgrade is in progress.
  • The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
  • After the upgrade is complete, you cannot revert to the previous OS.

To upgrade the OS kernel, follow the steps below.

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

Caution
  • For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity.

  • Especially when the backup data exceeds 100 GB and undergoes frequent changes, please 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.

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

Check Backup History

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

To view the backup history, follow these steps.

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
  3. PostgreSQL(DBaaS) List page, click the resource to view the backup history. 3. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.

Delete backup file

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

To delete the backup history, follow these steps.

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

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

To recover PostgreSQL (DBaaS), follow these steps.

  1. Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
  3. PostgreSQL(DBaaS) resource Click the resource you want to restore on the list page. 3. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Click the Database Recovery button. 4. Go to the Database Recovery page.
  5. After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
    Category
    required status
    Detailed description
    Recovery TypeRequiredSet the point in time the user wants to recover
    • Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
    • Custom point: Recover to a user-specified point within the range of recoverable backup times. The recoverable period depends on the Archive backup cycle setting, allowing recovery from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the desired date and time for the backup
    server name prefixEssentialRecovery 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 nameRequiredCluster name of the recovery DB
    • Enter using English letters, 3 ~ 20 characters
    • A cluster is a unit that groups multiple servers
    Service Type > Server TypeRequiredServer type for the recovery DB installation
    • Standard: standard specifications commonly used
    • High Capacity: large-capacity server with 24 vCores or more
    Service Type > Planned ComputeSelectStatus 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
    Service Type > Block StorageRequiredBlock Storage settings used by the recovery DB
    • Basic OS: Area where the DB engine is installed
    • DATA: Storage area for table data, archive files, etc.
      • 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 usernameRequiredDatabase username configured in the source DB
    Database Port numberRequiredDatabase port number configured in the source DB
    IP access controlSelectIP address for accessing the recovery DB
    • Enter in IP format (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 periodSelectDatabase maintenance window
    • If you select Use, set the day of week, start time, and duration
    • It is recommended to set a maintenance window for stable 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.
    TagSelectAdd 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.

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

To configure a Replica, follow these steps.

  1. All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
  2. On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
  3. On the PostgreSQL(DBaaS) List page, click the resource to configure a Replica. 3. PostgreSQL(DBaaS) Details Navigate to the page.
  4. Click the Replica configuration button. 4. Go to the Replica configuration page.
  5. After entering the information in the Replica configuration area, click the Complete button.
    Category
    required status
    Detailed description
    RegionRequiredRegion to configure the Replica
    • Replica configuration (Other Region)is displayed only when selected
    Replica countRequiredNumber of Replicas to configure
    • Up to 5 can be configured per cluster
    • If you select more than one value, additionally enter the Replica name and service type information
    Replica nameRequiredReplica server name
    • 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 TypeEssentialReplica server type
    • Standard: standard specification commonly used
    • High Capacity: large-capacity server with 24 vCores or more
    Service Type > Planned ComputeSelectStatus 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
    Service Type > Block StorageRequiredBlock 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 controlSelectService Access Policy Configuration
    • Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
    • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
    • To delete an entered IP, click the x button next to the entered IP
    maintenance periodSelectDatabase maintenance window
    • 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.
    tagSelectionAdd 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.

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

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

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

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

Architecture
Figure. PostgreSQL(DBaaS) server connection architecture

Scenario components

You can build the scenario using the following services.

Service group
service
Detailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
NetworkingVPC > SubnetA service that lets users subdivide the network within a VPC to match their purpose and scale.
NetworkingVPC > Public IPA service that reserves a public IP and allocates and releases it to Compute resources.
NetworkingVPC > Internet GatewayA service that connects VPC resources to the Internet
NetworkingSecurity GroupVirtual firewall that controls server traffic
DatabasePostgreSQL(DBaaS)A service that easily creates and manages EPAS in a web environment
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeVirtual Server > KeypairEncryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
  • Since the default policy of a Security Group is Deny All, you must register only the allowed IPs.
  • The All Open (Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
    • By specifying the required IP and port and setting a policy, you can strengthen security.

Scenario 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

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

For detailed creation instructions, refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
  2. On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
  3. Click the Create Subnet button. You will be taken to the Create Subnet page.
  4. On the Subnet Creation page, enter the information required to create the service.
    • Select the Subnet type as General.
    • Select a pre‑created VPC.
    • Enter the IP range as 192.168.x.0/24.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • When creation is complete, check the created resources on the Subnet List page.

1-3. Create Internet Gateway

For detailed creation steps, refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click the All Services > Networking > VPC menu. Go to the VPC’s Service Home page.
  2. On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
  3. Click the Create Internet Gateway button. You will be taken to the Create Internet Gateway page.
  4. On the Internet Gateway Creation page, enter the required information to create the service.
    • Select a pre‑created VPC.
    • In the Firewall usage option, select Use.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the Internet Gateway list page.

1-4. Create Public IP

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

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

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

For detailed creation instructions, see the Compute > Virtual Server > How-to guides guide.
  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Virtual Server Creation button. You will be taken to the Virtual Server Creation page.
  3. On the Virtual Server Creation page, enter the required information to create the service.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resources on the Virtual Server List page.

2-3. Verify Bastion host login ID and password

  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. Click the Virtual Server menu on the Service Home page. You will be taken to the Virtual Server List page.
  3. On the Virtual Serve List page, click the resource you created in 2-2. Bastion host Create. You will be taken to that resource’s detailed information page.
  4. On the detail page, click the RDP password view button in the Keypair name field. The RDP password view popup window will open.
  5. In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
  6. After attaching, click the Password Check button. The ID and Password required to access the resource are displayed.

Create Database

Describes the process of creating a Database service.

3-1. Create PostgreSQL (DBaaS) Service

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

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

4-2. Add IGW Firewall Rule

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

  1. In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
  2. When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password 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

  1. Go to the official pgAdmin page and download the pgAdmin program.
  2. Connect the user’s PC hard drive to upload the file to the Bastion host.
  3. In the Local Resources tab of the Remote Desktop Connection, click the Details button for the Local Devices and Resources item.
  4. Select the local disk of the location where the file was downloaded on the drive, and click the OK button.
  5. Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install.

5-3. Connect to the database using the DB client program (pgAdmin)

  1. Run pgAdmin and click the Add New Server button.
  2. 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 fieldinput value
    GeneralNameCustom (ex. service name)
    ConnectionHost name/addressDatabase server IP
    ConnectionPortDatabase Port
    ConnectionMaintenance databaseDatabase name
    ConnectionPasswordDatabase password
    Table.DB connection client program input fields
  3. 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

Note
You can view the list of extensions included in each PostgreSQL version on the PostgreSQL official page.

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 nameExplanation
pgauditProvides detailed audit logging at the session and object level
pg_cronA scheduler that can schedule jobs using cron syntax within the database.
pg_hint_planProvides a feature to apply hint clauses to SQL execution plans.
pgvectorProvides vector data types and AI vector operation features such as similarity search.
postgisGIS (Geographic Information System) provides spatial object storage and spatial query functionality
Table. PostgreSQL (DBaaS) Extension additional installation items

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

API Reference

2.4 - CLI Reference

CLI Reference

2.5 - Release Note

PostgreSQL(DBaaS)

2026.03.19
FEATURE Add OS(Kernel) upgrade feature
  • The OS (Kernel) upgrade feature enhances the latest security patches and stability.
2025.12.16
FEATURE Add Replica configuration feature for disaster recovery
  • You can set up a disaster-recovery Replica using the Replica configuration (Other Region) feature.
2025.07.01
FEATURE User (access control) management, Archive configuration feature, DB Audit Log export feature added, backup notification feature provided, migration feature added
  • Add 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
    • DB Audit Log Export feature added
    • 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
2025.02.27
FEATURE New version, added server types and per-server IP configuration, added Block Storage capacity expansion feature
  • 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.
2024.10.01
NEW PostgreSQL(DBaaS) service official version release
  • 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.
2024.07.02
NEW Beta version release
  • 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.

Architecture
Figure. MariaDB (DBaaS) Architecture

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.

serviceProvided versionEOS Date (Samsung Cloud Platform new creation stop date)EoTS Date (Community technical support end date)
MariaDB (Community)10.6.52026-03-192026-07-06
10.6.92026-03-192026-07-06
10.6.102026-03-192026-07-06
10.6.122026-03-192026-07-06
10.6.142026-03-192026-07-06
10.6.152026-03-192026-07-06
10.6.162026-03-192026-07-06
10.6.172026-03-192026-07-06
10.6.192026-03-192026-07-06
10.6.222026-03-192026-07-06
10.11.82027-09 (planned)2028-02-16
10.11.92027-09 (planned)2028-02-16
10.11.132027-09 (planned)2028-02-16
11.4.72028-12 (planned)2029-05-29
Table. Engine versions offered for MariaDB (DBaaS)
information

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
CategoryExampleDetailed description
Server typeStandardProvided server types
  • Standard: Standard configuration (vCPU, Memory) commonly used
  • High Capacity: Large server specifications of 24 vCores or more
Server specificationsdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) commonly used
  • dbh2: Large-scale server specifications
    • Provides servers with 24 vCores or more
Server specificationsv2vCore count
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. MariaDB (DBaaS) server type components

Preceding Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

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

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
exampleDetailed description
Server typeStandardProvided server type classifications
  • Standard: Configured with commonly used standard specifications (vCPU, Memory)
  • High Capacity: Large-capacity server specifications exceeding Standard
Server specificationsdb1Provided server type classification and generation
  • db1: indicates a standard specification, and 1 denotes the generation
  • dbh2: h indicates a high-capacity server specification, and 2 denotes the generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. MariaDB (DBaaS) server type format

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb1v1m21 vCore2 GBUp to 10 Gbps
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. MariaDB (DBaaS) server type specifications - db1 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb2v1m21 vCore2 GBUp to 10 Gbps
Standarddb2v2m42 vCore4 GBUp to 10 Gbps
Standarddb2v2m82 vCore8 GBUp to 10 Gbps
Standarddb2v2m162 vCore16 GBUp to 10 Gbps
Standarddb2v2m242 vCore24 GBUp to 10 Gbps
Standarddb2v2m322 vCore32 GBUp to 10 Gbps
Standarddb2v4m84 vCore8 GBUp to 10 Gbps
Standarddb2v4m164 vCore16 GBUp to 10 Gbps
Standarddb2v4m324 vCore32 GBUp to 10 Gbps
Standarddb2v4m484 vCore48 GBUp to 10 Gbps
Standarddb2v4m644 vCore64 GBUp to 10 Gbps
Standarddb2v6m126 vCore12 GBUp to 10 Gbps
Standarddb2v6m246 vCore24 GBUp to 10 Gbps
Standarddb2v6m486 vCore48 GBUp to 10 Gbps
Standarddb2v6m726 vCore72 GBUp to 10 Gbps
Standarddb2v6m966 vCore96 GBUp to 10 Gbps
Standarddb2v8m168 vCore16 GBUp to 10 Gbps
Standarddb2v8m328 vCore32 GBUp to 10 Gbps
Standarddb2v8m648 vCore64 GBUp to 10 Gbps
Standarddb2v8m968 vCore96 GBUp to 10 Gbps
Standarddb2v8m1288 vCore128 GBUp to 10 Gbps
Standarddb2v10m2010 vCore20 GBUp to 10 Gbps
Standarddb2v10m4010 vCore40 GBUp to 10 Gbps
Standarddb2v10m8010 vCore80 GBUp to 10 Gbps
Standarddb2v10m12010 vCore120 GBUp to 10 Gbps
Standarddb2v10m16010 vCore160 GBUp to 10 Gbps
Standarddb2v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb2v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb2v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb2v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb2v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb2v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb2v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb2v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb2v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb2v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb2v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb2v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb2v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb2v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. MariaDB (DBaaS) server type specifications - db2 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBMaximum 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBMaximum 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBMaximum 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBMaximum 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBMaximum 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBUp to 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBUp to 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBUp to 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBMaximum 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBUp to 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBUp to 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBMaximum 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBMaximum 25 Gbps
Table. MariaDB (DBaaS) server type specifications - dbh2 server type

3.1.2 - Monitoring Metrics

Cloud Monitoring service termination notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Service 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.
  2. 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.
* 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 itemsDetailed descriptionunit
Active LocksNumber of Active Lockscnt
Active SessionsNumber of Active Sessionscnt
Connection Usage [Total]DB connection session usage rate%
ConnectionsNumber of connectionscnt
Connections [MAX]max connected threads countcnt
Binary Log Used [MB]binary log usageMB
Data Directory Used [MB]data directory usageMB
Open FilesNumber of open DB filescnt
Open Files [MAX]Number of DB files that can be openedcnt
Open Files UsageDB file maximum count usage rate%
Relay Log Used [MB]relay log usageMB
Instance Status [PID]mariadbd processpid
Safe PIDmariadbd_safe processpid
Slave Behind Master secondsData time difference between Master and Slave (run only on slave)sec
Tablespace UsedTablespace usageMB
Tablespace Used [Total]Total tablespace usageMB
Running Threadsrunning thread countcnt
SlowqueriesNumber 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 timesec
Wait LocksNumber of sessions blocked for more than 60 seconds by lockcnt
Table. MariaDB(DBaaS) Monitoring Metrics

3.1.3 - ServiceWatch Metrics

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

Reference
For how to view metrics in ServiceWatch, refer to the ServiceWatch guide.

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

MariaDB basic metrics

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

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.

Cloud Monitoring Service Termination Notice

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.

  1. 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.
  2. 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.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch can be found in the ServiceWatch 개요.

Create MariaDB (DBaaS)

You can create and use a MariaDB (DBaaS) service from the Samsung Cloud Platform Console.

information
  • Before creating the service, configure the VPC’s subnet type as General.
    • If the subnet type is Local, the corresponding Database service cannot be created.
  • When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to the statistical collection environment.

To create a MariaDB (DBaaS), follow the steps below.

  1. All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
  2. On the Service Home page, click the Create MariaDB (DBaaS) button. 2. Go to the Create MariaDB (DBaaS) page.
  3. 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 status
      Detailed description
      Image versionRequiredProvide 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 status
      Detailed description
      Server name PrefixRequiredThe 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 namerequiredCluster name composed of DB servers
      • Enter using English letters, 3 ~ 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type for DB installation
      • Standard: Standard specifications commonly used
      • High Capacity: Large-capacity server with 24 vCores or more
      Service Type > Planned ComputeSelectStatus of resources with Planned Compute configured
      • In Use: Number of resources with Planned Compute that are currently in use
      • Configured: Number of resources with Planned Compute configured
      • Coverage Preview: Amount applied per resource by Planned Compute
      • Create Planned Compute Service: Navigate to the Planned Compute service application page
      Service Type > Block StoragerequiredBlock Storage settings used by the 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
      • 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 /tmp area is used, and backup fails if capacity is insufficient
        • For each service, only one Block Storage is allocated for Archive, TEMP, and BACKUP
      Redundancy configurationSelectRedundancy configuration
      • When redundancy is enabled, the DB instance is configured as an Active DB and a Standby DB
      Network > Common SettingsRequiredNetwork settings for servers created by the service
      • Select when you want to apply the same settings to all installed servers
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • IP can only be 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 SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select when you want to apply different settings for each installed server
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • Enter the IP for each server
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select a reserved IP from the VPC product’s Public IP. For more information, see Public IP 생성하기
      IP access controlSelectService Access Policy Configuration
      • Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
      • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      maintenance periodSelectDatabase maintenance window
      • If you select Use, set the day of week, start time, and duration
      • It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
      • If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.
      Table. MariaDB (DBaaS) Service Information Input Items
    • Enter required database configuration information Enter or select the required information in this area.
      Category
      required status
      Detailed description
      Database nameRequiredServer name applied during DB installation
      • must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
      Database usernameRequiredDB 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 passwordRequiredPassword to use when accessing the DB
      • Include English letters, numbers, and special characters ( excluded) and enter 8~30 characters
      Database password verificationRequiredRe-enter the same password to use for DB access
      Database Port numberRequiredPort number required for DB connection
      • Enter the DB port within the range 1200 ~ 65535
      Backup > UseSelectBackup usage
      • Select Use to set the backup file retention period, backup start time, and Archive backup interval
      Backup > Retention periodSelectBackup retention period
      • Select the backup retention period. Set the file retention period from 7 days to 35 days
      • Backup files incur additional charges based on size
      Backup > Backup Start PeriodSelectionBackup 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 cycleSelectArchive 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 SettingsSelectionWhether 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_events parameter, and can modify it through the Parameter screen
          Enabling Audit may degrade database performance
      ServiceWatch log collectionSelectionWhether to collect ServiceWatch logs
      • Select Use to configure the ServiceWatch log collection feature
      • 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
      ParameterRequiredParameters 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 setRequiredCharacter 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 zoneRequiredStandard 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 status
      Detailed description
      tagSelectionAdd 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
  4. 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.

  1. All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB(DBaaS) List page is accessed.
  3. 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.
      CategoryDetailed description
      Cluster statusCluster 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 controlButtons to change the cluster state
      • Start: Start a stopped cluster
      • Stop: Stop a running cluster
      • Restart: Restart a running cluster
      • Switch-Over: Switch a standby cluster to Active
      More featuresCluster management 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 cancellationCancel service button
      Table. MariaDB (DBaaS) status information and additional features

Detailed information

On the MariaDB (DBaaS) List page, you can view detailed information of the selected resource and, if necessary, edit the information.

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

Replica information

Replica information tab is enabled only when a Replica is configured in the cluster. Replica information tab allows you to view the Master cluster name, replica count, and Replica status.

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

tag

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

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

Work History

MariaDB(DBaaS) List page lets you view the operation history of the selected resource.

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

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.

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

  1. All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
  3. On the MariaDB(DBaaS) List page, click the resource to view the service status. 3. MariaDB(DBaaS) Details Go to the page.
  4. Click the Service Status Synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
  5. When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.

Change server type

You can change the configured server type.

Caution
If you modify the server type, a server restart is required. Please separately verify any software license modifications or software settings and their implementation resulting from server specification changes.

To change the server type, follow these steps.

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

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

  1. All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
  3. On the MariaDB (DBaaS) List page, click the resource to add storage. 3. MariaDB(DBaaS) Details Go to the page.
  4. Click the Add Disk button at the bottom of the details. 4. Additional Storage Request The popup window opens.
  5. Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.

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.

  1. All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
  3. Click the resource to change the server type on the MariaDB (DBaaS) List page. 3. MariaDB(DBaaS) Details Go to the page.
  4. Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
  5. Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.

Cancel 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.

Caution
  • For a DB with a Replica configured, terminating the Master DB does not delete the Replica. * If you also delete the replica, please cancel it separately from the resource list.
  • If you terminate the DB, all stored data and any backup data that has been configured will be deleted.

To cancel MariaDB (DBaaS), follow the steps below.

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

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

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

If you change the character_set_server value, first verify the collation that matches the character set using the command below.

SQL> SHOW COLLATION WHERE Charset = 'character set name';

Set the parameter values for character-set-server, collation-server, and init_connect using the verified collation.

ItemDetailed descriptionRestart option
character-set-serverSpecify the default character setRestart required
collation-serverSpecify default collationRestart required
init_connectSQL statements executed when the client connects to the databaseNo restart required
Table. Parameter setting items

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.

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

  1. Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. Click the MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
  3. 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.
  4. Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
  5. DB User Management page, click the Search button. Retrieving the data may take a short while.
  6. If a correction is needed, click the Edit button, then change the status field value or enter remarks.
  7. When the input is complete, click the Complete button.

Managing DB Access Control

Provides IP-based DB user access control management functionality. Users can directly specify the IPs that may access the database, configuring it so that only authorized IPs are allowed.

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

Query DB Access Control

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

  1. Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
  3. 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.
  4. Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. On the DB Access Control Management page, click the Search button. The query may take a moment.

Add DB access control

To add IP access control, follow these steps.

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

Delete DB access control

To delete IP access control, follow these steps.

  1. Click the All Services > Database > MariaDB(DBaaS) menu. You will be taken to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
  3. MariaDB(DBaaS) List page, click the resource for which you want to delete IP access control. MariaDB(DBaaS) Details page will be opened.
  4. Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. DB Access Control Management page, click the Search button. Retrieving the data may take a short time.
  6. When the query is complete, click the Delete button. The Delete popup window opens.
  7. 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.

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

Configure Archive mode

To set the Archive mode, follow these steps.

  1. Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
  3. MariaDB(DBaaS) List page, click the resource you want to set Archive mode for. You will be taken to the MariaDB(DBaaS) Details page.
  4. Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
  5. On the Archive Settings Management page, click the Search button. The query may take a short time.
  6. Click the Edit button and select the usage status and retention period.
  7. When the edit is complete, click the Done button.

Delete Archive file

To delete the Archive file, follow these steps.

  1. Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
  3. MariaDB(DBaaS) List page, click the resource you want to set Archive mode for. You will be taken to the MariaDB(DBaaS) Details page.
  4. Click the More button, then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
  5. On the Archive Settings Management page, if you want to delete all Archive files, click 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.

  1. Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Go to the MariaDB(DBaaS) List page.
  3. MariaDB(DBaaS) List page, click the resource to view the service status. You will be taken to the MariaDB(DBaaS) Details page.
  4. Click the Edit icon of Audit Settings at the bottom of the detailed information. The Edit Audit Settings popup window opens.
  5. 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.

information
  • To use the DB Log export function, you need to create an Object Storage. For creating Object Storage, please refer to the Object Storage User Guide.
  • Please be sure to check the expiration date and time of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
  • Please ensure that authentication key information is not exposed externally.

Setting DB Log Export Mode

To set the DB Log export mode, follow these steps.

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

  1. Click the All Services > Database > MariaDB(DBaaS) menu. Go to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
  3. 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.
  4. Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
  5. On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, 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.

Warning
  • First retrieve the service status by synchronizing it, then perform the version upgrade.
  • Please perform the version upgrade after configuring a backup. If you do not set up a backup, you may be unable to recover some data if a problem occurs during the 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.

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

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

To configure Migration, follow these steps.

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

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

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

  1. Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) List page.
  3. On the MariaDB(DBaaS) List page, click the resource to promote to Master. You will be taken to the MariaDB(DBaaS) Details page.
  4. Click the More button, then click the Master Promotion button. The Master Promotion Notification popup opens.
  5. In the Master Promotion Notification popup, click the Confirm button.

Upgrade OS Kernel

The OS Kernel can be upgraded to improve the functionality of the running database and apply security patches.

Caution
  • The service will be unavailable while the OS upgrade is in progress.
  • The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
  • After the upgrade is complete, you cannot revert to the previous OS.

To upgrade the OS Kernel, follow these steps.

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

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

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

Check backup history

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

To check the backup history, follow these steps.

  1. All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
  3. MariaDB (DBaaS) List page: click the resource to view the backup history. 3. MariaDB(DBaaS) Details Go to the page.
  4. Click the Backup History button. 4. Backup History the popup window opens.
  5. Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.

Delete backup files

To delete the backup file, follow these steps.

Caution
Backup files cannot be restored after deletion. Please be sure to verify whether the data is unnecessary before deleting it.
  1. All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. 2. Navigate to the MariaDB(DBaaS) List page.
  3. MariaDB (DBaaS) List page: click the resource to view the backup history. 3. MariaDB(DBaaS) Details Navigate to the page.
  4. Click the Backup History button. 4. Backup History popup opens.
  5. 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.

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

To recover MariaDB (DBaaS), follow these steps.

  1. All Services > Database > MariaDB(DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB (DBaaS) List Go to the page.
  3. On the MariaDB (DBaaS) List page, click the resource you want to recover. 3. MariaDB(DBaaS) Details Go to the page.
  4. Click the Database Recovery button. 4. Go to the Database Recovery page.
  5. After entering information in the Database recovery configuration area, click the Complete button.
    Category
    required status
    Detailed description
    Recovery TypeRequiredSet the point in time the user wants to recover
    • Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
    • Custom point: Recover to a user‑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 prefixRequiredServer 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 nameRequiredCluster name of the recovery DB
    • Enter using English letters, 3 ~ 20 characters
    • A cluster is a unit that groups multiple servers
    Service Type > Server TypeEssentialServer 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 ComputeSelectionStatus of resources with Planned Compute configured
    • In Use: Number of resources with Planned Compute configured that are currently in use
    • Configured: Number of resources with Planned Compute configured
    • Coverage Preview: Amount applied per resource by Planned Compute
    Service Type > Block StorageRequiredBlock Storage settings used by the recovery DB
    • Basic OS: Area where the DB engine is installed
    • DATA: Storage area for table data, archive files, etc.
      • Applied identically with the storage type set in the source cluster
      • Enter capacity as a multiple of 8 within the range 16 to 5,120
    • Additional: Storage area for DATA, Archive, TEMP, Backup data
      • Applied identically with the storage type set in the source cluster
      • In the recovery DB, only DATA, TEMP, and Archive purposes can be added
      • After selecting Use, enter the storage purpose and capacity
      • To add storage, click the Add button; to delete, click the x button
      • Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
    Database usernameRequiredDatabase username configured in the source DB
    Database Port numberRequiredDatabase port number set in the source DB
    IP access controlSelectionIP 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 periodSelectDatabase maintenance window
    • If you select Use, set the day of week, start time, and duration
    • It is recommended to set a maintenance window for stable 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.
    tagSelectAdd 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.

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

To configure a Replica, follow these steps.

  1. All Services > Database > MariaDB (DBaaS) Click the menu. 1. Go to the Service Home page of MariaDB (DBaaS).
  2. On the Service Home page, click the MariaDB(DBaaS) menu. 2. MariaDB (DBaaS) List page is accessed.
  3. On the MariaDB (DBaaS) List page, click the resource to configure a Replica. 3. MariaDB(DBaaS) Details Go to the page.
  4. Click the Replica configuration button. 4. Replica configuration Navigate to the page.
  5. After entering information in the Replica configuration area, click the Complete button.
    Category
    required status
    Detailed description
    RegionRequiredRegion to configure the Replica
    • Replica configuration (Other Region) is displayed only when selected
    Replica countRequiredNumber of Replicas to configure
    • Up to 5 can be configured per cluster
    • If you select more than one value, additionally enter the Replica name and service type information
    Replica nameRequiredReplica server name
    • 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 TypeEssentialReplica server type
    • Standard: standard specification commonly used
    • High Capacity: large-capacity server with 24vCore or more (to be provided later)
    Service Type > Planned ComputeSelectStatus 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
    Service Type > Block StorageRequiredBlock 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 controlSelectionService Access Policy Configuration
    • Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
    • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
    • To delete an entered IP, click the x button next to the entered IP
    maintenance periodSelectDatabase maintenance window
    • If you select Use, set the day of week, start time, and duration
    • It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
    • If set to unused, we are not responsible for issues arising from patches not being applied.
    tagSelectAdd Tag
    • 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.

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

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

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

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

Architecture
Figure. MariaDB (DBaaS) server connection architecture

Scenario components

You can build the scenario using the following services.

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

For detailed creation instructions, see the Networking > VPC > How-to guides guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
  2. Click the Create VPC button on the Service Home page. You will be taken to the Create VPC page.
  3. On the VPC creation page, enter the information required to create the service.
    • Enter the IP range as 192.168.x.0/16 .
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resources on the VPC List page.

1-2. Create Subnet

For detailed creation instructions, refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
  2. On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
  3. Click the Create Subnet button. You will be taken to the Create Subnet page.
  4. On the Subnet Creation page, enter the information required to create the service.
    • Select the Subnet type as General.
    • Select a pre‑created VPC.
    • Enter the IP range as 192.168.x.0/24.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, check the created resources on the Subnet list page.

1-3. Create Internet Gateway

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

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

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

For detailed creation steps, refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
  3. Click the Create Keypair button. You will be taken to the Create Keypair page.
  4. Enter the required information needed to create a service on the Keypair creation page.
  5. Check the creation information and click the Complete button.
    • The key can be downloaded only once, and reissuance is not available.
    • Please store the downloaded key in a secure location.

2-2. Create Bastion host

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

  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
  3. On the Virtual Serve List page, click the resource you created in [2-2. Bastion host Creation]. You will be taken to the detailed information page for that resource.
  4. On the detail information page, click the RDP password view button in the Keypair name field. The RDP password view popup window will open.
  5. In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
  6. After attaching, click the Password Check button. The ID and Password required to access the resource are displayed.

Create Database

Describes the process of creating a Database service.

3-1. MariaDB(DBaaS) Create Service

For detailed creation instructions, refer to the Database > MariaDB(DBaaS) > How-to guides guide.
  1. Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
  2. On the Service Home page, click the Create MariaDB (DBaaS) button. You will be taken to the Create MariaDB (DBaaS) page.
  3. 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.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, check the created 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

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

4-2. Adding IGW Firewall Rules

For detailed creation instructions, refer to the Networking > Firewall > How-to guides guide.
  1. Click the All Services > Networking > Firewall menu. Navigate to the Service Home page of Firewall.
  2. On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
  3. On the Firewall List page, select the Internet Gateway Resource Name created in 1-3. Internet Gateway 생성하기. You will be taken to the detailed information page for that resource.
  4. Click the Rules tab on the detail information page. You will be taken to the Rules tab.
  5. Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
  6. Add Rule In the popup window, enter the rule below, and click the Confirm button.
    origin addressDestination addressProtocolPortOperationdirectionExplanation
    Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
    Table. Internet Gateway Firewall rules that 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

  1. In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
  2. When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password verified in 2-3. 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

  1. Visit the official MySQL page and download the MySQL Workbench program.
  2. Connect the user’s PC hard drive to upload the file to the Bastion host.
  3. In the Local Resources tab of the Remote Desktop Connection, click the Details button of the Local Devices and Resources item.
  4. Select the local disk of the location where the file was downloaded on the drive, and click the OK button.
  5. Copy the downloaded file, upload it to the Bastion Host, and click the MySQL Workbench installer to install.

5-3. Connect to the Database using the DB client program (MySQL Workbench)

  1. Launch MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup appears.
  2. 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 fieldinput value
    Connection NameCustom (e.g., service name)
    Host nameDatabase server IP
    PortDatabase Port
    UsernameDatabase username
    Table. DB connection client program input fields
  3. 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.
  4. Click Database > Connect to Database. The Connect to Database popup window appears.
  5. 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

API Reference

3.4 - CLI Reference

CLI Reference

3.5 - Release Note

MariaDB(DBaaS)

2026.03.19
FEATURE Configure Replica for disaster recovery, add OS (Kernel) upgrade feature, provide Servicewatch integration feature
  • You can set up a disaster-recovery Replica using the Replica configuration (Other Region) feature.
  • Strengthen the latest security patches and stability through the OS(Kernel) upgrade feature.
  • You can monitor metrics and logs by integrating with Servicewatch.
2025.07.01
FEATURE User (access control) management, Archive configuration feature, DB Audit Log export feature addition, backup notification feature provision, migration feature addition
  • 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
    • DB Audit Log Export feature added
    • Backup Notification Feature provided
    • 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
2025.02.27
FEATURE Add server type and configure per-server IP, add Block Storage capacity expansion feature
  • 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.
  • Samsung Cloud Platform Common Feature Changes
    • Account, IAM, Service Home, tags, and other common CX changes have been reflected.
2024.10.01
NEW MariaDB(DBaaS) service official version launch
  • 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.
2024.07.02
NEW Beta version release
  • 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.

Architecture
Figure. MySQL (DBaaS) Architecture

Provided Features

MySQL(DBaaS) provides the following features.

  • Auto Provisioning (Auto Provisioning): Allows installation and configuration of Database(DB) via UI, and provides an Active-standby redundancy configuration based on storage replication. * When the active server fails, it automatically fails over to standby.
  • Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, you can restart if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, the user can manually perform node switching between Active and Standby via a switch‑over.
  • Backup and Recovery: Provides data backup functionality based on its own backup commands. * The backup schedule and retention policy can be set by the user, and additional fees apply based on the backup size. * It also provides a recovery function for backed‑up data, so when the user performs a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user (the backup save point or a user‑specified point). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour earlier, based on the stored backup and archive files.
  • Version Management: Provides a version upgrade (Minor) feature based on certain feature enhancements and security patches. * Whether to perform a backup for a version upgrade can be selected by the user, and if a backup is performed, the data is backed up before applying the patch, after which the DB engine is updated.
  • Replica configuration: Up to five Read Replicas can be configured in the same or different regions for read load balancing and disaster recovery (DR).
  • Parameter management: Performance improvements and security-related DB configuration parameters can be modified.
  • Service Status Query: Retrieves the current DB service’s final status.
  • Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
  • DB User Management: Query and manage the DB account (user) information registered in the DB.
  • DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
  • Archive Management: You can set the retention period (1~35 days) for Archive files on the DB server and configure the Archive mode (On/Off).
  • Export DB Log: You can export stored logs to the user’s Object Storage through Audit settings.
  • Migration: Synchronize data in real time with the live database and support migration using replication without service interruption.
  • OS Kernel Upgrade: The OS kernel can be upgraded to apply certain feature improvements and security patches.

Component

MySQL(DBaaS) provides pre‑validated engine versions and a variety of server types in accordance with the open‑source support policy. Users can select and use it based on the scale of the service they wish to configure.

Engine version

The engine versions supported by MySQL (DBaaS) are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.

Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.

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

The next version of MySQL is scheduled to be released after July 2026. The actual service delivery schedule is subject to change.

  • MySQL 8.4.7

Server type

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

For detailed information about the server types provided by MySQL(DBaaS), see MySQL(DBaaS) 서버 타입.

Standard db1v2m4
CategoryExampleDetailed description
Server typeStandardProvided server types
  • Standard: Standard configuration (vCPU, Memory) commonly used
  • High Capacity: Large server specifications of 24 vCores or more
Server specificationsdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) commonly used
  • dbH2: Large-capacity server specifications
    • Provides servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. MySQL(DBaaS) server type components

Preceding Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

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

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
exampleDetailed description
Server typeStandardProvided server type classifications
  • Standard: Configured with the commonly used standard specifications (vCPU, Memory)
  • High Capacity: Large-capacity server specifications exceeding Standard
Server specificationsdb1Provided server type classification and generation
  • db1: indicates a standard specification, and 1 denotes the generation
  • dbh2: h indicates a high-capacity server specification, and 2 denotes the generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. MySQL (DBaaS) server type format

db1 server type

The db1 server type of MySQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. MySQL (DBaaS) server type specifications - db1 server type

db2 server type

The db2 server type of MySQL (DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

  • Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb2v2m42 vCore4 GBUp to 10 Gbps
Standarddb2v2m82 vCore8 GBUp to 10 Gbps
Standarddb2v2m162 vCore16 GBUp to 10 Gbps
Standarddb2v2m242 vCore24 GBUp to 10 Gbps
Standarddb2v2m322 vCore32 GBUp to 10 Gbps
Standarddb2v4m84 vCore8 GBUp to 10 Gbps
Standarddb2v4m164 vCore16 GBUp to 10 Gbps
Standarddb2v4m324 vCore32 GBUp to 10 Gbps
Standarddb2v4m484 vCore48 GBUp to 10 Gbps
Standarddb2v4m644 vCore64 GBUp to 10 Gbps
Standarddb2v6m126 vCore12 GBUp to 10 Gbps
Standarddb2v6m246 vCore24 GBUp to 10 Gbps
Standarddb2v6m486 vCore48 GBUp to 10 Gbps
Standarddb2v726 vCore72 GBUp to 10 Gbps
Standarddb2v6m966 vCore96 GBUp to 10 Gbps
Standarddb2v8m168 vCore16 GBUp to 10 Gbps
Standarddb2v8m328 vCore32 GBUp to 10 Gbps
Standarddb2v8m648 vCore64 GBUp to 10 Gbps
Standarddb2v8m968 vCore96 GBUp to 10 Gbps
Standarddb2v8m1288 vCore128 GBUp to 10 Gbps
Standarddb2v10m2010 vCore20 GBUp to 10 Gbps
Standarddb2v10m4010 vCore40 GBUp to 10 Gbps
Standarddb2v10m8010 vCore80 GBUp to 10 Gbps
Standarddb2v10m12010 vCore120 GBUp to 10 Gbps
Standarddb2v10m16010 vCore160 GBUp to 10 Gbps
Standarddb2v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb2v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb2v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb2v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb2v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb2v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb2v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb2v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb2v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb2v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb2v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb2v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb2v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb2v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. MySQL (DBaaS) server type specifications - db2 server type

dbh2 server type

The dbh2 server type of MySQL (DBaaS) is offered with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.

  • Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
  • Supports up to 128 vCPUs and 1,536 GB of memory
  • Networking speed up to 25 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBMaximum 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBMaximum 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBMaximum 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBMaximum 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBUp to 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBMaximum 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBMaximum 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBMaximum 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBMaximum 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBMaximum 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBMaximum 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBMaximum 25 Gbps
Table. MySQL (DBaaS) server type specifications - dbh2 server type

4.1.2 - Monitoring metrics

Cloud Monitoring Service Termination Notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service, which was released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Services by Resource

    • New Resources: Resources created after the service improvement work in March 2026 are monitored by default using the ServiceWatch service.
    • Existing resources: After the service improvement work in September 2026 We provide monitoring in parallel using the Cloud Monitoring service and the ServiceWatch service.
    • During the parallel operation period, we must prepare for the Servicewatch transition. *
      Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e. You need to verify the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete the process.
  2. Cloud Monitoring Service Phased Termination Schedule Notice

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch: see the ServiceWatch 개요.

MySQL(DBaaS) Monitoring Metrics

The table below shows the performance monitoring metrics for MySQL (DBaaS) that can be viewed through Cloud Monitoring. For detailed Cloud Monitoring usage, refer to the Cloud Monitoring guide.

For MySQL (DBaaS) server monitoring metrics, please refer to the Virtual Server Monitoring Metrics guide.

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

4.1.3 - ServiceWatch Metrics

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

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

Basic Metrics

The following are the basic metrics for the namespace MySQL(DBaaS).

The indicators whose names are displayed in bold below are the key indicators selected from the basic metrics provided by MySQL(DBaaS). Key metrics are used to build service dashboards that are automatically created for each service in ServiceWatch.

Each metric guides users via the user guide on which statistical values are meaningful when viewing that metric, and among the meaningful statistics, the values displayed in bold are the primary statistics. In the service dashboard, you can view key metrics using the primary statistical values.

OS Basic Metrics

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

MySQL Basic Metrics

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

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.

Cloud Monitoring Service Termination Notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Service per Resource

    • New Resources: Resources created after the service improvement work in March 2026 are monitored by default using the ServiceWatch service.
    • Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
    • During the parallel operation period, you must prepare for the Servicewatch transition. *
      Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e.g. You must review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
  2. Notice of the phased termination schedule for Cloud Monitoring service

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch can be found in the ServiceWatch 개요.

Create MySQL (DBaaS)

You can create and use a MySQL (DBaaS) service from the Samsung Cloud Platform Console.

information
  • Before creating the service, configure the VPC’s subnet type as General.
    • If the subnet type is Local, the corresponding Database service cannot be created.
  • When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to a statistical collection environment.

To create a MySQL (DBaaS), follow the steps below.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the Create MySQL(DBaaS) button. 2. Go to the MySQL(DBaaS) Creation page.
  3. MySQL (DBaaS) Creation page: enter the information required to create the service and select detailed options.
    • Select the required information in the Image and version selection area.
      Category
      required status
      Detailed description
      Image versionEssentialProvide a list of MySQL (DBaaS) versions
      Table. MySQL (DBaaS) Image and version selection options
    • In the Service Information Input area, enter or select the required information.
      Category
      required status
      Detailed description
      Server name PrefixRequiredThe server name where the DB will be installed
      • starts with a lowercase English letter and uses lowercase letters, numbers, and the special character (-) to enter 3 to 13 characters
      • A postfix such as 001, 002 is appended based on the server name, creating the actual server name
      Cluster nameEssentialCluster name of DB servers
      • Enter using English letters, 3 ~ 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type for DB installation
      • Standard: standard specifications commonly used
      • High Capacity: large‑capacity server with 24 vCores or more
      Service Type > Planned ComputeSelectionStatus of resources with Planned Compute configured
      • In Use: Number of resources with Planned Compute configured that are currently in use
      • Configured: Number of resources with Planned Compute configured
      • Coverage Preview: Amount applied per resource by Planned Compute
      • Create Planned Compute Service: Navigate to the Planned Compute service request page
      Service Type > Block StorageRequiredBlock Storage configuration used by the DB according to its purpose
      • Basic OS: Area where the DB engine is installed
      • DATA: Storage area for table data, archive files, etc.
        • Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
          • SSD: High‑performance general volume
          • HDD: General volume
          • SSD_KMS, HDD_KMS: Additional encrypted volumes that use Samsung Cloud Platform KMS (Key Management System) encryption keys
        • The configured storage type is applied identically to additional storage
        • Capacity must be entered as a multiple of 8 within the range 16 to 5,120
        • Since executing SQL or monthly batch jobs can cause large sorts that may interrupt service, a separate TEMP storage must be allocated and used
      • Add: Storage areas for DATA, Archive, TEMP, Backup data
        • After selecting Use, enter the storage’s purpose and capacity
        • The storage type is applied the same as the type set for DATA, and capacity can be entered as a multiple of 8 within the range 16 to 5,120
        • To add storage, click the Add button; to delete, click the x button. Up to 9 can be added.
        • Temporarily store backup data in BACKUP storage before transmitting it
          • If the data to be backed up exceeds 100 GB and undergoes frequent changes, it is recommended to add a separate BACKUP storage for reliable backup. Set the backup capacity to about 60 % of the DATA capacity.
          • If a BACKUP storage is not added, the /tmp area is used, and backup will fail if capacity is insufficient
        • For each service, only one Block Storage is allocated for Archive, TEMP, and BACKUP
      Redundant configurationSelectRedundancy configuration
      • When redundancy is used, the DB instance is configured as separate Active DB and Standby DB
      Network > Common SettingsRequiredNetwork settings for servers created by the service
      • Select when you want to apply the same settings to all installed servers
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • IP can only be auto‑generated
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use is checked, you can select from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
      Network > Server-specific SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select when you want to apply different settings for each installed server
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • Enter the IP for each server
        • The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select from reserved IPs in the VPC product’s Public IP. For more information, see Public IP 생성하기
      IP access controlSelectService Access Policy Configuration
      • Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
      • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      maintenance periodSelectDatabase maintenance window
      • If you select Use, set the day of week, start time, and duration
      • It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruption
      • If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.
      Table. MySQL (DBaaS) Service Configuration Items
    • Enter required database configuration information In this section, enter or select the required information.
      Category
      Required status
      Detailed description
      Database nameRequiredServer name applied during DB installation
      • must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
      Database usernameRequiredDatabase user name
      • An account with the same name is also created on the OS
      • Enter using lowercase English letters, 2 to 20 characters
      • Restricted database user names can be viewed in the Console
      Database passwordrequiredPassword to use when accessing the DB
      • Enter 8 to 30 characters, including letters, numbers, and special characters (excluding )
      Database password verificationRequiredRe-enter the same password to use for DB access
      Database Port numberEssentialPort number required for DB connection
      • Enter DB port within the range 1200 ~ 65535
      Backup > UseSelectBackup usage
      • Use to select and set backup file retention period, backup start time, and Archive backup interval
      Backup > Retention periodSelectBackup retention period
      • Select the backup retention period. Set the file retention period from 7 days to 35 days
      • Backup files incur additional charges based on size
      Backup > Backup Start PeriodSelectBackup start time
      • Select backup start time
      • The minutes during which the backup runs (minutes) are set randomly, and the backup end time cannot be set
      Backup > Archive backup cycleSelectionArchive backup frequency
      • Select the archive backup frequency
      • The archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
      ParameterRequiredParameters to be used in the DB
      • Click the View button to view the parameter’s detailed information
      • Parameters can be modified after the DB creation is complete, and after modification the DB must be restarted
      DB character setRequiredCharacter encoding to use for the database
      Table case sensitivitySelectDB Table case sensitivity
      time zoneRequiredStandard time zone for the database
      ServiceWatch log collectionSelectionWhether to collect ServiceWatch logs
      • Select Use to enable the ServiceWatch log collection feature
      • Up to 5 GB is provided free of charge for all services within the account, and charges apply based on storage size for usage exceeding 5 GB
      • When collecting, log groups and log streams are created automatically, and they cannot be deleted until the resource is removed
      • To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
      Table. MySQL (DBaaS) Database configuration items
    • Additional Information Input area, please enter or select the required information.
      Category
      required status
      Detailed description
      TagSelectAdd Tag
      • Up to 50 per resource can be added
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. MySQL (DBaaS) additional information input fields
  4. Check the detailed information and estimated billing amount generated in the Summary panel, and click the Create button.
    • When creation is complete, check the created resources on the Resource List page.

View MySQL (DBaaS) detailed information

The MySQL (DBaaS) service allows you to view and edit the full list of resources and detailed information. MySQL(DBaaS) Details page consists of Details, Tags, Operation History tabs, and when the DB has a Replica configured, a Replica Information tab is added.

To view detailed information about the MySQL (DBaaS) service, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
  3. On the MySQL(DBaaS) List page, click the resource to view detailed information. 3. MySQL(DBaaS) Details Go to the page.
    • MySQL(DBaaS) Details At the top of the page, status information and additional feature details are displayed.
      CategoryDetailed description
      Cluster statusCluster status with DB installed
      • Creating: Cluster is being created
      • Editing: Cluster is transitioning to an operational state
      • Error: Cluster encountered a failure while performing a task
        • If this persists, contact the administrator
      • Failed: Cluster failed during creation
      • Restarting: Cluster is being restarted
      • Running: Cluster is operating normally
      • Starting: Cluster is starting
      • Stopped: Cluster is stopped
      • Stopping: Cluster is being stopped
      • Synchronizing: Cluster is synchronizing
      • Terminating: Cluster is being terminated
      • Unknown: Cluster status is unknown
        • If this persists, contact the administrator
      • Upgrading: Cluster is being upgraded
      Cluster controlButtons to change the cluster state
      • Start: Start a stopped cluster
      • Stop: Stop a running cluster
      • Restart: Restart a running cluster
      • Switch-Over: Switch a standby cluster to active
      More featuresCluster management buttons
      • Service status synchronization: Real-time DB service status lookup
      • Backup history: When backup is configured, verify whether backups run correctly and view the history
      • Database recovery: Recover the DB based on a specific point in time
      • Parameter management: View and modify DB configuration parameters
      • Replica configuration: Set up a read‑only Replica cluster
      • Replica configuration (Other-Region): Set up a disaster‑recovery Replica in another region; the button is disabled if the account has no region to configure
      • DB user management: View and manage DB account (user) information registered in the DB
      • DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB
      • Archive management: Set archive file retention periods and configure archive mode
      • DB Log export: Export stored logs to the user’s Object Storage via audit settings
      • Migration configuration: Provides migration functionality using replication
      • OS (Kernel) upgrade: Upgrade the OS kernel version
      Service terminationCancel service button
      Table. MySQL (DBaaS) status information and additional features

Detailed information

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

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

Replica information

Replica Information tab is enabled only when a Replica is configured in the cluster. Replica information tab allows you to view the Master cluster name, replica count, and Replica status.

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

tag

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

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

Work History

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

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

Managing MySQL(DBaaS) Resources

If you need to change or restore the existing configuration options of a provisioned MySQL (DBaaS) resource, or set up a replica, you can perform the tasks on the MySQL(DBaaS) Detailed Information page.

Control operation

If changes occur to a running MySQL (DBaaS) resource, you can start, stop, or restart it. Additionally, when HA is configured, you can switch the Active‑Standby servers using a switch‑over.

To control the operation of MySQL (DBaaS), follow the steps below.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List page, click the resource to control its operation. 3. MySQL(DBaaS) Details Go to the page.
  4. Check the MySQL (DBaaS) status and complete the change using the control button below.
    • Start: DB service is installed on the server and the DB service is running (Running).
    • Stop: The server where the DB service is installed and the DB service are stopped (Stopped).
    • Restart: Only the DB service will be restarted.
    • Switch Over: You can switch the DB’s Active server and Standby server.

Synchronize Service Status

You can synchronize the real-time service status of MySQL (DBaaS).

To check the service status of MySQL (DBaaS), follow the steps below.

  1. Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
  3. MySQL (DBaaS) List page, click the resource to view its service status. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
  5. When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.

Change server type

You can change the configured server type.

To change the server type, follow these steps.

Caution
  • If you modify the server type, a server restart is required. * Please separately verify any software license modifications or software settings and their implementation due to specification changes.
  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List page: click the resource for which you want to change the server type. 3. Navigate to the MySQL (DBaaS) Details page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
  5. Server Type Edit After selecting the server type in the popup window, click the Confirm button.

Add storage

If you need more than 5 TB of data storage, you can add additional storage. For a redundant DB configuration, all redundant servers are added simultaneously.

Caution
  • It is applied in the same way as the Storage type selected when creating the service.
  • In a high‑availability configured database, adding storage is applied simultaneously to the storage of both the active and standby databases.
  • If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. * Please expand the Replica storage first, then expand the Master cluster storage.
  • When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.

To add storage, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource to add storage. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
  5. Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.

Expanding storage

Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.

To expand storage capacity, follow the steps below.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
  3. MySQL(DBaaS) List page, click the resource whose server type you want to change. 3. MySQL(DBaaS) Details Go to the page.
  4. Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
  5. Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.

Cancel MySQL (DBaaS)

You can cancel unused MySQL (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact that may occur when the service is discontinued.

Caution
  • For a DB with a Replica configured, terminating the Master DB does not delete the Replica. * If you also delete the replica, please cancel it separately from the resource list.
  • If you terminate the DB, all stored data and any configured backup data will be deleted.

To cancel MySQL (DBaaS), follow the steps below.

  1. Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
  3. On the MySQL(DBaaS) List page, select the resource to cancel and click the Cancel Service button.
  4. After termination is complete, check on the MySQL(DBaaS) list page whether the resource has been terminated.

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.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. Click the resource you want to view or modify parameters for on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
  5. Parameter Management popup window, click the Search button. The Search Notification popup window opens.
  6. Lookup Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.

Modify Parameter

To modify the configuration parameters, follow these steps.

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

If you change the character_set_server value, first verify the collation that matches the character set using the command below.

SQL> SHOW COLLATION WHERE Charset = 'character set name';

Set the parameter values for character-set-server, collation-server, and init_connect with the confirmed collation.

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

Managing DB Users

Provides management functions to retrieve DB user information and modify status information.

Query DB users

To retrieve DB users, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource for which you want to view DB users. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
  5. On the DB User Management page, click the Search button. Retrieving the data may take a moment.

Changing DB User Status

Follow these steps to change the status of the retrieved DB user.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the MySQL(DBaaS) Service Home page.
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) list page.
  3. On the MySQL(DBaaS) List page, click the resource for which you want to modify the DB user. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button, then click the DB User Management button. You will be directed to the DB User Management page.
  5. On the DB User Management page, click the Search button. The query may take a short time.
  6. If modification is needed, click the Edit button, and change the status field value or enter remarks.
  7. When the input is complete, click the Complete button.

Managing DB Access Control

Provides IP-based DB user access control management functionality. Users can directly specify the IPs that can access the database, configuring it so that only authorized IPs are allowed access.

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

Query DB Access Control

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

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List page, click the resource you want to manage access control for. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. On the DB Access Control Management page, click the Search button. Retrieving the data may take a moment.

Add DB access control

To add IP access control, follow these steps.

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

Delete DB access control

To delete IP access control, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource for which you want to delete IP access control. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
  5. On the DB Access Control Management page, click the View button. Retrieving the data may take a short while.
  6. When the query is complete, click the Delete button. The Delete popup window opens.
  7. In the Delete popup window, click the Confirm button.

Manage Archive

Provides the ability to configure Archive mode and set the retention period for Archive logs, allowing users to flexibly configure Archive log management policies to suit their operational environment. Additionally, it provides a feature to manually delete Archive logs, allowing you to clean up unnecessary log data and manage system resources effectively.

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

Configure Archive mode

To set Archive mode, follow these steps.

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

Delete Archive file

To delete the Archive file, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource for which you want to set Archive mode. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
  5. On the Archive Settings Management page, if you want to delete all Archive files, click Delete All Archives; if you only want to delete the backed‑up Archive files, click the Delete Backed‑up Archive button.

DB Log Export

Supports exporting log data that requires long-term retention among audit logs to Object Storage. Users can directly configure the log types to be stored, the target bucket for export, and the export interval. Based on the configured criteria, logs are copied to the specified Object Storage for retention. Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for long-term storage.

information
  • To use the DB Log export function, you need to create an Object Storage. For creating Object Storage, please refer to the Object Storage User Guide.
  • Please be sure to check the expiration date and time of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
  • Please ensure that authentication key information is not exposed externally.

Setting DB Log Export Mode

To set the DB Log export mode, follow these steps.

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

Managing DB Log Export

To modify, cancel, or immediately export the DB Log export settings, follow these steps.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource you want to manage DB Log export for. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button and then click the Export DB Log button. You will be taken to the Export DB Log page.
  5. On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, Cancel buttons.
    • Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
    • Edit: Modify the DB Log export mode setting.
    • Cancel: Disables the DB Log export mode setting.

Minor Version Upgrade

We provide version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades within the same Major version are supported.

Warning
  • First retrieve the service status by synchronizing it, then perform the version upgrade.
  • Please perform the version upgrade after configuring a backup. If you do not set up a backup, you may be unable to recover some data if a problem occurs during the update.
  • In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. Please check the Replica version first and, if necessary, perform a version upgrade.
  • The backed-up data will be automatically deleted after the version upgrade is completed.

To upgrade the version, follow these steps.

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

Configure Migration

Provides a Migration feature that synchronizes in real time with the live database and replicates using a Replication method without service interruption.

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

To configure Migration, follow these steps.

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

Promote Migration Cluster to Master Cluster

You can promote a configured Migration Cluster to a Master Cluster.

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

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

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource to promote to Master. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button, then click the Master promotion button. The Master promotion notification popup opens.
  5. In the Master Promotion Notification popup, click the Confirm button.

Upgrade OS Kernel

The OS kernel can be upgraded to improve the functionality of the running database and apply security patches.

Caution
  • The service will be unavailable while the OS upgrade is in progress.
  • The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
  • After the upgrade is complete, you cannot revert to the previous OS.

To upgrade the OS Kernel, follow the steps below.

  1. Click the All Services > Database > MySQL(DBaaS) menu. Navigate to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. You will be taken to the MySQL(DBaaS) List page.
  3. On the MySQL(DBaaS) List page, click the resource to upgrade the OS Kernel. You will be taken to the MySQL(DBaaS) Details page.
  4. Click the More button, then click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup opens.
  5. OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.

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.

Caution
  • For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity. * Especially when the backup data exceeds 100 GB and undergoes frequent changes, please secure additional storage amounting to about 60 % of the data size. * For instructions on adding and expanding storage, please refer to the MySQL(DBaaS) Add Storage, MySQL(DBaaS) Expand Storage guides.
  • If a backup is configured, it will run at the designated time after the set time, and additional fees will be incurred based on the backup size.
  • If you change the backup setting to unset, backup execution stops immediately, and the stored backup data is deleted and can no longer be used.

To set up a backup, follow these steps.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Navigate to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List page, click the resource for which you want to configure backup. 3. MySQL(DBaaS) Details Go to the page.
  4. Click the Edit button of the backup item. 4. Backup Settings popup window opens.
  5. When configuring a backup, click Enable in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
    • If you wish to stop the backup configuration, deselect Backup Settings in the Use popup and authenticate via the logged-in user’s mobile phone.
      When user authentication is complete, the backup configuration is disabled and backup execution stops.

Check backup history

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

To view the backup history, follow these steps.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL (DBaaS) List Navigate to the page.
  3. MySQL(DBaaS) List On the page, click the resource for which you want to view the backup history. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.

Delete backup files

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

To delete the backup history, follow these steps.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. Go to the MySQL(DBaaS) List page.
  3. MySQL(DBaaS) List On the page, click the resource to view the backup history. 3. MySQL(DBaaS) Details Go to the page.
  4. Click the Backup History button. 4. Backup History popup window opens.
  5. Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
    • When user authentication is completed, the backup file is deleted.

MySQL(DBaaS) Recover

When a failure or data loss requires restoration from a backup file, the recovery feature enables point‑in‑time restoration. When performing a MySQL (DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the DB is installed with the version from the backup point, and the recovery proceeds with the DB’s configuration information and data.

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

To recover MySQL (DBaaS), follow these steps.

  1. Click the All Services > Database > MySQL (DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Go to the page.
  3. MySQL(DBaaS) resource On the list page, click the resource you want to restore. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Database Recovery button. 4. Go to the Database Recovery page.
  5. Database Recovery Configuration after entering the relevant information in the area, click the Complete button.
    Category
    required status
    Detailed description
    Recovery TypeRequiredSet the point in time the user wants to recover
    • Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
    • Custom point: Recover to a user-specified point within the range of recoverable backup times. The recoverable period depends on the Archive backup cycle setting, allowing recovery from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the desired date and time for the backup
    Server name prefixRequiredServer name of the recovery DB
    • Start with a lowercase English letter and use lowercase letters, numbers, and special characters (-) to enter 3 to 16 characters
    • Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
    Cluster nameRequiredCluster name of the recovery DB
    • Enter using English letters, 3 ~ 20 characters
    • A cluster is a unit that groups multiple servers
    Service Type > Server TypeRequiredServer type for the recovery DB installation
    • Standard: Standard specification commonly used
    • High Capacity: Large-capacity server with 24 vCores or more (to be provided later)
    Service Type > Planned ComputeSelectionStatus of resources with Planned Compute configured
    • In Use: Number of resources with Planned Compute that are currently in use
    • Configured: Number of resources with Planned Compute configured
    • Coverage Preview: Amount applied per resource by Planned Compute
    • Create Planned Compute Service: Navigate to the Planned Compute service application page
    Service Type > Block StorageRequiredBlock Storage settings used by the recovery DB
    • Basic OS: Area where the DB engine is installed
    • DATA: Storage area for table data, archive files, etc.
      • Applied identically with the storage type set in the source cluster
      • Enter capacity as a multiple of 8 within the range 16 to 5,120
    • Additional: Storage area for DATA, Archive, TEMP, Backup data
      • Applied identically with the storage type set in the source cluster
      • In the recovery DB, only DATA, TEMP, and Archive purposes can be added
      • After selecting Use, enter the storage purpose and capacity
      • To add storage, click the Add button; to delete, click the x button
      • Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
      • ___HTML_MARKER***
    Database usernameRequiredDatabase username configured in the source DB
    Database Port numberRequiredDatabase port number configured in the source DB
    IP access controlSelectIP address for accessing the recovery DB
    • Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.1/32, 192.168.10.1/32), then click the Add button
    • To delete an entered IP, click the x button next to the entered IP
    maintenance periodSelectDatabase maintenance window
    • If you select Use, set the day, start time, and duration
    • It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruption
    • If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
    tagSelectAdd Tag
    • Add Tag button after clicking, enter or select Key, Value values
    Table. MySQL (DBaaS) recovery configuration items

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.

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

To configure a Replica, follow these steps.

  1. All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
  3. On the MySQL(DBaaS) List page, click the resource to configure a Replica. 3. MySQL(DBaaS) Details Navigate to the page.
  4. Click the Replica configuration button. 4. Go to the Replica configuration page.
  5. After entering information in the Replica configuration area, click the Done button.
    Category
    required status
    Detailed description
    RegionrequiredRegion to configure the Replica
    • Replica configuration (Other Region) is displayed only when selected
    Replica countRequiredNumber of Replicas to configure
    • Up to 5 can be configured per cluster
    • If you select more than one value, additionally enter the Replica name and service type information
    Replica nameRequiredReplica server name
    • Start with a lowercase English letter, and use lowercase letters, numbers, and special characters (-) to enter 3 to 19 characters
    • The entered Replica name is displayed as the cluster name in the list
    Service Type > Server TypeRequiredReplica server type
    • Standard: standard specification commonly used
    • High Capacity: large-capacity server with 24 vCores or more
    Service Type > Planned ComputeSelectionStatus of resources with Planned Compute configured
    • In Use: Number of resources with Planned Compute configured that are currently in use
    • Configured: Number of resources with Planned Compute configured
    • Coverage Preview: Amount applied per resource by Planned Compute
    • Create Planned Compute Service: Navigate to the Planned Compute service application page
    IP access controlSelectService Access Policy Configuration
    • Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
    • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
    • To delete an entered IP, click the x button next to the entered IP
    maintenance periodSelectDatabase maintenance window
    • If you select Use, set the day of week, start time, and duration
    • It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruptions
    • If set to unused, we are not responsible for issues arising from patches not being applied.
    TagSelectAdd Tag
    • Add Tag after clicking the button, enter or select Key, Value values
    Table. MySQL (DBaaS) Replica configuration items

Reconfigure Replica

If a network outage or replication delay with the Master Cluster occurs, you can use the Replica reconstruction function to replicate the Master Cluster’s data again.

To reconfigure the Replica, follow the steps below.

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

Promoting a Replica Cluster to a Master Cluster

You can promote a configured Replica Cluster to a Master Cluster.

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

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

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

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.

Architecture
Figure. MySQL (DBaaS) server connection architecture

Scenario components

You can build the scenario using the following services.

Service group
service
Detailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
NetworkingVPC > SubnetA service that lets users subdivide the network within a VPC to match their purpose and scale.
NetworkingVPC > Public IPA service that reserves a public IP and allocates and releases it to Compute resources
NetworkingVPC > Internet GatewayA service that connects VPC resources to the Internet
NetworkingSecurity GroupVirtual firewall that controls server traffic
DatabaseMySQL(DBaaS)A service that easily creates and manages MySQL in a web environment
ComputeVirtual ServerVirtual server optimized for cloud computing
ComputeVirtual Server > KeypairEncryption file used to connect to the Virtual Server
Table. Scenario component list
Reference
  • Since the default policy of a Security Group is Deny All, you must register only the allowed IPs.
  • The All Open (Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
    • By specifying the required IP and port and setting a policy, you can strengthen security.

Scenario configuration method

Create the services needed to build the scenario by following the steps below.

Set up the network

Describes the process of configuring the network environment for accessing the Bastion Host and Database services.

1-1. Create VPC

For detailed creation steps, refer to the Networking > VPC > How-to guides guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
  2. Click the VPC Creation button on the Service Home page. You will be taken to the VPC Creation page.
  3. On the VPC Creation page, enter the information required to create the service.
    • Enter the IP range as 192.168.x.0/16.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resources on the VPC List page.

1-2. Create Subnet

For detailed creation steps, refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
  2. On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
  3. Click the Create Subnet button. You will be taken to the Create Subnet page.
  4. On the Subnet Creation page, enter the information required to create the service.
    • Select the Subnet type as General.
    • Select a pre‑created VPC.
    • Enter the IP range as 192.168.x.0/24.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • When creation is complete, verify the created resources on the Subnet list page.

1-3. Create Internet Gateway

For detailed creation steps, please refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click the All Services > Networking > VPC menu. Go to the VPC’s Service Home page.
  2. On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
  3. Click the Create Internet Gateway button. You will be taken to the Create Internet Gateway page.
  4. On the Internet Gateway Creation page, enter the required information to create the service.
    • Select a pre‑created VPC.
    • In the Firewall usage option, select Use.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the Internet Gateway List page.

1-4. Create Public IP

For detailed creation steps, refer to the Networking > VPC > How-to guides > Public IP guide.
  1. Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
  2. On the Service Home page, click the Public IP menu. You will be taken to the Public IP List page.
  3. Click the Public IP Reservation button. You will be taken to the Public IP Reservation page.
  4. On the Public IP reservation page, enter the required information to reserve the service.
  5. In the Summary panel, verify the detailed information and estimated billing amount you generated, and click the Complete button.
    • When creation is complete, check the created resources on the Public IP List page.

1-5. Create Security Group

For detailed creation instructions, refer to the Networking > Security Group > How-to guides guide.
  1. Click the All Services > Networking > Security Group menu. You will be taken to the Service Home page of the Security Group.
  2. Click the Create Security Group button on the Service Home page. You will be taken to the Create Security Group page.
  3. On the Security Group creation page, enter the required information for creating the service.
  4. Check the input information and click the Complete button.
    • When creation is complete, verify the created resource on the Security Group List page.

Create Bastion host

This explains the process of configuring a Bastion Host where the Database access client must be installed.

2-1. Create Server Keypair

For detailed creation instructions, refer to the Compute > Virtual Server > How-to guides > Keypair guide.
  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
  3. Click the Create Keypair button. You will be taken to the Create Keypair page.
  4. Enter the required information needed to create a service on the Keypair creation page.
  5. Check the creation information and click the Complete button.
    • The key can be downloaded only on the first attempt, and reissuance is not available.
    • Please store the downloaded key in a secure location.

2-2. Create Bastion host

For detailed creation instructions, see the Compute > Virtual Server > How-to guides guide.
  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Create Virtual Server button. You will be taken to the Create Virtual Server page.
  3. On the Virtual Server Creation page, enter the required information to create the service.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, check the created resources on the Virtual Server List page.

2-3. Bastion host Check login ID and PW

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

Create Database

Explains the process of creating a Database service.

3-1. Create MySQL(DBaaS) Service

For detailed creation steps, refer to the Database > MySQL(DBaaS) > How-to guides guide.
  1. Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
  2. On the Service Home page, click the MySQL(DBaaS) Create button. You will be taken to the MySQL(DBaaS) Create page.
  3. On the MySQL(DBaaS) Creation page, enter the required information needed to create the service.
    • Select the pre‑created VPC and Subnet and connect them.
    • Enter the database-related creation details on the required information input screen.
    • Add the Bastion host IP in the IP access control settings.
    • The Database Port defaults to 2866, but the user can also specify it.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • Once creation is complete, check the created resource on the MySQL(DBaaS) list page.

Configure Rules

It explains the process of configuring rules for a user to connect to the Bastion host and rules for connecting to the Database from the Bastion host.

4-1. Adding security rules to Security Group

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

4-2. Adding IGW Firewall Rule

For detailed creation instructions, see the Networking > Firewall > How-to guides guide.
  1. All Services > Networking > Firewall Click the menu. Go to the Service Home page of the Firewall.
  2. On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
  3. On the Firewall List page, select the Internet Gateway resource name created in 1-3. Create Internet Gateway. You will be taken to the detailed information page of that resource.
  4. Click the Rules tab on the detail page. You will be taken to the Rules tab.
  5. Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
  6. Add Rule In the popup window, enter the rule below, and click the Confirm button.
    origin addressDestination addressProtocolPortoperationdirectionExplanation
    Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
    Table. Internet Gateway Firewall rules that should be added

Connect to Database

Describes the process of a user accessing the database via a DB client program.

This guide explains how to connect using MySQL Workbench. Since there are various database client programs and CLI utilities, you may install and use the tool that best fits your needs.

5-1. Connecting to Bastion host

  1. In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
  2. When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password verified in 2-3. Check the Bastion host access ID and PW and click the Confirm button.

5-2. Install DB access client program (MySQL Workbench) on the Bastion host

  1. Visit the official MySQL page and download the MySQL Workbench program.
  2. Connect the user’s PC hard drive to upload the file to the Bastion host.
  3. In the Local Resources tab of the Remote Desktop Connection, click the Details button of the Local Devices and Resources item.
  4. Select the local disk where the file was downloaded on the drive, and click the OK button.
  5. Copy the downloaded file, upload it to the Bastion Host, and click the MySQL Workbench installer to install.

5-3. Connect to the Database using the DB client program (MySQL Workbench)

  1. Launch MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup appears.
  2. Manage Server Connection In the popup window, click the New button at the lower left, enter the Database server information created in 3-1. MySQL(DBaaS) 서비스 생성하기, and click the Test Connection button. A Password popup will appear.
    Required input fieldinput value
    Connection NameCustom (ex. service name)
    Host nameDatabase server IP
    PortDatabase Port
    UsernameDatabase username
    Table.DB connection client program input fields
  3. In the Password popup, enter the password you set in 3-1. MySQL(DBaaS) Create Service and click the OK button. When the operation completes successfully, click the OK button in the Manage Server Connection popup.
  4. Click Database > Connect to Database. The Connect to Database popup appears.
  5. Select the Connection Name registered in Stored Connection to perform a Database connection. After connecting, you can try simple Query, etc.

4.3 - API Reference

API Reference

4.4 - CLI Reference

CLI Reference

4.5 - Release Note

MySQL(DBaaS)

2026.03.19
FEATURE Configure Replica for disaster recovery, add OS (Kernel) upgrade feature, provide Servicewatch integration feature
  • You can set up a disaster-recovery Replica using the Replica configuration (Other Region) feature.
  • Strengthen the latest security patches and stability through the OS (Kernel) upgrade feature.
  • You can monitor metrics and logs by integrating with Servicewatch.
2025.07.01
FEATURE User (access control) management, Archive configuration feature, DB Audit Log export feature added, backup notification feature provided, migration feature added
  • Add MySQL (DBaaS) feature
2025.02.27
FEATURE Add server type and per‑server IP setting, add Block Storage capacity expansion feature
  • MySQL (DBaaS) feature change
    • Add second-generation server type
      • Add a 2nd‑generation (dbh2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, see mysql(DBaaS) 서버 타입.
    • After the service is created, you can expand the configured Block Storage capacity.
    • Server-specific network IP configuration feature added allows common or server-specific settings depending on the usage purpose.
  • Samsung Cloud Platform common feature changes
    • Account, IAM, Service Home, tags, and other common CX changes have been applied.
2024.10.01
NEW MySQL(DBaaS) service official version release
  • A MySQL (DBaaS) service that enables easy creation and management of MariaDB in a web environment has been released.

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.

Provided versionEOS Date (Samsung Cloud Platform new creation stop date)EoTS Date (Community technical support end date)
Microsoft SQL Server 2019 Enterprise2029-06 (planned)2030-01-08(Extended Support)
2025-02-28(Standard Support)
Microsoft SQL Server 2019 Standard2029-06 (planned)2030-01-08(Extended Support)
2025-02-28(Standard Support)
Microsoft SQL Server 2022 Enterprise2032-06 (planned)2033-01-11(Extended Support)
2028-01-11(Standard Support)
Microsoft SQL Server 2022 Standard2032-06 (planned)2033-01-11(Extended Support)
2028-01-11(Standard Support)
Table. Engine versions provided by Microsoft SQL Server(DBaaS)

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
CategoryexampleDetailed description
Server typeStandardProvided server types
  • Standard: Standard configuration (vCPU, Memory) commonly used
  • High Capacity: Large server specifications with 24 vCores or more
Server specificationsdb1Provided server specifications
  • db1: Standard specifications (vCPU, Memory) commonly used
  • dbh2: Large-capacity server specifications
    • Provides servers with 24 vCores or more
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. Microsoft SQL Server(DBaaS) server type components

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 CategoryserviceDetailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
Table. Microsoft SQL Server(DBaaS) required services

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
exampleDetailed description
Server typeStandardProvided server type classifications
  • Standard: Configured with the commonly used standard specifications (vCPU, Memory)
  • High Capacity: Large-capacity server specifications exceeding Standard
Server specificationsdb1Provided server type classification and generation
  • db1: means a standard specification, and 1 indicates the generation
  • dbh2: h indicates a high-capacity server specification, and 2 indicates the generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. Microsoft SQL Server (DBaaS) server type format

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb1v2m42 vCore4 GBUp to 10 Gbps
Standarddb1v2m82 vCore8 GBUp to 10 Gbps
Standarddb1v2m162 vCore16 GBUp to 10 Gbps
Standarddb1v2m242 vCore24 GBUp to 10 Gbps
Standarddb1v2m322 vCore32 GBUp to 10 Gbps
Standarddb1v4m84 vCore8 GBUp to 10 Gbps
Standarddb1v4m164 vCore16 GBUp to 10 Gbps
Standarddb1v4m324 vCore32 GBUp to 10 Gbps
Standarddb1v4m484 vCore48 GBUp to 10 Gbps
Standarddb1v4m644 vCore64 GBUp to 10 Gbps
Standarddb1v6m126 vCore12 GBUp to 10 Gbps
Standarddb1v6m246 vCore24 GBUp to 10 Gbps
Standarddb1v6m486 vCore48 GBUp to 10 Gbps
Standarddb1v6m726 vCore72 GBUp to 10 Gbps
Standarddb1v6m966 vCore96 GBUp to 10 Gbps
Standarddb1v8m168 vCore16 GBUp to 10 Gbps
Standarddb1v8m328 vCore32 GBUp to 10 Gbps
Standarddb1v8m648 vCore64 GBUp to 10 Gbps
Standarddb1v8m968 vCore96 GBUp to 10 Gbps
Standarddb1v8m1288 vCore128 GBUp to 10 Gbps
Standarddb1v10m2010 vCore20 GBUp to 10 Gbps
Standarddb1v10m4010 vCore40 GBUp to 10 Gbps
Standarddb1v10m8010 vCore80 GBUp to 10 Gbps
Standarddb1v10m12010 vCore120 GBUp to 10 Gbps
Standarddb1v10m16010 vCore160 GBUp to 10 Gbps
Standarddb1v12m2412 vCore24 GBMaximum 12.5 Gbps
Standarddb1v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb1v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb1v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb1v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb1v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb1v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb1v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb1v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb1v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb1v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb1v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb1v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb1v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. Microsoft SQL Server (DBaaS) server type specifications - db1 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standarddb2v2m42 vCore4 GBUp to 10 Gbps
Standarddb2v8m82 vCore8 GBUp to 10 Gbps
Standarddb2v2m162 vCore16 GBUp to 10 Gbps
Standarddb2v2m242 vCore24 GBUp to 10 Gbps
Standarddb2v2m322 vCore32 GBUp to 10 Gbps
Standarddb2v4m84 vCore8 GBUp to 10 Gbps
Standarddb2v4m164 vCore16 GBUp to 10 Gbps
Standarddb2v4m324 vCore32 GBUp to 10 Gbps
Standarddb2v4m484 vCore48 GBUp to 10 Gbps
Standarddb2v4m644 vCore64 GBUp to 10 Gbps
Standarddb2v6m126 vCore12 GBUp to 10 Gbps
Standarddb2v6m246 vCore24 GBUp to 10 Gbps
Standarddb2v6m486 vCore48 GBUp to 10 Gbps
Standarddb2v726 vCore72 GBUp to 10 Gbps
Standarddb2v6m966 vCore96 GBUp to 10 Gbps
Standarddb2v8m168 vCore16 GBUp to 10 Gbps
Standarddb2v8m328 vCore32 GBUp to 10 Gbps
Standarddb2v8m648 vCore64 GBUp to 10 Gbps
Standarddb2v8m968 vCore96 GBUp to 10 Gbps
Standarddb2v8m1288 vCore128 GBUp to 10 Gbps
Standarddb2v10m2010 vCore20 GBUp to 10 Gbps
Standarddb2v10m4010 vCore40 GBUp to 10 Gbps
Standarddb2v10m8010 vCore80 GBUp to 10 Gbps
Standarddb2v10m12010 vCore120 GBUp to 10 Gbps
Standarddb2v10m16010 vCore160 GBUp to 10 Gbps
Standarddb2v12m2412 vCore24 GBUp to 12.5 Gbps
Standarddb2v12m4812 vCore48 GBUp to 12.5 Gbps
Standarddb2v12m9612 vCore96 GBUp to 12.5 Gbps
Standarddb2v12m14412 vCore144 GBUp to 12.5 Gbps
Standarddb2v12m19212 vCore192 GBUp to 12.5 Gbps
Standarddb2v14m2814 vCore28 GBUp to 12.5 Gbps
Standarddb2v14m5614 vCore56 GBUp to 12.5 Gbps
Standarddb2v14m11214 vCore112 GBUp to 12.5 Gbps
Standarddb2v14m16814 vCore168 GBUp to 12.5 Gbps
Standarddb2v14m22414 vCore224 GBUp to 12.5 Gbps
Standarddb2v16m3216 vCore32 GBUp to 12.5 Gbps
Standarddb2v16m6416 vCore64 GBUp to 12.5 Gbps
Standarddb2v16m12816 vCore128 GBUp to 12.5 Gbps
Standarddb2v16m19216 vCore192 GBUp to 12.5 Gbps
Standarddb2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. Microsoft SQL Server (DBaaS) server type specifications - db2 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacitydbh2v24m4824 vCore48 GBMaximum 25 Gbps
High Capacitydbh2v24m9624 vCore96 GBMaximum 25 Gbps
High Capacitydbh2v24m19224 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v24m28824 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v32m6432 vCore64 GBUp to 25 Gbps
High Capacitydbh2v32m12832 vCore128 GBMaximum 25 Gbps
High Capacitydbh2v32m25632 vCore256 GBMaximum 25 Gbps
High Capacitydbh2v32m38432 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v48m19248 vCore192 GBMaximum 25 Gbps
High Capacitydbh2v48m57648 vCore576 GBMaximum 25 Gbps
High Capacitydbh2v64m25664 vCore256 GBMaximum 25 Gbps
High Capacitydbh2v64m76864 vCore768 GBMaximum 25 Gbps
High Capacitydbh2v72m28872 vCore288 GBMaximum 25 Gbps
High Capacitydbh2v72m86472 vCore864 GBMaximum 25 Gbps
High Capacitydbh2v96m38496 vCore384 GBMaximum 25 Gbps
High Capacitydbh2v96m115296 vCore1152 GBMaximum 25 Gbps
High Capacitydbh2v128m512128 vCore512 GBMaximum 25 Gbps
High Capacitydbh2v128m1536128 vCore1536 GBMaximum 25 Gbps
Table. Microsoft SQL Server (DBaaS) server type specifications - dbh2 server type

5.1.2 - Monitoring metrics

Cloud Monitoring Service Termination Notice

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.

  1. 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.
  2. 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.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch 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 itemsDetailed descriptionunit
Active LocksNumber of Active Lockscnt
Active SessionsNumber of Sessions in Active statecnt
Active Transactions [Total]Number of active transactionscnt
Blocking Session IDLong-running query (slow query)ID
Connected UsersNumber of users connected to the systemcnt
Datavolume Size [Free]Available spacebytes
DBFiles [Not Online]Run a query to verify that all data files are ONLINE.cnt
Instance State [Cluster]Status during MSSQL cluster configurationstate
Instance State [PID]sqlservr.exe process pidPID
Lock Processes [Blocked]Number of SQL processes blocked by other processescnt
Lock Waits [Per Second]Lock wait count per secondcnt
Page IO Latch Wait TimePage IO latch waits average wait timems
SlowqueriesNumber of SQL queries running for a long time (over 5 minutes)cnt
Slowquery CPU TimeCPU time spent executing SQL that runs for a long time (over 5 minutes)ms
Slowquery Execute Context IDContext ID linked to the execution task of a SQL that has been running for a long time (over 5 minutes)ID
Slowquery Memory UsageMemory usage incurred by the execution of SQL that runs for a long time (over 5 minutes)bytes
Slowquery Session IDSession ID of SQL queries running for a long time (over 5 minutes)ID
Slowquery Wait Duration TimeTotal wait time for wait typems
Tablespace UsedData volume sizebytes
Transaction Time [MAX]Long-running transactioncnt
Table. Microsoft SQL Server (DBaaS) Monitoring Metrics

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.

Cloud Monitoring service termination notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Service per Resource

    • New Resources: Resources created after the service improvement work in 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.
  2. Notice of the phased termination schedule for Cloud Monitoring service

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (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**.

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.

Information

Before creating the service, configure the VPC’s subnet type as General.

  • If the subnet type is Local, the corresponding Database service cannot be created.

To create a Microsoft SQL Server (DBaaS), follow the steps below.

  1. Click the All Services > Database > Microsoft SQL Server (DBaaS) menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) Create button. 2. Go to the Microsoft SQL Server(DBaaS) Create page.
  3. 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 status
      Detailed description
      Image versionRequiredProvide 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 status
      Detailed description
      Server name PrefixRequiredServer 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 nameRequiredCluster name of DB servers
      • Enter in English using 3 to 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type for DB installation
      • Standard: Standard specification commonly used
      • High Capacity: Large-capacity server with 24 vCores or more
      Service Type > Planned ComputeSelectStatus 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
      Service Type > Block StoragerequiredBlock 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
          Additional: Data storage area
          • After selecting Use, enter the storage’s purpose and capacity
          Click the Add button to add storage, or click the x button to delete
        • Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
      Redundant configurationSelectRedundancy configuration status
      • When redundancy configuration is used, the DB instance is set up as an Active DB and a Standby DB
      Network > Common SettingsRequiredNetwork 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 SettingsRequiredNetwork 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 controlSelectionService Access Policy Configuration
      • Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
      • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
      • To delete an entered IP, click the x button next to the entered IP
      maintenance periodSelectDatabase maintenance window
      • If you select Use, set the day of week, start time, and duration
      • It is recommended to set a maintenance window for stable management of the DB. Patch operations will be performed at the scheduled time, causing service interruption
      • If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.
      Table. Microsoft SQL Server(DBaaS) Service Configuration Items
    • Please enter or select the required information in the Enter required database configuration information area.
      Category
      required status
      Detailed description
      Database service nameRequiredDatabase management unit name
      • Starts with an uppercase English letter and uses English characters, input 1 ~ 15
      Database name > defaultRequiredServer 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 > AddRequiredServer 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 usernameRequiredDB 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 passwordRequiredDatabase connection password
      • English letters, numbers, and special characters ( excluding) including, enter 8-30 characters
      Database password verificationRequiredCheck DB connection password
      • Re-enter the DB connection password identically
      Database Port numberRequiredDB connection port number
      • Enter DB port within the range 1200 - 65535
      LicenseRequiredSQL Server License Key
      • Enter the issued license key
      • If the entered license key is not valid, the service may not be created
      Backup > UseSelectBackup 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 PeriodSelectionBackup 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 PeriodSelectionBackup 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)SelectFull backup schedule
      • Select the day of the week for full backup execution
      • Full backup is performed on a weekly basis
      Backup > Archive backup cycleSelectionArchive backup frequency
      • Select the archive backup frequency
      • The archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
      Audit Log SettingsSelectionAudit Log storage option
      • Use to enable the Audit Log feature
      • DDL and user connection information records are stored
      • Enabling Audit may degrade DB performance
      ParameterRequiredDB 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 CollationSelectionData sorting method
      • A command that specifies the data sorting and comparison method, which can produce different results depending on the settings.
      time zoneRequiredStandard 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 status
      Detailed description
      tagSelectAdd Tag
      • Up to 50 per resource can be added
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. Microsoft SQL Server (DBaaS) additional information input fields
  4. 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.

  1. Click the All Services > Database > Microsoft SQL Server (DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
  2. From the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
  3. 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.
      CategoryDetailed description
      Cluster statusCluster status with DB installed
      • Creating: Cluster is being created
      • Editing: Cluster is transitioning to an operational state
      • Error: Cluster encountered a failure while performing a task
        • If this persists, contact the administrator
      • Failed: Cluster failed during creation
      • Restarting: Cluster is being restarted
      • Running: Cluster is operating normally
      • Starting: Cluster is starting
      • Stopped: Cluster is stopped
      • Stopping: Cluster is being stopped
      • Synchronizing: Cluster is synchronizing
      • Terminating: Cluster is being terminated
      • Unknown: Cluster status is unknown
        • If this persists, contact the administrator
      • Upgrading: Cluster is being upgraded
      Cluster controlButtons 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 featuresCluster 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 cancellationService cancellation button
      Table. Microsoft SQL Server(DBaaS) status information and additional features

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.

CategoryDetailed description
Server InformationServer information configured in this cluster
  • Category: Server type (Primary, Secondary)
  • Server name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the DB service, it refers to the cluster SRN
Resource NameResource name
  • In the DB service, it refers to the cluster name
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation date and timeService creation date and time
ModifierUser who edited the service information
Modification dateDate and time the service information was modified
Image versionInstalled DB image and version information
  • If a version upgrade is required, click the Edit icon to configure
Cluster nameCluster name of the configured servers
Databse service nameDatabase Management Unit Name
Database usernameDB user name
Database name > Default DatabaseServer name applied during DB installation
Database name > Add DatabaseServer name applied during DB installation
  • When adding a Database, click the Add button. For adding a Database, refer to Add Database
  • When deleting an added Database, click the Edit icon. For deleting a Database, refer to Delete Database
Planned ComputeResource status with Planned Compute configured
maintenance periodDB Maintenance Period Status
  • If you need to set the maintenance period, click the Edit icon to configure
BackupBackup configuration status
  • If backup configuration is required, click the Edit icon to set it
Audit Log SettingsAudit Log configuration status
  • If you need to configure Audit Log, click the Edit icon to set it up
time zoneStandard time zone for the database
DB CollationData sorting method
VIPVirtual IP information
  • can be checked only when high availability is configured
NetworkNetwork information (VPC, Subnet) where the DB is installed
IP access controlService access policy configuration
  • If you need to add or remove IPs, click the Edit icon to configure
Primary & SecondaryPrimary/Secondary server type, default OS, additional Disk information
  • If you need to modify the server type, click the Edit icon next to the server type to configure. The server type modification procedure is described in Changing Server Type
    • Modifying the server type requires a server reboot
  • If you need to expand storage, click the Edit icon next to the storage capacity to expand. The storage expansion procedure is described in Expanding Storage
  • If you need to add storage, click the Add Disk button next to the additional Disk to add. The storage addition procedure is described in Adding Storage
Table. Microsoft SQL Server (DBaaS) Database detailed information items

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.

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

Work History

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

CategoryDetailed description
Task History ListResource Change History
  • Operation timestamp, Resource ID, Resource Name, Operation details, Event topic, Operation result, Operator information verification
Table. Microsoft SQL Server (DBaaS) job history tab detailed information items

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.

  1. Click the All Services > Database > Microsoft SQL Server (DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Navigate to the Microsoft SQL Server(DBaaS) List page.
  3. 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.
  4. 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.

  1. All Services > Database > Microsoft SQL Server(DBaaS) menu, please click. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
  3. 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.
  4. Click the Service Status Synchronization button. 4. During the query, the cluster changes to Synchronizing state.
  5. When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.

Change server type

You can change the configured server type.

To change the server type, follow these steps.

Caution
  • If you modify the server type, a server restart is required. * Please separately verify any software license modifications or software settings and their implementation resulting from server specification changes.
  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Navigate to the Microsoft SQL Server(DBaaS) List page.
  3. 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.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
  5. 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.

Caution
  • 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.
  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Navigate to the Microsoft SQL Server(DBaaS) List page.
  3. Microsoft SQL Server(DBaaS) List page, click the resource to add storage. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
  4. Click the Add Disk button at the bottom of the details. 4. Additional Storage Request The popup window opens.
  5. Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.

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.

  1. All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
  3. 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.
  4. Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
  5. Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.

Cancel 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.

Caution
If you terminate the DB, all stored data and any configured backup data will be deleted.

To cancel Microsoft SQL Server(DBaaS), follow the steps below.

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

  1. Click the All Services > Database > Microsoft SQL Server (DBaaS) menu. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
  2. Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. You will be taken to the Microsoft SQL Server(DBaaS) List page.
  3. 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.
  4. Click the Add button in the Database name field. The Add Database popup window opens.
  5. 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.

  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. Navigate to the Microsoft SQL Server(DBaaS) List page.
  3. 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.
  4. Click the Edit button for the Database name field. The Add Database Delete popup window opens.
  5. Additional Database Deletion In the request popup, check the Database you want to delete and click the Delete button. The Database Deletion popup opens.
  6. 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.

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

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

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

  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. You will be taken to the Service Home page of Microsoft SQL Server(DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
  3. 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.
  4. Click the More button, then click the DB User Management button. You will be taken to the DB User Management page.
  5. On the DB User Management page, click the Search button. Retrieving may take a short time.
  6. If a correction is needed, click the Edit button, then change the status field value or enter remarks.
  7. 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.

  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Go to the Service Home page of Microsoft SQL Server(DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
  3. 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.
  4. Click the Edit icon of Audit Settings at the bottom of the detailed information. The Edit Audit Settings popup window opens.
  5. 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.

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

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

  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
  3. 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.
  4. Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
  5. On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, 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.

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

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

Caution

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

Check backup history

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

To view the backup history, follow these steps.

  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
  3. Microsoft SQL Server(DBaaS) List page, click the resource to view the backup history. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.

Delete backup file

To delete the backup history, follow these steps.

Caution
Backup files cannot be restored after deletion. Please be sure to verify that the data is unnecessary before deleting it.
  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
  3. 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.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. 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.

  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server(DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
  3. 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.
  4. Click the Database Recovery button. 4. Go to the Database Recovery page.
  5. After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
    Category
    required status
    Detailed description
    Recovery TyperequiredSet the point in time the user wants to recover
    • Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
    • Custom point: Recover to a user‑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 prefixRequiredRecovery 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 nameEssentialRecovery DB cluster name
    • Enter using English letters, 3 ~ 20 characters
    • A cluster is a unit that groups multiple servers
    Service Type > Server TypeRequiredRecovery DB Server Type
    • Standard: Standard specification commonly used
    • High Capacity: Large-capacity server with 24 vCores or more
    Service Type > Planned ComputeSelectionStatus of resources with Planned Compute configured
    • In Use: Number of resources with Planned Compute configured that are currently in use
    • Configured: Number of resources with Planned Compute configured
    • Coverage Preview: Amount applied per resource by Planned Compute
    • Create Planned Compute Service: Navigate to the Planned Compute service application page
    Service Type > Block StorageRequiredBlock 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 usernameRequiredDatabase username
    • Apply the same username set in the original cluster
    Database Port numberEssentialDatabase Port number
    • Apply the same Port number as set in the original cluster
    IP access controlSelectService Access Policy Configuration
    • Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
    • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button
    • To delete an entered IP, click the x button next to the entered IP
    maintenance periodSelectDatabase maintenance window
    • If you select Use, set the day, 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.
    tagSelectionAdd 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.

  1. All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
  2. On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. You will be taken to the Microsoft SQL Server(DBaaS) List page.
  3. 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.
  4. Click the Secondary Add button. Navigate to the Secondary Add page.
  5. After entering information in the Secondary configuration area, click the Create button.
    Category
    Required status
    Detailed description
    Secondary numberRequiredNumber of Secondary to configure
    • Only one can be configured per cluster
    Secondary nameRequiredSecondary 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 TypeRequiredSecondary server type
    • Apply the same as the server type set in the source DB
    Service Type > Planned ComputeSelectStatus 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
    Network > Common SettingsRequiredNetwork settings where servers generated by the service are installed
    • Applied identically to the network settings configured in the original DB
    Network > Server-specific SettingsRequiredNetwork 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/24 Enter an IP address within the range
    LicenseRequiredSQL 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.

Architecture
Figure. Microsoft SQL Server(DBaaS) server connection architecture

Scenario components

You can build the scenario using the following services.

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

For detailed creation steps, refer to the Networking > VPC > How-to guides guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
  2. Click the VPC Creation button on the Service Home page. You will be taken to the VPC Creation page.
  3. On the VPC Creation page, enter the information required to create the service.
    • Enter the IP range as 192.168.x.0/16.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • When creation is complete, check the created resources on the VPC List page.

1-2. Create Subnet

For detailed creation instructions, see the Networking > VPC > How-to guides > Subnet guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
  2. On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
  3. Click the Create Subnet button. You will be taken to the Create Subnet page.
  4. On the Subnet Creation page, enter the information required to create the service.
    • Select the Subnet type as General.
    • Select a pre‑created VPC.
    • Enter the IP range as 192.168.x.0/24.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, check the created resources on the Subnet list page.

1-3. Create Internet Gateway

For detailed creation instructions, refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
  2. On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
  3. Click the Create Internet Gateway button. Navigate to the Create Internet Gateway page.
  4. Internet Gateway Creation page, enter the required information for creating the service.
    • Select a pre‑created VPC.
    • In the Firewall usage option, select Use.
  5. 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

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

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

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

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

  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
  3. On the Virtual Serve List page, click the resource you created in 2-2. Bastion host Create. You will be taken to the detailed information page for that resource.
  4. On the detail information page, click the RDP password view button in the Keypair name field. The RDP password view popup window opens.
  5. In the popup window, perform RDP password lookup, and attach the keypair file downloaded from 2-1. Create Server Keypair.
  6. After attaching, click the Password Check button. The ID and Password for accessing the resource are displayed.

Create Database

Describes the process of creating a Database service.

3-1. Microsoft SQL Server(DBaaS) Create Service

For detailed creation instructions, refer to the Database > Microsoft SQL Server(DBaaS) > How-to guides guide.
  1. Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. Go to the Service Home page of Microsoft SQL Server(DBaaS).
  2. On the Service Home page, click the Create Microsoft SQL Server (DBaaS) button. Navigate to the Create Microsoft SQL Server (DBaaS) page.
  3. 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.
  4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, check the created 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

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

4-2. Add IGW Firewall rule

For detailed creation instructions, see the Networking > Firewall > How-to guides guide.
  1. All Services > Networking > Firewall Click the menu. Then navigate to the Service Home page of Firewall.
  2. From the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
  3. On the Firewall List page, select the Internet Gateway resource name created in 1-3. Create Internet Gateway. You will be taken to the detailed information page of that resource.
  4. Click the Rules tab on the detail information page. You will be taken to the Rules tab.
  5. Click the Add Rule button on the Rules tab. It navigates to the Add Rule popup.
  6. Add Rule In the popup window, enter the rule below, and click the Confirm button.
    origin addressDestination addressProtocolPortoperationdirectionExplanation
    Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
    Table. Internet Gateway Firewall rules that 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

  1. In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
  2. When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password verified in 2-3. Check Bastion host login ID and PW and click the Confirm button.

5-2. Install the DB client program (SSMS) on the Bastion host

  1. Go to the official Microsoft SQL Server page and download the SSMS program.
  2. Connect the user’s PC hard drive to upload the file to the Bastion host.
  3. In the Remote Desktop Connection’s Local Resources tab, click the Details button for the Local Devices and Resources item.
  4. Select the local disk of the location where the file was downloaded on the drive, and click the OK button.
  5. Copy the downloaded file, upload it to the Bastion Host, and click the SSMS (Microsoft SQL Server Management Studio) installation file to install.

5-3. Connect to the Database using the DB client program (SSMS)

  1. Run SSMS (Microsoft SQL Server Management Studio). A Connect to Server popup will appear.
  2. 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 fieldinput value
    Server typeDatabase Engine
    Server nameDatabase server IP, Database Port (ex. 192.168.10.1,2866)
    AuthenticationSQL Server Authentication
    LoginDatabase username
    PasswordDatabase password
    EncryptionOptional
    Table.DB connection client program input fields
  3. Once the connection is established, the database will be accessed. After connecting, you can execute simple queries, among other tasks.

5.3 - API Reference

API Reference

5.4 - CLI Reference

CLI Reference

5.5 - Release Note

Microsoft SQL Server(DBaaS)

2025.07.01
FEATURE User (access control) management, add DB Audit Log export feature, provide backup notification feature
2025.02.27
NEW Microsoft SQL Server(DBaaS) service official version release
  • 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.

Architecture
Figure. CacheStore(DBaaS) Architecture

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.

imageProvided versionEoS DateEoTS Date
Redis OSS Sentinel7.2.112029-06 (planned)2029-12-01
valkey Sentinel8.1.4TBDTBD
Table. CacheStore (DBaaS) provided engine versions
information

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
CategoryexampleDetailed description
Server typeStandardProvided server type
  • Standard: commonly used standard specifications (vCPU, Memory) configuration
Server specificationsredis1Provided server specifications
  • redis1: Standard specifications (vCPU, Memory) commonly used
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. CacheStore (DBaaS) server type components

Preceding Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

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

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
exampleDetailed description
Server typeStandardProvided server type classification
  • Standard: Configured with the commonly used standard specifications (vCPU, Memory)
Server specificationsredis1Provided server type classification and generation
  • redis: means standard specifications, and 1 indicates the generation
Server specificationsv2Number of vCores
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. CacheStore (DBaaS) server type format

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standardredis1v1m21 vCore2 GBUp to 10 Gbps
Standardredis1v2m42 vCore4 GBUp to 10 Gbps
Standardredis1v2m82 vCore8 GBUp to 10 Gbps
Standardredis1v2m162 vCore16 GBUp to 10 Gbps
Standardredis1v2m242 vCore24 GBUp to 10 Gbps
Standardredis1v4m84 vCore8 GBUp to 10 Gbps
Standardredis1v4m164 vCore16 GBUp to 10 Gbps
Standardredis1v4m324 vCore32 GBUp to 10 Gbps
Standardredis1v4m484 vCore48 GBUp to 10 Gbps
Standardredis1v4m644 vCore64 GBUp to 10 Gbps
Standardredis1v6m726 vCore72 GBUp to 10 Gbps
Standardredis1v6m966 vCore96 GBUp to 10 Gbps
Standardredis1v8m1288 vCore128 GBUp to 10 Gbps
Standardredis1v10m16010 vCore160 GBUp to 10 Gbps
Standardredis1v12m19212 vCore192 GBUp to 12.5 Gbps
Standardredis1v14m22414 vCore224 GBUp to 12.5 Gbps
Standardredis1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore (DBaaS) server type specifications - redis1 server type

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
CategoryServer typevCPUMemoryNetwork Bandwidth
Standardcss1v1m21 vCore2 GBUp to 10 Gbps
Standardcss1v2m42 vCore4 GBUp to 10 Gbps
Standardcss1v2m82 vCore8 GBUp to 10 Gbps
Standardcss1v2m162 vCore16 GBUp to 10 Gbps
Standardcss1v2m242 vCore24 GBUp to 10 Gbps
Standardcss1v4m84 vCore8 GBUp to 10 Gbps
Standardcss1v4m164 vCore16 GBUp to 10 Gbps
Standardcss1v4m324 vCore32 GBUp to 10 Gbps
Standardcss1v4m484 vCore48 GBUp to 10 Gbps
Standardcss1v4m644 vCore64 GBUp to 10 Gbps
Standardcss1v6m726 vCore72 GBUp to 10 Gbps
Standardcss1v6m966 vCore96 GBUp to 10 Gbps
Standardcss1v8m1288 vCore128 GBUp to 10 Gbps
Standardcss1v10m16010 vCore160 GBUp to 10 Gbps
Standardcss1v12m19212 vCore192 GBUp to 12.5 Gbps
Standardcss1v14m22414 vCore224 GBUp to 12.5 Gbps
Standardcss1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. CacheStore (DBaaS) server type specifications - css1 server type

6.1.2 - Monitoring metrics

Cloud Monitoring Service Termination Notice

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.

  1. 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.
  2. Cloud Monitoring Service Phased Termination Schedule Notice

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, 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 개요.

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 itemsDetailed descriptionunit
Active Defragmentation Keys [Hits]Number of keys after defragmentationcnt
Active Defragmentation Keys [Miss]Number of keys skipped in the active defragmentation removal processcnt
Active Defragmentationd [Hits]Number of value reallocations performed by the active defragmentation removal processcnt
Active Defragmentations [Miss]Count of value reallocations interrupted by the active defragmentation removal processcnt
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 SizeAOF buffer sizebytes
AOF File Size [Current]AOF current file sizebytes
AOF File Size [Lastest Startup]AOF file size on recent start or rewritebytes
AOF Rewrite Buffer SizeAOF rewrite buffer sizebytes
AOF Rewrite Current TimeIf applicable, the time of the ongoing AOF rewrite operationsec
AOF Rewrite Last TimeFinal AOF rewrite timesec
CallsNumber of calls that reached command execution (not rejected)cnt
Changes [Last Saved]Number of changes after the final dumpcnt
Client Output Buffer [MAX]Longest output list among current client connectionscnt
Clients [Sentinel]Number of client connections (Sentinel)cnt
Connected SlavesNumber of connected slavescnt
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 operationbytes
Copy On Write Allocated Size [RDB]COW allocation size during the final RBD save operationbytes
CPU Time [Average]Average CPU time used per command executioncnt
CPU Time [Total]Total CPU time used by these commandsusec
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 UsedDataset sizebytes
Disk Useddatadir usageMB
Evicted KeysNumber of evicted keys caused by the maxmemory limitcnt
Fsyncs [Delayed]Delayed fsync countercnt
Fsyncs [Pending]Number of pending fsync operations in the background I/O queuecnt
Full ResyncsNumber of full resynchronizations with the slavecnt
Keys [Expired]Total number of key expiration eventscnt
Keys [Keyspace]Number of keys in the key spacecnt
Lastest Fork Duration TimeRecent fork (fork) operation timeusec
Lookup Keys [Hit]Number of successful key lookups in the dictionarycnt
Lookup Keys [Miss]Number of failed key lookups in the main dictionarycnt
Lua Engine Memory UsedMemory used by the Lua enginebytes
Master Last Interaction Time AgoTime elapsed since the final interaction with the mastersec
Master Last Interaction Time Ago [Sync]Time elapsed since the final interaction with the mastersec
Master OffsetCurrent replication offset of the serverpid
Master Second OffsetOffset until the replication ID is acceptedpid
Master Sync Left BytesRemaining bytes before synchronization completesbytes
Memory Fragmentation RateRatio of used_memory_rss to used_memory%
Memory Fragmentation Rate [Allocator]Fragmentation ratio%
Memory Fragmentation UsedBytes between used_memory_rss and used_memorybytes
Memory Fragmentation Used [Allocator]resident bytebytes
Memory Max ValueMemory limitbytes
Memory Resident [Allocator]resident memorybytes
Memory RSS Rate [Allocator]Resident ratio%
Memory Used [Active]Active memorybytes
Memory Used [Allocated]Allocated memorybytes
Memory Used [Resident]Resident bytebytes
Network In Bytes [Total]Total network input (bytes)bytes
Network Out Bytes [Total]Total network output (bytes)bytes
Network Read RateNetwork read speed (KB/sec)cnt
Network Write RateNetwork write speed (KB/sec)cnt
Partial Resync Requests [Accepted]Number of accepted partial resynchronization requestscnt
Partial Resync Requests [Denied]Number of rejected partial resynchronization requestscnt
Peak Memory ConsumedMaximum memory used by CacheStore (DBaaS)bytes
Processed CommandsNumber of commands processed per secondcnt
Processed Commands [Total]Total number of processed commandscnt
Pub/Sub ChannelsGlobal count of pub/sub channels with client subscriptionscnt
Pub/Sub PatternsGlobal count of publish/subscribe patterns with client subscriptionscnt
RDB Saved Duration Time [Current]If applicable, the time of the ongoing RDB save operationsec
RDB Saved Duration Time [Last]Final RDB save operation timesec
Received Connections [Total]Total number of received connectionscnt
Rejected Connections [Total]Total number of rejected connectionscnt
Replication Backlog Actove CountReplication backlog activation flagcnt
Replication Backlog Master OffsetMaster offset of the replication backlog buffercnt
Replication Backlog SizeData size of the replication backlog bufferbytes
Replication Backlog Size [Total]Total size of the replication backlog bufferbytes
Slave PriorityServer priority as a fault remediation targetcnt
Slave Replication OffsetReplication offset of the slave serverpid
Slow OperationsNumber of slow taskscnt
Sockets [MIGRATE]Number of sockets opened for migrationcnt
Tracked Keys [Expiry]Number of keys tracked for expiration (applicable only to writable slaves)cnt
Instance Status [PID]redis-server process PIDpid
Sentinel Status [PID]sentinel process PIDpid
Table. CacheStore (DBaaS) Monitoring Metrics

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.

Cloud Monitoring Service Termination Notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Service per Resource

    • New Resources: Resources created after the 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.
  2. Notice of the phased termination schedule for Cloud Monitoring service

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch can be found in the ServiceWatch 개요.

Create CacheStore (DBaaS)

You can create and use the CacheStore (DBaaS) service from the Samsung Cloud Platform Console.

Information

Before creating the service, configure the VPC’s subnet type as General.

  • If the subnet type is Local, the corresponding Database service cannot be created.

To create a CacheStore (DBaaS), follow the steps below.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Go to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the Create CacheStore (DBaaS) button. 2. Create CacheStore (DBaaS) Go to the page.
  3. 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 status
      Detailed description
      Image versionEssentialProvide 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 status
      Detailed description
      Server name PrefixRequiredServer 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 nameRequiredCluster 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 TypeRequiredServer type for installing Redis/Valkey
      • Standard: Standard specification commonly used
      Service Type > Planned ComputeRequiredStatus 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
      Service Type > Block StorageRequiredBlock 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
      high availabilitySelectHigh 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
      NetworkRequiredThe network where CacheStore (DBaaS) is installed
      • Select a pre‑created VPC and Subnet to connect
      • IP can only be auto‑generated
      Network > Common SettingsRequiredNetwork settings for servers created by the service
      • Select when you want to apply the same settings to all installed servers
      • Select a pre‑created VPC and Subnet
        • IP can only be auto‑generated
      Network > Server-specific SettingsRequiredNetwork 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 controlSelectService Access Policy Configuration
      • Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
      • Enter in IP format (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 periodSelectCacheStore(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
    • Enter or select the required information in the Database Configuration Required Information Input area.
      Category
      required status
      Detailed description
      BackupSelectBackup 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 numberRequiredPort number required for Redis/Valkey connection
      • Enter a port within the range 1200 ~ 65535
      Redis/Valkey passwordEssentialPassword required when connecting to Redis/Valkey
      • include letters, numbers, and special characters (excluding $ ) and enter 8 to 30 characters
      Check Redis/Valkey passwordRequiredRe-enter the same password
      ParameterRequiredParameters 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 zoneRequiredThe 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 status
      Detailed description
      TagSelectAdd Tag
      • Up to 50 per resource can be added
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. CacheStore (DBaaS) additional information input fields
  4. 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.

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

Detailed Information

CacheStore(DBaaS) List page allows you to view detailed information of the selected resource and, if needed, modify the information.

CategoryDetailed description
Server InformationServer information configured in this cluster
  • Category: Server type (Master, Replica, Sentinel)
  • Server name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
serviceService name
Resource TypeResource type
SRNUnique resource ID in Samsung Cloud Platform
  • In the DB service, it refers to the cluster SRN
Resource NameResource name
  • In the DB service, it refers to the cluster name
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation date and timeService creation date and time
ModifierUser who edited the service information
Modification dateDate and time the service information was modified
Image versionInstalled Redis/Valkey image and version information
  • If a Minor version upgrade is required, click the Edit icon to configure
Cluster nameCluster name of the configured Redis/Valkey servers
Planned ComputeResource status with Planned Compute configured
maintenance periodDB patch work period setting status
  • If you need to set the maintenance period, click the Edit icon to configure
BackupBackup Configuration Status
  • If backup configuration is required, click the Edit icon to set it
Redis/Valkey Port numberPort number required for connecting to Redis/Valkey
time zoneRedis/Valkey time zone
Sentinel Port numberPort number for communication between Master and Replica
VIPVirtual IP information
  • can be checked only when high availability is configured
NetworkNetwork information (VPC, Subnet) where CacheStore (DBaaS) is installed
IP access controlService access policy configuration
  • If you need to add or remove an IP, click the Edit icon to configure
Master & ReplicaMaster, Replica server type, base OS, additional Disk information
  • If you need to modify the server type, click the Edit icon next to the server type to configure
  • Modifying the server type requires a server reboot. Please separately verify any software license changes or software configuration and application resulting from specification changes.
SentinelSentinel server type, basic OS information
  • When configuring HA, it is possible to verify when selecting one Replica
Table. CacheStore (DBaaS) Database detailed information items

Tag

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

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, search the existing list of created Keys and Values and select
Table. CacheStore (DBaaS) tag tab items

Work History

On the CacheStore(DBaaS) List page, you can view the operation history of the selected resource.

CategoryDetailed description
Task History ListResource change history
  • You can view the operation timestamp, resource ID, resource name, operation details, event topic, operation result, and operator information
  • To perform an advanced search, click the Advanced Search button
Table. CacheStore (DBaaS) operation history tab detailed information items

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.

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

  1. Click the All Services > Database > CacheStore(DBaaS) menu. 1. Go to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. Navigate to the CacheStore(DBaaS) List page.
  3. CacheStore(DBaaS) List page, click the resource to view the service status. 3. CacheStore(DBaaS) Details Go to the page.
  4. Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
  5. When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.

Change server type

You can change the configured server type.

Caution
If you modify the server type, a server restart is required. Please separately verify any software license modifications or software settings and their implementation resulting from server specification changes.

To change the server type, follow these steps.

  1. All Services > Database > CacheStore(DBaaS) Click the menu. 1. Go to the Service Home page of CacheStore (DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. 2. Go to the CacheStore(DBaaS) List page.
  3. On the CacheStore(DBaaS) List page, click the resource to change the server type. 3. Go to the CacheStore(DBaaS) Details page.
  4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
  5. 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.

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

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

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

Rename Command

Caution
When the Rename-Command is applied, the service will be interrupted due to a CacheStore (DBaaS) restart.

Provides Redis OSS/Valkey command lookup and command name editing functionality. To look up commands and edit command names, follow these steps.

  1. Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. You will be taken to the CacheStore(DBaaS) List page.
  3. 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.
  4. Click the More button, then click the Rename-Command button. You will be taken to the Rename-Command page.
  5. On the Rename-Command page, click the Lookup button. The Lookup notification popup opens.
  6. View Notification when the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
  7. If a modification is needed, click the Edit button and enter the changes in the custom value field of the Command you want to modify.
  8. 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.

Caution
First query the service status via service status synchronization, then proceed with the version upgrade.

To upgrade the Minor Version, follow the steps below.

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

Warning

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.
  1. Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
  2. Click the CacheStore(DBaaS) menu on the Service Home page. You will be taken to the CacheStore(DBaaS) List page.
  3. 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.
  4. Click the Edit icon of the backup item. The Backup Settings popup window opens.
  5. 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

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

To check the backup history, follow these steps.

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

Delete backup file

To delete the backup history, follow these steps.

Warning
Backup files cannot be restored after deletion. Please be sure to verify that the data is unnecessary before deleting.
  1. Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
  2. Click the CacheStore(DBaaS) menu on the Service Home page. You will be taken to the CacheStore(DBaaS) List page.
  3. CacheStore(DBaaS) List Click the resource whose backup history you want to view. You will be taken to the CacheStore(DBaaS) Details page.
  4. Click the Backup History button. The Backup History popup window opens.
  5. 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.

  1. Click the All Services > Database > CacheStore(DBaaS) menu. Navigate to the Service Home page of CacheStore(DBaaS).
  2. On the Service Home page, click the CacheStore(DBaaS) menu. You will be taken to the CacheStore(DBaaS) List page.
  3. On the CacheStore(DBaaS) List page, click the resource you want to recover. You will be taken to the CacheStore(DBaaS) Details page.
  4. Click the Database Recovery button. You will be taken to the Database Recovery page.
  5. After entering information in the Database recovery configuration area, click the Complete button.
    Category
    Required
    Detailed description
    Recovery typeRequiredUser 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 prefixRequiredServer name of the recovery DB
    • Start with a lowercase English letter and use lowercase letters, numbers, and special characters (-) to enter 3 to 16 characters
    • A postfix such as 001, 002 is appended to the base server name to create the actual server name
    Cluster nameRequiredCluster 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 TypeRequiredServer 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 ComputeSelectionStatus of resources with Planned Compute configured
    • In Use: Number of resources with Planned Compute that are currently in use
    • Configured: Number of resources with Planned Compute configured
    • Coverage Preview: Amount applied by Planned Compute per resource
    Service Type > Block StorageRequiredBlock 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 numberRequiredRedis/Valkey port number configured in the source DB
    IP access controlSelectionService 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 periodSelectionCacheStore(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.
    tagSelectionAdd 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.

Architecture
Figure. CacheStore (DBaaS) server connection architecture

Scenario components

You can build the scenario using the following services.

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

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

For detailed creation instructions, refer to the Networking > VPC > How-to guides > Subnet guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
  2. On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
  3. Click the Subnet Create button. You will be taken to the Subnet Create page.
  4. On the Subnet Creation page, enter the information required to create the service.
    • Select the Subnet type as General.
    • Select a pre‑created VPC.
    • Enter the IP range as 192.168.x.0/24.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • After creation is complete, check the created resources on the Subnet List page.

1-3. Create Internet Gateway

For detailed creation steps, refer to the Networking > VPC > How-to guides > Internet Gateway guide.
  1. Click the All Services > Networking > VPC menu. You will be taken to the VPC’s Service Home page.
  2. On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
  3. Click the Create Internet Gateway button. Navigate to the Create Internet Gateway page.
  4. 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.
  5. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
    • When creation is complete, verify the created resource on the Internet Gateway list page.

1-4. Create Public IP

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

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

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

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

  1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
  3. On the Virtual Serve List page, click the resource you created in 2-2. Bastion host Create. You will be taken to the detailed information page for that resource.
  4. On the detail page, click the RDP password view button in the Keypair name field. The RDP password view popup window will open.
  5. In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
  6. After attaching, click the Password verification button. The ID and Password for accessing the resource are displayed.

Create Database

Describes the process of creating a Database service.

3-1. Create CacheStore(DBaaS) Service

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

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

4-2. Add IGW Firewall rule

For detailed creation instructions, refer to the Networking > Firewall > How-to guides guide.
  1. All Services > Networking > Firewall Click the menu. Go to the Service Home page of Firewall.
  2. From the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
  3. On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. You will be taken to the detailed information page for that resource.
  4. Click the Rules tab on the detail page. You will be taken to the Rules tab.
  5. Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
  6. Add Rule In the popup window, enter the rule below and click the Confirm button.
    origin addressDestination addressProtocolPortOperationdirectionExplanation
    Bastion connection PC IPBastion host IPTCP3389(RDP)AllowInboundUser PC → Bastion host
    Table. Internet Gateway Firewall rules that 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

  1. In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
  2. When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password 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

  1. Please download the Another Redis Desktop Manager program.
  2. Connect the user’s PC hard drive to upload the file to the Bastion host.
  3. In the Local Resources tab of the Remote Desktop Connection, click the Details button for the Local Devices and Resources item.
  4. Select the local disk where the file was downloaded on the drive, and click the OK button.
  5. Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install.

5-3. Connect to the database using the DB client program (Another Redis Desktop Manager)

  1. Run Another Redis Desktop Manager and click New Connection. The New Connection popup will appear.
  2. New Connection in the popup window, enter the Database server information created from 3-1. CacheStore(DBaaS) 서비스 생성하기 and click the OK button.
    Required input fieldinput value
    HostDatabase server IP
    PortDatabase Port
    PasswordDatabase password
    Connection NameCustom (ex. service name)
    Table.DB connection client program input fields
  3. After connecting, you can check basic Redis information, manage data, and perform CRUD operations on keys.

6.3 - API Reference

API Reference

6.4 - CLI Reference

CLI Reference

6.5 - Release Note

CacheStore(DBaaS)

2026.03.19
FEATURE Minor version upgrade feature addition
  • We ensure stable service continuity through the Minor version upgrade feature.
2025.07.01
FEATURE User (access control) management, add DB Audit Log export feature, provide backup notification 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
    • Add HDD, HDD_KMS types to Block Storage type
2025.02.27
FEATURE Common feature change
  • Samsung Cloud Platform Common Feature Changes
    • Account, IAM, Service Home, tags, and other common CX changes have been applied.
2024.10.01
NEW CacheStore(DBaaS) service official version release
  • 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.
2024.07.02
NEW Beta version release
  • 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

Architecture
Figure. Scalable DB(DBaaS) Architecture

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.

Provided versionEOS Date (Samsung Cloud Platform new creation stop date)EoTS Date (Community technical support end date)
10.11.132027-06 (planned)2028-02-16
Table. Engine versions provided by Scalable DB(DBaaS)

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
exampleDetailed description
Server typeHigh CapacityProvided server type classification
Server specificationssdbh2Provided server type classification and generation
  • sdbh: h indicates a high-capacity server specification, and 2 indicates the generation
Server specificationsv24Number of vCores
  • v24: 24 virtual cores
Server specificationsm48Memory Capacity
  • m48: 48GB Memory
Table. Scalable DB(DBaaS) server type components

Provision status by region

Scalable DB(DBaaS) is available in the following environments.

regionProvision 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
Table. Scalable DB(DBaaS) availability by region

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 CategoryserviceDetailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
Table. Scalable DB(DBaaS) required services

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
exampleDetailed description
Server typeHigh CapacityProvided server type classification
Server specificationssdbh2Provided server type classification and generation
  • sdbh: h indicates a high-capacity server specification, and 2 indicates the generation
Server specificationsv24Number of vCores
  • v24: 24 virtual cores
Server specificationsm48Memory Capacity
  • m48: 48GB Memory
Table. Scalable DB (DBaaS) server type format

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
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacitysdbh2v24m4824 vCore48 GBMaximum 25 Gbps
High Capacitysdbh2v24m9624 vCore96 GBMaximum 25 Gbps
High Capacitysdbh2v24m19224 vCore192 GBMaximum 25 Gbps
High Capacitysdbh2v24m28824 vCore288 GBMaximum 25 Gbps
High Capacitysdbh2v32m6432 vCore64 GBMaximum 25 Gbps
High Capacitysdbh2v32m12832 vCore128 GBMaximum 25 Gbps
High Capacitysdbh2v32m25632 vCore256 GBMaximum 25 Gbps
High Capacitysdbh2v32m38432 vCore384 GBMaximum 25 Gbps
High Capacitysdbh2v48m19248 vCore192 GBMaximum 25 Gbps
High Capacitysdbh2v48m57648 vCore576 GBMaximum 25 Gbps
High Capacitysdbh2v64m25664 vCore256 GBUp to 25 Gbps
High Capacitysdbh2v64m76864 vCore768 GBMaximum 25 Gbps
High Capacitysdbh2v72m28872 vCore288 GBMaximum 25 Gbps
High Capacitysdbh2v72m86472 vCore864 GBMaximum 25 Gbps
High Capacitysdbh2v96m38496 vCore384 GBUp to 25 Gbps
High Capacitysdbh2v96m115296 vCore1152 GBMaximum 25 Gbps
High Capacitysdbh2v128m512128 vCore512 GBMaximum 25 Gbps
High Capacitysdbh2v128m1536128 vCore1536 GBMaximum 25 Gbps
Table. Scalable DB(DBaaS) server type specifications - sdbh2 server type

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.

Reference
For instructions on how to view metrics in ServiceWatch, refer to the ServiceWatch guide.

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

Scalable DB Basic Metrics

Category
Performance itemsunitDetailed descriptionmeaningful statistics
ActivelockActive locksCountNumber of transactions in lock wait (Lock Wait) state for 1 minute (60 seconds) or longer in the InnoDB storage engine
  • Total
  • Average
  • Maximum
  • Minimum
ActivesessionActive sessionsCountNumber of active sessions
  • Total
  • Average
  • Maximum
  • Minimum
ActivesessionConnection usagePercentDB connection session usage rate
  • Total
  • Average
  • Maximum
  • Minimum
ActivesessionConnectionsCountDB connection session
  • Total
  • Average
  • Maximum
  • Minimum
ActivesessionAborted ConnectionsCount/MinuteNumber of abnormal terminated connections
  • Total
  • Average
  • Maximum
  • Minimum
DatafileCurrent open filesCountNumber of file descriptors opened by the DB
  • Total
  • Average
  • Maximum
  • Minimum
DatafileMax open filesCountMaximum number of file descriptors the DB can open
  • Total
  • Average
  • Maximum
  • Minimum
DatafileOpen files usagePercentDB file maximum count utilization
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnoDB buffer pool hit ratioPercentThe proportion of data read directly from memory without accessing the disk
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnodb row lock wait transactionsCountCurrent number of InnoDB transactions waiting for a row lock
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnoDB row lock timeMillisecondsTotal time waited due to InnoDB row locks (in milliseconds)
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnoDB deadlocksCount/MinuteNumber of transactions rolled back due to deadlock
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBTable lock waitsCount/MinuteNumber of waits that occurred to acquire a table lock
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBTemp disk tablesCount/MinuteNumber of Temp Tables created on disk
  • Total
  • Average
  • Maximum
  • Minimum
InnoDBInnodb log waitsCountNumber of times waited to write the redo log to disk
  • Total
  • Average
  • Maximum
  • Minimum
ProxySQLProxy UptimeSecondsExpress the proxy’s uptime in seconds
  • Total
  • Average
  • Maximum
  • Minimum
ProxySQLBackend connections(CONNECTED)CountNumber of sessions connected to the Proxy server
  • Total
  • Average
  • Maximum
  • Minimum
ProxySQLClient connections connectedCountNumber of client sessions currently connected to the proxy
  • Total
  • Average
  • Maximum
  • Minimum
ProxySQLQueries routedCountNumber of queries routed to the backend server
  • Total
  • Average
  • Maximum
  • Minimum
ProxySQLBackend connections(ACTIVE, IDLE)CountActive / idle connection count per endpoint
  • Total
  • Average
  • Maximum
  • Minimum
ProxySQLBackend server statusNoneBackend server status
  • 1 - Online
  • 2- SHUNNED
  • 3 - OFFLINE_SOFT
  • 4 - OFFLINE_HARD
  • 5 - SHUNNED_REPLICATION_LAG
  • Total
  • Average
  • Maximum
  • Minimum
ProxySQLBackend conneciton checkCountBackend server connection success/failure count-
StateInstance stateNoneCheck Scalable DB status up/down
  • 1 - Up
  • 0 - Down
-
StateSlave behind master secondsSecondsReplica latency (unit: seconds)
  • Total
  • Average
  • Maximum
  • Minimum
StateSlave io thread running (Replica Only)NoneI/O Thread status
  • 1 - Running
  • 0 - Down
-
StateSlave SQL thread running (Replica Only)NoneSQL Thread status
  • 1 - Running
  • 0 - Down
-
TablespaceTablespace usedMegabytesTablespace usage
  • Total
  • Average
  • Maximum
  • Minimum
TablespaceTablespace used(TOTAL)MegabytesTablespace usage (total)
  • Total
  • Average
  • Maximum
  • Minimum
TransactionsSlow queriesCountNumber of queries running longer than 10 seconds
  • Total
  • Average
  • Maximum
  • Minimum
TransactionsLong transaction timeSecondsLong Transaction time
  • Total
  • Average
  • Maximum
  • Minimum
TransactionsWait locksCountNumber of sessions waiting for lock
  • Total
  • Average
  • Maximum
  • Minimum
TransactionsSQL Queries/MinuteCount/MinuteQueries executed per minute
  • Total
  • Average
  • Maximum
  • Minimum
Table. Scalable DB basic metrics

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.

information
When a large number of rows are modified in a single transaction, the changes are processed on the Primary node and then replicated to the Read node, where they are applied all at once, causing a brief spike in load on the Read node. This can cause replication lag, and depending on the Lagging value set by the user, routing to a specific Read node may become unavailable. Therefore, when performing large-scale data modification operations, it is recommended to split them into multiple transactions and keep the commit (Commit) cycle of each transaction short.

Create Scalable DB(DBaaS)

You can create and use the Scalable DB (DBaaS) service in the Samsung Cloud Platform Console.

information

Before creating the service, configure the VPC’s subnet type as General.

  • If the subnet type is Local, the corresponding Database service cannot be created.

To create a Scalable DB (DBaaS), follow the steps below.

  1. All Services > Database > Scalable DB(DBaaS) Click the menu. 1. Go to the Service Home page of Scalable DB (DBaaS).

  2. On the Service Home page, click the Create Scalable DB (DBaaS) button. 2. Create Scalable DB (DBaaS) Navigate to the page.

  3. 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 status
      Detailed description
      Image versionRequiredProvide 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 status
      Detailed description
      Server name PrefixRequiredServer 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 nameRequiredCluster name of DB servers
      • Enter using English letters, 3 - 20 characters
      • A cluster is a unit that groups multiple servers
      Service Type > Server TypeRequiredServer type on which the DB will be installed
      • High Capacity: Large-capacity server with 24 vCores or more
      Service Type > Planned ComputeSelectStatus of resources with Planned Compute configured
      • In Use: Number of resources with Planned Compute that are currently in use
      • Configured: Number of resources with Planned Compute configured
      • Coverage Preview: Amount applied per resource by Planned Compute
      • Create Planned Compute Service: Navigate to the Planned Compute service application page
      Service Type > Block StorageRequiredBlock Storage settings used by the 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 /tmp area is recommended
          • For each service, Archive, TEMP, and BACKUP storages are allocated only one Block Storage each
      Network > Common SettingsRequiredNetwork settings for servers created by the service
      • Select when you want to apply the same settings to all installed servers
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • IP can only be 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 SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select when you want to apply different settings for each installed server
      • Select a pre‑created VPC, Subnet, IP, and Public NAT
        • Enter the IP for each server
        • 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 controlSelectionService Access Policy Configuration
      • Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
      • Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click the Add button.
      • To delete an entered IP, click the x button next to the entered IP.
      maintenance periodSelectDatabase maintenance window
      • If you select Use, set the day, 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
    • Service Information Input (Read Node) Enter or select the required information in this area.
      Category
      required status
      Detailed description
      Read Node countRequiredSelect 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 TypeRequiredServer type on which the DB will be installed
      • High Capacity: large-capacity server with 24 vCores or more
      Service Type > Planned ComputeSelectionStatus of resources with Planned Compute configured
      • In Use: Number of resources with Planned Compute configured that are currently in use
      • Configured: Number of resources with Planned Compute configured
      • Coverage Preview: Amount applied per resource by Planned Compute
      Service Type > Block StorageRequiredBlock 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 /tmp area is recommended
          • For each service, Archive, TEMP, and BACKUP storages are allocated only one Block Storage each
      Network > Common SettingsRequiredNetwork 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 SettingsRequiredNetwork 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 CountRequiredEnter 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 policyoptionAuto 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 PolicyoptionAuto 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 status
      Detailed description
      Proxy Endpoint Settings > Read Endpoint PortRequiredSet 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 PortRequiredSet 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 TimeRequiredEnter 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 CountRequiredSet 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 CountRequiredSet 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 TimeRequiredSet 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 status
      Detailed description
      Database nameRequiredServer name applied during DB installation
      • must start with an English letter and be entered using English letters and numbers, 3 - 20 characters long
      Database usernameRequiredDB user name
      • An account with the same name is also created on the OS
      • Enter using lowercase English letters, 2 to 20 characters
      • Restricted database user names can be viewed in the Console
      Database passwordRequiredPassword to use when accessing the DB
      • Enter 8 - 30 characters including letters, numbers, and special characters (excluding )
      Database password verificationRequiredRe-enter the same password to use for DB access
      Database Port numberRequiredPort number required for DB connection
      • Enter the DB port within the range 1200 ~ 65535
      Backup > UseSelectionBackup usage
      • Select Use to set backup file retention period, backup start time, and Archive backup interval
      Backup > Retention PeriodSelectionBackup 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 TimeSelectionBackup start time
      • Select backup start time
      • The minutes during which the backup runs (minutes) are set randomly, and the backup end time cannot be set
      Backup > Archive backup cycleSelectionArchive backup 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.
      ParameterRequiredParameters to be used in the DB
      • Query button can be clicked to view detailed information of the parameters
      DB character setRequiredSet 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 zoneRequiredStandard time zone for the database
      ServiceWatch log collectionSelectionServiceWatch log collection status
      • use to enable the ServiceWatch log collection feature
      • Up to 5 GB is provided free of charge for all services within the account, and charges apply based on storage size for usage exceeding 5 GB
      • When collecting, log groups and log streams are created automatically and 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 status
      Detailed description
      tagSelectionAdd 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
  4. 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.

  1. All Services > Database > Scalable DB(DBaaS) Click the menu. 1. Go to the Service Home page of Scalable DB (DBaaS).
  2. On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Navigate to the Scalable DB(DBaaS) List page.
  3. 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.
      CategoryDetailed description
      Cluster statusCluster 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 controlButton to change the cluster state
      • Start: Start a stopped cluster
      • Stop: Stop a running cluster
      View more featuresCluster-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 노드 삭제하기
      Service terminationButton to cancel the service
      Table. Scalable DB (DBaaS) status information and additional features

Detailed Information

Scalable DB (DBaaS) List page allows you to view detailed information of the selected resource and edit the information if needed.

CategoryDetailed description
Server InformationServer information configured in this cluster
  • Category: Server type (Primary Node (Active), Primary Node (Standby), Read Node)
  • Server Name: Server name
  • IP:Port: Server IP and port
  • Status: Server status
  • Restart button click restarts the server
    • For Primary Nodes, Active and Standby servers are restarted simultaneously, and for Read Nodes, each Read Node is restarted individually
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In the DB service, it refers to the cluster SRN
Resource NameResource name
  • In the DB service, it refers to the cluster name
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation date and timeService creation date and time
ModifierUser who edited the service information
Modification dateDate and time the service information was modified
Image versionInstalled DB image and version information
  • If a version upgrade is required, click the Edit icon to configure
Cluster nameCluster name of the DB servers
Read Endpoint PortPort connected to the Read Node that handles read requests
Write Endpoint PortPort connected to the Primary Node that handles write requests
Database nameServer name applied during DB installation
Database usernameDB user name
Planned ComputeResources with Planned Compute configured
maintenance periodDB patch work period setting status
  • If you need to set the maintenance period, click the Edit icon to configure
BackupBackup configuration status
  • If backup configuration is required, click the Edit icon to set it
DB character setCharacter set to use for the DB
ServiceWatch log collectionServiceWatch Log Collection Configuration Status
  • If log collection configuration is required, click the Edit icon next to Log Collection to configure
Scailing policy node countScailing policy node count configuration status
  • If you need to change the Scailing policy node count, click the Edit icon to configure
time zoneStandard time zone for the database
NetworkNetwork information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP))
IP access controlService access policy configuration
  • If you need to add or remove IPs, click the Edit icon to configure
Resource Management (Primary)Primary Node configuration information for the DB server
Resource Management (Read Node)Read Node configuration information for the DB server
Table. Scalable DB (DBaaS) Database detailed information items

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.

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

Job History

Scalable DB(DBaaS) List page lets you view the operation history of the selected resource.

CategoryDetailed description
Task History ListResource Change History
  • Operation timestamp, Resource ID, Resource name, Operation details, Event topic, Operation result, Operator information verification
Table. Work History Tab Detailed Information Items

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.

information
The Switch-Over, Disk expansion/addition, server type change, and DB service management features of Scalable DB (DBaaS) will be provided later.

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.

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

  1. All Services > Database > Scalable DB (DBaaS) Click the menu. 1. Navigate to the Service Home page of Scalable DB (DBaaS).
  2. On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Scalable DB(DBaaS) List Navigate to the page.
  3. Scalable DB(DBaaS) List Click the resource on the page to view the service status. 3. Scalable DB(DBaaS) Details Navigate to the page.
  4. Service Status Sync Click the button. 4. While it is being queried, the cluster changes to Synchronizing state.
  5. When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.

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.

  1. All Services > Database > Scalable DB(DBaaS) Click the menu. 1. Navigate to the Service Home page of Scalable DB (DBaaS).
  2. On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Go to the Scalable DB (DBaaS) List page.
  3. Scalable DB(DBaaS) List Click the resource on the page to view the service status. 3. Scalable DB(DBaaS) Details Navigate to the page.
  4. In the add-on menu, click the Proxy Endpoint Settings Management button. 4. Proxy Endpoint Settings Management Navigate to the page.
  5. On the Proxy Endpoint Settings Management page, click the Search button. 5. Next, when the query alert appears, click the Confirm button.
  6. On the Proxy Endpoint Settings Management page, click the Edit button. 6. Go to the Proxy Endpoint Settings Edit page.
  7. 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.

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

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

  1. Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
  2. On the Service Home page, click the Scalable DB(DBaaS) menu. You will be taken to the Scalable DB(DBaaS) List page.
  3. 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.
  4. On the Scalable DB(DBaaS) Details page, click the Read Node Status tab.
  5. On the Read Node status query page, click the Status Query button.
  6. When the alert window appears, click the Confirm button. The query results will be displayed in the Read Node status list.
CategoryDetailed description
Read Node statusRead Node server status
  • You can view the server name, status query, status details, and status check time
  • While being queried, the cluster remains in the Synchronizing state, and once the query completes, the cluster changes to the Running state
Table. Read Node status view tab detailed information items

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

Caution

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.

  1. Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
  2. On the Service Home page, click the Scalable DB(DBaaS) menu. You will be taken to the Scalable DB(DBaaS) List page.
  3. 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.
  4. On the Scalable DB(DBaaS) Detail page, click the Auto Scaling Policy tab.
  5. On the Auto Scaling policy page, click the Add Policy button.
  6. 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.
  7. Set the detailed items of the selected Scale policy and click the Confirm button.
  8. 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.

  1. Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
  2. On the Service Home page, click the Scalable DB(DBaaS) menu. You will be taken to the Scalable DB(DBaaS) List page.
  3. 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.
  4. On the Scalable DB(DBaaS) Details page, click the Auto Scaling Policy tab.
  5. On the Auto Scaling policy page, click the Edit button for the policy you want to modify.
  6. 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.

  1. Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
  2. Click the Scalable DB(DBaaS) menu on the Service Home page. You will be taken to the Scalable DB(DBaaS) List page.
  3. 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.
  4. On the Scalable DB(DBaaS) Details page, click the Auto Scaling Policy tab.
  5. On the Auto Scaling policy page, select the policy to delete and click the Delete button.
  6. 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.

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

  1. Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
  2. Click the Scalable DB(DBaaS) menu on the Service Home page. You will be taken to the Scalable DB(DBaaS) List page.
  3. 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.
  4. On the Scalable DB(DBaaS) Details page, click Additional Functions > Add Node. You will be taken to the Add Read Node page.
  5. 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.

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

  1. Click the All Services > Database > Scalable DB(DBaaS) menu. Navigate to the Service Home page of Scalable DB(DBaaS).
  2. Click the Scalable DB(DBaaS) menu on the Service Home page. Navigate to the Scalable DB(DBaaS) List page.
  3. Scalable DB(DBaaS) List Click the resource to view detailed information. Scalable DB(DBaaS) Details You will be taken to the page.
  4. Scalable DB(DBaaS) Details on the page, click Additional Functions > Delete Node.
  5. When the Delete dialog for Read Node appears, select the items to delete and click the Delete button.
  6. When the alert window appears, enter the name of the node to delete and click the Confirm button.
  7. 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.

information
Scalable DB(DBaaS)’s recovery feature will be provided later.

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.

Caution
  • For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity.
  • Especially when the backup data exceeds 100 GB and undergoes frequent changes, please 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.

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

Check backup history

Information
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on configuring notification policies, see Create Notification Policy.

To view the backup history, follow these steps.

  1. Click the All Services > Database > Scalable DB(DBaaS) menu. 1. Navigate to the Service Home page of Scalable DB (DBaaS).
  2. On the Service Home page, click the Scalable DB(DBaaS) menu. 2. Scalable DB(DBaaS) List Go to the page.
  3. Scalable DB(DBaaS) List page: click the resource to view the backup history. 3. Scalable DB(DBaaS) Details Navigate to the page.
  4. Click the Backup History button. 4. Backup History The popup window opens.
  5. Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.

Delete backup file

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

To delete the backup history, follow these steps.

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

2026.03.19
FEATURE Provide Servicewatch log integration feature
  • You can monitor logs by integrating with Servicewatch.
2025.12.16
NEW product launch
  • The fully managed Database service, Scalable DB (DBaaS), which flexibly adjusts resources according to traffic changes, has been launched.