Create and connect instance

Create instance

An instance is a virtualized hardware resource used to configure servers with various instance types. Here's how to create an instance in the Virtual Machine service:

1. Go to the KakaoCloud Console > Beyond Compute Service > Virtual Machine menu.

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

3. In the Create instance screen, enter the required information and click [Create]. Network access configuration may take up to 10 minutes, during which the server may be temporarily inaccessible.

   

   Item	Description
   ① Basic info	Name: Name of the instance - Duplicate names allowed within the same project - When creating multiple instances, names are auto-filled based on the first instance
   ② Image	Image to use - Default tab: Official images provided by Kakao Enterprise - My images tab: Custom images created by the user (see Manage image)
   ③ Instance type	Conditions for the instance - See Instance type specifications
   ④ Volume	Volume attached to the instance. The root volume is shown by default, and up to 9 additional volumes can be added. - Size: 1–5,120 GB - Type: SSD only - Max IOPS: Predefined by volume size (modification to be supported) Delete with instance: Option to delete the volume when the instance is deleted ⚠️ If not selected, the volume remains and incurs charges. To avoid charges, delete it from the volume list.
   ⑤ Key pair	Key pair to apply to the instance - Click [Create key pair] to create and assign one (see Manage key pair) ⚠️ Private key files cannot be downloaded again. Store them securely. ⚠️ You cannot connect to the instance without a key pair.
   ⑥ Network	VPC: The network for the instance Subnet: Choose a subnet within the network - If needed, create a new VPC and subnet via KakaoCloud Console > VPC - Public IPs can be assigned after creation via Associate public IP Network interface: The primary network interface for the instance - Type: Choose new or existing - IP assignment: If new, auto-assigns an available IP from the subnet CIDR Security group: Security group to apply Inbound/Outbound rules - Inbound: Apply required ports based on image: ㄴ Linux: TCP 22 ㄴ Windows: TCP 3389 ㄴ Windows + MSSQL: TCP 3389, 1433 - Outbound: Allow all protocols and ports by default
   ⑦ Advanced settings	User script: A script that runs during first boot to configure the environment automatically - Provide a cloud-init script (max 16 KB) or upload a file - Stored in /var/lib/cloud/instances - View logs with: ㄴ 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 ⚠️ Incorrect or incomplete scripts may cause boot failure. CPU multithreading: Optimize performance by limiting to one thread per core - Disable for workloads like HPC

info

• From January 16, 2023, hostnames are auto-assigned using the primary network interface's private IP (e.g., host-100-100-17-22).
• After instance creation, the hostname updates to the host-IP format during the networking phase.

Connect to instance

To connect to an instance, metadata must be accessible. If the instance's security group does not include the "default security group," you must define outbound rules for metadata retrieval in a custom group. For details, see Custom security group.

Connect to Linux instance

Connect to Linux instances using SSH. You can also find this via Virtual Machine > Instance > [More] > SSH connect. Ensure security groups allow access and that a public or private IP is assigned.

OS	Security group rule	Allowed port
Linux	Inbound	TCP 22 (default)

SSH connection

Step 1. Prepare SSH client

Install an SSH client in advance. Requirements vary by OS:

OS	Requirements
Linux/macOS	Use terminal after installing SSH client
Windows	Install OpenSSH client (via cmd) or use PuTTY

Step 2. Connect via SSH

Connect using the SSH command with the private key, username, and instance IP:

SSH connection command

ssh -i {PATH_TO_PRIVATE_KEY} {USERNAME}@{INSTANCE_IP}

Item	Description
{PATH_TO_PRIVATE_KEY}	Path to your SSH private key file
{USERNAME}	Default username depending on image
{INSTANCE_IP}	Public or private IP assigned to the instance

Connect to Windows instance

To connect to a Windows instance, install the Windows App and allow TCP/3389 in the security group from the source IP of your PC.

Step 1. Prepare RDP client

Install the Windows App. On macOS, download it from the App Store.

Step 2. Connect via RDP

1. Go to the KakaoCloud Console > Beyond Compute Service > Virtual Machine.

2. In the Instance menu, click [More] > RDP connect and check the required information:

   Item	Description
   Public IP	Assign a public IP to connect from outside. Assign it via [More] > Associate public IP.
   Username	Fixed as administrator
   Password	Click [Register key pair], upload the private key file to retrieve the password

3. Launch the Windows App. Go to Devices, click the [+] icon, and select Add PC. Enter the information and keep default settings:

   Item	Description
   PC name	The instance's public IP
   Credentials	Click Add Credentials, then enter the username and password from step 2

4. Under Devices > Saved PCs, double-click your saved instance to connect.

info

• It may take a few minutes after instance creation for the initial password to be ready.
• You can only log in using the initial password from the key pair file. If changed, it must be updated within the OS.
• The console only provides the initial password. Changed passwords are not retrievable.
• Windows instances support WSL 1.

caution

If multiple instances with the same hostname exist in a VPC, some network functions may not work properly. Avoid duplicate hostnames when creating or renaming instances.