Compute

• 1: Virtual Server
• 1.1: Overview
• 1.1.1: Server Type
• 1.1.2: Monitoring Metrics
• 1.1.3: ServiceWatch Metrics
• 1.2: How-to guides
• 1.2.1: Image
• 1.2.2: Keypair
• 1.2.3: Server Group
• 1.2.4: Change IP
• 1.2.5: Configure Linux NTP
• 1.2.6: Configure RHEL Repo and WKMS
• 1.2.7: Install ServiceWatch Agent
• 1.3: API Reference
• 1.4: CLI Reference
• 1.5: Release Note
• 2: Virtual Server Auto-Scaling
• 2.1: Overview
• 2.1.1: Monitoring Metrics
• 2.1.2: ServiceWatch Metrics
• 2.2: How-to guides
• 2.2.1: Launch Configuration
• 2.2.2: Manage Policy
• 2.2.3: Manage Schedule
• 2.2.4: Manage Notification
• 2.3: API Reference
• 2.4: CLI Reference
• 2.5: Release Note
• 3: GPU Server
• 3.1: Overview
• 3.1.1: Server type
• 3.1.2: Monitoring Metrics
• 3.1.3: ServiceWatch Metrics
• 3.2: How-to guides
• 3.2.1: Manage Image
• 3.2.2: Manage Keypair
• 3.2.3: Use Multi-instance GPU on GPU Server
• 3.2.4: Use NVSwitch on GPU Server
• 3.2.5: Install ServiceWatch Agent
• 3.3: API Reference
• 3.4: CLI Reference
• 3.5: Release Note
• 4: Bare Metal Server
• 4.1: Overview
• 4.1.1: Server Type
• 4.1.2: Monitoring Metrics
• 4.2: How-to guides
• 4.2.1: Install ServiceWatch Agent
• 4.2.2: Setting up RHEL Repo and WKMS
• 4.3: API Reference
• 4.4: CLI Reference
• 4.5: Release Note
• 5: Multi-node GPU Cluster
• 5.1: Overview
• 5.1.1: Server type
• 5.1.2: Monitoring Metrics
• 5.2: How-to guides
• 5.2.1: Manage Cluster Fabric
• 5.2.2: Install ServiceWatch Agent
• 5.2.3: Multi-node GPU Cluster Service Scope and Inspection Guide
• 5.3: Release Note
• 6: Cloud Functions
• 6.1: Overview
• 6.1.1: ServiceWatch Metrics
• 6.2: How-to guides
• 6.2.1: Configure Trigger
• 6.2.2: Blueprint Detailed Guide
• 6.2.3: Integrate PrivateLink Service
• 6.2.4: Resource-based Policy Guide
• 6.3: API Reference
• 6.4: CLI Reference
• 6.5: Release Note
• 7: Virtual Server DR
• 7.1: Overview
• 7.2: Release Note
• 8: Block Storage
• 8.1: Overview
• 8.1.1: Monitoring Metrics
• 8.2: How-to guides
• 8.2.1: Connect to Server
• 8.2.2: Use Snapshot
• 8.2.3: Move Volume
• 8.3: API Reference
• 8.4: CLI Reference
• 8.5: Release Note

1 - Virtual Server

1.1 - Overview

Service Overview

Virtual Server is a cloud computing-optimized virtual server that lets you freely allocate the amount you need at the required time without having to purchase infrastructure resources such as CPU and memory individually. In a cloud environment, you can use resources with optimized performance according to your computing purpose, such as development, testing, and application execution.

Features

• Easy and convenient computing environment setup: Through a web-based Console, users can easily perform self-service provisioning of Virtual Servers, as well as resource and cost management. If you need to change the capacity of major resources such as CPU or Memory while using a Virtual Server, you can easily scale up or down without operator intervention.

• Providing various types of services: Provides virtualized vCore/Memory resources according to predefined server types (1~128 vCore).

  • General Virtual Server: Provides commonly used computing specs (up to 16 vCore, 256 GB)
  • High-capacity Virtual Server: Provided when resources larger than the standard Virtual Server spec are needed.

• Strong Security Implementation: By using the Security Group service, you can control inbound/outbound traffic communicating with the external Internet or other VPCs (Virtual Private Cloud) to securely protect the server. Additionally, real-time monitoring enables stable operation of computing resources.

Service Architecture Diagram

Provided features

Virtual Server provides the following features.

• Auto Provisioning and Management: Provides Virtual Server provisioning, resource management, and cost management functions through a web-based Console. If you need to change the capacity of major resources such as CPU or Memory while using Virtual Server, you can modify the server type immediately using the server type modification feature.
• Standard Server Types and Image Provision: Provides virtualized vCore/Memory resources according to standard server types, and offers standard OS images.
• Storage Connection: Provides additional attached storage beyond the OS disk. Block Storage, File Storage, and Object Storage can be attached and used.
• Network Connection: You can connect the standard subnet/IP settings of the Virtual Server and the Public NAT IP. Provides a local subnet connection for inter-server communication. This can be modified on the detail page.
• Security Group Application: Use the Security Group service to control inbound and outbound traffic communicating with external internet or other VPCs, thereby securely protecting the server.
• Monitoring: You can view monitoring information for computing resources such as CPU, Memory, and Disk through the Cloud Monitoring service.
• Backup and Recovery: You can back up and restore the Virtual Server Image using the Backup service.
• Cost Management: You can create, stop, or terminate servers as needed, and since billing is based on actual usage time, you can monitor costs according to consumption.
• ServiceWatch Service Integration: You can monitor data using the ServiceWatch service.

Component

Virtual Server provides standard server types and standard OS images. Users can select and use them according to the desired service scale.

Image

You can create and manage images. The main features are as follows.

• Image creation: You can create an Image from the configuration of a Virtual Server you are using, and you can also create an Image by uploading your Image file to Object Storage.
• Create Shared Image: You can create an Image with Visibility set to Private as a Shared Image that can be shared.
• Share with another Account: You can share the Image with another Account.
• Refer to the How-to guides > Image document for how to create and use images.

Keypair

To ensure a more secure OS login, we strengthen security by providing a Key Pair instead of the ID/Password entry method. The main features are as follows.

• Keypair creation: Generate a user credential to connect to the Virtual Server.
• Retrieve Public Key: You can load a file or manually enter the public key to retrieve it.
• Refer to the How-to guides > Keypair document for creating and using keypairs.

Server Group

Through Server Group settings, you can position the Block Storage added when creating a Virtual Server close to or distributed across racks and hosts. The main features are as follows.

• Server Group Creation: You can set Virtual Servers belonging to the same Server Group as Anti-Affinity(Distributed placement), Affinity(Proximate placement), or Partition(Virtual Server and Block Storage distributed placement).
• Refer to the How-to guides > Server Group document for how to create and use Server Groups.

OS Image provided version

The OS images provided by Virtual Server are as follows

Server type

The server types supported by Virtual Server are as follows. For detailed information about server types, see Virtual Server Server Types.

Standard s1v2m4

Constraints

Preliminary Service

This is a list of services that need to be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

1.1.1 - Server Type

Virtual Server server type

Virtual Server provides server types that match the intended use. Server types consist of various combinations such as CPU, Memory, and Network Bandwidth. The host server used for a Virtual Server is determined by the server type selected when creating the Virtual Server. Please choose a server type based on the specifications of the application you plan to run on the Virtual Server.

The server types supported by Virtual Server are as follows.

Standard s1v2m4

s1 server type

The s1 server type of Virtual Server is offered with standard specifications (vCPU, Memory) and is suitable for various applications.

• First generation of Samsung Cloud Platform v2: Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor with up to 3.3 GHz
• Supports up to 16 vCPUs and 256 GB of memory
• Maximum networking speed of 12.5 Gbps

s2 server type

The Virtual Server s2 server type is offered with standard specifications (vCPU, Memory) and is suitable for various applications.

• Samsung Cloud Platform v2, 2nd generation: Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H Processor up to 3.2 GHz
• Supports up to 16 vCPUs and 256 GB of memory
• Maximum networking speed of 12.5 Gbps

h2 Server Type

The h2 server type of Virtual Server is offered with high-capacity specifications and is suitable for applications that require large-scale data processing.

• Second generation of Samsung Cloud Platform v2: Intel 4th‑generation (Sapphire Rapids) Xeon Gold 6448H processor up to 3.2 GHz
• Supports up to 128 vCPUs and 1,536 GB of memory
• Networking speed up to 25 Gbps

1.1.2 - Monitoring Metrics

Virtual Server Monitoring Metrics

The table below shows the monitoring metrics of Virtual Server that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

Provides basic monitoring metrics even without installing an agent, as shown below table. Please check the Virtual Server monitoring metrics (default). Additionally, the metrics that can be viewed by installing the Agent are in the table below. Virtual Server additional monitoring metrics (Agent installation required)** Please refer to it.

For Windows OS, memory-related metrics can only be viewed after installing the Agent.

1.1.3 - ServiceWatch Metrics

Virtual Server sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at 5‑minute intervals. If detailed monitoring is enabled, you can view data collected at 1‑minute intervals.

See How-to guides > ServiceWatch Enable Detailed Monitoring for instructions on enabling detailed monitoring of Virtual Server.

Basic Metrics

The following are the basic metrics for the Virtual Server namespace.

The indicators whose names are displayed in bold below are the indicators selected as key metrics among the default metrics provided by Virtual Server. The key metrics are used to build service dashboards that are automatically generated for each service in ServiceWatch. They can also be viewed on the Monitoring tab of the Virtual Server detail page.

Each metric provides guidance in the user guide on which statistical value is meaningful to query, and among the meaningful statistics, the values shown in bold text are the primary statistics. In the service dashboard or monitoring tab, you can view primary metrics using these primary statistics.

1.2 - How-to guides

Users can create the service by entering the required information for a Virtual Server and selecting detailed options through the Samsung Cloud Platform Console.

Create Virtual Server

You can create and use a Virtual Server service in the Samsung Cloud Platform Console.

To create a Virtual Server, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.

2. On the Service Home page, click the Create Virtual Server button. 2. Navigate to the Create Virtual Server page.

3. On the Virtual Server 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	required status	Detailed description
     Image	Required	Select the provided Image type Standard: Samsung Cloud Platform standard provided Image Alma Linux, Oracle Linux, RHEL, Rocky Linux, Ubuntu, Windows Custom: User-created Image Kubernetes: Image for Kubernetes RHEL, Ubuntu Marketplace: Image subscribed from Marketplace
     Image version	Required	Select version of the selected Image Provide version list of the server Image

     Table. Virtual Server Image and version selection input items
   • In the Service Information Input area, enter or select the required information.

     Category	required status	Detailed description
     Number of servers	Required	Number of servers to create concurrently Only numeric input is allowed, and enter a value between 1~100
     Service Type > Server Type	Required	Virtual Server server type Standard: standard specifications commonly used High Capacity: large‑capacity server specifications beyond Standard For detailed information about the server types provided by Virtual Server, see Virtual Server 서버 타입
     Service Type > Planned Compute	Required	Planned Compute-configured resource status 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 creation page For more details, refer to Planned Compute Apply
     Block Storage	Essential	Block Storage settings used by the server according to purpose Basic OS: Area where the OS is installed and used Capacity is entered in Units, and the minimum size varies by OS Image type Alma Linux: Enter a value between 2~1,536 Oracle Linux: Enter a value between 7~1,536 RHEL: Enter a value between 2~1,536 Rocky Linux: Enter a value between 2~1,536 Ubuntu: Enter a value between 2~1,536 Windows: Enter a value between 4~1,536 SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management Service) encryption keys Encryption can be applied only at initial creation and cannot be changed afterward Using the SSD_KMS disk type may cause performance degradation SSD_Provisioned: SSD volume with configurable IOPS and Throughput Additional: Used when extra user space beyond the OS area is needed After selecting Use, enter the storage type and capacity To add storage, click the + button; to delete, click the x button (up to 25 can be added) Capacity is entered in Units, with a value between 1~1,536 1 Unit equals 8 GB, so 8~12,288 GB are created SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management Service) encryption keys Encryption can be applied only at initial creation and cannot be changed afterward Using the SSD_KMS disk type may cause performance degradation SSD/HDD_MultiAttach: Volume that can be attached to two or more servers SSD_Provisioned: SSD volume with configurable IOPS and Throughput For details on each Block Storage type, see Block Storage 생성하기 Delete on termination: When Delete on Termination is selected, the volume is terminated together with the server A volume with an existing snapshot is not deleted even when Delete on termination is enabled A multi‑attach volume can be deleted only when the server being removed is the last remaining server attached to the volume Max IOPS: Enter a maximum IOPS value between 5,000~20,000 Not configurable for disk types HDD, HDD_KMS, HDD_MultiAttach Max Throughput: Enter a maximum Throughput value between 250~1,000 Not configurable for disk types HDD, HDD_KMS, HDD_MultiAttach
     Server Group	Select	After selecting Use for setting Anti-Affinity (distributed placement), Affinity (proximate placement), Partition (distributed placement of Virtual Server and Block Storage) for servers belonging to the same Server Group , select the Server Group , choose Create New to create the Server Group
     Servers belonging to the same Server Group are placed in a Best Effort manner according to the selected policy
     The policy can be selected among Anti-Affinity (distributed placement), Affinity (proximate placement), Partition (distributed placement of Virtual Server and Block Storage)

     Table. Virtual Server service information input items
     Caution

     When using the Partition (distributed placement of Virtual Server and Block Storage) policy among Server Group policies, you cannot allocate additional Block Storage Volumes after creating a Virtual Server, so create all required Block Storage during the Virtual Server creation step.
   • Required Information Input area, please enter or select the required information.

     Category	required status	Detailed description
     Server name	Essential	Enter a name to distinguish the server when the selected number of servers is 1 Set the hostname to the entered server name Enter using English letters, numbers, spaces, and special characters (-, _) within 63 characters
     Network Settings > Create New Network Port	Required	Set the network where the Virtual Server will be installed VPC Name: Select a pre‑created VPC General Subnet: Select a pre‑created general Subnet IP can be set to auto‑generate or user‑provided; if input is selected, the user can manually enter the IP NAT: Available only when there is a single server and the VPC is attached to an Internet Gateway. Checking Use allows selection of a NAT IP NAT IP: Select a NAT IP If no NAT IP is available, click the Create New button to generate a Public IP Refresh button to view and select the created Public IP Creating a Public IP incurs charges according to the Public IP pricing policy Local Subnet (optional): Select Use for a local Subnet It is not a required element for creating the service A pre‑created local Subnet must be selected IP can be set to auto‑generate or user‑provided; if input is selected, the user can manually enter the IP Security Group: Settings required to access the server Select: Choose a pre‑created Security Group Create New: If no applicable Security Group exists, it can be created separately in the Security Group service Up to 5 can be selected If no Security Group is set, all connections are blocked by default A Security Group must be configured to allow required connections
     Network Settings > Specify Existing Network Port	Required	Set the network where the Virtual Server will be installed VPC: Select a pre‑created VPC General Subnet: Select a pre‑created general Subnet and port NAT: Available only when there is a single server and the VPC is attached to an Internet Gateway. When enabled, you can select a NAT IP NAT IP: Select a NAT IP If no NAT IP is available to select, click the Create New button to generate a Public IP Refresh button to view and select the created Public IP Local Subnet (Optional): Choose Use for the local Subnet Select a pre‑created local Subnet and port
     Keypair	Required	User authentication method to use when connecting to the server Create new: Create a new one if a new keypair is required Refer to Keypair 생성하기 Default login account list by OS Alma Linux: almalinux Oracle Linux: cloud-user RHEL: cloud-user Rocky Linux: rocky Ubuntu: ubuntu Windows: sysadmin

     Table: Required input fields for Virtual Server
   • Additional Information Input area, please enter or select the required information.

     Category	required status	Detailed description
     Lock	Select	Lock usage setting Using the lock prevents actions such as server termination, start, stop, etc., from being executed, preventing misoperations due to mistakes
     Init script	Select	the script that runs when the server starts The init script must be written as a Batch script for Windows, a Shell script or cloud‑init for Linux, depending on the Image type. Up to 45,000 bytes can be entered
     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. Virtual Server additional information input fields

4. Summary Check the detailed information and estimated charges generated in the panel, and click the Create button.

   • Once creation is complete, check the created resources on the Virtual Server List page.

Check Virtual Server detailed information

The Virtual Server service allows you to view and edit the entire resource list and detailed information. The Virtual Server Details page includes the Details, Monitoring, Tags, Activity Log tabs.

To view detailed information about the Virtual Server service, follow these steps.

1. All Services > Compute > Virtual Server menu, click it. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to view detailed information. 3. Navigate to the Virtual Server Details page.
   • Virtual Server Details page displays status information and additional feature information, and consists of Details, Monitoring, Tags, Activity Log tabs.
   • For detailed information about Virtual Server Add-on Features, please refer to Virtual Server Management Add-on Features.

     Category	Detailed description
     Virtual Server status	Status of a user-created Virtual Server Build: State where a Build command has been received Building: Build in progress Networking: Server creation networking process Scheduling: Server creation scheduling process Block_Device_Mapping: Attaching Block Storage during server creation Spawning: Server creation process is ongoing Active: Available state Powering_off: State when a shutdown request is made Deleting: Server deletion in progress Reboot_Started: Reboot in progress Error: Error state Migrating: Server is being migrated to another host Reboot: Reboot command has been received Rebooting: Restart in progress Rebuild: Rebuild command has been received Rebuilding: State when a Rebuild request is made Rebuild_Spawning: Rebuild process is ongoing Resize: Resize command has been received Resizing: Resize in progress Resize_Prep: State when a server type change is requested Resize_Migrating: Server is being moved to another host while resizing Resize_Migrated: Server has completed moving to another host during resize Resize_Finish: Resize completed Revert_Resize: Resize or migration of the server failed for some reason. The target server is cleaned up and the original server is restarted Shutoff: State when powering off is completed Verity_ Resize: After a server type change request and Resize_Prep, the server type is confirmed or can be reverted Resize_Reverting: State when a server type revert is requested Resize_Confirming: State while confirming the server’s Resize request
     Server control	Buttons to change server status Start: Start a stopped server Stop: Stop a running server Restart: Restart a running server
     Image generation	Create a user Image from the current server’s Image For detailed Image creation instructions, see Create Image
     Console log	View console logs of the current server You can check the console logs output by the current server. For more details, see 콘솔 로그 확인하기
     Create dump	Create a dump of the current server Dump file is created inside the Virtual Server Refer to Dump 생성하기 for detailed dump creation instructions
     Rebuild	The OS area data and settings of the existing Virtual Server are deleted, and it is rebuilt on a new server For details, see Rebuild 수행하기
     Service termination	Button to cancel the service

     Table. Virtual Server status information and additional functions

