1 - Overview

Service Overview

Virtual Server is a virtual server optimized for cloud computing that lets you freely allocate and use infrastructure resources provided by the server—such as CPU and memory—without having to purchase them individually, and you can allocate as much as you need, when you need it. In a cloud environment, you can use resources with optimized performance according to the user’s computing purposes such as development, testing, and application execution.

Features

  • Easy and convenient computing environment setup: Through a web-based Console, users can easily use Self Service from Virtual Server provisioning to resource management and cost management. * When using a Virtual Server, if you need to change the capacity of major resources such as CPU or Memory, you can easily scale up or down without operator intervention.

  • Various Service Types Offered: Provides virtualized vCore/Memory resources based on predefined server types (1~128 vCore).

    • General Virtual Server: Provides commonly used computing specs (up to 16vCore, 256GB)
    • Large-capacity Virtual Server: Provided when resources larger than the standard Virtual Server spec are required.
  • Strong Security Implementation: Through the Security Group service, control inbound/outbound traffic communicating with the external Internet or other VPC(Virtual Private Cloud) to securely protect the server. * Additionally, real-time monitoring enables stable operation of computing resources.

Service architecture diagram

Diagram
Figure. Virtual Server 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 a Virtual Server, you can modify it immediately using the server type edit function.
  • Standard Server Type and Image Provision: Provides virtualized vCore/Memory resources according to the standard server type, and supplies a standard OS Image.
  • Storage Connection: Provides additional attached storage besides the OS disk. * Block Storage, File Storage, Object Storage can be additionally connected and used.
  • Network Connection: You can connect the Virtual Server’s standard subnet/IP settings and Public NAT IP. * Provides a local subnet connection for inter-server communication. * This task can be edited on the detail page.
  • Security Group Application: Through the Security Group service, control inbound/outbound traffic communicating with external internet or other VPCs to securely protect 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 recover Virtual Server Image using the Backup service.
  • Cost Management: You can create, stop, or terminate servers as needed, and because billing is based on actual usage time, you can verify costs according to usage.
  • ServiceWatch Service Integration: You can monitor data using the ServiceWatch service.

Components

Virtual Server provides standard server types and standard OS images. Users can select and use it 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 the Virtual Server you are using, and you can 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.
  • For instructions on creating and using images, see the How-to guides > Image document.

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: Creates a user credential for connecting to the Virtual Server.
  • Retrieve Public Key: You can retrieve the public key by loading a file or by manually entering the public key. Keypair 생성 및 활용 방법은 How-to guides > Keypair문서를 참고하세요.

