User Guide - cloudlink.co.kr · 64-bit CoreOS 681.2.0 64-bit CentOS 7.2 64-bit Debian 8.0.4 64-bit FreeBSD 10.1 64-bit Gentoo 13 64-bit OpenSUSE 13.1 64-bit SUSE Linux 64-bit Ubuntu

Elastic Compute Service

User Guide

-

-

User Guide Quick reference This article provides a quick reference for you on the use of ECS on the ECS Management Console. Must read: ECS usage instructions

A must-read for using ECS

Log on to an instance

How to log on to a Linux instance? How to log on to a Windows instance? If you forget your instance logon password (not the Management Terminal password), youcan reset the password.

Operate disks

How to attach a data disk after you purchase a cloud disk?

Change the operating system You can change the operating system, such as:

From Windows to Linux, or from Linux to Windows. From one version to another, for example, from Windows Server 2008 to Windows Server2012.

Elastic Compute Service User Guide

1

-

-

-

-

-

-

●

Change the image, for example, change to custom images, or shared images.

Use images and snapshots

How to copy images across different regions? How to define automatic snapshot policies when you want an automatic update policy forconfigurations or applications?

Enable Intranet communication

How to use security groups to enable intranet communication?

For the answers to the above questions, click the corresponding node in the left navigation bar. ECS Operation Instruction In order to ensure that your ECS instances run correctly, you must thoroughly read the followingconsiderations before use. General considerations Prohibitions

ECS instances should not be used for flow-through services. The punishment for violatorscan be instance shutdown, lockout and even termination of services.Do not upgrade the ECS kernel or operating system (OS) without prior authorization.Do not activate SELinux.Do not uninstall PVDriver.Do not arbitrarily modify the network adapter’s MAC address.

Suggestions

For an ECS with memory larger than 4GB, it is recommended to use a 64-bit OS because amaximum of 4GB memory addressing is supported on a 32-bit OS. For example:

64-bit Aliyun Linux 15.1


2

●

●

●

●

●

●

●

●

●

●

-

-

-

-

-

-

-

-

-

-

-

-

64-bit CoreOS 681.2.064-bit CentOS 7.264-bit Debian 8.0.464-bit FreeBSD 10.164-bit Gentoo 1364-bit OpenSUSE 13.164-bit SUSE Linux64-bit Ubuntu 14.0464-bit Windows 200864-bit Windows 2012

A 32-bit Windows OS supports CPUs of up to 4 cores. In order to ensure service continuity and avoid service unavailability due to downtimemigration, it is recommended to enable service applications to be started when the OS starts.For I/O-optimized instances, do not stop the aliyun-service process.

Restrictions

Virtual application installation and subsequent virtualization (for example, using VMware) arenot supported.ECS does not support sound card applications or connection of external hardware devices(for example, hardware dongles, USB drives, external hard disks, USB keys of banks).ECS does not support SNAT and other IP packet address translation services. You can do thisusing your own VPN or proxies.ECS does not support multicast protocol. If you need to use multicasting services, it isrecommended to use unicast point-to-point method.Currently, SLS (Simple Log Service) only supports 32-bit Linux ECS in the Project regions, thatis, East China 1 (Hangzhou) and North China 1 (Qingdao).

Considerations for Windows

Do not close the built-in shutdownmon.exe process. Otherwise, it may take more time torestart your Windows server.For normal use of the server, do not rename, delete or disable administrator accounts.The use of virtual memory is not recommended.A password modified on the console applies to the administrator account. If theadministrator account has been deleted or renamed, clicking the Change Password buttonwill automatically create an administrator account.If the computer name is changed, the following key values must be updated in the registryas well. Otherwise, the change will fail and as a result, some third-party applications cannotbe installed. The following key values must be modified in the registry: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\ComputerName\ActiveComputerN


3

-

-

-

-

-

-

-

-

-

-

-

-

ame HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName

Considerations for Linux

Do not modify the content of the default /etc/issue file. Modifying this file will make buttonson the management console unusable.Do not modify directory permissions in partitions, especially the permissions for directoriessuch as /etc, /sbin, /bin, /boot, /dev, /usr, and /lib. Improper modification of permissionsmay cause errors.Do not rename, delete or disable Linux root account.Do not compile the Linux kernel, or perform any other operations on the Linux kernel.Attach a data disk before use because a data disk is not partitioned or formatted.The use of swap for partitioning is not recommended.Do not enable the NetWorkManager service for it conflicts with the internal network serviceof the system and thus causes network errors.

Considerations for Pay-As-You-Go payment service

You cannot switch between the Subscription service and the Pay-As-You-Go service. An ECSserver can use one and only one payment service.A record-filing service is not provided.5-day unconditional refund is not supported.Modifying configuration for the Pay-As-You-Go service is not supported (includingbandwidth upgrade, CPU/memory upgrade and adding data disk). If you select a fixed0Mbps bandwidth, you will not be allocated an external IP address and cannot upgrade thebandwidth.Total fee per hour = CPU fee ＋ memory fee ＋ data disk fee ＋ public bandwidth fee. CPU,memory, data disk and fixed bandwidth are all charged per hour.

Use Management Terminal The Management Terminal is a convenient tool to log on to an ECS instance (either Linux orWindows), especially when other remote connection tools (such as Putty, Xshell and SecureCRT) arenot able to do so. For skilled users, it is a handy self-service tool to solve problems. Scenarios


4

No matter whether you have purchased bandwidth or not, you can log on to an ECS instance throughthe Management Terminal. The Management Terminal is also applicable to, but not limited to, thefollowing scenarios:

Check the progress when the ECS instance boot speed is slow (for example, self-check isinitiated). Reconfigure the firewall since remote connection (such as Putty) fails due to a software setuperror in the ECS instance (for example, firewall was enabled by misoperation). Log on to the ECS instance and end abnormal processes when applications consume highCPU usage or bandwidth, preventing remote connection (for example, full occupation of theCPU/bandwidth caused by botnet attacks).

Procedure

Log on to the ECS Management Console. Go to the ECS instance to be connected. Click More > Connect to Management Terminal on the right.

When you log on to the ECS Management Console for the first time, the system promptsthe Management Terminal password, which appears only once. You need to enter thispassword each time you log on to the Management Terminal. Remember to write down the


5

password. If you forget the password, or prefer to use a password you are familiar with, click Changethe Password of the Management Terminal on the upper right corner.

Click Send Remote Command on the upper left corner, and then click Connect toManagement Terminal. Enter the Management Terminal password to connect to the ECSinstance.

For a Linux instance, enter the user name and password to log in. If you continue to see ablack screen, this is because the Linux instance is in sleep mode. Click the mouse or pressany key to wake it up. For Linux, you can use CTRL+ALT+F1 to F10 to switch between terminals.


6

For a Windows instance, on the Management Terminal interface, send the remotecommand CTRL+ALT+DELETE. The logon interface for Windows is displayed. Enter the username and password to log on.

Change password

Log on to the ECS Management Console. Go to the ECS instance to be connected. Click More > Connect to Management Terminal on the right.


7

When you log on to the ECS Management Console for the first time, the system promptsthe Management Terminal password, which appears only once. You will need to enter thispassword each time you attempt to log on to the Management Terminal. Remember towrite down the password. If you forget your password, or prefer to use a password you are familiar with, click ChangeVNC Password on the upper right corner to change the password.

Enter your password of up to 6 characters. Uppercase and lowercase letters and numbersare supported, while special characters are not. You must restart the instance through the Management Console for the password to takeeffect. Restarting within the instance doesn’t work.

FAQ

Is the Management Terminal exclusive? Yes. When one user is using it, others cannot use it anymore. Why cannot I log on through the Management Terminal after changing the password? You must restart the instance on the Management Console (not within the instance) for thepassword to take effect. I see a black screen after logon. What should I do? A black screen indicates that the instance is in sleep mode.


8

-

-

For a Linux instance, press any key to wake it up.For a Windows instance, send the remote command CTRL+ALT+DEL to bring backthe logon interface.

I cannot access the Management Terminal. What should I do? You can solve it as follows: log on to the Management Console using Chrome, press F12 toopen the developer tool, and then check the information in the Console for analysis. I am using IE8.0 or Firefox, why cannot I open the Management Terminal? Only IE10 or higher are supported. Some versions of Firefox are not supported. To solve this problem, download the latest IE version or use Chrome instead. Chromesupports the Management Console better.

Instances Create an instance You can create an instance that runs Linux, or Windows. Also, you can create an instance from acustom image. Create a new Windows instance For the procedure of creating an instance running Windows, see Quickstart for Windows. Create a new Linux instance For the procedure of creating an instance running Linux, see Quickstart for Linux. Create an instance from a custom image If you already have instances that you want to replicate the operating system, installed applications,and data in new instances, you can create new instances from custom images. It is an effective way toscale up your system to meet your growing needs. For the procedure of creating an instance from a custom image, see Create an instance from acustom image.


9

Create a custom image from an instance You can create a custom image from an instance by choosing and packing disks, including the systemdisk and data disk, into the image. During this process, snapshots are created automatically for alldisks of the instance, and these snapshots compose the new image. To create a custom image from snapshots, see Create a custom image from snapshots. Note: To avoid data breach, make sure that you have cleared all the confidential information beforecreating a custom image. To create a custom image, follow these steps:

Log on to the ECS Console。 Click Instances on the left navigation bar. On the top of the instance list, click your target region. Locate your target instance, and then click More > Create a custom image from the menuon the right。 Enter the name and description for the image. Click Create.

The custom image is only ready after all the snapshots are created successfully. Log on to a Linux instance Your local OS decides the utilities used for remote logon to ECS instances. The table below shows theutilities for remote logon to instances.

Local OS Instance OS

Logon Method

Management Terminal Putty

SSHCommandLine

SSH ControlLight

LinuxLinux

√

Windows √ √


10

-

-

1.

2.

-

-

-

3.

Log on from Windows After an ECS instance is created, you can log on to it through either of the following methods:

Remote logon Software (for instance Putty): Before using this method, ensure that theinstance can be accessed from the Internet. However, if you did not purchase bandwidthwhen creating an instance, this remote desktop connection method does not work. You canuse the Management Terminal instead.Management Terminal: No matter whether you have purchased bandwidth or not, you canlog on to an instance through the Management Terminal of the Management Console.

Use a remote connection application The usage of different remote connection utilities is similar. This document uses Putty as an exampleto describe how to log on to an instance remotely. Putty is free and easy to use. You can download itat http://www.putty.org/.

Start Putty.exe.Enter the public IP address of the instance in Host Name (or IP address).

Use the default port 22.Select SSH in Connection Type.Type a session name in Saved Sessions, and then click Save. Thus, you can directlyload the session without entering the IP address next time.

Click Open to connect.

Mac √ √

iPhone √

Android √


11

4.

5.

In the first connection, the following message will be displayed. Click Yes.

Enter your user name and password for the Linux ECS instance as prompted. The passwordwill not be displayed on the screen. Then press Enter.


12

-

-

-

1.

2.

3.

Now, you are successfully connected to the instance and can work on it. Use the Management Terminal The Management Terminal is a convenient tool that you can use to log on to the instance when otherremote connections tools (such as Putty, Xshell, and SecureCRT) are not able to. For skilled users, it isa handy self-service tool to solve problems. Scenarios No matter whether you have purchased bandwidth or not, you can log on to an instance through the Management Terminal. The Management Terminal is also applicable to, but not limited to, thefollowing scenarios:

You want to check the progress when the instance boot speed is slow (for example, self-check is initiated).You need to reconfigure the firewall since remote connection (such as Putty) fails due to asoftware setup error in the instance (for example, firewall enabled by misoperation).You have to log on to the instance and end abnormal processes when applications consumehigh CPU usage or bandwidth, preventing remote connection (for example, full occupationof the CPU/bandwidth by processes due to a botnet attack).

Procedure

Log on to the ECS Management Console.Go to the instance to be connected.Click More > Connect to Management Terminal on the right.


13

4.

5.

At your first logon, the Management Terminal password will be prompted. The promptappears only once. You need to enter this password each time you attempt to log on to theManagement Terminal. Remember to write down the password. If you forget the password, click Change VNC Password in the upper right corner.

Click Send Remote Command in the upper left corner, and then click Connect toManagement Terminal. Enter the Management Terminal password to connect to theinstance.


14

6. Enter the user name and password to log on. If you continue to see a black screen, this isbecause the Linux instance is in sleep mode. Click the mouse or press any key to wake it up.

Log on from Linux or Mac OS X Directly connect to the instance using SSH commands, for example: ssh root@Instance’s public IPaddress. Then, enter the password of the root user. Log on from a mobile app You can log on from a remote desktop application installed on your smart phone. For example,iPhone users can download SSH Control Light from the App Store and use it to log on to Linuxinstances. What if I forget my logon password? If you forget your instance logon password (not the Management Terminal password), reset thelogon password. For details, refer to Reset the password. Log on to a Windows instance Your local OS decides the utilities used for remote logon to ECS instances. The table below shows theutilities for remote logon to instances.

Local OS Instance OS Manageme MSTSC rdesktop MSTSC APP


15

-

-

Log on from Windows This section describes how to log on to a Windows instance from a local Windows OS. After an ECS instance is created, you can log on to the server through either of the followingmethods:

Microsoft Terminal Services Client (MSTSC): Before using this method, ensure that theinstance can be accessed from the Internet. However, if you did not purchase bandwidthwhen creating the instance, this remote desktop connection method does not work.Management Terminal: Either purchased bandwidth or not, you can log on to an instancethrough the Management Terminal.

Use MSTSC

Choose Start > Remote Desktop Connection, or choose Start > Search and enter mstsc. Youcan also press the shortcut key Win+R to open the Run window, enter mstsc, and thenpress Enter to start remote desktop connection. In the Remote Desktop Connection dialog box, enter the public IP address of the instance.Click Show Options.

nt Terminal

Linux Windows √

Windows Windows √ √

Mac Windows √ √

iPhone Windows √

Android Windows √


16

Enter the user name. The default value is Administrator. Click Allow me to save credentials.In this way, you do not need to manually enter the password again when you log on later.

To make it easy to copy local files to the instance, you can enable the sharing of localcomputer resources through MSTSC. Click the Local Resources tab. Usually, the Clipboard check box needs to be selected. However, after the Clipboard option is selected, only localtext messages can be copied directly to the instance, and files cannot be copied. To copy files, click More and select Drives to choose the disks for storing files.


17


18

-

In the Display tab, you can resize the remote desktop window, which is usually set to FullScreen.

Click Connect.

Now, you are successfully connected to the instance and can work on it. Use the Management Terminal The Management Terminal is a convenient tool that you can use to log on to the instance when otherremote connections tools (such as Putty, Xshell, and SecureCRT) are not able to. For users withadequate technical skills, it is a handy self-service tool to solve problems. Scenarios Either having purchased bandwidth or not, you can log on to an instance through the ManagementTerminal. The Management Terminal is also applicable to, but not limited to, the following scenarios:

You want to check the progress when the instance boot speed is slow (for example, self-check is initiated).


19

-

-

You need to reconfigure the firewall since remote connection (such as Putty) fails due to asoftware setup error in the instance (for example, firewall enabled by misoperation).You have to log on to the instance and end abnormal processes when applications consumehigh CPU usage or bandwidth, preventing remote connection (for example, full occupationof the CPU/bandwidth by processes due to a botnet attack).

Procedure:

Log on to the ECS Management Console. Go to the instance to be connected. Click More > Connect to Management Terminal on the right.

At your first logon, the Management Terminal password will be prompted. The promptappears only once. You will need to enter this password each time you attempt to log on tothe Management Terminal. Remember to write down the password. If you forget the password, click Change VNC Password in the upper right corner.


20

Click Send Remote Command in the upper left corner, and then click Connect toManagement Terminal. Enter the Management Terminal password to connect to theinstance.

On the Management Terminal interface, send the remote command CTRL+ALT+DELETE.The logon interface for Windows server instance is displayed. Enter the user name andpassword to log on.


21

Log on from Linux You can use a remote connection utility for remote logon. If you did not purchase bandwidth, youneed to log on to the management console before connecting the instance. Use a remote connection application When you need to log on to a Windows instance remotely from a Linux system, you must use acompatible remote desktop connection utility. We recommend you use rdesktop. Start rdesktop and enter the following command (replace the parameter values in the example withyour own data):

Arguments:

```rdesktop -u administrator -p password -f -g 1024*720 192.168.1.1 -r clipboard:PRIMARYCLIPBOARD -rdisk:sunray=/home/yz16184```


22

-

-

-

-

-

-

-

-

-

-u is the user name. For a Windows instance, the default user name is administrator.-p is the Windows instance logon password.-f indicates full screen is the default view. Use the key combination Ctrl+Alt+Enter to switchout of full screen mode.-g is the resolution. If the connector “*” is omitted, the default resolution is full screen.Replace 192.168.1.1 with the IP address of your Windows instance.-d is the domain name, e.g. for INC domains, the parameter would be ‘-d inc’.-r is the multimedia redirect. For example, to enable sound, use -r sound, to use the localsound card, use -r sound : local, to enable a Udisk, use -r disk:usb=/mnt/usbdevice.-r clipboard:PRIMARYCLIPBOARD: This parameter can be used to directly copy and paste textbetween the local Linux system and the remote Windows instance. Chinese characters arealso supported.-r disk:sunray=/home/yz16184: This indicates that a directory on the local Linux system ismapped onto the Windows hard disk. This allows you to transfer files without relying onSamba or FTP.

Use the Management Terminal The operation procedure is the same as that from a local Windows OS. Log on from Mac OS X Download and install the remote desktop connection utility for Mac OS X at http://www.microsoft.com/zh-cn/download/details.aspx?spm=5176.2020520101.0.0.QyZT2p&id=18140. Log on from a mobile app You can log on from a remote desktop app installed on your smart phone. For example, iPhone userscan download Microsoft Remote Desktop from the App Store and use it to log on to Windowsinstances. What if I forget my logon password? If you forget your instance logon password (not the Management Terminal password), see Reset thepassword. Change the operating systemOn the management console, you can change the operating system, for example, changing Ubuntu


23

-

-

1.

2.

3.

4.

5.

6.

7.