Detailed Information

Virtual Server List page lets you view detailed information of the selected resource and, if needed, modify the information.

Monitoring

You can monitor the ServiceWatch metrics of the resources selected on the Virtual Server List page. In the Monitoring tab, you can view monitoring charts for the Virtual Server, and each chart is based on the available Service Watch metrics.

Tag

Virtual Server List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.

Job History

Virtual Server List page allows you to view the operation history of the selected resource.

Control Virtual Server Operation

If you need to control the operation of a created Virtual Server resource, you can perform the task from the Virtual Server List or Virtual Server Details page. You can start, stop, and restart a running server.

Getting Started with Virtual Server

You can start a Virtual Server that is Shutoff. To start the Virtual Server, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. Virtual Server List page, click the resource to start among the shutoff servers, and navigate to the Virtual Server Details page.
   • On the Virtual Server List page, you can Start each resource via the right More button.
   • After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Start button at the top.
4. Virtual Server Details page, click the Start button at the top to start the server. 4. Check the status of the modified server in the Status Indicator item.
   • When the Virtual Server start is complete, the server status changes from Shutoff to Active.
   • For detailed information about the Virtual Server status, please refer to Virtual Server Detailed Information.

Stop Virtual Server

You can stop a Virtual Server that is running (Active). To stop the Virtual Server, follow the steps below.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to stop among the active servers, and proceed to the Virtual Server Details page.
   • On the Virtual Server List page, you can stop each resource via the right More button.
   • After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Stop button at the top.
4. On the Virtual Server Details page, click the Stop button at the top to start the server. 4. Check the status of the modified server in the Status Indicator item.
   • When the Virtual Server shutdown is complete, the server status changes from Active to Shutoff.
   • For detailed information about the Virtual Server status, please refer to Virtual Server Detailed Information.

Restart Virtual Server

You can restart the created Virtual Server. To restart the Virtual Server, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. On the Virtual Server List page, click the resource to restart, and go to the Virtual Server Details page.
   • On the Virtual Server list page, you can restart each resource via the right More button.
   • After selecting multiple servers with checkboxes, you can control multiple servers simultaneously using the Restart button at the top.
4. On the Virtual Server Details page, click the Restart button at the top to start the server. 4. Check the status of the changed server in the Status Display section.
   • During a Virtual Server restart, the server status goes through Rebooting and finally changes to Active.
   • For detailed information about the Virtual Server status, please refer to Virtual Server Detailed Information.

Managing Virtual Server Resources

If you need server control and management functions for the created Virtual Server resources, you can perform tasks on the Virtual Server List or Virtual Server Details page.

Create Image

You can create an image of a running Virtual Server.

To create an Image of a Virtual Server, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of Virtual Server.

2. On the Service Home page, click the Virtual Server menu. 2. Navigate to the Virtual Server List page.

3. On the Virtual Server List page, click the resource to create an Image. 3. Navigate to the Virtual Server Details page.

4. On the Virtual Server Details page, click the Create Image button. 4. Go to the Image creation page.

   • Enter the required information in the Service Information Input area.

     Category	required status	Detailed description
     Image name	Required	the name of the Image to be created English letters, numbers, spaces, and special characters (-, _) within 200 characters

     Table. Image service information input fields

5. Check the input information and click the Complete button.

   • When creation is complete, check the created resources on the All Services > Compute > Virtual Server > Image List page.

Edit Server Type

You can modify the server type of a Virtual Server.

To modify the server type of a Virtual Server, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
2. On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
3. On the Virtual Server List page, click the resource you want to control. 3. Go to the Virtual Server Details page.
4. On the Virtual Server Details page, check the server status and click the Edit button for the server type. 4. Edit Server Type popup window opens.
5. Edit Server Type In the popup window, after changing the server type, click the Confirm button.
   • If you modify the Virtual Server’s server type, the Virtual Server status changes to a state related to performing a resize.
   • For detailed information about the Virtual Server status, please refer to Virtual Server Detailed Information.

Service Architecture Diagram

Provided features

Virtual Server Auto-Scaling provides the following features.

• Launch Configuration: It is a configuration template used to create a Virtual Server in an Auto-Scaling Group. When creating a Launch Configuration, you set information about the Virtual Server such as the image, server type, Key Pair, Block Storage, etc.
• Server Count Adjustment: Provides several ways to adjust the number of servers. By using policies, you can add a Virtual Server when load exceeds a threshold and release the Virtual Server when demand is low, maintaining application availability while reducing costs. You can also add and release Virtual Servers according to a predefined schedule, and manually adjust the number of servers in an Auto-Scaling Group as needed.
• Load Balancer Integration: You can use a Load Balancer to evenly distribute application traffic across Virtual Servers. Whenever a Virtual Server is added or removed, it is automatically registered with or deregistered from the Load Balancer.
• Network Connection: You can connect the Auto-Scaling Group’s standard subnet, automatic IP allocation, and Public NAT IP. Provides a local subnet connection for inter-server communication.
• Security Group Application: Security Group is a virtual logical firewall that controls inbound/outbound traffic generated on a Virtual Server. Inbound rules control incoming traffic to the Virtual Server, and outbound rules control outgoing traffic from the Virtual Server.
• Monitoring: You can view monitoring data such as CPU, Memory, and Disk of Virtual Servers created in an Auto-Scaling Group via the ServiceWatch service. Based on the monitoring data, you can set load thresholds using Auto-Scaling policies, and when thresholds are exceeded, you can add or remove servers.

Component

Virtual Server Auto-Scaling creates an Auto-Scaling Group through a Launch Configuration and monitors and manages the servers.

Launch Configuration

This is a Configuration template used to create a Virtual Server in an Auto-Scaling Group. The main features are as follows.

• Image: Provides OS standard images and Custom images created by the user. Users can select and use them according to the service they wish to configure.
• Keypair: Provides the Keypair method for secure OS access.
• Init script: Users can define a script to be executed when the Virtual Server starts.
• For more details, refer to Launch Configuration Create.

Auto-Scaling Group

Launch Configuration is used as a pre-configuration template for creating servers. By creating an Auto-Scaling Group, you can adjust and manage the number of servers. The main features are as follows.

• Launch Configuration: A Configuration template used to create a Virtual Server in an Auto-Scaling Group.
• Server Count Setting: Virtual Server Auto-Scaling provides several ways to adjust the number of servers in an Auto-Scaling Group.
  • Fixed Server Count Method: When creating an Auto-Scaling Group, this method keeps the default settings using the configured number of servers without any additional schedules or policies. Refer to Create Auto-Scaling Group to set the Min, Desired, and Max server counts.
  • Server Count Manual Adjustment Method: In an Auto-Scaling Group, you can increase or decrease the number of servers by modifying the server count to the desired amount. You can choose whether to manually set the desired server count. Please refer to 서버 수 수정하기.
  • Schedule reservation method: You can schedule daily, weekly, monthly, or one-time, and set the desired number of servers at the specified time. This is useful when you can predict when to scale the number of servers up or down. If you use the schedule method, please refer to Manage Schedules to add and manage schedules.
  • Policy Mode: You can use a policy to dynamically adjust servers. When a monitoring metric exceeds a configured threshold, the number of servers is adjusted. At this time, you can choose one of three methods to adjust the server count: increase or decrease by a specified number, increase or decrease by a specified percentage, or fix the server count to a given value. When servers are started or terminated due to a policy, the monitoring metric (CPU utilization) may temporarily exceed the threshold registered in the policy. However, because this is a brief moment, a cooldown period is set to avoid treating it as an abnormal situation. If you want to use the policy mode, see Managing Policies.
• Load Balancer: Automatically connects and disconnects to the Load Balancer registered in the Auto-Scaling Group whenever a Virtual Server is added or terminated.
  • Refer to Auto-Scaling Group Detailed Information for detailed information about the Load Balancer of an Auto-Scaling Group.

Constraints

The constraints of Virtual Server Auto-Scaling are as follows.

Prior Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.

2.1.1 - Monitoring Metrics

Virtual Server Auto-Scaling is a service provided for Virtual Servers that offers individual Virtual Server monitoring metrics and monitoring metrics provided by policies based on Cloud Monitoring.

Virtual Server Monitoring Metrics

The table below shows the monitoring metrics of Virtual Server that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

Memory-related metrics are not provided for Windows OS.

Monitoring metrics provided by Cloud Monitoring-based policies

The table below shows the monitoring metrics provided by the policy of a Cloud Monitoring‑based Auto‑Scaling Group. For detailed information on policy settings based on Cloud Monitoring, see 정책 관리하기.

2.1.2 - ServiceWatch Metrics

Virtual Server Auto-Scaling is a service provided for Virtual Servers that offers individual Virtual Server monitoring metrics and monitoring metrics supplied by ServiceWatch-based policies.

Virtual Server Monitoring Metrics

The basic metrics provided by Virtual Server can be found in ServiceWatch > Virtual Server Basic Metrics.

ServiceWatch monitoring metrics provided by the Auto-Scaling Group policy

The table below shows the ServiceWatch monitoring metrics provided by the Auto-Scaling Group policy. For detailed information on configuring Auto-Scaling Group policies, see Managing Policies.

2.2 - How-to guides