Server Group {#server-group}

Server Group 설정을 통해 Virtual Server 및 Virtual Server 생성 시 추가한 Block Storage를 랙(Rack) 및 호스트에 근접 또는 분산 배치 가능합니다. 주요 기능은 다음과 같습니다.

Server Group 생성: 동일 Server Group에 소속된 Virtual Server를 Anti-Affinity(분산배치), Affinity(근접배치), Partition(Virtual Server와 Block Storage 분산배치)로 설정할 수 있습니다.

OS Image version provided

The OS images provided by Virtual Server are as follows.

OS Image versionEoS Date
Alma Linux 8.102029-05-31
Alma Linux 9.62025-11-17
Oracle Linux 8.102029-07-31
Oracle Linux 9.62025-11-25
RHEL 8.102029-05-31
RHEL 9.42026-04-30
RHEL 9.62027-05-31
Rocky Linux 8.102029-05-31
Rocky Linux 9.62025-11-30
Ubuntu 22.042027-06-30
Ubuntu 24.042029-06-30
Windows 20162027-01-12
Windows 20192029-01-09
Windows 20222031-10-14
Table. Virtual Server provided OS Image version
Reference
  • Linux operating systems such as Alma Linux and Rocky Linux provide only even Minor versions, except for the final release version of a Major version. * This is a policy to ensure the stability and consistency of the SCP system. We recommend checking the EOS (End of Support) and EOL (End of Life) dates for the operating system, and, if necessary, applying new or additional individual packages to maintain a stable environment.

Server type

The server types supported by Virtual Server are as follows. For detailed information about server types, see Virtual Server 서버 타입.

Standard s1v2m4
구분
예시상세 설명
서버 타입StandardProvided server type classifications
  • Standard: Configured with the commonly used standard specifications (vCPU, Memory)
  • High Capacity: Large‑capacity server specifications beyond Standard
Server specificationss1Provided server type classification and generation
  • s1: s means standard specification, and 1 indicates the generation provided by Samsung Cloud Platform v2
  • s2: s means standard specification, and 2 indicates the generation provided by Samsung Cloud Platform v2
  • h2: h means high-capacity server specification, and 2 indicates the generation provided by Samsung Cloud Platform v2
Server specificationsv2vCore count
  • v2: 2 virtual cores
Server specificationsm4Memory capacity
  • m4: 4GB Memory
Table. Virtual Server server type

Constraints

Reference
  • When creating a Virtual Server with Rocky Linux or Oracle Linux, additional configuration is required for time synchronization (NTP:Network Time Protocol). * If created with a different image, it is set automatically and no additional configuration is required.
    For more details, please refer to Linux NTP 설정하기.
  • If RHEL and Windows Server were created before August 2025, the RHEL Repository and WKMS (Windows Key Management Service) settings need to be modified.
    For detailed information, refer to RHEL Repo 및 WKMS 설정하기.

Preceding 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.

Service CategoryserviceDetailed description
NetworkingVPCA service that provides an isolated virtual network in a cloud environment
NetworkingSecurity GroupVirtual firewall that controls server traffic
Table. Virtual Server Pre-service

1.1 - Server type

Virtual Server server type

Virtual Server provides server types according to the intended use. Server types are composed of various combinations such as CPU, Memory, and Network Bandwidth. When creating a Virtual Server, the host server used for the Virtual Server is determined by the selected server type. Please select the server type according to the specifications of the application you want to run on the Virtual Server.

The server types supported by Virtual Server are as follows.

Standard s1v2m4
Category
ExampleDetailed description
Server typeStandard제공되는 서버 타입 구분
  • Standard: 일반적으로 사용되는 표준 사양(vCPU, Memory)으로 구성
  • High Capacity: Standard 이상의 대용량 서버으로 사양
서버 사양s1제공되는 서버 타입 구분 및 세대를 의미
  • 영문자: 서버 타입 구분
    • s: 일반 사양
    • h: 대용량 서버 사양
  • 숫자: Samsung Cloud Platform v2에서 제공하는 세대
    • 1, 2, 3: 1세대, 2세대, 3세대
서버 사양v2vCore 개수
  • v2: 2개의 가상 코어
서버 사양m4메모리 용량
  • m4: 4 GB Memory
Table. Virtual Server server type format
Notice
For s3 and h3 server types, they are available only on Samsung Cloud Platform for Enterprise and Samsung Cloud Platform for Samsung. Samsung Cloud Platform Sovereign is scheduled to be offered after November 2026.

s1 server type

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

  • Samsung Cloud Platform v2’s first generation: Intel 3rd‑generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
구분서버 타입vCPUMemoryNetwork Bandwidth
Standards1v1m21 vCore2 GBMaximum 10 Gbps
Standards1v2m42 vCore4 GBUp to 10 Gbps
Standards1v2m82 vCore8 GBUp to 10 Gbps
Standards1v2m162 vCore16 GBUp to 10 Gbps
Standards1v2m242 vCore24 GBUp to 10 Gbps
Standards1v2m322 vCore32 GBUp to 10 Gbps
Standards1v4m84 vCore8 GBUp to 10 Gbps
Standards1v4m164 vCore16 GBUp to 10 Gbps
Standards1v4m324 vCore32 GBUp to 10 Gbps
Standards1v4m484 vCore48 GB최대 10 Gbps
Standards1v4m644 vCore64 GB최대 10 Gbps
Standards1v6m126 vCore12 GBUp to 10 Gbps
Standards1v6m246 vCore24 GBUp to 10 Gbps
Standards1v6m486 vCore48 GBUp to 10 Gbps
Standards1v6m726 vCore72 GBUp to 10 Gbps
Standards1v6m966 vCore96 GBUp to 10 Gbps
Standards1v8m168 vCore16 GBUp to 10 Gbps
Standards1v8m328 vCore32 GBUp to 10 Gbps
Standards1v8m648 vCore64 GBUp to 10 Gbps
Standards1v8m968 vCore96 GBUp to 10 Gbps
Standards1v8m1288 vCore128 GBUp to 10 Gbps
Standards1v10m2010 vCore20 GBUp to 10 Gbps
Standards1v10m4010 vCore40 GB최대 10 Gbps
Standards1v10m8010 vCore80 GB최대 10 Gbps
Standards1v10m12010 vCore120 GBUp to 10 Gbps
Standards1v10m16010 vCore160 GBUp to 10 Gbps
Standards1v12m2412 vCore24 GBUp to 12.5 Gbps
Standards1v12m4812 vCore48 GBMaximum 12.5 Gbps
Standards1v12m9612 vCore96 GBUp to 12.5 Gbps
Standards1v12m14412 vCore144 GBMaximum 12.5 Gbps
Standards1v12m19212 vCore192 GBMaximum 12.5 Gbps
Standards1v14m2814 vCore28 GBUp to 12.5 Gbps
Standards1v14m5614 vCore56 GBUp to 12.5 Gbps
Standards1v14m11214 vCore112 GBMaximum 12.5 Gbps
Standards1v14m16814 vCore168 GBUp to 12.5 Gbps
Standards1v14m22414 vCore224 GB최대 12.5 Gbps
Standards1v16m3216 vCore32 GB최대 12.5 Gbps
Standards1v16m6416 vCore64 GBUp to 12.5 Gbps
Standards1v16m12816 vCore128 GBUp to 12.5 Gbps
Standards1v16m19216 vCore192 GBMaximum 12.5 Gbps
Standards1v16m25616 vCore256 GBUp to 12.5 Gbps
Table. Virtual Server server type specifications - s1 server type

s2 server type

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

  • Second generation of Samsung Cloud Platform v2: 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
CategoryServer typeCPU vCoreMemoryNetwork Bandwidth(Gbps)
Standards2v1m21 vCore2 GBUp to 10 Gbps
Standards2v2m42 vCore4 GBUp to 10 Gbps
Standards2v2m82 vCore8 GBUp to 10 Gbps
Standards2v2m162 vCore16 GBUp to 10 Gbps
Standards2v2m242 vCore24 GBUp to 10 Gbps
Standards2v2m322 vCore32 GBUp to 10 Gbps
Standards2v4m84 vCore8 GBUp to 10 Gbps
Standards2v4m164 vCore16 GBUp to 10 Gbps
Standards2v4m324 vCore32 GBUp to 10 Gbps
Standards2v4m484 vCore48 GBUp to 10 Gbps
Standards2v4m644 vCore64 GBUp to 10 Gbps
Standards2v6m126 vCore12 GBUp to 10 Gbps
Standards2v6m246 vCore24 GBUp to 10 Gbps
Standards2v6m486 vCore48 GBUp to 10 Gbps
Standards2v6m726 vCore72 GBMaximum 10 Gbps
Standards2v6m966 vCore96 GBUp to 10 Gbps
Standards2v8m168 vCore16 GBUp to 10 Gbps
Standards2v8m328 vCore32 GBUp to 10 Gbps
Standards2v8m648 vCore64 GBUp to 10 Gbps
Standards2v8m968 vCore96 GBUp to 10 Gbps
Standards2v8m1288 vCore128 GBUp to 10 Gbps
Standards2v10m2010 vCore20 GBUp to 10 Gbps
Standards2v10m4010 vCore40 GBUp to 10 Gbps
Standards2v10m8010 vCore80 GBUp to 10 Gbps
Standards2v10m12010 vCore120 GBUp to 10 Gbps
Standards2v10m16010 vCore160 GBUp to 10 Gbps
Standards2v12m2412 vCore24 GB최대 12.5 Gbps
Standards2v12m4812 vCore48 GBUp to 12.5 Gbps
Standards2v12m9612 vCore96 GBUp to 12.5 Gbps
Standards2v12m14412 vCore144 GBUp to 12.5 Gbps
Standards2v12m19212 vCore192 GBUp to 12.5 Gbps
Standards2v14m2814 vCore28 GBUp to 12.5 Gbps
Standards2v14m5614 vCore56 GBUp to 12.5 Gbps
Standards2v14m11214 vCore112 GBUp to 12.5 Gbps
Standards2v14m16814 vCore168 GBUp to 12.5 Gbps
Standards2v14m22414 vCore224 GBUp to 12.5 Gbps
Standards2v16m3216 vCore32 GBUp to 12.5 Gbps
Standards2v16m6416 vCore64 GBUp to 12.5 Gbps
Standards2v16m12816 vCore128 GBUp to 12.5 Gbps
Standards2v16m19216 vCore192 GBUp to 12.5 Gbps
Standards2v16m25616 vCore256 GBUp to 12.5 Gbps
Table. Virtual Server server type specifications – s2 server type

s3 server type

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

  • Samsung Cloud Platform v2’s 3rd generation: Intel 6th‑generation (Granite Rapids) Xeon 6737P Processor up to 4.0 GHz
  • Supports up to 16 vCPUs and 256 GB of memory
  • Maximum networking speed of 12.5 Gbps
CategoryServer typeCPU vCoreMemoryNetwork Bandwidth(Gbps)
Standards3v1m21 vCore2 GBUp to 10 Gbps
Standards3v2m42 vCore4 GBMaximum 10 Gbps
Standards3v2m82 vCore8 GBUp to 10 Gbps
Standards3v2m162 vCore16 GBUp to 10 Gbps
Standards3v2m242 vCore24 GBMaximum 10 Gbps
Standards3v2m322 vCore32 GBUp to 10 Gbps
Standards3v4m84 vCore8 GBUp to 10 Gbps
Standards3v4m164 vCore16 GBUp to 10 Gbps
Standards3v4m324 vCore32 GBUp to 10 Gbps
Standards3v4m484 vCore48 GBMaximum 10 Gbps
Standards3v4m644 vCore64 GBUp to 10 Gbps
Standards3v6m126 vCore12 GBMaximum 10 Gbps
Standards3v6m246 vCore24 GBUp to 10 Gbps
Standards3v6m486 vCore48 GBUp to 10 Gbps
Standards3v6m726 vCore72 GBUp to 10 Gbps
Standards3v6m966 vCore96 GBMaximum 10 Gbps
Standards3v8m168 vCore16 GBMaximum 10 Gbps
Standards3v8m328 vCore32 GBUp to 10 Gbps
Standards3v8m648 vCore64 GBMaximum 10 Gbps
Standards3v8m968 vCore96 GBUp to 10 Gbps
Standards3v8m1288 vCore128 GBUp to 10 Gbps
Standards3v10m2010 vCore20 GBUp to 10 Gbps
Standards3v10m4010 vCore40 GBMaximum 10 Gbps
Standards3v10m8010 vCore80 GBMaximum 10 Gbps
Standards3v10m12010 vCore120 GBUp to 10 Gbps
Standards3v10m16010 vCore160 GBMaximum 10 Gbps
Standards3v12m2412 vCore24 GBUp to 12.5 Gbps
Standards3v12m4812 vCore48 GBUp to 12.5 Gbps
Standards3v12m9612 vCore96 GBUp to 12.5 Gbps
Standards3v12m14412 vCore144 GBMaximum 12.5 Gbps
Standards3v12m19212 vCore192 GBUp to 12.5 Gbps
Standards3v14m2814 vCore28 GBUp to 12.5 Gbps
Standards3v14m5614 vCore56 GBUp to 12.5 Gbps
Standards3v14m11214 vCore112 GBUp to 12.5 Gbps
Standards3v14m16814 vCore168 GBUp to 12.5 Gbps
Standards3v14m22414 vCore224 GBUp to 12.5 Gbps
Standards3v16m3216 vCore32 GBUp to 12.5 Gbps
Standards3v16m6416 vCore64 GBUp to 12.5 Gbps
Standards3v16m12816 vCore128 GBUp to 12.5 Gbps
Standards3v16m19216 vCore192 GBUp to 12.5 Gbps
Standards3v16m25616 vCore256 GBUp to 12.5 Gbps
표. Virtual Server 서버 타입 사양 - s3 서버 타입

h2 Server Type

The h2 server type of Virtual Server is offered with high-capacity server 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
  • Maximum networking speed of 25 Gbps
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacityh2v24m4824 vCore48 GBMaximum 25 Gbps
High Capacityh2v24m9624 vCore96 GBMaximum 25 Gbps
High Capacityh2v24m19224 vCore192 GBMaximum 25 Gbps
High Capacityh2v24m28824 vCore288 GBMaximum 25 Gbps
High Capacityh2v32m6432 vCore64 GBMaximum 25 Gbps
High Capacityh2v32m12832 vCore128 GBMaximum 25 Gbps
High Capacityh2v32m25632 vCore256 GBMaximum 25 Gbps
High Capacityh2v32m38432 vCore384 GBMaximum 25 Gbps
High Capacityh2v48m9648 vCore96 GBMaximum 25 Gbps
High Capacityh2v48m19248 vCore192 GBMaximum 25 Gbps
High Capacityh2v48m38448 vCore384 GBMaximum 25 Gbps
High Capacityh2v48m57648 vCore576 GBMaximum 25 Gbps
High Capacityh2v64m12864 vCore128 GBMaximum 25 Gbps
High Capacityh2v64m25664 vCore256 GBMaximum 25 Gbps
High Capacityh2v64m51264 vCore512 GBMaximum 25 Gbps
High Capacityh2v64m76864 vCore768 GBMaximum 25 Gbps
High Capacityh2v72m14472 vCore144 GBMaximum 25 Gbps
High Capacityh2v72m28872 vCore288 GBMaximum 25 Gbps
High Capacityh2v72m57672 vCore576 GBMaximum 25 Gbps
High Capacityh2v72m86472 vCore864 GBMaximum 25 Gbps
High Capacityh2v96m19296 vCore192 GBMaximum 25 Gbps
High Capacityh2v96m38496 vCore384 GBMaximum 25 Gbps
High Capacityh2v96m76896 vCore768 GBMaximum 25 Gbps
High Capacityh2v96m115296 vCore1152 GBMaximum 25 Gbps
High Capacityh2v128m256128 vCore256 GBMaximum 25 Gbps
High Capacityh2v128m512128 vCore512 GBMaximum 25 Gbps
High Capacityh2v128m1024128 vCore1024 GBMaximum 25 Gbps
High Capacityh2v128m1536128 vCore1536 GBMaximum 25 Gbps
Table. Virtual Server server type specifications - h2 server type

h3 Server Type

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

  • Samsung Cloud Platform v2’s 3rd generation: Intel 6th‑generation (Granite Rapids) Xeon 6738P Processor up to 4.1 GHz
  • Supports up to 128 vCPUs and 1,536 GB of memory
  • Maximum networking speed of 25G bps
CategoryServer typevCPUMemoryNetwork Bandwidth
High Capacityh3v24m4824 vCore48 GBMaximum 25 Gbps
High Capacityh3v24m9624 vCore96 GBMaximum 25 Gbps
High Capacityh3v24m19224 vCore192 GBMaximum 25 Gbps
High Capacityh3v24m28824 vCore288 GBMaximum 25 Gbps
High Capacityh3v32m6432 vCore64 GBMaximum 25 Gbps
High Capacityh3v32m12832 vCore128 GBMaximum 25 Gbps
High Capacityh3v32m25632 vCore256 GBMaximum 25 Gbps
High Capacityh3v32m38432 vCore384 GBMaximum 25 Gbps
High Capacityh3v48m9648 vCore96 GBMaximum 25 Gbps
High Capacityh3v48m19248 vCore192 GBMaximum 25 Gbps
High Capacityh3v48m38448 vCore384 GBMaximum 25 Gbps
High Capacityh3v48m57648 vCore576 GBMaximum 25 Gbps
High Capacityh3v64m12864 vCore128 GBMaximum 25 Gbps
High Capacityh3v64m25664 vCore256 GBMaximum 25 Gbps
High Capacityh3v64m51264 vCore512 GBMaximum 25 Gbps
High Capacityh3v64m76864 vCore768 GBMaximum 25 Gbps
High Capacityh3v72m14472 vCore144 GBMaximum 25 Gbps
High Capacityh3v72m28872 vCore288 GBMaximum 25 Gbps
High Capacityh3v72m57672 vCore576 GBMaximum 25 Gbps
High Capacityh3v72m86472 vCore864 GBUp to 25 Gbps
High Capacityh3v96m19296 vCore192 GBMaximum 25 Gbps
High Capacityh3v96m38496 vCore384 GBMaximum 25 Gbps
High Capacityh3v96m76896 vCore768 GBMaximum 25 Gbps
High Capacityh3v96m115296 vCore1152 GBMaximum 25 Gbps
High Capacityh3v128m256128 vCore256 GBMaximum 25 Gbps
High Capacityh3v128m512128 vCore512 GBMaximum 25 Gbps
High Capacityh3v128m1024128 vCore1024 GBMaximum 25 Gbps
High Capacityh3v128m1536128 vCore1536 GBMaximum 25 Gbps
Table. Virtual Server server type specifications - h3 server type

1.2 - Monitoring Metrics

Cloud Monitoring service termination notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued in September 2026.
Starting after the September 2026 release, resource monitoring of the Samsung Cloud Platform via Cloud Monitoring will no longer be possible.

With the new alternative service, you can continuously perform resource monitoring by leveraging ServiceWatch released in October 2025.
ServiceWatch provides more modern and powerful features, replacing Cloud Monitoring to deliver a seamless monitoring environment.

Detailed information about ServiceWatch can be found in the ServiceWatch Overview.

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.

Performance itemsDetailed descriptionunit
Memory Total [Basic]bytes of usable memorybytes
Memory Used [Basic]Current memory usage in bytesbytes
Memory Swap In [Basic]bytes of the replaced memorybytes
Memory Swap Out [Basic]bytes of the replaced memorybytes
Memory Free [Basic]bytes of unused memorybytes
Disk Read Bytes [Basic]Read bytesbytes
Disk Read Requests [Basic]Number of read requestscnt
Disk Write Bytes [Basic]write bytesbytes
Disk Write Requests [Basic]Number of write requestscnt
CPU Usage [Basic]Average system CPU usage over 1 minute%
Instance State [Basic]Instance statusstate
Network In Bytes [Basic]Received bytesbytes
Network In Dropped [Basic]Incoming packet dropcnt
Network In Packets [Basic]Number of received packetscnt
Network Out Bytes [Basic]sent bytesbytes
Network Out Dropped [Basic]Transmit packet dropcnt
Network Out Packets [Basic]Number of transmitted packetscnt
Table. Virtual Server Monitoring Metrics (Provided by default)
Performance itemsDetailed descriptionunit
Core Usage [IO Wait]Ratio of CPU time spent in wait state (disk wait)%
Core Usage [System]Proportion of CPU time spent in kernel space%
Core Usage [User]Proportion of CPU time spent in user space%
CPU CoresNumber of CPU cores on the hostcnt
CPU Usage [Active]Percentage of CPU time used other than Idle and IOWait states%
CPU Usage [Idle]It is the proportion of CPU time spent in idle state.%
CPU Usage [IO Wait]This is the proportion of CPU time spent in a waiting state (disk wait).%
CPU Usage [System]Percentage of CPU time used by the kernel%
CPU Usage [User]Percentage of CPU time used in user space%
CPU Usage/Core [Active]Percentage of CPU time used other than Idle and IOWait states%
CPU Usage/Core [Idle]It is the proportion of CPU time spent in idle state.%
CPU Usage/Core [IO Wait]This is the proportion of CPU time spent in a waiting state (disk wait).%
CPU Usage/Core [System]Percentage of CPU time used by the kernel%
CPU Usage/Core [User]Percentage of CPU time used in user space%
DiskCPU Usage [IO Request]Proportion of CPU time during which I/O requests to the device were executed%
Disk Queue Size [Avg]The average queue length of requests executed for the device.num
Disk Read BytesThe number of bytes read per second from the device.bytes
Disk Read Bytes [Delta Avg]Average of system.diskio.read.bytes_delta for individual disksbytes
Disk Read Bytes [Delta Max]Maximum system.diskio.read.bytes_delta of individual disksbytes
Disk Read Bytes [Delta Min]Minimum of system.diskio.read.bytes_delta for individual disksbytes
Disk Read Bytes [Delta Sum]Sum of system.diskio.read.bytes_delta of individual disksbytes
Disk Read Bytes [Delta]Delta of the system.diskio.read.bytes value for each Diskbytes
Disk Read Bytes [Success]Total bytes successfully readbytes
Disk Read RequestsNumber of read requests to the disk device per secondcnt
Disk Read Requests [Delta Avg]Average of system.diskio.read.count_delta for individual diskscnt
Disk Read Requests [Delta Max]Maximum system.diskio.read.count_delta for individual diskscnt
Disk Read Requests [Delta Min]Minimum of system.diskio.read.count_delta for individual diskscnt
Disk Read Requests [Delta Sum]Sum of the system.diskio.read.count_delta of individual diskscnt
Disk Read Requests [Success Delta]Delta of system.diskio.read.count for each Diskcnt
Disk Read Requests [Success]Total number of successful readscnt
Disk Request Size [Avg]It is the average size of requests executed on the device (unit: sectors).num
Disk Service Time [Avg]Average service time (milliseconds) of input requests executed on the device.ms
Disk Wait Time [Avg]Average time taken for requests executed on the supported device.ms
Disk Wait Time [Read]Average disk wait timems
Disk Wait Time [Write]Average disk wait timems
Disk Write Bytes [Delta Avg]Average of system.diskio.write.bytes_delta for each diskbytes
Disk Write Bytes [Delta Max]Maximum system.diskio.write.bytes_delta of individual disksbytes
Disk Write Bytes [Delta Min]Minimum of system.diskio.write.bytes_delta for individual disksbytes
Disk Write Bytes [Delta Sum]Sum of system.diskio.write.bytes_delta for individual disksbytes
Disk Write Bytes [Delta]Delta of the system.diskio.write.bytes value for each Diskbytes
Disk Write Bytes [Success]Total number of bytes successfully writtenbytes
Disk Write RequestsNumber of write requests to the disk device per secondcnt
Disk Write Requests [Delta Avg]Average of system.diskio.write.count_delta for individual diskscnt
Disk Write Requests [Delta Max]Maximum system.diskio.write.count_delta of individual diskscnt
Disk Write Requests [Delta Min]Minimum of system.diskio.write.count_delta for individual diskscnt
Disk Write Requests [Delta Sum]Sum of system.diskio.write.count_delta for individual diskscnt
Disk Write Requests [Success Delta]Delta of system.diskio.write.count for each Diskcnt
Disk Write Requests [Success]Total number of successful writescnt
Disk Writes BytesBytes per second written to the devicebytes
Filesystem Hang Checkfilesystem(local/NFS) hang check(normal:1, abnormal:0)status
Filesystem NodesTotal number of file nodes in the file system.cnt
Filesystem Nodes [Free]It is the total number of available file nodes in the file system.cnt
Filesystem Size [Available]Disk space (bytes) available to unauthorized usersbytes
Filesystem Size [Free]Available disk space (bytes)bytes
Filesystem Size [Total]Total disk space (bytes)bytes
Filesystem UsageUsed disk space percentage%
Filesystem Usage [Avg]Average of individual filesystem.used.pct%
Filesystem Usage [Inode]iNode usage rate%
Filesystem Usage [Max]Maximum among individual filesystem.used.pct%
Filesystem Usage [Min]Min among individual filesystem.used.pct%
Filesystem Usage [Total]-%
Filesystem UsedUsed disk space (bytes)bytes
Filesystem Used [Inode]iNode usagebytes
Memory FreeTotal available memory (bytes)bytes
Memory Free [Actual]Actual usable Memory (bytes)bytes
Memory Free [Swap]Available Swap memorybytes
Memory TotalTotal Memorybytes
Memory Total [Swap]Total Swap memory.bytes
Memory UsagePercentage of used memory%
Memory Usage [Actual]Percentage of memory actually used%
Memory Usage [Cache Swap]cached swap usage%
Memory Usage [Swap]Percentage of used Swap memory%
Memory UsedUsed Memorybytes
Memory Used [Actual]Actual memory used (bytes)bytes
Memory Used [Swap]Used Swap memorybytes
CollisionsNetwork collisioncnt
Network In BytesNumber of received bytesbytes
Network In Bytes [Delta Avg]Average of system.network.in.bytes_delta for individual networksbytes
Network In Bytes [Delta Max]Maximum system.network.in.bytes_delta for each Networkbytes
Network In Bytes [Delta Min]Minimum of system.network.in.bytes_delta for each networkbytes
Network In Bytes [Delta Sum]Sum of system.network.in.bytes_delta for individual networksbytes
Network In Bytes [Delta]Delta of received byte countbytes
Network In DroppedNumber of deleted packets among incoming packetscnt
Network In ErrorsNumber of errors during receptioncnt
Network In PacketsNumber of received packetscnt
Network In Packets [Delta Avg]Average of system.network.in.packets_delta for individual Networkscnt
Network In Packets [Delta Max]Maximum of system.network.in.packets_delta for each Networkcnt
Network In Packets [Delta Min]Minimum of system.network.in.packets_delta for each Networkcnt
Network In Packets [Delta Sum]Sum of system.network.in.packets_delta for individual Networkscnt
Network In Packets [Delta]Delta of received packet countcnt
Network Out BytesNumber of transmitted bytesbytes
Network Out Bytes [Delta Avg]Average of system.network.out.bytes_delta for individual networksbytes
Network Out Bytes [Delta Max]Maximum system.network.out.bytes_delta for each Networkbytes
Network Out Bytes [Delta Min]Minimum of system.network.out.bytes_delta for individual Networksbytes
Network Out Bytes [Delta Sum]Sum of system.network.out.bytes_delta for individual Networksbytes
Network Out Bytes [Delta]Delta of transmitted byte countbytes
Network Out DroppedNumber of deleted packets among outgoing packetscnt
Network Out ErrorsNumber of errors during transmissioncnt
Network Out PacketsNumber of transmitted packetscnt
Network Out Packets [Delta Avg]Average of system.network.out.packets_delta for each Networkcnt
Network Out Packets [Delta Max]Maximum system.network.out.packets_delta for each Networkcnt
Network Out Packets [Delta Min]Minimum of system.network.out.packets_delta for each Networkcnt
Network Out Packets [Delta Sum]Sum of system.network.out.packets_delta for individual networkscnt
Network Out Packets [Delta]Delta of transmitted packet countcnt
Open Connections [TCP]All open TCP connectionscnt
Open Connections [UDP]All open UDP connectionscnt
Port UsageConnectable port utilization%
SYN Sent SocketsNumber of sockets in SYN_SENT state (when connecting from local to remote)cnt
Kernel PID Maxkernel.pid_max valuecnt
Kernel Thread Maxkernel.threads-max valuecnt
Process CPU UsagePercentage of CPU time consumed by the process since the last update%
Process CPU Usage/CorePercentage of CPU time used by the process since the last event%
Process Memory UsageProportion of main memory (RAM) occupied by a process%
Process Memory UsedResident Set size. The amount of memory a process occupies in RAM.bytes
Process PIDprocess pidpid
Process PPIDParent process PIDpid
Processes [Dead]Number of deadProcessescnt
Processes [Idle]idle Processes countcnt
Processes [Running]running Processes countcnt
Processes [Sleeping]sleeping processes countcnt
Processes [Stopped]stopped processes countcnt
Processes [Total]Total number of processescnt
Processes [Unknown]Number of processes whose status cannot be retrieved or is unknowncnt
Processes [Zombie]Number of zombie processescnt
Running Process Usageprocess usage%
Running ProcessesNumber of running processescnt
Running Thread UsageThread usage rate%
Running ThreadsTotal number of threads running in running processescnt
Context Switchescontext switch count (per second)cnt
Load/Core [1 min]The load over the last 1 minute divided by the number of corescnt
Load/Core [15 min]The load over the last 15 minutes divided by the number of corescnt
Load/Core [5 min]The load over the last 5 minutes divided by the number of corescnt
Multipaths [Active]External storage connection path status = active countcnt
Multipaths [Failed]External storage connection path status = failed countcnt
Multipaths [Faulty]External storage connection path status = faulty countcnt
NTP Offset lastsample’s measured offset (time difference between NTP server and local environment)num
Run Queue LengthExecution queue lengthnum
UptimeOS uptime (milliseconds)ms
Context Switchies CPUcontext switch count (per second)cnt
Disk Read Bytes [Sec]Number of bytes read in one second from a Windows logical disk
  • Windows only
cnt
Disk Read Time [Avg]Data read average time (seconds)
  • Windows only
sec
Disk Transfer Time [Avg]Disk average wait time (seconds)
  • Windows only
sec
Disk Write Bytes [Sec]Number of bytes written in one second on a Windows logical disk
  • Windows only
cnt
Disk Write Time [Avg]Average data write time (seconds)
  • Windows only
sec
Pagingfile Usagepaging file usage
  • Windows only
%
Pool Used [Non Paged]Nonpaged Pool usage in kernel memory
  • Windows only
bytes
Pool Used [Paged]Paged Pool usage in kernel memory
  • Windows only
bytes
Process [Running]Number of currently running processes
  • Windows only
cnt
Threads [Running]Number of currently running threads
  • Windows only
cnt
Threads [Waiting]Number of threads waiting for processor time
  • Windows only
cnt
Table. Additional monitoring metrics for Virtual Server (Agent installation required)

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.

Reference
For how to view metrics in ServiceWatch, refer to the ServiceWatch guide.

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.

Performance item (indicator name)Detailed descriptionunitmeaningful statistics
Instance StateInstance status display
  • 1 - Active
  • 0 - Off
None
  • Total
CPU UsageCPU usagePercent
  • Average
  • Maximum
  • Minimum
Disk Read BytesBytes read from block device (bytes)Bytes
  • Total
  • Average
  • Maximum
  • Minimum
Disk Read RequestsNumber of read requests on a block deviceCount
  • Total
  • Average
  • Maximum
  • Minimum
Disk Write BytesWrite capacity (bytes) on block deviceBytes
  • Total
  • Average
  • Maximum
  • Minimum
Disk Write RequestsNumber of write requests on block deviceCount
  • Total
  • Average
  • Maximum
  • Minimum
Network In BytesReceived bytes on the network interfaceBytes
  • Total
  • Average
  • Maximum
  • Minimum
Network In DroppedNumber of packet drops received on the network interfaceCount
  • Total
  • Average
  • Maximum
  • Minimum
Network In PacketsNumber of packets received on the network interfaceCount
  • Total
  • Average
  • Maximum
  • Minimum
Network Out BytesData transmitted on the network interface (bytes)Bytes
  • Total
  • Average
  • Maximum
  • Minimum
Network Out DroppedNumber of packet drops transmitted from the network interfaceCount
  • Total
  • Average
  • Maximum
  • Minimum
Network Out PacketsNumber of packets transmitted on the network interfaceCount
  • Total
  • Average
  • Maximum
  • Minimum
Table. Virtual Server basic metrics
Reference
Refer to the ServiceWatch Agent guide for how to collect metrics using the ServiceWatch Agent.

2 - How-to guides

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

Create Virtual Server

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

To create a Virtual Server, 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 Create Virtual Server button. 2. 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
      Detailed description
      ImageEssentialSelect the type of Image provided
      • Standard: Samsung Cloud Platform standard Image
        • Alma Linux, Oracle Linux, RHEL, Rocky Linux, Ubuntu, Windows
      • Custom: User-created Image
      • Kubernetes: Kubernetes Image
        • RHEL, Ubuntu
      • Marketplace: Image subscribed from Marketplace
      Image versionEssentialSelect version of the chosen Image
      • Provide version list of the provided server Image
      Table. Virtual Server Image and version selection input items
    • Enter or select the required information in the Service Information Input area.
      Category
      Required
      Detailed description
      Number of serversEssentialNumber of servers to create simultaneously
      • Only numeric input is allowed, enter a value between 1~100
      Service Type > Server TypeEssentialVirtual Server 서버 타입
      • Standard: standard specifications commonly used
      • High Capacity: large-capacity server specifications beyond Standard
      Service Type > Planned ComputeEssentialStatus of resources with Planned Compute set
      • In Use: Number of resources with Planned Compute that are currently in use
      • Configured: Number of resources with Planned Compute set
      • Coverage Preview: Amount applied per resource by Planned Compute
      Block StorageEssentialBlock Storage settings used by the server according to purpose
      • Basic OS: The area where the OS is installed and used
        • Enter the size in Units; 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 7 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 2 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 Service) encryption keys
          • Encryption can only be applied 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: Use when additional user 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 – 12,288 GB
        • 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 only be applied at initial creation and cannot be changed afterward
          • Using the SSD_KMS disk type may result in performance degradation
        • SSD/HDD_MultiAttach: Volume that can be attached to two or more servers
        • SSD_Provisioned: SSD volume with configurable IOPS and Throughput
      • Delete on termination: When Delete on Termination is selected, the volume is terminated together with the server
        • Volumes with snapshots are 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 and 20,000
        • Cannot be set for disk types HDD, HDD_KMS, or HDD_MultiAttach
      • Max Throughput: Enter a maximum Throughput value between 250 and 1,000
        • Cannot be set for disk types HDD, HDD_KMS, or HDD_MultiAttach
      Server GroupSelectionAfter selecting Use to set 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 a Server Group
      Place servers belonging to the same Server Group according to the selected policy using a Best Effort method
      The policy is selected from Anti-Affinity (distributed placement), Affinity (proximate placement), or 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 stage.
    • Required Information Input area, please enter or select the necessary information.
      Category
      Required
      Detailed description
      Server nameEssentialEnter 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 PortEssentialSet 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 auto‑generated or manually entered, and if Enter is selected, the user can input the IP directly
        • 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 to select, click the Create New button to generate a Public IP
          • Refresh button: Click 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 the local Subnet
        • It is not a required element for creating the service
        • A pre‑created local Subnet must be selected
        • IP can be auto‑generated or manually entered, and selecting Enter allows the user to input the IP directly
      Network Settings > Specify Existing Network PortEssentialSet 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 has an Internet Gateway attached. When selected, you can choose a NAT IP
        • NAT IP: Select the NAT IP
          • If there is no NAT IP 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): Select Use for the local subnet
        • Select a pre-created local Subnet and Port
      Security GroupSelectionSettings required to connect to the server
      • Select: Up to 5 pre‑created Security Groups can be selected
      • Create New: If there is no applicable Security Group, create one separately in the Security Group service
      • If a Security Group is not set, all connections are blocked, so you must configure it to allow the necessary connections
      KeypairEssentialUser authentication method to use when connecting to the server
      • Default login account list by OS
        • Alma Linux: almalinux
        • Oracle Linux: cloud-user
        • RHEL: cloud-user
        • Rocky Linux: rocky
        • Ubuntu: ubuntu
        • Windows: sysadmin
      Table. Virtual Server required information input fields
      Reference
      • The default OS account can serve as the default user account in a cloud environment and can be used for initial configuration via cloud-init and SCP-related functions.
      • If you delete or change the primary account, related Samsung Cloud Platform functions may not work properly, so deletion or modification is not recommended.
    • Additional Information Input area, enter or select the required information.
      Category
      Required
      Detailed description
      LockSelectionLock usage setting
      • When you use Lock, it prevents actions such as terminating, starting, or stopping the server, thereby avoiding malfunctions caused by mistakes
      Init scriptSelectionScript 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
      tagSelectionAdd Tag
      • Up to 50 can be added per resource
      • After clicking the Add Tag button, input or select Key, Value values
      Table. Virtual Server additional information input fields
  4. Summary Verify the detailed information and estimated charges generated in the panel, then click the Create button.

  5. When the popup indicating creation opens, click the Confirm button.

    • When creation is complete, verify the created resources on the Virtual Server List page.
