The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.
Available in VPC
Review supported environments, service limits, and pricing information before using Server.
Cloud specifications
Server supports the following cloud environment specifications:
| Item | Specifications |
|---|---|
| Region | Korea, Singapore, and Japan |
| Platform | VPC |
| Language | Korean, English, and Japanese |
For more information about the VPC environment, see VPC overview on the NAVER Cloud Platform portal. To verify VPC support for specific services, see Ncloud user environment guide.
Server specifications
Check the server type and image provided by NAVER Cloud Platform before creating a server.
NAVER Cloud Platform provides servers from g1 to g3.
- 1st generation (g1) server: The original version developed at the initial launch of the service. They are the XEN hypervisor-based servers where you can use HDD and SSD-based storage.
- 2nd generation (g2) server: An improved version with enhanced CPU and network performance and greater stability compared to 1st generation servers. They are the XEN hypervisor-based servers where you can use HDD and SSD-based storage.
- 3rd generation (g3) server: KVM hypervisor-based servers introduced for improved performance over previous generations. Unlike g1/g2 servers, g3 servers have distinct compatibility for servers, storage, snapshots, and server images. Available storage types include FB1/2 (Fixed Block Storage) and CB1/2 (Common Block Storage).
- Resources with different hypervisors are not compatible with each other.
- Currently, g3 servers are supported only in the Korea, Singapore, and Japan Regions.
Overview by hypervisor
Hypervisor is a concept added to categorize the compatibility of resources (services) provided by NAVER Cloud Platform. NAVER Cloud Platform provides XEN and KVM hypervisors, and the following resources (services) are classified by hypervisor compatibility:
| Hypervisor | Server generation | Server type | Server image (OS) | Storage type | Snapshot | My server image |
|---|---|---|---|---|---|---|
| XEN | g1, g2 | Mirco, Standard, High-Memory, High-CPU, CPU-Intensive, GPU |
XEN-based server image | HDD, SSD | XEN-based snapshot | XEN-based My server image |
| KVM | g3 | Mirco, Standard, High-Memory, High-CPU, CPU-Intensive, GPU, SFC |
KVM-based server image | FB1, FB2 CB1, CB2 |
KVM-based snapshot | KVM-based My server image |
- Server
- Storage (Block Storage)
- Snapshot
- My server image (Server Image)
Resources (services) with different hypervisors are not compatible with each other.
For example, you cannot create a server based on KVM from My server image created with a server based on XEN.
Characteristics of KVM-based server
Unlike XEN-based g1 and g2 servers, KVM-based g3 servers have the following characteristics:
- g3 server spec codes do not include storage information (e.g., B50, B100).
- g3 server names exclude disk information. Example: 2 vCPUs, 4 GB memory.
- As for g3 servers, the storage information is excluded from the existing OS SW code.
The following is the performance QoS by specification for KVM-based g3 servers:
The maximum possible performance values are displayed for the network, storage IOPS, and storage throughput.
Standard
| CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
|---|---|---|---|---|
| 2 | 8 | 1 | 81 | 4,725 |
| 4 | 16 | 1 | 144 | 7,875 |
| 8 | 32 | 2 | 288 | 15,0000 |
| 16 | 64 | 2 | 594 | 25,0000 |
| 32 | 128 | 5 | 850 | 40,0000 |
| 48 | 192 | 5 | 1,188 | 70,0000 |
| 64 | 256 | 10 | 1,188 | 100,0000 |
High Memory
| CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
|---|---|---|---|---|
| 2 | 16 | 1 | 81 | 4,725 |
| 4 | 32 | 2 | 144 | 7,875 |
| 8 | 64 | 5 | 288 | 15,0000 |
| 16 | 128 | 5 | 594 | 25,0000 |
| 32 | 256 | 10 | 850 | 40,0000 |
| 48 | 384 | 10 | 1,188 | 70,0000 |
| - | - | - | - | - |
High CPU/CPU Intensive
| CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
|---|---|---|---|---|
| 2 | 4 | 1 | 81 | 5,250 |
| 4 | 8 | 1 | 144 | 7,875 |
| 8 | 16 | 1 | 288 | 15,0000 |
| 16 | 32 | 2 | 594 | 25,0000 |
| 32 | 64 | 2 | 850 | 40,0000 |
| 48 | 96 | 2 | 1,188 | 70,0000 |
| 64 | 128 | 5 | 1,188 | 100,0000 |
GPU - L4
| GPU (EA) | GPU Memory(GB) | CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
|---|---|---|---|---|---|---|
| 1 | 24 | 4 | 48 | 2 | 144 | 7,875 |
| 1 | 24 | 8 | 48 | 2 | 288 | 15,000 |
| 2 | 48 | 8 | 96 | 2 | 288 | 15,0000 |
| 2 | 48 | 16 | 96 | 2 | 594 | 25,0000 |
| 4 | 96 | 16 | 192 | 5 | 594 | 25,0000 |
| 4 | 96 | 32 | 192 | 5 | 850 | 40,0000 |
GPU - L40S
| GPU (EA) | GPU Memory(GB) | CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
|---|---|---|---|---|---|---|
| 1 | 48 | 16 | 96 | 2 | 594 | 25,000 |
| 1 | 48 | 32 | 96 | 2 | 850 | 40,000 |
| 2 | 96 | 32 | 192 | 5 | 850 | 40,0000 |
| 2 | 96 | 64 | 192 | 5 | 1,188 | 100,0000 |
| 4 | 192 | 64 | 384 | 10 | 1,188 | 100,0000 |
| 4 | 192 | 128 | 384 | 10 | 1,188 | 100,0000 |
Server spec code
Server spec code is a code developed for viewing the specifications of a server at a glance. You can find it when creating servers or checking the information of a created server.
The indication rules of the code are as follows:
| mi | 1 | - | g3 | a | (-h50) |
|---|---|---|---|---|---|
| Server type | Number of vCPUs | - | Server generation | CPU type | Storage type/capacity |
| Item | Description |
|---|---|
| Server type |
|
| Number of vCPUs | Number of CPU cores (number of Hyperthread on criteria for Bare Metal Server) |
| Server generation |
|
| CPU type |
|
| Storage type/capacity | Default storage information for g1/g2 servers only
|
The number of vCPUs and the memory ratio are fixed in accordance with the server type, so you can know the server specifications.
| Server type | vCPU (no.): memory (GB) ratio | Examples |
|---|---|---|
| Standard | 1:4 | s2: Example: 2 vCPUs, 8 GB memory |
| High Memory | 1:8 | m4: 4 vCPUs, 32 GB memory |
| High CPU, CPU Intensive | 1:2 | c16 or ci16: 16 vCPUs, 32 GB memory |
Server types provided
The server types provided by NAVER Cloud Platform are as follows:
Currently, g3 servers are supported only in the Korea, Singapore, and Japan Regions.
| Type | Supported Regions | Characteristics | Recommended use cases |
|---|---|---|---|
| Standard | Korea, Singapore, and Japan | Provides balanced memory-to-vCPU ratio allocation for versatile performance across various workloads. | A general web service or database server. |
| High Memory | Korea, Singapore, and Japan | Provides services suitable for memory-intensive works such as large data processing. | High performance database server. |
| High CPU | Korea, Singapore, and Japan | Provides a higher vCPU-to-memory ratio for compute-intensive workloads. | Scientific modeling. |
| Micro | Korea |
|
Trial server. |
| CPU Intensive | Korea | Equipped with a high-performance CPU, optimized for tasks that require a lot of computation. |
|
| GPU | Korea, Singapore, and Japan | Servers equipped with GPUs, suitable for parallel processing like big data analysis and machine learning. |
|
| Bare Metal Server (general). | Korea, Singapore, and Japan | Provides high-performance physical server that can be independently used in a cloud format. |
|
| Bare Metal Server (A100) | Korea | Provides high-performance physical server that can be independently used and specialized for AI, data analysis, and HPC in a cloud format. |
|
Available services per server type
The services available for each server type are as follows:
| Server type | Add storage | Change storage size | Use SSD storage | Use Auto Scaling | Use Network Interface | |
|---|---|---|---|---|---|---|
| Server | Micro, GPU | O | O | O | X | X |
| Standard, High Memory, High CPU, CPU Intensive | O | O | O | O | O | |
| Bare Metal Server | X | X | O | X | O | |
SSD storage provided in Bare Metal Servers refers not to Block Storage SSD but to Local SSD Storage.
Storage available by server type
The storages available for each server type are as follows:
| Server | Storage | |
|---|---|---|
| Server | Standard-g3 | FB1, FB2, CB1, CB2 |
| High Memory-g3 | ||
| High CPU-g3 | ||
| Micro-g3 | ||
| Standard-g2 | HDD, SSD | |
| High Memory-g2 | ||
| High CPU-g2 | ||
| CPU Intensive-g2 | ||
| GPU | ||
| Bare Metal Server | - | |
Server-related resource limits
Server-related resources can be used within the following limits:
| Resource | Default value | Description |
|---|---|---|
| Number of servers | It differs depending on the server type. For more information, see Server creation limit by server type. | If the limit needs to be increased, see FAQs and contact Customer Support. |
| Maximum number of public IPs per server | 1 per server. | Cannot increase limit. |
| Maximum number of ACGs per VPC | 500 | Cannot increase limit. |
| Maximum number of ACGs per server | 3 | Cannot increase limit. |
| Maximum number of rules per ACG | 50 | Cannot increase limit. |
| Maximum number of network interfaces | 3 (However, 1 for Micro-g3) | Cannot increase limit. |
| Available days to stop server | Up to 90 days per 1 stop and 180 cumulative days in a 12-month period. | The limit cannot be increased. (While the server is stopped, only the basic disk fee to install the operating system is charged.) |
Server creation limit by server type
The server creation limit differs according to the country and member type (individual or corporate) selected upon signing up. If you want to change the limit, please contact Customer Support > Contact Support.
If you need more servers than the server creation limits, check the FAQs and contact Customer support to increase the limit.
Server image specifications
For more information on server images provided by NAVER Cloud Platform, see Various server images.
Storage specifications
Additional Block Storage specifications are as follows:
KVM-based storage
The types of available storages in KVM-based g3 servers are classified depending on the purpose of use and usage. The storage specifications by type are as follows:
| Item | FB1, FB2 (Fixed Block Storage) | CB1, CB2 (Common Block Storage) |
|---|---|---|
| Description |
|
|
| Media type | HDD | SSD |
| Minimum size | 100 GB | 10 GB |
| Maximum size | 16 TB | 16 TB (for default storage, maximum size of 2 TB). |
| Maximum number of additional storages | 20 | 20 |
| IOPS | 500 (fixed) | 100-16,000 (it may vary depending on the size) |
| IOPS Burst | - | 3,000 (applied when the basic performance is equal to or less than 3,000) |
| Throughput | 4-500 MB/s (it may vary depending on the size) | 100-250 MB/s (it may vary depending on the size) |
| Throughput burst | 25-500 MB/s (it may vary depending on the size) | - |
- The maximum number of additional storages does not include the default storage. 1 default storage is provided when you create a server, and you can add 20 additional storages.
- In the case of Micro server, no fee is charged up to 10 GB for the default storage CB1/2, and fees are charged for additional storages regardless of the storage type.
- As for the CB1/2 storage's IOPS, 100 IOPS is provided between 10 GB and 30 GB if you change the storage size. Afterwards, it increases by 3 IOPS per 1 GB. Up to 16,000 IOPS (4 KiB I/O) is provided.
- The throughput of CB1/2 storage is provided as 100 MB/s up to 150 GB. Afterwards, it increases by 1 MB/s per 1 GB. Up to 250 MB/s is provided.
- Specification changes between FB1/2 and CB1/2 storage types are not possible.
XEN-based storage
The available storage specifications in the XEN-based g1 and g2 servers are as follows:
| Item | HDD | SSD |
|---|---|---|
| Minimum size | 10 GB | 10 GB |
| Maximum size | 2 TB | 2 TB |
| Maximum number of additional storages | 15 (it may differ depending on the operating system) | 15 (it may differ depending on the operating system) |
- The maximum number of additional storages does not include the default storage. 1 default storage is provided when you create a server, and you can add 15 additional storages.
- When it comes to SSD block storage, 4,000 IOPS is provided between 10 GB to 100 GB. Afterward, it increases by 40 IOPS per 1 GB. Up to 20,000 IOPS (4 KiB I/O) is provided.
ACG specifications
Each account of NAVER Cloud Platform has a default ACG created. The ACG provided by default follows the basic rules as follows:
ACG specifications
Each account of NAVER Cloud Platform has a default ACG created. The ACG provided by default follows the basic rules as follows:
- Block all inbound traffic.
- Allow all outbound traffic (specified as rule).
- Allow bidirectional network communication between servers in Default ACG (added as rule, can be deleted).
:::
Pricing information
Servers are offered on a pay-as-you-go pricing plan. For more information on Server's pricing, see the following pages: