How-to guides
Users can create the service by entering the required information for MySQL (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Resource-specific Monitoring Service Application Guide
- New Resources: Resources created after the March 2026 service improvement work are provided with default monitoring using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide monitoring concurrently through the Cloud Monitoring service and the ServiceWatch service.
- During the parallel operation period, we need to prepare for the Servicewatch transition. *
Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (ex. Check the event policy, etc., and perform tasks such as resetting the ServiceWatch service, then complete them.
Cloud Monitoring Service Phased Termination Schedule Notice
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the November service termination, Cloud Monitoring data cannot be accessed. * Be sure to complete the ServiceWatch migration within the parallel operation period**
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in ServiceWatch 개요.
MySQL(DBaaS) Create
You can create and use a MySQL (DBaaS) service from the Samsung Cloud Platform Console.
- Before creating the service, configure the VPC’s Subnet type as General.
- If the subnet type is Local, the creation of the corresponding Database service is not possible.
- When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to a statistical collection environment.
- This service is provided on a Single-AZ basis.
To create MySQL (DBaaS), follow the steps below.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) Create button. 2. Create MySQL (DBaaS) Navigate to the page.
- MySQL(DBaaS) Creation page: enter the information required to create the service and select detailed options.
- In the Image and version selection area, select the required information.
Category Required statusDetailed description Image version Required Provide a list of MySQL (DBaaS) versions Table. MySQL (DBaaS) Image and version selection items - Enter or select the required information in the Service Information Input area.
Category Required statusDetailed description Server name Prefix Required Server name where the DB will be installed - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (
-) be entered with 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
Cluster name Required cluster name composed 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 for DB installation - Standard: Standard specification commonly used
- High Capacity: Large-capacity server with 24vCore or more
- For detailed information about the server types provided by MySQL (DBaaS), see MySQL(DBaaS) server type
Service Type > Planned Compute Selection Planned Compute가 설정된 자원 현황 - 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 Planned Compute 신청하기
Service Type > Block Storage Required Block Storage settings used by the DB according to purpose - Base OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
- SSD: High‑performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes that use Samsung Cloud Platform KMS (Key Management System) encryption keys
- The configured storage type is applied identically to additional storage
- Capacity must be entered as a multiple of 8 within the range 16–5,120
- Since executing SQL or monthly batch jobs can cause large sorts that may interrupt service, a separate TEMP storage should be allocated and used
- Select a storage type and then enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
- Add: Storage areas for DATA, Archive, TEMP, Backup data
- After selecting Use, enter the storage’s purpose and capacity
- The storage type is applied the same as the type set for DATA, and capacity can be entered as a multiple of 8 within the range 16–5,120
- Click the Add button to add storage, or click the x button to delete. Up to 9 can be added
- Temporarily store backup data in BACKUP storage before transmitting it
- If the data to be backed up exceeds 100 GB and undergoes frequent changes, it is recommended to add a separate BACKUP storage for reliable backup. Set the backup capacity to about 60 % of the DATA capacity
- If a BACKUP storage is not added, the
/tmparea is used, and backup will fail if there is insufficient capacity
- For each service, Archive, TEMP, and BACKUP storages are allocated only one Block Storage each
Redundant configuration Selection Redundancy configuration status - When redundancy configuration is used, the DB instance is set up as an Active DB and a Standby DB
Network > Common Settings Required Network settings for servers deployed by the service - Select when you want to apply the same settings to all deployed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Each server’s IP is generated automatically
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select from reserved IPs in the VPC product’s Public IP. For more information, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select when you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select from reserved IPs in the VPC product’s Public IP. For more information, see Public IP 생성하기
IP access control Selection Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
- Enter the IP in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the IP
Maintenance period Selection DB maintenance window - If you select Use, set the day, start time, and duration
- The maintenance window is a feature that lets the user define the time slot for performing patch operations, and any patch work within that period must be carried out by the user.
- We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
Table. MySQL(DBaaS) service configuration items - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (
- Enter required database configuration information In this section, enter or select the necessary information.
Category RequiredDetailed description Database name Required Server name applied when installing DB - Starts with an English letter and uses English letters and numbers, entered in 3 to 20 characters
Database username Required DB user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- Restricted database user names can be viewed in the Console
Database password Required Password to use when accessing the DB - Include English letters, numbers, and special characters (
“‘excluded) and enter 8~30 characters
Check database password Required Re-enter the same password to use for DB access Database Port number Required Port number required for DB connection - Enter DB port within the range 1200 ~ 65535
Backup > Use Selection: Backup usage - Select Use to set the backup file retention period, backup start time, and Archive backup interval
Backup > Retention Period Selection Backup retention period - Select the backup retention period. Set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Period Selection Backup start time - Select backup start time
- The minute(s) (minutes) at which the backup runs is set randomly, and the backup end time cannot be set
Backup > Archive backup schedule Selection Archive backup interval - Select the Archive backup interval
- The Archive backup interval is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Parameter Required Parameters for the DB - View button can be clicked to view the parameter’s detailed information
- Parameters can be modified after the DB creation is complete, and the DB must be restarted after modification
DB character set Required Character encoding to use for the DB Table case sensitivity Selection Case sensitivity of DB table Time zone Required Standard time zone used by the database ServiceWatch log collection Selection ServiceWatch log collection status - Select Use to configure the ServiceWatch log collection feature
- It is provided free of charge up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB.
- When collected, log groups and log streams are created automatically, and they cannot be deleted until the resource is removed.
- To prevent exceeding 5 GB, direct deletion of log data or shortening the retention period is recommended.
Table. MySQL(DBaaS) Database configuration items - In the Additional Information Input area, enter or select the required information.
Category Required statusDetailed description tag Selection Add Tag - Up to 50 can be added per resource
- Add Tag button, then enter or select Key, Value values
Table. MySQL (DBaaS) additional information input fields
- In the Image and version selection area, select the required information.
- Summary Check the detailed information and estimated charges generated in the panel, and click the Create button.
- Once creation is complete, verify the created resource on the Resource List page.
Check MySQL(DBaaS) detailed information
The MySQL (DBaaS) service allows you to view and edit the entire resource list and detailed information. MySQL(DBaaS) Details page consists of the Details, Tags, Activity History tabs, and for databases with a Replica configured, the Replica Information tab is added.
To view detailed information about the MySQL (DBaaS) service, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- On the MySQL(DBaaS) List page, click the resource to view detailed information. 3. MySQL(DBaaS) Details Go to the page.
- MySQL(DBaaS) Details At the top of the page, status information and 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 an operational 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 restarting
- Running: Cluster is operating normally
- Starting: Cluster is starting
- Stopped: Cluster is stopped
- Stopping: Cluster is being stopped
- Synchronizing: Cluster is synchronizing
- Terminating: Cluster is being terminated
- Unknown: Cluster status is unknown
- If it occurs continuously, contact the administrator
- Upgrading: Cluster is being upgraded
Cluster control Buttons to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to Active
View more features Cluster-related management buttons - Service status synchronization: Real-time DB service status lookup
- Backup history: If backup is configured, check whether it runs correctly and view its history
- Database recovery: Recover the DB based on a specific point in time
- Parameter management: Ability to view and modify DB configuration parameters
- Replica configuration: Set up a read‑only cluster as a Replica
- Replica configuration (Other-Region): Configure a disaster‑recovery Replica in another region; the button is disabled if the account has no region to configure
- DB user management: View and manage DB account (user) information registered in the DB
- DB access control management: Register and revoke allowed IPs based on DB accounts registered in the DB
- Archive management: Set archive file retention periods and configure archive mode
- DB Log export: Export stored logs to the user’s Object Storage via Audit settings
- Migration configuration: Provides migration functionality using replication
- Block Storage usage management: Provides usage query functionality per Block Storage type
- OS (Kernel) upgrade: Upgrade the OS kernel version
Service cancellation Cancel service button Table. MySQL (DBaaS) status information and additional features
- MySQL(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
Detailed Information
MySQL(DBaaS) List page allows you to view detailed information of the selected resource and edit the information if needed.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation Date/Time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date and time | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster type | Cluster type (Master Cluster, Replica Cluster, Migration Cluster) |
| Cluster name | Cluster name of the DB servers |
| Master cluster name | Replica’s Master cluster name
|
| Database name | Server name applied during DB installation |
| Database username | DB user name |
| Planned Compute | Resource status with Planned Compute configured
|
| Maintenance period | DB Maintenance Period Status
|
| Backup | Backup Configuration Status
|
| ServiceWatch log collection | ServiceWatch Log Collection Configuration Status
|
| DB character set | Encoding method to be used for the DB |
| Table case sensitivity | Case sensitivity of DB table |
| Time zone | Standard time zone used by the database |
| VIP | Virtual IP information
|
| Network | Network information of the DB installation (VPC, Subnet, VIP, NAT IP(VIP)) |
| Service access policy configuration
- If you need to add or remove an IP, click the Edit icon to configure
- If you need to modify the server type, click the Edit icon next to the server type to configure it. Refer to the server type modification procedure in 서버 타입 변경하기
- Modifying the server type requires a server reboot
- If you need to expand storage, click the Edit icon next to the storage capacity to expand it. Refer to the storage expansion procedure in 스토리지 증설하기
- If you need to add storage, click the Add Disk button next to the additional Disk to add it. Refer to the storage addition procedure in 스토리지 추가하기
Replica information
Replica information tab is enabled only when a Replica is configured in the cluster. Replica information tab allows you to view the Master cluster name, replica count, and Replica status.
| Category | Detailed description |
|---|---|
| Master information | Name of the Master cluster |
| Replica count | Number of Replicas created in the Master cluster |
| Replica status | Replica server status in the Master cluster
|
tag
MySQL(DBaaS) List page lets you view the tag information of the selected resource, and you can add, change, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Job History
On the MySQL(DBaaS) List page, you can view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource change history
|
MySQL(DBaaS) Managing Resources
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 task on the MySQL(DBaaS) Detailed Information page.
Operation Control
If changes occur to a running MySQL (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch the Active‑Standby servers via a switch‑over.
To control the operation of MySQL (DBaaS), follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Go to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- MySQL(DBaaS) List On the page, click the resource to control its operation. 3. MySQL(DBaaS) Details Go to the page.
- Check the MySQL (DBaaS) status and complete the change using the control button below.
- Start: DB service is installed on the server and the DB service is running (Running).
- Stop: The server where the DB service is installed and the DB service 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 MySQL (DBaaS).
To view the service status of MySQL(DBaaS), follow these steps.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- MySQL(DBaaS) List On the page, click the resource to view the service status. 3. MySQL(DBaaS) Details Go to the page.
- Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
- When the query completes, the status in the server information item is updated, and the cluster changes to Running state.
Change Server Type
You can change the configured server type.
To change the server type, follow these steps.
- If you modify the server type, a server restart is required. * Please separately verify any SW license modifications or SW settings and their implementation due to spec changes.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- MySQL(DBaaS) List page, click the resource whose server type you want to change. 3. Navigate to the MySQL(DBaaS) Details page.
- Click the Edit icon for the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Edit Server Type In the popup window, select the server type, then click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. For a redundant DB setup, all redundant servers are added simultaneously.
- It is applied in the same way as the Storage type selected when creating the service.
- For a high‑availability configured database, adding storage is applied simultaneously to the storage of both the Active DB and the Standby DB.
- A Replica’s storage cannot be larger than the primary’s storage. * Please expand the Master storage after expanding the Replica storage.
- When adding Archive/Temp storage, the DB restarts and is temporarily unavailable.
To add storage, follow these steps.
- All Services > Database > MySQL(DBaaS) Click the menu. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- On the MySQL(DBaaS) List page, click the resource to add storage. 3. MySQL(DBaaS) Details Go to the page.
- Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.
Expanding storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In 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. 1. Navigate to the Service Home page of MySQL (DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- On the MySQL(DBaaS) List page, click the resource to change the server type. 3. MySQL(DBaaS) Details Go to the page.
- Click the Edit icon for the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage popup opens.
Terminate MySQL(DBaaS)
You can cancel unused MySQL (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be discontinued immediately, so you should proceed with the termination only after fully considering the impact of the service interruption.
- Replica is not deleted together. * If you delete the replica as well, please cancel it separately from the resource list.
- If you terminate the DB, all stored data and any configured backup data will be deleted.
To cancel MySQL (DBaaS), follow the steps below.
- Click the All Services > Database > MySQL(DBaaS) menu. 1. Navigate to the Service Home page of MySQL(DBaaS).
- On the Service Home page, click the MySQL(DBaaS) menu. 2. MySQL(DBaaS) List Navigate to the page.
- MySQL(DBaaS) List page, select the resource to cancel, and click the Cancel Service button.
- After termination is complete, verify on the MySQL(DBaaS) list page that the resource has been terminated.