information
  • When entering the server name, if spaces and special characters (_) are used, the OS hostname will have those spaces and special characters (_) converted to the special character (-) and set. * Refer to this when setting the OS hostname.
    • Example: If the server name is ‘server name_01’, the OS hostname is set to ‘server-name-01’.
  • If you need to manage server names uniquely, specify a different server name (Prefix) when creating them.
    • When creating a server, because the numbering does not automatically increment based on the server name (Prefix), a Virtual Server with the same name can be created.
    • Example: If you first create two Virtual Servers using the server name (Prefix) ’test’, ’test-1’ and ’test-2’ will be created. * After that, even if you create two Virtual Servers using the prefix ’test’ again, ’test-1’ and ’test-2’ will be created.
Reference
  • When creating a Virtual Server with Rocky Linux or Oracle Linux, additional configuration is required for time synchronization (NTP:Network Time Protocol). * For detailed information, refer to Linux NTP 설정하기.
  • If RHEL and Windows Server were created before July 2025, the RHEL Repository and WKMS (Windows Key Management Service) settings need to be modified. * For more information, refer to RHEL Repo 및 WKMS 설정하기.

View Virtual Server Details

The Virtual Server service lets you view and modify the complete resource list and detailed information. The Virtual Server Details page consists of Details, Monitoring, Tags, Activity History tabs.

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

  1. All Services > Compute > Virtual Server Click the 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 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 Additional Features, please refer to Virtual Server 관리 부가 기능.
      CategoryDetailed description
      Virtual Server statusState of a user-created Virtual Server
      • Build: State where a Build command has been issued
      • Building: Build in progress
      • Networking: Server creation process in progress
      • Scheduling: Server creation process in progress
      • Block_Device_Mapping: Connecting Block Storage during server creation
      • Spawning: State where the server creation process is ongoing
      • Active: Available state
      • Powering_off: State when a stop request is made
      • Deleting: Server deletion in progress
      • Reboot_Started: Reboot in progress state
      • Error: Error state
      • Migrating: State where the server is migrating to another host
      • Reboot: State where a Reboot command has been issued
      • Rebooting: Reboot in progress
      • Rebuild: State where a Rebuild command has been issued
      • Rebuilding: State when a Rebuild request is made
      • Rebuild_Spawning: State where the Rebuild process is ongoing
      • Resize: State where a Resize command has been issued
      • Resizing: Resize in progress
      • Resize_Prep: State when a server type modification is requested
      • Resize_Migrating: State where the server is moving to another host while resizing
      • Resize_Migrated: State where the 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 source server is restarted
      • Shutoff: State when powering off is completed
      • Verity_ Resize: State after Resize_Prep is performed following a server type modification request, where the server type is finalized or can be reverted
      • Resize_Reverting: State when a server type revert request is made
      • Resize_Confirming: State where the server’s Resize request is being confirmed
      Server controlButton to change server status
      • Start: Start a stopped server
      • Stop: Stop a running server
      • Restart: Restart a running server
      Image generationCreate a user Image from the current server’s Image
      Console logCurrent server console log view
      Create dumpCreate a dump of the current server
      • The dump file is created inside the Virtual Server
      RebuildThe OS area data and settings of the existing Virtual Server are deleted, and it is rebuilt as a new server
      Service cancellationCancel service button
      Table. Virtual Server status information and additional features

Detailed Information

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

CategoryDetailed description
serviceService Name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Virtual Server, it refers to the Virtual Server SRN
Resource nameresource name
  • In the Virtual Server service it refers to the Virtual Server name
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation Date/TimeService creation date and time
EditorUser who edited the service information
Modification timestampDate and time the service information was modified
Server nameServer name
  • Edit Click the button to change the name
  • When changing the server name, the OS hostname is not changed; only the information within the Samsung Cloud Platform Console is updated
  • Modification is not allowed for Virtual Servers created from other resources
Server typevCPU, memory information display
  • If you need to change to a different server type, click the Edit button to configure
Image nameServer OS Image and version
  • Image version and Image selectable by build date
LockIndicates whether Lock is enabled or disabled
  • If you need to change the Lock property value, click the Edit button to set it
Server groupServer group name to which the server belongs
  • If the server group is not used, it will not be displayed.
Keypair nameServer authentication information set by the user
  • The default login accounts for each OS are as follows.
    • Alma Linux: almalinux
    • Oracle Linux: cloud-user
    • RHEL: cloud-user
    • Rocky Linux: rocky
    • Ubuntu: ubuntu
    • Windows: sysadmin