Users can create the service by entering the required information for an Auto-Scaling Group and selecting detailed options through the Samsung Cloud Platform Console.

Create Auto-Scaling Group

You can create and use the Auto-Scaling Group service from the Samsung Cloud Platform Console.

To create an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.

3. On the Auto-Scaling Group List page, click the Create Auto-Scaling Group button. You will be taken to the Create Auto-Scaling Group page.

4. On the Auto-Scaling Group Creation page, enter the information required to create the service.

   • In the Launch Configuration area, select the Launch Configuration.
     • Launch Configuration creation button can be clicked to create a new Launch Configuration.
   • Enter or select the required information in the Service Information Input area.

     Category	Whether required	Detailed description
     Auto-Scaling Group name	Required	Auto-Scaling Group name Manage servers of the same type and purpose as a group
     Server name	Required	Server name to be created within the Auto-Scaling Group The server name is automatically assigned as a combination of the entered server name and a sequence, serving as an identifier to distinguish servers created within the Auto-Scaling Group.
     Number of servers	Required	Number of servers to create in the Auto-Scaling Group Enter a value between 0 and 20 (Min≤Desired≤Max) Min: Set the minimum number of servers the Auto-Scaling Group should maintain Desired: Set the target number of servers within the Auto-Scaling Group; also indicates the number of servers initially created when the Auto-Scaling Group is created Max: Set the maximum number of servers the Auto-Scaling Group can maintain After creating the Auto-Scaling Group, you can adjust the settings using the Edit button. For details, see Modify Server Count
     Desired server count manual setting	Selection	Select whether to manually change the Desired number of servers Even after creating the Auto-Scaling Group, configure it via the Edit button. For details, refer to Manually edit Desired server count
     Network Settings > Network Settings	Required	Network settings for Auto-Scaling Group Select the desired VPC and standard Subnet IP can only be auto-generated. When you select local Subnet, you can choose the desired local Subnet, and IP can only be auto-generated
     Network Settings > Security Group	Selection	To allow required connections, you need to configure a Security Group If you do not configure a Security Group, all inbound and outbound traffic will be blocked according to the default rule (Any/Deny) For Linux servers, allow SSH traffic For Windows servers, allow RDP traffic Even after creating an Auto-Scaling Group, configure it using the modify button. For details, refer to Configure Security Group
     Load Balancer	Selection	Connect the Auto-Scaling Group to a Load Balancer Register the Auto-Scaling Group’s servers as members of the LB server group LB server group: Select a LB server group that exists in the chosen VPC Port: Enter a value between 1 and 65,534 Press the + button to add an LB server group (up to a total of three LB server groups and ports are allowed) LB server groups that use Weighted Round Robin or Weighted Least Connection load balancing cannot be selected Draining Timeout value: After checking Draining Timeout as Enabled, you can set the Draining Timeout value Draining Timeout: The waiting period before removing a server from the Load Balancer Since sessions may remain connected to the server, setting a Draining Timeout and waiting allows safe session termination If the Load Balancer is unused, Draining Timeout cannot be set The default is 300 seconds; you can enter a value from 1 second up to 3,600 seconds. Changes can be made after creating the Auto-Scaling Group; for details, see Using Auto-Scaling Group Load Balancer

     Table. Auto-Scaling Group service information input items
   • In the Scaling policy setting area, set the scaling policy.
     • For detailed information on policy settings, refer to Add Policy.

       Category	Required	Detailed description
       Current setting	Selection	Set scaling policy now Add Policy button click shows policy information input fields
       Set later	Selection	After creating an Auto-Scaling Group, set policies on the detail information page

       Table. Auto-Scaling Group scaling policy configuration items
   • In the Notification Settings area, configure the notification recipients and notification method.
     • For detailed information on notification settings, see Add Notification.

       Category	Required?	Detailed description
       Current setting	Selection	Set the notification recipients and notification method now Click the Add Notification button to open the Add Notification popup For detailed information about notification settings, see the details In the notification recipients list, click the Edit button to modify the notification information
       Set later	Selection	After creating an Auto-Scaling Group, set the notification recipients and notification method on the details page.

       Table. Auto-Scaling Group notification configuration items
   • In the Additional Information Input area, enter or select the required information.

     Category	Required status	Detailed description
     Status check	Selection	Check the status of Virtual Server and Load Balancer and replace servers that are Unhealthy Virtual Server status check: Enabled is the default and cannot be changed Load Balancer status check: Enabled only when a Load Balancer is connected in the service information input area Grace period: Set the time to defer status checks until the newly added server operates normally Enter 0 to disable the status check grace period
     tag	Selection	Add Tag Up to 50 per resource can be added After clicking the Add Tag button, enter or select Key, Value values

     Table. Auto-Scaling Group additional information input fields

     Caution

     A server that the user changes to Stop is not considered Unhealthy, so even when using the health check feature, the server will not be replaced.

5. 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 Auto-Scaling Group on the Auto-Scaling Group list page.

Check detailed information of Auto-Scaling Group

Auto-Scaling Group service allows you to view and edit the full resource list and detailed information. The Auto-Scaling Group Details page is composed of Details, Policies, Schedule, Virtual Server, Load Balancer, Tags, Operation History tabs.

To view detailed information about the Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to view detailed information. You will be taken to the Auto-Scaling Group Details page.
   • Auto-Scaling Group Details page displays status information and additional feature information, and consists of Details, Policies, Schedule, Virtual Server, Load Balancer, Tags, Activity History tabs.

     Category	Detailed description
     Auto-Scaling Group status	Status of the Auto-Scaling Group created by the user Creating: Creating Auto-Scaling Group In Service: Serviceable state Scale In: Scale In in progress Scale Out: Scale Out in progress Cool Down: Cooling down Terminating: Terminating Auto-Scaling Group Attach to LB: Attaching to Load Balancer Detach from LB: Detaching from Load Balancer
     Delete Auto-Scaling Group	Button to delete Auto-Scaling Group

     Table. Auto-Scaling Group status information and additional features

Detailed Information

Auto-Scaling Group List page lets you view detailed information of the selected resource and modify it if necessary.

Policy

On the Auto-Scaling Group List page, you can view the policy list of the selected resource and, if needed, add or manage policies.

Schedule

On the Auto-Scaling Group List page, you can view the schedule list of the selected resource and, if necessary, add or manage schedules.

Virtual Server

Auto-Scaling Group List You can view the Virtual Server list of the selected resource on the page.

Load Balancer

On the Auto-Scaling Group List page, you can view the Load Balancer list of the selected resource, and, if needed, add or manage Load Balancers.

Notification

Auto-Scaling Group List page allows you to view the notification recipients and notification methods for the selected resource.

tag

Auto-Scaling Group List page lets you view the tag information of selected resources, and add, modify, or delete them.

Work History

You can view the operation history of the selected resource on the Auto-Scaling Group List page.

Auto-Scaling Group Managing Resources

If you need to manage a created Auto-Scaling Group, you can perform actions on the Auto-Scaling Group Details page.

Edit Launch Configuration

You can modify the Launch Configuration of an Auto-Scaling Group.

To modify the Launch Configuration of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group list page.

3. On the Auto-Scaling Group List page, click the resource you want to edit the Launch Configuration for. You will be taken to the Auto-Scaling Group Details page.

4. Launch Configuration name. Click the Edit button. The Launch Configuration Edit popup opens. You can view the list of selectable Launch Configurations.

   Category	Detailed description
   Launch Configuration name	Launch Configuration name
   image	Launch Configuration OS Image
   Server type	Launch Configuration server type
   Block Storage	Launch Configuration Block Storage Settings
   Number of Auto-Scaling Groups	Number of Auto-Scailg Groups with Launch Configuration applied
   View Details	Button to view Launch Configuration details

   Table. Launch Configuration list items

5. In the Launch Configuration Edit popup, select the Launch Configuration to modify, then click the Confirm button. The Launch Configuration Edit Notification popup opens. Check the message in the Launch Configuration Edit Notification popup and click the Confirm button.

Edit server count

You can modify the number of servers in the Auto-Scaling Group.

To modify the number of servers in an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group list page.
3. On the Auto-Scaling Group List page, click the resource to edit the server count. You will be taken to the Auto-Scaling Group Details page.
4. Click the Edit button for server count. The Edit Server Count popup opens.
5. Modify Server Count In the popup window, after entering the required fields, click the Confirm button.

   Category	Required	Detailed description
   Number of servers > Min	Required	Minimum number of servers to modify Set the number of servers that the Auto-Scaling Group should maintain at a minimum
   Number of servers > Desired	Required	Target server count to modify Set the target server count within the Auto-Scaling Group Desired server count manual setting is disabled; you cannot modify the Desired server count. To modify the Desired server count, see Desired server count manual setting modification
   Number of servers > Max	Required	Target number of servers to modify Set the maximum number of servers the Auto-Scailg Group can maintain

   Table. Auto-Scailg Group server count modification items

Terminate Virtual Server Created by Auto-Scaling Group

Virtual Servers created in an Auto-Scaling Group can be terminated by clicking the terminate button on the Virtual Server’s detail page or by modifying the server count.

Cancel on the Virtual Server detail page

To cancel a Virtual Server on the Virtual Server detail page, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. On the Service Home page, click the Virtual Server menu. You will be taken to the Virtual Server List page.
3. On the Virtual Server List page, select the Virtual Server created by the Auto-Scaling Group. Navigate to the Virtual Server Details page.
4. Click the Cancel Service button on the Virtual Server Details page. A popup confirming the server termination will appear.
5. Click the Confirm button. Server termination is complete.

