This topic describes how to manage cloud phones. This topic also describes the status of cloud phones and common operations on cloud phones.
Cloud phone lifecycle
The lifecycle of a cloud phone starts when you create the cloud phone and ends when you delete the cloud phone. During this process, the cloud phone goes through different states. This topic describes all states of a cloud phone during its lifecycle.
Cloud phone status
The following table describes the states of a cloud phone.
State in the Cloud Phone console | State in an API call response | Type | Description |
Creating | CREATING | Transitory | The cloud phone is being created and soon to be available. |
Available | RUNNING | Stable | The cloud phone runs as expected and is ready for use. A cloud phone can be accessed only if it is in the Available state. Note Subscription cloud phones also enter the Available state when they are about to expire. You must pay close attention to their remaining subscription duration. |
Stopping | STOPPING | Transitory | After you stop the cloud phone, the cloud phone briefly enters the Stopping state and finally enters the Stopped state. |
Stopped | STOPPED | Stable | After you stop the cloud phone, the cloud phone enters the Stopping state and then the Stopped state. |
Starting | STARTING | Transitory | After you start the cloud phone, the cloud phone briefly enters the Starting state and finally enters the Available state. |
Failed | FAILED | Stable | The cloud phone enters the Failed state during the creation process due to specific reasons. |
Restarting | REBOOTING | Transitory | After you restart the cloud phone, the cloud phone briefly enters the Restarting state. Then, the cloud phone goes through the Stopping, Stopped, and Starting states, and finally enters the Available state. |
Resetting | RESETTING | Transitory | After you reset the OS of the cloud phone, the cloud phone briefly enters the Resetting state. Then, the cloud phone goes through the Stopping, Stopped, and Starting states, and finally enters the Available state. |
Backing Up | BACKUPING | Transitory | When you back up data on the cloud phone, the cloud phone enters the Backing Up state. After the cloud phone exits the Backing Up state, it enters the Available state. |
Restoring | RECOVERING | Transitory | When you restore data on the cloud phone, the cloud phone enters the Restoring state. After data restoration is complete, the cloud phone enters the Available state. |
Backup failure | BACKUP_FAILED | Stable | If a backup operation fails on the cloud phone, the cloud phone enters the Backup failure state. |
Restoration failure | RECOVER_FAILED | Stable | If a data restoration operation fails on the cloud phone, the cloud phone enters the Restoration failure state. |
Abnormal | UNAVAILABLE | Stable | If an exception occurs on the cloud phone due to specific operations, the cloud phone enters the Abnormal state. To remove the cloud phone from the Abnormal state, you can restart or initialize the OS of the cloud phone. |
Expired | EXPIRED | Stable | If the cloud phone is billed based on the subscription billing method, the cloud phone enters the Expired state after its subscription duration ends. |
Overdue | CEASED | Stable | If your Alibaba Cloud account has an overdue payment, subscription cloud phones in the account enter the Overdue state. |
Change the name of a cloud phone
After you create a cloud phone, the system assigns a name identical to the cloud phone ID to the cloud phone. You can change the name of your cloud phone for easy management and identification based on your business requirements.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the cloud phone belongs to go to the Instance page.
Move the pointer over the name of the cloud phone whose name you want to change and click
. 
Click OK.
Manage cloud phones
Assign cloud phones to users
After you assign cloud phones to users, the users can connect to and access the cloud phones. You can assign each cloud phone to only one user.
Prerequisites
Before you assign a cloud phone, make sure that it is in one of the following states: Available, Stopping, Stopped, Starting, Backing Up, Restoring, Backup failure, and Restoration failure.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and click Assign User in the Actions column. You can select multiple cloud phones and choose More > Assign User in the lower part of the page.
Cancel assignment
After you assign cloud phones to users, you can also cancel the assignment to release the control of the users over the cloud phones. You cannot cancel the assignment of multiple cloud phones at the same time.
Prerequisites
Before you cancel the assignment of a cloud phone, make sure that the cloud phone is in one of the following states: Available, Stopping, Stopped, Starting, Backing Up, Restoring, Backup failure, Restoration failure, Overdue, and Expired.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and click Unassign in the Actions column.
Bind key pairs
Prerequisites
Before you bind a key pair to a cloud phone, make sure that the cloud phone is in the Available state.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and choose
> Attach Key Pair in the Actions column. You can also select multiple cloud phones at the same time and choose More > Attach Key Pair in the lower part of the page.
Unbind key pairs from cloud phones
Prerequisites
Before you unbind a key pair from a cloud phone, make sure that the cloud phone is in the Available state.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and choose
> Unbind Key Pair in the Actions column.
Restart cloud phones
Prerequisites
Before you restart a cloud phone, make sure that the cloud phone is in one of the following states: Available, Abnormal, Backup failure, and Restoration failure.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and click Restart in the Actions column. You can also select multiple cloud phones and choose More > Restart in the lower part of the page.
Start cloud phones
Prerequisites
Before you start a cloud phone, make sure that the cloud phone is in one of the following states: Stopped, Backup failure, and Restoration failure.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and choose
> Start in the Actions column. You can also select multiple cloud phones and choose More > Start in the lower part of the page.
Stop cloud phones
Prerequisites
Before you stop a cloud phone, make sure that the cloud phone is in one of the following states: Available, Backup failure, and Restoration failure.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and choose
> Stop in the Actions column. You can also select multiple cloud phones and choose More > Stop in the lower part of the page.
Create images
Prerequisites
Before you create an image for a cloud phone, make sure that the cloud phone is in the Stopped state.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone, click the
icon, and then click Create Image. In the Create Image panel, configure the Image Name and Description parameters and click OK.
You can choose Image > Custom Image to check the image information and status.
Back up data
Prerequisites
An Object Storage Service (OSS) bucket whose name is prefixed with cloudphone-saved-bucket- is created in the OSS console. To prevent additional traffic fees and the need for Internet access, we recommend that you create the OSS bucket in the same region as your desired cloud phone.
A directory is created in the OSS bucket. This directory is required in the following steps.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and click Data Backup in the Actions column.
In the OSS Bucket Name drop-down list, select the OSS bucket whose name is prefixed with cloudphone-saved-bucket-.
If you select an OSS bucket that resides in a region different from that of the cloud phone, you must enable Internet access for the cloud phone to allow for file transfer. In addition, data backup incurs Internet traffic.
If you select an OSS bucket that resides in the same region as the cloud phone, you do not need to enable Internet access for the cloud phone, and no additional fees are generated.
In the OSS Object Name field, select your OSS object.
In the Specify a file path drop-down list, enter the desired file path.
The file path must be the absolute path to the file system of the cloud phone.
The file path can be a file or a folder.
You can click + Add to specify multiple paths for backup purposes.
In the Description field, enter a description for the backup file.
Click OK.
Check whether the cloud phone enters the Backing Up state. When the cloud phone changes from Backing Up to Available, click Back Up in the left-side navigation pane to view the backup file that is generated.
Restore data
Prerequisites
A backup file is created from the desired cloud phone.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and click Restore Data in the Actions column.
In the OSS Object Name drop-down list, select the backup file created from the current cloud phone.
If you move the backup file in the OSS bucket to a new location, click Change Backup File Address to select the new address of the backup file.
Click OK.
Check whether the cloud phone enters the Restoring state. When the status of the cloud phone changes from Restoring to Available, the data restoration task is complete.
Upload files
Prerequisites
The file that you want to upload is saved in the OSS bucket whose name is prefixed with cloudphone-saved-bucket-.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and click Upload File in the Actions column.
In the Upload Data drop-down list, select the OSS bucket whose name is prefixed with cloudphone-saved-bucket-.
If you select an OSS bucket that resides in a region different from that of the cloud phone, you must enable Internet access for the cloud phone to allow for file transfer. In addition, data upload incurs Internet traffic.
If you select an OSS bucket that resides in the same region as the cloud phone, you do not need to enable Internet access for the cloud phone and no additional fees are generated.
In the OSS Object Name drop-down list, select the desired OSS object.
In the Specify a file path drop-down list, select the desired file path.
The file path must be the absolute path to the file system of the cloud phone.
The file path must be a folder.
Click OK.
Cloud Phone does not provide the data upload progress or status. You can run the “ls xxxx/xxxx” command by using Cloud Assistant to check whether the data upload task is successful.
Download files
Prerequisites
An OSS bucket and directory are created. Before you proceed, go to the OSS console to create an OSS bucket whose name is prefixed with cloudphone-saved-bucket- and create a directory in the bucket.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and click Download File in the Actions column.
In the Download Path drop-down list, select the OSS bucket whose name is prefixed with cloudphone-saved-bucket-.
If you select an OSS bucket that resides in a region different from that of the cloud phone, you must enable Internet access for the cloud phone to allow for file transfer. In addition, data download incurs Internet traffic.
If you select an OSS bucket that resides in the same region as the cloud phone, you do not need to enable Internet access for the cloud phone, and no additional fees are generated.
In the OSS Object Name drop-down list, select the desired OSS bucket.
In the Specify a file path drop-down list, select the desired file path.
The file path must be the absolute path to the file system of the cloud phone.
The file path can be a file or a folder.
If you use a folder as the file path, the file path must end with a forward slash (/).
Click OK.
Cloud Phone does not provide the file download progress or status. You can go to the OSS console and find the desired OSS bucket to check whether the file download task is successful.
Run remote commands
You can send remote commands to a cloud phone from the Cloud Phone console to perform routine O&M operations, without the need to log on to the cloud phone. The following section describes how to send commands to a cloud phone from the Cloud Phone console.
Prerequisites
Before you send remote commands to a cloud phone, make sure that the cloud phone is in the Available state.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone, click the
icon, and then click Remote Command in the Actions column. You can also select multiple cloud phones and choose More > Remote Command in the lower part of the page.
In the Remote Command panel, enter a Shell command in the Command Content field. In this example, the ls command is used.
Click Execute to run the Shell command.
In the Command Output field, view the command execution result.
Initialize OSs
Prerequisites
Before you initialize the OS of a cloud phone, make sure that the cloud phone is in one of the following states: Available, Stopped, Abnormal, Backup failure, and Restoration failure.
Procedure
Log on to the Cloud Phone console.
In the left-side navigation pane, click Instance Group.
On the Instance Group page, click the ID of the instance group to which the desired cloud phone belongs to go to the Instance page.
Find the desired cloud phone and click Initialize System in the Actions column. You can also select multiple cloud phones and choose More > Initialize System in the lower part of the page.