Planned ComputeResource status with Planned Compute configured
ServiceWatch detailed monitoringDisplay whether ServiceWatch detailed monitoring is enabled
  • To enable ServiceWatch detailed monitoring, click the Edit button to configure
  • Not provided for Auto-Scaling Groups and Virtual Servers created in the Marketplace
networkNetwork information of the Virtual Server
  • VPC, standard Subnet, IP and status, Public NAT IP and status, Private NAT IP and status, Virtual IP, Security Group
  • If an IP change is required, click the Edit button to configure
    • Editing is possible only when the Virtual Server status is other than Active, Shutoff
    • For the default port, Default is displayed next to the IP, and it cannot be detached
  • If a Security Group change is required, click the Edit button to configure
  • If a Virtual IP change is required, it can be edited on the Virtual IP Management tab of the Networking > VPC > Subnet Details page
  • Add as a new network port: select a standard Subnet and IP
    • You can select a different standard Subnet within the same VPC
    • Enter the IP manually when editing
  • Add using an existing network port: select a pre‑created standard Subnet and port
Local SubnetLocal Subnet information of the Virtual Server
  • Local Subnet, Local Subnet IP, Security Group name, Virtual IP
  • If a Security Group change is required, you can click the Edit button to configure it
  • Add as a new network port: select the local Subnet and IP
    • After selecting another regular Subnet within the same VPC, enter the IP
  • Add to an existing network port: select a pre‑created local Subnet and port
Block StorageBlock Storage information attached to the server
  • Volume ID, Volume Name, Disk Type, Capacity, Connection Information, Type, Delete on termination, Status
  • Add: Connect additional Block Storage when needed
  • Edit Delete on termination: Modify the Delete on termination value of the selected Block Storage in the list
  • More > Detach: Detach the connection of the selected Block Storage from the list
    • Detachment is not possible for OS default Storage
Table. Virtual Server detailed information tab items

Monitoring

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

CategoryDetailed description
Period setting areaPeriod selection applied to the chart
  • Indicator query can be set from now up to a maximum of 455 days
Time Zone Settings AreaSelect the time zone applied to the chart
Reset buttonReset all modifications and settings in the chart.
Refresh Settings AreaSelect chart refresh interval
  • Refresh button displays information anew based on the current time
  • Click the refresh interval to select the desired interval: Off, 10 seconds, 1 minute, 2 minutes, 5 minutes, 15 minutes
Go to the service dashboardGo to the ServiceWatch dashboard list screen
MoreDisplay additional tasks for managing charts
graph areaData graph collected during the period applied to the chart
  • Available graph
    • Average CPU Usage (Percent)
    • Average Disk Reads (Bytes)
    • Average Disk Writes (Bytes)
    • Summary Disk Read Requests (Count)
    • Summary Disk Write Requests (Count)
    • Maximum Network In (Bytes)
    • Maximum Network Out (Bytes)
    • Summary Instance State (Any)
  • When the mouse cursor is placed on the graph, a popup displays the time, data value, and metric data information for that point
  • You can drag the mouse to zoom in on a specific area of the graph
  • Clicking a label shown in the legend displays detailed information about that legend in a popup
Table. Virtual Server Monitoring Tab Chart Items
Reference
  • The metrics provided by basic monitoring are data collected at 5‑minute intervals.
  • For detailed information about the ServiceWatch metrics of Virtual Server, see Virtual Server의 ServiceWatch 지표.

Tag

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

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the list of previously created Keys and Values
Table. Virtual Server Tag Tab Items

Job History

On the Virtual Server List page, you can view the operation history of the selected resource.

CategoryDetailed description
Task History ListResource Change History
  • You can view the operation details, operation time, resource type, resource name, operation result, and operator information
  • Operation History List Click the relevant resource in the list. Operation History Details popup window opens.
Table. Virtual Server operation history tab detailed information items

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.

Virtual Server Getting Started

You can start a Virtual Server that is shut off. To start 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. Virtual Server List page, click the resource to start among the stopped (Shutoff) servers, and navigate to the Virtual Server Details page.
    • On the Virtual Server List page, you can Start each resource using the right More button.
    • After selecting multiple servers with checkboxes, you can control multiple servers simultaneously via the Start button at the top.
  4. On the Virtual Server Details page, click the Start button at the top to start the server. 4. Check the status of the changed 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 상세 정보 확인하기.

Stop Virtual Server

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

  1. All Services > Compute > Virtual Server Click the menu. 1. Go to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. 2. Virtual Server List Navigate to the page.
  3. Virtual Server List page, click the resource to stop among the servers that are active, and navigate to the Virtual Server Details page.
    • On the Virtual Server List page, you can Stop each resource using 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 changed 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 상세 정보 확인하기.

Restart Virtual Server

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

  1. All Services > Compute > Virtual Server Click the 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 restart, and navigate to the Virtual Server Details page.
    • Virtual Server List page allows you to restart each resource via the right More button.
    • After selecting multiple servers with checkboxes, you can control multiple servers simultaneously via 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 Indicator item.
    • During a Virtual Server restart, the server status passes through Rebooting and finally changes to Active.
    • For detailed information about the Virtual Server status, please refer to Virtual Server 상세 정보 확인하기.

Managing Virtual Server Resources

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

Create Image

You can create an image of a running Virtual Server.

Reference

This document provides instructions on how to create a user image on a running Virtual Server.

  • Virtual Server List or Virtual Server Details page, click the Create Image button to generate a user Image.
  • Refer to Image 상세 가이드 내 Image 생성하기 for the method of uploading a user’s owned Image file to create an Image.

To create a Virtual Server Image, follow the steps below.

  1. All Services > Compute > Virtual Server Click the 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 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
      Detailed description
      Image nameEssentialthe name of the Image to be created
      • Enter within 200 characters using English letters, numbers, spaces, and special characters(-, _)
      Table. Image service information input items
  5. Check the input information and click the Done button.

    • Once creation is complete, check the created resource on the All Services > Compute > Virtual Server > Image List page.
information
  • When an Image is created, the generated Image is stored in the Object Storage used as internal storage. * Therefore, usage fees will be charged for Image storage.
  • Since the file system of an Image created from an Active Virtual Server cannot be guaranteed to be intact, it is recommended to stop the server before creating the Image.

Edit server type

You can modify the server type of a Virtual Server.

Reference
For the configurable server types provided by Virtual Server, refer to Virtual Server 서버 타입.

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

  1. All Services > Compute > Virtual Server Click the menu. 1. Go 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 control its operation. 3. Navigate to the Virtual Server Details page.
  4. On the Virtual Server Details page, check the server status and click the server type Edit button. 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 상세 정보 확인하기.
Reference
If you change the Virtual Server’s server type, monitoring performance metric data may not be collected properly for a short period. In the next collection cycle (1 minute), normal performance metrics will be collected.

Change IP

Please refer to IP 변경하기 for instructions on changing the IP.

Caution
  • If you proceed with changing the IP, you will no longer be able to communicate using that IP, and you cannot cancel the IP change while it is in progress.
  • The server is rebooted to apply the changed IP.
  • If the server is running the Load Balancer service, you must delete the old IP from the LB server group and directly add the new IP as a member of the LB server group.
  • Servers using Public NAT/Private NAT must disable and reconfigure Public NAT/Private NAT after changing the IP.
    • If you are using Public NAT/Private NAT, first disable the use of Public NAT/Private NAT, complete the IP change, and then reconfigure.
    • Whether to use Public NAT/Private NAT can be changed by clicking the Edit button of Public NAT IP/Private NAT IP on the Virtual Server Details page.
  • Public NAT IP can only be modified when there is one server, the VPC is connected to an Internet Gateway, and the regular subnet is public.

Enable detailed monitoring for ServiceWatch

By default, Virtual Server is linked with ServiceWatch for basic monitoring. You can enable detailed monitoring as needed to identify operational issues more quickly and take action. For detailed information about ServiceWatch, refer to the ServiceWatch 개요.

Caution
Basic monitoring is provided for free, but enabling detailed monitoring incurs additional charges. Please note the usage.

To enable detailed ServiceWatch monitoring for 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. Navigate to the Virtual Server List page.
  3. On the Virtual Server List page, click the resource to enable detailed ServiceWatch monitoring. 3. Navigate to the Virtual Server Details page.
  4. Click the Edit button for ServiceWatch detailed monitoring on the Virtual Server Details page. 4. ServiceWatch Detailed Monitoring Edit Navigate to the popup window.
  5. ServiceWatch Detailed Monitoring Edit In the popup window, after selecting Enable, review the instructions and click the Confirm button.
  6. On the Virtual Server Details page, view the detailed ServiceWatch monitoring items.

Disable detailed monitoring for ServiceWatch

Caution
Disabling detailed monitoring is required for cost efficiency. Maintain detailed monitoring only when absolutely necessary, and disable detailed monitoring otherwise.

To disable detailed ServiceWatch monitoring of a Virtual Server, follow these steps.

  1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Virtual Server menu. 2. Navigate to the Virtual Server List page.
  3. Virtual Server list on the page, click the resource to disable ServiceWatch detailed monitoring. 3. Navigate to the Virtual Server Details page.
  4. On the Virtual Server Details page, click the Edit button for ServiceWatch detailed monitoring. 4. ServiceWatch Detailed Monitoring Edit Navigate to the popup window.
  5. ServiceWatch Detailed Monitoring Edit In the popup window, after deselecting Enable, review the guidance message and click the Confirm button.
  6. On the Virtual Server Details page, check the ServiceWatch detailed monitoring items.

Virtual Server management add‑on features

For Virtual Server management, you can view console logs, generate dumps, and perform rebuilds. To view the console log, generate a dump, and rebuild a Virtual Server, follow these steps.

Check console log

You can view the current console log of the Virtual Server.

To view the console log of a Virtual Server, follow these steps.

  1. All Services > Compute > Virtual Server Click the 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 On the page, click the resource to view the console log. 3. Navigate to the Virtual Server Details page.
  4. Virtual Server Details on the page, click the Console Log button. 4. Console Log navigates to the popup window.
  5. Console Log Check the console log output in the popup window.

Create Dump

To create a Dump file of 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. Navigate 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.
  4. Click the Create Dump button on the Virtual Server Details page.
    • The dump file is created inside the Virtual Server.

Execute Rebuild

You can delete the OS data and configuration of the existing Virtual Server and rebuild it on a new server.

To perform a Rebuild of a Virtual Server, follow these steps.

  1. All Services > Compute > Virtual Server Click the menu. 1. Go 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 perform Rebuild. 3. Navigate to the Virtual Server Details page.
  4. On the Virtual Server Details page, click the Rebuild button.
    • During a Virtual Server Rebuild, the server status changes to Rebuilding, and when the Rebuild is complete, it returns to its pre‑Rebuild state.
    • For detailed information about the Virtual Server status, please refer to Virtual Server 상세 정보 확인하기.

Terminate Virtual Server

If you terminate an unused Virtual Server, you can reduce operating costs. However, if you terminate a Virtual Server, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact of service interruption.

Caution
Please be aware that data cannot be recovered after terminating the service.

To cancel 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. Virtual Server List page is accessed.
  3. On the Virtual Server List page, select the resource to terminate, and click the Terminate Service button.
    • The termination of attached storage depends on the Delete on termination setting; see 해지 제약 사항.
  4. If the termination is complete, check on the Virtual Server list page whether the resource has been terminated.

Termination constraints

When a Virtual Server termination request cannot be processed, a popup window will provide guidance. Please refer to the case below.

Cancellation not allowed
  • If File Storage is connected: Disconnect the File Storage first.
  • If the LB server group is connected: First, disconnect the LB server group pool connection.
  • When Lock is set: After changing the Lock setting to disabled, try again.
  • If the Auto-Scaling Group attached to the Virtual Server is not In Service: After changing the status of the attached Auto-Scaling Group, try again.

Termination of attached storage varies depending on the Delete on termination setting; please refer to it.

Delete on termination: delete per configuration
  • Whether the volume is deleted also depends on the Delete on termination setting.
    • Delete on termination when not set: Even if you terminate the Virtual Server, the volume will not be deleted.
    • Delete on termination when set: If the Virtual Server is terminated, the volume will be deleted.
  • Volumes that have a snapshot will not be deleted even if Delete on termination is set.
  • A multi-attach volume can be deleted only when the server being deleted is the last remaining server attached to the volume.

2.1 - Image

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

Create Image

You can create and use the Image service while using the Virtual Server service in the Samsung Cloud Platform Console.

To create an Image, follow the steps below.

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

  2. On the Service Home page, click the Image menu. 2. Go to the Image list page.

  3. Click the Create Image button on the Image List page. 3. Navigate to the Image creation page.

    • Enter or select the required information in the Service Information Input area.
      Category
      required status
      Detailed description
      Image nameRequiredthe name of the Image to create
      • Enter within 255 characters using English letters, numbers, spaces, and special characters(-, _)
      Image file > URLRequiredAfter uploading an image file to Object Storage, enter the URL
      • The URL can be copied on the Object Storage Details page
      • The bucket in Object Storage where the image file is uploaded must exist in the same zone as the server to be created
      • Image files can only be in the .qcow2 format
      • You must upload a secure image file to minimize security risks.
      OS typeRequiredOS type of the uploaded Image file
      • Select from Alma Linux, CentOS, Oracle Linux, RHEL, Rocky Linux, Ubuntu
      Minimum diskRequiredMinimum disk capacity (GB) of the Image to be created
      • 0~12,288GB, please enter a value
      Minimum RAMRequiredMinimum RAM size (GB) of the Image to be created
      • 0~2,097,151GB Enter a value
      VisibilityRequiredDisplay access permissions for the Image
      • Private: Only usable within the account
      • Shared: Can be shared across accounts
      ProtectedSelectionSelect whether Image deletion is prohibited
      • If you check Use, it prevents accidental deletion of the Image
      • This setting cannot be changed after the Image is created
      Table. Image service information input items
    • Additional Information Input in this area, enter or select the required information.
      Category
      required status
      Detailed description
      tagSelectionAdd Tag
      • Up to 50 per resource can be added
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. Image additional information input fields
  4. 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 resources on the Image List page.

Check Image detailed information

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

To view detailed information of the Image service, follow the steps below.

  1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Image menu. 2. Go to the Image list page.
  3. On the Image list page, click the resource to view detailed information. 3. Navigate to the Image Details page.
    • Image Details page displays status information and additional feature information, and consists of Details, Tags, Activity Log tabs.
      CategoryDetailed description
      Image statusStatus of the Image created by the user
      • Active: Available state
      • Queued: When an Image creation request is made, the Image is uploaded and is pending processing
      • Importing: When an Image creation request is made, the Image is uploaded and is being processed
      Create shared ImageCreate an Image to share with another Account
      • Creation is possible only when the Image’s Visibility is private and the Image contains snapshot information
      • Creation is not allowed if the OS disk size is 500 GB or larger
      Share with another accountImage can be shared with another Account
      • If the Image’s Visibility is Shared, it can be shared with another Account
      • Create shared Image or displayed only on Images created by uploading a qcow2 file
      Delete ImageDelete Image button
      • Deleting the Image cannot be undone
      Table. Image status information and additional functions