Cancel by adjusting the server count

To cancel a Virtual Server by modifying the server count, follow the steps below.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to terminate the Virtual Server. You will be taken to the Auto-Scaling Group Details page.
4. Click the Edit button of the Server Count item. The Server Count Edit popup opens.
5. Server Count Edit In the popup window, after reducing the Desired number, click the Confirm button. As the Desired server count is adjusted, the Virtual Server will be terminated.

Modify manual setting of desired server count

You can manually change the Desired server count of the Auto-Scaling Group.

To modify the manual setting of the Desired server count for an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to manually change the Desired server count. You will be taken to the Auto-Scaling Group Details page.
4. Click the Edit button for the server count. The Desired server count manual setting popup opens.
5. Desired server count manual setting After selecting whether to use it in the popup window, click the Confirm button.

Configure Security Group

You can configure the Security Group of an Auto-Scaling Group.

Follow these steps to configure the Security Group of an Auto-Scaling Group.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.

3. On the Auto-Scaling Group List page, click the resource to configure the Security Group. You will be taken to the Auto-Scaling Group Details page.

4. Click the Edit button for Security Group. Security Group Edit popup opens. You can view the list of selectable Security Groups.

   Category	Detailed description
   Security Group name	Security Group name

   Table. Security Group list items

5. Security Group edit In the popup window, after selecting the Security Group, click the Confirm button. Security Group edit notification popup opens. Check the message of the Security Group edit notification popup and click the Confirm button.

Change status check

You can configure it to check the status of Virtual Server and Load Balancer and automatically replace servers that are in an Unhealthy state.

1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Go to the Auto-Scaling Group list page.
3. On the Auto-Scaling Group List page, click the resource for which you want to change the Load Balancer health check function. You will be taken to the Auto-Scaling Group Details page.
4. Click the Edit button of Status Check. Status Check Edit popup window opens.
5. Status Check Edit In the popup, choose whether to enable Load Balancer Status Check.
6. After entering the Grace period, click the Confirm button.
   • If you do not want to use the grace period, set the grace period to 0.

Manage Additional Information for Auto-Scaling Group

You can set the Load Balancer of an Auto-Scaling Group to enabled and select the LB server group. For an Auto-Scaling Group that is using a Load Balancer, you can change it to disabled.

Modify Load Balancer Draining Timeout

You can set the Load Balancer Draining Timeout of an Auto-Scaling Group.

To set the Load Balancer Draining Timeout of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. Auto-Scaling Group List page, click the resource to set the Load Balancer Draining Timeout. You will be taken to the Auto-Scaling Group Details page.
4. Click the Load Balancer tab. You will be taken to the Load Balancer list page.
5. Click the Edit button for Draining Timeout. The Draining Timeout Edit popup opens.
6. Draining Timeout Edit In the popup window, select whether to use Draining Timeout, and enter the Draining Timeout duration (seconds).
7. Draining Timeout Edit After verifying the input values in the popup window, click the Confirm button. Draining Timeout Edit Notification popup window opens. Check the message in the notification popup and click the Confirm button.

Using Load Balancer

You can modify the Load Balancer of an Auto-Scaling Group. To configure the Load Balancer of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource that will use the Load Balancer. Navigate to the Auto-Scaling Group Details page.
4. Click the Load Balancer tab. You will be taken to the Load Balancer list page.
5. Click the Edit button of the Load Balancer. The Load Balancer Edit popup opens.
6. Load Balancer Edit Please select whether to use it in the popup. Selecting Use allows you to choose a Load Balancer.

   Category	Detailed description
   LB server group	LB server group name Select the LB server group that is created in the selected VPC LB server groups that use Weighted Round Robin or Weighted Least Connection load balancing cannot be selected
   Port	Port information of the LB server group When registering as a member of the LB server group, enter the required port information in the registration details. Enter a value between 1 and 65,534

   Table. Load Balancer list items
   • Click the + button to add an LB server group. Up to three are allowed. Click the X button to remove the added Load Balancer.
7. Check the Load Balancer list and click the Confirm button. Load Balancer Modification Notification popup opens. Verify the message in the notification popup and click the Confirm button.

Not Using Load Balancer

You can modify the Auto-Scaling Group’s Load Balancer to be unused. To set the Auto-Scaling Group’s Load Balancer to unused, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to change the Load Balancer to unused. You will be taken to the Auto-Scaling Group Details page.
4. Click the Load Balancer tab. You will be taken to the Load Balancer list page.
5. Click the Edit button of the Load Balancer. The Load Balancer Edit popup opens.
6. Load Balancer edit Choose whether to use it in the popup window. If you deselect Use, Load Balancer will no longer be used.
7. Use deselection, and click the Confirm button. Load Balancer Modification Notification popup opens. Verify the message in the notification popup and click the Confirm button.

Delete Auto-Scaling Group

Deleting an unused Auto-Scaling Group can reduce operational costs. However, terminating an Auto-Scaling Group may cause the running service to stop immediately, so you should thoroughly consider the impact of service interruption before proceeding with the termination.

To terminate an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to terminate. Navigate to the Auto-Scaling Group Details page.
4. Click the Auto-Scaling Group Delete button.
5. After the deletion is complete, verify that the resource has been removed on the Auto-Scaling Group List page.

2.2.1 - Launch Configuration

To create an Auto-Scaling Group, a Launch Configuration must be created in advance.

Create Launch Configuration

You can create and use the Launch Configuration service in the Samsung Cloud Platform Console.

To create a Launch Configuration, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

2. Click the Launch Configuration menu. Navigate to the Launch Configuration List page.

3. On the Launch Configuration list page, click the Create Launch Configuration button. You will be taken to the Create Launch Configuration page.

4. On the Launch Configurationp Creation page, in the Image and Version Selection area, select the required information and click the Next button.

   Reference

   Please refer to the server type in Virtual Server OS Image Provisioning Versions for images selectable in Launch Configuration.

5. Enter the required information in the Service Information Input area of the Launch Configurationp Creation page.

   Category	Required status	Detailed description
   Launch Configuration name	Required	Launch Configuration name Name used to distinguish the Launch Configuration
   Service Type > Server Type	Required	Launch Configuration server type Standard: Standard specifications commonly used High Capacity: Large-scale server specifications beyond Standard Refer to Virtual Server Server Type for selectable server types
   Block Storage	Required	Configure Block Storage according to the purpose of the Launch Configuration Basic OS: The area where the OS is installed and used Enter the size in Units, and the minimum size varies depending on the OS image type Alma Linux: Enter a value between 2 and 1,536 Oracle Linux: Enter a value between 5 and 1,536 RHEL: Enter a value between 2 and 1,536 Rocky Linux: Enter a value between 2 and 1,536 Ubuntu: Enter a value between 1 and 1,536 Windows: Enter a value between 4 and 1,536 SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption keys Encryption can be applied only at initial creation and cannot be changed afterward Performance degradation occurs when using the SSD_KMS disk type Additional: Use when extra space beyond the OS area is needed After selecting Use, enter the storage type and size Click the + button to add storage, or the x button to delete (up to 25 can be added) Enter the size in Units, with a value between 1 and 1,536 Since 1 Unit equals 8 GB, this creates 8 GB to 12,288 GB SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption keys Encryption can be applied only at initial creation and cannot be changed afterward Performance degradation occurs when using the SSD_KMS disk type SSD_MultiAttach: Volume that can be attached to more than one server For details on each Block Storage type, see Create Block Storage
   Keypair	Required	Select the user authentication method for the Launch Configuration Server authentication information for accessing the servers created by generating an Auto-Scaling Group with a Launch Configuration New creation: Create a new one if a new Keypair is required Refer to Create Keypair for how to create a new Keypair Default login account list by OS Alma Linux: almalinux RHEL: cloud-user Rocky Linux: rocky Ubuntu: ubuntu Windows: sysadmin
   File Storage Settings	Selection	Scale-out/Scale-in can be set to automatically connect File Storage Volume: After clicking the Select button, choose the Volume to use in the Select File Storage popup Up to 5 can be selected The selected Volume can be deleted by clicking the X button

   Table. Launch Configuration service information input items

6. On the Launch Configuration Creation page, after entering information in the Additional Information Input area, click the Next button.

   Category	Required	Detailed description
   Init Script	Selection	Script that runs when the server of an Auto Scaling Group using a Launch Configuration starts Enter within 45,000 bytes The init script must be a batch script for Windows, a shell script for Linux, or cloud‑init, depending on the selected image.
   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. Launch Configuration additional information input fields

7. Verify creation information Check the information you entered on the page and the estimated amount, and click the Create button.

   • When creation is complete, verify the created Launch Configuration on the Launch Configuration List page.

View Launch Configuration Details

The Launch Configuration service allows you to view and edit the full list of resources and detailed information. Launch Configuration Details page consists of Details, Tags, Activity Log tabs.

To view detailed information of the Launch Configuration, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Launch Configuration menu. Navigate to the Launch Configuration List page.
3. On the Launch Configuration List page, click the resource you want to view detailed information for. You will be taken to the Launch Configuration Details page.
   • Launch Configuration Details At the top of the page, status information and additional feature information are displayed, and it consists of Details, Tags, Activity History tabs.

     Category	Detailed description
     Launch Configuration status	User-created Launch Configuration status Active: Available
     Delete Launch Configuration	Delete Launch Configuration button

     Table. Launch Configuration status information and additional features

