This is the multi-page printable view of this section. Click here to print.
PostgreSQL(DBaaS)
- 1: Overview
- 1.1: Server Types
- 1.2: Monitoring metrics
- 2: How-to guides
- 2.1: DB Service Manage
- 2.2: Backing up and restoring the DB
- 2.3: Configure Read Replica
- 2.4: DB Server Connection
- 2.5: Extension Use
- 3: API Reference
- 4: CLI Reference
- 5: Release Note
1 - Overview
Service Overview
PostgreSQL (DBaaS) is an open-source relational database management system (RDBMS). Samsung Cloud Platform provides an environment that automates PostgreSQL installation through a web-based console and performs management functions for operation.
PostgreSQL (DBaaS) is designed as a high‑availability architecture that performs storage‑based data replication and minimizes failover time. To prevent data loss, when the contents of the Active server change, they are synchronously replicated to the Standby server, and up to five read‑only Replica servers for read load balancing and disaster recovery (DR) are provided. Additionally, to prepare for potential issues with the DB server or data, we provide a feature that automatically backs up at a user-specified time, enabling recovery of data at the desired point.
Provided Features
PostgreSQL (DBaaS) provides the following features.
- Auto Provisioning: UI allows installation and configuration of Database (DB), and provides an Active‑standby redundancy configuration built on storage replication. * When the active server fails, it automatically fails over to standby.
- Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, you can restart if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, the user can manually perform node switching between Active and Standby via a switch‑over.
- Backup and Recovery: Provides data backup functionality based on its own backup commands. * The backup schedule and retention policy can be set by the user, and additional fees apply based on the backup size. * It also provides a recovery function for backed‑up data, so when the user performs a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user (the backup save point or a user‑specified point). * When restoring to a user-specified point in time, the restore point can be set up to 5 minutes, 10 minutes, 30 minutes, or 1 hour earlier, based on the stored backup files and archive files.
- Version Management: Provides version upgrade (Minor) functionality due to certain feature improvements and security patches. * Whether to perform a backup for a version upgrade can be selected by the user, and if a backup is performed, the data is backed up before applying the patch, after which the DB engine is updated.
- Replica configuration: For load balancing reads and disaster recovery (DR), up to five Read Replicas can be configured in the same or different regions.
- Audit Settings: Supports audit (Audit) functionality for key activities within the database.
- Parameter management: You can modify DB configuration parameters related to performance improvement and security.
- Service Status Query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, and DB performance monitoring information can be accessed through the Cloud Monitoring service.
- DB User Management: Query and manage the DB account (user) information registered in the DB.
- DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
- Archive Management: You can set the retention period (1 to 35 days) for Archive files on the DB server and configure the Archive mode (On/Off).
- Export DB Log: You can export stored logs to the user’s Object Storage through Audit settings.
- Migration: Synchronize data in real time with the operational database and support migration using replication without service interruption.
- OS kernel upgrade: The OS Kernel can be upgraded to apply certain feature improvements and security patches.
Component
PostgreSQL(DBaaS) provides pre‑validated engine versions and various server types in accordance with the open‑source support policy. Users can select and use it according to the scale of the service they wish to configure.
Engine version
The engine versions supported by PostgreSQL (DBaaS) are as follows.
Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
- PostgreSQL: https://www.postgresql.org/support/versioning/
| Provided version | EOS Date (Samsung Cloud Platform new creation stop date) | EoTS Date (Community Technical Support End Date) |
|---|---|---|
| 14.17 | 2026-05-20 | 2026-11-12 |
| 14.18 | 2026-05-20 | 2026-11-12 |
| 14.19 | 2026-05-20 | 2026-11-12 |
| 15.12 | 2027-06 (planned) | 2027-11-11 |
| 15.13 | 2027-06 (planned) | 2027-11-11 |
| 15.14 | 2027-06 (planned) | 2027-11-11 |
| 16.8 | 2028-06 (planned) | 2028-11-09 |
| 16.9 | 2028-06 (planned) | 2028-11-09 |
| 16.10 | 2028-06 (planned) | 2028-11-09 |
| 17.6 | 2029-06 (planned) | 2029-11-08 |
The next version of PostgreSQL is scheduled to be available after July 2026. The actual service delivery schedule is subject to change.
- PostgreSQL 15.15
- PostgreSQL 16.11
- PostgreSQL 17.17
Server type
The server types supported by PostgreSQL (DBaaS) are as follows.
For detailed information about the server types offered by PostgreSQL(DBaaS), see PostgreSQL(DBaaS) Server Types.
Standard db1v2m4
| Category | Example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server types
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
Preceding Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
1.1 - Server Types
PostgreSQL(DBaaS) server type
PostgreSQL (DBaaS) offers server types composed of various combinations of CPU, Memory, and Network Bandwidth. When creating PostgreSQL(DBaaS), the Database Engine is installed based on the server type chosen for the intended use.
The server types supported by PostgreSQL (DBaaS) are as follows.
Standard db1v2m4
Category | example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type classifications
|
| Server specifications | db1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
db1 server type
The db1 server type of PostgreSQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db1v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
db2 server type
The db2 server type of PostgreSQL (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db2v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db2v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db2v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db2v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db2v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db2v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db2v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db2v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db2v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db2v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db2v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db2v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db2v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db2v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db2v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db2v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db2v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db2v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db2v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db2v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db2v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db2v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db2v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db2v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db2v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db2v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db2v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db2v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db2v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db2v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
dbh2 server type
The dbh2 server type of PostgreSQL (DBaaS) is provided with high-capacity server specifications and is suitable for database workloads that require large-scale data processing.
- Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
- Supports up to 128 vCPUs and 1,536 GB of memory
- Networking speed up to 25 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Maximum 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Maximum 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Maximum 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Maximum 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Maximum 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Maximum 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Maximum 25 Gbps |
1.2 - Monitoring metrics
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service per Resource
- New Resources: Resources created after the service improvement work in July 2026 are monitored by default using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring via Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings linked with existing Cloud Monitoring (e.g. You must verify items such as event policies and perform tasks such as resetting the ServiceWatch service, then complete them.
Cloud Monitoring Service Phased Termination Schedule Notice
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period.**
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
PostgreSQL(DBaaS) Monitoring Metrics
The table below shows performance monitoring metrics for PostgreSQL (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
For PostgreSQL (DBaaS), refer to the Virtual Server Monitoring Metrics guide.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Locks [Access Exclusive] | Number of Access Exclusive Locks | cnt |
| Active Locks [Access Share] | Number of Access Share Locks | cnt |
| Active Locks [Total] | Total number of active locks | cnt |
| Active Sessions | Number of Sessions in Active state | cnt |
| Active Sessions [Total] | Total number of Sessions in Active state | cnt |
| Apply Lag Time | Apply lag time | min |
| Check No Replication | Check No Replication value | cnt |
| Check Replication | Check Replication Status value | status |
| Connection Usage | DB connection usage rate (%) | % |
| Connection Usage [Total] | DB connection usage rate (%) | % |
| DB Age Max | Database age (frozen XID) value | age |
| Exclusive Locks | Number of Exclusive Locks | cnt |
| Idle In Transaction Sessions | Number of sessions in idle-in-transaction state | cnt |
| Idle In Transaction Sessions [Total] | Total number of sessions in Idle in transaction state | cnt |
| Idle Sessions | Number of idle sessions | cnt |
| Idle Sessions [Total] | Total number of sessions in Idle state | cnt |
| Row Exclusive Locks | Number of Row Exclusive Locks | cnt |
| Row Share Locks | Row Share Locks count | cnt |
| Share Locks | Number of Share Locks | cnt |
| Share Row Exclusive Locks | Number of Share Row Exclusive Locks | cnt |
| Share Update Exclusive Locks | Number of Share Update Exclusive Locks | cnt |
| Slowqueries | Number of SQL queries running for a long time (over 5 minutes) | cnt |
| Tablespace Used | Table space size | bytes |
| Tablespace Used [Total] | Table space size | bytes |
| Tablespace Used Bytes [MB] | File system directory usage (MB) | MB |
| Tablespaces [Total] | File system directory usage (MB) | MB |
| Transaction Time Max [Long] | Long-running Transaction time (minutes) | min |
| Transaction Time Max Total [Long] | Long-running Transaction time (minutes) | min |
| Wait Locks | Number of lock-waiting sessions (by DB) | cnt |
| Wait Locks [Long Total] | Number of lock‑waiting sessions lasting 300 seconds | cnt |
| Wait Locks [Long] | Number of sessions waiting due to lock occurrence | cnt |
| Wait Locks [Total] | Total number of sessions waiting due to lock occurrence | cnt |
| Waiting Sessions | Number of Sessions in Waiting state | cnt |
| Waiting Sessions [Total] | Total number of Sessions in Waiting state | cnt |
2 - How-to guides
Users can create the service by entering the required information for PostgreSQL (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
- New Resources: Resources created after the service improvement work in July 2026 are provided with monitoring using the ServiceWatch service by default.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring via Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e.g. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
Notice of the phased termination schedule for Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration work within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
Create PostgreSQL (DBaaS)
You can create and use a PostgreSQL (DBaaS) service from the Samsung Cloud Platform Console.
- Before creating the service, configure the VPC’s subnet type as General.
- If the subnet type is Local, the creation of the corresponding Database service is not possible.
- When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to a statistical collection environment.
To create PostgreSQL(DBaaS), follow the steps below.
Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
On the Service Home page, click the PostgreSQL(DBaaS) Create button. 2. Navigate to the Create PostgreSQL (DBaaS) page.
Create PostgreSQL (DBaaS) page, enter the information required to create the service and select advanced options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version required Provide a list of PostgreSQL (DBaaS) versions Table. PostgreSQL (DBaaS) Image and version selection options - In the Service Information Input area, enter or select the required information.
Category required statusDetailed description Server name Prefix Required Server name where the DB will be installed - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
-) with a length of 3 to 13 characters
- A postfix such as 001, 002 is appended to the base server name to generate the actual server name
Cluster name Required Cluster name of DB servers - Enter using English letters, 3 to 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for DB installation - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server with 24 vCores or more
- For detailed information about the server types provided by PostgreSQL (DBaaS), refer to PostgreSQL(DBaaS) Server Type
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute Apply
Service Type > Block Storage Required Block Storage configuration used by the DB according to its purpose - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Select a storage type and then enter the capacity (refer to Create Block Storage for details on each Block Storage type)
- SSD: High‑performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes that use Samsung Cloud Platform KMS (Key Management System) encryption keys
- The configured storage type is applied identically to additional storage
- Enter capacity as a multiple of 8 within the range 16–5,120
- Because executing SQL or monthly batch jobs can cause large sorts that may interrupt service, a separate TEMP storage must be allocated and used
- Add: DATA, Archive, TEMP, Backup data storage areas
- After selecting Use, enter the storage’s purpose and capacity
- The storage type is applied the same as the type set for DATA, and capacity can be entered as a multiple of 8 within the range 16–5,120
- To add storage, click the Add button; to delete, click the x button. Up to 9 can be added
- Backup data is temporarily stored in the BACKUP storage before transmission
- If the data to be backed up exceeds 100 GB and changes frequently, it is recommended to add a separate BACKUP storage for reliable backup; set the backup capacity to about 60 % of the DATA capacity
- If a BACKUP storage is not added, the
/tmparea is used, and backup will fail if capacity is insufficient
- For each service, Archive, TEMP, and BACKUP storages are allocated only one Block Storage each
- Select a storage type and then enter the capacity (refer to Create Block Storage for details on each Block Storage type)
Redundant configuration Select Redundancy configuration status - When redundancy configuration is used, the DB instance is set up as an Active DB and a Standby DB
Network > Common Settings Required Network settings for servers created by the service - Select when you want to apply the same settings to all installed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be generated automatically
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway; when Use is checked, you can select a reserved IP from the VPC product’s Public IP pool. For more information, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select a reserved IP from the VPC product’s Public IP. For more details, refer to Public IP 생성하기
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day, start time, and duration
- It is recommended to set a maintenance window for stable management of the database. Patch operations will be performed at the scheduled time, causing service interruption
- If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
Table. PostgreSQL (DBaaS) Service Information Input Items - must start with a lowercase English letter and be entered using lowercase letters, numbers, and the special character (
- Enter or select the required information in the Database Configuration Required Information Input area.
Category required statusDetailed description Database name Required Server name applied during DB installation - must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
Database username Required DB user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Restricted database user names can be viewed in the Console
Database password Required Password to use when accessing the DB - Enter 8 to 30 characters, including letters, numbers, and special characters (excluding
“‘)
Database password verification Required Re-enter the same password to be used for DB access Database Port number Required Port number required for DB connection - Enter the DB port within the range 1200 ~ 65535
Backup > Use Select Backup usage - Select Use to set the backup file retention period, backup start time, and Archive backup interval
Backup > Retention period Select Backup retention period - Select the backup retention period, set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Period Selection Backup start time - Select backup start time
- The minutes (minutes) during which the backup runs are set randomly, and the backup end time cannot be set
Backup > Archive backup cycle Select Archive backup frequency - Select the archive backup frequency
- The archive backup frequency is recommended to be 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
Audit Log Settings Select Whether to store Audit Log - Select Enable to configure the Audit Log feature
- DDL, DML, and user connection information records are stored
- Users can specify the type of SQL statements to audit via the
log_statementparameter, and can modify it through the Parameter screen
- For detailed information about this parameter, refer to the PostgreSQL documentation
- Users can specify the type of SQL statements to audit via the
- Enabling Audit may degrade database performance
- DDL, DML, and user connection information records are stored
Parameter Required Parameters to be used in the DB - Lookup button can be clicked to view detailed information of the parameter
- Parameters can be modified after the DB creation is complete, and the DB must be restarted after any modifications
Database Encoding Essential Character encoding method to be used for the DB - Character set used when storing text data
- The DB is created with the selected encoding as the default setting
DB Locale Required Locale to be used for the DB - settings related to string handling, number/currency/date/time formatting, etc.
- The DB is created with default settings using the selected Locale
time zone Required Standard time zone for the database Table. PostgreSQL (DBaaS) Database configuration items - In the Additional Information Input area, enter or select the required information.
Category required statusDetailed description Tag Select Add Tag - Up to 50 per resource can be added
- After clicking the Add Tag button, enter or select Key, Value values
Table. PostgreSQL (DBaaS) Additional Information Input Fields
- Select the required information in the Image and version selection area.
Summary Review the detailed information and estimated charges generated in the panel, then click the Create button.
- Once creation is complete, check the created resource on the Resource List page.
View PostgreSQL (DBaaS) details
The PostgreSQL (DBaaS) service allows you to view and edit the full list of resources and detailed information. PostgreSQL(DBaaS) Details page consists of Details, Tags, Activity History tabs, and when the DB has a Replica configured, a Replica Information tab is added.
To view detailed information about the PostgreSQL (DBaaS) service, follow the steps below.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List Click the resource on the page to view detailed information. 3. PostgreSQL(DBaaS) Details Go to the page.
- PostgreSQL(DBaaS) Details The top of the page displays status information and additional feature details.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Creating cluster
- Editing: Cluster is transitioning to an operational state
- Error: Cluster encountered an error during operation
- If it occurs continuously, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Restarting cluster
- Running: Cluster is running normally
- Starting: Starting cluster
- Stopped: Cluster is stopped
- Stopping: Cluster is stopping
- Synchronizing: Synchronizing cluster
- Terminating: Terminating cluster
- Unknown: Unknown cluster status
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is transitioning to an upgrading state
Cluster control Button to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to active
View more features Cluster-related management buttons - Service status synchronization: Retrieve real-time DB service status
- Backup history: When backup is configured, verify successful execution and view the history
- Database recovery: Recover the DB based on a specific point in time
- Parameter management: View and modify DB configuration parameters
- Replica configuration: Set up a read‑only Replica cluster
- Replica configuration (Other Region): Set up a disaster‑recovery Replica in another region; if the account has no region to configure, the button is disabled
- DB user management: View and manage DB account (user) information registered in the DB
- DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB
- Archive settings management: Set archive file retention period and enable archive mode
- Export DB logs: Export logs stored via audit settings to the user’s Object Storage
- Migration configuration: Provide migration functionality using replication method
- OS (Kernel) upgrade: Upgrade the OS kernel version
Service termination Button to cancel the service Table. PostgreSQL (DBaaS) status information and additional features
- PostgreSQL(DBaaS) Details The top of the page displays status information and additional feature details.
Detailed information
PostgreSQL (DBaaS) List page allows you to view detailed information of the selected resource and, if needed, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation date and time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster type | Cluster types (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster name | Cluster name of the DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied during DB installation |
| Database username | DB user name |
| Planned Compute | Resources with Planned Compute configured
|
| maintenance period | DB patch work period setting status
|
| Backup | Backup Configuration Status
|
| Audit Log Settings | Audit Log configuration status
|
| time zone | Standard time zone for the database |
| DB Locale | Locale to use for the DB |
| Database Encoding | Character encoding to use for the DB |
| VIP | Virtual IP information
|
| Network | Network information where the DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP access control | Service access policy configuration
|
| Active & Standby | Active/Standby server type, default OS, additional Disk information
|
Replica information
Replica information tab is enabled only when a Replica is configured in the cluster. Through the Replica information tab, you can view the Master cluster name, the number of replicas, and the replication status of the Replica.
| Category | Detailed description |
|---|---|
| Master information | Name of the Master cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status in the Master cluster
|
tag
On the PostgreSQL (DBaaS) List page, you can view the tag information of the selected resource and add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Work History
On the PostgreSQL (DBaaS) List page, you can view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Managing PostgreSQL (DBaaS) Resources
If you need to change or restore the existing configuration options of a created PostgreSQL (DBaaS) resource, or require a Replica configuration, you can perform the operation on the PostgreSQL(DBaaS) Details page.
Control operation
If changes occur to a running PostgreSQL (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Active‑Standby servers via a switch‑over.
To control the operation of PostgreSQL(DBaaS), follow the steps below.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL (DBaaS) List On the page, click the resource you want to control. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Check the PostgreSQL (DBaaS) status and complete the change using the control button below.
- Start: DB service is installed on the server and the DB service is running (Running).
- Stop: The server hosting the DB service and the DB service itself are stopped.
- Restart: Only the DB service will be restarted.
- Switch Over: You can switch the DB’s Active server and Standby server.
Synchronize service status
You can synchronize the real-time service status of PostgreSQL (DBaaS).
To check the service status of PostgreSQL (DBaaS), follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List Click the resource on the page to view the service status. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Service Status Synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.
Change server type
You can change the configured server type.
To change the server type, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL (DBaaS) List page, click the resource whose server type you want to change. 3. PostgreSQL(DBaaS) Details Go to the page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Edit Server Type After selecting the server type in the popup window, click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. For a DB configured with redundancy, all redundant servers are added simultaneously.
- It is applied in the same way as the Storage type selected when creating the service.
- In a redundant DB setup, adding storage is applied simultaneously to the storage of both the Active and Standby DBs.
- If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. * First expand the Replica storage, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Go to the page.
- On the PostgreSQL (DBaaS) List page, click the resource to add storage. 3. PostgreSQL(DBaaS) Details Go to the page.
- Click the Add Disk button at the bottom of the details. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.
Expand storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In a redundant DB configuration, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL(DBaaS) List page, click the resource you want to change the server type for. 3. PostgreSQL(DBaaS) Details Go to the page.
- Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
- Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.
Cancel PostgreSQL (DBaaS)
You can cancel unused PostgreSQL (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact that may occur when the service is discontinued.
- For a DB with a Replica configured, terminating the Master DB does not delete the Replica. * If you also delete the replica, cancel it separately from the resource list.
- If you terminate the DB, all stored data and any configured backup data will be deleted.
To cancel PostgreSQL (DBaaS), follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL (DBaaS) List page, select the resource to cancel and click the Cancel Service button.
- After termination is complete, check on the PostgreSQL(DBaaS) list page whether the resource has been terminated.
2.1 - DB Service Manage
Users can manage PostgreSQL (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
Provides a feature that allows you to easily view and modify database configuration parameters.
Query Parameters
To retrieve configuration parameters, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource whose parameters you want to view or modify. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management in the popup window, click the Search button. The Search Notification popup window opens.
- Lookup Notification when the popup window opens, click the Confirm button. The lookup may take a short amount of time.
Modify Parameter
To modify the configuration parameters, follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource whose parameters you want to view or modify. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup opens.
- Parameter Management popup window, click the Search button. Search Notification popup window opens.
- Lookup Notification When the popup window opens, click the Confirm button. Retrieving may take a short amount of time.
- If a modification is needed, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
- When the input is complete, click the Complete button.
DB User Management
Provides management functions to retrieve DB user information and modify status information.
Query DB Users
To retrieve DB users, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Click the Service Home page’s PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource you want to view DB users for. PostgreSQL(DBaaS) Details page will be opened.
- Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
- DB User Management page, click the Search button. Retrieving the data may take a short time.
Changing DB User Status
Follow these steps to change the status of the retrieved DB user.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List On the page, click the resource whose DB user you want to modify. PostgreSQL(DBaaS) Details You will be taken to the page.
- Click the More button, then click the DB User Management button. You will be taken to the DB User Management page.
- On the DB User Management page, click the Search button. The query may take a short time.
- If modification is needed, click the Edit button, and change the status field value or enter remarks.
- When the input is complete, click the Complete button.
Managing DB Access Control
Provides IP-based DB user access control management functionality. Users can directly specify the IPs that can access the database, configuring it so that only authorized IPs are allowed access.
Query DB Access Control
Follow these steps to query DB users with IP access control enabled.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource you want to manage access control for. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a short time.
Add DB access control
To add IP access control, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. You will be taken to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource for which you want to add IP access control. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a short time.
- When the query is complete, click the Add button. The Add DB Access Control popup window opens.
- Add DB Access Control In the popup window, select the DB username and enter the IP address.
- When the input is complete, click the Complete button.
Delete DB access control
To delete IP access control, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Go to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource for which you want to delete IP access control. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button, then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- On the DB Access Control Management page, click the Search button. Retrieving the data may take a short time.
- When the query is complete, click the Delete button. The Delete popup window will open.
- Click the Confirm button on the Delete popup.
Manage Archive
Provides the ability to configure Archive mode and set the retention period for Archive logs, allowing users to flexibly configure Archive log management policies to suit their operational environment. Additionally, it provides a feature to manually delete Archive logs, allowing you to clean up unnecessary log data and manage system resources effectively.
Configure Archive mode
To set the Archive mode, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page: click the resource for which you want to set Archive mode. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- On the Archive Settings Management page, click the Search button. Retrieval may take a short time.
- Click the Edit button and select the usage status and retention period.
- When the edit is complete, click the Done button.
Delete Archive file
To delete the Archive file, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource for which you want to set Archive mode. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Archive Settings Management button. You will be taken to the Archive Settings Management page.
- Archive Settings Management page, if you want to delete all Archive files, click the Delete All Archives button; if you only want to delete backed-up Archive files, click the Delete Backed-up Archives button.
Modify Audit Settings
You can change the Audit log storage settings for PostgreSQL (DBaaS).
Follow these steps to change the Audit log storage settings for PostgreSQL (DBaaS).
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. You will be taken to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page: click the resource to view the service status. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the Edit icon of Audit Settings at the bottom of the detailed information. The Edit Audit Settings popup window opens.
- Edit Audit Settings After modifying the usage in the popup window, click the Confirm button.
- When Enable is selected, the Audit log feature is configured. Enabling the Audit log may degrade DB performance.
- If you turn off Use, the Audit log storage file will be deleted. Before turning it off, back up the Audit log file separately.
DB Log Export
Supports exporting log data that requires long-term retention among audit logs to Object Storage. Users can directly configure the log types to be stored, the target bucket for export, and the export interval. Based on the configured criteria, logs are copied to the specified Object Storage for retention. Additionally, to efficiently manage disk space, we provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for long-term archiving.
- To use the DB Log export feature, you must create an Object Storage. For creating an Object Storage, please refer to the Object Storage User Guide.
- Please be sure to check the expiration date and time of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
- Please ensure that authentication key information is not exposed externally.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Navigate to the PostgreSQL(DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource you want to export the DB Log from. PostgreSQL(DBaaS) Details page will open.
- Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
- On the DB Log Export page, click the Register button. You will be taken to the DB Log Export Register page.
- On the DB Log Export Registration page, after entering the required information, click the Complete button.
Category Required Detailed descriptionLog type Required Log type to be saved Save bucket name Required Object Storage bucket name to be saved Authentication key > Access key Required Access key for accessing the Object Storage you want to store Authentication key > Secret key Required Secret key for accessing the Object Storage you want to store File creation cycle Required File creation frequency in Object Storage Whether to delete original logs Selection Whether to delete the original logs when exporting to Object Storage Table. PostgreSQL (DBaaS) DB Log Export Configuration Items
Managing DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the Service Home page’s PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- Click the resource you want to manage DB Log export for on the PostgreSQL(DBaaS) List page. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button, then click the DB Log Export button. You will be taken to the DB Log Export page.
- On the DB Log Export page, click the More button for the log type you want to manage, then click Export Now, Edit, or Cancel.
- Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
- Edit: Modify the DB Log export mode setting.
- Cancel: Cancel the DB Log export mode setting.
Minor Version Upgrade
We provide version upgrade functionality for some feature improvements and security patches. Only Minor version upgrades within the same Major version are supported.
- First retrieve the service status by synchronizing it, then perform the version upgrade.
- Please perform the version upgrade after configuring a backup. If you do not set up a backup, you may be unable to recover some data if a problem occurs during the update.
- In a DB with a Replica configured, the Master DB version cannot be higher than the Replica version. Please check the Replica version first and, if necessary, perform a version upgrade.
- The backed-up data will be automatically deleted after the version upgrade is completed.
To upgrade the Minor Version, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource to upgrade the version. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the Edit button in the Image version item. The Version Upgrade popup window opens.
- Version Upgrade In the popup, select the updated version and backup setting, then click the Confirm button.
- Version Upgrade Notification Click the Confirm button in the popup window.
Configure Migration
Provides a Migration feature that synchronizes in real time with the live database and replicates using a Replication method without service interruption.
To configure Migration, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- From the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource to migrate. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button, then click the Migration configuration button. The Migration configuration popup opens.
- In the popup window, review the instructions and click the Confirm button. You will be taken to the Migration configuration page.
- Migration Configuration page, after entering the required information, click the Check Connection button.
- When the connection is complete, click the Complete button.
Category Required Detailed descriptionSource DB Database name Required Database name of the source DB to be migrated Source DB IP Required IP of the Source DB that is the migration target Source DB Port Required Port of the Source DB to be migrated Source DB username Required Username of the source DB that is the migration target Source DB password Required Password of the source DB that is the migration target Table. PostgreSQL (DBaaS) migration configuration items
Promote Migration Cluster to Master Cluster
You can promote a configured Migration Cluster to a Master Cluster.
To promote the Migration Cluster to Master, follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- From the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) List page.
- On the PostgreSQL(DBaaS) List page, click the resource to promote to Master. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Master Promotion button. The Master Promotion Notification popup window opens.
- In the Master Promotion Notification popup, click the Confirm button.
Upgrade OS Kernel
The OS kernel can be upgraded to improve the functionality of the running database and apply security patches.
- The service will be unavailable while the OS upgrade is in progress.
- The upgrade duration may vary depending on the version, and if the upgrade fails, it will be rolled back to the previous configuration.
- After the upgrade is complete, you cannot revert to the previous OS.
To upgrade the OS kernel, follow the steps below.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. You will be taken to the Service Home page of PostgreSQL(DBaaS).
- From the Service Home page, click the PostgreSQL(DBaaS) menu. You will be taken to the PostgreSQL(DBaaS) list page.
- PostgreSQL(DBaaS) List page, click the resource to upgrade the OS Kernel. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button, then click the OS(Kernel) Upgrade button. The OS(Kernel) Upgrade Notification popup window opens.
- OS(Kernel) Upgrade Notification In the popup window, review the instructions and click the Confirm button.
2.2 - Backing up and restoring the DB
Users can configure backups of PostgreSQL (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Backing up PostgreSQL(DBaaS)
PostgreSQL (DBaaS) provides a data backup feature based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.
Configure backup
For backup configuration of PostgreSQL(DBaaS), refer to PostgreSQL(DBaaS) 생성하기.
To modify the backup settings of the created resource, follow the steps below.
For reliable backups, we recommend adding a separate BACKUP storage or sufficiently expanding the storage capacity.
Especially when the backup data exceeds 100 GB and undergoes frequent changes, please provision additional storage amounting to about 60 % of the data size.
For instructions on adding and expanding storage, refer to the PostgreSQL(DBaaS) Add Storage and PostgreSQL(DBaaS) Expand Storage guides.
If a backup is configured, it will run at the designated time after the set schedule, and additional fees will be incurred based on the backup size.
If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
To set up a backup, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Navigate to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List page, click the resource you want to configure backup for. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Edit button of the backup item. 4. Backup Settings popup window opens.
- When setting up a backup, click Enable in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, and then click the Confirm button.
- If you stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Once user authentication is complete, the backup configuration is disabled and backup execution stops.
- If you stop the backup configuration, deselect Use in the Backup Settings popup and authenticate using the logged-in user’s mobile phone.
Check Backup History
To view the backup history, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List page, click the resource to view the backup history. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. Navigate to the PostgreSQL (DBaaS) List page.
- PostgreSQL(DBaaS) List page, click the resource to view the backup history. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
- When user authentication is completed, the backup file is deleted.
PostgreSQL(DBaaS) Recover
If a failure or data loss requires restoration from a backup file, you can recover using the recovery feature based on a specific point in time. When performing a PostgreSQL (DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds with the database’s configuration information and data.
To recover PostgreSQL (DBaaS), follow these steps.
- Click the All Services > Database > PostgreSQL(DBaaS) menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) resource Click the resource you want to restore on the list page. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Database Recovery button. 4. Go to the Database Recovery page.
- After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
Category required statusDetailed description Recovery Type Required Set the point in time the user wants to recover - Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
- Custom point: Recover to a user-specified point within the range of recoverable backup times. The recoverable period depends on the Archive backup cycle setting, allowing recovery from the start of the first backup up to 1 hour/30 minutes/10 minutes/5 minutes before the current time. Select the desired date and time for the backup
server name prefix Essential Recovery DB server name - must start with a lowercase English letter and use lowercase letters, numbers, and special characters (
-) to input 3 to 16 characters
- A postfix such as 001, 002 is appended to the base server name, generating the actual server name
Cluster name Required Cluster name of the recovery DB - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for the recovery DB installation - Standard: standard specifications commonly used
- High Capacity: large-capacity server with 24 vCores or more
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service request page
- For more details, see Planned Compute 신청하기
Service Type > Block Storage Required Block Storage settings used by the recovery DB - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Same as the storage type set in the original cluster
- Enter capacity as a multiple of 8 within the range 16 to 5,120
- Additional: Storage area for DATA, Archive, TEMP, Backup data
- Same as the storage type set in the original cluster
- In the recovery DB, only DATA, TEMP, and Archive purposes can be added.
- After selecting Use, enter the storage purpose and capacity
- To add storage, click the Add button; to delete, click the x button
- Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Database username Required Database username configured in the source DB Database Port number Required Database port number configured in the source DB IP access control Select IP address for accessing the recovery DB - Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.1/32,192.168.10.1/32), then click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - If you select Use, set the day of week, start time, and duration
- It is recommended to set a maintenance window for stable DB management. Patch operations will be performed at the scheduled time, causing service interruption
- If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.
Tag Select Add Tag - Add Tag after clicking the button Enter or select Key, Value values
Table. PostgreSQL (DBaaS) recovery configuration items
2.3 - Configure Read Replica
Users can enter the required information for a Read Replica through the Samsung Cloud Platform Console and create the service using detailed options.
Configure Replica
Through replica configuration, you can create replica servers for read-only or disaster recovery purposes. You can create up to 5 replicas per database.
To configure a Replica, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL(DBaaS) List page, click the resource to configure a Replica. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Replica configuration button. 4. Go to the Replica configuration page.
- After entering the information in the Replica configuration area, click the Complete button.
Category required statusDetailed description Region Required Region to configure the Replica - Replica configuration (Other Region)is displayed only when selected
Replica count Required Number of Replicas to configure - Up to 5 can be configured per cluster
- If you select more than one value, additionally enter the Replica name and service type information
Replica name Required Replica server name - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters(
-) enter 3 to 19 characters
- The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type Essential Replica server type - Standard: standard specification commonly used
- High Capacity: large-capacity server with 24 vCores or more
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Navigate to the Planned Compute service application page
- For more details, see Planned Compute 신청하기
Service Type > Block Storage Required Block Storage configuration for using a replica DB - Basic OS: Area used on the server where the DB is installed
- Applied identically according to the storage type set in the source DB
- Capacity cannot be set
- DATA: Storage area for table data, archive files, etc.
- Applied identically according to the storage type set in the source DB
- Capacity cannot be set
- Additional: Storage area for DATA, Archive, TEMP, Backup data
- Applied identically according to the storage type set in the source DB
- In a replica, only DATA and TEMP purposes can be added
- After selecting Use, enter the storage purpose and capacity. Capacity must be a multiple of 8 within the range 16 to 5,120
- To add storage, click the Add button; to delete, click the x button. Up to 9 can be added.
IP access control Select Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is not required
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
maintenance period Select Database maintenance window - Select Use to set the day, start time, and duration
- It is recommended to configure a maintenance window for stable database management. Patch operations will be performed at the scheduled time, causing service interruption
- If set to unused, we are not responsible for issues arising from patches not being applied.
tag Selection Add Tag - Add Tag After clicking the Add Tag button, enter or select Key and Value
Table. PostgreSQL (DBaaS) Replica configuration items
Reconfigure Replica
If a network failure or replication delay with the Master Cluster occurs, you can re-replicate the Master Cluster’s data using the Replica reconstruction feature.
To reconfigure the Replica, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- On the PostgreSQL(DBaaS) List page, click the resource to reconfigure the replica. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Replica Reconstruction Click the button. 4. Replica Reconfiguration Notification A popup window opens.
- Replica Reconfiguration Notification popup window, click the Confirm button.
Promoting a Replica Cluster to a Master Cluster
You can promote a fully configured Replica Cluster to a Master Cluster.
To promote a Replica Cluster to Master, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. 1. Go to the Service Home page of PostgreSQL (DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. 2. PostgreSQL (DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List page, click the resource to promote to Master. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the More button, then click the Master Promotion button. 4. Master Promotion Notification The popup window opens.
- Master Promotion Notification In the popup window, click the Confirm button.
2.4 - DB Server Connection
Scenario Overview
PostgreSQL(DBaaS) Server Connection The scenario involves creating a Bastion host (Virtual Server) and a Database service, and accessing the DB service through the Bastion host. To reliably connect to PostgreSQL (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish network connectivity using it. It is recommended to configure the Database service in a Private Subnet environment and the Bastion host in a restricted Public Subnet environment to maintain stability and a high level of security.
This scenario primarily describes creating a Bastion host and a Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Scenario components
You can build the scenario using the following services.
| Service group | service | Detailed description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that lets users subdivide the network within a VPC to match their purpose and scale. | |
| Networking | VPC > Public IP | A service that reserves a public IP and allocates and releases it to Compute resources. | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the Internet | |
| Networking | Security Group | Virtual firewall that controls server traffic | |
| Database | PostgreSQL(DBaaS) | A service that easily creates and manages EPAS in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- Since the default policy of a Security Group is Deny All, you must register only the allowed IPs.
- The All Open (Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
- By specifying the required IP and port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the steps below.
Set up the network
This explains the process of configuring the network environment for accessing the Bastion Host and Database services.
1-1. Create VPC
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- Click the VPC Creation button on the Service Home page. You will be taken to the VPC Creation page.
- On the VPC Creation page, enter the information required to create the service.
- Enter the IP range as
192.168.x.0/16.
- Enter the IP range as
- Summary panel, verify the detailed information and estimated billing amount generated there, and click the Complete button.
- After creation is complete, check the created resources on the VPC List page.
1-2. Create Subnet
- Click the All Services > Networking > VPC menu. You will be taken to the VPC Service Home page.
- On the Service Home page, click the Subnet menu. You will be taken to the Subnet List page.
- Click the Create Subnet button. You will be taken to the Create Subnet page.
- On the Subnet Creation page, enter the information required to create the service.
- Select the Subnet type as General.
- Select a pre‑created VPC.
- Enter the IP range as
192.168.x.0/24.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, check the created resources on the Subnet List page.
1-3. Create Internet Gateway
- Click the All Services > Networking > VPC menu. Go to the VPC’s Service Home page.
- On the Service Home page, click the Internet Gateway menu. You will be taken to the Internet Gateway List page.
- Click the Create Internet Gateway button. You will be taken to the Create Internet Gateway page.
- On the Internet Gateway Creation page, enter the required information to create the service.
- Select a pre‑created VPC.
- In the Firewall usage option, select Use.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resource on the Internet Gateway list page.
1-4. Create Public IP
- Click the All Services > Networking > VPC menu. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Public IP menu. You will be taken to the Public IP List page.
- Click the Public IP Reservation button. You will be taken to the Public IP Reservation page.
- On the Public IP reservation page, enter the required information needed to reserve the service.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resources on the Public IP List page.
1-5. Create Security Group
- Click the All Services > Networking > Security Group menu. Navigate to the Service Home page of Security Group.
- Click the Create Security Group button on the Service Home page. You will be taken to the Create Security Group page.
- Security Group creation Enter the required information needed to create the service on the page.
- Check the input information and click the Complete button.
- When creation is complete, check the created resources on the Security Group List page.
Create bastion host
Describes the process of configuring a Bastion Host that requires the database client to be installed.
2-1. Create Server Keypair
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
- Click the Create Keypair button. You will be taken to the Create Keypair page.
- On the Keypair Creation page, enter the required information needed to create the service.
- Verify the creation information and click the Complete button.
- The key can be downloaded only on the first attempt, and reissuance is not available.
- Please store the downloaded key in a secure location.
2-2. Create Bastion host
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- On the Service Home page, click the Virtual Server Creation button. You will be taken to the Virtual Server Creation page.
- On the Virtual Server Creation page, enter the required information to create the service.
- Select Windows for the image.
- Select the pre‑created VPC and Subnet.
- Click Use NAT, and select the reserved Public IP from 1-4. Create Public IP.
- 2-1. Create Server Keypair Connect the Keypair created there.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resources on the Virtual Server List page.
2-3. Verify Bastion host login ID and password
- Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
- Click the Virtual Server menu on the Service Home page. You will be taken to the Virtual Server List page.
- On the Virtual Serve List page, click the resource you created in 2-2. Bastion host Create. You will be taken to that resource’s detailed information page.
- On the detail page, click the RDP password view button in the Keypair name field. The RDP password view popup window will open.
- In the RDP password lookup popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
- After attaching, click the Password Check button. The ID and Password required to access the resource are displayed.
- The ID and password will later be used as credentials to access the Bastion host in 5-1. Bastion host Connecting.
Create Database
Describes the process of creating a Database service.
3-1. Create PostgreSQL (DBaaS) Service
- Click the All Services > Database > PostgreSQL(DBaaS) menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) Create button on the Service Home page. You will be taken to the PostgreSQL(DBaaS) Create page.
- PostgreSQL(DBaaS) Creation On the page, enter the required information to create the service.
- Select the pre‑created VPC and Subnet and connect them.
- Enter the database-related creation information on the required information input screen.
- Add the Bastion host IP in the IP access control section.
- The Database Port defaults to 2866, but the user can also specify it.
- In the Summary panel, verify the detailed information and estimated billing amount, then click the Complete button.
- After creation is complete, verify the created resource on the PostgreSQL(DBaaS) list page.
Configuring Rules
It explains the process of configuring rules for a user to connect to the Bastion host and rules for connecting to the Database from the Bastion host.
4-1. Security Group Add Security Rules
- Click the All Services > Networking > Security Group menu. Navigate to the Service Home page of Security Group.
- From the Service Home page, click the Security Group menu. You will be taken to the Security Group List page.
- Select the Security Group resource created in 1-5. Create Security Group. Navigate to the detailed information page of that resource.
- Click the Rules tab on the detail page. You will be taken to the Rules tab.
- On the Rules tab, click the Add Rule button. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
direction remote Target address Protocol Port Explanation Inbound CIDR User PC IP TCP 3389 (RDP) Bastion client PC → Bastion host Outbound CIDR DB IP TCP Database Port (manual entry) Bastion host → Database Table: Security Group rules that need to be added
4-2. Add IGW Firewall Rule
- All Services > Networking > Firewall Click the menu. Go to the Service Home page of the Firewall.
- On the Service Home page, click the Firewall menu. You will be taken to the Firewall List page.
- On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway Creation. You will be taken to the detailed information page of that resource.
- Click the Rules tab on the detail information page. You will be taken to the Rules tab.
- Click the Add Rule button on the Rules tab. You will be taken to the Add Rule popup.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
origin address Destination address Protocol Port Operation direction Explanation Bastion connection PC IP Bastion host IP TCP 3389(RDP) Allow Inbound User PC → Bastion host Table. Internet Gateway Firewall rules that need to be added
Connect to Database
Describes the process of a user accessing the database via a DB client program.
This guide explains how to connect using pgAdmin. Since there are various database client programs and CLI utilities, you may install and use the tool that best fits your needs.
5-1. Connecting to Bastion host
- In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
- When the remote desktop connection succeeds, the user credential input window opens. Enter the ID and Password you verified in 2-3. Bastion host access ID and PW verification and click the Confirm button.
5-2. Install DB connection client program (pgAdmin) on the Bastion host
- Go to the official pgAdmin page and download the pgAdmin program.
- pgAdmin program download URL: https://www.pgadmin.org/download/
- Connect the user’s PC hard drive to upload the file to the Bastion host.
- In the Local Resources tab of the Remote Desktop Connection, click the Details button for the Local Devices and Resources item.
- Select the local disk of the location where the file was downloaded on the drive, and click the OK button.
- Copy the downloaded file, upload it to the Bastion Host, and click the pgAdmin installer to install.
5-3. Connect to the database using the DB client program (pgAdmin)
- Run pgAdmin and click the Add New Server button.
- In the Register - Server popup window, enter the Database server information created in 3-1. PostgreSQL(DBaaS) 서비스 생성하기 into the General and Connection tabs, and click the Save button.
Screen (tab) Required input field input value General Name Custom (ex. service name) Connection Host name/address Database server IP Connection Port Database Port Connection Maintenance database Database name Connection Password Database password Table.DB connection client program input fields - Click the name of the database created in pgAdmin to connect.
- After connecting, you can perform simple queries, among other tasks.
2.5 - Extension Use
PostgreSQL(DBaaS) Extension usage
You can view the list of extensions that can be installed in the current database with the SQL statement below.
SQL> select * from pg_available_extensions;
PostgreSQL (DBaaS) includes the following items in addition to the default extensions for each version.
| Extension name | Explanation |
|---|---|
| pgaudit | Provides detailed audit logging at the session and object level |
| pg_cron | A scheduler that can schedule jobs using cron syntax within the database. |
| pg_hint_plan | Provides a feature to apply hint clauses to SQL execution plans. |
| pgvector | Provides vector data types and AI vector operation features such as similarity search. |
| postgis | GIS (Geographic Information System) provides spatial object storage and spatial query functionality |
If you need to install additional extensions beyond the items above, refer to Support Center > Inquiry and contact us.
- After a request is received, we will review it and proceed with installation. Please note that some extensions may not function properly during replica configuration and recovery.
3 - API Reference
4 - CLI Reference
5 - Release Note
PostgreSQL(DBaaS)
- The OS (Kernel) upgrade feature enhances the latest security patches and stability.
- You can set up a disaster-recovery Replica using the Replica configuration (Other Region) feature.
- Add PostgreSQL (DBaaS) feature
- Add Second-Generation Server Type
- Add a second‑generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) processor. For more details, see PostgreSQL(DBaaS) 서버 타입.
- DB user and access control management and Archive configuration feature added
- For more details, see DB User Management, DB Access Control Management, Archive Management.
- DB Audit Log Export feature added
- For more details, refer to DB Log Export.
- Backup Notification Feature provided
- Provides notification functionality for backup success and failure. For detailed information, refer to Create Notification Policy.
- Add Migration feature
- Provides replication-based zero-downtime data migration functionality. For more details, see Configuring Migration.
- Add HDD, HDD_KMS types to Block Storage type
- Add Second-Generation Server Type
- PostgreSQL(DBaaS) feature change
- Add new PostgreSQL versions: 13.16, 14.13, 15.8
- Add second-generation server type
- Add a 2nd‑generation (dbh2) server type based on Intel 4th‑generation (Sapphire Rapids) Processor. For details, see PostgreSQL(DBaaS) server type.
- After creating the service, Block Storage capacity expansion is possible.
- Server-specific network IP configuration feature has been added allowing either a common configuration or a server-specific configuration depending on the intended use.
- Samsung Cloud Platform common feature changes
- Account, IAM, Service Home, tags, and other common CX changes have been applied.
- A volume-encrypted storage selection option has been added to the Block Storage type.
- A Role Switch (Active ↔ Standby) feature has been added for the Active DB and Standby DB configured with redundancy.
- It is linked with the cloud monitoring service, enabling performance and log monitoring of DB instances.
- Based on the server type selected by the customer, Planned Compute policy can be set.
- A PostgreSQL (DBaaS) service that enables easy creation and management of PostgreSQL in a web environment has been launched.

