Create server

Prev Next

Available in VPC

You can create a server from the NAVER Cloud Platform console.

Note
  • To ensure service continuity without interruption in the event of unexpected server failures or scheduled changes, it is recommended to configure servers with inter-zone redundancy by default. To configure redundancy, see Load Balancer overview.
  • NAVER Cloud Platform provides a High Availability (HA) structure to prepare for failures in the physical server, such as memory, CPU, and power supply. HA is a policy for preventing hardware failures from expanding into the virtual machine (VM) server. It supports live migration, which automatically migrates the VM on the host server to another secure host server when a failure occurs in the aforementioned host server. However, the VM server is rebooted when an error occurs where Live Migration cannot be initiated. If the service is operated on a single VM server, a VM restart may cause a service disruption. To reduce the frequency of failures, it is recommended to configure VM server redundancy as described above.

The console interface for creating servers has been updated following the introduction of the third-generation servers. Currently, both the new console interface revamped for user convenience and the previous console interface are provided. First, select the console interface you want to use.
You can create g3 servers only using the new console interface, whereas you can create the g1 and g2 servers using both interfaces.

Note

The existing console interface is scheduled to be discontinued, and only the new console interface will be available.

Create server with the new console interface

To create a server with the new console interface:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to i_menu > Services > Compute > Server.
  2. Click [Create server].
  3. In the console selection popup, select New console interface, and then click [Create server].
  • You can set the currently selected console interface to be used continuously, preventing any further popup from being displayed. Continue using the currently selected server creation console next time. Select it by marking the checkbox.
  1. Follow the next steps:
Note

To create a server, a VPC and a Subnet must be created first. If you don't have a VPC and a Subnet created, see the following guides to create them first, and then create a server:

1. Select server image

Select the server image to use.

  1. Select the tab in which the server image will be displayed.
  • [Latest server image]: Displays the latest version of server images by OS.
  • [NCP server image]: Displays all server images provided by NAVER Cloud Platform.
  • [My server image]: Displays server images that you have created or that have been shared with you.
  • [3rd party image]: Displays server images created by vendor, not by NCP.
  1. Select the OS and hypervisor type.
  • You can also search by entering a server image keyword.
  1. From the server image list, click [Next] to the right of the server image you want.
  • Depending on the selected server type, consent to provide third-party information may be required. If applicable, agree to the terms of service.
Note

For more information about the server image, see Various server images.

2. Configure server settings

Specify the server configuration information.

  1. Select the VPC and Subnet you want to deploy a server to.
  • To communicate with an external private network, you must deploy the server to a Public Subnet so that it can be assigned a public IP.
  • If you need to create a new VPC or Subnet, click [Create VPC] or [Create Subnet] and proceed with the operation on the page.
  1. Select the server specifications.
  • Select the server type first. The available server types may vary depending on the previously configured server image.
  • High-CPU: Suitable for computing-intensive workloads (e.g., scientific modeling).
  • Standard: Suitable for general web and database.
  • High-Memory: Suitable for high performance database.
  • GPU: Suitable for parallel operations, such as big data analysis and processing, scientific computing, and machine learning.
  • CPU-Intensive: Suitable for machine and deep learning that require a lot of computation or a high-performance web server.
  • Select the specification code that matches your desired detailed specifications.
  • For more information about specification codes, see Server specification code.
  1. Select the pricing plan.
  • If your monthly usage time is high, select the monthly pricing plan; if your usage time is low, select the hourly pricing plan.
Note

If you are likely to change the server specifications in the future, use the hourly pricing plan. Changing server specifications may result in duplicate charges. If you change specifications while using the monthly pricing plan, charges are calculated on a daily basis, which could potentially result in higher charges compared to using the hourly pricing plan.

  1. Enter the number of servers and server names.
  • You can create up to 10 servers.
  • If you create multiple servers, you must enter a starting number. You can only enter numbers in the starting number, and "001" is the default value.
  • The server name must be 3-30 characters long and begin with a letter. They must contain lowercase letters, numbers, and/or hyphens. If you do not enter a server name, the name is automatically created.
  • Select The hostname is set with the entered server name. to apply the host name set on the server OS identical to the server name.
  1. Enter the network interfaces to assign to the server.
  • You must register the eth0 IP, and it becomes the server's default private IP.
  • Enter the desired IP, and then click [Add]. The IP must be within the selected Subnet range.
  • Leaving the IP field blank and clicking the [Add] automatically allocates it.
  • Apart from the default eth0, you can create 2 additional network interfaces. This requires having other private subnets within the same zone. The entered value becomes the additional private IP for the server.
