Manage instance

The following is to manage virtual machine instances.

View instance list

View, search, and manage the list of running instances and information about each instance.

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

2. Check the list of currently running instances in the Instance menu. Then, click the instance filter to see a list of instances by property.
   

   Instance list

   Category	Description
   Name	User-specified instance name / instance's unique ID
   ID	Unique ID of the instance
   State	State of the instance - Refer to Instance lifecycle.
   Type	Server type of instance - You can check detailed specifications (vCPU, Memory) by hovering the mouse cursor
   Image	Images installed on the instance
   Private IP	Virtual network IP address automatically assigned to your instance
   Public IP	Public IP address assigned and connected by the user
   AZ	Availability zone in which the instance is created
   Created	Instance creation date
   [More] icon	Provides extra functions - For more details, refer to More features.

More features

Click the [More] icon of the instance to perform extra features.

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

2. In the Instance menu, click the [More] icon.

   More features

   More Features	Description	Instance state after launch
   Start	Start instance - Converts an instance in a stopped or terminated state to Active state	Active
   Stop	Stop instance	Stopped
   Reboot	Restart instance (soft reboot)	Active
   Hard reboot	Hard reboot instance	Active
   Terminate	Shelve instance	Shelved_offloaded
   Rename instance	Launch pop-up window to edit instance name and description	-
   Change instance type	Run a pop-up window to change (resize) the type of instance - Type change is possible in Stopped state	-
   Modify security group	Launch the popup window to set the security group for the instance.	-
   Associate public IP	Launch pop-up window associate public IP to instance - Only. Project Admin can use this feature.	-
   Disassociate public IP	Launch a pop-up window to Disassociate public IP from instance - Only. Project Admin can use this feature.	-
   Change source/destination checks	Run a popup window to configure the source/destination check (allowed_address_pairs)	-
   Use SSH to connect	Run a pop-up window to provide instructions for SSH connection to the instance - Available for instances with a Linux-based OS installed	-
   Use RDP to connect	Run a pop-up window to provide instructions for RDP connection to the instance - Available for instances with Windows OS installed	-
   View system log	Run a pop-up window to check the system log saved in the instance - Data containing all records of the audited system, displaying progress such as program operation status - Not supported in instances with Windows OS installed	-
   Create image	Run a pop-up window to create the root volume of the instance as an image - Instances can be created with a backed-up image. - While instances can create images in both stopped and active states, it's recommended to create images when the instance is in a stopped state.	-
   Delete instance	Shut down the instance completely and return it.	-

View instance details

Find the instance details such as networks connected to the instance, security, volume, action log, and monitoring information.

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

2. In the Instance menu, select the instance.

3. Check the information.

   Details

   Check the details of a specific instance.

   Details tab

   Category	Description
   Instance name	Instance name
   Instance ID	Instance unique ID
   Host name	Hostname automatically generated in the form of private IP
   Availability Zone	The availability zone where the instance is stored
   Creator	The user who created the instance
   Created	Instance creation date (time elapsed from creation date)
   Type	The instance type selected when creating the instance.
   vCPU	Number of vCPUs
   Image	Image name of instance
   Memory	Memory size selected upon creation
   Key pair	Instance's key pair
   Volume	Number of volumes applied to the instance

   Network

   Check the network and IP information of the instance.

   All instances are provided by VPC. For details, please refer to VPC.

   Category	Description
   VPC	VPC name of the instance
   VPC ID	VPC ID of the instance
   Subnet	Subnet name of the instance
   Subnet ID	Subnet ID of the instance
   Public IP	Public IP of the instance
   Public DNS	Public DNS of the instance - It is automatically created when connecting to the public IP,.
   Private IP	Private IP of the instance
   Private DNS	Private DNS for the instance

   Security

   Check the security group and its policies applied to the instance.

   Category	Description
   Security group	List of configured security groups
   Detailed policy	Detailed policy of the set security group - Inbound tab: Inbound rules of the applied security group - Outbound tab: Outbound rules of the applied security group

   Volume

   Check volume details attached to the instance.

   Category	Description
   Name	Name of the volume
   ID	Unique ID of the volume
   State	Status of the volume - For detailed volume status, refer to Volume Status Value
   Mount point	Associated Mount Point
   Type	Type of the volume
   Size	Size of the volume
   Snapshot schedule	Associated Snapshot Schedule Policy
   Creation	Creation date and time of the volume
   [More]	Execute functions by item - Modify volume: Set the number of volumes to apply to an instance - Attach/Disconnect volume: Set and disconnect instances to be connected - Delete when instance is deleted: Delete volume when the instance is deleted - Create snapshot: Create a snapshot for the volume - Delete volume: Delete the created volume

   Action Log

   Check the action log to see which user executed which action command.

   Category	Item	Description
   Request id	-	Unique ID in request log
   Type	create	create instance action
   	delete	Delete instance Action
   	stop	Instance Stop Action
   	terminate	Terminate instance action
   	start	Instance launch action
   	reboot	Instance Reboot Action
   	revertResize	Action to revert instance type change
   	confirmResize	Action to confirm instance type change
   	resize	Action to change instance type
   	attach_interface	Action to attach an interface to an instance
   	detach_interface	Action to release interface to instance
   	attach_volume	Action to attach a volume to an instance
   	detach_volume	Action to disassociate a volume from an instance
   	detach_interface	Action to disassociate a volume from an instance
   	createImage	Action to create instance image
   Username	-	Account ID of the user who executed the action
   Request date and time	-	Action execution date and time

   Monitoring

   Monitoring allows you to manage resources flexibly and efficiently, and minimizes the resources required for management.
   Instance monitoring is divided into Basic monitoring and Detailed monitoring.

