It provides a service to easily create and manage relational, unstructured, and data analysis databases in a web environment.
This is the multi-page printable view of this section. Click here to print.
Database
- 1: EPAS(DBaaS)
- 1.1: Overview
- 1.1.1: Server Type
- 1.1.2: Monitoring Metrics
- 1.2: How-to guides
- 1.2.1: EPAS(DBaaS) server connection
- 1.2.2: Managing DB Service
- 1.2.3: DB Backup and Recovery
- 1.2.4: Configuring Read Replica
- 1.2.5: Extension use
- 1.3: API Reference
- 1.4: CLI Reference
- 1.5: Release Note
- 2: PostgreSQL(DBaaS)
- 2.1: Overview
- 2.1.1: Server Type
- 2.1.2: Monitoring Metrics
- 2.2: How-to guides
- 2.2.1: Managing DB Services
- 2.2.2: DB Backup and Recovery
- 2.2.3: Read Replica Setup
- 2.2.4: Connect to DB Server
- 2.2.5: Using Extensions
- 2.3: API Reference
- 2.4: CLI Reference
- 2.5: Release Note
- 3: MariaDB(DBaaS)
- 3.1: Overview
- 3.1.1: Server Type
- 3.1.2: Monitoring Metrics
- 3.2: How-to guides
- 3.2.1: MariaDB(DBaaS) server connection
- 3.2.2: Managing DB Services
- 3.2.3: DB Backup and Recovery
- 3.2.4: Configuring Read Replica
- 3.3: API Reference
- 3.4: CLI Reference
- 3.5: Release Note
- 4: MySQL(DBaaS)
- 4.1: Overview
- 4.1.1: Server Type
- 4.1.2: Monitoring Metrics
- 4.2: How-to guides
- 4.2.1: MySQL(DBaaS) server connection
- 4.2.2: Managing DB Services
- 4.2.3: DB Backup and Recovery
- 4.2.4: Setting up Read Replica
- 4.3: API Reference
- 4.4: CLI Reference
- 4.5: Release Note
- 5: Microsoft SQL Server(DBaaS)
- 5.1: Overview
- 5.1.1: Server Type
- 5.1.2: Monitoring Metrics
- 5.2: How-to guides
- 5.2.1: Managing DB Services
- 5.2.2: DB Backup and Recovery
- 5.2.3: Add Secondary
- 5.2.4: Microsoft SQL Server(DBaaS) server connection
- 5.3: API Reference
- 5.4: CLI Reference
- 5.5: Release Note
- 6: CacheStore(DBaaS)
- 6.1: Overview
- 6.1.1: Server Type
- 6.1.2: Monitoring Metrics
- 6.2: How-to guides
- 6.2.1: Managing CacheStore Service
- 6.2.2: CacheStore Backup and Recovery
- 6.2.3: CacheStore(DBaaS) server connection
- 6.3: API Reference
- 6.4: CLI Reference
- 6.5: Release Note
1 - EPAS(DBaaS)
1.1 - Overview
Service Overview
EPAS (DBaaS) is a relational database management system (RDBMS) with high compatibility with Oracle databases. Samsung Cloud Platform provides an environment that can automate EPAS installation and perform management functions for operation through a web-based console.
EPAS(DBaaS) is designed as a high-availability architecture that performs storage-based data replication and minimizes failover time. To prevent data loss, when the content of the Active server changes, it is synchronously replicated to the Standby server, and up to five read-only servers called Replicas are provided for read load balancing and disaster recovery (DR). Additionally, to prepare for issues with the DB server or data, it offers an automatic backup function at user-specified times, supporting data recovery at the desired point in time.
Provided Features
EPAS(DBaaS) provides the following functions.
- Auto Provisioning (Auto Provisioning): Installation and configuration of Database (DB) is possible via UI, and provides an Active-standby redundancy configuration built on storage replication. In case of an Active server failure, automatic failover to Standby occurs.
- Operation Control Management: Provides a function to control the status of running servers. In addition to start and stop, restart is possible if there is an issue with the DB or to apply configuration values. In case of high availability (HA) configuration, the user can directly perform node switching of Active-Standby via Switch-over.
- Backup and Recovery: Provides data backup functionality based on its own backup command. Backup time slots and storage agencies can be set by the user, and additional fees are incurred depending on backup volume. It also provides a recovery function for backed‑up data, and when the user performs a recovery, a separate DB is created and recovery proceeds to the point in time selected by the user (backup save point, user‑specified point). If recovery is set to a user‑specified point, the recovery point can be set to 5 minutes/10 minutes/30 minutes/1 hour before based on the stored backup file and archive file.
- Version Management: Provides version upgrade (Minor) functionality according to some feature improvements and security patches. Whether to perform a backup for the version upgrade can be selected by the user, and if a backup is performed, data is backed up before applying the patch, then the DB engine is updated.
- Replica configuration: You can add up to 5 read-only Read Replicas, enabling read performance scaling and load balancing.
- Audit setting: Provides an Audit setting feature that can monitor the user’s DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) execution.
- Parameter management: Performance improvement and security-related DB configuration parameter modifications are possible.
- Service status query: Retrieve the final status of the current DB service.
- Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
- DB User Management: Query and manage DB account (user) information registered in the DB.
- DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
- Archive Management: You can set the archive file retention period (1 day~35 days) within the DB server and configure the archive mode (On/Off).
- DB Log Export: Through Audit settings, saved logs can be exported to the user’s Object Storage.
- Migration: Synchronize data in real-time with the operating database, and support migration using the Replication method without service interruption.
Components
EPAS (DBaaS) provides pre-validated engine versions and various server types. Users can select and use them according to the scale of the service they want to configure.
Engine Version
The engine versions supported by EPAS (DBaaS) are as follows.
Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.
According to the supplier’s policy, the EOS and EoTS dates may change, so please refer to the supplier’s license management policy page for details.
| Provided version | EOS Date(Samsung Cloud Platform New creation stop date) | EoTS Date(Community Technical support end date) |
|---|---|---|
| 14.17 | 2026-06 (scheduled) | 2026-12-01 |
| 14.18 | 2026-06 (scheduled) | 2026-12-01 |
| 15.12 | 2027-09 (scheduled) | 2028-02-13 |
| 15.13 | 2027-09 (scheduled) | 2028-02-13 |
| 16.8 | 2028-06 (scheduled) | 2028-11-09 |
| 16.9 | 2028-06 (scheduled) | 2028-11-09 |
Server Type
The server types supported by EPAS (DBaaS) are as follows.
For detailed information about the server types provided by EPAS(DBaaS), please refer to EPAS(DBaaS) server type.
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. For details, 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 independent virtual network in a cloud environment |
1.1.1 - Server Type
EPAS(DBaaS) Server Type
EPAS(DBaaS) provides server types with various combinations of CPU, Memory, Network Bandwidth, and more. When creating an EPAS(DBaaS), the Database Engine is installed according to the selected server type based on the intended use.
The server types supported by EPAS(DBaaS) are as follows:
Standard db1v2m4
Classification | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Classification of provided server types
|
| Server Specification | db1 | Classification of provided server types and generations
|
| Server Specification | v2 | Number of vCores
|
| Server Specification | m4 | Memory capacity
|
db1 Server Type
The db1 server type of EPAS(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
- Supports up to 16 vCPUs and 256 GB of memory
- Up to 12.5 Gbps networking speed
| Classification | 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 |
dbh2 Server Type
The dbh2 server type of EPAS(DBaaS) is provided with high-capacity server specifications and is suitable for large-scale data processing database workloads.
- Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
- Supports up to 128 vCPUs and 1,536 GB of memory
- Up to 25Gbps networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Up to 25 Gbps |
1.1.2 - Monitoring Metrics
EPAS(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics of EPAS (DBaaS) that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
EPAS(DBaaS) server monitoring metrics refer to the Virtual Server Monitoring Metrics guide.
| Performance Item | Detailed Description | Unit |
|---|---|---|
| Active Locks [Access Exclusive] | Access Exclusive Locks count | cnt |
| Active Locks [Access Share] | Access Share Lock count | cnt |
| Active Locks | Active Locks count | cnt |
| Active Locks [Total] | Active Locks total count | 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 count usage rate(%) | % |
| DB Age Max | Database age (frozen XID) value | age |
| Exclusive Locks | Exclusive Locks count | cnt |
| Idle In Transaction Sessions | Number of sessions in idle in transaction state | cnt |
| Idle In Transaction Sessions [Total] | Idle in transaction state Session total count | cnt |
| Idle Sessions | Number of idle sessions | cnt |
| Idle Sessions [Total] | Total number of idle sessions | cnt |
| Row Exclusive Locks | Row Exclusive Locks count | cnt |
| Row Share Locks | Row Share Locks count | cnt |
| Share Locks | Share Locks count | cnt |
| Share Row Exclusive Locks | Share Row Exclusive Locks count | cnt |
| Share Update Exclusive Locks | Share Update Exclusive Locks count | cnt |
| Slowqueries | Number of SQL queries running for a long time (5 minutes or more) | 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 waiting lock sessions (by DB) | cnt |
| Wait Locks [Long Total] | Long duration (300 seconds) Lock waiting session count | 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 |
1.2 - How-to guides
The user can enter the required information for EPAS (DBaaS) and select detailed options through the Samsung Cloud Platform Console to create the service.
Creating EPAS(DBaaS)
You can create and use the EPAS (DBaaS) service from the Samsung Cloud Platform Console.
- Please configure the VPC’s Subnet type as General before creating the service.
- If the Subnet type is Local, the creation of the corresponding Database service is not possible.
- If you load more than 2 TB of large data, backups may take a long time or the DB’s performance may degrade. To prevent this, you need to consider operational aspects such as cleaning up unnecessary data or moving old data to a statistical collection environment.
To create EPAS (DBaaS), follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
- Service Home on the page click the EPAS(DBaaS) Creation button. Navigate to the EPAS(DBaaS) Creation page.
- Create EPAS (DBaaS) page, enter the information required to create the service, and select detailed options.
- Image and Version Selection Select the required information in the area.
Category RequiredDetailed description Image version Required Provide version list of EPAS (DBaaS) Table. EPAS(DBaaS) Image and Version Selection Items - Service Information Input area, please enter or select the required information.
Category RequiredDetailed description Server Name Prefix Required Server name where DB will be installed - Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (
-) to input 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is attached to create the actual server name
Cluster Name Required Cluster name of DB servers - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type where DB will be installed - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server with 24 vCore or more
- For detailed information about the server types provided by EPAS (DBaaS), refer to EPAS(DBaaS) Server Type
Service Type > Planned Compute Select Status of resources with Planned Compute set - In Use: Number of resources with Planned Compute set that are currently in use
- Configured: Number of resources with Planned Compute set
- 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 Apply for Planned Compute
Service Type > Block Storage Required Block Storage settings used by DB according to purpose - Base OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Select the storage type and then enter the capacity. (For details on each Block Storage type, refer to Create Block Storage)
- SSD: High‑performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes using Samsung Cloud Platform KMS (Key Management System) encryption keys
- Select the storage type and then enter the capacity. (For details on each Block Storage type, refer to Create Block Storage)
- The configured storage type is applied identically to additional storage
- Capacity must be entered as a multiple of 8 within the range 16–5,120
- Since large sorts during SQL execution or monthly batch processes can cause service interruption, a separate TEMP storage must be allocated and used
- Add: DATA, Archive, TEMP, Backup data storage areas
- Select Use, then enter the storage purpose and capacity
- The storage type is applied the same as set for DATA, and capacity can be entered as a multiple of 8 within the range 16–5,120
- Click the + button to add storage, and the x button to delete. Up to 9 can be added
- Backup data is temporarily stored in 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 no BACKUP storage is added, using the
/tmparea is recommended
- For each service, only one Block Storage is allocated for Archive, TEMP, and BACKUP
Redundancy Configuration Select Redundancy Configuration Status - If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
Network > Common Settings Required Network settings where servers generated by the service are installed - Select if you want to apply the same settings to all servers being installed
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be auto‑generated
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select a reserved IP from the VPC product’s Public IP pool. For more information, see Create Public IP.
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select if you want to apply different settings per installed server
- Select a pre-created VPC, Subnet, IP, Public NAT
- Enter each server’s IP
- 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, see Create Public IP
IP Access Control Select Service Access Policy Settings - Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required.
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
Maintenance Period Select DB Maintenance Period - Use is selected, set the day of the week, start time, and duration
- It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption
- If set to not use, Samsung SDS is not responsible for issues arising from patches not being applied
Table. EPAS (DBaaS) Service Information Input Items - Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (
- Image and Version Selection Select the required information in the area.
- Database configuration required information input area, please input or select the required information.
Category RequiredDetailed description Database name Required Server name applied when installing DB - Start with an English letter, and use English letters and numbers, input 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 ~ 20 characters
- Restricted Database usernames can be checked in the Console
Database password Required Password to use when accessing the DB - Enter 8-30 characters including letters, numbers, and special characters (
“‘excluded)
Database Password verification Required Re-enter the same password to be used when accessing the DB Database Port number Required Port number required for DB connection - Enter DB port within the range 1,024 ~ 65,535
Backup > Use Select Whether to use backup - Select Use to set backup file retention period, backup start time, and Archive backup cycle.
Backup > Retention Period Select Backup Retention Period - Select the backup retention period. File retention period can be set from 7 days to 35 days.
- Backup files incur additional charges based on size.
Backup > Backup Start Period Select Backup Start Time - Select backup start time
- The minutes (minutes) when the backup is performed are set randomly, and the backup end time cannot be set
Backup > Archive backup frequency Select Archive backup frequency - Select the Archive backup frequency
- Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
Audit Log Settings Select Whether to store Audit Log - Select Use to configure the Audit Log feature
- DDL, DML, SELECT, and user connection information records are stored
- Users can specify the types of SQL statements to audit via the
edb_audit_statementparameter, and can modify it through the Parameter screen
- Refer to the EDB documentation for details on this parameter
- Users can specify the types of SQL statements to audit via the
- Enabling Audit may degrade DB performance
Parameter Required DB configuration parameters - View button click to view detailed information of the parameter
- Parameters can be modified after the service creation is completed, and after modification, the DB must be restarted
Database Encoding Required Character encoding method to be used for the DB - Character set used when storing text data
- The DB is created with the selected encoding as the default setting
DB Locale Required Locale to use for the DB - Settings related to string processing, number/currency/date/time display formats, etc.
- The DB is created with the selected Locale as the default setting
Time zone Required Standard time zone to be used by the Database License Required Check EPAS License - As a verification item for license usage, you cannot proceed to the next step unless you click confirm.
Table. EPAS(DBaaS) Database configuration items- Enter additional information area, please input or select the required information.
Category Required or notDetailed description Tag Select Add Tag - Up to 50 can be added per resource
- After clicking the Add Tag button, enter or select Key, Value values
Table. EPAS (DBaaS) Additional Information Input Items
- 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 Resource List page.
EPAS(DBaaS) Check detailed information
EPAS(DBaaS) service can view and edit the full resource list and detailed information. EPAS(DBaaS) Detail page consists of Detail Information, Tag, Operation History tabs, and for a DB with a Replica configured, a Replica Information tab is additionally provided.
To view detailed information about the EPAS (DBaaS) service, follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- Click the resource to view detailed information on the EPAS(DBaaS) List page. Move to the EPAS(DBaaS) Details page.
- EPAS(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
Category Detailed description Cluster Status Cluster status with DB installed - Creating: Creating cluster
- Editing: Cluster is changing to operation execution state
- Error: Cluster error occurred during operation execution
- If it occurs continuously, contact the administrator
- Failed: Cluster failed during creation process
- Restarting: Restarting cluster
- Running: Cluster is operating normally
- Starting: Starting cluster
- Stopped: Cluster is stopped
- Stopping: Cluster is in stopping state
- Synchronizing: Synchronizing cluster
- Terminating: Terminating cluster
- Unknown: Unknown cluster status
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is changing to upgrade execution state
Cluster Control Buttons to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to active
More features Cluster related management buttons - Service status synchronization: Real-time DB service status lookup
- Backup history: If backup is set, check whether backup runs normally and view history
- Database recovery: Recover DB based on a specific point in time
- Parameter management: View and modify DB configuration parameters
- Replica configuration: Set up a read-only cluster as a Replica
- DB user management: View and manage DB account (user) information registered in the DB
- DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB
- Archive management: Set archive file retention period and archive mode
- Export DB Log: Through Audit settings, export stored logs to user’s Object Storage
- Migration configuration: Provide Migration function using Replication method
Service termination Button to cancel the service Table. EPAS (DBaaS) status information and additional features
- EPAS(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
Detailed Information
EPAS(DBaaS) List page allows you to view detailed information of the selected resource and, if necessary, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in the respective 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 |
| Creator | User who created the service |
| Creation time | Service creation time |
| Editor | User who modified the service information |
| Modification Time | Date and time when service information was modified |
| Image/Version | Installed DB image and version information
|
| Cluster Type | Cluster Type (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster Name | Name of the cluster composed of DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied when installing DB |
| Database username | DB user name |
| Planned Compute | Resource status with Planned Compute configured
|
| Maintenance Period | DB Maintenance Period Status
|
| Backup | Backup Settings Status
|
| Audit Log Settings | Audit Log Settings Status
|
| Time zone | Standard time zone used by the Database |
| DB Locale | Locale to use for DB |
| Database Encoding | Character encoding method to be used in DB |
| VIP | Virtual IP information
|
| Network | Network information where DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP Access Control | Service Access Policy Settings
|
| 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 check the master cluster name, replica count, and Replica status.
| Category | Detailed description |
|---|---|
| Master Information | Name of Master Cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica Status | Replica server status created in the Master cluster
|
Tag
EPAS(DBaaS) List page 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
|
Work History
On the EPAS(DBaaS) List page, you can view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Work History List | Resource Change History
|
EPAS(DBaaS) Manage Resources
If you need to change or restore the existing configuration options of a created EPAS (DBaaS) resource, or require a Replica configuration, you can perform the work on the EPAS (DBaaS) Details page.
Operating Control
If changes occur to the running EPAS (DBaaS) resources, you can start, stop, or restart them. Also, if HA is configured, you can switch the Active-Standby servers via Switch-over.
To control the operation of EPAS (DBaaS), follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. Navigate to the EPAS(DBaaS) List page.
- Click the resource to control operation on the EPAS(DBaaS) List page. It moves to the EPAS(DBaaS) Detail page.
- Check the EPAS (DBaaS) status and complete the change using the control button below.
- Start: The server where the DB service is installed and the DB service is running.
- Stop: The server where the DB service is installed and the DB service 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 EPAS (DBaaS).
To check the service status of EPAS (DBaaS), follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- Click the resource to view the service status on the EPAS(DBaaS) List page. It will navigate to the EPAS(DBaaS) Details page.
- Service Status Synchronization Click the button. While it is being queried, the cluster will change 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 the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. Go to the EPAS(DBaaS) List page.
- Click the resource to change the server type on the EPAS (DBaaS) List page. It will navigate to the EPAS (DBaaS) Details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Edit Server Type popup window will open.
- Server Type Edit In the popup window, after selecting the server type, click the Confirm button.
Add storage
If more than 5 TB of data storage space is required, additional storage can be added. In the case of a redundant DB configuration, both redundant servers are added simultaneously.
To add storage, follow these steps.
- It is applied the same way as the Storage type selected when creating the service.
- In the case of a redundant DB, adding storage will be applied simultaneously to the storage of the Active DB and the Standby DB.
- If a Replica exists, the Master cluster’s storage cannot be larger than the Replica’s storage. Expand the Replica storage first, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
- All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- EPAS(DBaaS) List Click the resource to add storage on the page. EPAS(DBaaS) Details Navigate to the page.
- Click the Add Disk button at the bottom of the detailed information. The Request Additional Storage popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.
Expanding Storage
You can expand the storage added to the data area up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
- All Services > Database > EPAS(DBaaS) Click the menu. Navigate to the Service Home page of EPAS(DBaaS).
- Service Home page, click the EPAS(DBaaS) menu. Navigate to the EPAS(DBaaS) List page.
- EPAS(DBaaS) 목록 Click the resource to change the server type on the page. EPAS(DBaaS) 상세 Navigate to the page.
- Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. The Edit Additional Storage popup window opens.
- Add Storage Modification After entering the expansion capacity in the popup window, click the Confirm button.
EPAS(DBaaS) Cancel
You can cancel unused EPAS (DBaaS) to reduce operating costs. However, if you cancel the service, the service currently in operation may be stopped immediately, so you should proceed with the cancellation after fully considering the impact that may occur when the service is discontinued.
- In the case of a DB with a Replica configured, even if you terminate the Master DB, the Replica is not deleted together. If you also want to delete the Replica, please terminate it separately from the resource list.
- If you cancel the DB, stored data and, if backup is set, backup data will also be deleted.
To cancel EPAS (DBaaS), follow the steps below.
- Click the All Services > Database > EPAS(DBaaS) menu. Go to the Service Home page of EPAS(DBaaS).
- Click the EPAS(DBaaS) menu on the Service Home page. You will be taken to the EPAS(DBaaS) List page.
- EPAS(DBaaS) list on the page, select the resource to cancel, and click the Cancel Service button.
- Once the termination is complete, check whether the resource has been terminated on the EPAS(DBaaS) list page.
1.2.1 - EPAS(DBaaS) server connection
Scenario Overview
The EPAS(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and Database service are created to access the DB service through the Bastion host. To securely access EPAS(DBaaS) in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.
This scenario largely describes the process of creating a Bastion host and Database service, configuring the network environment for Bastion host and Database connection, and accessing it through a DB connection client.
Scenario Components
You can configure 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 allows users to subdivide the network into smaller segments for specific purposes/sizes within the VPC | |
| Networking | VPC > Public IP | A service that reserves public IP and assigns and returns it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the internet | |
| Networking | Security Group | A virtual firewall that controls the server’s traffic | |
| Database | EPAS(DBaaS) | A service that easily creates and manages EPAS in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to access Virtual Server | |
| Table. List of scenario components |
Scenario composition method
To configure the scenario, create the necessary services through the following procedure.
1. Configuring the Network
This describes the process of configuring the network environment for Bastion Host and Database service connection.
1-1. Creating a VPC
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
- VPC Creation page, please enter the information required for service creation.
- IP range should be entered as
192.168.x.0/16.
- IP range should be entered as
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- After creation is complete, check the created resource on the VPC list page.
1-2. Creating a Subnet
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Subnet menu. It moves to the Subnet list page.
- Click the Subnet Creation button. It moves to the Subnet Creation page.
- Subnet creation page where you enter the information needed to create a service.
- Subnet type should be selected as General.
- Please select a pre-created VPC.
- IP range should be entered as
192.168.x.0/24.
- In the Summary panel, review the detailed information and estimated charge, then click the Complete button.
- After creation is complete, check the created resource in the Subnet list page.
1-3. Creating an Internet Gateway
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Internet Gateway menu. Move to the Internet Gateway list page.
- Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
- Internet Gateway creation page, please enter the required information necessary for service creation.
- Please select a pre-created VPC.
- Select use in the Firewall usage item.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- After creation is complete, check the created resource on the Internet Gateway list page.
1-4. Creating a Public IP
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Public IP menu. It moves to the Public IP list page.
- Public IP Reservation button, click. Move to the Public IP Reservation page.
- Public IP Reservation page, enter the required information necessary for service reservation.
- Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
- Once creation is complete, check the created resource on the Public IP List page.
1-5. Creating a Security Group
- Click on the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
- Click the Security Group Creation button on the Service Home page. It moves to the Security Group Creation page.
- Security Group creation page where you enter the required information necessary for service creation.
- Check the input information and click the Complete button.
- Once creation is complete, check the created resource on the Security Group list page
2. Creating a Bastion Host
This explains the process of configuring the Bastion Host where the database connection client should be installed.
2-1. Creating a Server Keypair
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Click the Keypair menu on the Service Home page. It moves to the Keypair list page.
- Create Keypair button should be clicked. It moves to the Create Keypair page.
- Keypair creation page, please enter the required information necessary for service creation.
- Check the creation information and click the Complete button.
- The key can only be downloaded for the first time, and re-issuance is not provided.
- Please keep the downloaded key in a safe place.
2-2. Creating a Bastion Host
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Click the Virtual Server Creation button on the Service Home page. It moves to the Virtual Server Creation page.
- Virtual Server Creation page, please enter the required information necessary for service creation.
- The image is Windows, please select.
- Please select the pre-created VPC and Subnet.
- Click NAT Use and select the Public IP reserved in 1-4. Creating Public IP.
- 2-1. Creating a server Keypair Connect the Keypair created from
- Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
- After creation is complete, check the created resource on the Virtual Server list page.
2-3. Check Bastion host connection ID and PW
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
- Virtual Serve list page, click on the resource created in 2-2. Bastion host creation. It moves to the detailed information page of the corresponding resource.
- Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window will open.
- RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Creating a server keypair.
- After attaching, click the Password Check button. The ID and password required to access the resource will be displayed.
- The ID and Password will be used as information to connect to the Bastion host later, as described in 5-1. Connect to Bastion host.
3. Creating a Database
Describes the process of creating a Database service.
3-1. Creating EPAS(DBaaS) Service
- Click on the menu for all services > Database > EPAS(DBaaS). It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) creation button. It moves to the EPAS(DBaaS) creation page.
- EPAS(DBaaS) creation page, please enter the required information necessary for service creation.
- Select and connect the pre-created VPC and Subnet.
- Enter Database related creation information on the required information input screen.
- Add the Bastion host IP to the IP access control items.
- Database Port is 2866 by default, but you can specify it as you want.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- Once the creation is complete, check the created resource on the EPAS(DBaaS) list page.
4. Setting Rules
This describes the process of setting rules for users to access the Bastion host and rules for the Bastion host to access the Database.
4-1. Adding Security Group Security Rules
- Click All services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
- Service Home page, click the Security Group menu. It moves to the Security Group list page.
- 1-5. Creating a Security Group Select the Security Group resource created from. It will move to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule popup window, enter the rules below, and click the OK button
| Direction | Remote | Destination Address | Protocol | Port | Description |
|---|---|---|---|---|---|
| Inbound | CIDR | User PC IP | TCP | 3389 (RDP) | Bastion access PC → Bastion host |
| Outbound | CIDR | DB IP | TCP | Database Port (direct input) | Bastion host → Database |
4-2. Adding IGW Firewall Rules
- Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
- Service Home page, click the Firewall menu. It moves to the Firewall list page.
- Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway, and move to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule popup window, enter the rules below, and click the OK button.
| Departure Address | Destination Address | Protocol | Port | Action | Direction | Description |
|---|---|---|---|---|---|---|
| Bastion connection PC IP | Bastion host IP | TCP | 3389(RDP) | Allow | Inbound | User PC → Bastion host |
| Fig. Internet Gateway Firewall rules to be added |
5. Connect to Database
This explains the process of a user accessing the Database through a DB connection client program.
This guide provides instructions on how to connect using pgAdmin. There are various database client programs and CLI utilities, so you can install and use the tools that suit you.
5-1. Connecting to the Bastion host
- Run Remote Desktop Connection in the Windows environment of the PC you want to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
- After a successful remote desktop connection, the user credential input window opens. Enter the ID and Password confirmed in 2-3. Checking Bastion host access ID and PW and click the Confirm button.
5-2. Installing DB connection client program (pgAdmin) on the Bastion host
- Go to the official pgAdmin page and download the pgAdmin program.
- pgAdmin program download path: https://www.pgadmin.org/download/
- Connect the hard drive of the user PC to upload the file to the Bastion host.
- Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
- Select the local disk where the file was downloaded to the drive and click the Confirm button.
- Copy the downloaded file and upload it to the Bastion Host, then click the pgAdmin installation file to install it.
5-3. Using DB connection client program (pgAdmin) to connect to the database
- Run pgAdmin and click the Add New Server button.
- In the Register - Server popup window, enter the Database server information created in 3-1. Creating EPAS(DBaaS) service in the General tab and Connection tab, and click the Save button.
Screen (Tab) Required Input Element Items 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 DB Connection Client Program Input Items - Click the database name created on pgAdmin to connect.
- You can try simple queries after connecting.
1.2.2 - Managing DB Service
The user can manage EPAS(DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
It provides a function to easily query and modify database configuration parameters.
Parameter Inquiry
To view the configuration parameters, follow these steps.
- Click All Services > Database > EPAS(DBaaS) menu. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- EPAS(DBaaS) List page, click the resource you want to query and modify parameters. It moves to the EPAS(DBaaS) Details page.
- Click the More button and click the Parameter Management button. The Parameter Management popup window opens.
- In the Parameter Management popup window, click the Inquiry button. The Inquiry Notification popup window opens.
- When the query notification pop-up window opens, click the OK button. It may take a little time to query.
Modifying Parameters
To modify the configuration parameters, follow these steps.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- On the EPAS(DBaaS) list page, click the resource you want to query and modify parameters. It moves to the EPAS(DBaaS) detail page.
- Click the More button and click the Parameter Management button. The Parameter Management popup window opens.
- In the Parameter Management popup window, click the Search button. The Search Notification popup window opens.
- When the query notification popup window opens, click the OK button. It may take some time to query.
- If modification is needed, click the Modify button and enter the modification details in the customized value area of the parameter to be modified.
- When the input is complete, click the Save button.
Manage DB users
It provides management functions that can query DB user information and change status information.
Querying DB Users
To query DB users, follow the following procedure.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- Click on the resource you want to query the DB user on the EPAS(DBaaS) list page. It moves to the EPAS(DBaaS) details page.
- Click the More button and click the DB User Management button. It moves to the DB User Management page.
- On the DB User Management page, click the Search button. It may take some time to retrieve the results.
Change DB User Status
To change the status of the retrieved DB user, follow the next procedure.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- On the EPAS(DBaaS) list page, click the resource you want to modify the DB user. It moves to the EPAS(DBaaS) detail page.
- Click the More button and click the DB User Management button. It moves to the DB User Management page.
- On the DB User Management page, click the Search button. It may take some time to retrieve the results.
- If modification is needed, click the Modify button and enter the status area value change or note contents.
- When the input is complete, click the Save button.
DB Access Control Management
It provides IP-based DB user access control management function. Users can directly specify the IP that can access the database, so that only allowed IPs can access.
Checking DB Access Control
To view DB users with IP access control set, follow the next procedure.
- All services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- On the EPAS(DBaaS) list page, click the resource for which you want to manage access control. It moves to the EPAS(DBaaS) details page.
- Click the More button and click the DB Access Control Management button. It moves to the DB Access Control Management page.
- DB Access Control Management page, click the Search button. It takes a little time to search.
Add DB Access Control
To add IP access control, follow the next procedure.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- On the EPAS(DBaaS) list page, click the resource for which you want to add IP access control. It moves to the EPAS(DBaaS) details page.
- Click the More button and click the DB Access Control Management button. It moves to the DB Access Control Management page.
- DB Access Control Management page, click the Search button. It takes a little time to search.
- When the inquiry is complete, click the Add button. The Add DB Access Control popup window will open.
- Add DB Access Control popup window, select DB username and enter IP Address.
- When the input is complete, click the Save button.
Delete DB Access Control
To delete IP access control, follow these steps.
- All services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- On the EPAS(DBaaS) list page, click the resource for which you want to delete IP access control. It moves to the EPAS(DBaaS) details page.
- Click the More button and click the DB Access Control Management button. It moves to the DB Access Control Management page.
- DB Access Control Management page, click the Inquiry button. It takes a little time to inquire.
- When the inquiry is complete, click the Delete button. The Delete popup window will open.
- Delete popup window, click the OK button.
Managing Archives
It provides archive mode setting and archive log storage period setting functions, allowing users to flexibly set archive log management policies according to their operating environment. Additionally, it provides a function to manually delete Archive logs, allowing you to clean up unnecessary log data and effectively manage system resources.
Setting Archive Mode
To set the archive mode, follow the next procedure.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- On the EPAS(DBaaS) list page, click the resource for which you want to set the Archive mode. It moves to the EPAS(DBaaS) detail page.
- Click the More button and click the Archive Settings Management button. It moves to the Archive Settings Management page.
- Archive settings management page, click the Inquiry button. It takes a little time to inquire.
- Click the Modify button and select whether to use it and the storage period.
- When the modification is complete, click the Save button.
Delete Archive Files
To delete an Archive file, follow these steps.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- On the EPAS(DBaaS) list page, click the resource for which you want to set the Archive mode. It moves to the EPAS(DBaaS) details page.
- Click the More button and click the Archive Settings Management button. It moves to the Archive Settings Management page.
- Archive settings management page, if you want to delete all Archive files, click the Delete all Archives, if you want to delete only the backed up Archive files, click the Delete backed up Archives button.
DB Log export
It supports exporting log data that requires long-term storage in the 감사(Audit) log to Object Storage. Users can directly set the type of log to be stored, the destination bucket to be exported, and the cycle of exporting logs. It copies and stores logs to the specified Object Storage according to the set criteria. Additionally, to efficiently manage disk space, it provides an option to automatically delete the original log files while exporting logs to Object Storage at the same time. By utilizing this option, you can effectively secure the storage capacity while safely storing the necessary log data for a long time.
- To use the DB Log export function, Object Storage creation is required. Please refer to the Object Storage user guide for Object Storage creation.
- Please make sure to check the expiration date of the authentication key. If the authentication key expires, logs will not be stored in the Bucket.
- Please be careful not to expose the authentication key information to the outside.
Set DB Log Export Mode
To set the DB log export mode, follow the following procedure.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- EPAS(DBaaS) list page, click on the resource you want to export DB Log. It moves to the EPAS(DBaaS) details page.
- Click the More button and click the Export DB Log button. It moves to the Export DB Log page.
- On the DB Log Export page, click the Register button. It moves to the DB Log Export Registration page.
- On the DB Log Export Registration page, enter the corresponding information and click the Save button.
| Classification | Essential | Detailed Description |
|---|---|---|
| Log Type | Required | Type of log to be stored |
| Storage bucket name | Required | Name of the Object Storage bucket to store |
| Authentication key > Access key | Required | Access key to access the Object Storage to be stored |
| Authentication key > Secret key | Required | Secret key for accessing the Object Storage to be stored |
| File Creation Cycle | Required | Cycle of creating files in Object Storage |
| Whether to delete the original log | Select | Whether to delete the original log when exporting to Object Storage |
Managing DB Log Export
To modify, cancel, or immediately export the DB log export settings, follow these steps.
- Click All Services > Database > EPAS(DBaaS) menu. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- On the EPAS(DBaaS) list page, click the resource you want to manage DB log export. It moves to the EPAS(DBaaS) detail page.
- Click the More button and click the Export DB Log button. It moves to the Export DB Log page.
- On the DB Log Export page, click the More button according to the type of log you want to manage, and then click the Export Now, Modify, or Cancel button.
- Immediate Export: The selected log is exported to the existing Object Storage’s Bucket.
- Modify: Modifies the DB log export mode setting.
- Cancel: Cancels the DB log export mode setting.
Minor Version Upgrade
It provides a version upgrade feature due to some functional improvements and security patches. Only minor version upgrade is supported within the same major version.
- Please perform the version upgrade after checking the service status through service status synchronization.
- Please proceed with the version upgrade after setting up the backup. If you do not set up the backup, you may not be able to recover some data when a problem occurs during the upgrade.
- In the DB where Replica is configured, the Master DB version cannot be higher than the Replica version. Please check the Replica version first and perform a version upgrade if necessary.
- The backed-up data will be automatically deleted after the version upgrade is completed.
To perform a Minor Version upgrade, follow the procedure below.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- Click on the resource to be upgraded on the EPAS(DBaaS) list page. It moves to the EPAS(DBaaS) details page.
- Click the Edit button in the Image/Version item. The Version Upgrade popup window opens.
- In the 버전 업그레이드 popup window, select the modified version and whether to back up the settings, then click the 확인 button.
- In the Version Upgrade Notification popup window, click the OK button.
Configuring Migration
It provides a migration function that synchronizes with the operating database in real-time and replicates in a replication manner without interrupting the service.
To configure the migration, follow the next procedure.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- Click on the resource to be migrated on the EPAS(DBaaS) list page. It moves to the EPAS(DBaaS) details page.
- Click the More button and click the Migration Settings button. The Migration Settings popup window opens.
- Check the instructions in the Migration Configuration popup window and click the OK button. It moves to the Migration Configuration page.
- On the Migration Configuration page, enter the information and click the Check Connection button.
- Once the connection is complete, click the Complete button.
| Classification | Essential | Detailed Description |
|---|---|---|
| Source DB Database name | required | The name of the Source DB database that is the target of migration |
| Source DB IP | Required | IP of the Source DB that is the target of Migration |
| Source DB Port | Required | Port of the Source DB that is the target of Migration |
| Source DB username | required | Username of the Source DB that is the target of migration |
| Source DB password | required | Password of the Source DB that is the target of migration |
Migrating Cluster to Master Cluster
You can promote a fully configured Migration Cluster to a Master Cluster.
To promote the Migration Cluster to Master, follow these steps.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- On the EPAS(DBaaS) list page, click the resource to be promoted to Master. It moves to the EPAS(DBaaS) detail page.
- Click the More button and click the Master Promotion button. The Master Promotion Notification popup window opens.
- In the Master Promotion Alert popup window, click the Confirm button.
1.2.3 - DB Backup and Recovery
The user can set up the backup of EPAS(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.
EPAS(DBaaS) Backup
To ensure that the user’s data is safely stored, EPAS(DBaaS) provides a data backup function based on its own backup command, and also provides a backup history function to check if the backup was done normally, and can also delete the backed-up files.
Setting up backup
The method of setting up a backup for EPAS(DBaaS) is described in EPAS(DBaaS) creation guide.
To modify the backup settings of the generated resource, follow these steps.
- For stable backup, it is recommended to add a separate BACKUP storage or sufficiently increase the storage capacity. Especially when the backup target data exceeds 100 GB and there are many data changes, please secure additional storage equivalent to about 60% of the data capacity. For storage addition and expansion methods, refer to the EPAS(DBaaS) Add Storage, EPAS(DBaaS) Expand Storage guides. If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
- If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.
To set up a backup, follow these steps.
- All Services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- EPAS(DBaaS) list page, click the resource to set the backup. Move to the EPAS(DBaaS) details page.
- Click the Edit button of the backup item. The Backup Settings popup window opens.
- If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the OK button.
- If you want to stop the backup settings, uncheck Backup Settings in the popup window and click the OK button.
Check Backup History
To view the backup history, follow these steps.
- All services > Database > EPAS(DBaaS) menu is clicked. It moves to the Service Home page of EPAS(DBaaS).
- Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- EPAS(DBaaS) list page, click the resource to check the backup history. It moves to the EPAS(DBaaS) detail page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.
Deleting Backup Files
To delete the backup history, follow these steps.
- Click All Services > Database > EPAS(DBaaS) menu. It moves to the Service Home page of EPAS(DBaaS).
- Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- EPAS(DBaaS) list page, click the resource to check the backup history. It moves to the EPAS(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window, check the file you want to delete, and then click the Delete button.
EPAS(DBaaS) Recovery
In the event of a failure or data loss that requires restoration from a backup file, recovery is possible based on a specific point in time through the recovery function. When performing EPAS (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, and the DB is installed with the version at the backup point, and the recovery proceeds with the DB configuration information and data.
To recover EPAS(DBaaS), follow these procedures.
- Click All Services > Database > EPAS(DBaaS) menu. It moves to the Service Home page of EPAS(DBaaS).
- Service Home page, click the EPAS(DBaaS) menu. It moves to the EPAS(DBaaS) list page.
- EPAS(DBaaS) Resource list page, click the resource you want to restore. It moves to the EPAS(DBaaS) detail page.
- Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
- Database Recovery Configuration area, enter the corresponding information, and then click the Complete button.
| Classification | Necessity | Detailed Description |
|---|---|---|
| Recovery Type | Required | Set the point in time to recover
|
| Server name prefix | Required | Recovery DB server name
|
| Cluster Name | Required | Recovery DB Cluster Name
|
| Service Type > Server Type | Required | Recovery DB Server Type
|
| Service Type > Planned Compute | Select | Current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Block Storage settings used by the recovery DB
|
| Database username | required | Database username
|
| Database Port Number | required | Database Port Number
|
| IP Access Control | Select | Set Service Access Policy
|
| Maintenance period | Select | DB maintenance period
|
| Tag | Select | Add Tag
|
1.2.4 - Configuring Read Replica
Users can create a Read Replica by entering the required information through the Samsung Cloud Platform Console and configuring detailed options.
Configuring Replica
Replica configuration allows you to create a read-only replica server. You can create up to 5 replicas per database.
To configure a replica, follow these steps:
- All Services > Database > EPAS(DBaaS) menu, click. Move to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. Move to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource you want to configure the replica for. Move to the EPAS(DBaaS) Details page.
- Click the Configure Replica button. Move to the Configure Replica page.
- Enter the information in the Configure Replica section and click the Complete button.
| Category | Required | Detailed Description |
|---|---|---|
| Number of Replicas | Required | The number of replicas to configure
|
| Replica Name | Required | The name of the replica server
|
| Service Type > Server Type | Required | The type of replica server
|
| Service Type > Planned Compute | Optional | The current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Block storage settings for the replica DB
|
| IP Access Control | Optional | Service access policy setting
|
| Maintenance Period | Optional | DB maintenance period
|
Reconfiguring Replica
If a network failure or replication delay occurs between the master cluster, you can reconfigure the replica to re-replicate the master cluster’s data.
To reconfigure a replica, follow these steps:
- All Services > Database > EPAS(DBaaS) menu, click. Move to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. Move to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource you want to reconfigure the replica for. Move to the EPAS(DBaaS) Details page.
- Click the Reconfigure Replica button. The Reconfigure Replica Notification popup window opens.
- In the Reconfigure Replica Notification popup window, click the Confirm button.
Promoting Replica Cluster to Master
You can promote a configured replica cluster to a master cluster.
To promote a replica cluster to a master, follow these steps:
- All Services > Database > EPAS(DBaaS) menu, click. Move to the Service Home page of EPAS(DBaaS).
- On the Service Home page, click the EPAS(DBaaS) menu. Move to the EPAS(DBaaS) List page.
- On the EPAS(DBaaS) List page, click the resource you want to promote to a master. Move to the EPAS(DBaaS) Details page.
- Click the More button and then click the Promote to Master button. The Promote to Master Notification popup window opens.
- In the Promote to Master Notification popup window, click the Confirm button.
1.2.5 - Extension use
EPAS(DBaaS) Extension usage
The list of Extensions that can be installed in the current database can be checked with the following SQL sentence.
SQL> select * from pg_available_extensions;
In EPAS(DBaaS), the items that are installed additionally, excluding the default Extensions included in each version, are as follows.
| Extension Name | Description |
|---|---|
| pg_cron | a scheduler that allows job scheduling with cron syntax within the database |
| pgvector | Vector data type and similarity search, etc. AI vector operation function provided |
| postgis | GIS (Geographic Information System) provides spatial object storage and spatial query functionality |
In addition to the above items, if additional Extension installation is required, please refer to Support Center > Inquiry for inquiries.
- Once your inquiry is received, we will review and proceed with the installation. Please note that some Extensions may not work properly during Replica configuration and recovery.
1.3 - API Reference
1.4 - CLI Reference
1.5 - Release Note
EPAS(DBaaS)
- EPAS(DBaaS) feature added
- 2nd generation server type added
- Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see EPAS(DBaaS) server type
- DB user and access control management and Archive setting function added
- For more information, see DB User Management, DB Access Control Management, Archive Management
- DB Audit Log Export feature added
- For more information, see DB Log Export
- Backup Notification Feature provided
- Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
- Migration feature added
- Provides replication-based zero-downtime data migration feature. For more information, see Migration 구성하기
- Block Storage type added HDD, HDD_KMS type
- EPAS(DBaaS) service that can easily create and manage EPAS in a web environment has been released.
2 - PostgreSQL(DBaaS)
2.1 - Overview
Service Overview
PostgreSQL (DBaaS) is an open source relational database management system (RDBMS). Samsung Cloud Platform provides an environment that can automate PostgreSQL installation through a web-based console and perform 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 content of the Active server changes, it is synchronously replicated to the Standby server, and up to five read‑only servers called Replicas are provided for read‑load balancing and disaster recovery (DR). Additionally, to prepare for issues with the DB server or data, it offers an automatic backup function at user‑specified times, enabling data recovery to a desired point in time.
Provided Features
PostgreSQL (DBaaS) provides the following features.
- Auto Provisioning (Auto Provisioning): It is possible to install and configure the Database (DB) via UI, and it provides an Active-standby redundancy configuration built on storage replication. In case of an Active server failure, 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, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), the user can directly perform node switching between Active-Standby via Switch-over.
- Backup and Recovery: Provides a data backup function based on its own backup commands. The backup time window and storage organization can be set by the user, and additional fees are incurred based on backup size. It also provides a recovery function for backed-up data, so when the user performs a recovery, a separate DB is created and the recovery proceeds to the point in time selected by the user (backup save point, user-specified point). If the user restores to a specified point, the recovery point can be set to 5 minutes, 10 minutes, 30 minutes, or 1 hour before the stored backup file and archive file.
- Version Management: Provides version upgrade (Minor) functionality due to some feature improvements and security patches. Whether to perform a backup for the version upgrade can be selected by the user, and if a backup is performed, data is backed up before applying the patch, then the DB engine is updated.
- Replica configuration: For read load balancing and disaster recovery (DR), up to 5 Read Replicas can be configured in the same/different region.
- Audit Settings: Supports audit (Audit) functionality for major activities within the database.
- Parameter Management: Performance improvement and security-related DB configuration parameters can be modified.
- Service Status Query: Retrieve the final status of the current DB service.
- Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
- DB User Management: Retrieve and manage 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.
- Archive Management: You can set the retention period of Archive files (1 day~35 days) on the DB server and configure the Archive mode (On/Off).
- DB Log Export: You can export stored logs to the user’s Object Storage through Audit settings.
- Migration: Synchronize data in real time with the operating database, and support migration using the Replication method without service interruption.
Components
PostgreSQL (DBaaS) provides pre-validated engine versions and various server types according to the open source support policy. Users can select and use them according to the scale of the service they want 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-06 (scheduled) | 2026-11-12 |
| 14.18 | 2026-06 (scheduled) | 2026-11-12 |
| 15.12 | 2027-06 (scheduled) | 2027-11-11 |
| 15.13 | 2027-06 (scheduled) | 2027-11-11 |
| 16.8 | 2028-06 (scheduled) | 2028-11-09 |
| 16.9 | 2028-06 (scheduled) | 2028-11-09 |
Server Type
The server types supported by PostgreSQL (DBaaS) are as follows.
For detailed information about the server types provided by PostgreSQL(DBaaS), see PostgreSQL(DBaaS) server type.
Standard db1v2m4
Category
Example
Detailed description
Server Type
Standard
Provided Server Types- Standard: Standard specifications (vCPU, Memory) configuration commonly used
- High Capacity: Large-capacity server specifications of 24 vCores or more
Server specifications
db1
Provided server specifications- db1: Standard specifications (vCPU, Memory) configuration commonly used
- dbh2: Large-scale server specifications
- Provides servers with 24 vCores or more
Server specifications
v2
Number of vCores- v2: 2 virtual cores
Server Specifications
m4
Memory Capacity- m4: 4GB Memory
Table. PostgreSQL (DBaaS) server type components
# Preliminary Service
This is a list of services that must be pre-configured before creating the service. For details, please refer to the guide provided for each service and prepare in advance.<br>
Service Category
Service
Detailed Description
Networking
VPC
A service that provides an isolated virtual network in a cloud environment
Table. PostgreSQL(DBaaS) Pre-service
2.1.1 - Server Type
PostgreSQL(DBaaS) server type
PostgreSQL(DBaaS) provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth. When creating PostgreSQL(DBaaS), the Database Engine is installed according to the server type selected for the purpose of use.
The server types supported by PostgreSQL(DBaaS) are as follows.
Standard db1v2m4
Classification | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Provided server type distinction
|
| Server specification | db1 | Provided server type distinction and generation
|
| Server specification | v2 | Number of vCores
|
| Server specification | m4 | Memory capacity
|
| Fig. PostgreSQL(DBaaS) server type format |
db1 server type
The db1 server type of PostgreSQL(DBaaS) is provided with standard specifications(vCPU, Memory) and is suitable for various database workloads.
Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor Supports up to 16 vCPUs and 256 GB of memory Up to 12.5 Gbps of networking speed
| Classification | 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 |
dbh2 server type
The dbh2 server type of PostgreSQL(DBaaS) is provided with large-capacity server specifications and is suitable for database workloads for large-scale data processing.
Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor Supports up to 128 vCPUs and 1,536 GB of memory Up to 25Gbps of networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Up to 25 Gbps |
2.1.2 - Monitoring Metrics
PostgreSQL(DBaaS) Monitoring Metrics
The following table shows the performance monitoring metrics of PostgreSQL(DBaaS) that can be checked through Cloud Monitoring. For detailed instructions on using Cloud Monitoring, refer to the Cloud Monitoring guide.
For server monitoring metrics of PostgreSQL(DBaaS), refer to the Virtual Server Monitoring Metrics guide.
| Performance Item | 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 Active Sessions | cnt |
| Active Sessions [Total] | Total Number of Active Sessions | 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 Idle In Transaction Sessions | cnt |
| Idle In Transaction Sessions [Total] | Total Number of Idle In Transaction Sessions | cnt |
| Idle Sessions | Number of Idle Sessions | cnt |
| Idle Sessions [Total] | Total Number of Idle Sessions | cnt |
| Row Exclusive Locks | Number of Row Exclusive Locks | cnt |
| Row Share Locks | Number of Row Share Locks | 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 Long-Running SQL Queries (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] | Longest Running Transaction Time (minutes) | min |
| Transaction Time Max Total [Long] | Longest Running Transaction Time (minutes) | min |
| Wait Locks | Number of Sessions Waiting for Locks (per DB) | cnt |
| Wait Locks [Long Total] | Number of Sessions Waiting for Locks for a Long Time (over 300 seconds) | cnt |
| Wait Locks [Long] | Number of Sessions Waiting for Locks | cnt |
| Wait Locks [Total] | Total Number of Sessions Waiting for Locks | cnt |
| Waiting Sessions | Number of Waiting Sessions | cnt |
| Waiting Sessions [Total] | Total Number of Waiting Sessions | cnt |
2.2 - How-to guides
Users can enter the required information for PostgreSQL (DBaaS) through the Samsung Cloud Platform Console, select detailed options, and create the service.
Creating PostgreSQL(DBaaS)
You can create and use PostgreSQL (DBaaS) services from the Samsung Cloud Platform Console.
- Please configure the VPC’s Subnet type as General before creating the service.
- If the Subnet type is Local, the creation of the corresponding Database service is not possible.
- If you load more than 2 TB of large data, backup may take a long time or the DB performance itself may degrade. To prevent this, you need to consider operational aspects such as cleaning up unnecessary data or moving old data to a statistical collection environment.
To create PostgreSQL (DBaaS), follow the steps below.
All Services > Database > PostgreSQL(DBaaS) Click the menu. Go to the Service Home page of PostgreSQL(DBaaS).
Click the PostgreSQL(DBaaS) Create button on the Service Home page. Navigate to the PostgreSQL(DBaaS) Create page.
PostgreSQL(DBaaS) Creation on the page, enter the information required to create the service, and select detailed options.
- Image and version selection Select the required information in the area.
Category Required or notDetailed description Image version Required Provide version list of PostgreSQL (DBaaS) Table. PostgreSQL (DBaaS) image and version selection items - Service Information Input Enter or select the required information in the area.
Category Required or notDetailed description Server Name Prefix Required Server name where DB will be installed - Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (
-) to input 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is attached to create the actual server name
Cluster Name Required Cluster name of DB servers - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type where DB will be installed - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server of 24 vCore or more
- For detailed information about server types provided by PostgreSQL (DBaaS), refer to PostgreSQL(DBaaS) Server Type
Service Type > Planned Compute Select Status of resources with Planned Compute set - In Use: Number of resources with Planned Compute set that are currently in use
- Configured: Number of resources with Planned Compute set
- 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 Apply for Planned Compute
Service Type > Block Storage Required Set Block Storage used by DB according to purpose - Base OS: Area where DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- After selecting storage type, enter capacity (refer to Create Block Storage for details of each Block Storage type)
- SSD: High-performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes using Samsung Cloud Platform KMS (Key Management System) encryption keys
- The configured storage type is applied identically to additional storage
- Capacity must be entered as a multiple of 8 within the range 16 ~ 5,120
- Because large sorts from SQL execution or monthly batch may cause service interruption, 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 the same as set for DATA, and capacity can be entered as a multiple of 8 within 16 ~ 5,120
- Click the + button to add storage, x button to delete. Up to 9 can be added
- Backup data is temporarily stored in BACKUP storage before transmission
- If backup data exceeds 100 GB and changes frequently, it is recommended to add a separate BACKUP storage for reliable backup; set backup capacity to about 60% of DATA capacity
- If BACKUP storage is not added, using the
/tmparea is recommended
- For each service, Archive, TEMP, BACKUP storages are allocated only one Block Storage
- After selecting storage type, enter capacity (refer to Create Block Storage for details of each Block Storage type)
Redundancy Configuration Select Redundancy Configuration Status - If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
Network > Common Settings Required Network settings where servers generated by the service are installed - Select if you want to apply the same settings to all servers being installed
- Select a pre-created VPC, Subnet, IP, Public NAT
- IP can only be auto-generated
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway; if you check Use, you can select from reserved IPs in the VPC product’s Public IP. For details, see Create Public IP
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select if 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 from reserved IPs in the VPC product’s Public IP. For more details, see Create Public IP.
IP Access Control Select Service Access Policy Settings - Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required.
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
Maintenance Period Select DB Maintenance Period - If Use is selected, set the day of the week, start time, and duration.
- It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption.
- If set to not use, Samsung SDS is not responsible for issues arising from patches not being applied.
Table. PostgreSQL(DBaaS) Service Information Input Items - Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (
- Database Configuration Required Information Input In the area, please enter or select the required information.
Category Required or notDetailed description Database name Required Server name applied when installing DB - Start with English letters, use English letters and numbers, input 3 ~ 20 characters
Database username Required DB user name - An account with that name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Restricted Database usernames can be checked in the Console
Database Password Required Password to use when accessing the DB - Enter 8~30 characters including letters, numbers, and special characters (excluding “ and ‘)
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 DB port within the range 1,024 ~ 65,535
Backup > Use Select Whether to use backup - Use to set backup file retention period, backup start time, Archive backup cycle
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 are charged separately based on size
Backup > Backup Start Period Select Backup Start Time - Select backup start time
- The minutes at which the backup runs are set randomly, and the backup end time cannot be set
Backup > Archive Backup Frequency Select Archive Backup Frequency - Select the Archive Backup Frequency
- Archive Backup Frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance.
Audit Log Settings Select Whether to store Audit Log - 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
- Refer to the PostgreSQL documentation for details on this parameter
- Users can specify the type of SQL statements to audit via the
- Enabling Audit may degrade DB performance
- DDL, DML, and user connection information records are stored
Parameter Required Parameters to use in the DB - Click the Search button to view detailed information of the parameters
- Parameters can be modified after 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 to use for DB - Settings related to string processing, number/currency/date/time display formats, etc.
- The DB is created with default settings using the selected Locale
Time zone Required Standard time zone to be used by the Database Table. PostgreSQL(DBaaS) Database configuration items - Additional Information Input Enter or select the required information in the area.
Category Required or notDetailed description Tag Select Add Tag - Up to 50 can be added per resource
- After clicking the Add Tag button, enter or select Key, Value values
Table. PostgreSQL(DBaaS) Additional Information Input Items
- Image and version selection Select the required information in the area.
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 resource on the Resource List page.
PostgreSQL(DBaaS) Check detailed information
PostgreSQL(DBaaS) service can view and edit the full resource list and detailed information. PostgreSQL(DBaaS) Details page consists of Details, Tags, Activity History tabs, and for databases with a Replica configured, a Replica Information tab is additionally provided.
To view detailed information of the PostgreSQL (DBaaS) service, follow the steps below.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. Move to the PostgreSQL(DBaaS) List page.
- Click the resource to view detailed information on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details 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 changing to operation execution state
- Error: Cluster encountered an error while performing tasks
- If it occurs continuously, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Cluster is being restarted
- Running: Cluster is operating normally
- Starting: Cluster is being started
- Stopped: Cluster is stopped
- Stopping: Cluster is being stopped
- Synchronizing: Cluster is being synchronized
- Terminating: Cluster is being deleted
- Unknown: Cluster status is unknown
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is changing to upgrade execution state
Cluster Control Buttons to change cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to active
More functions Cluster related management buttons - Service status synchronization: View real-time DB service status
- Backup history: If backup is set, check whether backup runs normally and view history
- Database recovery: Recover DB based on a specific point in time
- Parameter management: View and modify DB configuration parameters
- Replica configuration: Configure a read-only cluster Replica; if there is no region to configure for the account, the button is disabled
- Replica configuration (Other Region): Configure a disaster recovery Replica in another region
- DB user management: View and manage DB account (user) information registered in the DB
- DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB
- Archive management: Set archive file retention period and archive mode
- Export DB Log: Export logs stored via audit settings to the user’s Object Storage
- Migration configuration: Provide migration function using replication method
Service cancellation Button to cancel the service Table. PostgreSQL(DBaaS) status information and additional features
Detailed Information
PostgreSQL(DBaaS) List On the page, you can view detailed information of the selected resource and, if necessary, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in the respective 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 |
| Creator | User who created the service |
| Creation time | Service creation time |
| Editor | User who modified the service information |
| Modification DateTime | 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 | Name of the cluster composed of DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied when installing DB |
| Database username | DB user name |
| Planned Compute | Resource status with Planned Compute set
|
| Maintenance Period | DB Patch Work Period Setting Status
|
| Backup | Backup configuration status
|
| Audit Log Settings | Audit Log Settings Status
|
| Time zone | Standard time zone used by the Database |
| DB Locale | Locale to use for DB |
| Database Encoding | Character encoding method to be used in DB |
| VIP | Virtual IP information
|
| Network | Network information where DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP Access Control | Service Access Policy Settings
|
| 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 check 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 created 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
|
Work History
You can view the operation history of the selected resource on the PostgreSQL(DBaaS) List page.
| Category | Detailed description |
|---|---|
| Work 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 work on the PostgreSQL (DBaaS) Details page.
Operating Control
If changes occur to the running PostgreSQL (DBaaS) resources, you can start, stop, or restart them. Also, if 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. 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 Click the resource to control operation on the page. PostgreSQL(DBaaS) Details Navigate to the page.
- Check the PostgreSQL(DBaaS) status and complete the change using the control button below.
- Start: The server where the DB service is installed and the DB service is running.
- 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.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. Go to the Service Home page of PostgreSQL(DBaaS).
- Service Home page, click the PostgreSQL(DBaaS) menu. Navigate to the PostgreSQL(DBaaS) list page.
- PostgreSQL(DBaaS) List Click the resource to view the service status on the page. PostgreSQL(DBaaS) Details Navigate to the page.
- Service status synchronization Click the button. While it is being queried, the cluster changes to Synchronizing state.
- When the query is completed, the status is updated in the server information item, and the cluster changes to Running state.
Change Server Type
You can change the configured server type.
To change the server type, follow the steps below.
- All Services > Database > PostgreSQL(DBaaS) Click the 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) 목록 Click the resource to change the server type on the page. PostgreSQL(DBaaS) 상세 Navigate to the page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Edit Server Type popup window will open.
- Server Type Edit After selecting the server type in the popup window, click the Confirm button.
Add storage
If you need more than 5 TB of data storage space, you can add storage. In the case of a redundant DB configuration, all redundant servers are added simultaneously.
- It is applied the same way as the selected Storage type when creating a service.
- In the case of a DB configured for redundancy, adding storage will be applied simultaneously to the storage of the Active DB and the Standby DB.
- If a Replica exists, the Master cluster’s storage cannot be larger than the Replica’s storage. Expand the Replica storage first, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow the steps below.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate 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 on the page, click the resource to add storage. PostgreSQL(DBaaS) Details navigate to the page.
- At the bottom of the detailed information, click the Add Disk button. The Add Storage Request popup window opens.
- Additional Storage Request After entering purpose and capacity in the popup window, click the Confirm button.
Expanding storage
You can expand the storage added to the data area up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate 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 to change the server type. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the Edit icon of the additional Disk you want to expand at the bottom of the detailed information. Edit Additional Storage popup window opens.
- Add Storage Modification In the popup window, after entering the expansion capacity, click the Confirm button.
PostgreSQL(DBaaS) Cancel
You can cancel unused PostgreSQL (DBaaS) to reduce operating costs. However, if you cancel the service, the running service may be stopped immediately, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.
- In the case of a DB with a Replica configured, even if you terminate the Master DB, the Replica is not deleted together. If you also want to delete the Replica, terminate it separately from the resource list.
- If you terminate the DB, stored data and, if backup is set, all backup data will be deleted.
To cancel PostgreSQL (DBaaS), follow the steps below.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. Navigate to the Service Home page of PostgreSQL(DBaaS).
- Service Home page, click the PostgreSQL(DBaaS) menu. Navigate to the PostgreSQL(DBaaS) list page.
- PostgreSQL(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
- When the termination is complete, check whether the resource has been terminated on the PostgreSQL(DBaaS) list page.
2.2.1 - Managing DB Services
Users can manage PostgreSQL (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
It provides a feature to easily view and modify database configuration parameters.
Viewing Parameters
To view configuration parameters, follow these steps:
- Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
- Click the resource you want to view and modify parameters on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
Modifying Parameters
To modify configuration parameters, follow these steps:
- Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
- Click the resource you want to view and modify parameters on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
- If modification is required, click the Modify button and enter the modification details in the custom value area of the parameter to be modified.
- When the input is complete, click the Save button.
Managing DB Users
It provides a management feature that allows you to view DB user information and change status information.
Viewing DB Users
To view DB users, follow these steps:
- Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
- Click the resource you want to view DB users on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the DB User Management button. It moves to the DB User Management page.
- Click the View button on the DB User Management page. It takes some time to view.
Changing DB User Status
To change the status of the viewed DB user, follow these steps:
- Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
- Click the resource you want to modify DB users on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the DB User Management button. It moves to the DB User Management page.
- Click the View button on the DB User Management page. It takes some time to view.
- If modification is required, click the Modify button and change the status value or enter notes.
- When the input is complete, click the Save button.
Managing DB Access Control
It provides an IP-based DB user access control management feature. Users can directly specify the IP that can access the database, allowing only allowed IPs to access.
Viewing DB Access Control
To view DB users with IP access control set, follow these steps:
- Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
- Click the resource you want to manage access control on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
- Click the View button on the DB Access Control Management page. It takes some time to view.
Adding DB Access Control
To add IP access control, follow these steps:
- Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
- Click the PostgreSQL(DBaaS) menu on the Service Home page. It moves to the PostgreSQL(DBaaS) List page.
- Click the resource you want to add IP access control on the PostgreSQL(DBaaS) List page. It moves to the PostgreSQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
- Click the View button on the DB Access Control Management page. It takes some time to view.
- When the view is complete, click the Add button. The DB Access Control Add popup window opens.
- In the DB Access Control Add popup window, select the DB user name and enter the IP address.
- When the input is complete, click the Save button.
Deleting DB Access Control
To delete IP access control, follow these steps:
- All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- On the PostgreSQL(DBaaS) list page, click the resource for which you want to delete IP access control. It moves to the PostgreSQL(DBaaS) details page.
- Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
- On the DB Access Control Management page, click the Inquire button. It takes some time to inquire.
- Once the inquiry is complete, click the Delete button. The Delete pop-up window opens.
- In the Delete pop-up window, click the Confirm button.
Managing Archive
It provides functions to set Archive mode and Archive log retention period, allowing users to flexibly set Archive log management policies according to their operating environment. Additionally, it provides a function to manually delete Archive logs, allowing users to clean up unnecessary log data and effectively manage system resources.
Setting Archive Mode
To set Archive mode, follow these steps:
- All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- On the PostgreSQL(DBaaS) list page, click the resource for which you want to set Archive mode. It moves to the PostgreSQL(DBaaS) details page.
- Click the More button and then click the Archive Settings Management button. It moves to the Archive Settings Management page.
- On the Archive Settings Management page, click the Inquire button. It takes some time to inquire.
- Click the Modify button and select the usage and retention period.
- Once the modification is complete, click the Save button.
Deleting Archive Files
To delete Archive files, follow these steps:
- All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- On the PostgreSQL(DBaaS) list page, click the resource for which you want to set Archive mode. It moves to the PostgreSQL(DBaaS) details page.
- Click the More button and then click the Archive Settings Management button. It moves to the Archive Settings Management page.
- On the Archive Settings Management page, click the Delete All Archives button to delete all Archive files, or click the Delete Backed-up Archives button to delete only backed-up Archive files.
Exporting DB Logs
It supports exporting audit logs that require long-term storage to Object Storage. Users can directly set the type of log to be stored, the target Bucket, and the frequency of log export. According to the set criteria, it copies the logs to the specified Object Storage for storage. Additionally, to efficiently manage disk space, it provides an option to automatically delete the original log files when exporting logs to Object Storage. By utilizing this option, users can effectively secure storage capacity while safely storing necessary log data for long-term storage.
- To use the DB Log export function, Object Storage creation is required. Refer to the Object Storage User Guide for Object Storage creation.
- Be sure to check the expiration date of the authentication key. If the authentication key expires, logs will not be stored in the Bucket.
- Be cautious not to expose authentication key information to the outside.
Setting DB Log Export Mode
To set DB Log export mode, follow these steps:
- All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- On the PostgreSQL(DBaaS) list page, click the resource for which you want to export DB logs. It moves to the PostgreSQL(DBaaS) details page.
- Click the More button and then click the DB Log Export button. It moves to the DB Log Export page.
- On the DB Log Export page, click the Register button. It moves to the DB Log Export Registration page.
- On the DB Log Export Registration page, enter the corresponding information and click the Save button.
| Category | Required | Detailed Description |
|---|---|---|
| Log Type | Required | Type of log to be stored |
| Storage Bucket Name | Required | Name of the Object Storage Bucket to store |
| Authentication Key > Access Key | Required | Access key to access the Object Storage to store |
| Authentication Key > Secret Key | Required | Secret key to access the Object Storage to store |
| File Creation Cycle | Required | Cycle to create files in Object Storage |
| Original Log Deletion | Optional | Whether to delete the original log when exporting to Object Storage |
Managing DB Log Export
To modify, cancel, or immediately export DB log settings, follow these steps:
- All Services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- On the PostgreSQL(DBaaS) list page, click the resource for which you want to manage DB log export. It moves to the PostgreSQL(DBaaS) details page.
- Click the More button and then click the DB Log Export button. It moves to the DB Log Export page.
- On the DB Log Export page, click the More button for the log type you want to manage, and then click the Immediate Export, Modify, or Cancel button.
- Immediate Export: Exports the selected log to the Object Storage Bucket set earlier.
- Modify: Modifies the DB log export mode setting.
- Cancel: Cancels the DB log export mode setting.
Upgrading DB Version
It provides a version upgrade function due to some feature improvements and security patches. Only minor version upgrades are supported within the same major version.
- Please perform version upgrades after checking the service status through service status synchronization.
- Please set up backups before performing version upgrades. If backups are not set up, some data may not be recoverable in case of problems during updates.
- In DBs with Replicas configured, the Master DB version cannot be higher than the Replica version. Please check the Replica version first and perform version upgrades if necessary.
- Backed-up data will be automatically deleted after version upgrade completion.
To upgrade the version, follow these steps:
- Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- On the PostgreSQL(DBaaS) list page, click the resource to upgrade the version. It moves to the PostgreSQL(DBaaS) details page.
- Click the Modify button in the image/version item. The Version Upgrade popup window opens.
- In the Version Upgrade popup window, select the version to modify and whether to set backup, and then click the Confirm button.
- In the Version Upgrade Notification popup window, click the Confirm button.
Configuring Migration
It provides a migration function that synchronizes with the operating database in real-time and replicates in a replication manner without interrupting the service.
To configure migration, follow these steps:
- Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- On the PostgreSQL(DBaaS) list page, click the resource to migrate. It moves to the PostgreSQL(DBaaS) details page.
- Click the More button and then click the Configure Migration button. The Configure Migration popup window opens.
- In the Configure Migration popup window, check the instructions and click the Confirm button. It moves to the Configure Migration page.
- On the Configure Migration page, enter the corresponding information and click the Connect Check button.
- When the connection is complete, click the Complete button.
| Classification | Required | Detailed Description |
|---|---|---|
| Source DB Database Name | Required | Database name of the source DB that is the migration target |
| Source DB IP | Required | IP of the source DB that is the migration target |
| Source DB Port | Required | Port of the source DB that is the migration target |
| Source DB User Name | Required | User name of the source DB that is the migration target |
| Source DB Password | Required | Password of the source DB that is the migration target |
The configured migration cluster can be promoted to a master cluster.
To promote the migration cluster to master, follow these steps:
- Click the All Services > Database > PostgreSQL(DBaaS) menu. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- On the PostgreSQL(DBaaS) list page, click the resource to promote to master. It moves to the PostgreSQL(DBaaS) details page.
- Click the More button and then click the Promote to Master button. The Promote to Master Notification popup window opens.
- In the Promote to Master Notification popup window, click the Confirm button.
2.2.2 - DB Backup and Recovery
The user can set up a backup of PostgreSQL(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.
PostgreSQL(DBaaS) backup
PostgreSQL(DBaaS) provides a data backup feature based on its own backup command, and also provides an optimized backup environment for data protection and management through backup history checking and backup file deletion functions.
Setting up backup
The method of setting up a backup of PostgreSQL(DBaaS) is described in PostgreSQL(DBaaS) creation guide.
To modify the backup settings of the generated resource, follow these steps.
- For stable backup, it is recommended to add a separate BACKUP storage or to sufficiently expand the storage capacity. Especially when the backup target data exceeds 100 GB and there are many data changes, please secure additional storage equivalent to about 60% of the data capacity. For storage addition and expansion methods, refer to the PostgreSQL(DBaaS) Add Storage, PostgreSQL(DBaaS) Expand Storage guides.
- If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
- If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.
To set up a backup, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) menu is clicked. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- PostgreSQL(DBaaS) list page, click the resource to set the backup. It moves to the PostgreSQL(DBaaS) details page.
- Click the Edit button of the backup item. The Backup Settings popup window will open.
- If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the Confirm button.
- If you want to stop the backup setting, uncheck Use in the Backup Setting popup window and click the OK button.
Check Backup History
To view the backup history, follow these steps.
- 모든 서비스 > Database > PostgreSQL(DBaaS) menu should be clicked. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- PostgreSQL(DBaaS) list page, click the resource to check the backup history. It moves to the PostgreSQL(DBaaS) details page.
- Click the Backup History button. The Backup History popup window will open.
- Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.
Deleting backup files
To delete the backup history, follow these steps.
- All services > Database > PostgreSQL(DBaaS) menu, click. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- PostgreSQL(DBaaS) list page, click the resource to check the backup history. It moves to the PostgreSQL(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window, check the file you want to delete, and then click the Delete button.
PostgreSQL(DBaaS) recovery
In the event of a failure or data loss that requires restoration from a backup file, the recovery function can be used to restore to a specific point in time. When performing a PostgreSQL (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, the DB is installed with the version at the backup point, and the recovery proceeds with the DB configuration information and data.
To restore PostgreSQL(DBaaS), follow these steps.
- All services > Database > PostgreSQL(DBaaS) menu is clicked. It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the PostgreSQL(DBaaS) menu. It moves to the PostgreSQL(DBaaS) list page.
- PostgreSQL(DBaaS) resource list page, click the resource you want to restore. It moves to the PostgreSQL(DBaaS) detail page.
- Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
- Database Recovery Configuration area, enter the corresponding information, and then click the Complete button.
| Classification | Necessity | Detailed Description |
|---|---|---|
| Recovery Type | Required | Set the point in time to recover
|
| Server name prefix | Required | Server name of the recovery DB
|
| Cluster Name | Required | Cluster name of the recovery DB
|
| Service Type > Server Type | Required | Server type where the recovery DB will be installed
|
| Service Type > Planned Compute | Selection | Current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Recovery DB uses Block Storage settings
|
| Database username | required | Database username set in the original DB |
| Database Port number | required | Database Port number set in the original DB |
| IP Access Control | Select | IP address to access the recovery DB
|
| Maintenance period | Select | DB maintenance period
|
| Tag | Select | Add Tag
|
2.2.3 - Read Replica Setup
The user can enter the required information for a Read Replica through the Samsung Cloud Platform Console and create the service using detailed options.
Replica Configure
Through the 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. Navigate 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 Click the resource to configure the replica on the page. PostgreSQL(DBaaS) Detail Navigate to the page.
- Click the Replica configuration button. Navigate to the Replica configuration page.
- Replica configuration After entering information in the area, click the Complete button.
Category RequiredDetailed description Region Required Region to configure Replica - Replica configuration (Other Region) displayed only when selected
Number of Replicas Required Number of Replicas to configure - Up to 5 can be configured per cluster
- If selecting more than 2 values, additionally input Replica name and service type information
Replica name Required Replica server name - Start with a lowercase English letter, and use lowercase letters, numbers, and the special character (
-) to input 3 to 19 characters
- The entered Replica name is displayed as the cluster name in the list
Service Type > Server Type Required Replica Server Type - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server with 24 vCore or more
Service Type > Planned Compute Optional Status of resources with Planned Compute set - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute set
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Go to the Planned Compute service application page
- For details, refer to Apply for Planned Compute
IP Access Control Select Service Access Policy Settings - Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
Maintenance Period Select DB Maintenance Period - If Use is selected, set the day of the week, start time, and duration.
- It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption.
- If set to not use, we are not responsible for issues arising from patches not being applied.
Tag Select Add Tag - Add Tag button click then input or select Key, Value values
Table. PostgreSQL(DBaaS) Replica configuration items
Replica Reconstruct
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 function.
To reconstruct the Replica, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the menu. Go to the Service Home page of PostgreSQL(DBaaS).
- Service Home page, click the PostgreSQL(DBaaS) menu. Move to the PostgreSQL(DBaaS) list page.
- PostgreSQL(DBaaS) list page, click the resource to reconfigure the Replica. PostgreSQL(DBaaS) details page will be opened.
- Replica reconstruction Click the button. Replica reconstruction notification A popup window opens.
- Replica Reconstruction Notification in the popup window click the Confirm button.
Promote Replica Cluster to Master Cluster
You can promote a Replica Cluster that has completed configuration to a Master Cluster.
To promote a Replica Cluster to Master, follow these steps.
- All Services > Database > PostgreSQL(DBaaS) Click the 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.
- Click the resource to promote to Master on the PostgreSQL(DBaaS) List page. You will be taken to the PostgreSQL(DBaaS) Details page.
- Click the More button and click the Master promotion button. The Master promotion notification popup window opens.
- Master Promotion Notification in the popup window click the Confirm button.
2.2.4 - Connect to DB Server
Scenario Overview
The PostgreSQL(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and Database service are created, and the DB service is accessed through the Bastion host. To securely access PostgreSQL(DBaaS) in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.
This scenario largely describes the process of creating Bastion host and Database services, and configuring the network environment for Bastion host and Database connection, to connect through a DB access client.
Scenario Components
You can configure 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 allows users to subdivide the network into smaller parts for specific purposes/scales within the VPC | |
| Networking | VPC > Public IP | A service that reserves public IP and assigns and returns it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the internet | |
| Networking | Security Group | A virtual firewall that controls the server’s 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 Virtual Server |
Scenario composition method
To configure the scenario, create the necessary services through the following procedure.
1. Configuring the Network
This describes the process of configuring the network environment for Bastion Host and Database service connection.
1-1. Creating a VPC
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
- VPC Creation page, please enter the information required for service creation.
- IP range should be entered as
192.168.x.0/16.
- IP range should be entered as
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- After creation is complete, check the created resource on the VPC list page.
1-2. Creating a Subnet
- Click on the menu for all services > Networking > VPC. It moves to the Service Home page of VPC.
- Service Home page, click the Subnet menu. It moves to the Subnet list page.
- Click the Subnet Creation button. It moves to the Subnet Creation page.
- Subnet Creation page where you enter the information needed to create a service.
- Subnet type should be selected as General.
- Please select a pre-created VPC.
- IP range should be entered as
192.168.x.0/24.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- Once creation is complete, check the created resource on the Subnet list page.
1-3. Creating an Internet Gateway
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Internet Gateway menu. It moves to the Internet Gateway list page.
- Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
- Internet Gateway creation page, please enter the required information necessary for service creation.
- Please select a pre-created VPC.
- Select Use in the Firewall usage item.
- In the Summary panel, review the detailed information and the estimated charge, then click the Complete button.
- Once the creation is complete, check the created resource on the Internet Gateway list page.
1-4. Creating a Public IP
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Public IP menu. It moves to the Public IP list page.
- Public IP Reservation button, click. Move to the Public IP Reservation page.
- Public IP Reservation page, enter the required information necessary for service reservation.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- After creation is complete, check the created resource on the Public IP List page.
1-5. Creating a Security Group
- Click on the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
- Click the Security Group creation button on the Service Home page. It moves to the Security Group creation page.
- Security Group creation page where you enter the required information necessary for service creation.
- Check the input information and click the Complete button.
- After creation is complete, check the created resource on the Security Group list page
2. Creating a Bastion Host
This describes the process of configuring the Bastion Host where the database connection client should be installed.
2-1. Creating a Server Keypair
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Click the Keypair menu on the Service Home page. It moves to the Keypair list page.
- Keypair creation button should be clicked. It moves to the Keypair creation page.
- Keypair creation page, please enter the required information necessary for service creation.
- Check the creation information and click the Complete button.
- The key can only be downloaded for the first time, and re-issuance is not provided.
- Please keep the downloaded key in a safe place.
2-2. Creating a Bastion Host
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Click the Virtual Server Creation button on the Service Home page. It moves to the Virtual Server Creation page.
- Virtual Server creation page where you enter the required information necessary for service creation.
- Image is Windows please select.
- Please select the pre-created VPC and Subnet.
- Click NAT usage and select the Public IP reserved in 1-4. Public IP creation.
- 2-1. Creating Server Keypair Connect the Keypair created from 2-1. Creating Server Keypair.
- Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
- Once creation is complete, check the created resource on the Virtual Server list page.
2-3. Check Bastion host connection ID and PW
- Click on the menu for all services > Compute > Virtual Server. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
- Virtual Serve list page, click on the resource created in 2-2. Bastion host creation. It moves to the detailed information page of the corresponding resource.
- Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window will open.
- RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Creating a server keypair.
- After attaching, click the Password Check button. The ID and password required to access the resource will be displayed.
- The ID and Password will be used as information to connect to the Bastion host later, as described in 5-1. Connect to Bastion host.
3. Creating a Database
Describes the process of creating a database service.
3-1. Creating PostgreSQL(DBaaS) Service
- Click on the menu for all services > Database > PostgreSQL(DBaaS). It moves to the Service Home page of PostgreSQL(DBaaS).
- On the Service Home page, click the Create PostgreSQL(DBaaS) button. It moves to the Create PostgreSQL(DBaaS) page.
- PostgreSQL(DBaaS) creation page, please enter the required information needed for service creation.
- Select and connect the pre-created VPC and Subnet.
- Enter database-related creation information on the essential information input screen.
- Add the Bastion host IP to the IP access control items.
- Database Port is 2866 by default, but you can specify it as you want.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- After creation is complete, check the created resource on the PostgreSQL(DBaaS) list page.
4. Setting Rules
This describes the process of setting rules for users to access the Bastion host and rules for the Bastion host to access the Database.
4-1. Adding Security Group Security Rules
- Click on the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
- Service Home page, click the Security Group menu. Move to the Security Group list page.
- 1-5. Creating a Security Group Select the Security Group resource created from. It will move to the detailed information page of the resource.
- Click the Rules tab on the detail information page. It moves to the Rules tab.
- Click the Rules tab and click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule popup window, enter the rules below, and click the OK button
| Direction | Remote | Destination Address | Protocol | Port | Description |
|---|---|---|---|---|---|
| Inbound | CIDR | User PC IP | TCP | 3389 (RDP) | Bastion access PC → Bastion host |
| Outbound | CIDR | DB IP | TCP | Database Port (direct input) | Bastion host → Database |
| Fig. Security Group security rules to be added |
4-2. Adding IGW Firewall Rules
- Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
- Service Home page, click the Firewall menu. It moves to the Firewall list page.
- Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway, and move to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule In the popup window, enter the rules below and click the OK button.
| Departure Address | Destination Address | Protocol | Port | Action | Direction | Description |
|---|---|---|---|---|---|---|
| Bastion access PC IP | Bastion host IP | TCP | 3389(RDP) | Allow | Inbound | User PC → Bastion host |
| Table. Internet Gateway Firewall rules to be added |
5. Connect to Database
This describes the process of a user accessing the Database through a DB connection client program.
This guide provides instructions on how to connect using pgAdmin. There are various database client programs and CLI utilities, so you can install and use the tools that are suitable for the user.
5-1. Connect to the Bastion host
- Run Remote Desktop Connection in the Windows environment of the PC you want to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
- After a successful remote desktop connection, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Checking Bastion Host Access ID and PW and click the Confirm button.
5-2. Installing DB connection client program (pgAdmin) on the Bastion host
- Go to the official pgAdmin page and download the pgAdmin program.
- pgAdmin program download path: https://www.pgadmin.org/download/
- Connect the hard drive of the user PC to upload the file to the Bastion host.
- Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
- Select the local disk where the file was downloaded to the drive and click the Confirm button.
- Copy the downloaded file and upload it to the Bastion Host, then click the pgAdmin installation file to install it.
5-3. Using DB connection client program (pgAdmin) to connect to the database
- 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) service creation in the General tab and Connection tab, and click the Save button.
Screen (Tab) Required Input Element Items 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 DB connection client program input items - Click the database name created on pgAdmin to connect.
- You can try simple queries after connecting.
2.2.5 - Using Extensions
PostgreSQL(DBaaS) Extension usage
The list of extensions that can be installed in the current database can be checked with the following SQL statement.
SQL> select * from pg_available_extensions;
PostgreSQL(DBaaS) has the following additional installation items outside of the default extension by version:
| Extension name | description |
|---|---|
| pgaudit | provides detailed audit logging functionality at the session and object level |
| pg_cron | a scheduler that allows job scheduling with cron syntax within the database |
| pg_hint_plan | Provides a feature to apply hint clauses to SQL execution plans |
| pgvector | Vector data type and similarity search, etc. AI vector operation function provided |
| postgis | GIS (Geographic Information System) provides spatial object storage and spatial query functionality |
In addition to the above items, if additional Extension installation is required, please refer to Support Center > 문의하기 and inquire.
- Once the inquiry is received, we will proceed with the installation after review. Please note that some Extensions may not work normally during Replica configuration and recovery.
2.3 - API Reference
2.4 - CLI Reference
2.5 - Release Note
PostgreSQL(DBaaS)
- You can configure a disaster recovery Replica using the Replica configuration (Other Region) feature.
- PostgreSQL(DBaaS) Add feature
- 2nd generation server type added
- Intel 4th generation (Sapphire Rapids) Processor based 2nd generation (db2) server type added. For more details, see PostgreSQL(DBaaS) server type.
- DB User and Access Control Management and Archive Setting Feature added
- For more details, see DB User Management, DB Access Control Management, Archive Management.
- DB Audit Log Export feature added
- For more details, see DB Log Export.
- Backup notification feature provided
- Provides notification feature for backup success and failure. For more details, refer to Create Notification Policy.
- Migration feature added
- Provides replication-based zero-downtime data migration functionality. For more details, see Migration 구성하기.
- Add HDD, HDD_KMS types to Block Storage type
- 2nd generation server type added
- PostgreSQL(DBaaS) feature change
- PostgreSQL new version added: 13.16, 14.13, 15.8
- Add 2nd generation server type
- Intel 4th generation (Sapphire Rapids) Processor based 2nd generation (dbh2) server type added. For more details, see PostgreSQL(DBaaS) Server Type.
- After creating the service Block Storage capacity expansion is possible.
- Server-specific network IP configuration feature added allowing common or server-specific settings depending on the usage purpose.
- Samsung Cloud Platform Common Feature Change
- Account, IAM and Service Home, tags etc. have reflected the common CX changes.
- Block Storage type volume-encrypted storage selection option has been added.
- Redundant Active DB and Standby DB’s Role Switch (Active ↔ Standby) feature has been added.
- Linked with the cloud monitoring service, performance and log monitoring of DB instances is possible.
- Depending on the server type selected by the customer, Planned Compute policy setting is possible.
- PostgreSQL (DBaaS) service that can easily create and manage PostgreSQL in a web environment has been launched.
3 - MariaDB(DBaaS)
3.1 - Overview
Service Overview
MariaDB (DBaaS) is an open source relational database (RDBMS) with high compatibility with MySQL. Samsung Cloud Platform provides an environment that can automate MariaDB installation and perform management functions for operation through a web-based console.
MariaDB (DBaaS) is designed as a high-availability architecture that performs storage-based data replication and minimizes failover time. To prevent data loss, when the content of the Active server changes, it is synchronously replicated to the Standby server, and up to five read-only servers called Replicas are provided for read load balancing and disaster recovery (DR). Additionally, to prepare for issues with the DB server or data, it offers a feature that automatically backs up at a user-specified time, supporting data recovery at the desired point in time.
Provided Features
MariaDB (DBaaS) provides the following features.
- Auto Provisioning (Auto Provisioning): Installation and configuration of Database (DB) via UI is possible, and it provides an Active-standby redundancy configuration built on storage replication. In case of an Active server failure, 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, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), the user can directly perform node switching between Active-Standby via Switch-over.
- Backup and Recovery: Provides data backup functionality based on its own backup command. The backup time window and storage organization can be set by the user, and additional fees may be incurred depending on backup volume. It also provides a recovery function for backed-up data, so when the user performs recovery, a separate DB is created and recovery proceeds to the point in time selected by the user (backup save point, user-defined point). When recovering to a user-specified point, the recovery point can be set to 5 minutes/10 minutes/30 minutes/1 hour before the stored backup file and archive file.
- Version Management: Provides version upgrade (Minor) functionality due to some feature improvements and security patches. Whether to perform a backup for the version upgrade can be selected by the user, and if a backup is performed, data is backed up before applying the patch, then the DB engine is updated.
- Replica configuration: You can add up to 5 read-only Read Replicas, enabling read performance scaling and load balancing.
- Audit setting: Provides an Audit setting feature that can monitor the user’s DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) execution.
- Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
- Service status query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
- DB User Management: View and manage DB account (user) information registered in the DB.
- DB Access Control Management: Based on DB accounts registered in the DB, you can register and revoke allowed IPs for access.
- Archive Management: You can set the Archive file retention period (1 day~35 days) within the DB server and configure the Archive mode (On/Off).
- DB Log Export: Through Audit settings, you can export stored logs to the user’s Object Storage.
- Migration: Synchronize data in real time with the operating database, and support migration using replication method without service interruption.
Components
MariaDB (DBaaS) provides pre-validated engine versions and various server types according to the open source support policy. Users can select and use them according to the scale of the service they want to configure.
Engine Version
The engine versions supported by MariaDB (DBaaS) are as follows.
Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to 6 months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
- MariaDB (Community): https://mariadb.org/about/#maintenance-policy
| Service | Provided Version | EOS Date(Samsung Cloud Platform New Creation Stop Date) | EoTS Date(Community Technical Support End Date) |
|---|---|---|---|
| MariaDB (Community) | 10.6.5 | 2026-03 (planned) | 2026-07-06 |
| 10.6.9 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.10 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.12 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.14 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.15 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.16 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.17 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.19 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.6.22 | 2026-03 (scheduled) | 2026-07-06 | |
| 10.11.8 | 2027-09 (scheduled) | 2028-02-16 | |
| 10.11.9 | 2027-09 (scheduled) | 2028-02-16 | |
| 10.11.13 | 2027-09 (scheduled) | 2028-02-16 | |
| 11.4 | 2029-09 (scheduled) | 2030-01-16 |
Server Type
The server types supported by MariaDB (DBaaS) are as follows.
For detailed information about the server types provided by MariaDB(DBaaS), see MariaDB(DBaaS) Server Type.
Standard db1v2m4
| Category | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Provided Server Types
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | Number of vCores
|
| Server Specifications | m4 | Memory Capacity
|
Preliminary Service
This is a list of services that must be pre-configured before creating the service. For details, 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 independent virtual network in a cloud environment |
3.1.1 - Server Type
MariaDB(DBaaS) Server Type
MariaDB(DBaaS) provides server types with various combinations of CPU, Memory, and Network Bandwidth. When creating a MariaDB(DBaaS), the database engine is installed according to the selected server type, which is chosen based on the intended use.
The server types supported by MariaDB(DBaaS) are as follows:
Standard db1v2m4
Classification | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Classification of provided server types
|
| Server Specification | db1 | Classification of provided server types and generation
|
| Server Specification | v2 | Number of vCores
|
| Server Specification | m4 | Memory capacity
|
db1 Server Type
The db1 server type of MariaDB(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
- Supports up to 16 vCPUs and 256 GB of memory
- Up to 12.5 Gbps networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db1v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | db1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v6m12 | 6 vCore | 12 GB | Up to 10 Gbps |
| Standard | db1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db1v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
dbh2 Server Type
The dbh2 server type of MariaDB(DBaaS) is provided with high-capacity server specifications and is suitable for large-scale data processing database workloads.
- Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
- Supports up to 128 vCPUs and 1,536 GB of memory
- Up to 25Gbps networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Up to 25 Gbps |
3.1.2 - Monitoring Metrics
MariaDB(DBaaS) Monitoring Metrics
The following table shows the performance monitoring metrics of MariaDB(DBaaS) that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
For server monitoring metrics of MariaDB(DBaaS), refer to the Virtual Server monitoring metrics guide.
| Performance Item | Detailed Description | Unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Sessions | Number of Active Sessions | cnt |
| Connection Usage [Total] | DB connection session usage rate | % |
| Connections | Number of connections | cnt |
| Connections [MAX] | Maximum number of connected threads | cnt |
| Binary Log Used [MB] | Binary log usage | MB |
| Data Directory Used [MB] | Data directory usage | MB |
| Open Files | Number of open DB files | cnt |
| Open Files [MAX] | Maximum number of openable DB files | cnt |
| Open Files Usage | DB file maximum usage rate | % |
| Relay Log Used [MB] | Relay log usage | MB |
| Instance Status [PID] | mariadbd process | pid |
| Safe PID | mariadbd_safe process | pid |
| Slave Behind Master seconds | Time difference between Master and Slave data (only executed on slave) | sec |
| Tablespace Used | Tablespace usage | MB |
| Tablespace Used [Total] | Total Tablespace usage | MB |
| Running Threads | Number of running threads | cnt |
| Slowqueries | Number of sessions that execute SQL for more than 10 seconds | cnt |
| Slowqueries [Total] | Total number of sessions that execute SQL for more than 10 seconds | cnt |
| Transaction Time [Long] | Longest transaction execution time | sec |
| Wait Locks | Number of sessions blocked by lock for more than 60 seconds | cnt |
3.2 - How-to guides
The user can enter the required information for MariaDB (DBaaS) and select detailed options through the Samsung Cloud Platform Console to create the service.
Creating MariaDB(DBaaS)
You can create and use the MariaDB (DBaaS) service from the Samsung Cloud Platform Console.
- Please configure the VPC’s Subnet type as General before creating the service.
- If the Subnet type is Local, the creation of the corresponding Database service is not possible.
- If you load more than 2 TB of large data, backups may take a long time or the DB’s performance may degrade. To prevent this, you need to consider operational aspects such as cleaning up unnecessary data or moving old data to a statistical collection environment.
To create MariaDB (DBaaS), follow the steps below.
- Click the All Services > Database > MariaDB(DBaaS) menu. You will be taken to the Service Home page of MariaDB(DBaaS).
- Service Home on the page click the MariaDB(DBaaS) creation button. Navigate to the MariaDB(DBaaS) creation page.
- MariaDB(DBaaS) creation on the page, enter the information required to create the service, and select detailed options.
- Please select the required information in the Image and version selection area.
Category RequiredDetailed description Image version Required Provide version list of MariaDB (DBaaS) Table. MariaDB(DBaaS) Image and Version Selection Items - Service Information Input Enter or select the required information in the area.
Category Required or notDetailed description Server name Prefix Required Name of the server where the DB will be installed - Start with a lowercase English letter, and use lowercase letters, numbers, and the special character (
-) to input 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is attached to create the actual server name
Cluster Name Required Cluster name composed 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 where DB will be installed - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server of 24 vCore or more
- For detailed information about server types provided by MariaDB (DBaaS), refer to MariaDB(DBaaS) Server Type
Service Type > Planned Compute Select Status of resources with Planned Compute set - In Use: Number of resources with Planned Compute set that are currently in use
- Configured: Number of resources with Planned Compute set
- Coverage Preview: Amount applied by Planned Compute per resource
- Create Planned Compute Service: Go to the Planned Compute service application page
- For details, refer to Apply for Planned Compute
Service Type > Block Storage Required Block Storage settings used by DB according to purpose - Base OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Select the storage type and then enter the capacity. (For detailed information on each Block Storage type, refer to Create Block Storage)
- SSD: High-performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes using Samsung Cloud Platform KMS (Key Management System) encryption keys
- The configured storage type is applied identically to additional storage
- Capacity must be entered as a multiple of 8 within the range 16 ~ 5,120
- Since large sorts during SQL execution or monthly batch processes can cause service interruptions, a separate TEMP storage must be allocated and used
- Select the storage type and then enter the capacity. (For detailed information on each Block Storage type, refer to Create Block Storage)
- Additional: Data storage areas for DATA, Archive, TEMP, Backup
- After selecting Use, enter the storage’s purpose and capacity
- The storage type is applied the same as set for DATA, and capacity can be entered as a multiple of 8 within the range 16 ~ 5,120
- Click the + button to add storage, and the x button to delete. Up to 9 can be added
- Temporarily store backup data in BACKUP storage before transmitting backup data
- 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. It is advised to set the backup capacity to about 60% of the DATA capacity
- If a BACKUP storage is not added, using the
/tmparea is recommended
- For each service, only one Block Storage is allocated for Archive, TEMP, BACKUP
Redundancy Configuration Selection Redundancy Configuration Status - If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
Network > Common Settings Required Network settings where servers generated by the service are installed - Select if you want to apply the same settings to all servers being installed
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be auto‑generated
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select a reserved IP from the VPC product’s Public IP. See Create Public IP for details.
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select if you want to apply different settings per installed server
- Select a pre-created VPC, Subnet, IP, Public NAT
- Enter each server’s IP
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select from reserved IPs in the VPC product’s Public IP. For more details, see Create Public IP.
IP Access Control Select Service Access Policy Settings - Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required.
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
Maintenance Period Select DB Maintenance Period - Use is selected, set day of week, start time, and duration
- It is recommended to set a maintenance period for stable DB management. Patch work is performed at the set time, causing service interruption
- If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
Table. MariaDB (DBaaS) Service Information Input Items - Start with a lowercase English letter, and use lowercase letters, numbers, and the special character (
- Database configuration required information input area, please enter or select the required information.
Category Required or notDetailed description Database name Required Server name applied when installing DB - Start with English letters, use English letters and numbers, input 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 usernames can be checked in the Console
Database password Required Password to use when accessing the DB - Enter 8~30 characters including letters, numbers, and special characters (
“‘excluded)
Database Password Confirmation Required Re-enter the same password to be used when accessing the DB Database Port Number Required Port number required for DB connection - Enter DB port within the range 1,024 ~ 65,535
Backup > Use Select Whether to use backup - Select Use to set the backup file retention period, backup start time, and Archive backup cycle
Backup > Retention Period Select Backup retention period - Select backup retention period. File retention period can be set from 7 days to 35 days
- Backup files incur separate charges based on size
Backup > Backup Start Period Select 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 frequency Select Archive backup frequency - Select the Archive backup frequency
- Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Audit Log Settings Select Whether to store Audit Log - Enable를 선택하여 Audit Log 기능을 설정
- User connection information records are stored
- Users can specify the types of events to audit via the
server_audit_eventsparameter, and it can be modified through the Parameter screen
- Refer to the MariaDB documentation for details on this parameter
- Users can specify the types of events to audit via the
- Enabling Audit may degrade DB performance
- User connection information records are stored
Parameter Required Parameters to use in the DB - Lookup Click the button to view detailed information of the parameter
- Parameters can be modified after DB creation is complete, and after modification the DB must be restarted
DB character set Required Character encoding method to use for the DB - The character set used when storing text data, and the DB is created with this encoding set as the default.
Time zone Required Standard time zone to be used by the Database Table. MariaDB(DBaaS) Database configuration items - Additional Information Input area: enter or select the required information.
Category Required or notDetailed description Tag Select Add Tag - Up to 50 can be added per resource
- After clicking the Add Tag button, enter or select Key, Value values
Table. MariaDB(DBaaS) Additional Information Input Items
- Please select the required information in the Image and version selection area.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resource on the Resource List page.
MariaDB(DBaaS) Check detailed information
MariaDB(DBaaS) service can view and edit the full resource list and detailed information. The MariaDB(DBaaS) Details page consists of Details, Tags, Activity Log tabs, and for DBs with a Replica configured, an additional Replica Information tab is included.
To view detailed information about the MariaDB (DBaaS) service, follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. Navigate to the Service Home page of MariaDB(DBaaS).
- Click the MariaDB(DBaaS) menu on the Service Home page. You will be taken to the MariaDB(DBaaS) List page.
- Click the resource to view detailed information on the MariaDB(DBaaS) List page. You will be taken to the MariaDB(DBaaS) Details page.
- MariaDB(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
Category Detailed description Cluster Status Cluster status with DB installed - Creating: Cluster is being created
- Editing: Cluster is being changed to operation execution state
- Error: Cluster encountered a failure while performing tasks
- If it occurs continuously, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Cluster is being restarted
- Running: Cluster is operating normally
- Starting: Cluster is being started
- Stopped: Cluster is stopped
- Stopping: Cluster is being stopped
- Synchronizing: Cluster is being synchronized
- Terminating: Cluster is being deleted
- Unknown: Cluster status is unknown
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is changing to upgrade execution state
Cluster Control Button to change cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to active
More additional features Cluster related management buttons - Service status synchronization: Real-time DB service status lookup
- Backup history: If backup is set, check whether backup runs normally and view history
- Database recovery: Recover DB based on a specific point in time
- Parameter management: DB configuration parameters can be queried and modified
- Replica configuration: Set up a read-only cluster called Replica
- DB user management: View and manage 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
- Archive management: Can set archive file retention period and archive mode
- DB Log export: Through audit settings, stored logs can be exported to the user’s Object Storage
- Migration configuration: Provides migration functionality using replication method
Service termination Button to cancel the service Table. MariaDB (DBaaS) status information and additional features
Detailed Information
MariaDB(DBaaS) List page allows you to view detailed information of the selected resource and, if necessary, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in the respective 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 |
| Creator | User who created the service |
| Creation time | Service creation time |
| Editor | User who modified the service information |
| Modification date/time | Date and time when 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 | Name of the cluster composed of DB servers |
| Master Cluster Name | Master Cluster Name of the Replica
|
| Database name | Server name applied when installing DB |
| Database username | DB user name |
| Planned Compute | Resource status with Planned Compute set
|
| Maintenance Period | DB Maintenance Period Status
|
| Backup | Backup configuration status
|
| Audit Log Settings | Audit Log Settings Status
|
| Time zone | Standard time zone used by the Database |
| DB character set | character encoding method to be used in DB |
| VIP | Virtual IP information
|
| Network | Network information where DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP Access Control | Service Access Policy Settings
|
| 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 check the master cluster name, number of replicas, and replica status.
| Category | Detailed description |
|---|---|
| Master Information | Name of Master Cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status created in the Master cluster
|
Tag
MariaDB(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
|
Work History
You can view the operation history of the selected resource on the MariaDB(DBaaS) List page.
| Category | Detailed description |
|---|---|
| Work History List | Resource Change History
|
MariaDB(DBaaS) Manage Resources
If you need to change or restore the existing configuration options of a created MariaDB (DBaaS) resource, or need a Replica configuration, you can perform the work on the MariaDB(DBaaS) Details page.
Control Operation
If changes occur to the running MariaDB (DBaaS) resources, you can start, stop, or restart them. Also, if HA is configured, you can switch the Active-Standby servers via Switch-over.
To control the operation of MariaDB (DBaaS), follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. Navigate to the Service Home page of MariaDB(DBaaS).
- Click the MariaDB(DBaaS) menu on the Service Home page. Go to the MariaDB(DBaaS) list page.
- MariaDB(DBaaS) 목록 Click the resource to control operation. MariaDB(DBaaS) 상세 Navigate to the page.
- Check the status of MariaDB (DBaaS) and complete the change using the control button below.
- Start: The server where the DB service is installed and the DB service are 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 MariaDB (DBaaS).
To check the service status of MariaDB (DBaaS), follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. Navigate to the Service Home page of MariaDB(DBaaS).
- Click the MariaDB(DBaaS) menu on the Service Home page. Navigate to the MariaDB(DBaaS) List page.
- Click the resource to view the service status on the MariaDB(DBaaS) List page. Move to the MariaDB(DBaaS) Details page.
- Click the Service Status Synchronization button. 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 status.
Change Server Type
You can change the configured server type.
To change the server type, follow the steps below.
- Click the All Services > Database > MariaDB(DBaaS) menu. You will be taken to the Service Home page of MariaDB(DBaaS).
- Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) list page.
- MariaDB(DBaaS) List page, click the resource to change the server type. Move to the MariaDB(DBaaS) Details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Edit Server Type popup window will open.
- Edit Server Type After selecting the server type in the popup window, click the Confirm button.
Add Storage
If more than 5TB of data storage space is required, you can add storage. In the case of a redundant DB configuration, all redundant servers are added simultaneously.
- It will be applied the same way as the selected Storage type when creating the service.
- For a DB with redundancy configured, adding storage will be applied simultaneously to the storage of the Active DB and the Standby DB.
- If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. Expand the Replica storage first, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow the steps below.
- Click the All Services > Database > MariaDB(DBaaS) menu. Navigate to the Service Home page of MariaDB(DBaaS).
- Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) list page.
- MariaDB(DBaaS) List Click the resource to add storage on the page. MariaDB(DBaaS) Details Navigate to the page.
- Click the Add Disk button at the bottom of the detailed information. The Add Storage Request popup window opens.
- Additional Storage Request In the popup window, after entering purpose and capacity, click the Confirm button.
Expanding Storage
You can expand the storage added to the data area up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. Navigate to the Service Home page of MariaDB(DBaaS).
- Click the MariaDB(DBaaS) menu on the Service Home page. Navigate to the MariaDB(DBaaS) List page.
- Click the resource to change the server type on the MariaDB(DBaaS) List page. It moves to the MariaDB(DBaaS) Details page.
- Click the Edit icon of the additional Disk you want to add at the bottom of the detailed information. The Edit Additional Storage popup window opens.
- Add Storage Modification In the popup window, after entering the expansion capacity, click the Confirm button.
MariaDB(DBaaS) Cancel
You can cancel unused MariaDB (DBaaS) to reduce operating costs. However, if you cancel the service, the running service may be stopped immediately, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.
- In the case of a DB with a Replica configured, even if you terminate the Master DB, the Replica is not deleted together. If you also want to delete the Replica, please terminate it separately from the resource list.
- If you cancel the DB, stored data and, if backup was set, all backup data will be deleted.
To cancel MariaDB (DBaaS), follow the steps below.
- All Services > Database > MariaDB(DBaaS) Click the menu. Navigate to the Service Home page of MariaDB(DBaaS).
- Service Home page, click the MariaDB(DBaaS) menu. Navigate to the MariaDB(DBaaS) list page.
- MariaDB(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
- Once the termination is complete, check whether the resource has been terminated on the MariaDB(DBaaS) list page.
3.2.1 - MariaDB(DBaaS) server connection
Scenario Overview
The MariaDB(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and Database service are created, and the DB service is accessed through the Bastion host. To access MariaDB (DBaaS) stably in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and network connection using it. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.
This scenario largely describes the process of creating a Bastion host and Database service, and configuring the network environment for Bastion host and Database connection, to connect through a DB access client.
Scenario Components
You can configure the scenario using the following services.
| Service Group | Service | Detailed Description | |
|---|---|---|---|
| Networking | VPC | A service that provides an independent virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that allows users to subdivide the network into smaller parts for their purpose/scale within the VPC | |
| Networking | VPC > Public IP | A service that reserves a public IP and assigns and returns it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the internet | |
| Networking | Security Group | A virtual firewall that controls the server’s traffic | |
| Database | MariaDB(DBaaS) | A service that easily creates and manages MariaDB in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to Virtual Server |
Scenario composition method
To configure the scenario, create the necessary services through the following procedure.
1. Configuring the Network
This explains the process of configuring the network environment for Bastion Host and Database service connection.
1-1. Creating a VPC
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
- VPC Creation page, please enter the information required for service creation.
- IP range should be entered as
192.168.x.0/16.
- IP range should be entered as
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- Once the creation is complete, check the created resource on the VPC List page.
1-2. Creating a Subnet
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Subnet menu. It moves to the Subnet list page.
- Click the Subnet Creation button. It moves to the Subnet Creation page.
- Subnet creation page where you enter the information needed to create a service.
- Subnet type should be selected as General.
- Please select a pre-created VPC.
- IP range should be entered as
192.168.x.0/24.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- After creation is complete, check the created resource on the Subnet list page.
1-3. Creating an Internet Gateway
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Internet Gateway menu. It moves to the Internet Gateway list page.
- Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
- Internet Gateway creation page, please enter the required information necessary for service creation.
- Please select a pre-created VPC.
- Select Use in the Firewall usage item.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- Once the creation is complete, check the created resource on the Internet Gateway list page.
1-4. Creating a Public IP
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Public IP menu. It moves to the Public IP list page.
- Public IP Reservation button, click. Move to the Public IP Reservation page.
- Public IP Reservation page, enter the required information necessary for service reservation.
- In the Summary panel, review the details generated and the expected charge amount, then click the Complete button.
- Once creation is complete, check the created resource on the Public IP List page.
1-5. Creating a Security Group
- Click All services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
- Click the Security Group Creation button on the Service Home page. It moves to the Security Group Creation page.
- Security Group creation page, please enter the required information necessary for service creation.
- Check the input information and click the Complete button.
- After creation is complete, check the created resource on the Security Group list page
2. Creating a Bastion Host
This describes the process of configuring the Bastion Host where the database connection client should be installed.
2-1. Creating a Server Keypair
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Keypair menu. It moves to the Keypair list page.
- Create Keypair button should be clicked. It moves to the Create Keypair page.
- Keypair creation page, please enter the required information necessary for service creation.
- Check the creation information and click the Complete button.
- The key can only be downloaded for the first time, and re-issuance is not provided.
- Please keep the downloaded key in a safe place.
2-2. Creating a Bastion Host
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Click the Virtual Server Creation button on the Service Home page. It moves to the Virtual Server Creation page.
- Virtual Server Creation page, please enter the required information necessary for service creation.
- The image is Windows, please select.
- Please select a pre-created VPC and Subnet.
- Click NAT Use and select the Public IP reserved in 1-4. Creating Public IP.
- 2-1. Creating a server Keypair Connect the Keypair created from
- In the Summary panel, review the details generated and the expected charge amount, then click the Complete button.
- After creation is complete, check the created resource on the Virtual Server list page.
2-3. Check Bastion host connection ID and PW
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server menu. It moves to the Virtual Server list page.
- Virtual Serve list page, click on the resource created in 2-2. Creating a Bastion host. It moves to the detailed information page of the corresponding resource.
- Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window opens.
- RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Creating a server keypair.
- After attaching, click the Password Check button. The ID and password required to access the resource will be displayed.
- The ID and Password will be used as information to access the Bastion host later, as described in 5-1. Bastion host 접속하기.
3. Creating a Database
It describes the process of creating a database service.
3-1. Creating the MariaDB (DBaaS) Service
- Click on the menu for all services > Database > MariaDB(DBaaS). It moves to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the Create MariaDB(DBaaS) button. It moves to the Create MariaDB(DBaaS) page.
- MariaDB(DBaaS) creation page, please enter the required information needed for service creation.
- Select and connect the pre-created VPC and Subnet.
- Enter database-related creation information on the required information input screen.
- Add the Bastion host IP to the IP access control item.
- Database Port is 2866 by default, but you can specify it as you want.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- Once the creation is complete, check the created resource on the MariaDB(DBaaS) list page.
4. Setting Rules
This describes the process of setting rules for users to access the Bastion host and for the Bastion host to access the Database.
4-1. Adding Security Group Security Rules
- Click on the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
- Service Home page, click the Security Group menu. Move to the Security Group list page.
- 1-5. Creating a Security Group Select the Security Group resource created from. It will move to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule In the popup window, enter the rules below and click the OK button
| Direction | Remote | Destination Address | Protocol | Port | Description |
|---|---|---|---|---|---|
| Inbound | CIDR | User PC IP | TCP | 3389 (RDP) | Bastion access PC → Bastion host |
| Outbound | CIDR | DB IP | TCP | Database Port (direct input) | Bastion host → Database |
4-2. Adding IGW Firewall Rules
- Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
- Service Home page, click the Firewall menu. It moves to the Firewall list page.
- Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway, and move to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Rule tab, click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule In the popup window, enter the rules below and click the OK button.
| Departure Address | Destination Address | Protocol | Port | Action | Direction | Description |
|---|---|---|---|---|---|---|
| Bastion access PC IP | Bastion host IP | TCP | 3389(RDP) | Allow | Inbound | User PC → Bastion host |
| Fig. Internet Gateway Firewall rules to be added |
5. Connecting to the Database
This describes the process of a user accessing the Database through a DB connection client program.
This guide provides instructions on how to connect using MySQL Workbench. There are various database client programs and CLI utilities, so you can also install and use the tools that are suitable for users.
5-1. Connect to Bastion host
- Run Remote Desktop Connection in the Windows environment of the PC you want to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
- After a successful remote desktop connection, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Checking Bastion Host Access ID and PW and click the Confirm button.
5-2. Installing DB connection client program (MySQL Workbench) on the Bastion host
- Go to the official MySQL page and download the MySQL Workbench program.
- MySQL Workbench program download path: https://dev.mysql.com/downloads/workbench
- Connect the hard drive of the user’s PC to upload the file to the Bastion host.
- Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
- Select the local disk where the file was downloaded to the drive and click the Confirm button.
- Copy the downloaded file and upload it to the Bastion Host, then click the MySQL Workbench installation file to install it.
5-3. Using DB connection client program (MySQL Workbench) to connect to the Database
- Run MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup window will appear.
- Manage Server Connection popup window, click the New button at the bottom left and enter the database server information created in 3-1. MariaDB(DBaaS) service creation, then click the Test Connection button. A Password popup window will appear.
Required Input Element Items Input Value Connection Name Custom (ex. Service Name) Host name Database server IP Port Database Port Username Database user name DB connection client program input items - Password popup window, enter the password set in 3-1. MariaDB(DBaaS) service creation and click the OK button. When the success is complete, click the OK button in the Manage Server Connection popup window.
- Database > Connect to Database를 클릭하세요. Connect to Database popup window will appear.
- Select the Connection Name registered in Stored Connection to perform database connection. After connection, you can try simple queries, etc.
3.2.2 - Managing DB Services
Users can manage MariaDB (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
It provides a feature to easily view and modify database configuration parameters.
Viewing Parameters
To view configuration parameters, follow these steps:
- Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
- Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
- Click the resource you want to view and modify parameters on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window will open.
- Click the View button in the Parameter Management popup window. The View Notification popup window will open.
- When the View Notification popup window opens, click the OK button. It may take some time to view.
Modifying Parameters
To modify configuration parameters, follow these steps:
- Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
- Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
- Click the resource you want to view and modify parameters on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window will open.
- Click the View button in the Parameter Management popup window. The View Notification popup window will open.
- When the View Notification popup window opens, click the OK button. It may take some time to view.
- If modification is necessary, click the Modify button and enter the modification contents in the custom value area of the parameter to be modified.
- When the input is complete, click the Save button.
Managing DB Users
It provides a management feature that allows you to view DB user information and change status information.
Viewing DB Users
To view DB users, follow these steps:
- Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
- Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
- Click the resource you want to view DB users on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
- Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
- Click the View button on the DB User Management page. It may take some time to view.
Changing DB User Status
To change the status of the viewed DB user, follow these steps:
- Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
- Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
- Click the resource you want to modify DB users on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
- Click the More button and then click the DB User Management button. You will be taken to the DB User Management page.
- Click the View button on the DB User Management page. It may take some time to view.
- If modification is necessary, click the Modify button and change the status value or enter notes.
- When the input is complete, click the Save button.
Managing DB Access Control
It provides an IP-based DB user access control management feature. Users can directly specify the IP that can access the database, allowing only authorized IPs to access.
Viewing DB Access Control
To view DB users with IP access control set, follow these steps:
- Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
- Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
- Click the resource you want to manage access control on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- Click the View button on the DB Access Control Management page. It may take some time to view.
Adding DB Access Control
To add IP access control, follow these steps:
- Click the All Services > Database > MariaDB (DBaaS) menu. You will be taken to the Service Home page of MariaDB (DBaaS).
- Click the MariaDB (DBaaS) menu on the Service Home page. You will be taken to the MariaDB (DBaaS) List page.
- Click the resource you want to add IP access control on the MariaDB (DBaaS) List page. You will be taken to the MariaDB (DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. You will be taken to the DB Access Control Management page.
- Click the View button on the DB Access Control Management page. It may take some time to view.
- When the view is complete, click the Add button. The DB Access Control Add popup window will open.
- In the DB Access Control Add popup window, select the DB user name and enter the IP address.
- When the input is complete, click the Save button.
Deleting DB Access Control
To delete IP access control, follow these steps:
- All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
- On the MariaDB(DBaaS) list page, click the resource for which you want to delete IP access control. Move to the MariaDB(DBaaS) details page.
- Click the More button and then click the DB Access Control Management button. Move to the DB Access Control Management page.
- On the DB Access Control Management page, click the Inquire button. It takes some time to inquire.
- Once the inquiry is complete, click the Delete button. The Delete pop-up window opens.
- In the Delete pop-up window, click the Confirm button.
Managing Archives
The Archive mode setting and Archive Log storage period setting functions are provided to allow users to flexibly set the Archive log management policy according to their operating environment. In addition, the function to manually delete Archive logs is provided together, allowing users to clean up unnecessary log data and effectively manage system resources.
Setting Archive Mode
To set the Archive mode, follow these steps:
- All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
- On the MariaDB(DBaaS) list page, click the resource for which you want to set the Archive mode. Move to the MariaDB(DBaaS) details page.
- Click the More button and then click the Archive Settings Management button. Move to the Archive Settings Management page.
- On the Archive Settings Management page, click the Inquire button. It takes some time to inquire.
- Click the Modify button and select the usage and storage period.
- Once the modification is complete, click the Save button.
Deleting Archive Files
To delete Archive files, follow these steps:
- All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
- On the MariaDB(DBaaS) list page, click the resource for which you want to set the Archive mode. Move to the MariaDB(DBaaS) details page.
- Click the More button and then click the Archive Settings Management button. Move to the Archive Settings Management page.
- On the Archive Settings Management page, click the Delete All Archives button to delete all Archive files, or click the Delete Backed-up Archives button to delete only the backed-up Archive files.
Exporting DB Logs
Supports exporting log data that requires long-term storage among audit logs to Object Storage. Users can directly set the type of log to be stored, the target bucket to be exported, and the cycle of exporting logs. According to the set criteria, logs are copied to the specified Object Storage for storage. In addition, an option to automatically delete the original log file while exporting logs to Object Storage is provided to efficiently manage disk space. By utilizing this option, users can safely store necessary log data for a long time while effectively securing storage capacity.
- To use the DB Log export function, Object Storage creation is required. Refer to the Object Storage User Guide for Object Storage creation.
- Be sure to check the expiration date of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
- Be careful not to expose authentication key information to the outside.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps:
- All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
- On the MariaDB(DBaaS) list page, click the resource for which you want to export DB logs. Move to the MariaDB(DBaaS) details page.
- Click the More button and then click the DB Log Export button. Move to the DB Log Export page.
- On the DB Log Export page, click the Registration button. Move to the DB Log Export Registration page.
- On the DB Log Export Registration page, enter the corresponding information and click the Save button.
| Category | Required | Detailed Description |
|---|---|---|
| Log Type | Required | Type of log to be stored |
| Storage Bucket Name | Required | Name of the Object Storage bucket to be stored |
| Authentication Key > Access Key | Required | Access key to access the Object Storage to be stored |
| Authentication Key > Secret Key | Required | Secret key to access the Object Storage to be stored |
| File Creation Cycle | Required | Cycle of creating files in Object Storage |
| Original Log Deletion | Optional | Whether to delete the original log when exporting to Object Storage |
Managing DB Log Export
To modify, cancel, or immediately export DB log export settings, follow these steps:
- All Services > Database > MariaDB(DBaaS) menu, click. Move to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
- On the MariaDB(DBaaS) list page, click the resource for which you want to manage DB log export. Move to the MariaDB(DBaaS) details page.
- Click the More button and then click the DB Log Export button. Move to the DB Log Export page.
- On the DB Log Export page, click the More button according to the log type you want to manage, and then click the Immediate Export, Modify, or Cancel button.
- Immediate Export: Exports the selected log to the Object Storage bucket set earlier.
- Modify: Modifies the DB log export mode setting.
- Cancel: Cancels the DB log export mode setting.
Upgrading DB Version
Provides a version upgrade function due to some feature improvements and security patches. Only minor version upgrades are supported within the same major version.
- Please perform version upgrades after checking the service status through service status synchronization.
- Please set up backups before performing version upgrades. If backups are not set, some data may not be recoverable in case of problems during the upgrade.
- In DBs with replicas configured, the master DB version cannot be higher than the replica version. Please check the replica version first and perform version upgrades as needed.
- Backed-up data will be automatically deleted after the version upgrade is complete.
To upgrade the version, follow the procedure below.
- Click the All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
- Click the MariaDB(DBaaS) menu on the Service Home page. It moves to the MariaDB(DBaaS) list page.
- Click the resource to be upgraded on the MariaDB(DBaaS) list page. It moves to the MariaDB(DBaaS) details page.
- Click the Modify button in the image/version item. The version upgrade popup window opens.
- In the version upgrade popup window, select the version to be modified and the backup setting, and then click the Confirm button.
- Click the Confirm button in the version upgrade notification popup window.
Configuring Migration
It provides a migration function that synchronizes with the operating database in real-time and replicates in a replication manner without interrupting the service.
To configure the migration, follow the procedure below.
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) list page.
- Click the resource to be migrated on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
- Click the More button to click the Configure Migration button. The Configure Migration popup window opens.
- In the Configure Migration popup window, check the instructions and click the Confirm button. It moves to the Configure Migration page.
- On the Configure Migration page, enter the corresponding information and click the Connect Check button.
- When the connection is complete, click the Complete button.
| Classification | Required | Detailed Description |
|---|---|---|
| Source DB Database Name | Required | Database name of the source DB that is the migration target |
| Source DB IP | Required | IP of the source DB that is the migration target |
| Source DB Port | Required | Port of the source DB that is the migration target |
| Source DB User Name | Required | User name of the source DB that is the migration target |
| Source DB Password | Required | Password of the source DB that is the migration target |
The configured migration cluster can be promoted to a master cluster.
To promote the migration cluster to a master, follow the procedure below.
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) list page.
- Click the resource to be promoted to a master on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
- Click the More button to click the Promote to Master button. The Master Promotion Notification popup window opens.
- Click the Confirm button in the Master Promotion Notification popup window.
3.2.3 - DB Backup and Recovery
The user can set up a backup of MariaDB(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.
Backing up MariaDB(DBaaS)
PostgreSQL(DBaaS) provides a data backup feature based on its own backup command, and also provides an optimized backup environment for data protection and management through backup history checking and backup file deletion functions.
Setting up backup
The backup setting method of MariaDB(DBaaS) is referred to MariaDB(DBaaS) creation.
To modify the backup settings of the created resource, follow these steps.
- For stable backup, it is recommended to add a separate BACKUP storage or sufficiently increase the storage capacity. Especially when the backup target data exceeds 100 GB and there are many data changes, please secure additional storage equivalent to about 60% of the data capacity. For storage addition and expansion methods, please refer to the MariaDB(DBaaS) Add Storage, MariaDB(DBaaS) Expand Storage guides. If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
- If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.
- All Services > Database > MariaDB(DBaaS) menu is clicked. It moves to the Service Home page of MariaDB(DBaaS).
- Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
- MariaDB(DBaaS) list page, click the resource to set the backup. Move to the MariaDB(DBaaS) details page.
- Click the Edit button of the backup item. The Backup Settings popup window opens.
- If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the OK button.
- If you want to stop the backup setting, uncheck Use in the Backup Setting popup window and click the OK button.
Check backup history
To check the backup history, follow these steps.
- Click All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) list page.
- MariaDB(DBaaS) list page, click the resource to check the backup history. It moves to the MariaDB(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.
Deleting backup files
To delete a backup file, follow these steps.
- All Services > Database > MariaDB(DBaaS) menu is clicked. It moves to the Service Home page of MariaDB(DBaaS).
- On the Service Home page, click the MariaDB(DBaaS) menu. It moves to the MariaDB(DBaaS) list page.
- MariaDB(DBaaS) list page, click the resource to check the backup history. It moves to the MariaDB(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- In the Backup History popup window, check the files you want to delete and click the Delete button.
Restore MariaDB(DBaaS)
In the event of a failure or data loss that requires restoration from a backup file, recovery is possible based on a specific point in time through the recovery function. When performing MariaDB (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, and the DB is installed with the version at the backup point in time, and the recovery proceeds with the DB configuration information and data.
To restore MariaDB(DBaaS), follow these procedures.
- Click All Services > Database > MariaDB(DBaaS) menu. It moves to the Service Home page of MariaDB(DBaaS).
- Service Home page, click the MariaDB(DBaaS) menu. Move to the MariaDB(DBaaS) list page.
- MariaDB(DBaaS) list page, click the resource you want to restore. Move to the MariaDB(DBaaS) details page.
- Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
- After entering information in the database recovery configuration area, click the Complete button.
| Classification | Necessity | Detailed Description |
|---|---|---|
| Recovery Type | Required | Set the point in time to recover
|
| Server name prefix | Required | Server name of the recovery DB
|
| Cluster Name | Required | Cluster name of the recovery DB
|
| Service Type > Server Type | Required | Server type where the recovery DB will be installed
|
| Service Type > Planned Compute | Selection | Current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Block Storage settings used by the recovery DB
|
| Database username | required | Database username set in the original DB |
| Database Port number | required | Database Port number set in the original DB |
| IP Access Control | Select | IP address to access the recovery DB
|
| Maintenance period | Selection | DB maintenance period
|
| tag | selection | add tag
|
3.2.4 - Configuring Read Replica
Users can create a Read Replica by entering the required information through the Samsung Cloud Platform Console and configuring detailed options.
Configuring Replica
Replica configuration allows you to create a read-only replica server. You can create up to 5 replicas per database.
To configure a replica, follow these steps:
- Click All Services > Database > MariaDB(DBaaS). This will take you to the MariaDB(DBaaS) Service Home page.
- Click MariaDB(DBaaS) on the Service Home page. This will take you to the MariaDB(DBaaS) list page.
- Click the resource you want to configure a replica for on the MariaDB(DBaaS) list page. This will take you to the MariaDB(DBaaS) details page.
- Click the Replica Configuration button. This will take you to the Replica Configuration page.
- Enter the information in the replica configuration area and click the Complete button.
| Category | Required | Detailed Description |
|---|---|---|
| Number of Replicas | Required | The number of replicas to configure
|
| Replica Name | Required | The name of the replica server
|
| Service Type > Server Type | Required | The type of replica server
|
| Service Type > Planned Compute | Optional | The current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Block storage settings for the replica DB
|
| IP Access Control | Optional | Service access policy setting
|
| Maintenance Period | Optional | DB maintenance period
|
Reconfiguring Replica
If a network failure or replication delay occurs between the master cluster and the replica, you can reconfigure the replica to re-replicate the master cluster’s data.
To reconfigure a replica, follow these steps:
- Click All Services > Database > MariaDB(DBaaS). This will take you to the MariaDB(DBaaS) Service Home page.
- Click MariaDB(DBaaS) on the Service Home page. This will take you to the MariaDB(DBaaS) list page.
- Click the resource you want to reconfigure a replica for on the MariaDB(DBaaS) list page. This will take you to the MariaDB(DBaaS) details page.
- Click the Reconfigure Replica button. The Reconfigure Replica notification popup will open.
- Click the Confirm button in the Reconfigure Replica notification popup.
Promoting Replica Cluster to Master
You can promote a configured replica cluster to a master cluster.
To promote a replica cluster to a master, follow these steps:
- Click All Services > Database > MariaDB(DBaaS). This will take you to the MariaDB(DBaaS) Service Home page.
- Click MariaDB(DBaaS) on the Service Home page. This will take you to the MariaDB(DBaaS) list page.
- Click the resource you want to promote to a master on the MariaDB(DBaaS) list page. This will take you to the MariaDB(DBaaS) details page.
- Click the More button and then click the Promote to Master button. The Promote to Master notification popup will open.
- Click the Confirm button in the Promote to Master notification popup.
3.3 - API Reference
3.4 - CLI Reference
3.5 - Release Note
MariaDB(DBaaS)
- MariaDB(DBaaS) feature added
- 2nd generation server type added
- Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see MariaDB(DBaaS) server type
- DB user and access control management and Archive setting function added
- For more information, see DB User Management, DB Access Control Management, Archive Management
- DB Audit Log Export feature added
- For more detailed information, please refer to DB Log Export
- Backup Notification Feature provided
- Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
- Migration feature added
- Provides a Migration function that replicates the database in the Samsung Cloud Platform environment in Replication mode. For more information, see Configuring Migration
- Block Storage type added HDD, HDD_KMS type
- Migration feature added
- MariaDB(DBaaS) feature change
- 2nd generation server type added
* Added 2nd generation (dbh2) server type based on Intel 4th generation (Sapphire Rapids) processor. For more information, see MariaDB(DBaaS) server type
- After creating a service, it is possible to increase the Block Storage capacity that has been set.
- The server-based network IP setting function has been added, allowing for common settings or server-based settings according to the purpose of use.
- Samsung Cloud Platform common feature changes
- Account, IAM and Service Home, tags, etc. reflected common CX changes.
- Block Storage type has an option to select encrypted storage for volume added
- A feature that can switch the role (Active ↔ Standby) of Active DB and Standby DB composed of duplication has been added.
- Cloud monitoring service is linked, so DB instance performance and log monitoring are possible.
- Depending on the server type selected by the customer, Planned Compute policy settings are possible.
- A MariaDB(DBaaS) service that can easily create and manage MariaDB in a web environment has been released.
4 - MySQL(DBaaS)
4.1 - Overview
Service Overview
MySQL(DBaaS) is an open source relational database management system (RDBMS). Samsung Cloud Platform provides an environment that can automate MySQL installation and perform management functions for operation through a web-based console.
MySQL(DBaaS) is designed as a high-availability architecture that performs storage-based data replication and minimizes failover time. To prevent data loss, when the content of the Active server changes, it is synchronously replicated to the Standby server, and up to five read-only servers called Replicas for read load balancing and disaster recovery (DR) are provided. Additionally, to prepare for issues with the DB server or data, it offers an automatic backup function at user-specified times, supporting data recovery at the desired point in time.
Provided Features
MySQL(DBaaS) provides the following features.
- Auto Provisioning (Auto Provisioning): Installation and configuration of Database (DB) is possible via UI, and it provides an Active-standby redundancy configuration based on storage replication. In case of an Active server failure, automatic failover to Standby occurs.
- Operation Control Management: Provides functionality to control the status of running servers. In addition to start and stop, restart is possible if there is a DB issue or to apply configuration values. When configured for high availability (HA), users can directly perform node switching between Active-Standby via Switch-over.
- Backup and Recovery: Provides a data backup function based on its own backup commands. The backup time window and storage agency can be set by the user, and additional fees are incurred based on backup size. It also provides a recovery function for backed-up data, creating a separate DB when the user performs a recovery, and the recovery proceeds to the point in time selected by the user (backup save point, user-specified point). When recovering to a user-specified point, the recovery point can be set up to 5 minutes/10 minutes/30 minutes/1 hour before the stored backup file and archive file.
- Version Management: Provides version upgrade (Minor) functionality for some feature improvements and security patches. Whether to perform a backup for the version upgrade can be selected by the user, and if a backup is performed, the data is backed up before applying the patch, then the DB engine is updated.
- Replica configuration: You can add up to 5 read-only Read Replicas, enabling read performance scaling and load balancing.
- Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
- Service Status Query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, DB performance monitoring information can be checked via the Cloud Monitoring service.
- DB User Management: View and manage 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.
- Archive Management: You can set the Archive file retention period (1 day~35 days) within the DB server and configure the Archive mode (On/Off).
- DB Log Export: You can export stored logs to the user’s Object Storage through Audit settings.
- Migration: Synchronize data in real time with the operating database, and support migration using the Replication method without service interruption.
Components
MySQL (DBaaS) provides pre-validated engine versions and various server types according to the open-source support policy. Users can select and use them according to the scale of the service they want to configure.
Engine Version
The engine versions supported by MySQL(DBaaS) are as follows.
Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
- MySQL (Community): https://www.mysql.com/support/eol-notice.html
| Service | Provided Version | EOS Date(Samsung Cloud Platform New Creation Stop Date) | EoTS Date(Community Technical Support End Date) |
|---|---|---|---|
| MySQL (Community) | 8.0.28 | 2026-03 (scheduled) | 2026-04-30 |
| 8.0.30 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.32 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.33 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.34 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.35 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.36 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.37 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.41 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.0.42 | 2026-03 (scheduled) | 2026-04-30 | |
| 8.4.5 | 2031-12 (planned) | 2032-04-30 |
Server Type
The server types supported by MySQL (DBaaS) are as follows.
For detailed information about the server types provided by MySQL(DBaaS), please refer to MySQL(DBaaS) Server Types.
Standard db1v2m4
Category
Example
Detailed Description
Server Type
Standard
Provided Server Types- Standard: Standard specifications (vCPU, Memory) configuration commonly used
- High Capacity: Large server specifications of 24 vCores or more
Server Specifications
db1
Provided Server Specifications- db1: Standard specifications (vCPU, Memory) configuration commonly used
- dbH2: Large-scale server specifications
- Provides servers with 24 vCores or more
Server specifications
v2
Number of vCores- v2: 2 virtual cores
Server specifications
m4
Memory capacity- m4: 4GB Memory
Table. MySQL(DBaaS) server type components
# Pre-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 for details and prepare in advance.<br>
Service Category
Service
Detailed Description
Networking
VPC
A service that provides an independent virtual network in a cloud environment
Table. MySQL (DBaaS) Pre-service
4.1.1 - Server Type
MySQL(DBaaS) Server Type
MySQL(DBaaS) provides server types with various combinations of CPU, Memory, and Network Bandwidth. When creating a MySQL(DBaaS), the database engine is installed according to the selected server type, which is chosen based on the intended use.
The server types supported by MySQL(DBaaS) are as follows:
Standard db1v2m4
Classification | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Classification of provided server types
|
| Server Specification | db1 | Classification of provided server types and generations
|
| Server Specification | v2 | Number of vCores
|
| Server Specification | m4 | Memory capacity
|
db1 Server Type
The db1 server type of MySQL(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
- Supports up to 16 vCPUs and 256 GB of memory
- Up to 12.5 Gbps networking speed
| Classification | 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 |
dbh2 Server Type
The dbh2 server type of MySQL(DBaaS) is provided with high-capacity server specifications and is suitable for large-scale data processing database workloads.
- Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
- Supports up to 128 vCPUs and 1,536 GB of memory
- Up to 25Gbps networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Up to 25 Gbps |
4.1.2 - Monitoring Metrics
MySQL(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics of MySQL (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
MySQL(DBaaS)’s server monitoring metrics, please refer to the Virtual Server Monitoring Metrics guide.
| Performance Item | Detailed Description | Unit |
|---|---|---|
| Active Locks | Active Locks count | cnt |
| Active Sessions | Active Session count | cnt |
| Binary Log Used [MB] | binary log usage | MB |
| Connection Usage [Total] | DB connection session usage rate | % |
| Connections | Connection count | cnt |
| Connections [MAX] | Connection count | cnt |
| Connections | max connected threads count | cnt |
| Data Directory Used [MB] | data directory usage | MB |
| Instance Status [PID] | mysqld process pid | pid |
| Open Files | Number of DB files in open state | cnt |
| Open Files [MAX] | number of DB files that can be opened | cnt |
| Open Files Usage | DB file maximum count usage rate | % |
| Relay Log Used [MB] | relay log usage (MB) | MB |
| Running Threads | running thread number | cnt |
| Safe PID | safe program pid | pid |
| Slave Behind Master seconds | time difference with master node | sec |
| Slowqueries | Number of SQL queries running for a long time (5 minutes or more) (by DB) | cnt |
| Slowqueries [Total] | Number of SQL queries running for a long time (5 minutes or more) (total) | cnt |
| Tablespace Used | Tablespace usage | MB |
| Tablespace Used [Total] | Tablespace total usage | MB |
| Transaction Time [Long] | Transaction longest execution time | sec |
| Wait Locks | Number of sessions blocked for 60 seconds or more by lock | cnt |
4.2 - How-to guides
Users can enter the required information for MySQL (DBaaS) through the Samsung Cloud Platform Console, select detailed options, and create the service.
Creating MySQL(DBaaS)
You can create and use the MySQL (DBaaS) service in the Samsung Cloud Platform Console.
- Please configure the VPC’s Subnet type as General before creating the service.
- If the Subnet type is Local, the creation of the corresponding Database service is not possible.
- If you load more than 2 TB of large-scale data, backups may take a long time or the DB’s performance may degrade. To prevent this, you need to consider operational aspects such as cleaning up unnecessary data or moving old data to a statistical collection environment.
To create MySQL(DBaaS), follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) 생성 button on the Service Home page. You will be taken to the MySQL(DBaaS) 생성 page.
- MySQL(DBaaS) Creation page, enter the information required to create the service and select detailed options.
- Select the required information in the Image and Version Selection area.
Category RequiredDetailed description Image version Required Provide version list of MySQL (DBaaS) Table. MySQL(DBaaS) image and version selection items - Service Information Input area, please enter or select the required information.
Category RequiredDetailed description Server Name Prefix Required Server name where DB will be installed - Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (
-) to input 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is attached to create the actual server name
Cluster Name Required Cluster name composed 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 where DB will be installed - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server of 24 vCore or more
- For detailed information about the server types provided by MySQL (DBaaS), refer to MySQL (DBaaS) Server Types
Service Type > Planned Compute Optional Status of resources with Planned Compute set - In Use: Number of resources with Planned Compute that are in use
- Configured: Number of resources with Planned Compute set
- Coverage preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Go to Planned Compute service application page
- See Apply for Planned Compute for details
Redundancy configuration Select Redundancy configuration status - If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
Network > Common Settings Required Network settings where servers created by the service are deployed - Select if you want to apply the same settings to all servers being installed
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be auto‑generated
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select from reserved IPs in the VPC product’s Public IP. For details, see Create Public IP.
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select if you want to apply different settings per installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter each server’s IP
- 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, see Create Public IP.
IP Access Control Select Service Access Policy Settings - Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
Maintenance Period Select DB Maintenance Period - Use: set day of week, start time, and duration
- It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption.
- If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
Table. MySQL(DBaaS) Service Configuration Items - Start with an English lowercase letter, and use lowercase letters, numbers, and the special character (
- Database configuration required information input Enter or select the required information in the area.
Category RequiredDetailed description Database name Required Server name applied when installing DB - Start with an English letter, use English letters and numbers, and enter 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 usernames can be checked in the Console
Database password Required Password to use when accessing the DB - Enter 8-30 characters including letters, numbers, and special characters (
“‘excluded)
Database Password Confirmation Required Re-enter the same password to be used when accessing the DB Database Port number Required Port number required for DB connection - Enter DB port within the range 1,024 ~ 65,535
Backup > Use Select Whether to use backup - Select Use to set backup file retention period, backup start time, Archive backup cycle
Backup > Retention Period Select Backup Retention Period - Select the backup retention period. File retention period can be set from 7 days to 35 days
- Backup files incur additional charges depending on size
Backup > Backup Start Period Select Backup Start Time - Select backup start time
- The minutes (minutes) at which the backup is performed are set randomly, and the backup end time cannot be set
Backup > Archive backup frequency Select Archive backup frequency - Select the Archive backup frequency
- Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Parameter Required Parameters to use in the DB - View button to click to view detailed information of the parameter
- Parameters can be modified after DB creation is completed, and after modification the DB must be restarted
DB character set Required Character encoding method to be used in the DB Table case sensitivity select DB Table case sensitivity status Time zone Required Standard time zone to be used by the Database Table. MySQL(DBaaS) Database configuration items - Enter additional information in the area, please enter or select the required information.
Category RequiredDetailed description Tag Select Add Tag - Up to 50 can be added per resource
- After clicking the Add Tag button, enter or select Key, Value values
Table. MySQL(DBaaS) Additional Information Input Items
- Select the required information in the Image and Version Selection area.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resource on the Resource List page.
MySQL(DBaaS) Check detailed information
The MySQL (DBaaS) service allows you to view and edit the full resource list and detailed information. The MySQL (DBaaS) Details page consists of Details, Tags, Activity History tabs, and for databases with a Replica configured, a Replica Information tab is additionally provided.
To view detailed information of the MySQL (DBaaS) service, follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. You will be taken to the MySQL(DBaaS) List page.
- Click the resource to view detailed information on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- MySQL(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
Category Detailed description Cluster Status Cluster status with DB installed - Creating: Cluster is being created
- Editing: Cluster is changing to operation execution state
- Error: Cluster encountered a failure while performing a task
- If it occurs continuously, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Cluster is being restarted
- Running: Cluster is operating normally
- Starting: Cluster is being started
- Stopped: Cluster is stopped
- Stopping: Cluster is being stopped
- Synchronizing: Cluster is being synchronized
- Terminating: Cluster is being deleted
- Unknown: Cluster status is unknown
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is changing to upgrade execution state
Cluster Control Button to change cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to Active
More additional features Cluster related management buttons - Service status synchronization: Real-time DB service status lookup
- Backup history: If backup is set, check whether backup runs normally and view history
- Database recovery: Recover DB based on a specific point in time
- Parameter management: DB configuration parameters can be queried and modified
- Replica configuration: Set up a read-only cluster called Replica
- DB user management: View and manage 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
- Archive management: Can set archive file retention period and archive mode
- DB Log export: Through audit settings, stored logs can be exported to the user’s Object Storage
- Migration configuration: Provides migration functionality using replication method
Service cancellation Button to cancel the service Table. MySQL(DBaaS) status information and additional features
Detailed Information
MySQL(DBaaS) List page allows you to view detailed information of the selected resource and, if needed, modify the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in the 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 |
| Creator | User who created the service |
| Creation time | Service creation time |
| Editor | User who modified the service information |
| Modification Date/Time | Date and time when service information was modified |
| Image/Version | Installed DB image and version information
|
| Cluster Type | Cluster Type (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster Name | Name of the cluster composed of DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied when installing DB |
| Database username | DB user name |
| Planned Compute | Resource status with Planned Compute set
|
| Maintenance Period | DB Maintenance Period Status
|
| Backup | Backup Settings Status
|
| Time zone | Standard time zone used by the Database |
| DB character set | Encoding method to use in DB |
| Table case sensitivity | DB Table case sensitivity status |
| VIP | Virtual IP information
|
| Network | Network information where DB is installed (VPC, Subnet, VIP, NAT IP(VIP)) |
| IP Access Control | Service Access Policy Settings
|
| 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 check the Master cluster name, number of replicas, and Replica status.
| Category | Detailed description |
|---|---|
| Master Information | Name of Master Cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status created in the Master cluster
|
Tag
MySQL(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
|
Work History
On the MySQL(DBaaS) List page, you can view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Work History List | Resource Change History
|
MySQL(DBaaS) Resource Management
If you need to change or restore the existing configuration options of a created MySQL (DBaaS) resource, or require a Replica configuration, you can perform the tasks on the MySQL (DBaaS) Details page.
Operating Control
If changes occur to the running MySQL (DBaaS) resources, you can start, stop, or restart them. Also, if HA is configured, you can switch the Active-Standby servers via a switch‑over.
To control the operation of MySQL (DBaaS), follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Go to the MySQL(DBaaS) List page.
- Click the resource to control operation on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Check the status of MySQL (DBaaS) and complete the change using the control button below.
- Start: The server where the DB service is installed and the DB service are running (Running).
- Stop: The server where the DB service is installed and the DB service 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 MySQL (DBaaS).
To check the service status of MySQL (DBaaS), follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. Navigate to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Go to the MySQL(DBaaS) List page. 3. MySQL(DBaaS) List Click the resource to view the service status. MySQL(DBaaS) Detail Navigate to the page.
- Service status synchronization button. Click the button. While fetching, 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 the steps below.
- If you modify the server type, a server reboot is required. Please separately verify any SW license changes or SW settings and their application due to spec changes.
- All Services > Database > MySQL(DBaaS) Click the menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Go to the MySQL(DBaaS) List page.
- Click the resource to change the server type on the MySQL(DBaaS) 목록 page. It will move to the MySQL(DBaaS) 상세 page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Server Type Edit popup window will open.
- Server Type Edit In the popup window, after selecting the server type, click the Confirm button.
Add Storage
If you need more than 5 TB of data storage space, you can add storage. In the case of a redundant DB configuration, all redundant servers are added simultaneously.
- It is applied the same way as the selected Storage type when creating a service.
- If a DB is configured for high availability, adding storage will be applied simultaneously to the storage of the Active DB and the Standby DB.
- If a Replica exists, the storage of the Master cluster cannot be larger than the storage of the Replica. Please expand the Replica storage first, then expand the Master cluster storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable
To add storage, follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Navigate to the MySQL(DBaaS) List page.
- On the MySQL(DBaaS) List page, click the resource to add storage. It navigates to the MySQL(DBaaS) Details page.
- Click the Add Disk button at the bottom of the detailed information. The Add Storage Request popup window opens.
- Additional Storage Request After entering purpose and capacity in the popup window, click the Confirm button.
Expanding storage
The storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. Navigate to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. Navigate to the MySQL(DBaaS) list page.
- Click the resource to change the server type on the MySQL(DBaaS) List page. You will be taken to the MySQL(DBaaS) Details page.
- Click the Edit icon of the additional Disk you want to expand at the bottom of the detailed information. The Edit Additional Storage popup window opens.
- Add Storage Modification In the popup window, after entering the expansion capacity, click the Confirm button.
MySQL(DBaaS) Cancel
You can cancel unused MySQL (DBaaS) to reduce operating costs. However, if you cancel the service, the running service may be stopped immediately, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.
- In the case of a DB with a Replica configured, even if you terminate the Master DB, the Replica is not deleted together. If you also want to delete the Replica, please terminate it separately from the resource list.
- If you cancel the DB, any stored data and, if backup is set, all backup data will be deleted.
To cancel MySQL (DBaaS), follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. Go to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. You will be taken to the MySQL(DBaaS) List page.
- MySQL(DBaaS) List On the page, select the resource to cancel, and click the Cancel Service button.
- When the termination is complete, check whether the resource has been terminated on the MySQL (DBaaS) list page.
4.2.1 - MySQL(DBaaS) server connection
Scenario Overview
The MySQL(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and Database service are created, and the DB service is accessed through the Bastion host. To connect to MySQL(DBaaS) stably in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.
This scenario largely describes the process of creating a Bastion host and Database service, and configuring the network environment for Bastion host and Database connection, so that it can be accessed through a DB connection client.
Scenario Components
You can configure 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 allows users to subdivide the network into smaller sections for specific purposes/sizes within the VPC | |
| Networking | VPC > Public IP | A service that reserves a public IP and assigns and returns it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the internet | |
| Networking | Security Group | A virtual firewall that controls the server’s traffic | |
| Database | MySQL(DBaaS) | A service that easily creates and manages MySQL in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to Virtual Server |
Scenario composition method
To configure the scenario, create the necessary services through the following procedure.
1. Configuring the Network
This explains the process of configuring the network environment for Bastion Host and Database service connection.
1-1. Creating a VPC
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
- VPC Creation page, please enter the information needed to create the service.
- IP range should be entered as
192.168.x.0/16.
- IP range should be entered as
- In the Summary panel, review the detailed information and estimated charge, then click the Complete button.
- Once the creation is complete, check the created resource on the VPC list page.
1-2. Creating a Subnet
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Subnet menu. It moves to the Subnet list page.
- Click the Subnet Creation button. It moves to the Subnet Creation page.
- Subnet creation page where you enter the information needed to create a service.
- Subnet type should be selected as General.
- Please select a pre-created VPC.
- IP range should be entered as
192.168.x.0/24.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- After creation is complete, check the created resource on the Subnet list page.
1-3. Creating an Internet Gateway
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Internet Gateway menu. It moves to the Internet Gateway list page.
- Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
- Internet Gateway creation page, please enter the required information necessary for service creation.
- Please select a pre-created VPC.
- Select use in the Firewall usage item.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- Once the creation is complete, check the created resource on the Internet Gateway list page.
1-4. Creating a Public IP
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Click the Public IP menu on the Service Home page. It moves to the Public IP list page.
- Public IP Reservation button, click. Move to the Public IP Reservation page.
- Public IP Reservation page where you enter the required information necessary for service reservation.
- Check the detailed information generated in the Summary panel and the expected bill amount, and click the Complete button.
- After creation is complete, check the created resource on the Public IP List page.
1-5. Creating a Security Group
- Click the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
- Click the Security Group Creation button on the Service Home page. It moves to the Security Group Creation page.
- Security Group creation page where you enter the required information necessary for service creation.
- Check the input information and click the Complete button.
- Once creation is complete, check the created resource on the Security Group list page
2. Creating a Bastion Host
This describes the process of configuring the Bastion Host where the database connection client should be installed.
2-1. Creating a Server Keypair
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Click the Keypair menu on the Service Home page. It moves to the Keypair list page.
- Keypair creation button should be clicked. It moves to the Keypair creation page.
- Keypair creation page, please enter the required information necessary for service creation.
- Check the creation information and click the Complete button.
- The key can only be downloaded for the first time, and re-issuance is not provided.
- Please keep the downloaded key in a safe place.
2-2. Creating a Bastion Host
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Click the Virtual Server Creation button on the Service Home page. It moves to the Virtual Server Creation page.
- Virtual Server Creation page, please enter the required information necessary for service creation.
- The image is Windows, please select.
- Please select the pre-created VPC and Subnet.
- Click NAT Use and select the Public IP reserved in 1-4. Creating Public IP.
- 2-1. Creating a server Keypair Connect the Keypair created from
- Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
- Once creation is complete, check the created resource on the Virtual Server list page.
2-3. Check Bastion host connection ID and PW
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
- Virtual Serve list page, click on the resource created in 2-2. Creating a Bastion host. It moves to the detailed information page of the corresponding resource.
- Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window opens.
- RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Creating a server keypair.
- After attaching, click the Password Check button. The ID and password required to access the resource will be displayed.
- The ID and Password will be used as information to access the Bastion host later in 5-1. Bastion host 접속하기.
3. Creating a Database
It describes the process of creating a database service.
3-1. Creating a MySQL (DBaaS) Service
- Click on the menu for all services > Database > MySQL(DBaaS). It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the Create MySQL(DBaaS) button. It moves to the Create MySQL(DBaaS) page.
- MySQL(DBaaS) creation page, please enter the required information needed for service creation.
- Select and connect the pre-created VPC and Subnet.
- Enter database-related creation information on the required information input screen.
- Add the Bastion host IP to the IP access control item.
- Database Port is 2866 by default, but you can specify it as you want.
- In the Summary panel, review the detailed information and estimated charges, then click the Complete button.
- Once the creation is complete, check the created resource on the MySQL(DBaaS) list page.
4. Setting Rules
This explains the process of setting rules for users to access the Bastion host and rules for the Bastion host to access the Database.
4-1. Adding Security Group Security Rules
- Click the menu for all services > Networking > Security Group. It moves to the Service Home page of Security Group.
- Service Home page, click the Security Group menu. Move to the Security Group list page.
- 1-5. Creating a Security Group Select the Security Group resource created from. It will move to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule popup window, enter the rules below, and click the OK button
| Direction | Remote | Destination Address | Protocol | Port | Description |
|---|---|---|---|---|---|
| Inbound | CIDR | User PC IP | TCP | 3389 (RDP) | Bastion connection PC → Bastion host |
| Outbound | CIDR | DB IP | TCP | Database Port (direct input) | Bastion host → Database |
4-2. Adding IGW Firewall Rules
- Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
- Service Home page, click the Firewall menu. It moves to the Firewall list page.
- Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway, and move to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Click the Rule tab and click the Add Rule button. It moves to the Add Rule popup window.
- Add Rule In the popup window, enter the rules below and click the OK button.
| Departure Address | Destination Address | Protocol | Port | Action | Direction | Description |
|---|---|---|---|---|---|---|
| Bastion connection PC IP | Bastion host IP | TCP | 3389(RDP) | Allow | Inbound | User PC → Bastion host |
| Fig. Internet Gateway Firewall rules to be added |
5. Connect to Database
This describes the process of a user accessing the Database through a DB connection client program.
This guide provides instructions on how to connect using MySQL Workbench. There are various database client programs and CLI utilities, so you can install and use the tools that suit you.
5-1. Connecting to the Bastion host
- Run Remote Desktop Connection in the Windows environment of the PC you want to access the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
- After a successful remote desktop connection, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Checking Bastion Host Access ID and PW and click the Confirm button.
5-2. Install DB connection client program (MySQL Workbench) on the Bastion host
- Go to the official MySQL page and download the MySQL Workbench program.
- MySQL Workbench program download path: https://dev.mysql.com/downloads/workbench
- Connect the hard drive of the user’s PC to upload the file to the Bastion host.
- Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
- Select the local disk where the file was downloaded to the drive and click the Confirm button.
- Copy the downloaded file and upload it to the Bastion Host, then click the MySQL Workbench installation file to install it.
5-3. Using DB connection client program (MySQL Workbench) to connect to the Database
- Run MySQL Workbench and click Database > Manage connections. The Manage Server Connection popup window will appear.
- Manage Server Connection popup window, click the New button at the bottom left and enter the database server information created in 3-1. MySQL(DBaaS) service creation, then click the Test Connection button. A Password popup window will appear.
Required Input Element Items Input Value Connection Name Custom (ex. Service Name) Host name Database server IP Port Database Port Username Database username DB connection client program input items - Password popup window, enter the password set in 3-1. MySQL(DBaaS) service creation and click the OK button. When the success is complete, click the OK button in the Manage Server Connection popup window.
- Database > Connect to Database should be clicked. The Connect to Database popup window will appear.
- Select the Connection Name registered in Stored Connection to perform database connection. After connection, you can try simple queries, etc.
4.2.2 - Managing DB Services
Users can manage MySQL (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
It provides a feature to easily view and modify database configuration parameters.
Viewing Parameters
To view configuration parameters, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to view and modify parameters on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
Modifying Parameters
To modify configuration parameters, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to view and modify parameters on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
- If modification is necessary, click the Modify button and enter the modification contents in the user-defined value area of the parameter to be modified.
- When the input is complete, click the Save button.
Managing DB Users
It provides a management feature that allows you to view DB user information and change status information.
Viewing DB Users
To view DB users, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to view DB users on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB User Management button. It moves to the DB User Management page.
- Click the View button on the DB User Management page. It takes some time to view.
Changing DB User Status
To change the status of the viewed DB user, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to modify DB users on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB User Management button. It moves to the DB User Management page.
- Click the View button on the DB User Management page. It takes some time to view.
- If modification is necessary, click the Modify button and change the status area value or enter remarks.
- When the input is complete, click the Save button.
Managing DB Access Control
It provides an IP-based DB user access control management feature. Users can directly specify the IP that can access the database, allowing only allowed IPs to access.
Viewing DB Access Control
To view DB users with IP access control set, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to manage access control on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
- Click the View button on the DB Access Control Management page. It takes some time to view.
Adding DB Access Control
To add IP access control, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource you want to add IP access control on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the DB Access Control Management button. It moves to the DB Access Control Management page.
- Click the View button on the DB Access Control Management page. It takes some time to view.
- When the view is complete, click the Add button. The DB Access Control Add popup window opens.
- In the DB Access Control Add popup window, select the DB user name and enter the IP address.
- When the input is complete, click the Save button.
Deleting DB Access Control
To delete IP access control, follow these steps:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- Click the resource for which you want to delete IP access control on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
- Click the More button and then click the DB Access Control Management button. The DB Access Control Management page will be displayed.
- Click the Inquiry button on the DB Access Control Management page. It may take some time to retrieve the data.
- Once the inquiry is complete, click the Delete button. A Delete pop-up window will appear.
- Click the Confirm button in the Delete pop-up window.
Managing Archive
The Archive mode setting and Archive Log retention period setting functions are provided, allowing users to flexibly set the Archive log management policy according to their operating environment. Additionally, the function to manually delete Archive logs is provided together, allowing users to clean up unnecessary log data and effectively manage system resources.
Setting Archive Mode
To set the Archive mode, follow these steps:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- Click the resource for which you want to set the Archive mode on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
- Click the More button and then click the Archive Settings Management button. The Archive Settings Management page will be displayed.
- Click the Inquiry button on the Archive Settings Management page. It may take some time to retrieve the data.
- Click the Modify button and select the usage and retention period.
- Once the modification is complete, click the Save button.
Deleting Archive Files
To delete Archive files, follow these steps:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- Click the resource for which you want to set the Archive mode on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
- Click the More button and then click the Archive Settings Management button. The Archive Settings Management page will be displayed.
- Click the Archive All Delete button to delete all Archive files, or click the Backup Archive Delete button to delete only the backed-up Archive files.
Exporting DB Logs
The function to export audit logs to Object Storage is supported, allowing users to set the log type, target bucket, and export cycle. According to the set criteria, the logs are copied to the specified Object Storage for storage. Additionally, an option to automatically delete the original log files when exporting logs to Object Storage is provided, allowing users to effectively secure storage capacity while safely storing necessary log data.
- To use the DB Log export function, Object Storage creation is required. Refer to the Object Storage user guide for Object Storage creation.
- Be sure to check the expiration date of the authentication key. If the authentication key expires, the log will not be stored in the bucket.
- Be careful not to expose the authentication key information to the outside.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- Click the resource for which you want to export DB logs on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
- Click the More button and then click the DB Log Export button. The DB Log Export page will be displayed.
- Click the Register button on the DB Log Export page. The DB Log Export Registration page will be displayed.
- Enter the required information on the DB Log Export Registration page and click the Save button.
| Category | Required | Detailed Description |
|---|---|---|
| Log Type | Required | Log type to be stored |
| Storage Bucket Name | Required | Object Storage bucket name to store the log |
| Authentication Key > Access Key | Required | Access key to access the Object Storage |
| Authentication Key > Secret Key | Required | Secret key to access the Object Storage |
| File Creation Cycle | Required | Cycle to create files in Object Storage |
| Original Log Deletion | Optional | Whether to delete the original log when exporting to Object Storage |
Managing DB Log Export
To modify, cancel, or immediately export DB log settings, follow these steps:
- Click All Services > Database > MySQL(DBaaS) menu. The MySQL(DBaaS) Service Home page will be displayed.
- Click the MySQL(DBaaS) menu on the Service Home page. The MySQL(DBaaS) list page will be displayed.
- Click the resource for which you want to manage DB log export on the MySQL(DBaaS) list page. The MySQL(DBaaS) details page will be displayed.
- Click the More button and then click the DB Log Export button. The DB Log Export page will be displayed.
- Click the More button for the log type you want to manage on the DB Log Export page, and then click the Immediate Export, Modify, or Cancel button.
- Immediate Export: Exports the selected log to the Object Storage bucket.
- Modify: Modifies the DB log export mode setting.
- Cancel: Cancels the DB log export mode setting.
Upgrading DB Version
The function to upgrade the version for some feature improvements and security patches is provided. Only minor version upgrades are supported within the same major version.
- Please perform a service status synchronization to check the service status before upgrading the version.
- Please set up a backup before upgrading the version. If you do not set up a backup, you may not be able to recover some data in case of problems during the update.
- In the case of a DB with a replica configured, the master DB version must be higher than or equal to the replica version. Please check the replica version first and perform a version upgrade if necessary.
- The backed-up data will be automatically deleted after the version upgrade is complete.
To upgrade the version, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource to be upgraded on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the Modify button in the image/version item. The Version Upgrade popup window opens.
- In the Version Upgrade popup window, select the version to be modified and the backup setting, and then click the OK button.
- Click the OK button in the Version Upgrade Notification popup window.
Configuring Migration
It provides a migration function that synchronizes with the operating database in real-time and replicates in a replication manner without interrupting the service.
To configure the migration, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource to be migrated on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the Configure Migration button. The Configure Migration popup window opens.
- In the Configure Migration popup window, check the instructions and click the OK button. It moves to the Configure Migration page.
- On the Configure Migration page, enter the corresponding information and click the Connect Check button.
- When the connection is complete, click the Complete button.
| Classification | Required | Detailed Description |
|---|---|---|
| Source DB Database Name | Required | Database name of the source DB that is the migration target |
| Source DB IP | Required | IP of the source DB that is the migration target |
| Source DB Port | Required | Port of the source DB that is the migration target |
| Source DB User Name | Required | User name of the source DB that is the migration target |
| Source DB Password | Required | Password of the source DB that is the migration target |
The configured migration cluster can be promoted to a master cluster.
To promote the migration cluster to a master, follow these steps:
- Click the All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Click the MySQL(DBaaS) menu on the Service Home page. It moves to the MySQL(DBaaS) List page.
- Click the resource to be promoted to a master on the MySQL(DBaaS) List page. It moves to the MySQL(DBaaS) Details page.
- Click the More button and then click the Promote to Master button. The Master Promotion Notification popup window opens.
- Click the OK button in the Master Promotion Notification popup window.
4.2.3 - DB Backup and Recovery
The user can set up a backup of MySQL(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.
MySQL(DBaaS) Backup
PostgreSQL(DBaaS) provides a data backup feature based on its own backup command. It also provides an optimized backup environment for data protection and management through backup history checking and backup file deletion functions.
Setting up backup
The method of setting up a backup for MySQL(DBaaS) is described in MySQL(DBaaS) creation guide.
To modify the backup settings of the generated resource, follow these steps.
- For stable backup, it is recommended to add a separate BACKUP storage or to sufficiently expand the storage capacity. Especially when the backup target data exceeds 100 GB and the data change is frequent, please secure additional storage equivalent to about 60% of the data capacity. For storage addition and expansion methods, please refer to the MySQL(DBaaS) Add Storage, MySQL(DBaaS) Expand Storage guides. If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
- If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.
To set up backup, follow these steps.
- All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
- Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
- MySQL(DBaaS) list page, click the resource to set the backup. It moves to the MySQL(DBaaS) details page.
- Click the Edit button of the backup item. The Backup Settings popup window opens.
- If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the Confirm button.
- If you want to stop the backup settings, uncheck Use in the Backup Settings popup window and click the OK button.
Check Backup History
To view the backup history, follow these steps.
- All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
- MySQL(DBaaS) list page, click the resource to check the backup history. Move to the MySQL(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.
Delete backup files
To delete the backup history, follow these steps.
- Click All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
- MySQL(DBaaS) list page, click the resource to check the backup history. Move to the MySQL(DBaaS) detail page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window, check the file you want to delete, and then click the Delete button.
Recovering MySQL(DBaaS)
In the event of a failure or data loss that requires restoration from a backup file, recovery is possible based on a specific point in time through the recovery function. When performing MySQL (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, the DB is installed with the version at the backup point in time, and the recovery proceeds with the DB configuration information and data.
To restore MySQL(DBaaS), follow these steps.
- All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
- MySQL(DBaaS) resource list page, click the resource you want to restore. It moves to the MySQL(DBaaS) details page.
- Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
- Enter the corresponding information in the Database Recovery Configuration area, and then click the Complete button.
| Classification | Necessity | Detailed Description |
|---|---|---|
| Recovery Type | Required | Set the point in time you want to recover
|
| Server name prefix | Required | Server name of the recovery DB
|
| Cluster Name | Required | Cluster name of the recovery DB
|
| Service Type > Server Type | Required | Server type where the recovery DB will be installed
|
| Service Type > Planned Compute | Selection | Current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Recovery DB uses Block Storage settings
|
| Database username | required | Database username set in the original DB |
| Database Port number | required | Database Port number set in the original DB |
| IP Access Control | Select | IP address to access the recovery DB
|
| Maintenance period | Select | DB maintenance period
|
| tag | selection | add tag
|
4.2.4 - Setting up Read Replica
The user can enter the necessary information for the Read Replica through the Samsung Cloud Platform Console and create the service through detailed options.
Configuring Replica
You can create a read-only replica server through Replica configuration. Up to 5 Replicas can be created per Database.
To configure a replica, follow these procedures.
- All services > Database > MySQL(DBaaS) menu, click. It moves to the Service Home page of MySQL(DBaaS).
- Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
- MySQL(DBaaS) list page, click on the resource to configure the Replica. Move to the MySQL(DBaaS) details page.
- Click the Replica Configuration button. It moves to the Replica Configuration page.
- Enter information in the Replica Configuration area, then click the Complete button.
Classification NecessityDetailed Description Number of Replicas Required Number of Replicas to configure - Up to 5 can be configured per cluster
- If selecting 2 or more values, additional input of Replica name and service type information is required
Replica name required Replica server name - Starts with lowercase English letters, using lowercase letters, numbers, and special characters (
-) to input 3 ~ 19 characters
- The entered Replica name is exposed as the cluster name in the list
Service Type > Server Type Required Replica Server Type - Standard: Standard specification commonly used
- High Capacity: High-capacity server with 24vCore or more
Service Type > Planned Compute Select Current status of resources with Planned Compute set - In Use: Number of resources with Planned Compute set that are in use
- Settings: Number of resources with Planned Compute set
- Coverage Preview: Amount applied by Planned Compute for each resource
- Create Planned Compute Service: Move to the Planned Compute service application page
- For more information, refer to Apply for Planned Compute
IP Access Control Select Set service access policy - Set access policy for IP entered on the page, so separate Security Group policy setting is not required
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32), and click the Add button
- To delete the entered IP, click the x button next to the entered IP
Maintenance period Select DB maintenance period - Use is selected, set the day of the week, start time, and duration
- It is recommended to set the maintenance period for stable management of the DB. Patch work is performed at the set time and service interruption occurs
- If set to not used, the company is not responsible for the problems that occur due to non-application of patches.
tag selection add tag - add tag button click after Key, Value value input or selection
Table. MySQL(DBaaS) Replica Configuration Items
Replica reconstruction
In the event of a network failure or replication delay with the Master Cluster, the Replica reconstruction function can be used to re-replicate the Master Cluster’s data.
To reassemble the replica, follow the procedure below.
- Click All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
- Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
- Click on the resource to be reconstructed as a replica on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
- Replica Reconstruction 버튼을 클릭하세요. Replica Reconstruction Notification 팝업창이 열립니다.
- Replica Reconstruction Alert popup window, click the Confirm button.
Promote Replica Cluster to Master Cluster
You can promote a fully configured Replica Cluster to a Master Cluster.
To promote the Replica Cluster to Master, follow these steps.
- All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
- Click the resource to be promoted to Master on the MySQL(DBaaS) list page. It moves to the MySQL(DBaaS) details page.
- Click the More button and click the Master Promotion button. The Master Promotion Notification popup window opens.
- In the Master Promotion Alert popup window, click the OK button.
4.3 - API Reference
4.4 - CLI Reference
4.5 - Release Note
MySQL(DBaaS)
- MySQL(DBaaS) feature added
- 2nd generation server type added
- Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see MySQL(DBaaS) server type
- DB user and access control management and Archive setting function added
- For more detailed information, please refer to DB User Management, DB Access Control Management, Archive Management
- DB Audit Log Export feature added
- For more information, see Exporting DB Log
- Backup Notification Feature provided
- Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
- Migration feature added
- Provides replication-based zero-downtime data migration feature. For more information, see Migration 구성하기
- Block Storage type added HDD, HDD_KMS type
- Migration feature added
- MySQL(DBaaS) feature change
- 2nd generation server type added
- Added 2nd generation (dbh2) server type based on Intel 4th generation (Sapphire Rapids) processor. For more information, see mysql(DBaaS) server type
- After creating a service, it is possible to increase the Block Storage capacity that has been set.
- Server-specific network IP setting feature has been added, allowing for common settings or server-specific settings depending on the purpose of use.
- 2nd generation server type added
- Samsung Cloud Platform common feature changes
- Account, IAM and Service Home, tags, etc. reflected common CX changes.
- A MySQL(DBaaS) service that allows you to easily create and manage MariaDB in a web environment has been released.
5 - Microsoft SQL Server(DBaaS)
5.1 - Overview
Service Overview
Microsoft SQL Server (DBaaS) is a representative relational database management system (RDBMS) used in various applications. Samsung Cloud Platform provides an environment that can automate the installation of Microsoft SQL Server through a web-based console and perform management functions for operation.
Microsoft SQL Server(DBaaS) is designed with an Always On based availability architecture, and when the content of the Primary server changes, it is synchronously replicated to the Secondary server. Additionally, it provides an automatic backup function at user-specified times to prepare for issues with the DB server or data, supporting data recovery at the desired point in time.
Provided Features
Microsoft SQL Server(DBaaS) provides the following features.
- Auto Provisioning: Allows installation and configuration of Database (DB) via UI, provides a Primary-Secondary redundancy configuration built on Always On. In case of Primary server failure, it automatically fails over to Secondary.
- Operation Control Management: Provides a function to control the status of running servers. In addition to start and stop, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), the user can directly perform node switching between Primary-Secondary via Switch-over.
- Backup and Recovery: Provides data backup functionality based on its own backup commands. Backup time windows, retention agencies, and full backup days can be set by the user, and additional fees may apply based on backup volume. It also provides a recovery function for backed-up data, creating a separate database when the user performs a recovery, and the recovery proceeds to the point in time selected by the user (backup storage point, user-specified point). When restoring to a user-specified point, the restore point can be set to 5 minutes/10 minutes/30 minutes/1 hour before the stored backup file and archive file.
- Version Management: Provides version upgrade (Minor) functionality due to some feature improvements and security patches. Whether to perform backup for the version upgrade can be selected by the user, and if backup is performed, data is backed up before applying the patch, then the DB engine is updated.
- Secondary configuration: You can additionally configure a read-only Read Replica (Secondary Replica), enabling read performance scaling and load balancing.
- Audit setting: Provides an Audit setting feature that can monitor the user’s DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) execution.
- Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
- Service status query: Retrieves the final status of the current DB service.
- Monitoring: CPU, Memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
- DB User Management: View and manage DB account (user) information registered in the DB.
- DB Log Export: Through Audit settings, you can export the stored logs to the user’s Object Storage.
Components
Microsoft SQL Server(DBaaS) provides pre-validated engine versions and various server types. Users can select and use them according to the scale of the service they want to configure.
Engine Version
The engine versions supported by Microsoft SQL Server (DBaaS) are as follows.
Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.
According to the supplier’s policy, the EOS and EoTS dates may change, so please refer to the supplier’s license management policy page for details.
- Microsoft SQL Server: https://learn.microsoft.com/ko-kr/lifecycle/products/?terms=sql%20server
| Provided version | EOS Date(Samsung Cloud Platform New creation stop date) | EoTS Date(Community Technical support end date) |
|---|---|---|
| Microsoft SQL Server 2019 Enterprise | 2029-06 (Planned) | 2030-01-08(Extended Support) 2025-02-28(Standard Support) |
| Microsoft SQL Server 2019 Standard | 2029-06 (planned) | 2030-01-08(Extended Support) 2025-02-28(Standard Support) |
| Microsoft SQL Server 2022 Enterprise | 2032-06 (planned) | 2033-01-11(Extended Support) 2028-01-11(Standard Support) |
| Microsoft SQL Server 2022 Standard | 2032-06 (planned) | 2033-01-11(Extended Support) 2028-01-11(Standard Support) |
Server Type
Microsoft SQL Server(DBaaS) supported server types are as follows.
For detailed information about the server types provided by Microsoft SQL Server(DBaaS), refer to Microsoft SQL Server(DBaaS) Server Type.
Standard db1v2m4
| Category | Example | Detailed description |
|---|---|---|
| Server Type | Standard | Provided Server Types
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
Preliminary Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service for details and prepare in advance.
| Service Category | Service | Detailed Description |
|---|---|---|
| Networking | VPC | A service that provides an independent virtual network in a cloud environment |
5.1.1 - Server Type
Microsoft SQL Server(DBaaS) server type
Microsoft SQL Server(DBaaS) provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth, etc. When creating Microsoft SQL Server (DBaaS), the Database Engine is installed according to the server type selected for the purpose of use.
The server types supported by Microsoft SQL Server (DBaaS) are as follows.
Standard db1v2m4
Classification | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Provided server type distinction
|
| Server Specifications | db1 | Classification of provided server type and generation
|
| Server Specification | v2 | Number of vCores
|
| Server Specification | m4 | Memory Capacity
|
db1 server type
The db1 server type of Microsoft SQL Server (DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
- Supports up to 16 vCPUs and 256 GB of memory
- Up to 12.5 Gbps networking speed
| Classification | 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 Microsoft SQL Server(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
- Supports up to 16 vCPUs and 256 GB of memory
- Up to 12.5 Gbps networking speed
| Classification | 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 Microsoft SQL Server (DBaaS) is provided with large-capacity server specifications and is suitable for database workloads for large-scale data processing.
- Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
- Supports up to 128 vCPUs and 1,536 GB of memory
- up to 25Gbps of networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| High Capacity | dbh2v24m48 | 24 vCore | 48 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m96 | 24 vCore | 96 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m192 | 24 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v24m288 | 24 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m64 | 32 vCore | 64 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m128 | 32 vCore | 128 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m256 | 32 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v32m384 | 32 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m192 | 48 vCore | 192 GB | Up to 25 Gbps |
| High Capacity | dbh2v48m576 | 48 vCore | 576 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m256 | 64 vCore | 256 GB | Up to 25 Gbps |
| High Capacity | dbh2v64m768 | 64 vCore | 768 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m288 | 72 vCore | 288 GB | Up to 25 Gbps |
| High Capacity | dbh2v72m864 | 72 vCore | 864 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m384 | 96 vCore | 384 GB | Up to 25 Gbps |
| High Capacity | dbh2v96m1152 | 96 vCore | 1152 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m512 | 128 vCore | 512 GB | Up to 25 Gbps |
| High Capacity | dbh2v128m1536 | 128 vCore | 1536 GB | Up to 25 Gbps |
5.1.2 - Monitoring Metrics
Microsoft SQL Server(DBaaS) Monitoring Metrics
The following table shows the performance monitoring metrics of Microsoft SQL Server(DBaaS) that can be checked through Cloud Monitoring. For detailed usage of Cloud Monitoring, please refer to the Cloud Monitoring guide.
For server monitoring metrics of Microsoft SQL Server(DBaaS), please refer to the Virtual Server monitoring metrics guide.
| Performance Item | Detailed Description | Unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Sessions | Number of Active Sessions | cnt |
| Active Transactions [Total] | Number of active transactions | cnt |
| Blocking Session ID | Long-running query (slow query) | ID |
| Connected Users | Number of users connected to the system | cnt |
| Datavolume Size [Free] | Available space | bytes |
| DBFiles [Not Online] | Query to check if all data files are ONLINE | cnt |
| Instance State [Cluster] | State when configuring MSSQL cluster | state |
| Instance State [PID] | sqlservr.exe process pid | PID |
| Lock Processes [Blocked] | Number of SQL processes blocked by other processes | cnt |
| Lock Waits [Per Second] | Average number of lock waits per second | cnt |
| Page IO Latch Wait Time | Average wait time for Page IO latch waits | ms |
| Slowqueries | Long-running query (slow query) | cnt |
| Slowquery CPU Time | Long-running query (slow query) | ms |
| Slowquery Execute Context ID | Long-running query (slow query) | ID |
| Slowquery Memory Usage | Long-running query (slow query) | bytes |
| Slowquery Session ID | Long-running query (slow query) | ID |
| Slowquery Wait Duration Time | Long-running query (slow query) | ms |
| Tablespace Used | Datavolume size | bytes |
| Transaction Time [MAX] | Long-running transaction | cnt |
5.2 - How-to guides
Users can enter the required information for Microsoft SQL Server (DBaaS) through the Samsung Cloud Platform Console, select detailed options, and create the service.
Creating Microsoft SQL Server(DBaaS)
You can create and use the Microsoft SQL Server (DBaaS) service from the Samsung Cloud Platform Console.
Before creating the service, please configure the VPC’s Subnet type as General.
- If the Subnet type is Local, the creation of the corresponding Database service is not possible.
Microsoft SQL Server (DBaaS)를 생성하려면 다음 절차를 따르세요.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- Click the Microsoft SQL Server(DBaaS) Create button on the Service Home page. You will be taken to the Microsoft SQL Server(DBaaS) Create page.
- Microsoft SQL Server(DBaaS) creation On the page, enter the information required to create the service, and select detailed options.
- Select image and version area, select the required information.
Category RequiredDetailed description Image version Required Provide version list of Microsoft SQL Server (DBaaS) Table. Microsoft SQL Server (DBaaS) image and version selection items - Service Information Input area, enter or select the required information.
Category RequiredDetailed description Server Name Prefix Required Server name where DB will be installed - Start with a lowercase English letter, and use lowercase letters, numbers, and the special character (
-) to input 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is attached to create 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 where DB will be installed - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server with 24 vCore or more
- For detailed information about server types provided by Microsoft SQL Server (DBaaS), refer to Microsoft SQL Server(DBaaS) Server Types
Service Type > Planned Compute Select Resource status with Planned Compute set - In Use: Number of resources with Planned Compute set that are currently in use
- Configured: Number of resources with Planned Compute set
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Move to Planned Compute service application page
- Refer to Apply for Planned Compute for details
Redundancy Configuration Selection Redundancy Configuration Status - If redundancy configuration is used, the DB instance is configured as Active DB and Standby DB
Network > Common Settings Required Network settings where servers generated by the service are deployed - Select if you want to apply the same settings to all servers being installed
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- IP can only be auto‑generated
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If Use is checked, you can select from reserved IPs in the VPC product’s Public IP. For details, see Create Public IP
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select if you want to apply different settings per installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter each server’s IP
- 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 information, see Creating a Public IP.
IP Access Control Select Service Access Policy Settings - Since the access policy is set for the IP entered on the page, a separate Security Group policy setting is not required.
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the entered IP
Maintenance Period Select DB Maintenance Period - Use is selected, set the day of the week, start time, and duration
- It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption
- If set to not use, Samsung SDS is not responsible for issues arising from patches not being applied
Table. Microsoft SQL Server (DBaaS) Service Configuration Items - Start with a lowercase English letter, and use lowercase letters, numbers, and the special character (
- Select image and version area, select the required information.
- Database Configuration Required Information Input In the area, please enter or select the required information.
Category RequiredDetailed description Database service name required Database management unit name - Start with an uppercase English letter and use English letters to input 1 - 15
Database name > default required Server name applied when installing DB - Start with an English letter, and use English letters, numbers, and special characters (
.,_) to input 3-20 characters
Database name > Add Required Server name applied when installing DB - Select Use, then enter the name of the Database to install. It must start with an English letter, and be 3-20 characters using English letters, numbers, and special characters(
.,_)
- For each Database, the drive where data is stored can be selected from the drives added in Service Type > Block Storage
- Adding Databases is only possible in the Enterprise version, up to a maximum of 100
Database username Required DB user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- The following names cannot be used as a Database username
- root, user, sdscmpif, hacluster, adm, games, nobody, sshd, system, mail, postfix, sa, maxigent_cl
Database password Required DB connection password - Enter 8-30 characters including letters, numbers, and special characters (excluding “ ‘)
Database Password Verification Required Check DB connection password - Re-enter the DB connection password identically
Database Port number Required DB connection port number - Enter DB port within the range 1,024 - 65,535
License Required SQL Server License Key - Enter the issued license key
- If the entered license key is not valid, the service may not be created
Backup > Use Select Whether to use backup - Select Use to set backup file retention period, backup start time, Full backup schedule (day of week), Archive backup cycle.
Backup > Retention Period Select Backup Retention Period - Select the backup retention period. File retention period can be set from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Period Select Backup Start Time - Select backup start time
- The minutes when the backup runs are set randomly, and the backup end time cannot be set
Backup > Full Backup Schedule(Day) Select Full Backup Schedule - Select the day to run Full Backup
- Full Backup is performed on a weekly cycle
Backup > Archive backup frequency Select Archive backup frequency - Select the Archive backup frequency
- Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Audit Log Settings Select Whether to save Audit Log - Select Use to configure the Audit Log function
- DDL, user connection information records are saved
- If Audit is set, DB performance may degrade
Parameter Required DB configuration parameters - Query button can be clicked to view detailed information of the parameter
- Parameters can be modified after the service creation is completed, and after modification a DB Restart is required
DB Collation Select Data sorting method - A command that specifies the data sorting and comparison method, and the result of the operation may differ depending on the setting.
Time zone Required Standard time zone to be used by the Database Table. Microsoft SQL Server (DBaaS) Database configuration items- Enter additional information area, input or select the required information.
Category Required or notDetailed description Tag Select Add Tag - Up to 50 can be added per resource
- After clicking the Add Tag button, enter or select Key, Value values
Table. Microsoft SQL Server (DBaaS) Additional Information Input Items
- 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 Resource List page.
Microsoft SQL Server(DBaaS) Check detailed information
Microsoft SQL Server(DBaaS) service allows you to view and edit the full resource list and detailed information. Microsoft SQL Server(DBaaS) Details page consists of Details, Tags, Operation History tabs, and for databases with a configured Replica, a Replica Information tab is additionally provided.
To view detailed information of the Microsoft SQL Server (DBaaS) service, follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) menu, please click. Go to the Service Home page of Microsoft SQL Server(DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. Navigate to the Microsoft SQL Server(DBaaS) List page.
- Click the resource to view detailed information on the Microsoft SQL Server(DBaaS) List page. You will be taken to the Microsoft SQL Server(DBaaS) Details page.
- Microsoft SQL Server(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
Category Detailed description Cluster Status Cluster status with DB installed - Creating: Cluster is being created
- Editing: Cluster is changing to operation execution state
- Error: Cluster encountered a failure while performing a task
- If it occurs continuously, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Cluster is being restarted
- Running: Cluster is operating normally
- Starting: Cluster is being started
- Stopped: Cluster is stopped
- Stopping: Cluster is being stopped
- Synchronizing: Cluster is being synchronized
- Terminating: Cluster is being deleted
- Unknown: Cluster status is unknown
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is changing to upgrade execution state
Cluster Control Button to change cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to Active
More additional features Cluster-related management button - Service status synchronization: View real-time DB service status
- Backup history: If backup is configured, check whether backup runs correctly and view its history
- Database recovery: Recover the DB based on a specific point in time
- Parameter management: View and modify DB configuration parameters
- Add secondary: Configure a read-only cluster Replica
- DB user management: View and manage DB accounts (users) registered in the DB
- Export DB Log: Logs stored via Audit settings can be exported to the user’s Object Storage
Service termination Button to cancel the service Table. Microsoft SQL Server (DBaaS) status information and additional features
Detailed Information
Microsoft SQL Server(DBaaS) List page allows you to view detailed information of the selected resource and, if necessary, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in the respective 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 |
| Creator | User who created the service |
| Creation Time | Service Creation Time |
| Editor | User who modified the service information |
| Modification Time | Service information modification time |
| Image/Version | Installed DB image and version information
|
| Cluster Name | Name of the cluster composed of servers |
| Databse service name | Database management unit name |
| Database username | DB user name |
| Database name > Default Database | Server name applied during DB installation |
| Database name > Add Database | Server name applied when installing DB
|
| Planned Compute | Resource status with Planned Compute set
|
| Maintenance Period | DB Maintenance Period Status
|
| Backup | Backup configuration status
|
| Audit Log Settings | Audit Log Settings Status
|
| Time zone | Standard time zone used by the Database |
| DB Collation | Data sorting method |
| VIP | Virtual IP information
|
| Network | Network information where DB is installed (VPC, Subnet) |
| IP Access Control | Service Access Policy Settings
|
| Primary & Secondary | Primary/Secondary server type, default OS, additional Disk information
|
Tag
Microsoft SQL Server(DBaaS) List page you can view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag List | Tag List
|
Work History
Microsoft SQL Server(DBaaS) List You can view the operation history of the selected resource on the page.
| Category | Detailed description |
|---|---|
| Work History List | Resource Change History
|
Microsoft SQL Server(DBaaS) Managing Resources
If you need to change or recover the existing configuration options of a created Microsoft SQL Server (DBaaS) resource, or manage parameters, you can perform the tasks on the Microsoft SQL Server (DBaaS) Details page.
Operating Control
If changes occur to a running Microsoft SQL Server (DBaaS) resource, you can start, stop, or restart it. Also, if HA is configured, you can switch the Primary-Secondary servers via a switch-over.
To control the operation of Microsoft SQL Server (DBaaS), follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- Service Home page, click the Microsoft SQL Server(DBaaS) menu. Navigate to the Microsoft SQL Server(DBaaS) list page.
- Microsoft SQL Server(DBaaS) List On the page, click the resource to control operation. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Check the status of Microsoft SQL Server (DBaaS) and complete the change using the control button below.
- Start: The server where the DB service is installed and the DB service are 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 Primary server and Secondary server.
Synchronize Service Status
You can synchronize the real-time service status of Microsoft SQL Server (DBaaS).
To check the service status of Microsoft SQL Server (DBaaS), follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. You will be taken to the Microsoft SQL Server(DBaaS) List page.
- Microsoft SQL Server(DBaaS) List Click the resource to view the service status on the page. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Service Status Synchronization Click the button. While it is being queried, the cluster will change to Synchronizing state.
- When the query is completed, the status is updated in the server information item, and the cluster changes to Running state.
Change Server Type
You can change the configured server type.
To change the server type, follow the steps below.
- If you modify the server type, a server reboot is required. Please separately verify any SW license changes or SW settings and implementations due to server specification changes.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. Navigate to the Microsoft SQL Server(DBaaS) list page.
- Click the resource to change the server type on the Microsoft SQL Server(DBaaS) List page. Navigate to the Microsoft SQL Server(DBaaS) Details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Edit Server Type popup window will open.
- 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 space, you can add storage. In the case of a redundant DB configuration, all redundant servers are added simultaneously.
To add storage capacity, follow the steps below.
- It will be applied the same way as the Storage type selected when creating the service.
- For a high-availability configured DB, adding storage is applied simultaneously to the storage of the Primary DB and the Secondary DB.
- All Services > Database > Microsoft SQL Server(DBaaS) Please click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- Service Home page, click the Microsoft SQL Server(DBaaS) menu. Navigate to the Microsoft SQL Server(DBaaS) list page.
- Click the resource to add storage on the Microsoft SQL Server(DBaaS) List page. Navigate to the Microsoft SQL Server(DBaaS) Detail page.
- Click the Add Disk button at the bottom of the detailed information. The Add Storage Request popup window opens.
- Additional Storage Request In the popup window, after entering 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 the case of a redundant DB configuration, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Go to the Service Home page of Microsoft SQL Server(DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. Navigate to the Microsoft SQL Server(DBaaS) list page.
- Microsoft SQL Server(DBaaS) List Click the resource to change the server type on the page. Microsoft SQL Server(DBaaS) Detail Navigate to the page.
- Click the Edit icon of the additional Disk you want to expand at the bottom of the detailed information. The Edit Additional Storage popup window opens.
- Add Storage Modification After entering the expansion capacity in the popup window, click the Confirm button.
Microsoft SQL Server(DBaaS) Cancel
You can cancel the unused Microsoft SQL Server (DBaaS) to reduce operating costs. However, if you cancel the service, the running service may be immediately stopped, so you should consider the impact of service interruption sufficiently before proceeding with the cancellation.
To cancel Microsoft SQL Server (DBaaS), follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. Navigate to the Service Home page of Microsoft SQL Server(DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. Navigate to the Microsoft SQL Server(DBaaS) List page.
- On the Microsoft SQL Server(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
- After termination is completed, check whether the resource has been terminated on the Microsoft SQL Server(DBaaS) list page.
5.2.1 - Managing DB Services
Users can manage Microsoft SQL Server (DBaaS) through the Samsung Cloud Platform Console.
Managing Databases
For Microsoft SQL Server Enterprise version, you can add new databases. Up to 100 databases can be added per cluster.
Adding a Database
To add a database, follow these steps:
- Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
- On the Microsoft SQL Server (DBaaS) List page, click the resource you want to add storage to. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
- Click the Add button in the Database Name field. The Add Database popup window will open.
- In the Add Database popup window, click the + button to enter the database name and select the drive, then click the Confirm button.
Deleting a Database
To delete a database, follow these steps:
- Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
- On the Microsoft SQL Server (DBaaS) List page, click the resource you want to add storage to. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
- Click the Modify button in the Database Name field. The Delete Additional Database popup window will open.
- In the Delete Additional Database Request popup window, check the database you want to delete and click the Delete button. The Delete Database popup window will open.
- In the Delete Database popup window, enter the name of the database you want to delete and click the Confirm button.
Managing Parameters
It provides a feature to easily view and modify database configuration parameters.
Viewing Parameters
To view configuration parameters, follow these steps:
- Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
- On the Microsoft SQL Server (DBaaS) List page, click the resource you want to view and modify parameters for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window will open.
- In the Parameter Management popup window, click the View button. The View Notification popup window will open.
- When the View Notification popup window opens, click the Confirm button. It may take some time to view.
Modifying Parameters
To modify configuration parameters, follow these steps:
- Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
- On the Microsoft SQL Server (DBaaS) List page, click the resource you want to view and modify parameters for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window will open.
- In the Parameter Management popup window, click the View button. The View Notification popup window will open.
- When the View Notification popup window opens, click the Confirm button. It may take some time to view.
- If modification is necessary, click the Modify button and enter the modification details in the user-defined value field of the parameter to be modified.
- After entering the modification details, click the Save button.
Managing DB Users
It provides a feature to view and manage DB user information.
Viewing DB Users
To view DB users, follow these steps:
- Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
- On the Microsoft SQL Server (DBaaS) List page, click the resource you want to view DB users for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
- Click the More button and then click the DB User Management button. You will be moved to the DB User Management page.
- On the DB User Management page, click the View button. It may take some time to view.
Exporting DB Logs
It supports exporting audit logs that need to be stored for a long time to Object Storage. Users can set the log type to be stored, the target bucket to export to, and the export cycle. According to the set criteria, the logs are copied and stored in the designated Object Storage.
Additionally, to efficiently manage disk space, an option to automatically delete the original log files when exporting logs to Object Storage is provided. By utilizing this option, users can effectively secure storage capacity while safely storing necessary log data for a long time.
- To use the DB Log Export feature, Object Storage creation is required. Refer to the Object Storage User Guide for Object Storage creation.
- Please check the expiration date of the authentication key. If the authentication key expires, logs will not be stored in the bucket.
- Please be careful not to expose authentication key information to the outside.
Setting DB Log Export Mode
To set the DB Log export mode, follow these steps:
- Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
- On the Microsoft SQL Server (DBaaS) List page, click the resource you want to export DB logs from. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
- Click the More button and then click the DB Log Export button. You will be moved to the DB Log Export page.
- On the DB Log Export page, click the Register button. You will be moved to the DB Log Export Registration page.
- On the DB Log Export Registration page, enter the required information and click the Save button.
| Category | Required | Detailed Description |
|---|---|---|
| Log Type | Required | Log type to be stored |
| Storage Bucket Name | Required | Object Storage bucket name to store logs |
| Authentication Key > Access Key | Required | Access key to access Object Storage |
| Authentication Key > Secret Key | Required | Secret key to access Object Storage |
| File Creation Cycle | Required | Cycle to create files in Object Storage |
| Original Log Deletion | Optional | Whether to delete original logs when exporting to Object Storage |
Managing DB Log Export
To modify, cancel, or immediately export DB log settings, follow these steps:
- Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
- On the Microsoft SQL Server (DBaaS) List page, click the resource you want to manage DB log export for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
- Click the More button and then click the DB Log Export button. You will be moved to the DB Log Export page.
- On the DB Log Export page, click the More button for the log type you want to manage and click the Immediate Export, Modify, or Cancel button.
- Immediate Export: Exports the selected log to the Object Storage bucket.
- Modify: Modifies the DB log export mode setting.
- Cancel: Cancels the DB log export mode setting.
Upgrading Microsoft SQL Server (DBaaS) Version
It provides a feature to upgrade versions due to functional improvements and security patches. Only minor version upgrades are supported within the same major version.
- Please perform version upgrades after checking the service status through service status synchronization.
- Please set up backups before performing version upgrades. If backups are not set up, some data may not be recoverable in case of problems during the upgrade.
- Backed-up data will be automatically deleted after the version upgrade is complete.
To upgrade the version, follow these steps:
- Click All Services > Database > Microsoft SQL Server (DBaaS) menu. You will be moved to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server (DBaaS) menu. You will be moved to the Microsoft SQL Server (DBaaS) List page.
- On the Microsoft SQL Server (DBaaS) List page, click the resource you want to upgrade the version for. You will be moved to the Microsoft SQL Server (DBaaS) Details page.
- Click the Modify button in the Image/Version field. The Version Upgrade popup window will open.
- In the Version Upgrade popup window, select the version to upgrade to and whether to set up backups, then click the Confirm button.
- In the Version Upgrade Notification popup window, click the Confirm button.
5.2.2 - DB Backup and Recovery
The user can set up a backup of Microsoft SQL Server(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.
Microsoft SQL Server(DBaaS) backup
Microsoft SQL Server(DBaaS) provides a data backup feature based on its own backup command, and also provides an optimized backup environment for data protection and management through backup history checking and backup file deletion functions.
Setting up backup
The method of setting up a backup for Microsoft SQL Server(DBaaS) is described in the Microsoft SQL Server(DBaaS) creation guide, please refer to it.
To modify the backup settings of the generated resource, follow these steps.
If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
- If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.
- All services > Database > Microsoft SQL Server(DBaaS) menu, click. It moves to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. It moves to the Microsoft SQL Server(DBaaS) list page.
- Click the resource to set up backup on the Microsoft SQL Server(DBaaS) list page. It moves to the Microsoft SQL Server(DBaaS) details page.
- Click the Edit button of the backup item. The Backup Settings popup window opens.
- If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the OK button.
- If you want to stop the backup setting, uncheck 사용 in the 백업 설정 popup window and click the 확인 button.
Check Backup History
To view the backup history, follow these steps.
- Click All Services > Database > Microsoft SQL Server(DBaaS) menu. It moves to the Service Home page of Microsoft SQL Server(DBaaS).
- Service Home page, click the Microsoft SQL Server(DBaaS) menu. It moves to the Microsoft SQL Server(DBaaS) list page.
- Microsoft SQL Server(DBaaS) list page, click the resource to check the backup history. It moves to the Microsoft SQL Server(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.
Deleting backup files
To delete the backup history, follow these steps.
- Click All Services > Database > Microsoft SQL Server(DBaaS) menu. It moves to the Service Home page of Microsoft SQL Server(DBaaS).
- Service Home page, click the Microsoft SQL Server(DBaaS) menu. It moves to the Microsoft SQL Server(DBaaS) list page.
- Microsoft SQL Server(DBaaS) list page, click the resource to check the backup history. It moves to the Microsoft SQL Server(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window, check the file you want to delete, and then click the Delete button.
Microsoft SQL Server(DBaaS) Recovery
In the event of a disability or data loss that requires restoration with a backup file, recovery is possible based on a specific point in time through the recovery function. When performing Microsoft SQL Server (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, and the DB is installed with the version at the backup point, and the recovery proceeds with the DB configuration information and data.
To restore Microsoft SQL Server(DBaaS), follow these procedures.
- Click All Services > Database > Microsoft SQL Server(DBaaS) menu. It moves to the Service Home page of Microsoft SQL Server(DBaaS).
- Service Home page, click the Microsoft SQL Server(DBaaS) menu. Move to the Microsoft SQL Server(DBaaS) list page.
- Microsoft SQL Server(DBaaS) resource list page, click the resource you want to restore. Move to the Microsoft SQL Server(DBaaS) details page.
- Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
- Database Recovery Configuration area, enter the corresponding information and click the Complete button.
| Classification | Necessity | Detailed Description |
|---|---|---|
| Recovery Type | Required | Set the point in time to recover
|
| Server name prefix | Required | Recovery DB server name
|
| Cluster Name | Required | Recovery DB Cluster Name
|
| Service Type > Server Type | Required | Recovery DB Server Type
|
| Service Type > Planned Compute | Selection | Current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Recovery DB uses Block Storage settings
|
| Database username | required | Database username
|
| Database Port number | required | Database Port number
|
| IP Access Control | Select | Set service access policy
|
| Maintenance period | Select | DB maintenance period
|
| Tag | Select | Add Tag
|
5.2.3 - Add Secondary
The user can enter the required information of the Secondary through the Samsung Cloud Platform Console and create the service through detailed options.
Add Secondary
You can create a read-only replica server through Secondary configuration. To configure additional Secondary, it must be created with duplication configuration (HA) and Enterprise Edition, and the backup function must be enabled.
To configure Secondary, follow these procedures.
- Click on the menu for all services > Database > Microsoft SQL Server(DBaaS). It moves to the Service Home page of Microsoft SQL Server(DBaaS).
- Service Home page, click the Microsoft SQL Server(DBaaS) menu. It moves to the Microsoft SQL Server(DBaaS) list page.
- Click the resource to configure Secondary on the Microsoft SQL Server(DBaaS) list page. It moves to the Microsoft SQL Server(DBaaS) details page.
- Secondary Add 버튼을 클릭하세요. Secondary Add 페이지로 이동합니다.
- Secondary configuration area, enter information after, Complete button, click.
| Classification | Mandatory | Detailed Description |
|---|---|---|
| Secondary number | Essential | Number of Secondary configurations
|
| Secondary name | Required | Secondary server name
|
| Service Type > Server Type | Required | Secondary Server Type
|
| Service Type > Planned Compute | Select | Current status of resources with Planned Compute set
|
| Network > Common Settings | Required | Network settings for servers created by the service
|
| Network > Server Settings | Required | Network settings for servers created by the service
|
| License | Required | SQL Server License Key
|
5.2.4 - Microsoft SQL Server(DBaaS) server connection
Scenario Overview
The Microsoft SQL Server(DBaaS) server connection scenario is a scenario where a Bastion host (Virtual Server) and a Database service are created, and the DB service is accessed through the Bastion host. To securely access Microsoft SQL Server (DBaaS) in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.
This scenario largely describes the process of creating a Bastion host and Database service, and configuring the network environment for Bastion host and Database connection, and accessing it through a DB connection client.
Scenario Components
You can configure the scenario using the following services.
| Service Group | Service | Detailed Description | |
|---|---|---|---|
| Networking | VPC | A service that provides an independent virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that allows users to subdivide the network into smaller segments according to purpose/size within the VPC | |
| Networking | VPC > Public IP | A service that reserves public IP and assigns and returns it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the internet | |
| Networking | Security Group | A virtual firewall that controls the server’s traffic | |
| Database | Microsoft SQL Server(DBaaS) | A service that easily creates and manages Microsoft SQL Server in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- The default policy of Security Group is Deny All, so only allowed IPs must be registered.
- In/Outbound’s All Open(Any IP, Any Port) policy can expose cloud resources to external threats.
- By specifying the necessary IP and Port to set the policy, you can enhance security.
Scenario composition method
To configure the scenario, create the necessary services through the following procedure.
1. Configuring the Network
This describes the process of configuring the network environment for connecting to the Bastion Host and Database services.
1-1. Creating a VPC
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
- VPC Creation page, please enter the information required for service creation.
- IP range should be entered as
192.168.x.0/16.
- IP range should be entered as
- In the Summary panel, review the detailed information and estimated charges, and click the Complete button.
- Once creation is complete, check the resource you created on the VPC list page.
1-2. Creating a Subnet
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Subnet menu. It moves to the Subnet list page.
- Click the Subnet Creation button. It moves to the Subnet Creation page.
- Subnet Creation page where you enter the information needed to create a service.
- Subnet type should be selected as General.
- Please select a pre-created VPC.
- IP range should be entered as
192.168.x.0/24.
- In the Summary panel, review the detailed information and estimated charges, and click the Complete button.
- Once creation is complete, check the created resource on the Subnet list page.
1-3. Creating an Internet Gateway
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- On the Service Home page, click the Internet Gateway menu. It moves to the Internet Gateway list page.
- Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
- Internet Gateway Creation page, please enter the required information necessary for service creation.
- Please select a pre-created VPC.
- Select Use in the Firewall usage item.
- In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
- Once the creation is complete, check the created resource on the Internet Gateway list page.
1-4. Creating a Public IP
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Public IP menu. It moves to the Public IP list page.
- Public IP Reservation button, click. Move to the Public IP Reservation page.
- Public IP Reservation page where you enter the required information necessary for service reservation.
- In the Summary panel, review the detailed information and estimated billing amount, and click the Complete button.
- Once creation is complete, check the created resource on the Public IP list page.
1-5. Creating a Security Group
- Click All services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
- Service Home page, click the Create Security Group button. Move to the Create Security Group page.
- Security Group Creation page, please enter the required information necessary for service creation.
- Check the input information and click the Complete button.
- Once creation is complete, check the created resource on the Security Group list page
2. Creating a Bastion host
This describes the process of configuring the Bastion Host where the database connection client should be installed.
2-1. Creating Server Keypair
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Keypair menu. It moves to the Keypair list page.
- Create Keypair button will be clicked. It moves to the Create Keypair page.
- Keypair creation page where you enter the required information necessary for service creation.
- Check the creation information and click the Complete button.
- The key can only be downloaded for the first time, and re-issuance is not provided.
- Please make sure to store the downloaded key in a safe place.
2-2. Creating a Bastion Host
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server creation button. Move to the Virtual Server creation page.
- Virtual Server Creation page, please enter the required information necessary for service creation.
- Image is Windows, please select it.
- Please select a pre-created VPC and Subnet.
- Click NAT and select the Public IP reserved in 1-4. Public IP 생성하기.
- 2-1. Create Server Keypair and connect the Keypair created from there.
- Summary panel, check the detailed information generated and the expected billing amount, and click the Complete button.
- After creation is complete, check the created resource on the Virtual Server list page.
2-3. Check Bastion host connection ID and PW
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
- Virtual Serve list page, click on the resource created in 2-2. Bastion host creation. It moves to the detailed information page of the corresponding resource.
- In the detailed information page, click the RDP password inquiry button in the Keypair name item. The RDP password inquiry pop-up window opens.
- RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Server Keypair creation.
- After attaching, click the Password check button. The ID and password required to access the resource will be displayed.
- The ID and Password will be used as information to connect to the Bastion host later in 5-1. Connect to Bastion host.
3. Creating a Database
It describes the process of creating a Database service.
3-1. Creating Microsoft SQL Server (DBaaS) Service
- Click on the menu for all services > Database > Microsoft SQL Server(DBaaS). It moves to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Create Microsoft SQL Server(DBaaS) button. It moves to the Create Microsoft SQL Server(DBaaS) page.
- Microsoft SQL Server(DBaaS) creation page, please enter the required information needed for service creation.
- Select and connect to the pre-created VPC and Subnet.
- Enter Database related creation information on the required information input screen.
- Add the Bastion host IP in the IP access control item.
- Database Port is 2866 by default, but users can also specify it.
- In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
- Once creation is complete, check the created resource from the Microsoft SQL Server(DBaaS) list page.
4. Setting Rules
This describes the process of setting rules for users to connect to the Bastion host and rules for the Bastion host to connect to the Database.
4-1. Security Group Add Security Rules
- Click All Services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
- Service Home page, click the Security Group menu. Move to the Security Group list page.
- 1-5. Creating a Security Group Select the Security Group resource created from 1-5. Creating a Security Group. It moves to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Rule tab where you click the Add Rule button. Move to the Add Rule popup window.
- In the Add Rule popup window, enter the rules below and click the OK button
| Direction | Remote | Destination Address | Protocol | Port | Description |
|---|---|---|---|---|---|
| Inbound | CIDR | User PC IP | TCP | 3389 (RDP) | Bastion connection PC → Bastion host |
| Outbound | CIDR | DB IP | TCP | Database Port (direct input) | Bastion host → Database |
4-2. Adding IGW Firewall Rules
- Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
- Service Home page, click the Firewall menu. It moves to the Firewall list page.
- Firewall list page, select the Internet Gateway resource name created in 1-3. Creating Internet Gateway. It moves to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Rule tab, click the Add Rule button. Move to the Add Rule popup window.
- Add Rule In the popup window, enter the following rules and click the OK button.
| Departure Address | Destination Address | Protocol | Port | Action | Direction | Description |
|---|---|---|---|---|---|---|
| Bastion connection PC IP | Bastion host IP | TCP | 3389(RDP) | Allow | Inbound | User PC → Bastion host |
5. Connect to Database
This describes the process of a user accessing the Database through a DB connection client program.
This guide provides instructions on how to connect using SSMS (Microsoft SQL Server Management Studio). Since there are various database client programs and CLI utilities, you can also install and use the tools that are suitable for you.
5-1. Connect to the Bastion host
- Run Remote Desktop Connection in the Windows environment of the PC that wants to access the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
- When the remote desktop connection is successful, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Check Bastion host access ID and PW and click the Confirm button.
5-2. Install DB connection client program (SSMS) on Bastion host
- Go to the official Microsoft SQL Server page and download the SSMS program.
- SSMS program download path: https://learn.microsoft.com/en-us/ssms/download-sql-server-management-studio-ssms
- Connect the hard drive of the user PC to upload the file to the Bastion host.
- Click the Details button for local devices and resources entries in the Local Resources tab of Remote Desktop Connection.
- Select the local disk where the file was downloaded to the drive and click the Confirm button.
- Download the file, copy it to the Bastion Host, and upload it, then click the SSMS (Microsoft SQL Server Management Studio) installation file to install it.
5-3. Using DB Connection Client Program (SSMS) to Connect to Database
- Run SSMS (Microsoft SQL Server Management Studio). The Connect to Server popup window will appear.
- Connect to Server popup window, enter the database server information created in 3-1. Microsoft SQL Server(DBaaS) service creation and click the Connect button.
Required Input Element Items Input Value Server type Database Engine Server name Database server IP, Database Port (ex. 192.168.10.1,2866) Authentication SQL Server Authentication Login Database username Password Database password Encryption Optional DB Connection Client Program Input Items - Once the connection is complete, the Database will be connected. After connection, you can try performing simple queries, etc.
5.3 - API Reference
5.4 - CLI Reference
5.5 - Release Note
Microsoft SQL Server(DBaaS)
- Microsoft SQL Server(DBaaS) feature added
- 2nd generation server type added
- Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see Microsoft SQL Server (DBaaS) server type
- DB User and Access Control Management added
- For more detailed information, please refer to DB User Management, DB Access Control Management
- DB Audit Log Export feature added
- For more information, see Exporting DB Log
- Backup Notification Feature provided
* Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
- Block Storage type added **HDD, HDD_KMS type
- A Microsoft SQL Server (DBaaS) service that allows you to easily create and manage Microsoft SQL Server in a web environment has been released.
6 - CacheStore(DBaaS)
6.1 - Overview
Service Overview
CacheStore(DBaaS) is a service that provides the in‑memory based data stores Redis OSS and Valkey. Samsung Cloud Platform provides an environment that can automate the installation of Redis OSS and Valkey through a web‑based console and perform management functions for operation.
CacheStore (DBaaS) provides a Sentinel method consisting of a Master server that performs read/write operations and read-only Replica servers that replicate Master data. Sentinel checks the status of DB servers where the engine is installed, and if a failure occurs on the Master server, it automatically failovers the Replica servers to become the Master server. Additionally, to prepare for issues with the DB server or data, it offers a function that automatically backs up at a user-specified time, supporting data recovery based on the backup point.
Provided Features
CacheStore(DBaaS) provides the following features.
- Auto Provisioning (Auto Provisioning): UI allows installation and configuration of Database (DB), and a redundant configuration is possible with a Sentinel-based Single Master server and Replica server (1 or 2).
- Operation Control Function: Provides a function to control the status of running servers. In addition to start and stop, restart is possible if there is an issue with the DB or to apply configuration values. When configured for high availability (HA), you can switch Active-Standby servers via Switch-over.
- Backup and Recovery: Provides a data backup function based on its own backup commands. The backup time window and storage agency can be set by the user, and additional fees are incurred depending on the backup volume. It also provides a recovery function for backed-up data, so when the user performs a recovery, a separate DB is created and the recovery proceeds to the point in time selected by the user.
- Parameter Management: Performance improvement and security-related DB configuration parameter modifications are possible.
- Service status query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
Components
CacheStore (DBaaS) provides pre‑validated engine versions and various server types according to the open‑source support policy. Users can select and use them based on the scale of the service they wish to configure.
Engine Version
The engine versions supported by CacheStore(DBaaS) are as follows.
Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.
According to the supplier’s policy, the EOS and EoTS dates may change, so please refer to the supplier’s license management policy page for details.
| Image | Provided Version | EoS Date | EoTS Date |
|---|---|---|---|
| Redis OSS Sentinel | 7.2.11 | TBD | TBD |
| valkey Sentinel | 8.1.4 | TBD | TBD |
Server Type
The server types supported by CacheStore (DBaaS) are as follows.
For detailed information about the server types provided by CacheStore(DBaaS), see CacheStore(DBaaS) server type.
Standard redis1v2m4
Category
Example
Detailed description
Server Type
Standard
Provided Server Type- Standard: Standard specifications (vCPU, Memory) configuration commonly used
Server specifications
redis1
Provided server specifications- redis1: Standard specifications (vCPU, Memory) configuration commonly used
Server Specification
v2
Number of vCores- v2: 2 virtual cores
Server specifications
m4
Memory capacity- m4: 4GB Memory
Table. CacheStore(DBaaS) Server Type Components
# Preliminary Service
This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service for details and prepare in advance.<br>
Service Category
Service
Detailed Description
Networking
VPC
A service that provides an independent virtual network in a cloud environment
Table. CacheStore(DBaaS) Preliminary Service
6.1.1 - Server Type
CacheStore(DBaaS) server type
CacheStore(DBaaS) provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth, etc. When creating CacheStore(DBaaS), Redis is installed according to the selected server type suitable for the purpose of use.
The server types supported by CacheStore(DBaaS) are as follows.
Standard redis1v2m4
Classification | Example | Detailed Description |
|---|---|---|
| Server Type | Standard | Provided server type distinction
|
| Server Specification | redis1 | Provided server type distinction and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specification | m4 | Memory capacity
|
redis1 server type
The redis1 server type of CacheStore(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor Supports up to 16 vCPUs and 256 GB of memory Up to 12.5 Gbps of networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | redis1v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | redis1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | redis1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | redis1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | redis1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | redis1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | redis1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | redis1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | redis1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | redis1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | redis1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | redis1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | redis1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | redis1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | redis1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | redis1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | redis1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
css1 server type
The css1 server type of CacheStore(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.
Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor Supports up to 16 vCPUs and 256 GB of memory Up to 12.5 Gbps of networking speed
| Classification | Server Type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | css1v1m2 | 1 vCore | 2 GB | Up to 10 Gbps |
| Standard | css1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | css1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | css1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | css1v2m24 | 2 vCore | 24 GB | Up to 10 Gbps |
| Standard | css1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | css1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | css1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | css1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | css1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | css1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | css1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | css1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | css1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | css1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | css1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | css1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
| Table. CacheStore(DBaaS) server type specification - css1 server type |
6.1.2 - Monitoring Metrics
CacheStore(DBaaS) Monitoring Metrics
The following table shows the performance monitoring metrics of CacheStore(DBaaS) that can be checked through Cloud Monitoring. For detailed instructions on using Cloud Monitoring, refer to the Cloud Monitoring guide.
For server monitoring metrics of CacheStore(DBaaS), refer to the Virtual Server Monitoring Metrics guide.
| Performance Item | Detailed Description | Unit |
|---|---|---|
| Active Defragmentation Keys [Hits] | Number of keys defragmented | cnt |
| Active Defragmentation Keys [Miss] | Number of keys skipped in the active defragmentation process | cnt |
| Active Defragmentationd [Hits] | Number of value reassignments performed by the active defragmentation process | cnt |
| Active Defragmentations [Miss] | Number of value reassignments started and aborted by the active defragmentation process | cnt |
| Allocated Bytes [OS] | Number of bytes allocated by CacheStore(DBaaS) and recognized by the operating system (resident set size) | bytes |
| Allocated Bytes [Redis] | Total number of bytes allocated by CacheStore(DBaaS) | bytes |
| AOF Buffer Size | AOF buffer size | bytes |
| AOF File Size [Current] | Current AOF file size | bytes |
| AOF File Size [Lastest Startup] | AOF file size at the latest startup or rewrite | bytes |
| AOF Rewrite Buffer Size | AOF rewrite buffer size | bytes |
| AOF Rewrite Current Time | Time of the ongoing AOF rewrite operation, if any | sec |
| AOF Rewrite Last Time | Time of the last AOF rewrite operation | sec |
| Calls | Number of calls that reached command execution (not rejected) | cnt |
| Changes [Last Saved] | Number of changes since the last dump | cnt |
| Client Output Buffer [MAX] | Longest output list among current client connections | cnt |
| Clients [Sentinel] | Number of client connections (Sentinel) | cnt |
| Connected Slaves | Number of connected slaves | cnt |
| Connections [Blocked] | Number of clients waiting for blocking calls (BLPOP, BRPOP, BRPOPLPUSH) | cnt |
| Connections [Current] | Number of client connections (excluding slave connections) | cnt |
| Copy On Write Allocated Size [AOF] | COW allocation size during the last RDB save operation | bytes |
| Copy On Write Allocated Size [RDB] | COW allocation size during the last RDB save operation | bytes |
| CPU Time [Average] | Average CPU time used per command execution | cnt |
| CPU Time [Total] | Total CPU time used by these commands | usec |
| CPU Usage [System Process] | System CPU usage by background processes | % |
| CPU Usage [System] | System CPU usage by the CacheStore(DBaaS) server | % |
| CPU Usage [User Process] | User CPU usage by background processes | % |
| CPU Usage [User] | System CPU usage by background processes | % |
| Dataset Used | Dataset size | bytes |
| Disk Used | Datadir usage | MB |
| Evicted Keys | Number of evicted keys due to maxmemory limit | cnt |
| Fsyncs [Delayed] | Delayed fsync counter | cnt |
| Fsyncs [Pending] | Number of fsync operations pending in the background I/O queue | cnt |
| Full Resyncs | Number of full resynchronizations with slaves | cnt |
| Keys [Expired] | Total number of key expiration events | cnt |
| Keys [Keyspace] | Number of keys in the keyspace | cnt |
| Lastest Fork Duration Time | Time of the latest fork (fork) operation | usec |
| Lookup Keys [Hit] | Number of successful key lookups in the main dictionary | cnt |
| Lookup Keys [Miss] | Number of failed key lookups in the main dictionary | cnt |
| Lua Engine Memory Used | Memory used by the Lua engine | bytes |
| Master Last Interaction Time Ago | Time since the last interaction with the master | sec |
| Master Last Interaction Time Ago [Sync] | Time since the last interaction with the master | sec |
| Master Offset | Current replication offset of the server | pid |
| Master Second Offset | Offset until the replication ID is accepted | pid |
| Master Sync Left Bytes | Number of bytes left to synchronize | bytes |
| Memory Fragmentation Rate | Ratio of used_memory_rss to used_memory | % |
| Memory Fragmentation Rate [Allocator] | Fragmentation ratio | % |
| Memory Fragmentation Used | Difference between used_memory_rss and used_memory in bytes | bytes |
| Memory Fragmentation Used [Allocator] | Resident bytes | bytes |
| Memory Max Value | Memory limit | bytes |
| Memory Resident [Allocator] | Resident memory | bytes |
| Memory RSS Rate [Allocator] | Resident ratio | % |
| Memory Used [Active] | Active memory | bytes |
| Memory Used [Allocated] | Allocated memory | bytes |
| Memory Used [Resident] | Resident bytes | bytes |
| Network In Bytes [Total] | Total network input (bytes) | bytes |
| Network Out Bytes [Total] | Total network output (bytes) | bytes |
| Network Read Rate | Network read rate per second (KB/sec) | cnt |
| Network Write Rate | Network write rate per second (KB/sec) | cnt |
| Partial Resync Requests [Accepted] | Number of accepted partial resynchronization requests | cnt |
| Partial Resync Requests [Denied] | Number of denied partial resynchronization requests | cnt |
| Peak Memory Consumed | Maximum memory used by CacheStore(DBaaS) | bytes |
| Processed Commands | Number of commands processed per second | cnt |
| Processed Commands [Total] | Total number of processed commands | cnt |
| Pub/Sub Channels | Global number of pub/sub channels with client subscriptions | cnt |
| Pub/Sub Patterns | Global number of pub/sub patterns with client subscriptions | cnt |
| RDB Saved Duration Time [Current] | Time of the ongoing RDB save operation, if any | sec |
| RDB Saved Duration Time [Last] | Time of the last RDB save operation | sec |
| Received Connections [Total] | Total number of received connections | cnt |
| Rejected Connections [Total] | Total number of rejected connections | cnt |
| Replication Backlog Actove Count | Flag indicating whether replication backlog is active | cnt |
| Replication Backlog Master Offset | Master offset of the replication backlog buffer | cnt |
| Replication Backlog Size | Size of data in the replication backlog buffer | bytes |
| Replication Backlog Size [Total] | Total size of the replication backlog buffer | bytes |
| Slave Priority | Priority of the server as a failover target | cnt |
| Slave Replication Offset | Replication offset of the slave server | pid |
| Slow Operations | Number of slow operations | cnt |
| Sockets [MIGRATE] | Number of sockets open for migration | cnt |
| Tracked Keys [Expiry] | Number of keys tracked for expiration (only for writable slaves) | cnt |
| Instance Status [PID] | PID of the redis-server process | pid |
| Sentinel Status [PID] | PID of the sentinel process | pid |
6.2 - How-to guides
The user can enter the necessary information of CacheStore(DBaaS) through the Samsung Cloud Platform Console and create the service by selecting detailed options.
Creating CacheStore(DBaaS)
You can create and use the CacheStore(DBaaS) service in the Samsung Cloud Platform Console.
Please configure the Subnet type of VPC to General before creating the service.
- If the Subnet type is Local, the creation of the corresponding Database service is not allowed.
To create a CacheStore(DBaaS), follow these steps.
Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
On the Service Home page, click the CacheStore(DBaaS) creation button. It moves to the CacheStore(DBaaS) creation page.
CacheStore(DBaaS) creation page, enter the information required for service creation and select detailed options.
Image and Version Selection area, please select the necessary information.
Classification NecessityDetailed Description Image Version Required Provides a list of CacheStore (DBaaS) versions Fig. CacheStore(DBaaS) image and version selection itemsEnter Service Information Enter or select the required information in the area.
Classification NecessityDetailed Description Server Name Prefix Required Server name where Redis/Valkey will be installed - Starts with lowercase English letters, and consists of 3 to 13 characters using lowercase letters, numbers, and special characters (
-)
- A postfix such as 001, 002 is attached based on the server name to create the actual server name
Cluster Name Required Name of the cluster where Redis/Valkey is installed - Enter in English, 3-20 characters
- Cluster is a unit that bundles multiple servers
Service Type > Server Type Required Server type where Redis/Valkey will be installed - Standard: Standard specification commonly used
- For more information on the server types provided by CacheStore(DBaaS), refer to CacheStore(DBaaS) Server Type
Service Type > Planned Compute Required Current status of resources with Planned Compute set - In Use: Number of resources with Planned Compute set that are currently in use
- Settings: Number of resources with Planned Compute set
- Coverage Preview: Amount applied by Planned Compute for each resource
- Create Planned Compute Service: Move to the Planned Compute service application page
- For more information, refer to Apply for Planned Compute
Service Type > Block Storage Required Block Storage settings used by DB according to purpose - Basic OS: Area where DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Please select the storage type and enter the capacity. (For more information on each Block Storage type, see Creating Block Storage)
- SSD: High-performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes using Samsung Cloud Platform KMS (Key Management System) encryption key
- The set Storage type will be applied equally to additional storage
- Capacity should be entered in multiples of 8 within the range of 16 to 5,120
- Please select the storage type and enter the capacity. (For more information on each Block Storage type, see Creating Block Storage)
High Availability Optional Whether to configure High Availability (HA) - Using High Availability (HA) configuration provides Master-Replica configuration, and Replica can be configured with 1 or 2
- Sentinel Port Number: Port number used when connecting to Sentinel
- Port for Master-Replica communication, enter within the range of 1,024 to 65,535
- Number of Replicas: Number of Replicas to be configured
- If 1 is selected, it is configured as Master-Replica-Sentinel
- If 2 is selected, it is configured as Master-Replica-Replica, and Sentinel is automatically installed on the server where Redis is installed
- The server type of Sentinel is set to the minimum specification
Network Required The network where CacheStore(DBaaS) is installed - Select and connect the pre-created VPC and Subnet
- IP can only be generated automatically
Network > Common Settings Required Network settings for servers created by the service - Select if you want to apply the same settings to all servers being installed
- Select pre-created VPC and Subnet
- IP can only be generated automatically
Network > Server-specific settings Required Network settings for servers created by the service - Select to apply different settings for each server being installed
- Select pre-created VPC and Subnet, IP, Public NAT
- Enter the IP for each server
- The Public NAT function is only available if the VPC is connected to the Internet Gateway. If Use is checked, you can select from the reserved IP in the VPC product’s Public IP. For more information, see Creating Public IP
IP Access Control Select Set service access policy - Set access policy for the IP entered on the page, so you don’t need to set Security Group policy separately
- Enter in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32), and click the Add button
- To delete the entered IP, click the x button next to the entered IP
Maintenance period Selection CacheStore(DBaaS) maintenance period - Use is selected to set the day of the week, start time, and duration
- It is recommended to set the maintenance period for stable DB management, and patch work is performed at the set time, resulting in service interruption
- If not used, Samsung SDS is not responsible for any problems that occur due to non-application of patches
Fig. CacheStore(DBaaS) Service Configuration Items- Starts with lowercase English letters, and consists of 3 to 13 characters using lowercase letters, numbers, and special characters (
Database Configuration Required Information Input area, please enter or select the required information.
Classification NecessityDetailed Description Backup Selection Whether to use backup - Use is selected to set the backup file storage period and backup start time
- Backup files are charged separately according to capacity
- The file storage period can be set from 7 to 35 days
- The minute (minutes) when the backup is performed is set randomly, and the backup end time cannot be set
Redis/Valkey Port number mandatory Port number required for Redis/Valkey connection - Port must be entered within the range of 1,024 ~ 65,535
Redis/Valkey password mandatory Password required when connecting to Redis/Valkey - Enter 8-30 characters, including English, numbers, and special characters (excluding
$"‘)
Redis/Valkey password confirmation required Re-enter the password identically Parameter Required Redis/Valkey parameters to use - Query button can be clicked to check detailed information of parameters
- Parameters can be modified after creation is completed, and DB restart is required after modification
Time Zone Required Time zone where the Database will be used Fig. CacheStore(DBaaS) Database Configuration ItemsEnter Additional Information Enter or select the required information in the area.
Classification MandatoryDetailed Description Tag Selection Add Tag - Up to 50 can be added per resource
- Click the Add Tag button and enter or select Key, Value
Table. Additional information input items for CacheStore(DBaaS)
In the Summary panel, review the detailed information and estimated charges, and click the Complete button.
- Once creation is complete, check the created resource on the Resource List page.
Check CacheStore(DBaaS) detailed information
The CacheStore(DBaaS) service allows you to view and modify the entire resource list and detailed information. The CacheStore(DBaaS) details page consists of detailed information, tags, and operation history tabs.
To check the detailed information of the CacheStore(DBaaS) service, follow the next procedure.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- Service Home page, click the CacheStore(DBaaS) menu. Move to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to check the detailed information. Move to the CacheStore(DBaaS) details page.
- CacheStore(DBaaS) details page top shows status information and additional features.
| Division | Detailed Description |
|---|---|
| Cluster Status | Redis cluster status installed
|
| Cluster Control | Buttons that can change the cluster status
|
| Additional features more | Cluster-related management buttons
|
| Service Cancellation | A button to cancel the service |
Detailed Information
On the CacheStore(DBaaS) list page, you can check the detailed information of the selected resource and modify the information if necessary.
| Classification | Detailed Description |
|---|---|
| Server Information | Server information configured in the corresponding 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 |
| Creator | The user who created the service |
| Creation Time | Time when the service was created |
| Modifier | Service information modified user |
| Modified Time | Time when service information was modified |
| Image/Version | Installed Redis/Valkey Image and Version Information |
| Cluster Name | Redis/Valkey server cluster name |
| Planned Compute | Planned Compute settings for current resources
|
| Maintenance period | DB patch work period setting status
|
| Backup | Backup setting status
|
| Redis/Valkey Port number | Port number required for Redis/Valkey connection |
| Time Zone | Redis/Valkey Time Zone |
| Sentinel Port number | Port number for Master and Replica to communicate |
| VIP | Virtual IP information
|
| Network | Network information (VPC, Subnet) where CacheStore (DBaaS) is installed |
| IP Access Control | Service Access Policy Setting
|
| Master & Replica | Master, Replica server type, default OS, additional Disk information
|
| Sentinel | Sentinel server type, basic OS information
|
Tag
On the CacheStore(DBaaS) list page, you can check the tag information of the selected resource, and add, change, or delete it.
| Classification | Detailed Description |
|---|---|
| Tag List | Tag list
|
Work History
CacheStore(DBaaS) list page where you can check the operation history of the selected resource.
| Division | Detailed Description |
|---|---|
| Work History List | Resource Change History
|
CacheStore(DBaaS) resource management
If you need to change or restore the existing setting options of the generated CacheStore(DBaaS) resource, or change the command, you can perform the task from the CacheStore(DBaaS) details page.
Operating Control
If changes occur in the running CacheStore (DBaaS) resource, you can start, stop, and restart it. Also, if HA is configured, you can switch the Master-Replica server through Switch-over.
To control the operation of CacheStore(DBaaS), follow the next procedure.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to control the operation. Move to the CacheStore(DBaaS) details page.
- Check the CacheStore status and complete the change through the control button below.
- Start: The CacheStore service is installed on the server and the CacheStore service is running.
- Stop: CacheStore service can stop the server where CacheStore service is installed.
- Restart: Only the CacheStore service can be restarted.
- Switch Over: You can switch between the Master server and the Replica server.
Synchronizing Service Status
You can synchronize the real-time service status of CacheStore(DBaaS).
To check the service status of CacheStore(DBaaS), follow the next procedure.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to query the service status. Move to the CacheStore(DBaaS) details page.
- Click the 서비스 상태 동기화 button. During the query, the cluster changes to Synchronizing status.
- When the query is complete, the status is updated in the server information item, and the cluster changes to Running status.
Changing Server Type
You can change the configured server type.
To change the server type, follow these steps.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- On the CacheStore(DBaaS) list page, click the resource you want to change the server type for. It moves to the CacheStore(DBaaS) details page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Server Type Edit popup window opens.
- In the Server Type Modification popup window, select the server type and click the OK button.
Cancel CacheStore(DBaaS)
You can cancel unused CacheStore (DBaaS) to reduce operating costs. However, when canceling the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.
To cancel CacheStore(DBaaS), follow the procedure below.
- All Services > Database > CacheStore(DBaaS) menu is clicked. It moves to the Service Home page of CacheStore(DBaaS).
- Service Home page, click the CacheStore(DBaaS) menu. Move to the CacheStore(DBaaS) list page.
- On the CacheStore(DBaaS) list page, select the resource to be canceled and click the Service Cancellation button.
- Once the cancellation is complete, please check if the resource has been cancelled on the CacheStore(DBaaS) list page.
6.2.1 - Managing CacheStore Service
Users can manage CacheStore (DBaaS) through the Samsung Cloud Platform Console.
Managing Parameters
It provides a feature to easily view and modify database configuration parameters.
Viewing Parameters
To view configuration parameters, follow these steps:
- Click the All Services > Database > CacheStore (DBaaS) menu. It moves to the Service Home page of CacheStore (DBaaS).
- Click the CacheStore (DBaaS) menu on the Service Home page. It moves to the CacheStore (DBaaS) List page.
- Click the resource you want to view and modify parameters on the CacheStore (DBaaS) List page. It moves to the CacheStore (DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
Modifying Parameters
To modify configuration parameters, follow these steps:
- Click the All Services > Database > CacheStore (DBaaS) menu. It moves to the Service Home page of CacheStore (DBaaS).
- Click the CacheStore (DBaaS) menu on the Service Home page. It moves to the CacheStore (DBaaS) List page.
- Click the resource you want to view and modify parameters on the CacheStore (DBaaS) List page. It moves to the CacheStore (DBaaS) Details page.
- Click the More button and then click the Parameter Management button. The Parameter Management popup window opens.
- Click the View button in the Parameter Management popup window. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
- If modification is necessary, click the Modify button and enter the modification contents in the custom value area of the parameter to be modified.
- When the input is complete, click the Save button.
Renaming Commands
It provides a function to view and modify Redis OSS/Valkey Command names. To view and modify Command names, follow these steps:
- Click the All Services > Database > CacheStore (DBaaS) menu. It moves to the Service Home page of CacheStore (DBaaS).
- Click the CacheStore (DBaaS) menu on the Service Home page. It moves to the CacheStore (DBaaS) List page.
- Click the resource you want to modify the Command name on the CacheStore (DBaaS) List page. It moves to the CacheStore (DBaaS) Details page.
- Click the More button and then click the Rename-Command button. It moves to the Rename-Command page.
- Click the View button on the Rename-Command page. The View Notification popup window opens.
- When the View Notification popup window opens, click the OK button. It takes some time to view.
- If modification is necessary, click the Modify button and enter the modification contents in the custom value area of the Command to be modified.
- When the input is complete, click the Complete button.
6.2.2 - CacheStore Backup and Recovery
The user can set up backups of CacheStore(DBaaS) through the Samsung Cloud Platform Console and recover with the backed-up files.
CacheStore(DBaaS) backup
CacheStore(DBaaS) provides a data backup function based on its own backup command. It also provides an optimized backup environment for data protection and management through backup history check and backup file deletion functions.
Setting up backup
The method of setting up a backup for CacheStore(DBaaS) is described in CacheStore(DBaaS) creation guide, please refer to it.
To modify the backup settings of the generated resource, follow these steps.
If backup is set, backup will be performed at the specified time after the set time, and additional fees will be incurred depending on the backup capacity.
- If the backup setting is changed to unset, the backup operation will be stopped immediately, and the stored backup data will be deleted and can no longer be used.
- All Services > Database > CacheStore(DBaaS) menu, click. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to set the backup. It moves to the CacheStore(DBaaS) detail page.
- Click the Edit icon of the backup item. The Backup Settings popup window opens.
- If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the OK button.
- If you want to stop the backup setting, uncheck Use in the Backup Setting popup window and click the OK button.
Check Backup History
To check the backup history, follow these steps.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to check the backup history. It moves to the CacheStore(DBaaS) details page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.
Deleting Backup Files
To delete the backup history, follow these steps.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource to check the backup history. It moves to the CacheStore(DBaaS) detail page.
- Click the Backup History button. The Backup History popup window opens.
- Backup History popup window, check the file you want to delete and click the Delete button.
CachStore(DBaaS) recovery
In the event of a failure or data loss, where recovery from a backup file is necessary, the recovery function allows recovery based on a specific point in time.
To recover CacheStore(DBaaS), follow these steps.
- Click All Services > Database > CacheStore(DBaaS) menu. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) menu. It moves to the CacheStore(DBaaS) list page.
- CacheStore(DBaaS) list page, click the resource you want to restore. It moves to the CacheStore(DBaaS) details page.
- Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
- After entering information in the Database recovery configuration area, click the Complete button.
| Classification | Necessity | Detailed Description |
|---|---|---|
| Recovery Type | Required | User sets the point in time to recover
|
| Server name prefix | Required | Server name of the recovery DB
|
| Cluster Name | Required | Cluster name of the recovery DB
|
| Service Type > Server Type | Required | Server type where the recovery DB will be installed
|
| Service Type > Planned Compute | Selection | Current status of resources with Planned Compute set
|
| Service Type > Block Storage | Required | Block Storage setting used by recovery DB
|
| Redis/Valkey Port number | required | Redis/Valkey Port number set in the original DB |
| IP Access Control | Select | Set service access policy
|
| Maintenance period | Select | CacheStore(DBaaS) DB maintenance period
|
| Tag | Selection | Add Tag
|
6.2.3 - CacheStore(DBaaS) server connection
Scenario Overview
CacheStore(DBaaS) connection scenario is a scenario where Bastion host (Virtual Server) and Database service are created, and the DB service is accessed through the Bastion host. To connect to CacheStore (DBaaS) stably in the Samsung Cloud Platform environment, it is necessary to create a Bastion host and use it for network connection. To maintain a stable and high level of security, it is recommended to configure the Database service in a Private Subnet environment and configure the Bastion host in a limited Public Subnet environment.
This scenario largely describes the process of creating a Bastion host and Database service, and configuring the network environment for Bastion host and Database connection, allowing access through a DB connection client.
Scenario Components
You can configure the scenario using the following services.
| Service Group | Service | Detailed Description | |
|---|---|---|---|
| Networking | VPC | A service that provides an independent virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that allows users to subdivide the network according to purpose,size in VPC | |
| Networking | VPC > Public IP | A service that reserves public IP and assigns and returns it to Compute resources | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the internet | |
| Networking | Security Group | A virtual firewall that controls the server’s traffic | |
| Database | CacheStore(DBaaS) | A service that easily creates and manages CacheStore in a web environment | |
| Compute | Virtual Server | Cloud computing optimized virtual server | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- The default policy of Security Group is Deny All, so only allowed IPs should be registered.
- In/Outbound’s All Open(Any IP, Any Port) policy can expose cloud resources to external threats.
- By specifying the necessary IP and Port to set the policy, you can enhance security.
Scenario composition method
To configure the scenario, create the necessary services through the following procedure.
1. Configuring the Network
This describes the process of configuring the network environment for connecting to the Bastion Host and Database services.
1-1. Creating a VPC
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- On the Service Home page, click the Create VPC button. It moves to the Create VPC page.
- VPC Creation page, please enter the information required for service creation.
- IP range should be entered as
192.168.x.0/16.
- IP range should be entered as
- In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
- Once creation is complete, check the created resource on the VPC list page.
1-2. Creating a Subnet
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Subnet menu. It moves to the Subnet list page.
- Click the Subnet Creation button. It moves to the Subnet Creation page.
- Subnet Creation page where you enter the information needed to create a service.
- Subnet type should be selected as General.
- Please select a pre-created VPC.
- IP range should be entered as
192.168.x.0/24.
- In the Summary panel, review the detailed information and estimated charges, and click the Complete button.
- Once creation is complete, check the created resource on the Subnet list page.
1-3. Creating an Internet Gateway
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Internet Gateway menu. Move to the Internet Gateway list page.
- Click the Create Internet Gateway button. It moves to the Create Internet Gateway page.
- Internet Gateway creation page, please enter the required information necessary for service creation.
- Please select a pre-created VPC.
- Select Use in the Firewall usage item.
- In the Summary panel, review the detailed information and the estimated charge amount, and then click the Complete button.
- Once the creation is complete, check the created resource on the Internet Gateway list page.
1-4. Creating a Public IP
- Click All services > Networking > VPC menu. It moves to the Service Home page of VPC.
- Service Home page, click the Public IP menu. It moves to the Public IP list page.
- Public IP Reservation 버튼을 클릭하세요. Public IP Reservation 페이지로 이동합니다.
- Public IP Reservation page, please enter the required information necessary for service reservation.
- In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
- Once creation is complete, check the created resource on the Public IP list page.
1-5. Creating a Security Group
- Click All Services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
- Service Home page, click the Create Security Group button. Move to the Create Security Group page.
- Security Group Creation page, please enter the required information necessary for service creation.
- Check the input information and click the Complete button.
- Once creation is complete, check the created resource on the Security Group list page
2. Creating a Bastion host
This describes the process of configuring the Bastion Host where the database connection client should be installed.
2-1. Creating a Server Keypair
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Keypair menu. It moves to the Keypair list page.
- Create Keypair button will be clicked. It moves to the Create Keypair page.
- Keypair creation page where you enter the required information necessary for service creation.
- Check the creation information and click the Complete button.
- The key download is only available for the first time, and re-issuance is not provided.
- Please make sure to store the downloaded key in a safe place.
2-2. Creating a Bastion Host
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server creation button. Move to the Virtual Server creation page.
- Virtual Server Creation page, please enter the required information necessary for service creation.
- Image is Windows, please select.
- Please select the pre-created VPC and Subnet.
- Click NAT and select the Public IP reserved in 1-4. Public IP 생성하기.
- 2-1. Creating Server Keypair Connect the Keypair created from 2-1. 서버 Keypair 생성하기.
- In the Summary panel, review the detailed information and estimated billing amount, and click the Complete button.
- Once the creation is complete, check the created resource on the Virtual Server list page.
2-3. Check Bastion host connection ID and PW
- Click All Services > Compute > Virtual Server menu. It moves to the Service Home page of Virtual Server.
- Service Home page, click the Virtual Server menu. Move to the Virtual Server list page.
- Virtual Serve list page, click on the resource created in 2-2. Creating a Bastion host. It moves to the detailed information page of the corresponding resource.
- Click the RDP password inquiry button in the Keypair item on the detailed information page. The RDP password inquiry popup window opens.
- RDP password inquiry popup window, attach the keypair file downloaded from 2-1. Server Keypair creation.
- After attaching, click the Password confirmation button. The ID and password required to access the resource will be displayed.
- The ID and Password will be used as information to connect to the Bastion host later in 5-1. Connect to Bastion host.
3. Creating a Database
It describes the process of creating a Database service.
3-1. Creating CacheStore (DBaaS) Service
- All services > Database > CacheStore(DBaaS) menu is clicked. It moves to the Service Home page of CacheStore(DBaaS).
- On the Service Home page, click the CacheStore(DBaaS) creation button. It moves to the CacheStore(DBaaS) creation page.
- CacheStore(DBaaS) creation page, please enter the required information needed for service creation.
- Select and connect to the pre-created VPC and Subnet.
- Enter database-related creation information on the essential information input screen.
- Add the Bastion host IP to the IP access control item.
- Database Port is 2866 by default, but users can also specify it.
- In the Summary panel, review the detailed information and estimated charges, and then click the Complete button.
- Once creation is complete, check the created resource on the CacheStore(DBaaS) list page.
4. Setting Rules
This describes the process of setting rules for users to access the Bastion host and for the Bastion host to access the Database.
4-1. Security Group Add Security Rules
- Click All Services > Networking > Security Group menu. It moves to the Service Home page of Security Group.
- Service Home page, click the Security Group menu. Move to the Security Group list page.
- 1-5. Creating a Security Group Select the Security Group resource created from 1-5. Creating a Security Group. It moves to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Rule tab, click the Add Rule button. It moves to the Add Rule popup window.
- In the Add Rule popup window, enter the following rules and click the OK button
| Direction | Remote | Target Address | Protocol | Port | Description |
|---|---|---|---|---|---|
| Inbound | CIDR | User PC IP | TCP | 3389 (RDP) | Bastion connection PC → Bastion host |
| Outbound | CIDR | DB IP | TCP | Database Port (direct input) | Bastion host → Database |
4-2. Adding IGW Firewall Rules
- Click All services > Networking > Firewall menu. It moves to the Service Home page of Firewall.
- Service Home page, click the Firewall menu. It moves to the Firewall list page.
- Firewall list page, select the Internet Gateway resource name created in 1-3. Internet Gateway creation. It moves to the detailed information page of the corresponding resource.
- Click the Rules tab on the detailed information page. It moves to the Rules tab.
- Rule tab, click the Add Rule button. Move to the Add Rule popup window.
- In the Add Rule popup window, enter the following rules and click the OK button.
| Departure Address | Destination Address | Protocol | Port | Action | Direction | Description |
|---|---|---|---|---|---|---|
| Bastion connection PC IP | Bastion host IP | TCP | 3389(RDP) | Allow | Inbound | User PC → Bastion host |
5. Connecting to the Database
This explains the process of a user accessing the Database through a DB connection client program.
This guide provides instructions on how to connect using Another Redis Desktop Manager. There are various database client programs and CLI utilities, so you can also install and use the tools that are suitable for the user.
5-1. Connecting to the Bastion host
- Run Remote Desktop Connection in the Windows environment of the PC you want to connect to the Bastion host, enter the NAT IP of the Bastion Host, and click the Connect button.
- When the remote desktop connection is successful, the User Credential Input Window opens. Enter the ID and Password confirmed in 2-3. Check Bastion host access ID and PW and click the Confirm button.
5-2. Install DB connection client program (Another Redis Desktop Manager) on the Bastion host
- Download another Redis Desktop Manager program.
- Another Redis Desktop Manager program download path: https://github.com/qishibo/AnotherRedisDesktopManager/releases
- Connect the hard drive of the user PC to upload the file to the Bastion host.
- Click the Details button for local devices and resources items in the Local Resources tab of the remote desktop connection.
- Select the local disk where the file was downloaded to the drive and click the Confirm button.
- Download the file, copy it to the Bastion Host, and upload it, then click on the pgAdmin installation file to install it.
5-3. Using DB connection client program(Another Redis Desktop Manager) to connect to Database
- Run Another Redis Desktop Manager and click New Connection. The New Connection popup window will appear.
- New Connection popup window, enter the Database server information created in 3-1. CacheStore(DBaaS) 서비스 생성하기 and click the OK button.
Required Input Element Items Input Value Host Database Server IP Port Database Port Password Database password Connection Name Custom (ex. Service Name) DB Connection Client Program Input Items - After connecting, you can perform basic information checks on Redis, data management, and CRUD operations on keys.
6.3 - API Reference
6.4 - CLI Reference
6.5 - Release Note
CacheStore(DBaaS)
- CacheStore(DBaaS) feature added
- CacheStore(DBaaS) New Image Added
- Redis OSS was forked and developed as an open-source, Valkey image support
- 2nd generation server type added
- Intel 4th generation (Sapphire Rapids) processor-based 2nd generation (db2) server type added. For more information, see CacheStore(DBaaS) server type
- Backup Alert Feature provided
- Provides notification features for backup success and failure. For more information, see Creating a Notification Policy
- Block Storage type added HDD, HDD_KMS type
- Samsung Cloud Platform common feature changes
- Account, IAM and Service Home, tags, etc. reflected common CX changes.
- The service name is changed to CacheStore(DBaaS).
- Block Storage type has an option to select encrypted storage for volumes added.
- The Role Switch (Active ↔ Standby) function has been added to the Active DB and Standby DB composed of duplication.
- The cloud monitoring service is linked, so DB instance performance and log monitoring are possible.
- Depending on the server type selected by the customer, Planned Compute policy setting is possible.
- A Redis(DBaaS) service that can easily create and manage Redis OSS in a web environment has been released.










