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 the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Resource-Specific Monitoring Service Application Guide
- 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, settings configured by users linked with existing Cloud Monitoring (e. Check the event policy, etc., 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, Cloud Monitoring data cannot be viewed. * 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 PostgreSQL(DBaaS) services 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.
- This service is provided on a Single-AZ basis.
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 Create PostgreSQL (DBaaS) button. 2. Go to the PostgreSQL(DBaaS) Creation page.
On the PostgreSQL(DBaaS) Creation page, enter the information required to create the service and select detailed options.
- In the Image and version selection area, select the required information.
Category Required statusDetailed description Image version Required Provide a list of PostgreSQL (DBaaS) versions Table. PostgreSQL (DBaaS) Image and version selection items - Enter or select the required information in the Service Information Input area.
Category Required statusDetailed description Server name Prefix Required The server name where the DB will be installed - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (
-) be entered with a length of 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name Required Cluster name of DB servers - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service > Server Type Required Server type for DB installation - Standard: Standard specification commonly used
- High Capacity: Large-capacity server with 24 vCore or more
- For detailed information about the server types provided by PostgreSQL (DBaaS), refer to PostgreSQL(DBaaS) 서버 타입
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied by Planned Compute per resource
- Create Planned Compute Service: Go to the Planned Compute service application page
- For more details, refer to Planned Compute 신청하기
Service Type > Block Storage Required Configure Block Storage 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 Block Storage 생성하기 for details on each Block Storage type)
- SSD: High‑performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption keys
- The configured storage type is applied identically to additional storage
- Enter the capacity as a multiple of 8 within the range 16 to 5,120
- Since executing SQL or monthly batch jobs can cause service interruptions due to large sorts, a separate TEMP storage must be allocated and used
- Add: DATA, Archive, TEMP, Backup data storage areas
- After selecting Use, enter the storage purpose and capacity
- The storage type is applied the same as the type set for DATA, and the capacity can be entered as a multiple of 8 within the range 16 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; set the backup capacity to about 60 % of the DATA capacity.
- If a BACKUP storage is not added, the
/tmparea is used, and backup fails if the 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 Block Storage 생성하기 for details on each Block Storage type)
Redundant configuration Selection Redundancy configuration status - When redundancy is used, the DB instance is configured as an Active DB and a Standby DB.
Network > Common Settings Required Network settings for servers created by the service - Select when you want to apply the same settings to all installed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Each server’s IP is 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 details, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
| Selection | Service Access Policy Configuration
- Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
- Enter the IP 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 IP
- If you select Use, you can set the day of week, start time, and duration
- The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and any patch work within that period must be carried out directly by the user.
- We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
Table. PostgreSQL (DBaaS) service information input items - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (
- Enter required database configuration information in this area, enter or select the necessary information.
Category required statusDetailed description Database name Required Server name applied during DB installation - must start with an English letter and be entered using English letters and numbers, 3 ~ 20 characters
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 (
“‘excluded)
Check database password Required Re-enter the same password to use for DB access Database Port number Required Port number required for DB connection - Enter the DB port within the range 1200 ~ 65535
Backup > Use Selection Backup usage - Select Use to set the backup file retention period, backup start time, and Archive backup interval
Backup > Retention Period Selection Backup retention period - Select the backup retention period, and set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on their size
Backup > Backup Start Period Selection Backup start time - Select backup start time
- The minutes (minutes) at which the backup runs are set randomly, and the backup end time cannot be set
Backup > Archive backup schedule Selection 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 configuration Selection Whether to store Audit Log - Select Use to configure the Audit Log feature
- DDL, DML, and user connection information records are stored
- The user 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
- The user 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
ServiceWatch log collection Selection ServiceWatch log collection status - Select Use to configure the ServiceWatch log collection feature
- Provided free up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB
- When collected, log groups and log streams are created automatically, and they cannot be deleted until the resources are removed
- To prevent exceeding 5 GB, direct deletion of log data or shortening the retention period is recommended
Parameter Required Parameters to be used in the DB - Click the Query button to view the parameter’s detailed information
- Parameters can be modified after the DB creation is complete, and the DB must be restarted after modification
Database Encoding Required Character encoding method to be used for the DB - Character set used when storing text data
- The DB is created with the selected encoding as the default setting
DB Locale Required Locale - settings related to string handling, number/currency/date/time display formats, etc.
- The DB is created with default settings using the selected Locale
Time zone Required Standard time zone used by 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 Selection 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
- In the Image and version selection area, select the required information.
Summary Verify the detailed information and estimated charges generated in the panel, then click the Create button.
- Once creation is complete, verify the created resource on the Resource List page.
PostgreSQL(DBaaS) View detailed information
The PostgreSQL (DBaaS) service allows you to view and edit the full resource list and detailed information. On the PostgreSQL(DBaaS) Details page, it consists of the Details, Tags, Activity History tabs, and for databases with a Replica configured, a Replica Information tab is added.
Follow the steps below to view detailed information about the PostgreSQL (DBaaS) service.
- 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 Click the resource to view detailed information on the page. 3. PostgreSQL(DBaaS) Details Go to the page.
- PostgreSQL(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Cluster is being created
- Editing: Cluster is transitioning to an operational state
- Error: Cluster encountered an error during operation
- 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 being stopped
- Synchronizing: Synchronizing the cluster
- Terminating: Deleting the cluster
- Unknown: Cluster status is unknown
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is transitioning to an upgrading state
Cluster control Buttons to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to Active
View more features Cluster-related management buttons - Service Status Synchronization: Retrieve real-time DB service status
- Backup History: Check backup execution status and view history when backups are configured
- Database Recovery: Recover the database to a specific point in time
- Parameter Management: View and modify DB configuration parameters
- Replica Configuration: Configure a read‑only Replica cluster
- Replica Configuration (Other Region): Configure a disaster‑recovery Replica in another region; the button is disabled if the account has no region available for configuration
- DB User Management: View and manage DB account (user) information registered in the database
- DB Access Control Management: Register and revoke allowed IP addresses based on DB accounts registered in the database
- Archive Settings Management: Configure archive file retention period and archive mode
- DB Log Export: Export stored logs to the user’s Object Storage via Audit settings
- Migration Configuration: Provides migration functionality using a replication method
- Block Storage Usage Management: Provides usage query functionality for each Block Storage type
- OS (Kernel) Upgrade: Upgrade the OS Kernel version
Service cancellation Cancel Service button Table. PostgreSQL (DBaaS) status information and additional features
- PostgreSQL(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
Detailed Information
PostgreSQL(DBaaS) List page lets you view detailed information of the selected resource and, if necessary, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation Date/Time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date and time | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster type | Cluster type (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster name | Cluster name of the configured DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied during DB installation |
| Database username | DB user name |
| Planned Compute | Resource status with Planned Compute configured
|
| Maintenance Period | DB patch work period setting status
|
| Backup | Backup configuration status
|
| Audit Log configuration | Audit Log configuration status
|
| ServiceWatch log collection | ServiceWatch Log Collection Configuration Status
|
| Time zone | Standard time zone used by the database |
| DB Locale | Locale to use in the DB |
| Database Encoding | Character encoding to use for the DB |
| VIP | Virtual IP information
|
| Network | Network information 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. Replica information tab allows you to 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
PostgreSQL(DBaaS) List page allows you to view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Job History
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
|
PostgreSQL(DBaaS) Managing 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 task on the PostgreSQL(DBaaS) Details page.
Operation Control
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 page, click the resource you want to control. 3. Go to the PostgreSQL(DBaaS) Details 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 where the DB service is installed and the DB service will be 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 PostgreSQL (DBaaS).
To check the service status of 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) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List page, click the resource to view the service status. 3. Navigate to the PostgreSQL(DBaaS) Details page.
- Click the Service status synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query is completed, the status in the server information item is updated, and the cluster changes to 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. 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 to change the server type. 3. Navigate to the PostgreSQL(DBaaS) Details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Edit Server Type In the popup window, select the server type, then click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. In a redundant DB setup, all redundant servers are added simultaneously.
- It is applied in the same way as the Storage type selected when creating the service.
- For a DB configured with redundancy, adding storage is applied simultaneously to the storage of both the Active DB and the Standby DB.
- A Replica’s storage cannot be larger than the primary’s storage. * Expand the Replica storage first, then expand the Master 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. 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 Click the resource to add storage on the page. 3. PostgreSQL(DBaaS) Details Go to the page.
- Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.
Expanding storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In a redundant DB setup, 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 to change the server type. 3. PostgreSQL(DBaaS) Details Navigate to the page.
- Click the Edit icon for the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage A popup window opens.
- Edit Additional Storage After entering the expanded capacity in the popup window, click the Confirm button.
PostgreSQL(DBaaS) Terminate
You can cancel unused PostgreSQL (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be discontinued immediately, so you should proceed with the termination only after fully considering the impact of the service interruption.
- Replica is not deleted together. * If you also delete the Replica, handle it separately in the resource list.
- If you terminate the DB, all stored data and any configured backup data will be deleted.
To cancel 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) menu. 2. PostgreSQL(DBaaS) List Navigate to the page.
- PostgreSQL(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
- After termination is complete, check whether the resource has been terminated on the PostgreSQL(DBaaS) list page.