Delete instance

You can delete instances that are no longer in use.

caution

Deleted instance resources are completely retrieved and cannot be recovered once terminated.

• Volumes that are set to Delete when instance is deleted will be deleted along with the instance upon deletion.
• Volumes that are not set to Delete when instance is deleted will remain as detached volumes after the instance is deleted and will continue to incur charges. In this case, you must manually delete them from the volume list.

1. Go to Beyond Compute Service > Virtual Machine in the KakaoCloud Console.
2. In the Instance menu, select the [More] icon > Delete instance.
3. Enter the name of the instance to delete and click the [Delete] button.

Monitoring

Monitoring is divided into basic monitoring and detailed monitoring. For detailed monitoring, installation of a monitoring agent is required beforehand.

Basic monitoring

Check the results of basic monitoring.

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

2. In the Instance menu, select an instance.

3. Go to the instance's detail page > Monitoring tab, click the Basic monitoring tab.

   Basic monitoring data

   Item	Description
   vCPU Usage (Core)	Total vCPU usage over time
   Disk Read/Write Bytes	Disk (volume) read, write usage over time
   Network RX	Usage of Network RX over time
   Network TX	Usage of network TX over time
   Credit Usage	Number of CPU credits consumed during the measurement period (Burstable instances only)
   Credit Balance	CPU credit remaining on an instance (Burstable instances only)

Detailed monitoring

You can check detailed monitoring information after installing the Monitoring Agent in advance. The following is to install the Monitoring Agent.

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

2. In the Instance menu, select the instance to install the Monitoring Agent.

3. Click [Go to installation guide] displayed on the Monitoring tab.

4. After installing the Monitoring Agent, set each item in the Metric explorer tab of the Management > Monitoring > Explorer. For more details, see Management > Monitoring > How-to Guides > Use explorer.

5. To check the log, you can search each item in the Management > Monitoring > Explorer.

6. The monitoring dashboard is provided in a basic form. It is also possible to configure a custom dashboard to suit your monitoring purpose.

Associate public IP

Associate a public IP to a specific instance.

Permissions

Only Project Admin can associate a public IP.

1. Go to Beyond Compute Service > Virtual Machine in the KakaoCloud Console.
2. In the Instance menu, select the [More] icon > Associate public IP of the instance.
3. Check the information and click the [OK] button.

Disassociate public IP

Disassociate a connected public IP.

Permissions

Only Project Admin can disassociate a public IP.

caution

If you just disconnect without deleting resources to which the public IP is associated, the public IP will not be returned. In this case, you will be charged even if it is not used.

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

2. In the Instance menu, select the [More] icon > Disassociate public IP for the instance to disconnect from the public IP.

3. Click the checkbox to disassociate the public IP.

4. Click the [Disassociate] button.

Modify security group

You can modify a security group.

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

2. In the Instance menu, go to [More] icon > Modify security group.

3. Select the security group to apply to the instance.

   • If there are changes to multiple security groups, all policies in each security group will be also applied to the instance.

   Modify security group

4. Click the [Save] button.

Set time reference

