Prerequisites for using Server
- Print
- PDF
Prerequisites for using Server
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Available in VPC
Service specifications, preparations, and pricing information for best use of Server are described.
Cloud environment specifications
The cloud environment specifications supported by Server are as follows:
| Item | Specifications |
|---|---|
| Region | Korea, Singapore, and Japan |
| Platform | VPC |
| Language | Korean, English, and Japanese |
Note
If you are curious about the VPC environment, see Service introduction of NAVER Cloud Platform portal, and if you want to know whether the VPC environment is supported for each service, see the Ncloud use 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.
- g1 server: versions developed when the service was initially provided. They are the XEN hypervisor-based servers where you can use HDD and SSD-based storage.
- g2 server: a more advanced server than the g1 when it comes to the CPU and network, thus making its performance better and more stable. They are the XEN hypervisor-based servers where you can use HDD and SSD-based storage.
- g3 server: a server based on KVM hypervisor introduced for higher performance compared to the current servers. Its compatibility in servers, storage, snapshot, and server images is classified in comparison to the g1 and g2 servers, and you can use FB1 (Fixed Block Storage) and CB1 (Common Block Storage) storages.
Note
- Resources with different hypervisors are not compatible with each other.
- Currently, g3 servers are supported only in the Korea Region.
Characteristics of KVM-based server
The characteristics of g3 servers based on KVM, different from the g1 and g2 servers based on XEN, are as follows:
- G3 servers exclude the storage information from the server spec code. (excluding storage information, such as B50, B100, and so on)
- g3 server name excludes disk information. <example> 2 vCPUs, 4 GB memory
- As for g3 servers, the storage information is excluded from the existing OS SW code.
The performance QoS for each specification of g3 servers based on KVM is as follows:
Note
The maximum possible performance values are displayed for the network, storage IOPS, and storage throughput.
| Standard | High Memory | High CPU | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS | CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS | CPU (vCore) | Memory (GB) | Network (Gbps) | Throughput (MB/s) | IOPS |
| 2 | 8 | 1 | 81 | 4,725 | 2 | 16 | 1 | 81 | 4,725 | 2 | 4 | 1 | 81 | 5,250 |
| 4 | 16 | 1 | 144 | 7,875 | 4 | 32 | 2 | 144 | 7,875 | 4 | 8 | 1 | 144 | 7,875 |
| 8 | 32 | 2 | 288 | 15,000 | 8 | 64 | 2 | 288 | 15,000 | 8 | 16 | 1 | 288 | 15,000 |
| 16 | 64 | 2 | 594 | 25,000 | 16 | 128 | 5 | 594 | 25,000 | 16 | 32 | 2 | 594 | 25,000 |
| 32 | 128 | 5 | 850 | 40,000 | 32 | 256 | 10 | 850 | 40,000 | 32 | 64 | 2 | 850 | 40,000 |
| 48 | 192 | 5 | 1,188 | 70,000 | 48 | 384 | 10 | 1,188 | 70,000 | 48 | 96 | 2 | 1,188 | 70,000 |
| 64 | 256 | 10 | 1,188 | 100,000 | - | - | - | - | - | 64 | 128 | 5 | 1,188 | 100,000 |
Server spec code
Server spec code is a code developed for viewing the specifications of a server at a glance. When creating servers or checking the information of created server, you can find it.
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 the Bare Metal server) |
| Server generation |
|
| CPU type |
|
| Storage type/capacity | Default storage information limited to g1 and g2
|
Note
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: 2 vCPUs, 8 GB memory |
| High Memory | 1:8 | m4: 4 vCPUs, 32 GB memory |
| High CPU | 1:2 | c16: 16 vCPUs, 32 GB memory |
Server types provided
The server types provided by NAVER Cloud Platform are as follows:
Note
Currently, g3 servers are supported only in the Korea Region.
| Type | Supported regions | Characteristics | Recommended use cases |
|---|---|---|---|
| Standard (g3, g2) | Korea, Singapore, and Japan | Balanced memory-to-vCPU allocation ratio to provide services suitable for a wide variety of workloads in order to provide highly versatile performance | A general web service or database server |
| High Memory (g3, g2) | Korea, Singapore, and Japan | Provides services suitable for memory-intensive works such as large data processing | High performance database server |
| High CPU (g3, g2) | Korea, Singapore, and Japan | Increased the ratio of vCPU to memory to provide services suitable for computing-intensive workloads | Scientific modeling |
| Micro (g3) | Korea |
| Trial server |
| CPU Intensive (g2) | Korea | Equipped with a high-performance CPU, optimized for tasks that require a lot of computation |
|
| GPU (g1) | Korea, Singapore, and Japan |
|
|
| 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-g3 | O | O | O | X | X |
| Standard-g3, g2 | O | O | O | O | O | |
| High Memory-g3, g2 | O | O | O | O | O | |
| High CPU-g3, g2 | O | O | O | O | O | |
| CPU Intensive-g2 | O | O | O | O | O | |
| GPU | O | O | O | X | X | |
| Bare Metal Server | X | X | O | X | O | |
Note
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, CB1 |
| 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. See the limit in the server creation limit by server type | If the limit needs to be increased, contact Customer support |
| Maximum number of public IPs per server | 1 per server | If the limit needs to be increased, contact Customer support |
| Maximum number of ACGs per VPC | 500 | If the limit needs to be increased, contact Customer support |
| Maximum number of ACGs per server | 3 | If the limit needs to be increased, contact Customer support |
| Maximum number of rules per ACG | 50 | If the limit needs to be increased, contact Customer support |
| Maximum number of network interfaces | 3 (However, 1 for Micro-g3) | Can't increase limit |
| Available days to stop server | Up to 90 days per stop and 180 cumulative days in a 12-month period | The limit can't be increased (while the server is stopped, only the basic disk fee to install the operating system will be incurred) |
Server creation limit by server type
The server creation limit differs according to the country and member type (individual, corporate) selected upon signing up. If you want to change the limit, request it through Customer support > Contact us.
Note
If you need more servers than the server creation limit, contact Customer support to increase the limit.
Server image specifications
For 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 according to purpose of use and usage. The storage specifications by type are as follows:
| Item | FB1 (Fixed Block Storage) | CB1 (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 according to the size) |
| IOPS Burst | - | 3000 (applied when the basic performance is equal to or less than 3000) |
| Throughput | 4-500 Mb/s (it may vary according to the size) | 100-250 Mb/s (it may vary according to the size) |
| Throughput burst | 25-500 Mb/s (it may vary according to the size) | - |
Note
- 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, and fees are charged for additional storages regardless of the storage type.
- As for the CB1 storage's IOPS, 1000 IOPS is provided between 10 GB and 2000 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 storage is provided as 100 Mb/s up to 150 GB, and after that, it increases by 1 Mb/s per 1 GB. Up to 250 Mb/s is provided.
- The specifications of FB1 and CB1 storages cannot be changed.
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) |
Note
- 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.
- SSD block storage provides 4000 IOPS between 10 GB and 100 GB and additional 40 IOPS per 1 GB after that. 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 shown below.
- 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)
Note
ACGs directly created by users have no rules for outbound traffic, so all outgoing connections are blocked.
Usage fees
Server is serviced on a pay-as-you-go pricing plan. For more details about the pricing for Server, see the following pages.
Was this article helpful?