Detailed Information

On the Image list page, you can view detailed information of the selected resource and edit the information if needed.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • Image refers to Image SRN
Resource nameImage name
Resource IDImage’s unique resource ID
ConstructorUser who created the Image
Creation date and timeImage creation timestamp
ModifierUser who edited the image information
Modification date and timeDate and time the image information was modified
Image nameImage name
Minimum diskImage’s minimum disk capacity (GB)
  • If you need to modify the minimum disk, click the Edit button to set it
Minimum RAMMinimum RAM size (GB) of the Image
OS typeImage OS type
  • Alma Linux, CentOS, Oracle Linux, RHEL, Rocky Linux, SLES, Ubuntu
OS hash algorithmOS hash algorithm method
VisibilityDisplay access permissions for the Image
  • Private: Only usable within the account
  • Shared: Can be shared across accounts
ProtectedSelect whether Image deletion is prohibited
  • Use setting prevents accidental deletion of Image
Image sizeImage size
  • If the size of the generated Image is 1 GB or less, it is displayed as 1 GB
  • For Images created via snapshot, not displayed
Image typeClassification by Image creation method
  • Snapshot-Based: When the configuration of the currently used Virtual Server is created as an Image
  • Image-Based: When an Image is created by uploading a qcow2 extension file or by creating a shared Image
Image file URLWhen creating an Image, the URL of the Image file uploaded to Object Storage
  • Virtual Server detail page does not show Images created via the Image creation menu, but shows Images uploaded to Object Storage
Sharing statusCurrent status of sharing the Image with another Account
  • Approved Account ID: ID of the Account for which sharing is approved
  • Modification timestamp: The time when sharing was requested to another Account, and if the sharing status later changes from Pending → Accepted, it is updated to that time
  • Status: Approved status
    • Accepted: sharing is approved and active
    • Pending: awaiting approval
  • Sharing stopped: sharing has been stopped
Table. Image detail information tab items

Tag

Image List page allows you to view the tag information of the selected resource, and to add, modify, or delete it.

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the list of previously created Keys and Values
Table. Image tag tab item

Job History

You can view the operation history of the selected resource on the Image list page.

CategoryDetailed description
Task History ListResource change history
  • Operation timestamp, resource ID, resource name, operation details, event topic, operation result, check operator information
Table. Image Work History Tab Detailed Information Items

Image resource management

Describes the control and management functions of the generated Image.

Create shared Image

Create an Image to share with another Account.

Notice
  • You can create a shared Image only when the Image’s Visibility is private and the Image contains snapshot information.
  • If the OS disk size is 500 GB or larger, a shared Image cannot be created.
  • Only one OS area disk volume is included in the imaging target for shared images. * Since the additional attached data volume is not included in the Image, if needed, copy the data to a separate volume and use the volume migration feature.

To create a shared Image, follow the steps below.

  1. Log in to the account to be shared and 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 Image menu. 2. Go to the Image list page.
  3. On the Image List page, click the Image to create a shared Image. 3. Navigate to the Image Details page.
  4. Click the Create Image for Sharing button. 4. A popup window opens to notify the creation of a shared Image.
  5. After reviewing the notification content, click the Complete button.

Share Image to another Account

Create an Image to share with another Account.

Notice
  • You can share only the Image created by uploading a .qcow2 extension file or by using Create Shared Image on the Image Details page with another Account.
  • The Visibility of the Image to be shared must be Shared.

To share an Image with another Account, follow these steps.

  1. Log in to the account to be shared and 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 Image menu. 2. Go to the Image list page.

  3. Image List page, click the Image you want to share with another Account. 3. Go to the Image Details page.

  4. Share to another Account Click the button. 4. A popup window notifying image sharing opens.

  5. After reviewing the notification content, click the Confirm button. 5. Go to the Share Image with another Account page.

  6. Share Image with another Account on the page, enter Share Account ID, and click the Complete button. 6. A popup window notifying image sharing opens.

    Category
    required status
    Detailed description
    Image name-Name of the Image to share
    • Input not allowed
    Image ID-Image ID to share
    • Input not allowed
    Shared Account IDRequiredEnter another Account ID to share
    • English letters, numbers, and special characters- using them, enter within 64 characters
    Table. Image sharing items to another account

  7. After reviewing the notification content, click the Confirm button. 7. You can check the information from the sharing status on the Image Details page.

    • When the request is first made, the status is Pending, and when the receiving Account approves it, it changes to Accepted; if the approval is denied, it changes to Rejected.

Receive an Image shared from another Account

To receive an Image shared from another Account, follow these steps.

  1. Log in to the account to be shared and 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 Image menu. 2. Go to the Image list page.

  3. On the Image List page, click the More > Image Share Request List button. 3. Image sharing request list The popup window opens.

  4. Image Sharing Request List In the popup window, click the Approve or Reject button for the Image to be shared.

    CategoryDetailed description
    Image nameName of shared Image
    OS typeOS type of shared Image
    Owner Account IDOwner Account ID of the shared Image
    Creation date and timeCreation time of shared Image
    ApprovalApprove the shared image
    RejectReject the shared image
    Table. Image sharing request list item

  5. After reviewing the notification content, click the Confirm button. 5. You can view the shared Image from the Image list.

Delete Image

You can delete unused Image. However, since an Image cannot be recovered once deleted, you should fully consider the impact before proceeding with the deletion.

Caution
Please be aware that data cannot be recovered after deleting the service.

To delete the Image, follow these steps.

  1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Image menu. 2. Go to the Image list page.
  3. On the Image list page, select the resource to delete, and click the Delete button.
    • On the Image List page, select multiple Image check boxes and click the Delete button at the top of the resource list.
  4. After the deletion is complete, verify on the Image List page that the resource has been removed.

2.2 - Keypair

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

Creating a Keypair

In the Samsung Cloud Platform Console, you can create and use the Keypair service while using the Virtual Server service.

To create a keypair, 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 Keypair menu. You will be taken to the Keypair List page.

  3. On the Keypair List page, click the Create Keypair button. You will be taken to the Create Keypair page.

    • Enter the required information in the Service Information Input area.
      Category
      Required status
      Detailed description
      Keypair nameRequiredName of the Keypair to create
      • Enter within 255 characters using English letters, numbers, spaces, and special characters(-, _)
      Keypair typeRequiredssh
      Table. Keypair service information input fields
    • In the Additional Information Input area, enter or select the required information.
      Category
      Required
      Detailed description
      tagSelectionAdd Tag
      • Up to 50 can be added per resource
      • After clicking the Add Tag button, enter or select Key, Value values
      Table. Keypair additional information input fields
  4. Check the input information and click the Create button.

    • After creation is complete, check the created resources on the Keypair list page.
Caution
  • After creation is complete, you can download the Key only once for the first time. Since reissuance is not possible, ensure that it has been downloaded.
  • Store the downloaded Private Key in a safe place.

View detailed information of the Keypair

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

To view detailed information about a keypair, 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 Keypair menu. You will be taken to the Keypair List page.
  3. On the Keypair List page, click the resource to view detailed information. You will be taken to the Keypair Details page.
    • Keypair Details page displays status information and additional feature information, and consists of Details, Tags, Activity Log tabs.

Detailed Information

On the Keypair List page, you can view detailed information of the selected resource and edit the information if needed.

CategoryDetailed description
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Keypair, it refers to the Keypair SRN
Resource nameKeypair name
Resource IDUnique resource ID of the keypair
ConstructorUser who created the keypair
Creation date and timeKeypair creation timestamp
editorUser who modified the keypair information
Modification dateKeypair information modification timestamp
Keypair nameKeypair name
FingerprintA unique value for identifying the key
User IDUser ID of the keypair creator
public keyPublic key information
Table. Keypair detailed information tab items

tag

On the Keypair List page, you can view the tag information of the selected resource and add, modify, or delete it.

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the list of previously created Keys and Values
Table. Keypair Tag Tab Items

Job History

On the Keypair list page, you can view the operation history of the selected resource.

CategoryDetailed description
Task History ListResource Change History
  • Operation Time, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, Verify Operator Information
Table. Keypair operation history tab detailed information items

Keypair Resource Management

Describes the control and management functions of a keypair.

Get public key

To retrieve the public key, follow these steps.

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

  2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.

  3. On the Keypair List page, click the More button at the top and then click the Import Public Key button. You will be taken to the Import Public Key page.

    • Required Information Input area, please enter or select the required information.
      Category
      Required
      Detailed description
      Keypair nameRequiredKeypair name to create
      Keypair typeRequiredssh
      public keyRequiredPublic Key Input
      • Load File: Select the Attach File button to attach the public key file
        • Only files with the .pem extension can be attached
      • Public Key Input: Paste the copied public key value
        • Keypair Details page allows copying the public key value
      Table. Required input fields for retrieving the public key
  4. Review the entered information and click the Complete button.

    • When creation is complete, check the created resource on the Keypair list page.
Notice
Even if you generate a new Keypair using Get Public Key, the Keypair cannot be re-downloaded. Use the Keypair that was issued at the time of initial creation.

Delete Keypair

You can delete unused Keypairs. However, once a Keypair is deleted it cannot be recovered, so please review the impact thoroughly beforehand before proceeding with deletion.

Caution
Please note that data cannot be recovered after deleting the service.

To delete a keypair, follow these steps.

  1. Click the All Services > Compute > Virtual Server menu. Go to the Service Home page of Virtual Server.
  2. On the Service Home page, click the Keypair menu. You will be taken to the Keypair List page.
  3. On the Keypair List page, select the resource to delete, and click the Delete button.
    • On the Keypair List page, select multiple Keypair check boxes and click the Delete button at the top of the resource list.
  4. After the deletion is complete, verify on the Keypair List page that the resource has been deleted.

2.3 - Server Group

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

Create Server Group

In the Samsung Cloud Platform Console, you can create and use the Server Group service while using the Virtual Server service.

To create a Server Group, follow the steps below.

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

  2. On the Server Group page, click the Server Group menu. 2. Navigate to the Server Group List page.

  3. On the Server Group List page, click the Create Server Group button. 3. Server Group creation navigate to the page.

    • Enter or select the required information in the Service Information Input area.
      Category
      required status
      Detailed description
      Server Group nameRequiredEnter the name of the Server Group to be created
      • using English letters, numbers, spaces, and special characters (-, _) within 255 characters
      PolicyRequiredSelect the placement policy for Virtual Servers belonging to the same Server Group
      • Anti-Affinity(Distributed placement): A policy that places servers belonging to a Server Group on different racks and hosts as much as possible
      • Affinity(Proximity placement): A policy that places servers belonging to a Server Group close together within the same rack and host as much as possible
      • Partition(Virtual Server and Block Storage distributed placement): A policy that places Virtual Servers and their associated Block Storage from a Server Group into different distribution units (Partitions)
        • Up to three distributions are possible, and the setting can be applied when the number of possible distributions is two or more to ensure resource availability
        • Display the Partition number alongside to clearly indicate which Partition each Virtual Server and its associated Block Storage belong to
        • Partition numbers are assigned based on the Partition Size (up to 3) configured for the Server Group
      Table. Server Group Service Information Input Items
      Reference
      • Virtual Servers that belong to the same Server Group are placed on a Best Effort basis according to policy, but this is not strictly guaranteed.
    • Enter or select the required information in the Additional Information Input area.
      Category
      required status
      Detailed description
      tagSelectionAdd Tag
      • Up to 50 per resource can be added
      • After clicking the Add Tag button, input or select Key, Value values
      Table. Server Group additional information input items
  4. Check the input information and click the Generate button.

  5. When the popup notifying creation opens, click the Confirm button.

    • When creation is complete, check the created resources on the Server Group List page.

Check Server Group detailed information

The Server Group service lets you view and modify the complete resource list and detailed information. Server Group Details page consists of Details, Tags, Activity Log tabs.

To view detailed information about the Server Group, follow the steps below.

  1. All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Server Group menu. 2. Go to the Server Group List page.
  3. On the Server Group list page, click the resource to view detailed information. 3. Navigate to the Server Group Details page.
    • The Server Group Details page displays status information and additional feature information, and consists of Details, Tags, Operation History tabs.

Detailed Information

Server Group List page allows you to view detailed information of the selected resource and, if necessary, edit the information.

CategoryDetailed description
serviceservice name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • In Server Group, it refers to the Server Group SRN
Resource nameServer Group name
Resource IDServer Group’s unique resource ID
ConstructorUser who created the Server Group
Creation date and timeServer Group creation date and time
Server Group nameServer Group name
PolicyAnti-Affinity(distributed placement), Affinity(proximal placement), Partition(distributed placement of Virtual Server and Block Storage)
Partition SizePartition Size
Server Group memberServer name and Partition information of Virtual Servers belonging to the Server Group
  • Members cannot be modified after the initial Virtual Server is created
  • Anti-Affinity (distributed placement), Affinity (proximate placement) policy: Since this policy defines only the relative placement relationship between Virtual Servers, the Samsung Cloud Platform Console provides only the list of Virtual Servers belonging to the policy
  • Partition (distributed placement of Virtual Server and Block Storage) policy: The Partition number is displayed together so that you can clearly see which Partition the Virtual Server and its associated Block Storage belong to
    • Partition numbers are assigned based on the Partition Size (up to 3) set for the Server Group
Table. Server Group detailed information tab items

Tag

Server Group list page lets you view the tag information of the selected resource, and add, modify, or delete it.

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the list of previously created Keys and Values
Table. Server Group Tag Tab Items

Job History

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

CategoryDetailed description
Task History ListResource change history
  • Operation timestamp, resource ID, resource name, operation details, event topic, operation result, check operator information
Table. Server Group operation history tab detailed information items

Delete Server Group

You can delete unused Server Groups. However, since a Server Group cannot be recovered once deleted, please review the impact thoroughly in advance before proceeding with deletion.

Caution
Please be aware that data cannot be recovered after deleting the service.

To delete a Server Group, follow these steps.

  1. All Services > Compute > Virtual Server menu, click. 1. Navigate to the Service Home page of the Virtual Server.
  2. On the Service Home page, click the Server Group menu. 2. Go to the Server Group List page.
  3. On the Server Group List page, select the resource to delete, and click the Delete button.
    • On the Server Group List page, select multiple Server Group check boxes, and click the Delete button at the top of the resource list.
  4. After deletion is complete, check on the Server Group List page whether the resource has been deleted.

2.4 - Change IP

You can change the Virtual Server’s IP and add a network port to the Virtual Server to configure the IP.

Change IP

You can change the IP of the Virtual Server.