8.

9.

to CentOS. You can also reinstall the operating system. Changing the operating system is achieved by changing the system disk of the instance. For details,see Change the system disk. Note: Hong Kong, Singapore, and US regions do not support changing between Linux and Windows.A Linux or Windows can be only replaced by a different version of the same operating system type. Reset the instance password If you did not set a password when creating an instance or forget the password, you can reset theinstance password.

For Windows instances, the default user name is Administrator.For Linux instances, the default user name is root.

The procedure is as follows:

Log on to the ECS Management Console.Click Instances in the left-side navigation bar.Select a region at the top of the page.Select the desired instance.You can select multiple instances, as long as they are all in thesame status.Click Reset Password.In the pop-up box, enter the new password and click Submit.Obtain and enter the verification code sent to your phone. Click OK.Select the instance with the changed password and then click Restart. Note that the newpassword will only take effect after the instance is restarted on the console, not within theinstance.In the pop-up box, click OK to restart the instance.

Restart an instance On the console, you can restart an instance as if on a real server. Restarting an instance on the Management Console is different from restarting within an instance. Insome scenarios, you need to restart an instance on the Management Console, not within the instance.For example, if you have changed the password of the Management Terminal, you must restart theinstance on the Management Console for the change to take effect. In this case, restarting within theinstance does not work. Note:


24

-

-

1.

2.

3.

4.

5.

6.

1.

2.

3.

4.

5.

-

-

●

●

●

●

The restart operation can only be performed on instances in the running status.Be cautious when restarting, because the restart operation will stop the work of yourinstance and interrupt your business.


Log on to the ECS Management Console.Click Instances in the left-side navigation bar.Select a region at the top of the page.Select the desired instance. You can select multiple instances, as long as they are all in thesame status.Click Restart.In the pop-up box, click Restart and then click OK.

Start, view, or stop an instance This article describes how to start, view, and stop an instance. Start an instance On the console, you can start an instance just like a real server.

Log on to the ECS Management Console.Click Instances in the left-side navigation bar.Select a region at the top of the page.Select the desired instance. You can select multiple instances, as long as they are all in thesame status.Click Start.

View instances You can use the console to view all your instances. You can see the following information:

The quantity and running statuses of instances in each regionFor specific instances:

Basic, configuration, payment, and monitoring informationDisksSnapshotsTheir security groups

Use the following process to view instances:


25

1.

2.

3.

4.

5.

-

-

1.

2.

3.

4.

5.

6.

7.

Log on to the ECS Management Console.On the overview page, you can view the running statuses of ECS instances in all regions.If you want to view details for a specific instance, click Instance in the left navigation bar,click the region at the top of the page, and then click the name of the Instance you wish toview.You can view the instance details, including, its region, zone, configuration specification,and payment status. In addition, you can monitor its CPU and network usage on the rightside of the page.In the left navigation bar, you can also view and manage the instance’s disks, snapshots,and security group information.

Stop an instance On the console, you can stop an instance as if on a real server. Note:

The stop operation can only be performed on instances in the running status.Please caution that the stop operation will stop your instance and interrupt your business.


Log on to the ECS Management Console.Click Instances in the left-side navigation bar.Select a region at the top of the page.Select the desired instance. You can select multiple instances, but they must all be in thesame status.Click Stop.In the pop-up box, click Stop and then click OK.Obtain and enter the verification code sent to your phone. Click OK.

Release an instance and disable auto release(for Pay-As-You-Go instances) Note: This article only applies to Pay-As-You-Go instances. Release an instance If you no longer need a Pay-As-You-Go instance, you must release it. Otherwise, even if you stop it,Alibaba Cloud still charges you until you release the instance.


26

-

-

1.

2.

3.

4.

5.

6.

7.

8.

1.

2.

3.

4.

5.

6.

7.

1.

2.

3.

There are two ways to do this:

Release Now: immediately releases the Pay-As-You-Go instance.Timed Release: Arranges a release plan for your Pay-As-You-Go instances by selectingrelease times in the future. These times are precise to the hour. You can reset the setting tooverwrite the previous one. Note that instances are released every hour on the hour and onthe half hour, but the system will stop billing according to your specified release time.


Log on to the ECS Management Console.Click Instances in the left-side navigation bar.Select a region at the top of the page.Select an instance and then click Release Setting at the bottom of the instance table.In the pop-up window, select the release type: Release Now or Timed Release.If you select Timed Release, you need to specify if it is to be auto released and the releasedate and time.Click Next and then click OK.Enter the verification code sent to your phone and then click OK.

Disable auto release If you no longer want the system to automatically release your Pay-As-You-Go instances, you candisable the set auto release function. The procedure is as follows:

Log on to the ECS Management Console.Click Instances in the left-side navigation bar.Select a region at the top of the page.Select an instance and click More on the right side. Then, select Release Setting.In the pop-up window, select the release type Timed Release.Turn off the Auto-release Setting option.Click Next and then click OK.

Add an instance to a security group On the console, you can add an instance to a security group. A single ECS instance can join amaximum of 5 security groups.

Log on to the ECS Management Console.Click Instances in the left-side navigation bar.Select a region at the top of the page.


27

4.

5.

6.

7.

1.

2.

3.

4.

5.

6.

7.

1.

2.

3.

Select the desired instance and click the instance name or the corresponding Manage button on the right side to go to the instance details page.Click The Security Groups.Click Add Security Group. In the pop-up box, select the appropriate security group.Click OK.

After adding the instance to a security group, the security group rules will automatically be applied tothe instance. It does not need to be updated. Remove an instance from a security group Based on business needs, you may remove instances from security groups. Note that an instancemust be in at least 1 security group.

Log on to the ECS Management Console.Click Instances in the left-side navigation bar.Select a region at the top of the page.Select the desired instance and click the instance name or the corresponding Manage button on the right side to go to the instance details page.Click The Security Groups. Here, you will see the list of security groups to which the instancebelongs.Select the security group to remove from and click the Remove link on the right side.In the pop-up box, click OK.

Disks Create a cloud disk You can purchase cloud disks, also known as data disks, from the Management Console. Each useraccount can buy up to 250 cloud disks. Up to 4 data disks can be attached to a single ECS instance,with the maximum capacity of 2TB per data disk. To buy a cloud disk:

Log on to the ECS Management Console.Click Instances in the left navigation bar.Select a region at the top of the page. Then, click Create Instance in the top-right corner ofthe page.


28

4.

5.

6.

-

-

-

-

1.

2.

3.

4.

5.

6.

Click Cloud Disk.Select a region and zone. Note: A cloud disk can be attached to a server in the same zoneof the same region only. Cloud disks cannot be attached across regions.Select the cloud disk type, size and quantity. Then, click Confirm Order on the right side ofthe page.

Next step for Linux For Linux instances, cloud disks must be attached, partitioned and formatted before they can bedisplayed and used in the system.

For details about attaching a data disk, see Attach a data disk.For details about formatting partitions and attaching new partitions for an attached datadisk, see Format and attach a data disk.

Next step for Windows For Windows instances, you must attach and format a cloud disk before using it.

For details about attaching a data disk, see Attach a data disk.For details about formatting an attached data disk, see Format a data disk.

Create a cloud disk from a snapshot Sometimes you may need to access the data from a snapshot, but you do not want to roll back thesnapshot. In this case, you can create a cloud disk from the snapshot, and then attach it to theinstance on any ECS server in the same region. Currently, only creating a cloud disk from a snapshot of a data disk is supported. To create a cloud disk from a snapshot of a data disk:

Log on to the ECS Management Console.Click Instances in the left navigation bar.Select a region at the top of the page. Then, click Create Instance in the top-right corner ofthe page.Click Cloud Disk.Select a region and zone. Note: A cloud disk can be attached to a server in the sameavailability zone of the region only. Cloud disks cannot be attached across regions.Click Create disk with snapshot. Find the snapshot you want to use. You can search it by thesnapshot ID.


29

7.

8.

9.

10.

-

●

●

●

-

-

-

-

-

-

-

-

Confirm the order.After a while, the created disk is displayed in the disk list.Go to More > Attach. Enter the instance ID to which you want to attach the disk, and selectthe device name.Now you can log on to your instance to check the data on the disk. For Windowsinstances, you can see the disk after logon. For Linux instances, you need to mount it first.

Attach a data disk ECS supports the attachment of Basic Cloud Disk, Ultra Cloud Disks and SSD Cloud Disk that serve asdata disks. You have two ways to attach a data disk, either from the Instance menu or from the Diskmenu in the left navigation bar. The two ways are introduced below. Considerations Before attaching data disks, consider the following:

The instance must satisfy all of the following conditions: The instance is in Running or Stopped status.The security control marker is not Locked.The instance is not in arrears.

The cloud disk must be in Available status.A single instance can be attached with 1 system disk and up to 4 data disks (all diskcategories counted in).A cloud disk can be attached to an instance in the same zone only, not across zones.A cloud disk can be attached to only one instance at a time. Attachment to several instancesis not supported.A cloud disk can be attached to any instance in the same region and zone (Subscription orPay-As-You-Go instances).When a cloud disk acts as an instance’s system disk, it cannot be separately attached.

You can attach a disk either from the Instances menu or from the Disks menu in the navigation bar.