Consistent and accurate time references are important for many server operations and processes. The images provided by KakaoCloud use time synchronization services such as Network Time Protocol (NTP), Chrony, and systemd-timesyncd, which are provided by the operating system by default. These time synchronization services allow multiple servers to operate based on the same time reference and ensure consistent time references. However, these external services can only be used when the server has internet access.
In a local network environment, you can synchronize time using KakaoCloud's NTP service. For Linux environments, you can use the Chrony client to utilize KakaoCloud's NTP service within the instance.

info

• Synchronization of KakaoCloud is provided at the IPv4 address 169.254.169.123.

RHEL-based

1. Install the Chrony package.

   sudo yum install chrony

2. Open the /etc/chrony.conf file and add the following line.

   server 169.254.169.123 prefer iburst minpoll 4 maxpoll 4

3. Restart the chronyd daemon to apply the changes.

   sudo service chronyd restart

4. Configure Chrony to start at boot with the following command.

   sudo chkconfig chronyd on

5. Verify that Chrony is using the IP 169.254.169.123 for time synchronization. Also, check that the default time source marked with ^* is set to 169.254.169.123.

   $ chronyc sources
   MS Name/IP address         Stratum Poll Reach LastRx Last sample
   ===============================================================================
   ^- 193.123.243.2                 2   6    17     9  -8932us[-8909us] +/- 4550us
   ^- ec2-13-209-84-50.ap-nort>     2   6    17     9  -8534us[-8512us] +/- 5038us
   ^* 169.254.169.123               2   4    17     9    +11us[  +34us] +/-   39ms

6. Check Chrony's time synchronization status.

   $ chronyc tracking
   Reference ID    : A9FEA97B (169.254.169.123)
   Stratum         : 3
   Ref time (UTC)  : Wed Jun 28 08:14:40 2023
   System time     : 0.000019450 seconds fast of NTP time
   Last offset     : +0.000022669 seconds
   RMS offset      : 0.000022669 seconds
   Frequency       : 1.352 ppm slow
   Residual freq   : +2.810 ppm
   Skew            : 0.061 ppm
   Root delay      : 0.076084495 seconds
   Root dispersion : 0.000831026 seconds
   Update interval : 2.0 seconds
   Leap status     : Normal

Debian-based

1. Install the Chrony package.

   sudo apt install chrony

2. Open the /etc/chrony/chrony.conf file and add the following line.

   server 169.254.169.123 prefer iburst minpoll 4 maxpoll 4

3. Restart the chronyd daemon to apply the changes.

   sudo /etc/init.d/chrony restart

4. Verify that Chrony is using the IP 169.254.169.123 for time synchronization. Check that the default time source marked with ^* is set to 169.254.169.123.

   $ chronyc sources
   MS Name/IP address         Stratum Poll Reach LastRx Last sample
   ===============================================================================
   ^* 169.254.169.123               2   4    37     4    +41us[ +189us] +/-   39ms
   ^- pugot.canonical.com           2   6    17    18  -8895us[-8864us] +/-  162ms
   ^- prod-ntp-3.ntp1.ps5.cano>     2   6    17    18  -3232us[-3203us] +/-  125ms
   ^- prod-ntp-5.ntp1.ps5.cano>     2   6    17    19  -1723us[-1707us] +/-  123ms
   ^- alphyn.canonical.com          2   6    17    18  -2344us[-2321us] +/-  140ms
   ^- 121.174.142.82                3   6    17    19  -9870us[-9853us] +/-   28ms
   ^- ntp-seoul.gombadi.com         2   6    17    20  -8532us[-8519us] +/-   52ms
   ^- send.mx.cdnetworks.com        2   6    17    18  -8997us[-8971us] +/-   29ms
   ^- 193.123.243.2                 2   6    17    19  -9014us[-8994us] +/- 4132us

5. Check Chrony's time synchronization status.

   $ chronyc tracking
   Reference ID    : A9FEA97B (169.254.169.123)
   Stratum         : 3
   Ref time (UTC)  : Wed Jun 28 08:25:52 2023
   System time     : 0.000156159 seconds slow of NTP time
   Last offset     : -0.000184961 seconds
   RMS offset      : 0.000184961 seconds
   Frequency       : 5.999 ppm fast
   Residual freq   : -0.600 ppm
   Skew            : 35.807 ppm
   Root delay      : 0.076914668 seconds
   Root dispersion : 0.000669460 seconds
   Update interval : 16.2 seconds
   Leap status     : Normal