Detailed information

Launch Configuration list page allows you to view detailed information of the selected resource and edit the information if needed.

tag

Launch Configuration List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.

Work History

You can view the operation history of the selected resource on the Launch Configuration List page.

Delete Launch Configuration

Deleting unused Launch Configurations can reduce operational costs. However, terminating a Launch Configuration may cause running services to stop immediately, so you should carefully consider the impact of service interruption before proceeding with the termination.

To delete a Launch Configuration, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Launch Configuration menu. Go to the Launch Configuration List page.
3. On the Launch Configuration List page, click the resource to be terminated. Navigate to the Launch Configuration Details page.
4. Launch Configuration Delete Click the button.
5. After deletion is complete, verify on the Launch Configuration List page that the resource has been removed.

2.2.2 - Manage Policy

You can dynamically adjust the number of servers in an Auto-Scaling Group based on monitoring metrics. When the metric exceeds the threshold you set, the server count is adjusted. At that time, you can choose one of three methods to adjust the server count: increase or decrease by a specified number, increase or decrease by a specified percentage, or fix the server count to a given value. When servers are launched or terminated due to a policy, the monitoring metric, such as CPU utilization, may temporarily exceed the threshold registered in the policy. However, because this is a brief moment, a cooldown period is set to avoid treating it as an abnormal condition. You can add and manage policies for an Auto-Scaling Group created in the Samsung Cloud Platform Console.

Add Policy

You can add policies to an Auto-Scaling Group. To add a policy to an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.

3. Auto-Scaling Group List page, click the resource you want to view detailed information for. You will be taken to the Auto-Scaling Group Details page.

4. Click the Policy Tab. You will be taken to the Policy Tab page.

5. Click the Add Policy button. The Add Policy popup window opens.

   Category	Required	Detailed description
   Category	Required	Policy Category Scale In: return server count Scale Out: increase server count
   Policy Name	Required	Name for policy-specific categorization
   Execution conditions	Required	Conditions to execute the policy Statistic: How to calculate the Metric Type Average: Average of servers in the Auto-Scaling Group Min: Minimum value among servers in the Auto-Scaling Group Max: Maximum value among servers in the Auto-Scaling Group Metric Type: CPU Usage, Network In(bytes), Network Out(bytes), Network In(Packets), Network Out(Packets) Operator: >= > <= < Threshold: Threshold corresponding to the Metric Type Period: Continuous duration required to trigger the condition (the condition must be continuously satisfied for N minutes for the policy to execute)
   execution unit	Required	Policy execution method Policy Type: Select the type of policy to execute. Increase or decrease the number of servers by a specified count: Increase or decrease the server count to the Target Value Increase or decrease the number of servers by a specified ratio: Increase or decrease by the Target Value ratio Fix the number of servers to the entered value: Fix the server count according to the Target Value Target Value: The number or ratio to apply for the selected Policy Type
   cooldown	Required	The waiting time (seconds) when a server is started or terminated due to a policy The default is 300 seconds, and it can be set between a minimum of 60 seconds and a maximum of 3,600 seconds.

   Table. Add Policy Popup Items
   Reference

   Policy > Cooldown Settings

   • When a server is started or terminated due to a policy, it waits for the configured cooldown period. Temporarily, the monitoring metric CPU utilization may exceed the threshold defined in the policy. However, because this is a transient moment rather than a condition for adjusting the number of servers, it is not considered an abnormal situation, and the system waits by applying the cooldown time.
   guide

   Policy execution operates within the configured Min/Max server count range.

   • Even if you input values outside the Min/Max server count range—such as increasing, returning, or fixing the number of servers—it operates within the configured Min/Max server count.
   • Example: When the minimum number of servers is 3, even if you set the server count fixed to 1, the server count does not drop to 1 and remains at the minimum of 3.

6. Add Policy After entering the required values in the popup window, click the Confirm button. The added policy can be viewed in the Policy List.

Policy creation example

The following is an explanation of the policy example. Please refer to it when creating a policy.

Edit Policy

You can modify the policies of an Auto-Scaling Group. To modify the policies of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.

2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.

3. Auto-Scaling Group List page, click the resource to view detailed information. You will be taken to the Auto-Scaling Group Details page.

4. Click the Policy Tab. You will be taken to the Policy Tab page.

5. Click the More > Edit button for the policy you want to modify. The Policy Edit Popup opens.

   Category	Required	Detailed description
   Category	Required	Policy Classification Scale In: Return server count Scale Out: Increase server count
   Policy Name	Required	Name for policy-specific categorization
   Execution conditions	Required	Conditions to execute the policy Statistic: Method to calculate the Metric Type Average: Average of servers in the Auto-Scaling Group Min: Minimum value among servers in the Auto-Scaling Group Max: Maximum value among servers in the Auto-Scaling Group Metric Type: CPU Usage, Network In(bytes), Network Out(bytes), Network In(Packets), Network Out(Packets) Operator: >= > <= < Threshold: Threshold corresponding to the Metric Type Period: Continuous duration (in minutes) that triggers the execution condition
   execution unit	Required	Policy execution method Policy Type: Select the type of policy to execute. Increase or decrease the number of servers by a specified count: Increase or reduce the server count to the Target Value Increase or decrease the number of servers by a specified ratio: Increase or reduce by the Target Value ratio Fix the number of servers to the entered value: Fix the server count according to the Target Value Target Value: The number or ratio to execute the selected Policy Type
   Cool down	Required	The waiting time (seconds) when a server is started or terminated due to a policy The default is 300 seconds, and it can be set from a minimum of 1 second up to a maximum of 3,600 seconds

   Table. Policy edit popup items

6. Edit Policy In the popup window, after entering the required values, click the Confirm button.

Policy addition and modification constraints

When adding or modifying a policy, constraints exist based on the policy classification, execution conditions, and the scope of those conditions. Below is an example of constraints for the policy. Refer to the constraint examples to add or modify the policy.

Example 1 - Need to check for duplicate registration of policy classification/execution conditions

Policy classification (Scale Out or Scale In) and execution condition (Metric type) cannot be registered redundantly with the same values.

If a policy is registered as above, you cannot add a policy with the category (Scale Out) execution condition (Metric type=CPU Usage) or modify it to that condition.

Example 2 - Need to verify the execution condition range for execution conditions (Metric type) and execution conditions (Statistic) according to policy classification

When the policy type (Scale Out or Scale In) differs, duplicate registration of the execution condition range (Comparison operator + Threshold) is not allowed for the same execution condition (Metric type) and execution condition (Statistic).

If a policy is registered as shown above, you cannot add a policy as below or modify it under the following conditions.
If the average CPU Usage is 60% or higher, a Scale Out policy is already registered; therefore, registering a Scale In policy when the average CPU Usage is 60% or lower would duplicate the 60% execution condition and cannot be added.

Example 3 - Need to verify the execution condition range for execution conditions (Metric type) and execution conditions (Statistic) according to policy classification

When the policy classification (Scale Out or Scale In) differs, duplicate registration of the execution condition range (Comparison operator + Threshold) is not allowed for the same execution condition (Metric type) and execution condition (Statistic).

If a policy is registered as shown above, you cannot add a policy as below or modify it under the following conditions.
When the average CPU Usage is 10% or less, a Scale In policy is already registered; therefore, if the average CPU Usage is less than 60% / 60% or less / 10% or more / exceeds 9%, you cannot register a Scale Out policy because the execution condition ranges would overlap.

Example 4 - Execution conditions (Metric type) and execution conditions (Statistic) can be registered according to the execution condition range based on policy classification

If the policy type (Scale Out or Scale In) differs, you can register when the execution condition (Metric type) is the same but the execution condition (Statistic) is different, or when the execution condition range (Comparison operator + Threshold) does not overlap.

If a policy is already registered as shown above, you can add a policy as below or modify it with the following conditions. Registration is possible when the execution condition ranges do not overlap, or when the execution condition (Statistic) differs.

Delete Policy

You can delete a policy of an Auto-Scaling Group. To delete a policy of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. Auto-Scaling Group List page: click the resource you want to view details for. You will be taken to the Auto-Scaling Group Details page.
4. Click the Policy Tab. You will be taken to the Policy Tab page.
5. Select the policy to delete and click the Delete button. The Policy Deletion Confirmation popup opens.
6. Policy Deletion Confirmation Check the popup window and click the Confirm button.

2.2.3 - Manage Schedule

You can schedule reservations daily, weekly, monthly, or one-time, and set the desired number of servers at the specified time. This is useful when you can predict when you need to decrease or increase the number of servers.

Add schedule