If you need to attach multiple disks to a single instance, it is easier to do this from the Instances menu.If you need to attach disks to different instances, it is easier to do this from the Disks menu.


30

-

From the Instances menu

Log on to the ECS Management Console. Click Instances in the left navigation bar. Select a region at the top of the page. Click the name of the instance for attachment or click Manage on the right side of the Instance page.

Click Instance Disks in the left navigation bar. The disks already attached to the instance aredisplayed.

Click Attach Disk on the right side of the page and select Available Devices and Target Disk to attach the disk. As needed, set whether disks are to be released with instances andwhether snapshots are to be released with disks.

Release disk together with instance： When you release the instance, the disk willbe released together. Release auto-snapshot together with disk： When you release the disk, all autosnapshots will be released. But the snapshot you manually created will be retained.It is recommended you do not select this option.


31

After attaching a disk, you need to log on to the instance to format disk partitions and attach newpartitions. For details, refer to Next Step at the bottom of this page. From the Disks menu

Log on to the ECS Management Console. Click Disks in the left navigation bar. Select a region at the top of the page. Click the name of the disk to attach. The disk status must be Available. You cannot attachthe disks in In Use status. On the right end of the disk list, click More > Attach. Select the target instance and release action.


32

-

-

-

-

1.

2.

3.

4.

Release disk together with instance： When you release the instance, the disk willbe released together.Release auto-snapshot together with disk： When you release the disk, all autosnapshots will be released. But the snapshot you manually created will be retained.It is recommended you do not select this option.

After attaching a disk, you need to log on to the instance to format disk partitions and attach newpartitions. For details, refer to What is Next at the bottom of this page. What is next for Linux After attaching a disk, you need to log on to the instance to format disk partitions and attach newpartitions. For detailed instructions, see Format and attach a data disk. What is next for Windows After attaching a disk, you need to log on to the instance to format disk partitions. For detailedinstructions, see Format a data disk. Detach a data disk ECS supports the detachment of Basic Cloud Disks, Ultra Cloud Disks and SSD Cloud Disks that serveas data disks. You have two ways to detach a data disk, either from the Instances menu or from the Disks menu in the left navigation bar. Both are introduced below. You can only detach data disks, not system disks. Before detaching a data disk, note the following considerations:

In Windows, we recommend you stop the read and write operations on all file systems onthe disk to ensure data integrity. Otherwise, the data being read/written will be lost.In Linux, you must log on to the instance and run the unmount command for the disk. Afterthe command is run, go to the console and detach the disk.

From the Instances menu

Log on to the ECS Management Console.Click Instances in the left navigation bar. Then, select a region at the top of the page.Click the name of the instance for detachment or click Manage on the right side of theInstance page.Click Instance Disks in the left navigation bar. The disks already attached to the instance are


33

5.

6.

7.

1.

2.

3.

4.

5.

-

-

-

-

-

displayed.Click the disk to detach.Click Detach in the top-right corner of the page.In the pop-up box, click Confirm Detaching.

From the Disks menu

Log on to the ECS Management Console.Click Disks in the left navigation bar. Then, select a region at the top of the page.Click the name of the disk to detach. The disk status must be In Use.Click Detach in the top-right corner of the page.In the pop-up box, click Confirm Detaching.

Change the system disk By changing the system disk, you can change the operating system, for example, from WindowsServer 2003 to Windows 2012. Note: The Hong Kong, Singapore, and US regions do not support replacement between Linux andWindows. A Linux or Windows can be only replaced by a different version of the same operatingsystem type. Considerations for changing the system disk Risks

This operation requires you to stop your instance, which means interruption of yourbusiness. Therefore, perform this operation with caution.After replacement, you must redeploy the runtime environment on the new system disk.There is a possibility of a long interruption of your business. Therefore, perform thisoperation with caution.Replacing the system disk will result in the loss of the automatic snapshots and data on youroriginal system disk. Make necessary backup in advance.Manually created snapshots are retained after the replacement. However, since the disk ID ischanged, you can no longer use the manually created snapshots on the original system diskto roll back the new system disk. The retained snapshots can be used to create customimages.After the system disk is replaced, the original system disk will be deleted.


34

-

-

1.

2.

3.

4.

Note:

To retain enough snapshot quota for the auto snapshot policy of the new disk, you candelete unwanted snapshots.Changing the system disk will not change your instance IP address.

Retain auto snapshots By default, the auto snapshots will be released along with the disk. If you want to keep the autosnapshots, see Configure releasing auto snapshots together with disk. Procedure of changing the system disk A complete procedure of changing the system disk includes the following steps:

Create a snapshot for the current system disk.Create an image based on the snapshot.Change the system disk.Set auto snapshot policies for the new system disk.

If you do not want to retain the data in the system disk, but only want to change the operatingsystem, simply jump to Step 3 to change the system disk directly. Step 1: Create a snapshot based on the current system disk Skip this step if you do not want to retain the data on the system disk. Do not create the snapshot during busy hours. It takes about 40 minutes to create a snapshot of 40GB. Ensure you reserve sufficient time for it. Note: Make sure the system disk has at least 1GB free space; otherwise, the instance may fail to startafter you change the system disk.

Log on to ECS Management Console. Click Instances on the left navigation bar. Then click the region. Click the instance for which you want to change the system disk. Click Instance Disks on the left navigation bar. Find the system disk you want to change, and then click Create Snapshot.


35

Enter a name for the snapshot. Click Instance Snapshots on the left navigation bar, you can check the progress and statusof the snapshot.

Step 2: Create an image based on the snapshot Skip this step if you do not want to retain the data on the system disk. If you do want to retain the data on the current system disk, you need to create an image to replicatethe data on the system disk. Note: Make sure the system disk has at least 1GB free space; otherwise, the instance may fail to startafter you change the system disk.

Continue with the previous step. Find the snapshot you just created, and the click CreateCustom Image.

Enter a name and description for the image. Go back to the navigation bar, click Images, and you can check the process and status ofthe new image.

Step 3: Change the system diskTo change a system disk:


36

-

-

Log on to the ECS Management Console. Click Instances on the left navigation bar. Then, select a region at the top of the page. Stop the instance before changing the system disk. In the instance list, select the instancefor system disk replacement and click Stop at the bottom. After the instance is stopped, on the right end of the instance table, click More > ChangeSystem Disk. A dialog box showing the considerations is displayed. Read the considerations carefully,and then confirm the operation. Select an image. Set the password for Administrator or root. Click Pay Now. Pay for the expenditure that incurred, if any. An important message is prompted. Read it carefully. After confirming everything is correct,click OK.

Step 4: Configure the auto snapshot policies After changing the system disk, the auto snapshot policies you have set will no longer work for thenew system disk, because the disk ID has changed. In this case, you need to configure auto snapshotpolicies for the new system disk. For more information, see Set auto snapshot policies for disks. Reinitialize a disk Disk reinitialization restores a disk to the status when it was initially set up. Before reinitializing a disk, you must read the following considerations:

Reinitializing a disk will lose the data on that disk. Ensure you back up data before youproceed, for example, using a snapshot. For details, see Create a snapshot.Keep your cell phone reachable. You will receive a verification code on your phone for thereinitialization.

After disk reinitialization:


37

-

-

-

1.

2.

3.

4.

5.

6.

7.

1.

2.

3.

4.

The instance retains the operating system and version, and restores it to the initial status.The IP address of your ECS instance is not changed. The data on the original system disk willbe cleared, but the automatic backup of snapshots on the instance will be retained and canbe used to roll back the applications on the instance.For a data disk, you do not need to attach it after reinitialization.

Procedure

Log on to the ECS Management Console.Click Instances in the left navigation bar.Select a region at the top of the page.Stop the instance before reinitializing the disk. Select the instance for disk reinitializationand click Stop at the bottom.Click the instance name. Click Instance Disks in the left navigation bar. Select one or moredisks to reinitialize. Then, click Re-initialize Disk.

Enter a new password for login after the reinitialization is finished. Click Confirm Re-initializing Disk.Enter the verification code that you receive on your cell phone. Click OK.

Roll back a disk When you want to roll back the data on a disk to a previous time point, you can do this through diskrollback. Important: Snapshot rollback is irreversible. Once rollback is finished, the original data cannot berestored. Therefore, be careful when performing this operation. To roll back a disk:

Log on to the ECS Management Console.Click Instances in the left navigation bar. Then, select a region at the top of the page.Stop the instance before rolling back the disk. Select the instance for disk rollback and click Stop at the bottom.Click the instance name. Then, click Snapshots in the left navigation bar. Select the snapshot


38

5.

-

-

1.

2.

for rollback. You can select only one snapshot at a time. Then, click Disk Rollback.In the pop-up box, click OK.

After snapshot rollback is completed, the instance goes into the starting status and then the runningstatus. If you encounter an error during rollback, one possible cause is that the instance is still running, notfully stopped yet. Disk rollback can only be done when the instance is completely stopped. Wait untilthe instance is fully stopped before continuing with rollback. View monitoring information of a disk You can view the IOPS, BPS, and other monitoring information of a disk. The procedure is as follows:

Log on to the ECS Management Console. Select the disk for which to view monitoring information. There are two methods to locate adisk:

Click the instance to which the disk is attached on the instance list page, and thenclick Instance Disks.Locate the disk in the Disks list.

Click Disk Monitoring to view the IOPS and BPS monitoring information. Using the time segments in the top-right corner, you can select different monitoringperiods, such as 1 hour, 6 hours, 1 day, and 7 days. You can also use custom monitoringstart and end times.

Delete a data disk If you do not need a data disk any more, you can delete it. Important: Be careful that once you delete a data disk, there is no way to retrieve the data on thedisk.

Log on to the ECS Management Console.Click Disks in the left navigation bar. Then, select a region at the top of the page.


39

3.

4.

5.

-

-

-

-

1.

2.

3.

4.

5.

If you want to keep all automatic snapshots of the disk, on the right end of the disk, click More>Modify Attributes. Make sure that the option Release auto-snapshot together withdisk is selected. Otherwise, all your automatic snapshots will be deleted together with thedisk.On the right end of the disk, click More>Delete.Click Confirm Deletion to delete it.

Snapshots Create a snapshot You can easily create instance snapshots to save the system data status at a certain point in time asdata backup or to create images. Description:

The first time you create a snapshot for a disk, it will take a relatively long time because thisis a full snapshot.When you create additional snapshots for a disk, the process is quicker, but the length oftime depends on the amount of data changed since the last snapshot. The more data thathas changed, the longer the process.Creating snapshots of a disk may slightly reduce the disk performance. This may directlyaffect your business, as the disk will run slowly for a moment when you create a snapshot.The extent of the effect varies, depending on the amount of data changed. Do not createsnapshots during peak business hours.Manually created snapshots, unlike automatic snapshots, will be retained until manuallydeleted.


Log on to the ECS Management Console.Click Disks in the left navigation bar. Here, you will see a list of disks.Select the disk for which to create the snapshot. You can only select one disk at a time. Youcan select both system disks and data disks.Click Create Snapshot.Enter the snapshot name and click OK.

In the left navigation bar, you can click Snapshots to view all snapshots. Alternatively, go to Instances > Instance Snapshots to view the snapshots of a particular instance.


40

-

-

-

Create an auto snapshot policy You can create an auto snapshot policy for disks to define parameters such as the time for autosnapshot creation, repetition and retention. The procedure is as follows:

Log on to the ECS Management Console. In the left navigation bar, click Snapshot > Auto Snapshot Policy. Here, you can see a list ofauto snapshot policies. In the top-right corner, click Create Auto Snapshot Policy. Define the auto snapshot policy parameters.

Auto Snapshot Schedule: This is the name of the auto snapshot policy. The lengthmust be 2-128 characters. It must start with an upper or lowercase letter. It cancontain numbers, “_” and “-“.Time: There are 24 snapshot creation points in time every day between 00:00 and23:00.Repeated day: There are 7 possible repetition dates each week between Mondayand Sunday. Retention period: The number of days the snapshot is retained and can be 1-65536days or permanently, 30 days by default.


41

Click OK.

Delete an auto snapshot policy If you no longer need an auto snapshot policy, you can find the policy and then click Delete Policy toits right. Set auto snapshot policies for disks According to your business needs, you can set an auto snapshot policy for disks using the autosnapshot command auto_yyyyMMdd_1, for example, auto_20140418_1 Note:


42

-

-

-

-

-

1.

2.

3.

4.

5.

6.

1.

2.

3.

4.

5.

Creating snapshots may disturb read/write operations on your disk. It is recommended thatyou perform auto snapshots during the periods that the service load is low so as to reducethe effect on your service.When not in use, basic cloud disks do not apply auto snapshot policies.The snapshots you have manually created do not conflict with auto snapshots. However, ifyou are performing an auto snapshot on a disk, you must wait for it to finish before manuallycreating a snapshot.

You can specify and perform an auto snapshot policy through disk or snapshot.

Disk: To apply an auto snapshot policy for a specific disk.Snapshot: To apply a unified auto snapshot policy for several or all disks.

Enable auto snapshot policy through disk Use this method to specify an auto snapshot policy for a specific disk. The procedure is as follows:

Log on to the ECS Management Console.Click Disk in the left navigation bar.Select a region.Find the disk for which you want to execute the policy and then click Set auto SnapshotPolicy on the right side.You can enable the auto snapshot function and select the desired snapshot policy.Click OK.

Enable auto snapshot policy through snapshot Use this method to specify an auto snapshot policy for a disk.

Log on to the ECS Management Console.In the left navigation bar, click Snapshot > Auto Snapshot Policy.Select a region. Here, you can see a list of all the auto snapshot policies for this region.Find the auto snapshot policy you want to apply and then click Set Disk on the right side.Click the Disk without preset policy tab, select one or more disks that you want and thenclick Enable autosnapshot .


43

6.

1.

2.

3.

4.

5.

If you want to disable a snapshot policy on one or more disks, click the Disk with presetpolicy tab, find the disk(s) that you want to disable snapshot policy and then click Disableautosnapshot.

Configure releasing auto snapshots togetherwith the disk By default, when you detach a data disk, all auto snapshots are deleted together with the disk. However, if you decide to retain the auto snapshots when releasing the data disk, you can manuallyconfigure it.

Log on to the ECS Management Console.Click the region.Click Disks on the left navigation bar.Find the disk that you want to configure, and then click More > Modify Attributes.Mark or unmark Release auto-snapshot together with disk, and then click OK.


44

-

-

1.

2.

3.

4.

Delete a snapshot When you no longer need a snapshot or you have reached your snapshot quota, you can deletesnapshots to free up space. Note:

Once deleted, a snapshot cannot be restored in any way. Be careful when performing thisoperation.If a snapshot has been used to create a user-defined image, you must delete the associatedimage before you can delete the snapshot.

To delete a snapshot:

Log on to the ECS Management Console.In the left-side navigation bar, click Snapshots > Snapshots. Then, select a region to view allsnapshots in this region.Select one or more snapshots you want to delete.Click Delete. In the pop-up dialog box, click OK.

Images Create a custom image from snapshots Custom images help you effectively run ECS instances. Using custom images, you can activatemultiple ECS instances with identical OS and environment data at a time to meet your needs for


45

-

-

-

-

-

1.

2.

3.

elastic scaling. Custom images are based on snapshots of the disks of ECS at a certain point in time. You can set upidentical or different configurations for ECS instances created based on images. Considerations

An account supports up to 10 custom images with different data.Even if the ECS used for creating a custom image expires or the data is erased (that is, thesystem disk used for the snapshot expires or is released), the custom image and the ECSinstances created from the custom image will not be affected. However, auto snapshots willbe cleared when an ECS instance is released.You can upgrade the CPU, memory, bandwidth, hard drive and other configurations of ECSinstances activated using a custom image.Custom images cannot be used across regions.A custom image applies to any ECS payment mode, either yearly/monthly subscription orPay-As-You-Go. Custom images for ECS instances under yearly/monthly subscription planscan be used to create Pay-As-You-Go instances, and vice versa.

Operation procedure

Log on to the ECS Management Console.Click Snapshots in the left navigation bar. Here, you will see a list of snapshots. Then, selecta region at the top of the page.Select a snapshot with the disk attribute as System Disk. Click Create Custom Image. Datadisks cannot be used to create custom images.

In the pop-up dialog box, you can view the snapshot ID. Enter a name and description forthe custom image. You can also select up to four snapshots of data disks for the image. Note: Ensure that youdelete all confidential data before creating a custom image.


46

-

-

If the snapshot ID is left blank, an empty disk will be created. The default size is5GB. If you select available snapshots, the disk size is the same as the size of thesesnapshots.

Click Create.

You have now created a custom image. By clicking Images in the left navigation bar, you can view theimages you have created. Linux considerations

When creating custom images on a Linux instance, note that you do not need to load data


47

-

disk information in the /etc/fstab file. If you do, instances created using this image cannot bestarted.It is strongly recommended that you detach all the data disks in Linux before taking asnapshot and creating an image. Otherwise, there is a risk that the ECS instances createdbased on the custom image cannot be started and used.

How to detach disks and delete disk table data If /dev/hda5 is attached to /mnt/hda5, you can run any of the following three commands to detachthe file system:

/etc/fstab is an important configuration file in Linux. It contains details of the file system and storagedevices attached at startup. If you do not want to attach a specified partition when starting the VM, you need to delete thecorresponding lines from this configuration file. For example, you can delete the following statementto disconnect xvdb1 at startup:/dev/xvdb1 /leejd ext4 defaults 0 0 How to determine whether a data disk is detached and a customimage can be created You must ensure that the auto attach data disk statement line has been deleted from the fstab file. Use the mount command to view information on all attached devices. Ensure that the executionresults do not contain the information of the data disk partition. Relevant configuration files Before creating an image, ensure the key configuration files in the following table have not beenmodified; otherwise, the new instance will not start.

```umount /dev/hda5umount /mnt/hda5umount /dev/hda5 /mnt/hda5```

Configuration File Purpose Risks if changed