Caution
  • If you proceed with changing the IP, you will no longer be able to communicate using that IP, and you cannot cancel the IP change while it is in progress.
  • The server is rebooted to apply the changed IP.
  • If the server is running the Load Balancer service, you must delete the old IP from the LB server group and directly add the new IP as a member of the LB server group.
  • Servers using Public NAT/Private NAT must disable and reconfigure Public NAT/Private NAT after changing the IP.
    • If you are using Public NAT/Private NAT, first disable the use of Public NAT/Private NAT, complete the IP change, and then reconfigure.
    • You can change the usage of Public NAT/Private NAT by clicking the Edit button of Public NAT IP/Private NAT IP on the Virtual Server Details page.
  • Public NAT IP can only be modified when there is one server, the VPC is connected to an Internet Gateway, and the regular subnet is public.

To change the IP, follow these steps.

  1. All Services > Compute > Virtual Server Click the menu. 1. Go to the Service Home page of the Virtual Server.
  2. Click the Virtual Server menu on the Service Home page. 2. Go to the Virtual Server List page.
  3. On the Virtual Server list page, click the resource whose IP you want to change. 3. Virtual Server Details navigate to the page.
  4. On the Virtual Server Details page, click the Edit button for the IP entry you want to change. 4. IP edit The popup window opens.
  5. Edit IP in the popup window, after selecting Subnet, enter the IP to change.
  6. When the setup is complete, click the Confirm button.
  7. When the popup notifying IP modification opens, click the Confirm button.

Configure IP on the server after adding a network port

If you create a Virtual Server with Ubuntu Linux, after adding a network port in Samsung Cloud Platform, you also need to configure the IP on the server.

  1. As the root user on the Virtual Server’s OS, use the ip command to verify the assigned network interface name.

    Color mode
    ip a
    ip a
    코드블록. ip 명령어 - 네트워크 인터페이스 확인 명령어

    • If an added interface is present, the following result is displayed.
    Color mode
    [root@scp-test-vm-01 ~] # ip a
    3: ens7: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
        link/ether fa:16:3e:98:b6:64 brd ff:ff:ff:ff:ff:ff
        altname enp0s7
    [root@scp-test-vm-01 ~] # ip a
    3: ens7: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
        link/ether fa:16:3e:98:b6:64 brd ff:ff:ff:ff:ff:ff
        altname enp0s7
    코드블록. ip 명령어 - 네트워크 인터페이스 확인 결과
  2. Open the /etc/netplan/50-cloud-init.yaml file using a text editor (e.g., vim).

  3. Add the following content to the /etc/netplan/50-cloud-init.yaml file and save it.

    Color mode
    network:
    version: 2
    ethernets:
    ens7:
    match:
    macaddress: "fa:16:3e:98:b6:64"
          dhcp4: true
          set-name: "ens7"
          mtu: 9000
    network:
    version: 2
    ethernets:
    ens7:
    match:
    macaddress: "fa:16:3e:98:b6:64"
          dhcp4: true
          set-name: "ens7"
          mtu: 9000
    코드블록. YAML 파일 편집
Reference
Indentation is important in YAML files that configure netplan. When modifying a YAML file, please refer to the existing settings and be careful.
  1. Use the netplan command to set an IP on the added network DEVICE.

    Color mode
    netplan --debug apply
    netplan --debug apply
    코드블록. netplan 적용
  2. Use the ip command to verify that the IP is set correctly.

    Color mode
    [root@scp-test-vm-01 ~] # ip a
    3: ens7: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
        link/ether fa:16:3e:98:b6:64 brd ff:ff:ff:ff:ff:ff
        altname enp0s7
        inet 10.10.10.10/24 metric 100 brd 10.10.10.255 scope global dynamic ens7
           valid_lft 43197sec preferred_lft 43197sec
        inet6 fe80::f816:3eff:fe0a:96bf/64 scope link
           valid_lft forever preferred_lft forever
    [root@scp-test-vm-01 ~] # ip a
    3: ens7: <BROADCAST,MULTICAST> mtu 9000 qdisc noop state DOWN group default qlen 1000
        link/ether fa:16:3e:98:b6:64 brd ff:ff:ff:ff:ff:ff
        altname enp0s7
        inet 10.10.10.10/24 metric 100 brd 10.10.10.255 scope global dynamic ens7
           valid_lft 43197sec preferred_lft 43197sec
        inet6 fe80::f816:3eff:fe0a:96bf/64 scope link
           valid_lft forever preferred_lft forever
    코드블록. IP 설정 확인

2.5 - Configure Linux NTP

Users who create a Virtual Server with Rocky Linux or Oracle Linux via the Samsung Cloud Platform Console need additional configuration for time synchronization (NTP:Network Time Protocol). For other standard Linux images (RHEL, Alma Linux, Ubuntu), NTP is already configured, so no extra setup is required.

Installing NTP Daemon

You can configure NTP by installing the chrony daemon. To install the chrony daemon, follow the steps below.

Reference
For detailed information about chrony, see the chronyc page.
  1. Check whether the chrony package is installed by using the dnf command as the root user on the OS of the Virtual Server.

    Color mode
    dnf list chrony
    dnf list chrony
    Code block. dnf command - command to verify the chrony package installation

    • If the chrony package is installed, the following result is displayed.
Color mode
[root@scp-test-vm-01 ~] # dnf list chrony
Last metadata expiration check: 1:47:29 ago on Wed 19 Feb 2025 05:55:57 PM KST.
Installed Packages
chrony.x86_64                              3.5-1.0.1.el8                                              @anaconda
[root@scp-test-vm-01 ~] # dnf list chrony
Last metadata expiration check: 1:47:29 ago on Wed 19 Feb 2025 05:55:57 PM KST.
Installed Packages
chrony.x86_64                              3.5-1.0.1.el8                                              @anaconda
code block. dnf command - result of checking chrony package installation
  1. If the chrony package is not installed, install the chrony package using the dnf command.
    Color mode
    dnf install chrony -y
    dnf install chrony -y
    code block. dnf command - chrony package installation verification command

Configuring NTP Daemon

Reference
For detailed information about chrony, see the chronyc page.

To configure the chrony daemon, follow these steps.

  1. Open the /etc/chrony.conf file using a text editor (e.g., vim).
  2. Add the following content to the /etc/chrony.conf file and save it.
Color mode
server 198.19.0.54 iburst
server 198.19.0.54 iburst
Code block. Edit /etc/chrony.conf
  1. Use the systemctl command to configure the chrony daemon to start automatically.
Color mode
systemctl enable chronyd
systemctl enable chronyd
Code block. systemctl command - configure automatic start of chrony daemon
  1. Restart the chrony daemon using the systemctl command.

    Color mode
    systemctl restart chronyd
    systemctl restart chronyd
    code block. systemctl command - restart chrony daemon

  2. Run the chronyc sources command with the “v” option (display detailed information) to check the IP address of the configured NTP server and verify whether synchronization is in progress.

    Color mode
    chronyc sources -v
    chronyc sources -v
    Code block. chronyc sources command - check NTP synchronization

    • When you run the chronyc sources command, the following result is displayed.
Color mode
[root@scp-test-vm-01 ~] # chronyc sources -v

210 Number of sources = 1



  .-- Source mode   '^' = server,   '=' = peer,   '#' = local clock.

 / .- Source state     '*' = current synced,   '+' = combined ,   '-' = not combined,

| /    '?' = unreachable,   'x' = time may be in error,   '~' = time too variable.

|| .- xxxx [ yyyy ] +/- zzzz

||                      Reachability register (octal) -.                        |  xxxx = adjusted offset,

||                      Log2(Polling interval) --.          |                    |  yyyy = measured offset,

||                                                             |                   |  zzzz = estimated error.

||                                                        |       |                   

MS Name/IP address                  Stratum   Poll   Reach   LastRx   Last    sample

=========================================================================

^* 198.19.0.54                                 2      6     377      52      -129us[  -128us] +/-     14ms
[root@scp-test-vm-01 ~] # chronyc sources -v

210 Number of sources = 1



  .-- Source mode   '^' = server,   '=' = peer,   '#' = local clock.

 / .- Source state     '*' = current synced,   '+' = combined ,   '-' = not combined,

| /    '?' = unreachable,   'x' = time may be in error,   '~' = time too variable.

|| .- xxxx [ yyyy ] +/- zzzz

||                      Reachability register (octal) -.                        |  xxxx = adjusted offset,

||                      Log2(Polling interval) --.          |                    |  yyyy = measured offset,

||                                                             |                   |  zzzz = estimated error.

||                                                        |       |                   

MS Name/IP address                  Stratum   Poll   Reach   LastRx   Last    sample

=========================================================================

^* 198.19.0.54                                 2      6     377      52      -129us[  -128us] +/-     14ms
Code block. chronyc sources command - check NTP synchronization
  1. Run the chronyc tracking command to check the synchronization metrics.
    Color mode
    [root@scp-test-vm-01 ~] # chronyc tracking
    Reference ID        : A9FEA9FE (198.19.0.54)
    Stratum              : 3
    Ref time  (UTC)     : Wed  Feb  19  18:48:41  2025
    System time         : 0.000000039 seconds fast of NTP time
    Last offset            : -0.000084246 seconds
    RMS offset           : 0.000084246 seconds
    Frequency            : 21.667 ppm slow
    Residual freq        : +4.723 ppm
    Skew                  : 0.410 ppm
    Root delay           : 0.000564836 seconds
    Root dispersion     : 0.027399288 seconds
    Update interval      : 2.0 seconds
    Leap status           : Normal
    [root@scp-test-vm-01 ~] # chronyc tracking
    Reference ID        : A9FEA9FE (198.19.0.54)
    Stratum              : 3
    Ref time  (UTC)     : Wed  Feb  19  18:48:41  2025
    System time         : 0.000000039 seconds fast of NTP time
    Last offset            : -0.000084246 seconds
    RMS offset           : 0.000084246 seconds
    Frequency            : 21.667 ppm slow
    Residual freq        : +4.723 ppm
    Skew                  : 0.410 ppm
    Root delay           : 0.000564836 seconds
    Root dispersion     : 0.027399288 seconds
    Update interval      : 2.0 seconds
    Leap status           : Normal
    code block. chronyc tracking command - NTP synchronization metric

2.6 - Configure RHEL Repo and WKMS

information
  • If a user creates RHEL and Windows Server prior to August 2025 via the Samsung Cloud Platform Console, they need to modify the RHEL Repository and WKMS (Windows Key Management Service) settings.
  • The SCP RHEL Repository is a repository provided by SCP to support user environments such as VPC Private Subnets where external access is restricted.
    Since the SCP RHEL Repository synchronizes with each Region Local Repository according to an internal schedule, it is recommended to switch to an external public mirror site to apply the latest patches quickly.

RHEL Repository Configuration Guide

In Samsung Cloud Platform, when using RHEL, you can install and download the same packages as the official RHEL Repository by using the RHEL Repository provided by SCP.
SCP provides the latest repository for the given major version by default. To configure the RHEL repository, follow the steps below.

  1. As the root user on the Virtual Server, use the cat command to verify the /etc/yum.repos.d/scp.rhel8.repo or /etc/yum.repos.d/scp.rhel9.repo settings.

    Color mode
    cat /etc/yum.repos.d/scp.rhel8.repo
    cat /etc/yum.repos.d/scp.rhel8.repo
    Code block. Verify repo configuration (RHEL8)
    Color mode
    cat /etc/yum.repos.d/scp.rhel9.repo
    cat /etc/yum.repos.d/scp.rhel9.repo
    Code block. Verify repo configuration (RHEL9)

    • When checking the configuration file, the following result is displayed.
      Color mode
      [rhel-8-baseos]
      name=rhel-8-baseos
      gpgcheck=0
      enabled=1
      baseurl=http://scp-rhel8-ip/rhel/8/baseos
      [rhel-8-baseos-debug]
      name=rhel-8-baseos-debug
      gpgcheck=0
      enabled=1
      baseurl=http://scp-rhel8-ip/rhel/8/baseos-debug
      [rhel-8-appstream]
      name=rhel-8-appstream
      gpgcheck=0
      enabled=1
      baseurl=http://scp-rhel8-ip/rhel/8/appstream
      [rhel-8-baseos]
      name=rhel-8-baseos
      gpgcheck=0
      enabled=1
      baseurl=http://scp-rhel8-ip/rhel/8/baseos
      [rhel-8-baseos-debug]
      name=rhel-8-baseos-debug
      gpgcheck=0
      enabled=1
      baseurl=http://scp-rhel8-ip/rhel/8/baseos-debug
      [rhel-8-appstream]
      name=rhel-8-appstream
      gpgcheck=0
      enabled=1
      baseurl=http://scp-rhel8-ip/rhel/8/appstream
      Code block. Verify repo configuration (RHEL8)
      Color mode
      [rhel-9-for-x86_64-baseos-rpms]
      name=rhel-9-for-x86_64-baseos-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/baseos
      gpgcheck=0
      enabled=1
      [rhel-9-for-x86_64-appstream-rpms]
      name=rhel-9-for-x86_64-appstream-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/appstream
      gpgcheck=0
      enabled=1
      [codeready-builder-for-rhel-9-x86_64-rpms]
      name=codeready-builder-for-rhel-9-x86_64-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/codeready-builder
      gpgcheck=0
      enabled=1
      [rhel-9-for-x86_64-highavailability-rpms]
      name=rhel-9-for-x86_64-highavailability-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/ha
      gpgcheck=0
      enabled=1
      [rhel-9-for-x86_64-supplementary-rpms]
      name=rhel-9-for-x86_64-supplementary-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/supplementary
      gpgcheck=0
      enabled=1
      [rhel-9-for-x86_64-baseos-rpms]
      name=rhel-9-for-x86_64-baseos-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/baseos
      gpgcheck=0
      enabled=1
      [rhel-9-for-x86_64-appstream-rpms]
      name=rhel-9-for-x86_64-appstream-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/appstream
      gpgcheck=0
      enabled=1
      [codeready-builder-for-rhel-9-x86_64-rpms]
      name=codeready-builder-for-rhel-9-x86_64-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/codeready-builder
      gpgcheck=0
      enabled=1
      [rhel-9-for-x86_64-highavailability-rpms]
      name=rhel-9-for-x86_64-highavailability-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/ha
      gpgcheck=0
      enabled=1
      [rhel-9-for-x86_64-supplementary-rpms]
      name=rhel-9-for-x86_64-supplementary-rpms
      baseurl=http://scp-rhel9-ip/rhel/$releasever/x86_64/supplementary
      gpgcheck=0
      enabled=1
      Code block. Check repo configuration (RHEL9)
  2. Use a text editor (e.g., vim) to open the /etc/hosts file.

  3. Modify the /etc/hosts file with the following content and save it.

    Color mode
    198.19.2.13 scp-rhel8-ip scp-rhel9-ip scp-rhel-ip
    198.19.2.13 scp-rhel8-ip scp-rhel9-ip scp-rhel-ip
    code block. Change /etc/hosts file settings

  4. Use the yum command to verify the RHEL repository connection configured on the server.

    Color mode
    yum repolist –v
    yum repolist –v
    Code block. Verify repository connection settings

    • If the RHEL repository is successfully connected, you can view the repository list.
      Color mode
      Repo-id            : rhel-8-appstream
      Repo-name          : rhel-8-appstream
      Repo-revision      : 1718903734
      Repo-updated       : Fri 21 Jun 2024 02:15:34 AM KST
      Repo-pkgs          : 38,260
      Repo-available-pkgs: 25,799
      Repo-size          : 122 G
      Repo-baseurl       : http://scp-rhel8-ip/rhel/8/appstream
      Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
      Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
      
      Repo-id            : rhel-8-baseos
      Repo-name          : rhel-8-baseos
      Repo-revision      : 1718029433
      Repo-updated       : Mon 10 Jun 2024 11:23:52 PM KST
      Repo-pkgs          : 17,487
      Repo-available-pkgs: 17,487
      Repo-size          : 32 G
      Repo-baseurl       : http://scp-rhel8-ip/rhel/8/baseos
      Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
      Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
      
      Repo-id            : rhel-8-baseos-debug
      Repo-name          : rhel-8-baseos-debug
      Repo-revision      : 1717662461
      Repo-updated       : Thu 06 Jun 2024 05:27:41 PM KST
      Repo-pkgs          : 17,078
      Repo-available-pkgs: 17,078
      Repo-size          : 100 G
      Repo-baseurl       : http://scp-rhel8-ip/rhel/8/baseos-debug
      Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
      Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
      Repo-id            : rhel-8-appstream
      Repo-name          : rhel-8-appstream
      Repo-revision      : 1718903734
      Repo-updated       : Fri 21 Jun 2024 02:15:34 AM KST
      Repo-pkgs          : 38,260
      Repo-available-pkgs: 25,799
      Repo-size          : 122 G
      Repo-baseurl       : http://scp-rhel8-ip/rhel/8/appstream
      Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
      Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
      
      Repo-id            : rhel-8-baseos
      Repo-name          : rhel-8-baseos
      Repo-revision      : 1718029433
      Repo-updated       : Mon 10 Jun 2024 11:23:52 PM KST
      Repo-pkgs          : 17,487
      Repo-available-pkgs: 17,487
      Repo-size          : 32 G
      Repo-baseurl       : http://scp-rhel8-ip/rhel/8/baseos
      Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
      Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
      
      Repo-id            : rhel-8-baseos-debug
      Repo-name          : rhel-8-baseos-debug
      Repo-revision      : 1717662461
      Repo-updated       : Thu 06 Jun 2024 05:27:41 PM KST
      Repo-pkgs          : 17,078
      Repo-available-pkgs: 17,078
      Repo-size          : 100 G
      Repo-baseurl       : http://scp-rhel8-ip/rhel/8/baseos-debug
      Repo-expire        : 172,800 second(s) (last: Thu 08 Aug 2024 07:27:57 AM KST)
      Repo-filename      : /etc/yum.repos.d/scp.rhel8.repo
      Code block. Check repository list

