Skip to main content

Create and connect instance

info

This guide contains information about GPU and NPU instances.
Video transcoding instance is provided in Virtual Machine. For more details, refer to Virtual Machine > Create and connect instance.

Create instance​

Instances are virtualized hardware resources that configure servers of different instance types. Here's how to create an instance in GPU:

  1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.

  2. In the Instance menu, click the [Create instance] button.

  3. Enter the required information and click the [Create] button.

    • Network connection after creating an instance can take up to 10 minutes.

    image. Create instance Create instance

    ItemDescription
    ① Basic informationName: Instance name
    Count: Number of instances to create.
    - You can create 1 to 10 instances simultaneously.
    - Instances can be created up to the maximum quota allowed per project. :   
       ㄴ kr-central-2: 500 instances.
    ️
    ️ ⚠️ Quotas are shared between Virtual Machine instances and GPU instances.
    Description (Optional): Description of the instance
    ② ImageAn image to use.
    - Basic tab: Official images provided by KakaoCloud.
    - My image tab: Images created within your account. Refer to Create and manage image for details.
    ③ Instance typeSelect the conditions for the instance.
    - Refer to KakaoCloud Portal for detailed pricing information.
    ④ VolumeVolume connected to the instance. Root volume is displayed by default, and additionally custom volumes can be added if needed.
    - Size: Can be created from 1 to 5,120GB.
    - Type: Currently only SSD is supported, with various types planned for the future.
    - Maximum IOPS: Pre-set IOPS information is displayed for each volume size, with a future feature of providing editing capabilities.
    - Delete when instance is deleted: If selected, the volume will be deleted along with the instance.
    ⑤ Key pairA key pair to apply to the instance
    - Click Create key pair to generate and assign a new one. For details, refer to Create key pair For details.

    ⚠️ The private key file of the created key pair cannot be downloaded again, so make sure to securely store this information.
    ⑥ NetworkVPC: Network for the instance
    Subnet: A subnet created within the network.
    - If a new VPC and subnet are needed, they must be created in KakaoCloud Console > VPC.
    - Public IPs can be allocated after instance creation in Associate public IP.
    Security group: Security group to apply to the instance
    Inbound/Outbound rules
    - Inbound tab: Inbound policies, which must include the following inbound ports based on the OS image selected in the security group:
       ㄴ For instance connectivity, the following inbound ports must be allowed:
       ㄴ Linux-based: TCP port 22
       ㄴ Windows: TCP port 3389
       ㄴ Windows + MSSQL: TCP ports 3389, 1433
    - Outbound tab: Outbound policies allowing all protocols and ports.
    ⑦ Advanced settingsUser script: Enter or execute a user script.
    - Upon instance startup, execute user data to automatically configure the initial environment.
    - User scripts and cloud-init commands can be entered within 16KB or uploaded as a file.
    - The entered commands are copied and executed under /var/lib/cloud/instances upon initial instance startup.
    - To check script execution logs, use the following commands:
       ㄴ Ubuntu: sudo cat /var/log/syslog or sudo journalctl -u cloud-final.service
       ㄴ CentOS: sudo cat /var/log/messages or sudo journalctl -u cloud-final.service.

    ⚠️ Entering or executing an incorrect user script or an incomplete script may result in OS boot failure.
caution
  • If the created instance type is a Bare Metal Server with NVLink configuration (e.g., p2a.baremetal), you need to install Fabric Manager separately to utilize GPU features properly. Therefore, please install Fabric Manager as follows. For more details, refer to NVIDIA Fabric Manager Official Documentation > 2.6 Installation.
    • Ubuntu-based Linux: sudo apt-get install cuda-drivers-fabricmanager-[driver-branch]
    • RHEL-based Linux: sudo dnf module install nvidia-driver:[driver-branch]/fm
info
  • Volumes for which the Delete when instance is deleted option is not selected will remain as detached volumes and be charged for even if the instance is deleted. In that case, delete the instance directly from the volume list.
  • Instances created starting January 16, 2023 will automatically have their hostname set to a private IP. (e.g. host-100-100-17-22).
  • After an instance is created, it is updated in host-IP format at the networking stage, and hostname may be displayed as the instance name for a while after instance creation.

Connect instance​

Metadata is required to connect to an instance. If there is no default security group of the instance, define an outbound rules for metadata acquisition in the Custom security group. For more details, refer to Custom security group.

Connect to Linux instance​

Linux instances are connected using the SSH command. Check the related explanation by clicking GPU > Instance menu > [More] icon > Use SSH to connect. Set up the security group according to the OS image and prepare the connection with public/private IP.

OSPrerequisites
Linux/macOSInstall SSH client and use ssh command in the terminal.
Step 1. Prepare SSH client​

Install an SSH client in advance to use the SSH command. Below is the preparation requirements for installing an SSH client by operating system:

OSPrerequisites
Linux/macOSInstall an SSH client and use the ssh command in the terminal
WindowsInstall OpenSSH client to use the ssh command in the command prompt (cmd) or install a separate SSH client such as PuTTY
Step 2. Connect via SSH​

Use the SSH command to connect to the instance. Enter the path and file name of your private key (.pem), the username, and the address of the instance.

SSH command
ssh -i {PATH_TO_PRIVATE_KEY} {USERNAME}@{INSTANCE_IP}
CommandDescription
PATH_TO_PRIVATE_KEYPath to the private SSH key
USERNAMEUsername for connecting to the instance
INSTANCE_IPThe IP address of the instance
- Enter either a public or private IP according to the connection environment

Connect to Windows instance​

After the RDP connection, set up a Remote Desktop Connection to connect to the Windows instance. It is necessary to set up the security group according to the OS image, and prepare the connection so that it can be accessed via a public/private IP.

OSPrerequisites
WindowsInstall OpenSSH client to use ssh command in the Command Prompt (cmd) or install a separate SSH client like PuTTY.
Step 1. Connect via RDP​

Proceed with the RDP connection for an instance with Windows OS installed.

info
  • Setting the initial password to connect to an instance may take approximately 20 minutes after requesting instance creation.
  • Access is only possible with the password obtained through the initial key pair file. If the password is changed, manually do so through the operating system (OS).
  • KakaoCloud Console only provides the initially obtained password, and any subsequently changed passwords will not be provided.
  • There are restrictions on using WSL (Windows Subsystem For Linux) in Windows instances. For Linux, please use a Linux instance.

  1. Go to Beyond Compute Service > GPU in the KakaoCloud Console.

  2. In the Instance menu, select Use RDP to connect from the [More] icon of the instance.

    • The username automatically generated upon instance creation is Administrator.

  3. Click the [Upload key pair] button to upload the key pair (.pem) file associated with the instance to obtain the password.

    • The selected private key is not transmitted to the server.
Step 2. Connect via remote desktop​

To connect to the Windows instance, set up a remote PC (desktop) with the IP address and port number.

  1. Click on Start > Settings > System > Remote Desktop, or enter [Remote Desktop Connection](Microsoft Remote Desktop) in the search bar to launch Remote Desktop.

  2. Enter the public or private IP suitable for the instance's connection and click the [Connect] button.

    • If the instance is configured to use a different port number, add the port number after the IP address. (e.g. 10.0.0.0:1234)

  3. In Enter your credentials, enter the user name and password, click the [OK] button, and then access the respective Windows instance.

caution

If there are instances with the same hostname within the same network (VPC), some network functions may experience errors. Please be careful when changing the instance name or directly changing the host name.

Last updated on