ECS Backup Procedure
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the row containing the target ECS and choose More > Manage Image/Backup > Create Server Backup in the Operation column.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the ECS to be associated. The storage capacity used by the backup increases accordingly.
-ECS Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Server Backup in the Operation column.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the ECS to be associated. The storage capacity used by the backup increases accordingly.
- If the ECS is not associated with a vault, buy a vault first and then configure the backup information as prompted.
For details, see Creating a Server Backup Vault.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Click OK. The system automatically creates a backup for the ECS.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
@@ -14,7 +14,7 @@After the backup is complete, you can restore server data or create images on the Backups tab page. For details, see Restoring from a Cloud Server Backup and Using a Backup to Create an Image.
EVS Disk Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the row containing the target ECS and choose More > Manage Image/Backup > Create Disk Backup in the Operation column.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default. Click
to view the disks attached to the ECSs. Select the disks to be backed up. - Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the disks to be associated. The storage capacity used by the backup increases accordingly.
-EVS Disk Backup Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- In the ECS list, locate the target ECS and choose More > Manage Image/Backup > Create Disk Backup in the Operation column.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Server List: The ECS to be backed up is selected by default. Click to view the disks attached to the ECSs. Select the disks to be backed up.
- Name: Customize your backup name.
- Description: Supplementary information about the backup.
- Full Backup: If this option is selected, the system will perform full backup for the disks to be associated. The storage capacity used by the backup increases accordingly.
- Server List: The ECS to be backed up is selected by default. Click
- If the ECS is not associated with a vault, buy a vault first and then configure the backup information as prompted.
For details, see Creating a Disk Backup Vault.
- If the ECS has been associated with a vault, configure the backup information as prompted.
- Click OK. The system automatically creates a backup for the disk.
On the Backups tab page, if the status of the backup is Available, the backup task is successful.
diff --git a/docs/ecs/umn/en-us_topic_0013771092.html b/docs/ecs/umn/en-us_topic_0013771092.html index 9a1803b73..e77d1f5fc 100644 --- a/docs/ecs/umn/en-us_topic_0013771092.html +++ b/docs/ecs/umn/en-us_topic_0013771092.html @@ -8,7 +8,7 @@- On the page providing details about the ECS, view the ECS specifications.Figure 1 Viewing ECS specifications
- Check the specifications tables in ECS Types for the virtualization type.
- On the page providing details about the ECS, view the ECS specifications.
Notes
- Downgrading ECS specifications (vCPU or memory) will reduce performance.
- Certain ECS types do not support specifications modification currently. For details about available ECS types as well as their functions and usage, see "Notes" in ECS Types.
- When the disk status is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.
- Before modifying the specifications of a Windows ECS, modify the SAN policy by following the instructions provided in Why Does a Disk Attached to a Windows ECS Go Offline? to prevent disks from going offline after the specifications are modified.
- Before modifying specifications, make sure that the ECS has been stopped.
Notes
- Downgrading ECS specifications (vCPU or memory) will reduce performance.
- Certain ECS types do not support specifications modification currently. For details about available ECS types as well as their functions and usage, see "NOTE" in ECS Types.
- When the disk status is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.
- Before modifying the specifications of a Windows ECS, modify the SAN policy by following the instructions provided in Why Does a Disk Attached to a Windows ECS Go Offline? to prevent disks from going offline after the specifications are modified.
- Before modifying specifications, make sure that the ECS has been stopped.
Step 1: Modify Specifications
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, view the status of the target ECS.
If the ECS is not in Stopped state, click More in the Operation column and select Stop.
- Click More in the Operation column and select Modify Specifications.
The Modify ECS Specifications page is displayed.
diff --git a/docs/ecs/umn/en-us_topic_0017955633.html b/docs/ecs/umn/en-us_topic_0017955633.html index 6f60ce6d3..6cc5741f3 100644 --- a/docs/ecs/umn/en-us_topic_0017955633.html +++ b/docs/ecs/umn/en-us_topic_0017955633.html @@ -36,7 +36,7 @@
Logging In to a Linux ECS from a Local Linux Server
To log in to a Linux ECS from a local Linux server, perform the operations below.
- On the Linux CLI, run the following command to log in to the ECS:
-
xx.xx.xx.xx indicates the EIP bound to the ECS.
+ xx.xx.xx.xx indicates the EIP bound to the ECS.
- Verify the SSH fingerprint of the ECS and enter yes.
The authenticity of host 'xx.xx.xx.xx (xx.xx.xx.xx)' can't be established. ECDSA key fingerprint is SHA256:rnKuzrUSYS03MCoaxxxxxxxxxxxxxxxxxxxxxxxxxxx. diff --git a/docs/ecs/umn/en-us_topic_0018073215.html b/docs/ecs/umn/en-us_topic_0018073215.html index 64183fc6b..8925f3419 100644 --- a/docs/ecs/umn/en-us_topic_0018073215.html +++ b/docs/ecs/umn/en-us_topic_0018073215.html @@ -20,7 +20,7 @@
59
VBD disks + SCSI disks ≤ 60 (This constraint does not apply to local disks.)
-The number of local disks is determined based on the ECS flavor.
+The number of local disks is determined based on the ECS flavor.
D2
@@ -30,7 +30,7 @@30
VBD disks + SCSI disks ≤ 54 (This constraint does not apply to local disks.)
-The number of local disks is determined based on the ECS flavor.
+The number of local disks is determined based on the ECS flavor.
-Prerequisites
- The target ECS is stopped.
- The target ECS has a system disk attached.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
Only stopped ECSs support OS reinstallation. If the ECS is not stopped, stop it before proceeding with reinstallation.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Reinstall OS in the Operation column.
Only stopped ECSs support OS reinstallation. If the ECS is not stopped, stop it before proceeding with reinstallation.
- (Optional) Select the Encryption option to encrypt the system disk during OS reinstallation.
To enable encryption, click Create Xrole to assign KMS access permissions to EVS. If you have rights granting permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights to assign the KMS access permissions. For details, see Can All Users Use the Encryption Feature?
Encryption parameters are as follows:
- Encryption: indicates that the EVS disk has been encrypted.
- Create Xrole: assigns KMS access permissions to EVS to obtain KMS keys. After the permissions are assigned, follow-up operations do not require assigning permissions again.
- Xrole Name: EVSAccessKMS: specifies that permissions have been assigned to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
- KMS Key Name: specifies the name of the key used by the encrypted EVS disk. You can select an existing key, or click Create KMS Key and create a new one on the KMS console. The default value is evs/default.
- KMS Key ID: specifies the ID of the key used by the encrypted data disk.
- Run the following command to check whether SNAT has been configured:
SNAT has been configured if information similar to Figure 2 is displayed.
- - Add a route.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Network, click Virtual Private Cloud.
- Choose Route Tables in the left navigation pane. In the route table list, click a target route table. On the displayed page, click Add Route.
- Set route information on the displayed page.
- Destination: indicates the destination network segment. The default value is 0.0.0.0/0.
- Next Hop: indicates the private IP address of the proxy ECS.
You can obtain the private IP address of the ECS on the Elastic Cloud Server page.
+ - Add a route.
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Network, click Virtual Private Cloud.
- Choose Route Tables in the left navigation pane. In the route table list, click a target route table. On the displayed page, click Add Route.
- Set route information on the displayed page.
- Destination: indicates the destination network segment. The default value is 0.0.0.0/0.
- Next Hop: indicates the private IP address of the proxy ECS.
You can obtain the private IP address of the ECS on the Elastic Cloud Server page.
- To delete the added iptables rules, run the following command:
iptables -t nat -D POSTROUTING -o eth0 -s subnet/netmask-bits -j SNAT --to nat-instance-ip
diff --git a/docs/ecs/umn/en-us_topic_0030878383.html b/docs/ecs/umn/en-us_topic_0030878383.html index 3d32cd296..95aa529d5 100644 --- a/docs/ecs/umn/en-us_topic_0030878383.html +++ b/docs/ecs/umn/en-us_topic_0030878383.html @@ -10,9 +10,9 @@ - Configure required parameters.
You can click + to add more inbound rules.
Figure 1 Add Inbound Rule-
Table 1 Inbound rule parameter description Parameter
+Table 1 Inbound rule parameter description Parameter
Description
+Description
Example Value
Source
Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. For example:- IP address:
- Single IP address: 192.168.10.10/32
- All IP addresses: 0.0.0.0/0
- IP address range: 192.168.1.0/24
- Security group: sg-A
- IP address:
- Single IP address: 192.168.10.10/32
- All IP addresses: 0.0.0.0/0
- IP address range: 192.168.1.0/24
- Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
- IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
If the source is a security group, this rule will apply to all instances associated with the selected security group.
- Configure required parameters.
You can click + to add more outbound rules.
Figure 2 Add Outbound Rule-
Table 2 Outbound rule parameter description Parameter
+Table 2 Outbound rule parameter description Parameter
Description
+Description
Example Value
Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example:
- IP address:
- Single IP address: 192.168.10.10/32
- All IP addresses: 0.0.0.0/0
- IP address range: 192.168.1.0/24
- Security group: sg-A
- Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
- IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
0.0.0.0/0
If the OS running on an ECS cannot meet service requirements, change the ECS OS.
The cloud platform supports changing between image types (public images, private images, and shared images) and between OSs. You can change your OS by changing your ECS image.
--Constraints
- The EVS disk quota must be greater than 0.
- For details about the change between different OSs, see Notes on Change Between Windows and Linux.
- If an ECS OS is to be changed using a full-ECS image, the ECS system disk can be encrypted.
Constraints
- The OS change takes about 10 to 20 minutes During this process, the ECS status is Changing OS.
- Do not perform any operations on the ECS before the system injects the password or key pair. Otherwise, the login will fail.
- The ECS for which you want to change the OS must be in any of the following states: Stopped, Reinstallation failed, or Failed to change the OS.
- The target ECS must have a system disk attached.
- The EVS disk quota must be greater than 0.
- The system disk type cannot be changed.
- The system disk can be encrypted.
- For details about the change between different OSs, see Notes on Change Between Windows and Linux.
- If an ECS OS is to be changed using a full-ECS image, the ECS system disk can be encrypted.
Notes
- After the OS is changed, the original OS is not retained, and the original system disk is deleted, including the data in all partitions of the system disk.
- Back up data before changing the OS.
- Changing the OS does not affect data in data disks.
- After the OS is changed, your service running environment must be deployed in the new OS again.
- After the OS is changed, the ECS will be automatically started.
- After the OS is changed, the system disk type of the ECS cannot be changed.
- After the OS is changed, the IP and MAC addresses of the ECS remain unchanged.
- After the OS is changed, customized configurations, such as DNS and hostname of the original OS will be reset and require reconfiguration.
- It takes about 10 to 20 minutes to change the OS. During this process, the ECS is in Changing OS state.
- Do not perform any operations on the ECS immediately after its OS is changed. Wait for several minutes until the system successfully injects the password or key. Otherwise, the injection may fail, and the ECS cannot be logged in to.
- After the OS is changed, the password for logging in to the ECS is reset. To retrieve the password, perform the following operations:
- For a Linux ECS, log in to it using the key and set a new password. For instructions about how to log in to an ECS using a key pair, see Login Using an SSH Key.
- For a Windows ECS, retrieve the password by following the instructions provided in Obtaining the Password for Logging In to a Windows ECS.
Prerequisites
- The target ECS is stopped.
- The target ECS has a system disk attached.
- Necessary data has been backed up. (Changing the OS clears the data in all partitions of the system disk, including the system partition.)
- If the original ECS uses password authentication while the new ECS uses key pair authentication, ensure that a key pair is available.
- If you plan to use a private image to change the OS, ensure that a private image is available. For details about how to create a private image, see Image Management Service User Guide.
- If the image of a specified ECS is required, make sure that a private image has been created using this ECS.
- If a local image file is required, make sure that the image file has been imported to the cloud platform and registered as a private image.
- If a private image from another region is required, make sure that the image has been copied.
- If a private image from another user account is required, make sure that the image has been shared with you.
-Prerequisites
- The data is backed up. +
- If you want to change the login authentication mode from password to key pair during the OS change, create a key file in advance.
For details, see (Recommended) Creating a Key Pair on the Management Console.
+ - If you plan to use a private image to change the OS, ensure that a private image is available. For details about how to create a private image, see Image Management Service User Guide.
- If the image of a specified ECS is required, make sure that a private image has been created using this ECS.
- If a local image file is required, make sure that the image file has been imported to the cloud platform and registered as a private image.
- If a private image from another region is required, make sure that the image has been copied.
- If a private image from another user account is required, make sure that the image has been shared with you.
Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Change OS in the Operation column.
Only stopped ECSs support OS change. If the ECS is not stopped, stop it before proceeding with changing.
- - Modify related ECS parameters, such as Image Type and Image, based on service requirements.
For more details, see Creating an ECS.
+-Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, choose Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Change OS in the Operation column.
Only stopped ECSs support OS change. If the ECS is not stopped, stop it before proceeding with changing.
+ - Select the target image.
For more details, see Creating an ECS.
Figure 1 OS Change
- (Optional) Select the Encryption option to encrypt the system disk during OS change.
To enable encryption, click Create Xrole to assign KMS access permissions to EVS. If you have rights granting permission, assign the KMS access permissions to EVS. If you do not have the permission, contact the user having the security administrator rights to assign the KMS access permissions. For details, see Can All Users Use the Encryption Feature?
Encryption parameters are as follows:
@@ -28,7 +30,7 @@ - (Optional) Select a License Type (Use license from the system or Bring your own license (BYOL)) if the changed OS running on your ECS is billed. For more details, see License Types.The following OSs are billed:
- SUSE Linux Enterprise Server
- Oracle Enterprise Linux
- Red Hat Enterprise Linux
- Configure the login mode.
If the target ECS uses key pair authentication, you can replace the original key pair.
- - Click OK.
- On the Change ECS OS page, confirm the specifications, and click Submit.
After the application is submitted, the status Changing OS is displayed. When this status disappears, the OS change is complete.
+ - Click OK.
- On the Change ECS OS page, confirm the specifications, and click Submit.
After the application is submitted, the status Changing OS is displayed. When this status disappears, the OS change is complete.
A temporary ECS is created during the OS change process. After the process is complete, this ECS will be automatically deleted.
After the ECS is created, start it and run the cat [file] command to check the script execution result.
[root@XXXXXXXX ~]# cat /root/output.txt Hello, the time is now Mon, 16 Jul 2016 16:03:18+0800
-Example 2: Inject a Cloud-Config data script.
+Example 2: Inject a Cloud-Config data script.
When creating an ECS, set User Data to As text and enter the customized user data script.
#cloud-config bootcmd: @@ -229,7 +229,7 @@ yum update -y service httpd start chkconfig httpd on
Case 6
This case illustrates how to use the user data passing function to assign user root permission for remotely logging in to a Linux ECS. After passing the file to an ECS, you can log in to the ECS as user root using SSH key pair authentication.
+Case 6
This case illustrates how to use the user data passing function to assign user root permissions for remotely logging in to a Linux ECS. After passing the file to an ECS, you can log in to the ECS as user root using SSH key pair authentication.
User data example:
#cloud-config disable_root: false diff --git a/docs/ecs/umn/en-us_topic_0035470096.html b/docs/ecs/umn/en-us_topic_0035470096.html index f57559302..5071167e5 100644 --- a/docs/ecs/umn/en-us_topic_0035470096.html +++ b/docs/ecs/umn/en-us_topic_0035470096.html @@ -17,7 +17,7 @@
Network QoS
Network QoS uses basic technologies to improve the quality of network communication. A network with QoS enabled offers predictable network performance and effectively allocates network bandwidth to use network resources.
To obtain the QoS data of an ECS flavor, including the maximum bandwidth, assured bandwidth, maximum intranet PPS, and NIC multi-queue, see A Summary List of ECS Specifications.
The intranet bandwidth and PPS of an ECS are determined by the ECS flavor.- Assured intranet bandwidth: indicates the guaranteed bandwidth allocated to an ECS when there is a network bandwidth contention in the entire network.
- Maximum intranet bandwidth: indicates the maximum bandwidth that can be allocated to an ECS when the ECS does not compete for network bandwidth (other ECSs on the host do not have high requirements on network bandwidth).
- Maximum intranet PPS: indicates the maximum ECS capability in sending and receiving packets.
PPS: packets per second, indicates the number of packets sent per second. It is usually used to measure the network performance.
- - NIC multi-queues: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth
- Maximum NICs: indicates the maximum number of NICs that can be attached to an ECS. diff --git a/docs/ecs/umn/en-us_topic_0035470101.html b/docs/ecs/umn/en-us_topic_0035470101.html index d13a3b4b3..e14a45188 100644 --- a/docs/ecs/umn/en-us_topic_0035470101.html +++ b/docs/ecs/umn/en-us_topic_0035470101.html @@ -10,874 +10,874 @@
- For instructions about how to test PPS, see How Can I Test Network Performance?
- For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
- NIC multi-queues: allocates NIC interrupt requests to multiple vCPUs for higher PPS performance and bandwidth
- Maximum NICs: indicates the maximum number of NICs that can be attached to an ECS.
- For instructions about how to test PPS, see How Can I Test Network Performance?
- For instructions about how to enable NIC multi-queue, see Enabling NIC Multi-Queue.
- The maximum bandwidth is the total bandwidth allocated to an ECS. If an ECS has multiple NICs, the sum of the maximum bandwidths allocated to all NICs cannot exceed the maximum bandwidth allocated to the ECS.
Specifications
-Table 1 S3 ECS specifications Flavor
+-Table 1 S3 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
s3.medium.1
+s3.medium.1
1
+1
1
+1
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
CPU: Intel® Xeon® Cascade Lake 6278
+CPU: Intel® Xeon® Cascade Lake 6278
s3.large.1
+s3.large.1
2
+2
2
+2
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.1
+s3.xlarge.1
4
+4
4
+4
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.1
+s3.2xlarge.1
8
+8
8
+8
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.1
+s3.4xlarge.1
16
+16
16
+16
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.1
+s3.8xlarge.1
32
+32
32
+32
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
s3.medium.2
+s3.medium.2
1
+1
2
+2
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
s3.large.2
+s3.large.2
2
+2
4
+4
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.2
+s3.xlarge.2
4
+4
8
+8
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.2
+s3.2xlarge.2
8
+8
16
+16
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.2
+s3.4xlarge.2
16
+16
32
+32
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.2
+s3.8xlarge.2
32
+32
64
+64
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
s3.medium.4
+s3.medium.4
1
+1
4
+4
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
s3.large.4
+s3.large.4
2
+2
8
+8
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.4
+s3.xlarge.4
4
+4
16
+16
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.4
+s3.2xlarge.4
8
+8
32
+32
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.4
+s3.4xlarge.4
16
+16
64
+64
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.4
+s3.8xlarge.4
32
+32
128
+128
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
s3.medium.8
+s3.medium.8
1
+1
8
+8
0.8/0.15
+0.8/0.15
10
+10
1
+1
2
+2
KVM
+KVM
s3.large.8
+s3.large.8
2
+2
16
+16
1.5/0.3
+1.5/0.3
15
+15
1
+1
2
+2
KVM
+KVM
s3.xlarge.8
+s3.xlarge.8
4
+4
32
+32
2/0.5
+2/0.5
25
+25
1
+1
2
+2
KVM
+KVM
s3.2xlarge.8
+s3.2xlarge.8
8
+8
64
+64
3/1
+3/1
50
+50
2
+2
2
+2
KVM
+KVM
s3.4xlarge.8
+s3.4xlarge.8
16
+16
128
+128
6/2
+6/2
100
+100
4
+4
2
+2
KVM
+KVM
s3.8xlarge.8
+s3.8xlarge.8
32
+32
256
+256
8/2
+8/2
200
+200
8
+8
4
+4
KVM
+KVM
Table 2 S2 ECS specifications Flavor
+Table 2 S2 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
s2.medium.1
+s2.medium.1
1
+1
1
+1
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
CPU: Intel® Xeon® Skylake 6161
+CPU: Intel® Xeon® Skylake 6161
s2.large.1
+s2.large.1
2
+2
2
+2
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.1
+s2.xlarge.1
4
+4
4
+4
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.1
+s2.2xlarge.1
8
+8
8
+8
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.1
+s2.4xlarge.1
16
+16
16
+16
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.1
+s2.8xlarge.1
32
+32
32
+32
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
s2.medium.2
+s2.medium.2
1
+1
2
+2
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
s2.large.2
+s2.large.2
2
+2
4
+4
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.2
+s2.xlarge.2
4
+4
8
+8
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.2
+s2.2xlarge.2
8
+8
16
+16
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.2
+s2.4xlarge.2
16
+16
32
+32
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.2
+s2.8xlarge.2
32
+32
64
+64
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
s2.medium.4
+s2.medium.4
1
+1
4
+4
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
s2.large.4
+s2.large.4
2
+2
8
+8
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.4
+s2.xlarge.4
4
+4
16
+16
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.4
+s2.2xlarge.4
8
+8
32
+32
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.4
+s2.4xlarge.4
16
+16
64
+64
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.4
+s2.8xlarge.4
32
+32
128
+128
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
s2.medium.8
+s2.medium.8
1
+1
8
+8
0.5/0.1
+0.5/0.1
5
+5
1
+1
12
+12
KVM
+KVM
s2.large.8
+s2.large.8
2
+2
16
+16
0.8/0.2
+0.8/0.2
10
+10
1
+1
12
+12
KVM
+KVM
s2.xlarge.8
+s2.xlarge.8
4
+4
32
+32
1.5/0.4
+1.5/0.4
15
+15
1
+1
12
+12
KVM
+KVM
s2.2xlarge.8
+s2.2xlarge.8
8
+8
64
+64
3/0.8
+3/0.8
20
+20
2
+2
12
+12
KVM
+KVM
s2.4xlarge.8
+s2.4xlarge.8
16
+16
128
+128
4/1.5
+4/1.5
30
+30
4
+4
12
+12
KVM
+KVM
s2.8xlarge.8
+s2.8xlarge.8
32
+32
256
+256
6/3
+6/3
50
+50
8
+8
12
+12
KVM
+KVM
Overview
- M4 ECSs use the second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable computing performance. Using 25GE high-speed intelligent NICs, M4 ECSs provide a maximum memory size of 512 GiB based on DDR4 for memory-intensive applications with high requirements on network bandwidth and Packets Per Second (PPS).
- M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in the memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing mechanism to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive computing applications.
- M2 ECSs use Intel Xeon E5-2690 v4 CPUs and are designed for memory-optimized applications.
Specifications
-Table 1 M4 ECS specifications Flavor
+-Table 1 M4 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
m4.large.8
+m4.large.8
2
+2
16
+16
4/1.2
+4/1.2
40
+40
2
+2
2
+2
KVM
+KVM
CPU: Intel® Xeon® Cascade Lake 6266
+CPU: Intel® Xeon® Cascade Lake 6266
m4.xlarge.8
+m4.xlarge.8
4
+4
32
+32
8/2.4
+8/2.4
80
+80
2
+2
3
+3
KVM
+KVM
m4.2xlarge.8
+m4.2xlarge.8
8
+8
64
+64
15/4.5
+15/4.5
150
+150
4
+4
4
+4
KVM
+KVM
m4.3xlarge.8
+m4.3xlarge.8
12
+12
96
+96
17/7
+17/7
200
+200
4
+4
6
+6
KVM
+KVM
m4.4xlarge.8
+m4.4xlarge.8
16
+16
128
+128
20/9
+20/9
280
+280
8
+8
8
+8
KVM
+KVM
m4.6xlarge.8
+m4.6xlarge.8
24
+24
192
+192
25/14
+25/14
400
+400
8
+8
8
+8
KVM
+KVM
m4.8xlarge.8
+m4.8xlarge.8
32
+32
256
+256
30/18
+30/18
550
+550
16
+16
8
+8
KVM
+KVM
m4.16xlarge.8
+m4.16xlarge.8
64
+64
512
+512
40/36
+40/36
1,000
+1,000
32
+32
8
+8
KVM
+KVM
m4.2xlarge.16
+m4.2xlarge.16
8
+8
128
+128
15/4.5
+15/4.5
150
+150
4
+4
4
+4
KVM
+KVM
m4.2xlarge.32
+m4.2xlarge.32
8
+8
256
+256
15/4.5
+15/4.5
150
+150
4
+4
4
+4
KVM
+KVM
Table 2 M3 ECS specifications Flavor
+-Table 2 M3 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
m3.large.8
+m3.large.8
2
+2
16
+16
1.5/0.6
+1.5/0.6
30
+30
2
+2
12
+12
KVM
+KVM
CPU: Intel® Xeon® Skylake 6151
+CPU: Intel® Xeon® Skylake 6151
m3.xlarge.8
+m3.xlarge.8
4
+4
32
+32
3/1.1
+3/1.1
50
+50
2
+2
12
+12
KVM
+KVM
m3.2xlarge.8
+m3.2xlarge.8
8
+8
64
+64
5/2
+5/2
90
+90
4
+4
12
+12
KVM
+KVM
m3.4xlarge.8
+m3.4xlarge.8
16
+16
128
+128
10/4.5
+10/4.5
130
+130
4
+4
12
+12
KVM
+KVM
m3.8xlarge.8
+m3.8xlarge.8
32
+32
256
+256
15/9
+15/9
260
+260
8
+8
12
+12
KVM
+KVM
m3.15xlarge.8
+m3.15xlarge.8
60
+60
512
+512
17/17
+17/17
500
+500
16
+16
12
+12
KVM
+KVM
Table 3 M2 ECS specifications Flavor
+Table 3 M2 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Virtualization
+Virtualization
Hardware
+Hardware
m2.4xlarge.8
+m2.4xlarge.8
16
+16
128
+128
8/5
+8/5
40
+40
4
+4
KVM
+KVM
CPU: Intel® Xeon® Processor E5-2690 v4
+CPU: Intel® Xeon® Processor E5-2690 v4
m2.8xlarge.8
+m2.8xlarge.8
32
+32
256
+256
13/8
+13/8
60
+60
8
+8
KVM
+KVM
2023-10-31
+2023-12-18
+Modified the following content:
+- Added G7v ECSs in GPU-accelerated ECSs.
2023-10-31
Modified the following content:
- Added C7t ECSs in Dedicated General-Purpose ECSs.
Dedicated General-Purpose ECSs
-Overview
C7t ECSs support encryption using Intel® SGX to protect the confidentiality and integrity of key code and data from being damaged by malware. Based on the TPM/TCM chip, the boot chain from the underlying server hardware to the guest OS can be measured and verified to implement trusted boot.
+-Overview
+C7t ECSs support encryption using Intel® SGX to protect the confidentiality and integrity of key code and data from being damaged by malware. Based on the TPM/TCM chip, the boot chain from the underlying server hardware to the guest OS can be measured and verified to implement trusted boot.
C4 ECSs use second-generation Intel® Xeon® Scalable processors to provide powerful and stable computing performance. By using 25GE high-speed intelligent NICs, C4 ECSs offer ultra-high network bandwidth and PPS.
C3 ECSs use Intel® Xeon® Scalable processors, KVM virtualization, Data Plane Development Kit (DPDK) rapid packet processing mechanism, and high-performance NICs to deliver high and stable computing performance for enterprise-grade applications.
Scenarios
- C7t ECSs are suitable for:
- Scenarios involving sensitive information such as personal identity information and healthcare, financial, and intellectual property data
- Confidential data sharing in multi-party computation
- Blockchain
- Confidential machine learning
- Scenarios with high security and trustworthy requirements, such as finance, government, and enterprises
- Enterprise-class applications of various types and scales
Scenarios
- C7t ECSs are suitable for:
- Scenarios involving sensitive information such as personal identity information and healthcare, financial, and intellectual property data
- Confidential data sharing in multi-party computation
- Blockchain
- Confidential machine learning
- Scenarios with high security and trustworthy requirements, such as finance, government, and enterprises
- Enterprise-class applications of various types and scales
- C4 ECSs are suitable for:
- Websites and web applications that require high computing and network performance
- General databases
- Cache servers
- Medium- and heavy-load enterprise applications
- C3 ECSs are suitable for:
- Small- and medium-sized databases, cache clusters, and search clusters with high requirements on stability
- Enterprise-class applications of various types and scales
Specifications
-Table 1 C7t ECS specifications Flavor
+-Table 1 C7t ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
c7t.28xlarge.4.physical
+c7t.28xlarge.4.physical
112
+112
512
+512
64/64
+64/64
3000
+3000
32
+32
32
+32
BMS
+BMS
Table 2 C4 ECS specifications Flavor
+-Table 2 C4 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
c4.large.2
+c4.large.2
2
+2
4
+4
4/1.2
+4/1.2
40
+40
2
+2
2
+2
KVM
+KVM
CPU: Intel® Xeon® Cascade Lake 6266
+CPU: Intel® Xeon® Cascade Lake 6266
c4.xlarge.2
+c4.xlarge.2
4
+4
8
+8
8/2.4
+8/2.4
80
+80
2
+2
3
+3
KVM
+KVM
c4.2xlarge.2
+c4.2xlarge.2
8
+8
16
+16
15/4.5
+15/4.5
150
+150
4
+4
4
+4
KVM
+KVM
c4.3xlarge.2
+c4.3xlarge.2
12
+12
24
+24
17/7
+17/7
200
+200
4
+4
6
+6
KVM
+KVM
c4.4xlarge.2
+c4.4xlarge.2
16
+16
32
+32
20/9
+20/9
280
+280
8
+8
8
+8
KVM
+KVM
c4.6xlarge.2
+c4.6xlarge.2
24
+24
48
+48
25/14
+25/14
400
+400
8
+8
8
+8
KVM
+KVM
c4.8xlarge.2
+c4.8xlarge.2
32
+32
64
+64
30/18
+30/18
550
+550
16
+16
8
+8
KVM
+KVM
c4.16xlarge.2
+c4.16xlarge.2
64
+64
128
+128
40/36
+40/36
1000
+1000
32
+32
8
+8
KVM
+KVM
c4.large.4
+c4.large.4
2
+2
8
+8
4/1.2
+4/1.2
40
+40
2
+2
2
+2
KVM
+KVM
c4.xlarge.4
+c4.xlarge.4
4
+4
16
+16
8/2.4
+8/2.4
80
+80
2
+2
3
+3
KVM
+KVM
c4.2xlarge.4
+c4.2xlarge.4
8
+8
32
+32
15/4.5
+15/4.5
150
+150
4
+4
4
+4
KVM
+KVM
c4.3xlarge.4
+c4.3xlarge.4
12
+12
48
+48
17/7
+17/7
200
+200
4
+4
6
+6
KVM
+KVM
c4.4xlarge.4
+c4.4xlarge.4
16
+16
64
+64
20/9
+20/9
280
+280
8
+8
8
+8
KVM
+KVM
c4.6xlarge.4
+c4.6xlarge.4
24
+24
96
+96
25/14
+25/14
400
+400
8
+8
8
+8
KVM
+KVM
c4.8xlarge.4
+c4.8xlarge.4
32
+32
128
+128
30/18
+30/18
550
+550
16
+16
8
+8
KVM
+KVM
c4.16xlarge.4
+c4.16xlarge.4
64
+64
256
+256
40/36
+40/36
1000
+1000
32
+32
8
+8
KVM
+KVM
Table 3 C3 ECS specifications Flavor
+Table 3 C3 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
Virtualization
+Virtualization
Hardware
+Hardware
c3.large.2
+c3.large.2
2
+2
4
+4
1.5/0.6
+1.5/0.6
30
+30
2
+2
12
+12
KVM
+KVM
CPU: Intel® Xeon® Skylake 6151
+CPU: Intel® Xeon® Skylake 6151
c3.xlarge.2
+c3.xlarge.2
4
+4
8
+8
3/1
+3/1
50
+50
2
+2
12
+12
KVM
+KVM
c3.2xlarge.2
+c3.2xlarge.2
8
+8
16
+16
5/2
+5/2
90
+90
4
+4
12
+12
KVM
+KVM
c3.4xlarge.2
+c3.4xlarge.2
16
+16
32
+32
10/4
+10/4
130
+130
4
+4
12
+12
KVM
+KVM
c3.8xlarge.2
+c3.8xlarge.2
32
+32
64
+64
15/8
+15/8
260
+260
8
+8
12
+12
KVM
+KVM
c3.15xlarge.2
+c3.15xlarge.2
60
+60
128
+128
17/16
+17/16
500
+500
16
+16
12
+12
KVM
+KVM
c3.large.4
+c3.large.4
2
+2
8
+8
1.5/0.6
+1.5/0.6
30
+30
2
+2
12
+12
KVM
+KVM
c3.xlarge.4
+c3.xlarge.4
4
+4
16
+16
3/1
+3/1
50
+50
2
+2
12
+12
KVM
+KVM
c3.2xlarge.4
+c3.2xlarge.4
8
+8
32
+32
5/2
+5/2
90
+90
4
+4
12
+12
KVM
+KVM
c3.4xlarge.4
+c3.4xlarge.4
16
+16
64
+64
10/4
+10/4
130
+130
4
+4
12
+12
KVM
+KVM
c3.8xlarge.4
+c3.8xlarge.4
32
+32
128
+128
15/8
+15/8
260
+260
8
+8
12
+12
KVM
+KVM
c3.15xlarge.4
+c3.15xlarge.4
60
+60
256
+256
16/16
+16/16
500
+500
16
+16
12
+12
KVM
+KVM
+GPU-accelerated ECS Types
Recommended: Computing-accelerated P2s, Inference-accelerated Pi2, and Graphics-accelerated Enhancement G6
Available now: All GPU models except the recommended ones. If available ECSs are sold out, use the recommended ones.
-- G series +
Graphics-accelerated Enhancement G7v
Overview
+G7v ECSs use NVIDIA A40 GPUs and support DirectX, Shader Model, OpenGL, and Vulkan. Each GPU provides 48 GiB of GPU memory. Theoretically, G7v ECSs can provide 37.4 TFLOPS of FP32 peak performance and 74.8 TFLOPS (sparsity disabled) or 149.6 TFLOPS (sparsity enabled) of TF32 peak tensor performance. They deliver two times the rendering performance and 1.4 times the graphics processing performance of RTX6000 GPUs to meet professional graphics processing requirements.
+Select your desired GPU-accelerated ECS type and specifications.
+Specifications
+ ++
+Table 1 G7v ECS specifications Flavor
+vCPUs
+Memory
+(GiB)
+Max./Assured Bandwidth
+(Gbit/s)
+Max. PPS
+(10,000)
+Max. NIC Queues
+Max. NICs
+GPUs
+GPU Memory
+(GiB)
+Virtualization
+g7v.2xlarge.8
+8
+64
+15/3
+100
+4
+4
+1 × NVIDIA-A40-8Q
+8
+KVM
+g7v.4xlarge.8
+16
+128
+20/6
+150
+8
+8
+1 × NVIDIA-A40-16Q
+16
+KVM
+g7v.6xlarge.8
+24
+192
+25/9
+200
+8
+8
+1 × NVIDIA-A40-24Q
+24
+KVM
+G7v ECS Features
+- CPU: 3rd Generation Intel® Xeon® Scalable 6348 processors (3.0 GHz of base frequency and 3.5 GHz of turbo frequency)
- Graphics acceleration APIs
- DirectX 12.07, Direct2D, DirectX Video Acceleration (DXVA)
- Shader Model 5.17
- OpenGL 4.68
- Vulkan 1.18
- CUDA, DirectCompute, OpenACC, and OpenCL
- A single card is equipped with 10,752 CUDA cores, 84 second-generation RT cores, and 336 third-generation Tensor cores.
- Graphics applications accelerated
- Heavy-load CPU inference
- Application flow identical to common ECSs
- Automatic scheduling of G7v ECSs to AZs where NVIDIA A40 GPUs are used
- One NVENC (encoding) engine and two NVDEC (decoding) engines (including AV1 decoding) embedded
Supported Common Software
+G7v ECSs are used in graphics acceleration scenarios, such as video rendering, cloud desktop, and 3D visualization. If the software relies on GPU DirectX and OpenGL hardware acceleration, use G7v ECSs. G7v ECSs support the following commonly used graphics processing software:
+- AutoCAD
- 3DS MAX
- MAYA
- Agisoft PhotoScan
- ContextCapture
- Adobe Premiere Pro
- Solidworks
- Unreal Engine
- Blender
- Vray
Notes
+- G7v ECSs support the following OSs:
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- CentOS 8.2 64bit
- CentOS 7.6 64bit
- Ubuntu Server 20.04 64bit
- Ubuntu Server 18.04 64bit
- G7v ECSs created using a public image have had the GRID driver of a specific version installed by default. However, you need to purchase and configure a GRID license by yourself. Ensure that the GRID driver version meets service requirements.
- If a G7v ECS is created using a private image, make sure that the GRID driver was installed during the private image creation. If the GRID driver has not been installed, install the driver for graphics acceleration after the ECS is created.
Graphics-accelerated Enhancement G7
Overview
G7 ECSs use NVIDIA A40 GPUs and support DirectX, Shader Model, OpenGL, and Vulkan. Each GPU provides 48 GiB of GPU memory. Theoretically, G7 ECSs provide 37.4 TFLOPS of FP32 peak performance and 74.8 TFLOPS (sparsity disabled) or 149.6 TFLOPS (sparsity enabled) of TF32 peak tensor performance. They deliver two times the rendering performance and 1.4 times the graphics processing performance of RTX6000 GPUs to meet professional graphics processing requirements.
Select your desired GPU-accelerated ECS type and specifications.
Specifications
-Table 1 G7 ECS specifications Flavor
+Table 2 G7 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Virtualization
+Virtualization
g7.12xlarge.8
+g7.12xlarge.8
48
+48
384
+384
35/18
+35/18
750
+750
16
+16
8
+8
1 × NVIDIA-A40
+1 × NVIDIA-A40
1 × 48
+1 × 48
KVM
+KVM
g7.24xlarge.8
+g7.24xlarge.8
96
+96
768
+768
40/36
+40/36
850
+850
16
+16
8
+8
2 × NVIDIA-A40
+2 × NVIDIA-A40
2 × 48
+2 × 48
KVM
+KVM
Select your desired GPU-accelerated ECS type and specifications.
Specifications
-Table 2 G6 ECS specifications Flavor
+Table 3 G6 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Virtualization
+Virtualization
g6.4xlarge.4
+g6.4xlarge.4
16
+16
64
+64
25/15
+25/15
200
+200
8
+8
8
+8
1 × T4
+1 × T4
16
+16
KVM
+KVM
g6.10xlarge.7
+g6.10xlarge.7
40
+40
280
+280
25/15
+25/15
200
+200
16
+16
8
+8
1 × T4
+1 × T4
16
+16
KVM
+KVM
g6.20xlarge.7
+g6.20xlarge.7
80
+80
560
+560
30/30
+30/30
400
+400
32
+32
16
+16
2 × T4
+2 × T4
32
+32
KVM
+KVM
G6 ECSs are used in graphics acceleration scenarios, such as video rendering, cloud desktop, and 3D visualization. If the software relies on GPU DirectX and OpenGL hardware acceleration, use G6 ECSs. G6 ECSs support the following commonly used graphics processing software:
- AutoCAD
- 3DS MAX
- MAYA
- Agisoft PhotoScan
- ContextCapture
Notes
-- Table 3 lists the OSs supported by G6 ECSs.
-
Table 3 Supported OS versions OS
+- Table 4 lists the OSs supported by G6 ECSs.
+
Table 4 Supported OS versions OS
Version
+Version
EulerOS
+EulerOS
EulerOS 2.5 64bit
+EulerOS 2.5 64bit
Windows
+Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
P3 ECSs use NVIDIA A100 GPUs and provide flexibility and ultra-high-performance computing. P3 ECSs have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics. Theoretically, P3 ECSs provide 19.5 TFLOPS of FP32 single-precision performance and 156 TFLOPS (sparsity disabled) or 312 TFLOPS (sparsity enabled) of TF32 peak tensor performance.
Specifications
-Table 4 P3 ECS specifications Flavor
+Table 5 P3 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth (Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Virtualization
+Virtualization
p3.2xlarge.8
+p3.2xlarge.8
8
+8
64
+64
10/4
+10/4
100
+100
4
+4
4
+4
1 × NVIDIA A100 80GB
+1 × NVIDIA A100 80GB
80
+80
KVM
+KVM
p3.4xlarge.8
+p3.4xlarge.8
16
+16
128
+128
15/8
+15/8
200
+200
8
+8
8
+8
2 × NVIDIA A100 80GB
+2 × NVIDIA A100 80GB
160
+160
KVM
+KVM
p3.8xlarge.8
+p3.8xlarge.8
32
+32
256
+256
25/15
+25/15
350
+350
16
+16
8
+8
4 × NVIDIA A100 80GB
+4 × NVIDIA A100 80GB
320
+320
KVM
+KVM
p3.16xlarge.8
+p3.16xlarge.8
64
+64
512
+512
36/30
+36/30
700
+700
32
+32
8
+8
8 × NVIDIA A100 80GB
+8 × NVIDIA A100 80GB
640
+640
KVM
+KVM
Supported Common Software
P3 ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P3 ECSs. P3 ECSs support the following commonly used software:
- Common deep learning frameworks, such as TensorFlow, Spark, PyTorch, MXNet, and Caffee
- CUDA GPU rendering supported by RedShift for Autodesk 3dsMax and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
- More than 2,000 GPU-accelerated applications such as Amber, NAMD, and VASP
Notes
+Notes
- P3 ECSs support the following OSs:
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- CentOS 8.2 64bit
- CentOS 8.1 64bit
- CentOS 8.0 64bit
- CentOS 7.9 64bit
- CentOS 7.8 64bit
- CentOS 7.7 64bit
- CentOS 7.6 64bit
- If a P3 ECS is created using a private image, make sure that the Tesla driver has been installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS.
P2s ECSs use NVIDIA Tesla V100 GPUs to provide flexibility, high-performance computing, and cost-effectiveness. P2s ECSs provide outstanding general computing capabilities and have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics.
Specifications
-Table 5 P2s ECS specifications Flavor
+Table 6 P2s ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth (Gbit/s)
Max. PPS (10,000)
+Max. PPS (10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Connection
+GPU Connection
GPU Memory (GiB)
+GPU Memory (GiB)
Virtualization
+Virtualization
Hardware
+Hardware
p2s.2xlarge.8
+p2s.2xlarge.8
8
+8
64
+64
10/4
+10/4
50
+50
4
+4
4
+4
1 × V100
+1 × V100
PCIe Gen3
+PCIe Gen3
1 × 32 GiB
+1 × 32 GiB
KVM
+KVM
CPU: 2nd Generation Intel® Xeon® Scalable Processor 6278
+CPU: 2nd Generation Intel® Xeon® Scalable Processor 6278
p2s.4xlarge.8
+p2s.4xlarge.8
16
+16
128
+128
15/8
+15/8
100
+100
8
+8
8
+8
2 × V100
+2 × V100
PCIe Gen3
+PCIe Gen3
2 × 32 GiB
+2 × 32 GiB
KVM
+KVM
p2s.8xlarge.8
+p2s.8xlarge.8
32
+32
256
+256
25/15
+25/15
200
+200
16
+16
8
+8
4 × V100
+4 × V100
PCIe Gen3
+PCIe Gen3
4 × 32 GiB
+4 × 32 GiB
KVM
+KVM
p2s.16xlarge.8
+p2s.16xlarge.8
64
+64
512
+512
30/30
+30/30
400
+400
32
+32
8
+8
8 × V100
+8 × V100
PCIe Gen3
+PCIe Gen3
8 × 32 GiB
+8 × 32 GiB
KVM
+KVM
Supported Common Software
P2s ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P2s ECSs. P2s ECSs support the following commonly used software:-- Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- CUDA GPU rendering supported by RedShift for Autodesk 3dsMax and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
Notes- Table 6 lists the OSs supported by P2s ECSs.
-
Table 6 Supported OS versions OS
+Notes- Table 7 lists the OSs supported by P2s ECSs.
+
Table 7 Supported OS versions OS
Version
+Version
CentOS
+CentOS
CentOS 7.9 64bit
+CentOS 7.9 64bit
EulerOS
+EulerOS
EulerOS 2.5 64bit
+EulerOS 2.5 64bit
Oracle Linux
+Oracle Linux
Oracle Linux Server release 7.6 64bit
+Oracle Linux Server release 7.6 64bit
Ubuntu
+Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
+Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- By default, P2s ECSs created using a Windows public image have the Tesla driver installed.
- If a P2s ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS.
-Computing-accelerated P2v
Overview
+Computing-accelerated P2v
Overview
P2v ECSs use NVIDIA Tesla V100 GPUs and deliver high flexibility, high-performance computing, and high cost-effectiveness. These ECSs use GPU NVLink for direct communication between GPUs, improving data transmission efficiency. P2v ECSs provide outstanding general computing capabilities and have strengths in AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics.
Specifications
-Table 7 P2v ECS specifications Flavor
+Table 8 P2v ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth (Gbit/s)
+Max./Assured Bandwidth (Gbit/s)
Max. PPS (10,000)
+Max. PPS (10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Connection
+GPU Connection
GPU Memory
+GPU Memory
(GiB)
Virtualization
+Virtualization
Hardware
+Hardware
p2v.2xlarge.8
+p2v.2xlarge.8
8
+8
64
+64
10/4
+10/4
50
+50
4
+4
4
+4
1 × V100
+1 × V100
N/A
+N/A
1 × 16 GiB
+1 × 16 GiB
KVM
+KVM
CPU: Intel® Xeon® Skylake-SP Gold 6151 v5
+CPU: Intel® Xeon® Skylake-SP Gold 6151 v5
p2v.4xlarge.8
+p2v.4xlarge.8
16
+16
128
+128
15/8
+15/8
100
+100
8
+8
8
+8
2 × V100
+2 × V100
NVLink
+NVLink
2 × 16 GiB
+2 × 16 GiB
KVM
+KVM
p2v.8xlarge.8
+p2v.8xlarge.8
32
+32
256
+256
25/15
+25/15
200
+200
16
+16
8
+8
4 × V100
+4 × V100
NVLink
+NVLink
4 × 16 GiB
+4 × 16 GiB
KVM
+KVM
p2v.16xlarge.8
+p2v.16xlarge.8
64
+64
512
+512
30/30
+30/30
400
+400
32
+32
8
+8
8 × V100
+8 × V100
NVLink
+NVLink
8 × 16 GiB
+8 × 16 GiB
KVM
+KVM
Supported Common Software
P2v ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P2v ECSs. P2v ECSs support the following commonly used software:-- Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- CUDA GPU rendering supported by RedShift for Autodesk 3dsMax and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
Notes- Table 8 lists the OSs supported by P2v ECSs.
-
Table 8 Supported OS versions OS
+Notes- Table 9 lists the OSs supported by P2v ECSs.
+
Table 9 Supported OS versions OS
Version
+Version
CentOS
+CentOS
CentOS 7.9 64bit
+CentOS 7.9 64bit
EulerOS
+EulerOS
EulerOS 2.5 64bit
+EulerOS 2.5 64bit
Oracle Linux
+Oracle Linux
Oracle Linux Server release 7.6 64bit
+Oracle Linux Server release 7.6 64bit
Ubuntu
+Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
+Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
Computing-accelerated P2
Overview
Compared with P1 ECSs, P2 ECSs use NVIDIA Tesla V100 GPUs, which have improved both single- and double-precision computing capabilities by 50% and offer 112 TFLOPS of deep learning.
Specifications -Table 9 P2 ECS specifications Flavor
+Table 10 P2 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Local Disks
+Local Disks
Virtualization
+Virtualization
Hardware
+Hardware
p2.2xlarge.8
+p2.2xlarge.8
8
+8
64
+64
5/1.6
+5/1.6
35
+35
2
+2
12
+12
1 × V100
+1 × V100
1 × 16
+1 × 16
1 × 800 GiB NVMe
+1 × 800 GiB NVMe
KVM
+KVM
CPU: Intel® Xeon® Processor E5-2690 v4
+CPU: Intel® Xeon® Processor E5-2690 v4
p2.4xlarge.8
+p2.4xlarge.8
16
+16
128
+128
8/3.2
+8/3.2
70
+70
4
+4
12
+12
2 × V100
+2 × V100
2 × 16
+2 × 16
2 × 800 GiB NVMe
+2 × 800 GiB NVMe
KVM
+KVM
p2.8xlarge.8
+p2.8xlarge.8
32
+32
256
+256
10/6.5
+10/6.5
140
+140
8
+8
12
+12
4 × V100
+4 × V100
4 × 16
+4 × 16
4 × 800 GiB NVMe
+4 × 800 GiB NVMe
KVM
+KVM
- Excellent supercomputing ecosystem
-The supercomputing ecosystem allows you to build up a flexible, high-performance, cost-effective computing platform. A large number of HPC applications and deep-learning frameworks can run on P2 ECSs.
Supported Common Software
+Supported Common Software
P2 ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software requires GPU CUDA parallel computing, use P2 ECSs. P2 ECSs support the following commonly used software:- Common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- CUDA GPU rendering supported by RedShift for Autodesk 3dsMax and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
Notes- The system disk of a P2 ECS must be greater than or equal to 15 GiB. It is recommended that the system disk be greater than 40 GiB.
- The local NVMe SSDs attached to P2 ECSs are dedicated for services with strict requirements on storage I/O performance, such as deep learning training and HPC. Local disks are attached to the ECSs of specified flavors and cannot be separately bought. In addition, you are not allowed to detach a local disk and then attach it to another ECS.-
Data may be lost on the local NVMe SSDs attached to P2 ECSs due to a fault, for example, due to a disk or host fault. Therefore, you are suggested to store only temporary data in local NVMe SSDs. If you store important data in such a disk, securely back up the data.
- P2 ECSs do not support specifications modification.
- Table 10 lists the OSs supported by P2 ECSs.
-
Table 10 Supported OS versions OS
+- P2 ECSs do not support specifications modification.
- Table 11 lists the OSs supported by P2 ECSs. +
Table 11 Supported OS versions OS
Version
+Version
CentOS
+CentOS
CentOS 7.9 64bit
+CentOS 7.9 64bit
EulerOS
+EulerOS
EulerOS 2.5 64bit
+EulerOS 2.5 64bit
Oracle Linux
+Oracle Linux
Oracle Linux Server release 7.6 64bit
+Oracle Linux Server release 7.6 64bit
Ubuntu
+Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
+Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
P1 ECSs use NVIDIA Tesla P100 GPUs and provide flexibility, high performance, and cost-effectiveness. These ECSs support GPU Direct for direct communication between GPUs, improving data transmission efficiency. P1 ECSs provide outstanding general computing capabilities and have strengths in deep learning, graphic databases, high-performance databases, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics. They are designed for scientific computing.
Specifications
-Table 11 P1 ECS specifications Flavor
+Table 12 P1 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Local Disks
+Local Disks
(GiB)
Virtualization
+Virtualization
Hardware
+Hardware
p1.2xlarge.8
+p1.2xlarge.8
8
+8
64
+64
5/1.6
+5/1.6
35
+35
2
+2
12
+12
1 × P100
+1 × P100
1 × 16
+1 × 16
1 × 800
+1 × 800
KVM
+KVM
CPU: Intel® Xeon® Processor E5-2690 v4
+CPU: Intel® Xeon® Processor E5-2690 v4
p1.4xlarge.8
+p1.4xlarge.8
16
+16
128
+128
8/3.2
+8/3.2
70
+70
4
+4
12
+12
2 × P100
+2 × P100
2 × 16
+2 × 16
2 × 800
+2 × 800
KVM
+KVM
p1.8xlarge.8
+p1.8xlarge.8
32
+32
256
+256
10/6.5
+10/6.5
140
+140
8
+8
12
+12
4 × P100
+4 × P100
4 × 16
+4 × 16
4 × 800
+4 × 800
KVM
+KVM
Notes- It is recommended that the system disk of a P1 ECS be greater than 40 GiB.
- The local NVMe SSDs attached to P1 ECSs are dedicated for services with strict requirements on storage I/O performance, such as deep learning training and HPC. Local disks are attached to the ECSs of specified flavors and cannot be separately bought. In addition, you are not allowed to detach a local disk and then attach it to another ECS.
Data may be lost on the local NVMe SSDs attached to P1 ECSs due to a fault, for example, due to a disk or host fault. Therefore, you are suggested to store only temporary data in local NVMe SSDs. If you store important data in such a disk, securely back up the data.
- After a P1 ECS is created, you must install the NVIDIA driver for computing acceleration. For details, see Installing a Tesla Driver and CUDA Toolkit on a GPU-accelerated ECS.
- P1 ECSs do not support specifications change.
- P1 ECSs do not support automatic recovery.
- If the host is faulty or subhealthy, you need to stop the ECS for hardware repair.
- In case of system maintenance or hardware faults, the ECS will be redeployed (to ensure HA) and cold migrated to another host. The local disk data of the ECS will not be retained.
- Table 12 lists the OSs supported by P1 ECSs.
-
Table 12 Supported OS versions OS
+- Table 13 lists the OSs supported by P1 ECSs. +
Table 13 Supported OS versions OS
Version
+Version
CentOS
+CentOS
CentOS 7.9 64bit
+CentOS 7.9 64bit
Debian
+Debian
- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
- Debian GNU/Linux 11 64bit
- Debian GNU/Linux 10 64bit
Oracle Linux
+Oracle Linux
Oracle Linux Server release 7.6 64bit
+Oracle Linux Server release 7.6 64bit
Ubuntu
+Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Pi2 ECSs use NVIDIA Tesla T4 GPUs dedicated for real-time AI inference. These ECSs use the T4 INT8 calculator for up to 130 TOPS of INT8 computing. The Pi2 ECSs can also be used for light-load training.
Specifications
-Table 13 Pi2 ECS specifications Flavor
+Table 14 Pi2 ECS specifications Flavor
vCPUs
+vCPUs
Memory
+Memory
(GiB)
Max./Assured Bandwidth
+Max./Assured Bandwidth
(Gbit/s)
Max. PPS
+Max. PPS
(10,000)
Max. NIC Queues
+Max. NIC Queues
Max. NICs
+Max. NICs
GPUs
+GPUs
GPU Memory
+GPU Memory
(GiB)
Local Disks
+Local Disks
Virtualization
+Virtualization
Hardware
+Hardware
pi2.2xlarge.4
+pi2.2xlarge.4
8
+8
32
+32
10/4
+10/4
50
+50
4
+4
4
+4
1 × T4
+1 × T4
1 × 16 GiB
+1 × 16 GiB
N/A
+N/A
KVM
+KVM
CPU: Intel® Xeon® Skylake 6151 3.0 GHz or Intel® Xeon® Cascade Lake 6278 2.6 GHz
+CPU: Intel® Xeon® Skylake 6151 3.0 GHz or Intel® Xeon® Cascade Lake 6278 2.6 GHz
pi2.4xlarge.4
+pi2.4xlarge.4
16
+16
64
+64
15/8
+15/8
100
+100
8
+8
8
+8
2 × T4
+2 × T4
2 × 16 GiB
+2 × 16 GiB
N/A
+N/A
KVM
+KVM
pi2.8xlarge.4
+pi2.8xlarge.4
32
+32
128
+128
25/15
+25/15
200
+200
16
+16
8
+8
4 × T4
+4 × T4
4 × 16 GiB
+4 × 16 GiB
N/A
+N/A
KVM
+KVM
pi2.16xlarge.4
+pi2.16xlarge.4
64
+64
256
+256
30/30
+30/30
400
+400
32
+32
8
+8
8 × T4
+8 × T4
8 × 16 GiB
+8 × 16 GiB
N/A
+N/A
KVM
+KVM
- After a Pi2 ECS is stopped, basic resources including vCPUs, memory, image, and GPUs are not billed, but its system disk is billed based on the disk capacity. If other products, such as EVS disks, EIP, and bandwidth are associated with the ECS, these products are billed separately.
Resources are released after a Pi2 ECS is stopped. If resources are insufficient when the Pi2 ECS is started after being stopped, starting the ECS might fail. Therefore, if you need to use a Pi2 ECS for a long time, keep the ECS running.
- Table 14 lists the OSs supported by Pi2 ECSs.
-
Table 14 Supported OS versions OS
+- Table 15 lists the OSs supported by Pi2 ECSs.
+
Table 15 Supported OS versions OS
Version
+Version
CentOS
+CentOS
CentOS 7.9 64bit
+CentOS 7.9 64bit
Oracle Linux
+Oracle Linux
Oracle Linux Server release 7.6 64bit
+Oracle Linux Server release 7.6 64bit
Ubuntu
+Ubuntu
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
- Ubuntu 20.04 server 64bit
- Ubuntu 18.04 server 64bit
Windows
+Windows
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- Windows Server 2019 Standard 64bit
- Windows Server 2016 Standard 64bit
- Windows Server 2012 R2 Standard 64bit
- System disk image: contains an OS and application software for running services. You can use a system disk image to create ECSs and migrate your services to the cloud.
- Data disk image: contains only service data. You can create a data disk image from an ECS data disk. You can also use a data disk image to create EVS disks and migrate your service data to the cloud.
- Full-ECS image: contains all the data of an ECS, including the data on the data disks attached to the ECS. A full-ECS image can be used to rapidly create ECSs with service data.
You can use a private image to change the OS. For instructions about how to create a private image, see Image Management Service User Guide.
-Procedure
- Log in to the management console.
- Click in the upper left corner and select your region and project.
- Under Computing, click Elastic Cloud Server.
- Locate the row containing the target ECS and choose More > Manage Image/Backup > Create Image in the Operation column.
- Configure the following information:
Table 1 and Table 2 list the parameters in the Image Type and Source and Image Information areas, respectively.
+Procedure
- Table 15 lists the OSs supported by Pi2 ECSs.
+
- Table 13 lists the OSs supported by P1 ECSs. +
- Table 9 lists the OSs supported by P2v ECSs.
+
- Table 7 lists the OSs supported by P2s ECSs.
+
- Table 4 lists the OSs supported by G6 ECSs.
+
- IP address:
- Verify the SSH fingerprint of the ECS and enter yes.
- Server List: The ECS to be backed up is selected by default. Click
- If the ECS has been associated with a vault, configure the backup information as prompted.
- If the ECS has been associated with a vault, configure the backup information as prompted.