Windows Key Management Service Configuration Guide

In Samsung Cloud Platform, when using Windows Server, you can activate genuine licensing by utilizing the Key Management Service provided by SCP. Follow the steps below.

  1. Right-click the Windows Start icon, then run cmd from Windows PowerShell (Administrator) or the Windows Run menu.

  2. In Windows PowerShell (Administrator) or cmd, please register the KMS Server by running the command below.

    Color mode
    slmgr /skms 198.19.2.23:1688
    slmgr /skms 198.19.2.23:1688
    Code block. WKMS configuration

  3. After executing the KMS Server registration command, confirm the notification popup indicating successful registration, then click OK.

    Figure
    Figure. Verify WKMS settings
  4. In Windows PowerShell (Administrator) or cmd, run the command below to activate the product.

    Color mode
    slmgr /ato
    slmgr /ato
    Code block. Windows Server activation settings

  5. After confirming the notification popup that the product activation was completed successfully, click OK.

    Figure
    Figure. Verify Windows Server activation
  6. Please run the command below in Windows PowerShell (Administrator) or cmd to verify that activation has been completed.

    Color mode
    slmgr /dlv
    slmgr /dlv
    Code block. Verify Windows Server activation

  7. After confirming the notification popup that the product activation was completed successfully, click OK.

    Figure
    Figure. Windows Server genuine activation verification

2.7 - Install ServiceWatch Agent

Users can install the ServiceWatch Agent on a Virtual Server to collect custom metrics and logs.

Reference
Collecting custom metrics/logs via the ServiceWatch Agent is currently available only on Samsung Cloud Platform For Enterprise. It will also be available in other offerings in the future.
Caution
Metric collection through the ServiceWatch Agent is classified as custom metrics and, unlike the default metrics collected from each service, incurs charges; therefore, we recommend removing or disabling unnecessary metric collection settings.

ServiceWatch Agent

The agents that must be installed on a Virtual Server to collect ServiceWatch’s custom metrics and logs can be divided into two main types. It is the Prometheus Exporter and OpenTelemetry Collector.

CategoryDetailed description
Prometheus ExporterProvide metrics of a specific application or service in a format that Prometheus can scrape
  • Depending on the OS, you can use the Node Exporter for Linux servers and the Windows Exporter for Windows servers
Open Telemetry CollectorActs as a centralized collector that gathers telemetry data such as metrics and logs from distributed systems, processes (filtering, sampling, etc.), and exports them to various backends (e.g., Prometheus, Jaeger, Elasticsearch, etc.)
  • Exports data via the ServiceWatch Gateway so that ServiceWatch can collect metric and log data.
Table. Explanation of Prometheus Exporter and Open Telemetry Collector

Pre-configuration for Using ServiceWatch Agent

To use the ServiceWatch Agent, please refer to ServiceWatch Agent를 위한 사전 환경 설정 and prepare the prerequisite configuration.

Install Prometheus Exporter for Virtual Server (for Linux)

Install the Prometheus Exporter on a Linux server according to the steps below.

Node Exporter installation

Install Node Exporter according to the steps below.

  1. Node Exporter User Creation
  2. Node Exporter configuration

Create Node Exporter User

Create a dedicated user to securely isolate the Node Exporter process.

Color mode
sudo useradd --no-create-home --shell /bin/false node_exporter
sudo useradd --no-create-home --shell /bin/false node_exporter
code block. Node Exporter user creation command

Node Exporter configuration

  1. Download to install Node Exporter. This guide refers to the version below.
    • Download path: /tmp
    • Installed version: 1.7.0
      Color mode
      cd /tmp
      wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz
      cd /tmp
      wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz
      Code block. Node Exporter download command
Reference
The latest version of Node Exporter can be found at Node Exporter > Releases > Lastest, and specific versions of Node Exporter can be found at Node Exporter > Releases.
  1. Install the downloaded Node Exporter and grant permission to the executable file.

    Color mode
    cd /tmp
    sudo tar -xvf node_exporter-1.7.0.linux-amd64.tar.gz -C /usr/local/bin --strip-components=1 node_exporter-1.7.0.linux-amd64/node_exporter
    cd /tmp
    sudo tar -xvf node_exporter-1.7.0.linux-amd64.tar.gz -C /usr/local/bin --strip-components=1 node_exporter-1.7.0.linux-amd64/node_exporter
    code block. Node Exporter installation command
    Color mode
    sudo chown node_exporter:node_exporter /usr/local/bin/node_exporter
    sudo chown node_exporter:node_exporter /usr/local/bin/node_exporter
    Code block. Node Exporter permission setting command

  2. Create service file Configure Node Exporter to collect memory metrics (meminfo) or block storage metrics (filesystem).

    Color mode
    sudo vi /etc/systemd/system/node_exporter.service
    sudo vi /etc/systemd/system/node_exporter.service
    Code block. Command to open the Node Exporter service file
    Color mode
    [Unit]
    Description=Prometheus Node Exporter (meminfo only)
    Wants=network-online.target
    After=network-online.target
    
    [Service]
    User=node_exporter
    Group=node_exporter
    Type=simple
    ExecStart=/usr/local/bin/node_exporter \
      --collector.disable-defaults \    # disable default metrics
      --collector.meminfo \             # Enable memory metrics
      --collector.filesystem            # Block Storage filesystem metrics enable
    
    Restart=on-failure
    
    [Install]
    WantedBy=multi-user.target
    [Unit]
    Description=Prometheus Node Exporter (meminfo only)
    Wants=network-online.target
    After=network-online.target
    
    [Service]
    User=node_exporter
    Group=node_exporter
    Type=simple
    ExecStart=/usr/local/bin/node_exporter \
      --collector.disable-defaults \    # disable default metrics
      --collector.meminfo \             # Enable memory metrics
      --collector.filesystem            # Block Storage filesystem metrics enable
    
    Restart=on-failure
    
    [Install]
    WantedBy=multi-user.target
    code block. Result of opening the Node Exporter service file

Reference
  • The collector can be enabled or disabled using a flag.

    • –collector.{name}: Used to enable a specific metric.
    • –no-collector.{name}: Disables a specific metric.
    • To disable all default metrics and enable only a specific collector, you can use –collector.disable-defaults –collector.{name} ….
  • Below is a description of the main collector.

CollectorExplanationLabel
meminfoProvide memory statistics-
filesystemProvides file system statistics such as used disk space
  • device: the physical or virtual device path where the filesystem is located
    • Example: /dev/sda1
  • fstype: the type of the filesystem
    • Example: ext4, xfs, nfs, tmpfs
  • mountpoint: the path where the filesystem is mounted on the host OS. The most intuitive criterion for distinguishing disks
    • Example: /, /var/lib/docker, /mnt/data
Table: Description of major Node Exporter collectors
  • Node Exporter 지표 you can check the main metrics provided by Node Exporter and the Node Exporter Collector configuration method.
Reference
  • Detailed information about the collectable metrics and how to configure them can be found in Node Exporter > Collector.
  • The metrics available may vary depending on the version of the Node Exporter you are using. * Please refer to Node Exporter.
Caution
Since metric collection through the ServiceWatch Agent is classified as custom metrics and incurs charges unlike the default metrics, unnecessary metric collection must be removed or disabled to prevent excessive fees.
  1. Service activation and start Register the Node Exporter service and verify the registered service and configured metrics.
    Color mode
    sudo systemctl daemon-reload
    sudo systemctl enable --now node_exporter
    sudo systemctl daemon-reload
    sudo systemctl enable --now node_exporter
    Code block. Node Exporter service activation and start command
    Color mode
    sudo systemctl status node_exporter
    sudo systemctl status node_exporter
    Code block. Node Exporter service check command
    Color mode
    curl http://localhost:9100/metrics | grep node_memory
    curl http://localhost:9100/metrics | grep node_memory
    Code block. Node Exporter metric information check command
information
If you have completed the Node Exporter configuration, you must install the Open Telemetry Collector provided by ServiceWatch to finish setting up the ServiceWatch Agent.
For more details, see ServiceWatch > ServiceWatch Agent 사용하기.

Install Prometheus Exporter for Virtual Server (for Windows)

Install according to the steps below to use Prometheus Exporter on a Windows server.

Install Windows Exporter

Install the Windows Exporter following the steps below.

  1. Windows Exporter 설정

Windows Exporter configuration

  1. Download the installation file to install the Windows Exporter.
    • Download path: C:\Temp
    • Test version: 0.31.3
      Color mode
      $ mkdir /Temp
      $ Invoke-WebRequest -Uri "https://github.com/prometheus-community/windows_exporter/releases/download/v0.31.3/windows_exporter-0.31.3-amd64.exe" -OutFile "C:\Temp\windows_exporter-0.31.3-amd64.exe"
      $ mkdir /Temp
      $ Invoke-WebRequest -Uri "https://github.com/prometheus-community/windows_exporter/releases/download/v0.31.3/windows_exporter-0.31.3-amd64.exe" -OutFile "C:\Temp\windows_exporter-0.31.3-amd64.exe"
      code block. Download Windows Exporter
Reference
Windows Exporter version and installation files can be found at Windows Exporter > Releases.
  1. Windows Exporter execution test
    Windows Exporter enables all collectors by default, but to collect only the metrics you want, you need to enable the following collectors. The following is an example that activates a collector specified by the user.
    • Memory metric: memory
    • Block storage metric: local_disk
    • Host name: os
      Color mode
      $ cd C:\Temp
      $ .\windows_exporter-0.31.3-amd64.exe --collectors.enabled memory,logical_disk,os
      $ cd C:\Temp
      $ .\windows_exporter-0.31.3-amd64.exe --collectors.enabled memory,logical_disk,os
      code block. Windows Exporter execution test
Reference
  • The collector can be enabled using a flag.

    • –collectors.enabled “[defaults]" Metrics provided by default
    • –collector.enabled {name},{name},{name}…: Used to enable specific metrics.
  • Below is a description of the main collector.

CollectorExplanationLabel
memoryProvide memory statistics
logical_diskCollect performance and health metrics of logical disks (e.g., C:, D: drives) on the local system.
  • volume: the physical or virtual device path where the file system is located
    • Example: C:D:
Table. Description of major Windows Exporter collectors
  • Windows Exporter 지표 you can find the main metrics provided by Windows Exporter and the method to configure the Windows Exporter Collector.
Reference
  • Detailed information about the collectable metrics and how to configure them can be found in Windows Exporter > Collector.

  • The metrics that can be provided may vary depending on the version of the Windoes Exporter you are using. * Please refer to Windows Exporter.

Caution
Since metric collection through the ServiceWatch Agent is classified as custom metrics and incurs charges unlike the default metrics, unnecessary metric collection must be removed or disabled to prevent excessive fees.
  1. Service registration and verification Register the Windows Exporter service and verify the configured metrics.

    Color mode
    $ sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --collectors.enabled memory,logical_disk,os" DisplayName= "Prometheus Windows Exporter" start= auto
    $ Start-Service windows_exporter
    $ sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --collectors.enabled memory,logical_disk,os" DisplayName= "Prometheus Windows Exporter" start= auto
    $ Start-Service windows_exporter
    code block. Windows Exporter service registration
    Color mode
    # Service check
    $ Get-Service windows_exporter
    
    # Check metrics
    $ Invoke-WebRequest -Uri "http://localhost:9182/metrics" | Select-String memory
    # Service check
    $ Get-Service windows_exporter
    
    # Check metrics
    $ Invoke-WebRequest -Uri "http://localhost:9182/metrics" | Select-String memory
    Code block. Check Windows Exporter service

  2. Configuration file settings

    • You can set it to use a YAML configuration file by using the –config.file option.
      Color mode
      $ .\windows_exporter.exe --config.file=config.yml
      $ .\windows_exporter.exe --config.file="C:\Program Files\windows_exporter\config.yml" # If you use an absolute path, you must enclose the path in quotes.
      $ .\windows_exporter.exe --config.file=config.yml
      $ .\windows_exporter.exe --config.file="C:\Program Files\windows_exporter\config.yml" # If you use an absolute path, you must enclose the path in quotes.
      code block. Windows Exporter configuration file settings
      Color mode
      collectors:
        enabled: cpu,net,service
      collector:
        service:
          include: windows_exporter
      log:
        level: warn
      collectors:
        enabled: cpu,net,service
      collector:
        service:
          include: windows_exporter
      log:
        level: warn
      Code block. Example of a part of a Windows Exporter configuration file
    • Please refer to Windows Exporter > Official Example Configuration File.
      Color mode
      ---
      #Note this is not an exhaustive list of all configuration values
      collectors:
        enabled: cpu,logical_disk,net,os,service,system
      collector:
        service:
          include: windows_exporter
        scheduled_task:
          include: /Microsoft/.+
      log:
        level: debug
      scrape:
        timeout-margin: 0.5
      telemetry:
        path: /metrics
      web:
        listen-address: :9182
      ---
      #Note this is not an exhaustive list of all configuration values
      collectors:
        enabled: cpu,logical_disk,net,os,service,system
      collector:
        service:
          include: windows_exporter
        scheduled_task:
          include: /Microsoft/.+
      log:
        level: debug
      scrape:
        timeout-margin: 0.5
      telemetry:
        path: /metrics
      web:
        listen-address: :9182
      Code block. Example of a Windows Exporter configuration file
      Refer to the following to register a service using a configuration file.
      Color mode
      $ sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --config.file=C:\Temp\config.yml" DisplayName= "Prometheus Windows Exporter" start= auto
      $ Start-Service windows_exporter
      $ sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --config.file=C:\Temp\config.yml" DisplayName= "Prometheus Windows Exporter" start= auto
      $ Start-Service windows_exporter
      code block. Service registration using Windows Exporter configuration file
