How-to guides
Users can create the service by entering the required information for Vertica (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 terminated.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service by Resource
- New Resources: Resources created after the service improvement work in July 2026 are provided with monitoring using the ServiceWatch service by default.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring via Cloud Monitoring service and ServiceWatch service
- During the parallel operation period, you must prepare for the Servicewatch transition *
Performance and log data backup, user-configured settings linked with existing Cloud Monitoring (e. Check (e.g., event policies) and perform tasks such as resetting the ServiceWatch service, then complete them.
Notice of the phased termination schedule for Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Region | Cloud Monitoring console URL |
|---|---|
| kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All Cloud Monitoring services, including the API, are being permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All Cloud Monitoring services, including the API, are being permanently discontinued.
For detailed information about ServiceWatch, please refer to the ServiceWatch 개요.
Create Vertica(DBaaS)
You can create and use the Vertica (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 corresponding Database service cannot be created.
- 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 Vertica (DBaaS), follow the steps below.
All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica(DBaaS).
On the Service Home page, click the Vertica(DBaaS) Create button. 2. Go to the Create page.
Vertica(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 Vertica (DBaaS) versions Table. Vertica (DBaaS) image and version input fields - Enter or select the required information in the Service Information Input area.
Category Required statusDetailed description Server name Prefix required Server name where Vertica will be installed - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (
-) input 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is appended to create the actual server name
Cluster name required Cluster name of the servers - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Number of nodes Required Number of data nodes - Enter the number of nodes in the range of 1-10
- If you input the number of nodes as 2 or more and configure the cluster, you secure high availability (High Availability)
Service Type > Server Type required Data node server type - Standard: Standard specification commonly used
- High Capacity: Large-capacity server with 24 vCores or more
- For detailed information about the server types provided by Vertica (DBaaS), see Vertica(DBaaS) Server Type
Service Type > Planned Compute Select Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage preview: Amount applied per resource by Planned Compute
- Apply for Planned Compute service: Go to the Planned Compute service application page
- For more details, see Planned Compute Apply
Service Type > Block Storage required Block Storage type to be used for data nodes - Base OS: The area where the engine is installed
- DATA: Data file storage area
- After selecting the storage type, enter the capacity (for details on each Block Storage type, refer to Block Storage 생성하기)
- SSD: Standard Block Storage
- SSD_KMS: Additional encrypted volume using 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 of 16 to 5,120
- After selecting the storage type, enter the capacity (for details on each Block Storage type, refer to Block Storage 생성하기)
- Add: DATA, Backup data storage area
- After Use, enter the purpose and capacity
- To add storage, click the Add button; to delete, click the x button. Up to 9 can be added
- Capacity can be entered as a multiple of 8 within the range of 16 to 5,120, and up to 9 can be created
Management Console Select If you select Use, you can set the Node’s server type and Block Storage settings for cluster management and monitoring. Management Console > Server Type Required Select Data Node Server Type for Cluster Management and Monitoring Management Console > Block Storage required Select the Block Storage type to be used for data nodes for cluster management and monitoring Network > Common Settings required Network settings for servers generated by the service - Select this when you want to apply the same settings to all servers being installed
- Select a pre‑created VPC and Subnet
- Each server’s IP is generated automatically
- Public NAT setting is only available in per‑server configuration
Network > Server-specific Settings required Network settings for servers generated by the service - Select this option to apply different settings to each installed server
- Select a pre-created VPC and Subnet
- IP: Enter the IP address for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Selecting Use allows you to choose a reserved IP from the VPC product’s Public IP pool. For more information, see Public IP 생성하기.
IP access control Select 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 in IP format (e.g.,
192.168.10.1) or CIDR format (e.g.,192.168.10.0/24,192.168.10.1/32), then click the Add button
- To delete an entered IP, click the x button next to the IP
Maintenance Period Select DB maintenance window - If you select Use, set the day of week, start time, and duration
- The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and patch tasks within that time are performed directly by the user.
- We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
Table. Vertica (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 the area, enter or select the necessary information.
Category Required statusDetailed description Database name Required Server name applied during DB installation - Must start with an English letter and be entered using English letters and numbers, 3 to 20 characters long
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 checked 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
Database password verification Required Re-enter the same password to be used for DB access. Database Port number required Port number required for DB connection - Enter the DB port within the range 1200 ~ 65535
Backup > Use Select Node backup usage - Select Use to choose node backup retention period and backup start time
Backup > Retention Period Select Backup retention period - Select the backup retention period. Set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Time Select Backup start time - Select backup start time
- The minute(s) when the backup runs is set randomly, and the backup end time cannot be set
ServiceWatch log collection Selection ServiceWatch log collection status - Select Enable to configure the ServiceWatch log collection feature
- Provided free up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB
- When collected, log groups and log streams are created automatically, and they cannot be deleted until the resources are removed
- To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
License Key required Enter the Vertica License Key owned by the customer - If the entered license key is not valid, service creation is not possible
DB Locale required Settings related to string handling, numeric/currency/date/time display formats, etc., for use with Vertica (DBaaS) - The database is created with default settings based on the selected locale
Time zone required Standard time zone to use with Vertica (DBaaS) Table. Vertica (DBaaS) Required Configuration Items - In the Additional Information Input area, enter or select the required information.
Category whether requiredDetailed description tag Selection Add Tag - Up to 50 can be added per resource
- After clicking the Add Tag button, enter or select Key, Value values
Table. Vertica (DBaaS) Additional Information Input Fields
- In the Image and Version Selection area, select the required information.
Summary Check the detailed information and estimated billing amount generated in the panel, and click the Create button.
- When creation is complete, check the created resource on the Resource List page.
Vertica(DBaaS) Check detailed information
The Vertica (DBaaS) service lets you view and modify the complete resource list and detailed information. Vertica(DBaaS) Details page consists of the Detailed Information, Tags, Job History tabs.
To view detailed information about the Vertica (DBaaS) service, follow these steps.
- All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica(DBaaS).
- On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Go to the page.
- Vertica(DBaaS) List Click the resource to view detailed information on the page. 3. Vertica(DBaaS) Details Navigate to the page.
- Vertica(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
Category Detailed description Cluster status Cluster status - Creating: Creating the cluster
- Editing: Changing the cluster to an operational state
- Error: The cluster encountered a failure during operation
- If it occurs continuously, contact the administrator
- Failed: The cluster failed during creation
- Restarting: Restarting the cluster
- Running: The cluster is operating normally
- Starting: Starting the cluster
- Stopped: The cluster is stopped
- Stopping: The cluster is in the process of stopping
- Synchronizing: Synchronizing the cluster
- Terminating: Deleting the cluster
- Unknown: The cluster status is unknown
- If it occurs continuously, contact the administrator
- Upgrading: Upgrading the cluster
Cluster control Button to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
View more features Cluster management buttons - Service status synchronization: Real-time DB service status lookup
- Backup history: When backup is configured, check whether the backup executed correctly and view its history
- Database recovery: Recover the DB based on a specific point in time
Service cancellation Service cancellation button Table. Vertica (DBaaS) status information and additional features
- Vertica(DBaaS) Details At the top of the page, status information and information about additional features are displayed.
Detailed Information
On the Vertica(DBaaS) List page, you can 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 name | Cluster name of the configured servers |
| 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
|
| Managed Console | Managed Console resource status configured during DB installation |
| Network | Installed network information (VPC, Subnet) |
| IP access control | Service access policy settings
|
| time zone | Standard time zone for Vertica (DBaaS) DB usage |
| License | Vertica(DBaaS) license information |
| Server Information | Data/Console server type, base OS, additional Disk information
|
Tag
On the Vertica(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
|
Job History
Vertica(DBaaS) List page allows you to view the operation history of the selected resource.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Vertica(DBaaS) Managing Resources
If you need to change the existing configuration options of a created Vertica(DBaaS) resource or add storage, you can perform the task on the Vertica(DBaaS) Details page.
Control Operation
If changes occur to a running Vertica (DBaaS) resource, you can start, stop, or restart it.
To control the operation of Vertica (DBaaS), follow the steps below.
- All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Vertica(DBaaS) Service Home page.
- On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Go to the page.
- Vertica(DBaaS) List page, click the resource to control its operation. 3. Vertica(DBaaS) Details Navigate to the page.
- Check the Vertica (DBaaS) status and complete the change using the control button below.
- Start: Vertica (DBaaS) service is installed on the server and Vertica (DBaaS) service is running (Running).
- Stop: The server where the Vertica(DBaaS) service is installed and the Vertica(DBaaS) service will be stopped (Stopped).
- Restart: Only the Vertica(DBaaS) service will be restarted.
Synchronize service status
You can synchronize the real-time service status of Vertica (DBaaS).
To check the service status of Vertica (DBaaS), follow these steps.
- Click the All Services > Data Analytics > Vertica(DBaaS) menu. 1. Navigate to the Service Home page of Vertica(DBaaS).
- On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Go to the page.
- On the Vertica(DBaaS) List page, click the resource to view the service status. 3. Vertica(DBaaS) Details Navigate to the page.
- Click the Service Status Synchronization button. 4. During the query, 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.
- If the server type is configured as Standard, it cannot be changed to High Capacity. * If you want to change to High Capacity, create a new service.
- If you change the server type, a server restart is required. * Please separately verify any software license modifications or software settings and their implementation due to server specification changes.
To change the server type, follow these steps.
- All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica(DBaaS).
- Click the Vertica(DBaaS) menu on the Service Home page. 2. Vertica(DBaaS) List Navigate to the page.
- On the Vertica(DBaaS) List page, click the resource to change the server type. 3. Vertica(DBaaS) Details Go to the page.
- Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Edit Server Type 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, you can add additional storage. In a high‑availability configuration (HA cluster), expanding or adding storage capacity is applied simultaneously to all databases.
To add storage, follow the steps below.
- All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica(DBaaS).
- On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Navigate to the page.
- On the Vertica(DBaaS) List page, click the resource to add storage. 3. Vertica(DBaaS) Details Navigate to the page.
- Click the Add Disk button at the bottom of the details. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.
Expand storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. You can expand storage without stopping Vertica (DBaaS), and if it is configured as a cluster, all nodes are expanded simultaneously.
To increase storage capacity, follow the steps below.
- All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica(DBaaS).
- On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Navigate to the page.
- Click the resource to change the server type on the Vertica(DBaaS) List page. 3. Vertica(DBaaS) Details Go to the page.
- Click the Edit button for the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage The popup window opens.
- Add Storage Modification After entering the expansion capacity in the popup window, click the Confirm button.
Change Recovery DB Instance Type
After the DB recovery is complete, you can change the instance type on the Recovery details screen.
Recovery DB To change the instance type, follow the steps below.
- All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Vertica(DBaaS) Service Home page.
- Click the Vertica(DBaaS) menu on the Service Home page. 2. Vertica(DBaaS) List Go to the page.
- On the Vertica(DBaaS) List page, click the resource to change the Recovery DB instance type. 3. Vertica(DBaaS) Details Navigate to the page.
- Change Instance Type button, click it. 4. Change Instance Type A confirmation dialog will appear.
- The DB instance type is changed from Recovery to Active to perform the same function as a single DB.
Vertica(DBaaS) Terminate
You can terminate unused Vertica (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact of the service interruption.
To cancel Vertica (DBaaS), follow the steps below.
- All Services > Data Analytics > Vertica (DBaaS) Click the menu. 1. Go to the Service Home page of Vertica (DBaaS).
- On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Navigate to the page.
- On the Vertica(DBaaS) List page, select the resource to cancel, and click the Service Termination button.
- When the termination is complete, check on the Vertica(DBaaS) list page whether the resource has been terminated.