You can add a schedule to an Auto-Scaling Group. To add a schedule to an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. Auto-Scaling Group List page, click the resource you want to view detailed information for. You will be taken to the Auto-Scaling Group Details page.
4. Click the Schedule Tab. You will be taken to the Schedule Tab page.
5. Click the Add Schedule button. The Add Schedule popup window opens.

   Category	required	Detailed description
   Schedule name	Required	Name to distinguish by schedule
   Select server count	Required	Select the number of servers to adjust when executing the schedule Min: The minimum number of servers the Auto-Scailg Group should maintain Desired: The target number of servers within the Auto-Scailg Group Max: The maximum number of servers the Auto-Scailg Group can maintain
   Enter the number of servers	Required	Enter the value for the selected number of servers Min value: Enter a value between 0 and 50. (Min≤Desired≤Max) Desired value: Enter a value between 0 and 50. (Min≤Desired≤Max) Max value: Enter a value between 0 and 50. (Min≤Desired≤Max)
   Period	Required	Schedule execution frequency Daily: You can set the Start date, End date, and Permanent options for a daily schedule. You can also set the Time and Time zone Weekly: You can set the Start date, End date, Permanent options, and the Time and Time zone. You can also select the Day of week on which the weekly schedule will run. Monthly: You can set the Start date, End date, Permanent options, and the Time and Time zone. You can also enter the Date on which the monthly schedule will run One-time: You can set the Time and Time zone. You can also set the Date on which the one-time schedule will run
   Start date	Selection	Set schedule start date Cannot set a date earlier than the current date. The default is the current date.
   End date	Selection	Set schedule end date Cannot set a date earlier than the current date. The default is the current date plus 7 days.
   permanent	Selection	When configuring permanently, set the schedule end date to 9999-12-31
   time	Required	Schedule execution time setting Can be set in 30‑minute increments. Times earlier than the current date or current time cannot be set
   time zone	Required	Schedule execution time zone (example: Asia/Seoul (GMT +09:00))
   day of the week	Required	When Period is set to Weekly, select the Day of the week to execute the schedule
   Date	Required	When Period is set to Monthly, enter the Date on which the schedule will run Enter one or more values from -31 to 31, excluding 0. (Example: 3,4,5) When Period is set to Once, set the Date on which the schedule will run Setting a date earlier than the current date is not allowed. The default is the current date.

   Table. Schedule addition popup items
6. Add Schedule After entering the required values in the popup window, click the Confirm button.
7. Add Schedule Confirmation After checking the message in the popup window, click the Confirm button.

Modify schedule

You can modify the schedule of an Auto-Scaling Group. To modify the schedule of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource for which you want to view detailed information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Schedule Tab. You will be taken to the Schedule Tab page.
5. Click the More > Edit button of the schedule you want to modify. The Edit Schedule popup window will open.

   Category	required	Detailed description
   Schedule name	Required	Name to distinguish by schedule
   Select number of servers	Required	Select the number of servers to adjust when executing the schedule Min: The minimum number of servers the Auto-Scailg Group should maintain Desired: The target number of servers within the Auto-Scailg Group Max: The maximum number of servers the Auto-Scailg Group can maintain
   Enter number of servers	Required	Enter the value for the selected number of servers Min value: Enter a value between 0 and 50. (Min≤Desired≤Max) Desired value: Enter a value between 0 and 50. (Min≤Desired≤Max) Max value: Enter a value between 0 and 50. (Min≤Desired≤Max)
   period	Required	Schedule execution frequency Daily: You can set the Start Date and End Date, and Permanent setting for the daily schedule. You can also set the Time and Time Zone Weekly: You can set the Start Date and End Date, Permanent setting, and the Time and Time Zone. You can also select the Day of Week for the Weekly schedule to run. Monthly: You can set the Start Date and End Date, Permanent setting, and the Time and Time Zone. You can also enter the Date for the Monthly schedule to run. Once: You can set the Time and Time Zone. You can also set the Date for the Once schedule to run
   Start date	Selection	Set schedule start date Cannot set a date earlier than the current date. The default is the current date.
   End date	Selection	Set schedule end date Cannot set a date earlier than the current date. The default is the current date plus 7 days.
   Permanent	Selection	When configuring permanently, set the schedule end date to 9999-12-31.
   time	Required	Schedule execution time setting Can be set in 30‑minute increments. Times earlier than the current date or current time cannot be set
   time zone	Required	Schedule execution time zone (example: Asia/Seoul (GMT +09:00))
   day of the week	Required	When Period is weekly, select the day of the week to run the schedule.
   Date	Required	When Period is set to Monthly, enter the Date on which the schedule will run Enter one or more values from -31 to 31, excluding 0. (Example: 3,4,5) When Period is set to Once, set the Date on which the schedule will run Cannot set a date earlier than the current date. The default is the current date.

   Table. Schedule edit popup items
6. Schedule Edit After entering the required values in the popup window, click the Confirm button.
7. Schedule Modification Confirmation After checking the message in the popup window, click the Confirm button.

Delete schedule

You can delete the schedule of an Auto-Scaling Group. To delete the schedule of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource for which you want to view detailed information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Schedule Tab. You will be taken to the Schedule Tab page.
5. Select the schedule to delete and click the Delete button. Schedule Deletion Confirmation popup will open.
6. Schedule Deletion Confirmation Check the popup window and click the Confirm button.

2.2.4 - Manage Notification

You can designate a notification recipient and send alert messages via E‑mail or SMS for specific situations.

Add notification

You can add notifications to an Auto-Scaling Group. To add notifications to an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to which you want to add notification information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Notification Tab. You will be taken to the Notification Tab page.
5. Click the Add Notification button. The Add Notification popup opens.
6. Add Notification After entering the required values in the popup window, click the Confirm button.

   Category	Detailed description
   Notification timing	Notification timing when an Auto-Scaling Group alert occurs Server creation, Server termination, Server creation failure, Server termination failure, When policy execution conditions are met Multiple selection allowed
   Notification recipient	User who will receive the notification when an alert occurs Click the Add Notification Recipient button to select a user Only Samsung Cloud Platform users can be selected as recipients

   Table. Notification items

7. Add Notification Confirmation After checking the message in the popup window, click the Confirm button.

Edit Notification

You can modify the notification settings of an Auto-Scaling Group. To modify the notification settings of an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. Navigate to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to edit the notification information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Notification Tab. You will be taken to the Notification Tab page.
5. In the notification list, click the More > Edit button for the notification you want to modify. The Edit Notification popup window will open.
6. Edit Notification After editing the notification information in the popup window, click the Confirm button.

   Category	Detailed description
   Notification timing	Notification timing when an Auto-Scaling Group alert occurs Server creation, Server termination, Server creation failure, Server termination failure, When policy execution conditions are met Multiple selection allowed

   Table. Notification edit items
7. Edit Notification Confirmation After checking the message in the popup window, click the Confirm button.

Delete Notification

You can delete notifications for an Auto-Scaling Group. To delete notifications for an Auto-Scaling Group, follow these steps.

1. Click the All Services > Compute > Virtual Server menu. Navigate to the Service Home page of Virtual Server.
2. Click the Auto-Scaling Group menu. You will be taken to the Auto-Scaling Group List page.
3. On the Auto-Scaling Group List page, click the resource to edit the notification information. You will be taken to the Auto-Scaling Group Details page.
4. Click the Notification Tab. You will be taken to the Notification Tab page.
5. In the notification list, select the notification you want to delete, then click the Delete button. The Delete Notification Confirmation popup will open.
6. Delete Notification Confirmation Review the popup window and click the Confirm button.

2.3 - API Reference

2.4 - CLI Reference

2.5 - Release Note

Virtual Server Auto-Scaling

3 - GPU Server

3.1 - Overview

Service Overview

GPU Server is a virtualized computing service that lets you freely allocate and use infrastructure resources such as CPU, GPU, and memory provided by the server, without having to purchase them individually, and allocate as much as needed at the required time. It is suitable for tasks that require fast computation speed, such as AI model experimentation, prediction, and inference in a cloud environment, and you can flexibly select and use resources with optimized performance based on the type and scale of the work. The GPU Server provides the following features.

Provided Features

• GPU Server Management: Through a web-based console, users can directly Self Service create, delete, and modify GPU Server provisioning, monitoring, and billing.
• Product offerings by GPU quantity: Depending on the project’s purpose and scale, you can freely select the number of H100/A100 GPUs to configure a virtual server.
• High‑Performance GPU Provision: We provide a high‑performance GPU server at physical‑server level using a pass‑through method.
• Storage Connection: Provides additional attached storage besides the OS disk. * You can connect and use Block Storage, File Storage, and Object Storage.
• Strong Security Application: Use the Security Group service to control inbound/outbound traffic exchanged with the external internet or other VPC(Virtual Private Cloud), securely protecting the server.
• Monitoring: You can view monitoring information such as the status of computing resources—including CPU, Memory, Disk, and GPU—through the Cloud Monitoring service.
• Network Configuration Management: The server’s subnet/IP can be easily changed from the values set at initial creation. * NAT IP provides a management feature that lets you enable or disable it as needed.
• Key Pair method: To ensure a secure OS access method, we provide a Key Pair method instead of ID/PW login.
• Image Management: You can create and manage Custom Images, and it provides sharing functionality between projects.
• ServiceWatch Service Integration Offering: You can monitor data through the ServiceWatch service.

Component

GPU Server provides GPUs, NVSwitch, and NVLink on top of virtualized computing resources.

Specifications by GPU Type

GPU (Graphic Processing Unit) performs the calculations needed to create images that compose the computer screen, and because it is specialized for parallel processing, it can handle large amounts of data quickly, processing large-scale parallel operations such as artificial intelligence (AI) and data analysis.

The following are the specifications of the GPU Types offered by the GPU Server service.

Server type

The server types offered by the GPU Server are as follows. For detailed information about the server types provided by GPU Server, refer to GPU Server 서버 타입.

OS and GPU driver version

The operating systems (OS) supported by the GPU Server are as follows. Note that GPUs of type B300 are supported only from a specific GPU version onward, so please be careful when selecting images.