Reference
When using a configuration file together with command-line options, the values specified in the command-line options take precedence. Consequently, command-line options override the configuration file settings.
notice
If you have completed the Node Exporter configuration, you must install the OpenTelemetry Collector provided by ServiceWatch to finish the ServiceWatch Agent setup.
For detailed information, refer to ServiceWatch > ServiceWatch Agent 사용하기.

#Node Exporter metrics

Below is the collector and metric information that can be viewed through Node Exporter. It can be set as a Collector, or you can enable only specific metrics.

CategoryCollectorMetricDescription
Memorymeminfonode_memory_MemTotal_bytesTotal memory
Memorymeminfonode_memory_MemAvailable_bytesAvailable memory (used to determine if memory is insufficient)
Memorymeminfonode_memory_MemFree_bytesFree memory (empty memory)
Memorymeminfonode_memory_Buffers_bytesIO buffer
Memorymeminfonode_memory_Cached_bytesPage cache
Memorymeminfonode_memory_SwapTotal_bytesTotal swap
Memorymeminfonode_memory_SwapFree_bytesRemaining swap
Filesystemfilesystemnode_filesystem_size_bytesTotal file system size
Filesystemfilesystemnode_filesystem_free_bytestotal free space
Filesystemfilesystemnode_filesystem_avail_bytesSpace actually available to the user (available space for unprivileged users)
Table. Node Exporter key metrics

Node Exporter enables most collectors by default, but you can enable or disable only the collectors you want.

  • 메모리, 파일 시스템 Collector만 사용하고 싶을 때:
    Color mode
    ./node_exporter
      --collector.meminfo
      --collector.filesystem
    ./node_exporter
      --collector.meminfo
      --collector.filesystem
    code block. Enable specific collector in Node Exporter
  • Default 설정은 모두 해제하고 메모리, 파일 시스템 Collector만 사용하고 싶을 때:
    Color mode
    ./node_exporter
      --collector.disable-defaults
      --collector.meminfo
      --collector.filesystem
    ./node_exporter
      --collector.disable-defaults
      --collector.meminfo
      --collector.filesystem
    code block. Enable specific collector of Node Exporter
    Enable file system Collector for a specific mount point
    Color mode
    ./node_exporter
      --collector.disable-defaults
      --collector.filesystem.mount-points-include="/|/data"
    ./node_exporter
      --collector.disable-defaults
      --collector.filesystem.mount-points-include="/|/data"
    code block. Enable specific collector in Node Exporter
    Enable the file system Collector, excluding specific mount points
    Color mode
    ./node_exporter
      --collector.disable-defaults
      --collector.filesystem.mount-points-exclude="/boot|/var/log"
    ./node_exporter
      --collector.disable-defaults
      --collector.filesystem.mount-points-exclude="/boot|/var/log"
    code block. Enable specific collector in Node Exporter

파일 시스템 collector를 사용하고 싶지 않을때:

Color mode
./node_exporter --no-collector.filesystem
./node_exporter --no-collector.filesystem
code block. Disable specific collector in Node Exporter

Color mode
[Unit]
Description=Node Exporter
After=network-online.target

[Service]
User=nodeexp
ExecStart=/usr/local/bin/node_exporter
  --collector.disable-defaults
  --collector.meminfo
  --collector.filesystem

[Install]
WantedBy=multi-user.target
[Unit]
Description=Node Exporter
After=network-online.target

[Service]
User=nodeexp
ExecStart=/usr/local/bin/node_exporter
  --collector.disable-defaults
  --collector.meminfo
  --collector.filesystem

[Install]
WantedBy=multi-user.target
Code block. Node Exporter > /etc/systemd/system/node_exporter.service configuration

You can configure the Open Telemetry Collector to select and collect only the necessary metrics gathered from the Node Exporter. When you want to collect only specific metrics among those provided by a particular collector of Node Exporter, ServiceWatch를 위한 Open Telemetry Collector 사전 설정

Caution
Collecting metrics through the ServiceWatch Agent is classified as custom metrics, and unlike the default metrics collected from each service, it incurs charges; therefore, we recommend configuring only the metrics that are essential.

#Windows Exporter metrics

Below is the collector and metric information that can be viewed through the Windows Exporter. You can configure it as a Collector, or enable only specific metrics.

CategoryCollectorIndicator nameExplanation
Memorymemorywindows_memory_available_bytesAvailable memory
Memorymemorywindows_memory_cache_bytesCache memory
Memorymemorywindows_memory_committed_bytesCommitted memory
Memorymemorywindows_memory_commit_limitCommit limit
Memorymemorywindows_memory_pool_paged_bytespaged pool
Memorymemorywindows_memory_pool_nonpaged_bytesnon-paged pool
Disk informationlogical_diskwindows_logical_disk_free_bytesRemaining capacity
Disk informationlogical_diskwindows_logical_disk_size_bytesTotal capacity
Disk informationlogical_diskwindows_logical_disk_read_bytes_totalNumber of bytes read
Disk informationlogical_diskwindows_logical_disk_write_bytes_totalWrite byte count
Disk informationlogical_diskwindows_logical_disk_read_seconds_totalread latency
Disk informationlogical_diskwindows_logical_disk_write_seconds_totalwrite latency
Disk informationlogical_diskwindows_logical_disk_idle_seconds_totalidle time
Table. Windows Exporter Key Metrics

Windows Exporter enables most collectors by default, but you can configure only the collectors you want.

CPU, 메모리, 논리 디스크만 사용하고 싶을 때:

Color mode
#--collector.enabled option disables the default and activates only the specified Collector
.\windows_exporter.exe --collectors.enabled="memory,logical_disk"
#--collector.enabled option disables the default and activates only the specified Collector
.\windows_exporter.exe --collectors.enabled="memory,logical_disk"
code block. Enable a specific collector for Windows Exporter
Reference
Even without disabling unused collectors, using –collector.enabled will collect only the collectors specified in that option.

Color mode
#Register windows_exporter as a service
sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --config.file=C:\Temp\config.yml" DisplayName= "Prometheus Windows Exporter" start= auto
#Service start
Start-Service windows_exporter
#Register windows_exporter as a service
sc.exe create windows_exporter binPath= "C:\Temp\windows_exporter-0.31.3-amd64.exe --config.file=C:\Temp\config.yml" DisplayName= "Prometheus Windows Exporter" start= auto
#Service start
Start-Service windows_exporter
code block. service registration
Color mode
#Note this is not an exhaustive list of all configuration values
collectors:
  enabled: logical_disk,memory
collector:
  service:
    include: windows_exporter
  scheduled_task:
    include: /Microsoft/.+
log:
  level: debug
scrape:
  timeout-margin: 0.5
telemetry:
  path: /metrics
web:
  listen-address: ":9182"
#Note this is not an exhaustive list of all configuration values
collectors:
  enabled: logical_disk,memory
collector:
  service:
    include: windows_exporter
  scheduled_task:
    include: /Microsoft/.+
log:
  level: debug
scrape:
  timeout-margin: 0.5
telemetry:
  path: /metrics
web:
  listen-address: ":9182"
Code block. Service configuration file

Through the Open Telemetry Collector configuration, you can set it to collect only the required metrics gathered from the Windows Exporter. When you want to collect only specific metrics among those provided by a particular collector of the Windows Exporter, [ServiceWatch를 위한 Open Telemetry Collector 사전 설정](/userguide/management/service_watch/how_to_guides/service_watch_agent/

Caution
Metric collection through the ServiceWatch Agent is classified as custom metrics and incurs charges, unlike the default metrics collected from each service; therefore, we recommend configuring only the metrics that are essential.

3 - API Reference

API Reference

4 - CLI Reference

CLI Reference

5 - Release Note

Virtual Server

2026.07.16
FEATURE Add server type and other feature changes
  • Even if the Backup service is connected, you can delete the server.
    • When a server is deleted, the schedule of the associated backup is removed, but the backup itself remains intact and can be restored and utilized.
  • s3 and h3 server types have been added.
    • Samsung Cloud Platform Sovereign will be offered after November 2026.

2026.05.21
CHANGED Shared Image generation size limit and AIOS integration suspension
  • Creating a shared Image is limited based on the OS disk size.
    • If the OS disk size is 500 GB or larger, you cannot create a shared Image.
  • The AIOS service integration has been stopped.
    • Since the AIOS service has been discontinued, the AIOS integrated service (LLM Endpoint) has been removed from Virtual Server.
2026.03.19
FEATURE Add standard image, add SSD_Provisioned disk type, and add ServiceWatch metric monitoring capability
  • Additional OS Image provision
    • Standard Image has been added. * (Window server 2016)
  • An SSD volume with configurable IOPS and Throughput has been added.
    • When creating Block Storage, you can select the SSD_Provisioned disk type.
    • You can set the maximum IOPS and Throughput.
  • You can view the Virtual Server ServiceWatch metric monitoring graph on the detail page.
2025.12.16
FEATURE Virtual Server feature addition
  • Additional OS Image provision
    • Standard Image has been added. * (Alma Linux 9.6, Oracle Linux 9.6, RHEL 9.6, Rocky Linux 9.6)
  • Add new Server Group policy
    • Partition(Virtual Server and Block Storage distributed placement) policy has been added.
  • You can install the Virtual Server ServiceWatch Agent to collect custom metrics and logs.
2025.10.23
FEATURE Add server name change feature and provide ServiceWatch service integration
  • You can change the server name on the Virtual Server detail page in the Samsung Cloud Platform Console.
    • When the server name is changed, the OS hostname remains unchanged, and only the information within the Samsung Cloud Platform Console is updated.
  • ServiceWatch service integration provision
    • You can monitor data through the ServiceWatch service.
2025.07.01
FEATURE Add Virtual Server feature and change Image sharing method
  • Add Virtual Server feature
    • IP, Public NAT IP, Private NAT IP configuration feature has been added.
    • An LLM Endpoint is provided for LLM usage.
    • When creating a Virtual Server, you can select an OS Image subscribed from the Marketplace.
    • The second-generation server type has been added.
      • Add a 2nd-generation (s2) server type based on the Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, see Virtual Server 서버 타입.
  • The method for sharing images between accounts has changed.
    • qcow2 Image or shared Image can be newly created and shared.
2025.02.27
FEATURE NAT configuration feature and addition of OS Image, server type
  • Add Virtual Server feature
    • The NAT configuration feature has been added to Virtual Server.
    • Additional OS Image provision
      • Standard Image has been added. * (Alma Linux 8.10, Alma Linux 9.4, Oracle Linux 8.10, Oracle Linux 9.4, RHEL 8.10, RHEL 9.4, Rocky Linux 8.10, Rocky Linux 9.4, Ubuntu 24.04)
      • An image for Kubernetes has been added. * You can create a Kubernetes Engine using an image for Kubernetes.
    • Add second-generation server type
      • Add 2nd-generation (h2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, see Virtual Server 서버 타입.
  • Samsung Cloud Platform Common Feature Change
    • Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.
2024.10.01
NEW Virtual Server service official version release
  • Virtual Server service has been officially launched.
  • We have launched a virtualized server that can be freely allocated and used as needed at the required time without having to purchase infrastructure resources individually.
2024.07.02
NEW Beta version release
  • We have launched a virtualized server that can be freely allocated and used as needed at the required time without having to purchase infrastructure resources individually.
2025.10.23
FEATURE Add server name change feature and provide ServiceWatch service integration
  • You can change the server name on the Virtual Server detail page in the Samsung Cloud Platform Console.
    • When the server name is changed, the OS hostname remains unchanged, and only the information within the Samsung Cloud Platform Console is updated.
  • ServiceWatch service integration provision
    • You can monitor data through the ServiceWatch service.
2025.07.01
FEATURE Add Virtual Server feature and change Image sharing method
  • Add Virtual Server feature
    • IP, Public NAT IP, Private NAT IP configuration feature has been added.
    • An LLM Endpoint is provided for LLM usage.
    • When creating a Virtual Server, you can select an OS Image subscribed from the Marketplace.
    • The second-generation server type has been added.
      • Add a 2nd‑generation (s2) server type based on the Intel 4th‑generation (Sapphire Rapids) Processor. * For detailed information, see Virtual Server 서버 타입.
  • The method for sharing images between accounts has changed.
    • qcow2 Image or shared Image can be newly created and shared.
2025.02.27
FEATURE NAT configuration feature and addition of OS Image, server type
  • Add Virtual Server feature
    • The NAT configuration feature has been added to Virtual Server.
    • Additional OS Image provision
      • Standard Image has been added. * (Alma Linux 8.10, Alma Linux 9.4, Oracle Linux 8.10, Oracle Linux 9.4, RHEL 8.10, RHEL 9.4, Rocky Linux 8.10, Rocky Linux 9.4, Ubuntu 24.04)
      • An image for Kubernetes has been added. * You can create a Kubernetes Engine using an image for Kubernetes.
    • Add second-generation server type
      • Add 2nd-generation (h2) server type based on Intel 4th-generation (Sapphire Rapids) Processor. * For detailed information, see Virtual Server 서버 타입.
  • Samsung Cloud Platform Common Feature Change
    • Account, IAM, and Service Home, tags, etc., have been updated to reflect common CX changes.
2024.10.01
NEW Virtual Server service official version release
  • Virtual Server service has been officially launched.
  • We have launched a virtualized server that can be freely allocated and used as needed at the required time without having to purchase infrastructure resources individually.
2024.07.02
NEW Beta version release
  • We have launched a virtualized server that can be freely allocated and used as needed at the required time without having to purchase infrastructure resources individually.