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

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.

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.

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

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.

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.

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.

3 - API Reference

API Reference

4 - CLI Reference

CLI Reference

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.