Note

To network interfaces, see the following usage tips related:

  • You can utilize network interfaces to distinguish multiple servers intuitively based on their purpose of use.
    Example: Distinguish 10.1.1.1x as the development server and 10.1.1.2x as the production server.
  • Create multiple network interfaces in the following cases.
  • When you need different Subnets based on the characteristics of applications to be used on servers.
  • When you designed Subnets separated by purpose but need to integrate them into one server for use.
  1. Select whether to assign a public IP.
  • To select the option, you must create 1 server within the public subnet. If you create multiple servers, you can allocate a public IP individually after creation is complete.
  1. To create a placement group of the server, click to select Physical placement group.
  • A placement group is a method of deploying clusters (physical equipment) to run VMs, allowing you to create a new placement group or add to an existing group.
  • Currently, only Anti-Affinity (Dispersed placement) type is supported. It's a method of running VMs from different clusters to increase availability by dispersing the impact in case of physical failures.
  1. Select the server return protection status.
  • Return protection helps prevent the accidental return of servers. Enable the return protection for servers undertaking essential roles.
  1. If necessary, enter a note or select an automatic execution script.
  • Selecting an automatic execution script runs a script automatically after server creation is complete and allows you to configure the initial environment of the server. You must create scripts in the Init Script menu beforehand to select the option.
  1. If you have completed all settings, click [Next].

3. Set storage

For KVM-based 3rd-generation servers, you can configure the storage size and add storage. After configuring the server block storage, click [Next].

  • The storage size can be set from 10 GB to 20 TB based on Linux.
  • To add a new row to the storage list, click [Add storage]. Enter the storage information in the added row.
  • Storage name: Must be 3-30 characters long and begin with a letter. They must contain letters, numbers, hyphens, and/or underscores.
  • Snapshot name: Select the snapshot to use if you want to apply a snapshot.
  • Size: Enter a number between 10 and 16380.
  • Storage volume type: Select from CB1/2 or FB1/2.
  • You can create up to 20 additional storages.
  • If the default storage is encrypted, you can use only encrypted additional storage. Likewise, if the default storage is not encrypted, you can use only non-encrypted additional storage.
Note

If you need to change the storage volume type when creating a XEN-based server, click [Previous] and reselect the server spec code in the server settings step.

4. Configure authentication key

Select an authentication key you have or create a new one and click [Next].

  • To create a new authentication key, select Create new authentication key, enter the authentication key name, and click [Create and save authentication key].
Note

Authentication keys are necessary to get the administrator password for server access. Keep the saved PEM file in a safe location on your PC.

5. Configure network access

Select an ACG that you have or create a new one and click [Next].

  • You can select up to 3 ACGs.
  • default-acg is the ACG provided by default.
  • The setting is available only when creating a new network interface; if you use the existing network interfaces, the preset ACG is applied automatically.
Note

You can edit rules within ACGs in the ACG menu. For more information, see Set ACG.

6. Review final settings

Check the details, and then click [Create server].

Note

It may take several minutes or longer for the server to be created. Once the server creation is completed and the server starts running, Running is displayed on the server list.

Create server with the existing console interface

To create a server with the existing console interface:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to i_menu > Services > Compute > Server.
  2. Click [Create server].
  3. In the Select console popup, select Existing console interface, and then click [Create server].
  • You can set the currently selected console interface to be used continuously, preventing any further popup from being displayed. Continue using the currently selected server creation console next time. Select it by marking the checkbox.
  1. Follow the next steps:
Note

To create a server, a VPC and a Subnet must be created first. If you don't have a VPC and a Subnet created, see the following guides to create them first, and then create a server:

1. Select server image

Select the server image to use.

  1. Select the boot disk size, image type, OS image type, and server type.
  • Boot disk size: Select 50 GB for a Linux server, and 100 GB for a Windows server.
  • Image type: Select the image type according to the purpose of use.
  • Application: The server provided with specific applications.
  • DBMS: The server for the database.
  • OS: The server where only the operation system is applied.
  • Application/DBMS/OS image type: Select detailed options depending on the image type selected earlier.
  • Server type: Select the server specifications according to the purpose of use.
  • High CPU: Suitable for computing-intensive workloads (e.g., scientific modeling).
  • Standard: Suitable for general web and database.
  • High-Memory: Suitable for high performance database.
  • GPU: Suitable for parallel operations, such as big data analysis and processing, scientific computing, and machine learning.
  • CPU Intensive: Suitable for machine and deep learning that require a lot of computation or a high-performance web server.
  1. From the server image list, click [Next] to the right of the server image you want.
  • Depending on the selected server type, consent to provide third-party information may be required. If applicable, agree to the terms of service.