Preceding Service

This is a service that must be installed in advance before creating this service. Please prepare by referring to the user guide provided in advance.

3.1.1 - Server type

GPU Server server type

GPU servers are categorized by the GPU type they provide, and the GPU used in a GPU server is determined by the server type selected when creating the GPU server. Please select the server type based on the specifications of the application you want to run on the GPU server.

The server types supported by the GPU Server are as follows.

GPU-H100-2 g2v12h1

g1 server type

The g1 server type is a GPU Server that uses the NVIDIA A100 Tensor Core GPU, suitable for high-performance applications.

• Up to 8 NVIDIA A100 Tensor Core GPUs provided
• Equipped with 6,912 CUDA cores and 432 Tensor cores per GPU
• Supports up to 128 vCPUs and 1,920 GB of memory
• Networking speed up to 40 Gbps
• 600 GB/s GPU and NVIDIA NVSwitch P2P communication

g2 server type

The g2 server type is a GPU Server that uses the NVIDIA H100 Tensor Core GPU, making it suitable for high-performance applications.

• Up to 8 NVIDIA H100 Tensor Core GPUs provided
• Equipped with 16,896 CUDA cores and 528 Tensor cores per GPU
• Supports up to 96 vCPUs and 1,920 GB of memory
• Networking speed up to 40 Gbps
• 900 GB/s GPU and NVIDIA NVSwitch P2P communication

g3 server type

The g3 server type is a GPU Server that uses the NVIDIA B300 Tensor Core GPU, making it suitable for high-performance applications.

• Up to 8 NVIDIA B300 Tensor Core GPUs provided
• Equipped with 20,480 CUDA cores and 640 Tensor cores per GPU
• Supports up to 128 vCPUs and 3,840 GB of memory.
• Maximum 40 Gbps networking speed
• 1.8 TB/s GPU and NVIDIA NVSwitch P2P communication

3.1.2 - Monitoring Metrics

GPU Server Monitoring Metrics

The table below shows the monitoring metrics of the GPU server that can be viewed through Cloud Monitoring.

Even without installing the Agent, it provides basic monitoring metrics and the table below. Please check the GPU Server monitoring metrics (provided by default). Additionally, the metrics that can be viewed by installing the Agent are in the table. Please refer to the additional monitoring metrics for GPU Server (Agent installation required).

For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.

3.1.3 - ServiceWatch Metrics

The GPU Server sends metrics to ServiceWatch. The metrics provided by default monitoring are data collected at 5‑minute intervals. If detailed monitoring is enabled, you can view data collected at 1‑minute intervals.

Refer to How-to guides > ServiceWatch Detailed Monitoring Activation for how to enable detailed monitoring of the GPU Server.

Basic Metrics

The following are the basic metrics for the Virtual Server namespace.

The indicators whose names are displayed in bold below are the key indicators selected among the basic indicators provided by Virtual Server. The key metrics are used to build service dashboards that are automatically created for each service in ServiceWatch.

Each metric indicates through the user guide which statistical value is meaningful to view for that metric, and among the meaningful statistics, the statistical values shown in bold text are the primary statistics. In the service dashboard, you can view primary metrics using the primary statistical values.

3.2 - How-to guides

Users can create the service by entering the required GPU Server information and selecting detailed options through the Samsung Cloud Platform Console.

Creating a GPU Server

You can create and use a GPU Server service from the Samsung Cloud Platform Console.

To create a GPU server, follow the steps below.

1. Click the All Services > Compute > GPU Server menu. You will be taken to the Service Home page of GPU Server.

2. On the Service Home page, click the GPU Server Creation button. You will be taken to the GPU Server Creation page.

3. On the GPU Server 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	Required status	Detailed description
     Image	Required	Select the type of Image provided Standard: Samsung Cloud Platform standard provided Image RHEL, Ubuntu Custom: User-created Image Kubernetes: Image for Kubernetes Ubuntu
     Image version	Required	Select the version of the chosen Image Provides a list of versions for the offered server Image For detailed information about the provided server image, see OS and GPU driver versions

     Table. GPU Server image and version selection input fields
   • Service Information Input area, enter or select the required information.

     Category	Required status	Detailed description
     Number of servers	Required	Number of GPU Server servers to create concurrently Only numeric input is allowed, enter a value between 1 and 100
     Service Type > Server Type	Required	GPU Server server type Indicates the specifications of a GPU-type server, allowing selection of servers with 1, 2, 4, or 8 GPUs For detailed information about the server types provided by GPU Server, refer to GPU Server Server Types
     Service Type > Planned Compute	Selection	Resource status 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: Navigate to the Planned Compute service application page For more details, refer to Apply for Planned Compute
     Block Storage	Required	Configure the Block Storage used by the GPU Server according to its purpose Basic: The area where the OS is installed and used Capacity can be entered in units (the minimum capacity varies depending on the OS image type) RHEL: Values between 3 and 1,536 can be entered Ubuntu: Values between 3 and 1,536 can be entered SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption keys Encryption can be applied only at initial creation (cannot be changed after creation) Performance degradation occurs when using the SSD_KMS disk type SSD_Provisioned: SSD volume with configurable IOPS and throughput Additional: Used when the user needs extra space beyond the OS area After selecting Use, enter the storage type and capacity To add storage, click the + button (up to 25 can be added); to delete, click the x button Capacity can be entered in units, with values between 1 and 1,536 Since 1 Unit equals 8 GB, this creates 8 GB to 12,288 GB SSD: High‑performance general volume HDD: General volume SSD/HDD_KMS: Additional encrypted volume using Samsung Cloud Platform KMS (Key Management System) encryption keys Encryption can be applied only at initial creation (cannot be changed after creation) Performance degradation may occur when using the SSD_KMS disk type HDD/SSD_MultiAttach: Volume that can be attached to two or more servers SSD_Provisioned: SSD volume with configurable IOPS and throughput For details on each Block Storage type, refer to Create Block Storage Delete on termination: If Delete on Termination is set to Enabled, the volume is terminated together with the server Volumes with existing snapshots are not deleted even if Delete on termination is set to Enabled A multi‑attach volume can be deleted only when the server being removed is the last remaining server attached to the volume
     Max IOPS	Required	Enter a maximum IOPS value between 5,000~20,000 Can be set only when disk type is SSD_Provisioned
     Max Throughput	Required	Enter the maximum Throughput value between 250~1,000 Disk type can be set only when it is SSD_Provisioned

     Table. GPU Server Service Configuration Items
   • In the Required Information Input area, enter or select the necessary information.

     Category	required or not	Detailed description
     Server name	Required	Enter a name to distinguish the server when the selected number of servers is 1 Set the hostname using the entered server name Enter within 63 characters using letters, numbers, spaces, and special characters (- _)
     Server name Prefix	Required	Enter a Prefix to distinguish each server generated when the selected number of servers is 2 or more Automatically generated in the form of user input value (prefix) + ‘-#’ Enter within 59 characters using letters, numbers, spaces, and special characters (-, _)
     Network Settings > Create New Network Port	Required	Configure the network where the GPU Server will be installed Select a pre‑created VPC. General Subnet: Select a pre‑created general Subnet IP can be set to auto‑generate or manual entry; if manual is chosen, the user can directly input the IP NAT: Available only when there is a single server and the VPC is attached to an Internet Gateway. Checking Use enables selection of a NAT IP NAT IP: Select a NAT IP If no NAT IP is available, click the Create New button to generate a Public IP Click the Refresh button to view and select the created Public IP Creating a Public IP incurs charges according to the Public IP pricing policy Local Subnet (optional): Choose Use for a local Subnet It is not a required element for creating the service A pre‑created local Subnet must be selected IP can be set to auto‑generate or manual entry; selecting Manual allows the user to input the IP directly Security Group: Settings required to access the server Select: Choose a pre‑created Security Group Create New: If no applicable Security Group exists, you can create one separately in the Security Group service Up to 5 can be selected If no Security Group is set, all connections are blocked by default You must configure a Security Group to allow required connections
     Network Settings > Existing Network Port Assignment	Required	Set the network where the GPU server will be installed Select a pre-created VPC General Subnet: Select a pre-created general Subnet and Port NAT: Available only when there is a single server and the VPC is connected to an Internet Gateway. When you check to use it, you can select a NAT IP. NAT IP: Select a NAT IP If there is no NAT IP to select, click the Create New button to generate a Public IP Click the Refresh button to view and select the created Public IP Local Subnet (optional): Select Use for the local Subnet Select a pre-created local Subnet and Port
     Keypair	Required	User authentication methods to use when connecting to the server New creation: Create a new keypair if one is needed Refer to Keypair 생성하기 for how to create a new keypair Default login accounts by OS RHEL: cloud-user Ubuntu: ubuntu

     Table. Required input fields for GPU Server
   • Enter or select the required information in the Additional Information Input area.

     Category	Required	Detailed description
     Lock	Selection	Lock usage setting When Lock is enabled, it prevents actions such as server termination, start, and stop from being executed, thereby avoiding malfunctions caused by mistakes
     Init script	Selection	Script executed when the server starts The init script must be written as a Batch script for Windows, a Shell script for Linux, or cloud‑init, depending on the image type. Up to 45,000 bytes can be entered
     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. GPU Server additional information input fields

4. Summary Check the detailed information and estimated billing amount generated in the panel, and click the Create button.

   • Once creation is complete, check the created resources on the GPU Server List page.