/etc/issue, /etc/-release,/etc/*_version

For system release andversion

Modifying /etc/issue will makethe system release versionunidentifiable, and causeinstance creation failure.

/boot/grub/menu.lst,/boot/grub/grub.conf For system boot

Modifying/boot/grub/menu.lst will resultin kernel loading failure, andthe system cannot start.


48

-

-

-

-

-

-

1.

2.

3.

Create an instance using images Images are mainly used to create ECS instances. When using images, you must consider thefollowing:

Region: Only images in the current region can be used. Cross-regional use of images is notsupported. However, you can copy an image to another region. For details, see Copy animage.OS: Linux or Windows.OS bits: 32-bit or 64-bit.

When purchasing an instance, you can select a custom image, public image, or shared image.

Custom images are images you have manually created. They can be queried and managedon the custom image page of the console. See Create a custom image.Public images are images officially provided by Alibaba Cloud, available in various Windowsversions and Linux releases.Shared images are custom images that another account shares with you.

Operation procedure:

Log on to the ECS Management Console.Click Snapshots in the left-side navigation bar. Here, you will see a list of snapshots. Then,select a region at the top of the page.Select a snapshot with the disk attribute as System Disk. Click Create Custom Image. Notethat data disks cannot be used to create custom images.

/etc/fstab For attaching partitionsduring boot.

Modifying it will causepartition attaching failure, andthe system cannot start.

/etc/shadow For storing systempasswords.

If this file is set to read-only,the password file cannot beedited, and instance creationwill fail.

/etc/selinux/config For system security policiesModifying /etc/selinux/configand enabling SELinux will resultin start failure.


49

4.

5.

6.

7.

8.

9.

In the pop-up dialog box, you can view the snapshot ID. Enter a name and description forthe custom image. You can also add data snapshot to this image. Click Create.Click Instances in the left-side menu. In the top-right corner of the page, click CreateInstance.

Select the payment method, region, network type, instance, network bandwidth, and otherparameters. For details, see the instance creation process in the Quickstart for Linux and Quickstart for Windows.Select an image. In this example, a custom image is selected.

If the custom image you have selected contains multiple data disk snapshots, the samenumber of data disks will be created automatically. The size of each disk is the same as thecorresponding snapshot. You can increase the size, but cannot decrease it.Continue to set the other parameters and then click Buy Now.

Copy an image Copying an image lets you use images across regions. By default, custom images cannot be used across regions. However, you can copy the image from aregion to another. This allows you to deploy a backup image system or an identical application


50

1.

2.

3.

4.

5.

6.

7.

1.

2.

3.

4.

environment in another region. The time needed for copying is determined by the network transmission speed and the number oftasks in the task queue. Make sure you plan carefully for the operation. Procedure The procedure for copying an image is as follows:

Log on to the ECS Management Console.Click Images in the left-side navigation bar. Here, you will see a list of images.Select a region at the top of the page.Select the image to copy. The image type must be Custom Image. Then, click Copy Image at the right end of the image table. In the pop-up dialog box, you can view the image ID.Specify the target region to which you want to copy the image.Enter a name and description for the target image.Click OK to create an image copy task.

The copying process will take some time. You can wait and check the progress later. A snapshot and a custom image will be automatically created in the target region. Wait until theimage status changes to available before using the copy to create ECS instances. Cancel copying Before your custom image still has not been completely copied, you can cancel the operation. To cancel copying an image:

Log on to the ECS Management Console.Select Images and click the target region of the copy to view the image list.Select the copy target image and click Cancel Copy. The system will prompt you to cancelimage copying, and the image status will change to ‘creation failed’.Click OK to cancel the copy operation.

Share an image You can share your custom images with other users. Through the Management Console or ECS API,you can query images shared by other accounts to your own account. You can use the images sharedby other accounts to create ECS instances. Before sharing an image with other accounts, make sure the image does not contain any sensitive orimportant data or software.


51

-

-

-

-

-

-

-

-

1.

2.

3.

4.

5.

-

-

6.

Note: Alibaba Cloud does not guarantee the integrity or security of the images shared by otheraccounts. Ensure that you use only images shared by trusted accounts. When using such images tocreate ECS instances, ensure that you log on to the ECS instance to verify that the image is secure andcomplete. Considerations Restrictions

A single user can obtain a maximum of 30 shared images.One image can be shared with a maximum of 50 users.Shared images do not count as part of your image quota.Shared images can only be used to create instances in the same region as the source image.Only image owners can share images with other accounts. You cannot share an image thatcomes from account A with account B.

Impact of deleting shared images

You can delete a custom image even you have shared it with other accounts. Before deletingthe shared image, however, you need to unassociate it from other accounts.If you delete an account that has shared a custom image, the users who are using the sharedimage can no longer find the image through the Management Console or ECS API, or usethe image to create ECS instances.Deleting shared custom images may cause system disk reinitialization to fail for ECSinstances created from these images.

Operation procedure

Log on to the ECS Management Console.Click Images in the left-side navigation bar. Here, you will see a list of images.Select a region at the top of the page.Select the image to copy. The image type must be Custom Image. Then, click Share Image.In the pop-up dialog box, select the account type and enter an Alibaba Cloud account.There are two types of accounts:

Alibaba Cloud account: Enter the Alibaba Cloud account (login account) of the useryou want to share the image with.Account ID: Enter the Alibaba CloudID of the user you want to share the imagewith. The Account ID can be obtained from the User Center on the Alibaba Cloudwebsite by selecting Account Management > Security Settings > Account ID. Youcan log in at the following link: https://account.console.aliyun.com/#/secure

Click Share Image.


52

1.

2.

3.

4.

5.

Cancel sharing You can cancel sharing an image. This way, the accounts sharing this image cannot query or use theimage anymore. Note: If you cancel sharing an image that other account uses to create an ECS instance, the systemdisk of this instance cannot be reinitialized. Operation procedure

Log on to the ECS Management Console.Click Images in the left-side navigation bar. Here, you will see a list of images.Select a region at the top of the page.Click Share Image next to the image you want to cancel sharing.You can see a list of users this image is shared with. Click Unshare next to the account youwant to cancel sharing this image.


53

1.

2.

3.

4.

View the list of accounts sharing an image You can query a list of accounts that an image under your name is shared with. Operation procedure

Log on to the ECS Management Console.Click Images in the left-side navigation bar. Here, you will see a list of images.Select a region at the top of the page.Click Share Image next to the image you want to view the list of accounts sharing this

image.


54

1.

2.

3.

-

-

-

-

-

-

-

-

View shared image list You can query a list of images that other accounts share with you. Operation procedure

Log on to the ECS Management Console.Select the region to query.In the image list header, select Shared Image as the Image Type to view the list of imagesshared with you by other accounts.

Import an image You can import your physical image files to the ECS environment and create a custom image. You canthen use this image to create ECS instances. Restrictions Supported operating systems Windows (32 and 64-bit)

Microsoft Windows Server 2012 R2 (standard edition)Microsoft Windows Server 2012 (standard edition, data center edition)Microsoft Windows Server 2008 R2 (standard edition, data center edition, enterprise edition)Microsoft Windows Server 2008 (standard edition, data center edition, enterprise edition)Microsoft Windows Server 2003 R2 (standard edition, data center edition, enterprise edition)Microsoft Windows Server 2003 with Service Pack 1 (SP1) (standard edition, data centeredition, enterprise edition)Win7 professional edition and enterprise editionDoes not support Windows XP, Windows 8, and Windows 10


55

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

-

●

●

Linux (64-bit)

Red Hat Enterprise Linux (RHEL) 5,6,7CentOS 5,6,7Ubuntu 10,12,13,14Debian 6,7OpenSUSE 13.1SUSE Linux 10,11,12CoreOS 681.2.0+

Supported image formats

RAW formatVHD format

Supported file systems

Windows (32 and 64-bit) Supports NTFS format and MBR partition.Linux/Unix (32 and 64-bit) Supports ext3 and ext4 file system format and MBR partition.

Requirements and restrictions

This function only supports System Disk images, not Data Disk images.Does not support multiple network interfaces.Does not support IPv6 addresses.Password policy: 8-30 characters, must contain three types of characters(uppercase/lowercase letters, numbers, or special characters).Install the XEN and KVM virtualization platform drivers.

Windows Restrictions:

Windows system disk size: 40-500 GBImported Windows images must provide Windows activation service.The firewall must be disabled. Otherwise, remote login is not possible. Port 3389 must beenabled.Disable UAC.

Linux Restrictions:

Linux system disk size: 40-500 GBLinux core requirements:

SELinux is not activated.The firewall is disabled; port 22 is enabled by default.


56

●

-

-

-

-

-

-

-

-

-

-

-

-

Imported Red Hat Enterprise Linux (RHEL) images must have a BYOL license. Youmust buy your own product serial numbers and services from the manufacturer.

Import images from the Console Prerequisites

Create an image in accordance with the image restrictions and requirements.If you have not activated OSS already, activate OSS first.Use an OSS third-party tool client, OSS API or OSS SDK, to upload the file to a bucket in thesame region as the ECS custom image to import.Submit a ticket to apply for ECS image import permission.To import the image, you must manually grant OSS access permission to the official ECSservice account.

Operation procedure

Log on to the ECS Management Console. Click Images in the left-side navigation bar. Here, you will see a list of images. Click Import Image. Ensure the image to import meets the prerequisites. If you have not granted the official ECSservice account access to your OSS, image import may fail. Fill out the image import form.

Region: Select the region where you want to deploy the application.Image File OSS Address: Copy the object address taken from the OSS console.Image Name: The length should be 2-128 characters. It should start with an upperor lowercase letter or a Chinese character. It can contain numbers, “_”, and “-“.System Disk Size: Windows system disk size: 40-500 GB; Linux system disk size: 20-500 GB.System Architecture: 64-bit OS: x86_64; 32-bit OS: i386.Operating System Type: Windows or Linux.System Releases: Currently supported OS releases: Windows: Windows Server 2003, 2008, 2012, and Windows 7. Linux: CentOS, redhat, SUSE, Ubuntu, Debian, gentoo, FreeBSD, CoreOS, OtherLinux editions (submit a ticket to confirm the supported editions). If your image OS is a custom edition developed on a Linux core, submit a ticket to


57

-

-

-

-

contact Alibaba Cloud.Image Format: Supports RAW and VHD format. We recommend customers use theRAW format for a higher success rate. You cannot use qemu-image to create VHDimages.Image Description: Enter a description of the image.

Click Submit to create an image import task.

Image importing takes time, usually several hours. The duration of the task depends on the size ofyour image file and how many other import tasks are running. You can view the task progress in theimage list of the import region. You can also find and cancel the image import task in the task manager. Modify custom image names anddescriptions You can modify the names and descriptions of custom images at any time. The procedure is as follows:

Log in to the ECS Management Console. Click Images in the left-side navigation bar. Here, you will see a list of images. Select a region at the top of the page. Select the image to edit. The image type must be Custom image.

Modify Name: Move the mouse over the image name, and a small pen icon willappear. Click this icon to modify the image name.Modify Description: Click Modify Image Description.


58

1.

2.

3.

4.

5.

-

-

-

-

Click OK.

You have successfully modified the name and description of a custom image. Delete a custom image If you no longer need a custom image, you can delete it. To ensure successful deletion, check thatyou do not currently have any ECS instances created from this custom image. The procedure is as follows:

Log on to the ECS Management Console.Click Images in the left-side navigation bar. Here, you will see a list of images.Select a region at the top of the page.Select the image to delete. The image type must be Custom Image. Click Delete.In the pop-up dialog box, click OK.

You have now deleted the custom image. Security groups Default security group rules For Classic network In the Classic network, the default rules of the default security group are as follows:

Refuses all for Intranet ingress (inflow), and allows all for Intranet egress (outflow).Allows all for 0.0.0.0/0 for both Internet ingress and egress, that is, allows all for Internet.

For VPC In VPC, the default rules of the default security group are as follows:

Allows all for 0.0.0.0/0 for both Intranet ingress (inflow) and egress (outflow), that is, allowsall instances in the VPC to communicate with each other.For VPC security group rules, all rules are set on the Intranet ingress (inflow) and egress(outflow) directions, regardless of Intranet or Internet.


59

1.

2.

3.

4.

5.

-

-

6.

7.

1.

2.

3.

4.

For user-defined security groups For user-defined security groups, before you specify any rules, the default rules are to allow all foregress (outbound) and refuse all for ingress (inbound), regardless of Intranet or Internet. Create a security group As an important method of security isolation, the security group functions as virtual firewalls and isused to set network access controls for one or more ECS instances. When creating ECS instances, youmust select a security group. You can also add security group rules to control outbound (egress) andinbound (ingress) network access for all ECS instances in the security group. The procedure is as follows:

Log on to the ECS Management Console.Click Security Groups in the left-side navigation bar.Select a region.Click Create Security Group.In the pop-up dialog box for security group creation, enter the following information:

Security Group Name: The length must be 2-128 characters. It must start with anupper or lowercase letter or a Chinese character. It can contain numbers, “_”, and“-“.Security Group Description: The length must be 2-256 characters. It cannot startwith http:// or https://

Select a network type. There are two network types: Classic network and VPC. If you selectVPC, you must select a specific VPC. If no VPCs have been created in the current region, youmust create one first.Click OK to create the security group.

Query the security group list You can query security groups on the management console. The procedure is as follows:

Log on to the ECS Management Console.Click Security Groups in the left-side navigation bar.Select a region to display a list of all security groups in the region.You can enter a VPC ID in the filter input box to list all the security groups under this VPC.


60

1.

2.

3.

4.

-

-

5.

1.

2.

3.

4.

5.

6.

-

-

-

-

-

Modify security group properties You can modify security group names and descriptions. The procedure is as follows:

Log on to the ECS Management Console.Click Security Groups in the left-side navigation bar.Select a region to display a list of all security groups in the region.Find the security group to modify. Two methods are available:

Modify Name: Move the mouse over the name and click on the modify icon thatappears to modify the security group name.Modify Name and Description: Click Modify to the right of the security group youwish to modify. In the pop-up dialog box, you can modify the group name anddescription.

Click OK to modify the security group.

Authorize security group rules Authorized security group rules are designed to permit or forbid inbound (ingress) and outbound(egress) Internet or Intranet access for ECS instances in a security group. You can authorize or cancelsecurity group rules at any time. Security group rules you have changed will automatically apply toECS instances associated with the security group. When there are no rules in a security group, outbound access is permitted, but inbound access isforbidden for ECS instances. If two security groups have identical rules, but different access rules, access rejection rules are validand access acceptance rules are invalid. Operation procedure

Log on to the ECS Management Console.Click Security Groups in the left-side navigation bar.Select a region.Find the security group for rule authorization and click Configure Rules.Click Add Security Group Rule.In the pop-up dialog box, set the following parameters:

NIC Type: Internet | Intranet. If this security group belongs to a VPC, select Intranet.Rule Direction: Inflow | OutflowAuthorization Policy: Allow | RefuseProtocol Type: All | TCP | UDP | ICMP | GREPort Range: 1-65535; e.g. “1/200”, “80/80”, “-1/-1”


61

-

-

-

7.

-

-

-

-

-

-

-

-

-

Authorization Type: Address Field Access | Security Group AccessAuthorization Object: If the authorization type is address field access, enter theauthorization object in IP address or CIDR segment format, e.g: 10.0.0.0, 0.0.0.0/0,or 192.168.0.0/24. Only IPv4 addresses are supported. If the authorization type issecurity group access, select a security group from the security group list as theauthorization object.Priority: 1-100; the smaller the number, the higher the priority. For moreinformation about priorities, see later sections herein.

Click OK to authorize the security group rule for this security group.

ECS security group rule priority explanation

More recently created security groups have a higher priority. For example: An instance isassociated with two security groups, A and B, and A was created after B. In this case, ifconflicting rules with the same priority exist in groups A and B, the rule in group A will takeeffect.Security group priorities should not be regarded as only comparable within a security groupbecause they also apply when the policies of different security groups apply to the sameinstance. Therefore, if there is a conflict between rules in different security groups, the rulewith the highest rule priority will apply.If there are authorization rules with the same priority, drop rule will prevail.

Example: Scenario 1:

Security group A, creation time: 2015, rule 100: drop 80Security group B, creation time: 2014, rule 100: accept 80

Result: no connection with port 80 Scenario 2:


Result: connection possible with port 80 Scenario 3:


Result: no connection with port 80


62

1.

2.

3.

4.

5.

-

-

6.

1.

2.

3.

4.

5.

6.

7.

Solution for ineffective policies If packets are transmitted at short intervals throughout the security policy change process, thesecurity group policy will not apply the new rules. Solution: Disconnect from the instance for a period of time, then log on again. The policy will takeeffect. Query security group rules You can query security group rules. The procedure is as follows:

Log on to the ECS Management Console.Click Security Groups in the left-side navigation bar.Select a region.Select a security group and click Configure Rules.The content is different for classic networks and VPCs:

If the security group is VPC, you will see the following two security group rule tabs:Intranet Inbound (Ingress) and Intranet Outbound (Egress).If the security group is classic network, you will see the following four securitygroup rule tabs: Internet Inbound (Ingress), Internet Outbound (Egress), IntranetInbound (Ingress), and Intranet Outbound (Egress).

Click a tab to view the security group rules of the specified type.

Revoke security group rules If you no longer wish to apply a security group rule, you can cancel it. The procedure is as follows:

Log on to the ECS Management Console.Click Security Groups in the left-side navigation bar.Select a region.Select the security group for rule revocation and click Configure Rules.On the security group management page, find the type of rule you wish to revoke: InternetInbound, Internet Outbound, Intranet Inbound, or Intranet Outbound.Select a security group rule and click Delete.In the pop-up dialog box, click OK. The security group rule is now canceled.


63

1.

2.

3.

4.

5.

-

-

-

-

-

-

Delete a security group If a security group does not contain ECS instances and is not referenced in the rules of anothersecurity group, you can delete this security group. Deleting a security group will also delete all itssecurity group rules. The process for deleting a security group using the console is as follows:

Log on to the ECS Management Console.Click Security Groups in the left-side navigation bar.Select a region to display a list of all security groups in the region.Select one or more security groups (you can also select all security groups) and click Delete.In the pop-up dialog box, click OK to delete the security group.

Application scenarios Besides providing security assurance, you can use security groups for the following purposes:

Scenario 1: Intranet communicationScenario 2: Shield specific IP addresses or portsScenario 3: Only allow remote login of a specific IP addressScenario 4: Only allow an instance to access to a specific IP address

The following section gives detailed instructions for these four security group applications. Description: The cases introduced in this document only apply to Classic Networks. Scenario 1: Use security groups for Intranetcommunication In a classic network, you can use security groups for Intranet communication between different ECSinstances. There are two situations:

Case 1: Instances belonging to the same account in the same regionCase 2: Instances belonging to different accounts in the same region

Case 1: same account in the same region By setting security group rules, you can allow classic network ECS instances belonging to the sameaccount in the same region to communicate via Intranet. ECS instances in the same security group communicate via Intranet by default. However, ECS


64

-

-

-

-

1.

2.

1.

2.

3.

instances in different security groups do not communicate via Intranet by default. Use the solutionsbelow to allow Intranet communication:

Solution 1: You can place the ECS instances in the same security group to allow Intranetcommunication.Solution 2: If the ECS instances are not in the same security group, you can authorize Intranetcommunication between the two security groups by setting access-type security group rules.In Authorization Object, add the IP address of other instance.

Case 2: different accounts in the same region By setting security group rules, you can allow classic network ECS instances belonging to differentaccounts in the same region to communicate via Intranet. For example:

User A has a classic network ECS instance (Instance A, Intranet IP address: A.A.A.A) in the EastChina 1 region. Instance A belongs to the security group Group A.User B has a classic network ECS instance (Instance B, Intranet IP: B.B.B.B) in the East China 1region. Instance B belongs to the security group Group B.

In this situation, you can set a security group configuration that allows Intranet communicationbetween Instance A and Instance B as below:

User A adds the following rule for Group A: In Intranet Ingress the IP B.B.B.B is authorized toaccess all ECS instances in Group A.User B adds the following rule for Group B: In Intranet Ingress the IP A.A.A.A is authorizedto access all ECS instances in Group B.

Thus, the two instances can communicate via Intranet. Scenario 2: Use security groups to shield, intercept andblock access to ECS instance or a port of ECS instancefrom an IP address You can use security groups to shield, intercept and block access to ECS instance or a port of ECSinstance from an IP address. The procedure is as follows:

Log on to the ECS Management Console.Find the instance to configure.Open Instance Security Groups for this instance and click Configure Rules.


65

4.

5.

6.

Click Intranet Ingress and then click Add security group rule.

Select Refuse for the authorization policy and enter an IP address as the AuthorizationObject. Click OK.

If you want to restrict access to a port (for instance, shield access to Port 22 of your ECSinstance from a specific IP address), select Refuse as the authorization policy and TCP as theprotocol type. Then, enter 22/22 as the port range and the IP address to shield from as the


66

1.

2.

3.

4.

5.

authorization object. Click OK.

Scenario 3: Only allow remote login of a specific IPaddress By configuring security groups, you can allow only specific IP address to remotely log on to theinstance. What you need to do is configure rules for the Internet inflow. Take a Linux instance as an example. Configure to allow a specific IP address to access port 22.

Log on to the ECS Management Console.Find the instance to configure.Open Instance Security Groups for this instance and click Configure Rules.Click Internet Ingress and then click Add security group rule.Select Allow for the authorization policy and TCP for the protocol type. Then, enter 22/22 asthe port range and the specific IP address that you can use to access to the instance (1.2.3.4in this example). Enter 1 for priority. Click OK.


67

6. Add another security group rule. Select Refuse for the authorization policy and TCP for theprotocol type. Then, enter 22/22 for the port range and 0.0.0.0/0 for authorization object.Enter 2 for priority.


68

7. Add a third security group rule. Select Allow for the authorization policy and All for theprotocol type. Then, enter 0.0.0.0/0 for authorization object. Enter 3 for priority.


69

-

-

-

1.

2.

3.

4.

Once these three rules are set up, you will get the following result:

The request to access the port 22 from 1.2.3.4 is allowed, according to the rule with thepriority 1.The request to access the port 22 from other IP addresses are refused, according to the rulewith the priority 2.The request to access other ports are allowed, according to the rule with the priority 3.

Scenario 4: Only allow the instance to access to a specificIP address To achieve this, you can configure the Internet egress to refuse any IP (0.0.0.0/0), and then addanother rule to configure the Internet egress to allow the specific IP you want the instance to accessto. Set the priority of the allowing rule greater than the refusing rule.

Log on to the ECS Management Console.Find the instance to configure.Open Instance Security Groups for this instance and click Configure Rules.Select Refuse for the authorization policy, enter 0.0.0.0/0 for authorization object. Enter avalue greater than 1, for example, 2 for priority. Click OK.


70

5.

-

-

-

Add another rule. Select Allow for the authorization policy, enter the specific IP you wantthe instance to access to for authorization object. Enter 1 for priority. Click OK.

Log on to the instance and run ping, or telnet to test. You will find that you do not have access toother IP addresses except the specific one, which indicates that the configuration takes effect. Tags Restrictions

Currently, the Management Console only supports tagging instances.Each tag is composed of a key-value pair.Up to 10 tags can be bound to a single instance.


71

-

-

-

1.

2.

3.

4.

1.

2.

3.

4.

For a single instance, the tag key for each tag must be unique. Tags with identical tag keyswill be overwritten.Tag information is not transmitted across regions. For example, tags created in the EastChina 1 (Hangzhou) region will be invisible to the East China 2 (Shanghai) region.After unbinding a tag that is not bound to any other resource, the tag will be automaticallydeleted.

Edit a tag If you have a very large number of instances, you can tag them to facilitate classification and unifiedmanagement. The procedure is as follows:

Log on to the ECS Management Console.Click Instances in the left-side navigation bar. Then, select a region at the top of the page.On the right end of the instance, click More > Edit Tags.

In the pop-up dialog box, click Create, and then enter your custom tag key and value.

Delete a tag If a tag is no longer needed for an instance, you can delete it. The procedure is as follows:

Log on to the ECS Management Console.Click Instances in the left navigation bar. Then, select a region at the top of the page.Click More next to the instance 1 in the instance list, and then click Edit Tags.In the dialog box, click Delete Tag.


72

5.

6.

1.

2.

3.

4.

You can also go to Tag Management in the left navigation bar to view all tags of a user in acertain region. Select a tag and click Delete Tag to unbind the tag from all resourcesassociated with this tag in the current region. This means that the tag will be deleted andno longer exists. After you click Delete Tag, a pop-up dialog box will appear as shown below. Click OK toremove the tag from all instances permanently.

Tag-based searches You can use tags to quickly find the instances you need. The procedure is as follows:

Log on to the ECS Management Console.Click Instances in the left-side navigation bar. Then, select a region at the top of the page.In the instance 1 bar, click Tag Search in the top-right corner.

Select the tag library you want to use in the search.


73

5.

6.

7.

After the selection, all the tags for this tag key will be displayed. Select and add the requiredtag value to the search conditions on the right side. You can use up to five tags at a time tofilter the search results. The filtered results will show all resources bound to the selectedtag(s).

After selecting the tags you want to use in the search, click OK.

When the search is complete, the page will show the results corresponding to the selectedtag(s), as shown below.

Monitoring You can monitor the running status of ECS instances across multiple dimensions to make sure theyare running smoothly. You can monitor the running conditions of ECS instances using the two portals below:


74

-

-

1.

2.

3.

4.

●

●

1.

2.

3.

Instance detailsCloud Monitor

Instance details

Log on to the ECS Management Console.Click Instances in the left navigation bar. Then, select a region at the top of the page.Click the instance that you want to monitor.On the Instance Details page, you can view the monitoring information, including CPUusage and outbound/inbound network traffic information.

An explanation of the monitoring information is given below:

CPU: The displayed monitoring data shows the CPU usage percentage of the instance. Thehigher the percentage, the higher the CPU load of the instance.

For Windows instances, you can use the task manager on an instance to view theCPU usage. This lists programs by CPU usage, so you can see which programs areusing the CPU resources of the server.For Linux instances, you can use the top command to view CPU usage details. Loginto the instance and execute the top command in the command line. Then, pressShift+P to list programs by CPU usage, so you can see which processes are usingthe most CPU resources.

Network: The displayed monitoring data shows the Internet traffic of the instance in Kbps(1Mbps = 1,024Kbps). The monitoring data shows inbound and outbound instance traffic.For 1Mpbs of bandwidth, the bandwidth is working at full capacity if the outbound networktraffic reaches 1,024Kbps.

Cloud Monitor

On the management console, select Products and Services > CloudMonitor, or click SetAlarm Rules on the Instance Details page.Click ECS on the left-side navigation bar and then select the name of the instance you wishto monitor.Click Install to monitor the instance OS. Click the Monitor Icon to view the various basicparameters. Click Alarm Rules to set alarm rules.


75

For more information about Cloud Monitor, see CloudMonitor Product Documentation.


76

Documents

User Guide - cloudlink.co.kr · 64-bit CoreOS 681.2.0 64-bit CentOS 7.2 64-bit Debian 8.0.4 64-bit FreeBSD 10.1 64-bit Gentoo 13 64-bit OpenSUSE 13.1 64-bit SUSE Linux 64-bit Ubuntu