Note

For more information about the server image, see Various server images.

2. Configure server settings

Specify the server configuration information.

  1. Select the VPC and Subnet you want to deploy a server to.
  • To communicate with an external private network, you must deploy the server to a Public Subnet so that it can be assigned a public IP.
  • If you need to create a new VPC or Subnet, click [Create VPC] or [Create Subnet] and proceed with the operation on the page.
  1. Select a storage volume type.
  • SSD: Select for services requiring high-performance I/O.
  • HDD: Select for general services.
  1. Select the server type.
  • Select the appropriate number of CPUs and memory capacity for your purpose of use.
  1. To encrypt storage, click to select Apply storage encryption.
  • Select this option when security regulations for the server exist or when you need strong security.
  • The option is available only in some operating systems, and you can only add encrypted storage when this feature is enabled.
  1. Select the pricing plan.
  • If your monthly usage time is high, select the monthly pricing plan; if your usage time is low, select the hourly pricing plan.
Note

If you are likely to change the server specifications in the future, use the hourly pricing plan. Changing server specifications may result in duplicate charges. If you change specifications while using the monthly pricing plan, charges are calculated on a daily basis, which could potentially result in higher charges compared to using the hourly pricing plan.

  1. Enter the number of servers and server names.
  • You can create up to 10 servers.
  • If you create multiple servers, you must enter a starting number. You can only enter numbers in the starting number, and "001" is the default value.
  • The server name must be 3-30 characters long and begin with a letter. They must contain lowercase letters, numbers, and/or hyphens. If you do not enter a server name, the name is automatically created.
  • Select The hostname is set with the entered server name. to apply the host name set on the server OS identical to the server name.
  1. Enter the network interfaces to assign to the server.
  • You must register the eth0 IP, and it becomes the server's default private IP.
  • Enter the desired IP, and then click [Add]. The IP must be within the selected Subnet range.
  • Leaving the IP field blank and clicking the [Add] automatically allocates it.
  • Apart from the default eth0, you can create 2 additional network interfaces. This requires having other private subnets within the same zone. The entered value becomes the additional private IP for the server.
Note

To network interfaces, see the following usage tips related:

  • You can utilize network interfaces to distinguish multiple servers intuitively based on their purpose of use.
    Example: Distinguish 10.1.1.1x as the development server and 10.1.1.2x as the production server.
  • Create multiple network interfaces in the following cases.
  • When you need different Subnets based on the characteristics of applications to be used on servers.
  • When you designed Subnets separated by purpose but need to integrate them into one server for use.
  1. Select whether to assign a public IP.
  • To select the option, you must create 1 server within the public subnet. If you create multiple servers, you can allocate a public IP individually after creation is complete.
  1. To create a placement group of the server, click to select Physical placement group.
  • A placement group is a method of deploying clusters (physical equipment) to run VMs, allowing you to create a new placement group or add to an existing group.
  • Currently, only Anti-Affinity (Dispersed placement) type is supported. It's a method of running VMs from different clusters to increase availability by dispersing the impact in case of physical failures.
  1. Select the server return protection status.
  • Return protection helps prevent the accidental return of servers. Enable the return protection for servers undertaking essential roles.
  1. If necessary, enter a note or select an automatic execution script.
  • Selecting an automatic execution script runs a script automatically after server creation is complete and allows you to configure the initial environment of the server. You must create scripts in the Init Script menu beforehand to select the option.
  1. If you have completed all settings, click [Next].

3. Configure authentication key

Select an authentication key you have or create a new one and click [Next].

  • To create a new authentication key, select Create new authentication key, enter the authentication key name, and click [Create and save authentication key].
Note

Authentication keys are necessary to get the administrator password for server access. Keep the saved PEM file in a safe location on your PC.

4. Configure network access

Select an ACG that you have or create a new one and click [Next].

  • You can select up to 3 ACGs.
  • default-acg is the ACG provided by default.
  • The setting is available only when creating a new network interface; if you use the existing network interfaces, the preset ACG is applied automatically.
Note

You can edit rules within ACGs in the ACG menu. For more information, see Set ACG.

5. Review final settings

Check the details, and then click [Create server].

Note

It may take several minutes or longer for the server to be created. Once the server creation is completed and the server starts running, Running is displayed on the server list.