The value can be
Allow or
Deny.
- If the Action is set to Allow, traffic is allowed to access the cloud servers in the security group over specified ports.
- If the Action is set to Deny, traffic is denied to access the cloud servers in the security group over specified ports.
+
The value can be Allow or Deny. - If the Action is set to Allow, traffic is allowed to access the cloud servers in the security group over specified ports.
- If the Action is set to Deny, traffic is denied to access the cloud servers in the security group over specified ports.
|
Allow
@@ -64,7 +64,7 @@
All IP addresses0.0.0.0/0 represents all IPv4 addresses.
::/0 represents all IPv6 addresses.
-Security group: The source is from another security group. You can select a security group in the same region from the drop-down list. If there is instance A in security group A and instance B in security group B, and the inbound rule of security group A allows traffic from security group B, traffic is allowed from instance B 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 simpler way.
+Security group: The source is from another security group. You can select a security group in the same region from the drop-down list. If there is instance A in security group A and instance B in security group B, and the inbound rule of security group A allows traffic from security group B, traffic is allowed from instance B 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 simpler way.
|
IP address
@@ -87,9 +87,9 @@
Configure required parameters.You can click + to add more outbound rules.
Figure 2 Adding outbound rules
-Table 2 Outbound rule parameter descriptionParameter
+Table 2 Outbound rule parameter descriptionParameter
|
-Description
+ | Description
|
Example Value
|
diff --git a/docs/ecs/umn/en-us_topic_0031107266.html b/docs/ecs/umn/en-us_topic_0031107266.html
index 310369dbc..8cb3af9b9 100644
--- a/docs/ecs/umn/en-us_topic_0031107266.html
+++ b/docs/ecs/umn/en-us_topic_0031107266.html
@@ -6,11 +6,12 @@
PrerequisitesYou have obtained the private key file (.pem file) which was generated during the ECS creation.
Obtaining the Password Through the Management Console- Obtain the private key file (.pem file) used when you created the ECS.
- Log in to the management console.
- Click
 in the upper left corner and select a region and project. - Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Get Password.
Figure 1 Get Password
+Obtaining the Password Through the Management Console- Obtain the private key file (.pem file) used when you created the ECS.
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Get Password.
Figure 1 Get Password
- Use either of the following methods to obtain the password through the private key:
- Click Select File and upload the private key from a local directory.
- Copy the content of the private key file and paste it into the text box.
- Click Get Password to obtain a random password.
Obtaining the Password Through APIs- Obtain the private key file (.pem file) used when you created the ECS.
- Set up the API calling environment.
- Call APIs. For details, see API Usage Guidelines in the Elastic Cloud Server API Reference.
- Obtain the ciphertext password.
Call the password obtaining APIs to obtain the ciphertext password of the public key encrypted using RSA. The API URI is in the format "GET /v2/{project_id}/servers/{server_id}/os-server-password".
+Obtaining the Password Through APIs- Obtain the private key file (.pem file) used when you created the ECS.
- Set up the API calling environment.
- Call APIs. For details, see API Usage Guidelines in the Elastic Cloud Server API Reference.
- Obtain the ciphertext password.
Call the password obtaining APIs to obtain the ciphertext password of the public key encrypted using RSA.
+The API URI is in the following format: GET /v2/{project_id}/servers/{server_id}/os-server-password.
- Decrypt the ciphertext password.
Use the private key file used when you created the ECS to decrypt the ciphertext password obtained in step 4.
diff --git a/docs/ecs/umn/en-us_topic_0031107267.html b/docs/ecs/umn/en-us_topic_0031107267.html
index 4fc90a2f0..111aa1522 100644
--- a/docs/ecs/umn/en-us_topic_0031107267.html
+++ b/docs/ecs/umn/en-us_topic_0031107267.html
@@ -6,7 +6,7 @@
 Once deleted, the password cannot be retrieved, so record the password before deleting it.
Procedure- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Delete Password.
The system displays a message, asking you whether you want to delete the password.
+Procedure- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- On the Elastic Cloud Server page, select the target ECS.
- In the Operation column, click More and select Delete Password.
The system displays a message, asking you whether you want to delete the password.
Figure 1 Delete Password
- Click OK to delete the password.
- 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 a region and project.
- Under Computing, click 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 the change.
+Procedure- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click 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 the change.
- Select the target image.
For details, see Creating an ECS.
Figure 1 Changing an OS
- (Optional) Select the Encrypted option to encrypt the system disk during OS change.
To enable encryption, click Create Xrole to grant KMS access permissions to EVS. If you have the granting permission, grant KMS access permissions to EVS. If you do not have the granting permission, contact the user who has the Security Administrator permissions to grant KMS access permissions. For details, see Can All Users Use the Encryption Feature?
@@ -29,7 +29,7 @@
- Set Login Mode.
You can set the login mode for the ECS whose OS is to be changed based on service requirements.
- - Click OK.
- On the Change OS page, confirm the settings and click Submit.
After the application is submitted, the ECS status changes to Changing OS. When this status disappears, the OS change is complete.
+ - Click OK.
- On the Change OS page, confirm the settings and click Submit.
After the application is submitted, the ECS status changes to Changing OS. When this status disappears, the OS change is complete.
 During the OS change process, a temporary ECS is created. After the OS change is complete, this ECS will be automatically deleted.
@@ -39,7 +39,7 @@
- Mount the partition so that you can use the data disk.
mount Disk partition Device name
- Check the mount result.
df -TH
- - If the OS change fails, perform steps 3 to 10 again to retry the OS change.
- If the attempt still fails, contact customer service for manual recovery at the backend.
+ - If the OS change fails, perform the operations described in Procedure again to retry the OS change.
- If the attempt still fails, contact customer service for manual recovery at the backend.
diff --git a/docs/ecs/umn/en-us_topic_0032980085.html b/docs/ecs/umn/en-us_topic_0032980085.html
index 40c950192..389f6df47 100644
--- a/docs/ecs/umn/en-us_topic_0032980085.html
+++ b/docs/ecs/umn/en-us_topic_0032980085.html
@@ -9,20 +9,20 @@
- Removing an ECS from an ECS Group
- Deleting an ECS Group
Creating an ECS GroupCreate an ECS group and select a policy for the group. This policy applies to all ECSs in the same group. ECS groups are independent of each other.
- - Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- On the ECS Group page, click Create ECS Group.
- Enter the name of the ECS group.
- Select a policy for the ECS group.
- Click OK.
+ - Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- On the ECS Group page, click Create ECS Group.
- Enter the name of the ECS group.
- Select a policy for the ECS group.
- Click OK.
Adding an ECS to an ECS GroupTo improve service reliability, you can add ECSs to an ECS group so that these ECSs in this group can run on different hosts.
- After an ECS is added to an ECS group, the system reallocates a host to run this ECS to ensure that ECSs in this group run on different hosts. When you attempt to restart the ECS, the startup may fail due to insufficient resources. In such a case, remove the ECS from the ECS group and try to restart the ECS again.
- ECSs with local disks can be added to an ECS group only during the creation process. Once created, they cannot be added to any ECS groups.
- ECSs that have local disks, GPU cards, or FPGA cards attached can be added to an ECS group only during the creation process. Once created, they cannot be added to any ECS groups.
- - Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the row that contains the target ECS group and click Add ECS in the Operation column.
- On the Add ECS page, select an ECS to be added.
- Click OK. The ECS is added to the ECS group.
+ - Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the row that contains the target ECS group and click Add ECS in the Operation column.
- On the Add ECS page, select an ECS to be added.
- Click OK. The ECS is added to the ECS group.
Removing an ECS from an ECS GroupAfter an ECS is removed from an ECS group, the ECS does not comply with the ECS group policy anymore.
- - Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Expand the ECS group information and view the ECSs in the ECS group.
- Locate the ECS to be removed and click Remove in the Operation column.
Alternatively, select multiple ECSs to be removed and click Remove above the list.
+- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Expand the ECS group information and view the ECSs in the ECS group.
- Locate the ECS to be removed and click Remove in the Operation column.
Alternatively, select multiple ECSs to be removed and click Remove above the list.
- In the displayed dialog box, click OK.
The ECS is removed from the ECS group.
Deleting an ECS GroupAfter an ECS group is deleted, the policy does not apply to the ECSs in the ECS group anymore.
- - Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the ECS group to be deleted and click Delete in the Operation column.
- In the displayed dialog box, click OK.
+ - Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the navigation pane on the left, choose ECS Group.
- Locate the ECS group to be deleted and click Delete in the Operation column.
- In the displayed dialog box, click OK.
diff --git a/docs/ecs/umn/en-us_topic_0035470101.html b/docs/ecs/umn/en-us_topic_0035470101.html
index c13c18559..ffdb44867 100644
--- a/docs/ecs/umn/en-us_topic_0035470101.html
+++ b/docs/ecs/umn/en-us_topic_0035470101.html
@@ -1,11 +1,11 @@
General-Purpose ECSs
- OverviewGeneral-purpose ECSs provide a balance of compute, memory, and networking resources and a baseline level of vCPU performance with the ability to burst above the baseline. These ECSs are suitable for applications with general workloads, such as web servers, enterprise R&D, and small-scale databases.
+ OverviewGeneral-purpose ECSs provide a balance of compute, memory, and networking resources and a baseline level of vCPU performance with the ability to burst above the baseline. These ECSs are suitable for applications that do not always utilize full vCPU performance but occasionally burst, such as web servers, enterprise R&D, and small-scale databases.
S9 ECSs use the sixth-generation Intel® Xeon® Scalable processors and KVM virtualization to provide enhanced compute, network, and security performance as well as better cost-effectiveness. If you have requirements on performance stability, you can optimize the performance by referring to Best Practices for Performance Configuration to reduce the ping and TCP/UDP latency.
S7n ECSs use the 3rd generation Intel® Xeon® Scalable processors and 25GE high-speed intelligent NICs to provide high network bandwidth and packets per second (PPS) at the lowest possible price.
S3 ECSs are suitable for applications that require moderate performance generally but occasionally burstable high performance, such as light-workload web servers, enterprise R&D and testing environments, and low- and medium-performance databases.
- S2 ECSs use Intel® Xeon® Scalable processors, which significantly improve the comprehensive performance. They provide a balance of compute, memory, and networking resources and a baseline level of vCPU performance with the ability to burst above the baseline. These ECSs are suitable for the scenarios where vCPU performance is not often (or always) used but is occasionally used.
+ S2 ECSs use Intel® Xeon® Scalable processors, which significantly improve the comprehensive performance. They provide a balance of compute, memory, and networking resources and a baseline level of vCPU performance with the ability to burst above the baseline. They are suitable for applications that do not always utilize full vCPU performance but occasionally burst.
X1 ECSs use Intel® Xeon® Scalable processors, which significantly improve the comprehensive performance. They provide a balance of compute, memory, and networking resources and a baseline level of vCPU performance with the ability to burst above the baseline.
|---|
Table 3 S3 ECS specificationsFlavor
+Table 3 S3 ECS specificationsFlavor
|
-vCPUs
+ | vCPUs
|
-Memory
+ | Memory
(GiB)
|
-Max./Assured Network Bandwidth
+ | Max./Assured Network Bandwidth
(Gbit/s)
|
-Max. Network PPS
+ | Max. Network PPS
(10,000)
|
-Max. NIC Queues
+ | Network Connections
+(10,000)
|
-Max. NICs
+ | Max. NIC Queues
|
-Virtualization
+ | Max. NICs
|
-Hardware
+ | Max. EVS Disks
+ |
+Virtualization
+ |
+Hardware
|
|---|
-s3.medium.1
+ | s3.medium.1
|
-1
+ | 1
|
-1
+ | 1
|
-0.8/0.15
+ | 0.8/0.15
|
-10
+ | 10
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
|
-CPU: Intel® Xeon® Cascade Lake 6278
+ | 60
+ |
+KVM
+ |
+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
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.xlarge.1
+ | s3.xlarge.1
|
-4
+ | 4
|
-4
+ | 4
|
-2/0.5
+ | 2/0.5
|
-25
+ | 25
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.2xlarge.1
+ | s3.2xlarge.1
|
-8
+ | 8
|
-8
+ | 8
|
-3/1
+ | 3/1
|
-50
+ | 50
|
-2
+ | 200
|
-2
+ | 2
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.4xlarge.1
+ | s3.4xlarge.1
|
-16
+ | 16
|
-16
+ | 16
|
-6/2
+ | 6/2
|
-100
+ | 100
|
-4
+ | 200
|
-2
+ | 4
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.8xlarge.1
+ | s3.8xlarge.1
|
-32
+ | 32
|
-32
+ | 32
|
-8/2
+ | 8/2
|
-200
+ | 200
|
-8
+ | 200
|
-4
+ | 8
|
-KVM
+ | 4
+ |
+60
+ |
+KVM
|
-s3.medium.2
+ | s3.medium.2
|
-1
+ | 1
|
-2
+ | 2
|
-0.8/0.15
+ | 0.8/0.15
|
-10
+ | 10
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.large.2
+ | s3.large.2
|
-2
+ | 2
|
-4
+ | 4
|
-1.5/0.3
+ | 1.5/0.3
|
-15
+ | 15
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.xlarge.2
+ | s3.xlarge.2
|
-4
+ | 4
|
-8
+ | 8
|
-2/0.5
+ | 2/0.5
|
-25
+ | 25
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.2xlarge.2
+ | s3.2xlarge.2
|
-8
+ | 8
|
-16
+ | 16
|
-3/1
+ | 3/1
|
-50
+ | 50
|
-2
+ | 200
|
-2
+ | 2
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.4xlarge.2
+ | s3.4xlarge.2
|
-16
+ | 16
|
-32
+ | 32
|
-6/2
+ | 6/2
|
-100
+ | 100
|
-4
+ | 200
|
-2
+ | 4
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.8xlarge.2
+ | s3.8xlarge.2
|
-32
+ | 32
|
-64
+ | 64
|
-8/2
+ | 8/2
|
-200
+ | 200
|
-8
+ | 200
|
-4
+ | 8
|
-KVM
+ | 4
+ |
+60
+ |
+KVM
|
-s3.medium.4
+ | s3.medium.4
|
-1
+ | 1
|
-4
+ | 4
|
-0.8/0.15
+ | 0.8/0.15
|
-10
+ | 10
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.large.4
+ | s3.large.4
|
-2
+ | 2
|
-8
+ | 8
|
-1.5/0.3
+ | 1.5/0.3
|
-15
+ | 15
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.xlarge.4
+ | s3.xlarge.4
|
-4
+ | 4
|
-16
+ | 16
|
-2/0.5
+ | 2/0.5
|
-25
+ | 25
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.2xlarge.4
+ | s3.2xlarge.4
|
-8
+ | 8
|
-32
+ | 32
|
-3/1
+ | 3/1
|
-50
+ | 50
|
-2
+ | 200
|
-2
+ | 2
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.4xlarge.4
+ | s3.4xlarge.4
|
-16
+ | 16
|
-64
+ | 64
|
-6/2
+ | 6/2
|
-100
+ | 100
|
-4
+ | 200
|
-2
+ | 4
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.8xlarge.4
+ | s3.8xlarge.4
|
-32
+ | 32
|
-128
+ | 128
|
-8/2
+ | 8/2
|
-200
+ | 200
|
-8
+ | 200
|
-4
+ | 8
|
-KVM
+ | 4
+ |
+60
+ |
+KVM
|
-s3.medium.8
+ | s3.medium.8
|
-1
+ | 1
|
-8
+ | 8
|
-0.8/0.15
+ | 0.8/0.15
|
-10
+ | 10
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.large.8
+ | s3.large.8
|
-2
+ | 2
|
-16
+ | 16
|
-1.5/0.3
+ | 1.5/0.3
|
-15
+ | 15
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.xlarge.8
+ | s3.xlarge.8
|
-4
+ | 4
|
-32
+ | 32
|
-2/0.5
+ | 2/0.5
|
-25
+ | 25
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.2xlarge.8
+ | s3.2xlarge.8
|
-8
+ | 8
|
-64
+ | 64
|
-3/1
+ | 3/1
|
-50
+ | 50
|
-2
+ | 200
|
-2
+ | 2
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.4xlarge.8
+ | s3.4xlarge.8
|
-16
+ | 16
|
-128
+ | 128
|
-6/2
+ | 6/2
|
-100
+ | 100
|
-4
+ | 200
|
-2
+ | 4
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.8xlarge.8
+ | s3.8xlarge.8
|
-32
+ | 32
|
-256
+ | 256
|
-8/2
+ | 8/2
|
-200
+ | 200
|
-8
+ | 200
|
-4
+ | 8
|
-KVM
+ | 4
+ |
+60
+ |
+KVM
|
diff --git a/docs/ecs/umn/en-us_topic_0035550301.html b/docs/ecs/umn/en-us_topic_0035550301.html
index 2c51e1a49..99fd04821 100644
--- a/docs/ecs/umn/en-us_topic_0035550301.html
+++ b/docs/ecs/umn/en-us_topic_0035550301.html
@@ -1,10 +1,10 @@
Memory-optimized ECSs
-Overview- M9 ECSs use the sixth-generation Intel® Xeon® Scalable processors and KVM virtualization to provide enhanced compute, network, and security performance to fulfill the high-performance and large-memory requirements.
- M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced compute, security, and stability. Each M7n ECS can have a maximum number of 96 vCPUs and a memory speed of 3,200 MHz, and provide a secure and trusted cloud environment for memory-intensive compute applications.
- M4 ECSs use the second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable compute 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 PPS.
- M3 ECSs are developed based on the KVM virtualization platform and designed for processing large-scale data sets in memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive compute applications.
+ Overview- M9 ECSs use the sixth-generation Intel® Xeon® Scalable processors and KVM virtualization to provide enhanced compute, network, and security performance to fulfill the high-performance and large-memory requirements.
- M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced performance, security, and stability. An M7n ECS can have up to 96 vCPUs and 3,200 MHz memory frequency. It provides a secure and trusted cloud environment and is suitable for memory-intensive compute applications.
- M4 ECSs use the second-generation Intel® Xeon® Scalable processors with technologies optimized to offer powerful and stable compute 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 PPS.
- M3 ECSs are built on the KVM virtualization platform and designed for processing large-scale datasets in memory. They use Intel® Xeon® Scalable processors, network acceleration engines, and DPDK rapid packet processing to provide higher network performance and up to 512 GiB of DDR4 memory for memory-intensive compute applications.
Specifications
- Table 1 M9 ECS specificationsFlavor
+Table 1 M9 ECS specificationsFlavor
|
vCPUs
|
@@ -165,7 +165,7 @@
128
|
-1024
+ | 1,024
|
100/80
|
@@ -186,7 +186,7 @@
192
|
-1504
+ | 1,504
|
120/102
|
diff --git a/docs/ecs/umn/en-us_topic_0039588795.html b/docs/ecs/umn/en-us_topic_0039588795.html
index 80ff31796..b52a7a3c1 100644
--- a/docs/ecs/umn/en-us_topic_0039588795.html
+++ b/docs/ecs/umn/en-us_topic_0039588795.html
@@ -3,8 +3,8 @@
Viewing the ECS Creation Status
ScenariosAfter submitting the request for creating an ECS, you can view the creation status. This section describes how to view the creation status of an ECS.
- Procedure- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, select Elastic Cloud Server.
- After creating an ECS, view the creation status above the ECS list beside the common operations (Start, Stop, Restart, and Delete).
Figure 1 ECS creation status
- - Click the number displayed above Creating and view task details.
- An ECS that is being created is in one of the following states:
|---|
-2026-03-02
+ | 2026-04-08
+ |
+Added the following content:
+Configuring Secure Boot for an ECS
+ |
+
+2026-03-02
|
Modified the following content:
diff --git a/docs/ecs/umn/en-us_topic_0048642616.html b/docs/ecs/umn/en-us_topic_0048642616.html
index f2909e3ba..fa0c6b913 100644
--- a/docs/ecs/umn/en-us_topic_0048642616.html
+++ b/docs/ecs/umn/en-us_topic_0048642616.html
@@ -1,18 +1,18 @@
-Cloud-Init
-Cloud-Init is an open-source cloud initialization program, which initializes some of the customized configurations of a newly created ECS, such as the hostname, key pair, and user data.
- All standard (Standard_xxx) and enterprise (Enterprise_xxx) images support Cloud-Init. Only certain community images (Community_xxx) do not support it.
- Using Cloud-Init to initialize your ECSs will affect your ECS, IMS, and AS services.
+ Cloud-Init/Cloudbase-Init
+ Cloud-Init or Cloudbase-Init is an open-source cloud program that allows you to configure specific custom details of newly created ECSs (such as the hostname, key pair, and user data) during initialization.
+ All standard (Standard_xxx) and enterprise (Enterprise_xxx) images support Cloud-Init or Cloudbase-Init. Only certain community images (Community_xxx) do not support it.
+ Using Cloud-Init or Cloudbase-Init to initialize your ECSs will affect the use of your ECS, IMS, and AS services.
Impact on IMSTo ensure that ECSs that are created using a private image support custom configurations, you must install Cloud-Init or Cloudbase-Init on the ECSs before using them to create private images. - For Windows OSs, download and install Cloudbase-Init.
- For Linux OSs, download and install Cloud-Init.
- Once installed in an image, Cloud-Init or Cloudbase-Init automatically configures initial attributes for the ECSs created using this image.
+ Once installed in an image, Cloud-Init or Cloudbase-Init will automatically configure initial attributes for the ECSs when they are created using this image.
For more information, see Image Management Service User Guide.
- Impact on ECS- When creating an ECS, if the selected image supports Cloud-Init, you can use the User Data function to specify custom configuration, such as ECS login password to the ECS. Such custom settings will take effect upon ECS initialization. For details, see Injecting User Data.
- If Cloud-Init is supported, ECSs do not support password authentication anymore. All newly created ECSs use key pair authentication. This change will influence your ECS logins. For details, see the following sections:
-
- If Cloud-Init is supported, you can view and use metadata to configure and manage running ECSs. For details, see Obtaining ECS Details Using Metadata.
+ Impact on ECS- When creating an ECS, if the selected image supports Cloud-Init or Cloudbase-Init, you can inject custom information (such as the ECS login password) during the initialization. For details, see Injecting User Data.
- After Cloud-Init is supported, ECSs do not support password authentication anymore. All newly created ECSs use key pair authentication. This change will affect your login to ECSs. For details, see the following sections:
+
- After Cloud-Init or Cloudbase-Init is supported, you can view and use metadata to configure and manage running ECSs. For details, see Obtaining ECS Details Using Metadata.
- |
P3 ECS Features
-- CPU: 2nd Generation Intel® Xeon® Scalable 6248R processors and 3.0 GHz of basic frequency
- Up to eight NVIDIA A100 GPUs on an ECS
- NVIDIA CUDA parallel computing and common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- 19.5 TFLOPS of single-precision performance and 9.7 TFLOPS of double-precision performance on a single GPU
- NVIDIA Tensor cores with 156 TFLOPS of single- and double-precision performance for deep learning
- Up to 40 Gbit/s of network bandwidth on a single ECS
- 80 GB HBM2 GPU memory per graphics card, with a bandwidth of 1,935 Gbit/s
- Comprehensive basic capabilities
- User-defined network with flexible subnet division and network access policy configuration
- Mass storage, elastic expansion, and backup and restoration
- Elastic scaling
+- CPU: 2nd Generation Intel® Xeon® Scalable 6248R processors and 3.0 GHz of basic frequency
- Up to eight NVIDIA A100 GPUs on an ECS
- NVIDIA CUDA parallel computing and common deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
- 19.5 TFLOPS of single-precision performance and 9.7 TFLOPS of double-precision performance on a single GPU
- NVIDIA Tensor cores with 156 TFLOPS of mixed-precision performance for deep learning
- Up to 40 Gbit/s of network bandwidth on a single ECS
- 80 GB HBM2 GPU memory per graphics card, with a bandwidth of 1,935 Gbit/s
- Comprehensive basic capabilities
- User-defined network with flexible subnet division and network access policy configuration
- Mass storage, elastic expansion, and backup and restoration
- Elastic scaling
- Flexibility
Similar to other types of ECSs, P3 ECSs can be provisioned in a few minutes.
- 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 P3 ECSs.
Supported 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:
+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 parallel computing, use P3 ECSs. P3 ECSs support the following commonly used software:
- Common deep learning frameworks, such as TensorFlow, Spark, PyTorch, MXNet, and Caffe
- CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
- More than 2,000 GPU-accelerated applications such as Amber, NAMD, and VASP
-Notes
-- After a P3 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 will be released after a P3 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+ Notes
+ - After a P3 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 will be released after a P3 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop it.
- - 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 Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous compute. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
+ - 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 Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- Unlike general-purpose compute, GPU-accelerated ECSs deliver heterogeneous compute. Their specifications can only be modified within the same instance type.
- GPU-accelerated ECSs do not support live migration.
Computing-accelerated P2sOverview
- 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.
+ 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 fields such as AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics.
Specifications
Table 8 P2s ECS specificationsFlavor
@@ -892,15 +891,15 @@
Supported 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 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
+ 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 parallel computing, 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 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
- Notes- After a P2s 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 will be released after a P2s ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+ Notes- After a P2s 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 will be released after a P2s ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop it.
- - 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 has been installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous compute. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
+ - 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 has been installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- Unlike general-purpose compute, GPU-accelerated ECSs deliver heterogeneous compute. Their specifications can only be modified within the same instance type.
- GPU-accelerated ECSs do not support live migration.
- Computing-accelerated P2vOverview
- 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.
+ Computing-accelerated P2vOverview
+ 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 fields such as AI-based deep learning, scientific computing, Computational Fluid Dynamics (CFD), computing finance, seismic analysis, molecular modeling, and genomics.
Specifications
Table 9 P2v ECS specificationsFlavor
@@ -1035,16 +1034,16 @@
Supported 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 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
+ 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 parallel computing, 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 3ds Max and V-Ray for 3ds Max
- Agisoft PhotoScan
- MapD
- Notes- After a P2v 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 will be released after a P2v ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+ Notes- After a P2v 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 will be released after a P2v ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop it.
- - By default, P2v ECSs created using a Windows public image have the Tesla driver installed.
- By default, P2v ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- If a P2v 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 Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous compute. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
+ - By default, P2v ECSs created using a Windows public image have the Tesla driver installed.
- By default, P2v ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- If a P2v 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 Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- Unlike general-purpose compute, GPU-accelerated ECSs deliver heterogeneous compute. Their specifications can only be modified within the same instance type.
- GPU-accelerated ECSs do not support live migration.
- Inference-accelerated Pi5eOverview
+ Inference-accelerated Pi5eOverview
Pi5e ECSs use NVIDIA Ada Lovelace L4 Tensor Core GPUs that are dedicated to real-time AI inference. This series is the most efficient NVIDIA accelerator for mainstream applications. Servers equipped with L4 power up to 120x higher AI video performance and 2.7x more generative AI performance over CPU solutions, as well as over 4x more graphics performance than the previous GPU generation. NVIDIA L4's versatility and energy-efficient, single-slot, low-profile form factor make it ideal for global deployments, including edge locations.
- Specifications
+ Specifications
Table 10 Pi5e ECS specificationsFlavor
|
@@ -1216,11 +1215,11 @@
Pi5e ECS features:
- 1:4 ratio of vCPUs to memory
- CPU: 3rd Generation Intel® Xeon® Scalable 6348 processors (2.6 GHz of basic frequency and 3.5 GHz of turbo frequency)
- 24 GiB of GPU memory per card
- Up to 300 GB/s of GPU memory bandwidth
- GPUDirect Peer to Peer (P2P)
-Notes
+Notes
- Pi5e ECSs support automatic recovery when the hosts accommodating such ECSs become faulty.
- After a Pi5e ECS is stopped, its basic resources (vCPUs, memory, image, and encoding cards) are not billed, but its system disk is billed based on the disk capacity. If other service resources, such as EVS disks, EIPs, and bandwidth are associated with the ECS, these resources are billed separately.
- Specifications of Pi5e ECSs can only be changed to other specifications of the same instance type.
- Pi5e ECSs support TPM.
Inference-accelerated Pi2Overview
- Pi2 ECSs use NVIDIA Tesla T4 GPUs dedicated to real-time AI inference. These ECSs use the T4 INT8 calculator for up to 130 TOPS of INT8 performance. The Pi2 ECSs can also be used for light-load training.
+ Pi2 ECSs use NVIDIA Tesla T4 GPUs dedicated to real-time AI inference. These ECSs use the T4 INT8 calculator for up to 130 TOPS of INT8 performance. Pi2 ECSs can also be used for light-load training.
Specifications
Table 11 Pi2 ECS specificationsFlavor
@@ -1376,14 +1375,14 @@
Pi2 ECS Features
- CPU: 2nd Generation Intel® Xeon® Scalable 6278 processors (2.6 GHz of basic frequency and 3.5 GHz of turbo frequency), or Intel® Xeon® Scalable 6151 processors (3.0 GHz of basic frequency and 3.4 GHz of turbo frequency)
- Up to four NVIDIA Tesla T4 GPUs on an ECS
- GPU hardware passthrough
- Up to 8.1 TFLOPS of single-precision performance on a single GPU
- Up to 130 TOPS of INT8 performance on a single GPU
- 16 GiB of GDDR6 GPU memory with a bandwidth of 320 GiB/s on a single GPU
- Built-in one NVENC and two NVDECs
Supported Software
-Pi2 ECSs are used in GPU-based inference computing scenarios, such as image recognition, speech recognition, and natural language processing. The Pi2 ECSs can also be used for light-load training.
+Pi2 ECSs are used in GPU-based inference computing scenarios, such as image recognition, speech recognition, and natural language processing. Pi2 ECSs can also be used for light-load training.
Pi2 ECSs support the following commonly used software:
- Deep learning frameworks, such as TensorFlow, Caffe, PyTorch, and MXNet
Notes
-- 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 will be released after a Pi2 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
+ - 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 will be released after a Pi2 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop it.
- - Pi2 ECSs support automatic recovery when the hosts accommodating such ECSs become faulty.
- By default, Pi2 ECSs created using a Windows public image have the Tesla driver installed.
- By default, Pi2 ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- If a Pi2 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 Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous compute. Their specifications can only be changed to other specifications of the same instance type.
- GPU-accelerated ECSs do not support live migration.
+ - Pi2 ECSs support automatic recovery when the hosts accommodating such ECSs become faulty.
- By default, Pi2 ECSs created using a Windows public image have the Tesla driver installed.
- By default, Pi2 ECSs created using a Linux public image do not have a Tesla driver installed. After the ECS is created, install a driver on it for computing acceleration. For details, see Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- If a Pi2 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 Manually Installing a Tesla Driver on a GPU-accelerated ECS.
- Unlike general-purpose compute, GPU-accelerated ECSs deliver heterogeneous compute. Their specifications can only be modified within the same instance type.
- GPU-accelerated ECSs do not support live migration.
diff --git a/docs/ecs/umn/en-us_topic_0103285575.html b/docs/ecs/umn/en-us_topic_0103285575.html
index 1ac49181e..8b142ac5d 100644
--- a/docs/ecs/umn/en-us_topic_0103285575.html
+++ b/docs/ecs/umn/en-us_topic_0103285575.html
@@ -15,12 +15,12 @@
Using a Serial Number to Obtain the Disk Device Name (Windows)If a serial number is displayed on the console, use either of the following methods to obtain the disk name.
cmd
- - Start cmd in a Windows OS as an administrator and run either of the following commands:
wmic diskdrive get serialnumber
+- Start cmd in a Windows OS as an administrator and run any of the following commands:
wmic diskdrive get serialnumber
wmic path win32_physicalmedia get SerialNumber
wmic path Win32_DiskDrive get SerialNumber
A serial number is the first 20 digits of a disk UUID.
-For example, if the serial number of a VBD disk on the console is 97c876c0-54b3-460a-b, run either of the following commands to obtain the serial number of the disk on the ECS OS:
+For example, if the serial number of a VBD disk on the console is 97c876c0-54b3-460a-b, run any of the following commands to obtain the serial number of the disk on the ECS OS:
wmic diskdrive get serialnumber
wmic path win32_physicalmedia get SerialNumber
wmic path Win32_DiskDrive get SerialNumber
@@ -30,10 +30,10 @@
Figure 2 Checking the disk corresponding to the serial number
PowerShell
-- Start PowerShell as an administrator in a Windows OS.
- Run the following command to check the disk on which the logical disk is created:
- Windows Server 2012 or later
- Run the following command to check the disk on which the logical disk is created:
Get-CimInstance -ClassName Win32_LogicalDiskToPartition |select Antecedent, Dependent |fl
+- Start PowerShell as an administrator in a Windows OS.
- Check the disk on which the logical disk is created.
- Windows Server 2012 or later
- Run the following command to check the disk on which the logical disk is created:
Get-CimInstance -ClassName Win32_LogicalDiskToPartition |select Antecedent, Dependent |fl
As shown in Figure 3, the disk is Disk 0.
- Run the following command to view the mapping between the serial number and the disk:
Get-Disk |select Number, SerialNumber
-As shown in Figure 3, the disk is Disk 0.
+As shown in Figure 3, the serial number 97c876c0-54b3-460a-b is mapped to Disk 0.
Figure 3 Viewing the disk on which the logical disk is created
- Versions earlier than Windows 2012
- Run the following command to check the disk on which the logical disk is created:
Get-WmiObject -Class Win32_PhysicalMedia |select Tag, Serialnumber
diff --git a/docs/ecs/umn/en-us_topic_0105127983.html b/docs/ecs/umn/en-us_topic_0105127983.html
index a89f10c6f..b52aea2d6 100644
--- a/docs/ecs/umn/en-us_topic_0105127983.html
+++ b/docs/ecs/umn/en-us_topic_0105127983.html
@@ -1,7 +1,7 @@
Why Can't I Log In to My Linux ECS?
-SymptomA Linux ECS cannot be logged in to due to some reasons. For example, the network is abnormal, the firewall does not allow access to the local port for accessing the remote desktop, or the ECS vCPUs are overloaded.
+ SymptomA Linux ECS cannot be logged in to due to some reasons. For example, the network is abnormal, remote desktop access is blocked by the firewall on the ECS, or the ECS vCPUs are overloaded.
This section describes how to troubleshoot Linux ECS login failures.
If you cannot log in to your Linux ECS, follow the instructions provided in Checking the VNC Login. Then, locate the login fault by referring to Fault Locating.
@@ -11,7 +11,7 @@
- (Optional) When the system displays "Press CTRL+ALT+DELETE to log on", click Send CtrlAltDel in the upper part of the remote login page to log in to the ECS.
Do not press CTRL+ALT+DELETE on the physical keyboard because this operation does not take effect.
- If the VNC login still fails, record the resource details and fault occurred time for further fault locating and analysis.
+ If the VNC login still fails, record the resource details and fault occurrence time for further fault locating and analysis.
Fault LocatingIf you can log in to the ECS using VNC but cannot log in to it using a remote desktop connection, locate the fault by referring to this section.
The following fault causes are sequenced based on their occurrence probability.
@@ -107,7 +107,7 @@
Checking Whether the Security Group Is Correctly ConfiguredCheck whether the local host can access port 22 on the ECS.
Run the following command to check whether port 22 is accessible:
- telnet ECS private IP address
+ telnet <ECS-private-IP-address>
If port 22 is inaccessible, check whether port 22 is opened in the security group rule.
On the ECS details page, click the Security Groups tab and check that port 22 is configured in the inbound rule of the security group.
Figure 4 Checking remote access ports
@@ -123,7 +123,7 @@
Checking the IP Address Whitelist for SSH Logins (with HSS Enabled)After HSS is enabled, you can configure an IP address whitelist for SSH logins as required. The IP address whitelist controls SSH access to ECSs, effectively preventing account cracking.
After you configure the allowlist, SSH logins will be allowed only from IP addresses in the allowlist.
- - On the Events page, check whether a local host IP address is intercepted due to brute force cracking.
- Check whether the IP address whitelist for SSH logins has been enabled. If it has been enabled, ensure that the IP address of the local host has been added to the IP address whitelist.
- Before enabling this function, ensure that all IP addresses that need to initiate SSH logins are added to the allowlist. Otherwise, you cannot remotely log in to your ECS through SSH.
- Exercise caution when adding a local IP address to the allowlist. This will make HSS no longer restrict access from this IP address to your ECSs.
+ - On the Events page, check whether a local host IP address is intercepted due to brute force cracking.
- Check whether the IP address whitelist for SSH logins has been enabled. If it has been enabled, ensure that the IP address of the local host has been added to the IP address whitelist.
- Before enabling the whitelist to control SSH logins, ensure that all IP addresses that need to initiate SSH logins are added to the allowlist. Otherwise, you cannot remotely log in to your ECS through SSH.
- Exercise caution when adding a local IP address to the allowlist. This will make HSS no longer restrict access from this IP address to your ECSs.
For more details, see Configuring Server Login Protection.
@@ -138,10 +138,10 @@
You can also disable or uninstall the third-party antivirus software and try to remotely log in to the ECS again.
Checking Whether an Error Occurred During a Remote LoginIf an error message is displayed during remote login, check the operation guide based on the error information.
- If the fault persists, record the resource details and fault occurred time, and contact technical support for assistance.
+ If the fault persists, record the resource details and fault occurrence time, and contact technical support for assistance.
- If the fault persists after the preceding operations are performed, record the resource details and fault occurred time, and contact customer service for technical support.
+ If the fault persists after the preceding operations are performed, record the resource details and fault occurrence time, and contact customer service for technical support.
diff --git a/docs/ecs/umn/en-us_topic_0108255889.html b/docs/ecs/umn/en-us_topic_0108255889.html
index d60659aff..69bd76598 100644
--- a/docs/ecs/umn/en-us_topic_0108255889.html
+++ b/docs/ecs/umn/en-us_topic_0108255889.html
@@ -26,7 +26,7 @@
|
|---|
Procedure- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- View Failures on the right side of common operations above the ECS list.
Figure 1 Failures
+Procedure- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- View Failures on the right side of common operations above the ECS list.
Figure 1 Failures
- Click the number displayed in the Failures area to view task details.
- Creation Failures: show the failed ECS creation tasks.
- Operation Failures: show the tasks with failed operations and error codes, which help you troubleshoot the faults.
Constraints- Only stopped ECSs can be migrated.
- To ensure that the migration is successful, there must be an available DeH.
- CBR and CSBS backups are not affected by migrations.
- ECS IDs remain unchanged after a migration.
Procedure- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, locate the ECS to be migrated, choose More > View O&M and Monitoring > Reallocate ECS in the Operation column.
- In the displayed dialog box, select the target DeH.
If no DeHs are available, create a DeH first. For details, see Allocating DeHs in the Dedicated Host User Guide.
+ Procedure- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- In the ECS list, locate the ECS to be migrated, choose More > View O&M and Monitoring > Reallocate ECS in the Operation column.
- In the displayed dialog box, select the target DeH.
If no DeHs are available, create a DeH first. For details, see Allocating DeHs in the Dedicated Host User Guide.
- Click OK.
diff --git a/docs/ecs/umn/en-us_topic_0142266317.html b/docs/ecs/umn/en-us_topic_0142266317.html
index 48874ce12..24e649040 100644
--- a/docs/ecs/umn/en-us_topic_0142266317.html
+++ b/docs/ecs/umn/en-us_topic_0142266317.html
@@ -4,7 +4,7 @@
ScenariosAfter an ECS is created, you can change its name as needed.
Multiple ECS names can be changed in a batch. After the change is complete, the ECS names will be identical.
- Changing the Name of a Single ECS- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- Click the ECS for which you want to change the name.
The ECS details page is displayed.
+
diff --git a/docs/ecs/umn/en-us_topic_0177512565.html b/docs/ecs/umn/en-us_topic_0177512565.html
index 789968691..d866f8f94 100644
--- a/docs/ecs/umn/en-us_topic_0177512565.html
+++ b/docs/ecs/umn/en-us_topic_0177512565.html
@@ -786,437 +786,538 @@
|---|
- Table 3 S3 ECS specificationsFlavor
+Table 3 S3 ECS specificationsFlavor
|
-vCPUs
+ | vCPUs
|
-Memory
+ | Memory
(GiB)
|
-Max./Assured Network Bandwidth
+ | Max./Assured Network Bandwidth
(Gbit/s)
|
-Max. Network PPS
+ | Max. Network PPS
(10,000)
|
-Max. NIC Queues
+ | Network Connections
+(10,000)
|
-Max. NICs
+ | Max. NIC Queues
|
-Virtualization
+ | Max. NICs
|
-Hardware
+ | Max. EVS Disks
+ |
+Virtualization
+ |
+Hardware
|
|---|
-s3.medium.1
+ | s3.medium.1
|
-1
+ | 1
|
-1
+ | 1
|
-0.8/0.15
+ | 0.8/0.15
|
-10
+ | 10
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
|
-CPU: Intel® Xeon® Cascade Lake 6278
+ | 60
+ |
+KVM
+ |
+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
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.xlarge.1
+ | s3.xlarge.1
|
-4
+ | 4
|
-4
+ | 4
|
-2/0.5
+ | 2/0.5
|
-25
+ | 25
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.2xlarge.1
+ | s3.2xlarge.1
|
-8
+ | 8
|
-8
+ | 8
|
-3/1
+ | 3/1
|
-50
+ | 50
|
-2
+ | 200
|
-2
+ | 2
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.4xlarge.1
+ | s3.4xlarge.1
|
-16
+ | 16
|
-16
+ | 16
|
-6/2
+ | 6/2
|
-100
+ | 100
|
-4
+ | 200
|
-2
+ | 4
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.8xlarge.1
+ | s3.8xlarge.1
|
-32
+ | 32
|
-32
+ | 32
|
-8/2
+ | 8/2
|
-200
+ | 200
|
-8
+ | 200
|
-4
+ | 8
|
-KVM
+ | 4
+ |
+60
+ |
+KVM
|
-s3.medium.2
+ | s3.medium.2
|
-1
+ | 1
|
-2
+ | 2
|
-0.8/0.15
+ | 0.8/0.15
|
-10
+ | 10
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.large.2
+ | s3.large.2
|
-2
+ | 2
|
-4
+ | 4
|
-1.5/0.3
+ | 1.5/0.3
|
-15
+ | 15
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.xlarge.2
+ | s3.xlarge.2
|
-4
+ | 4
|
-8
+ | 8
|
-2/0.5
+ | 2/0.5
|
-25
+ | 25
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.2xlarge.2
+ | s3.2xlarge.2
|
-8
+ | 8
|
-16
+ | 16
|
-3/1
+ | 3/1
|
-50
+ | 50
|
-2
+ | 200
|
-2
+ | 2
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.4xlarge.2
+ | s3.4xlarge.2
|
-16
+ | 16
|
-32
+ | 32
|
-6/2
+ | 6/2
|
-100
+ | 100
|
-4
+ | 200
|
-2
+ | 4
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.8xlarge.2
+ | s3.8xlarge.2
|
-32
+ | 32
|
-64
+ | 64
|
-8/2
+ | 8/2
|
-200
+ | 200
|
-8
+ | 200
|
-4
+ | 8
|
-KVM
+ | 4
+ |
+60
+ |
+KVM
|
-s3.medium.4
+ | s3.medium.4
|
-1
+ | 1
|
-4
+ | 4
|
-0.8/0.15
+ | 0.8/0.15
|
-10
+ | 10
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.large.4
+ | s3.large.4
|
-2
+ | 2
|
-8
+ | 8
|
-1.5/0.3
+ | 1.5/0.3
|
-15
+ | 15
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.xlarge.4
+ | s3.xlarge.4
|
-4
+ | 4
|
-16
+ | 16
|
-2/0.5
+ | 2/0.5
|
-25
+ | 25
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.2xlarge.4
+ | s3.2xlarge.4
|
-8
+ | 8
|
-32
+ | 32
|
-3/1
+ | 3/1
|
-50
+ | 50
|
-2
+ | 200
|
-2
+ | 2
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.4xlarge.4
+ | s3.4xlarge.4
|
-16
+ | 16
|
-64
+ | 64
|
-6/2
+ | 6/2
|
-100
+ | 100
|
-4
+ | 200
|
-2
+ | 4
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.8xlarge.4
+ | s3.8xlarge.4
|
-32
+ | 32
|
-128
+ | 128
|
-8/2
+ | 8/2
|
-200
+ | 200
|
-8
+ | 200
|
-4
+ | 8
|
-KVM
+ | 4
+ |
+60
+ |
+KVM
|
-s3.medium.8
+ | s3.medium.8
|
-1
+ | 1
|
-8
+ | 8
|
-0.8/0.15
+ | 0.8/0.15
|
-10
+ | 10
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.large.8
+ | s3.large.8
|
-2
+ | 2
|
-16
+ | 16
|
-1.5/0.3
+ | 1.5/0.3
|
-15
+ | 15
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.xlarge.8
+ | s3.xlarge.8
|
-4
+ | 4
|
-32
+ | 32
|
-2/0.5
+ | 2/0.5
|
-25
+ | 25
|
-1
+ | 200
|
-2
+ | 1
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.2xlarge.8
+ | s3.2xlarge.8
|
-8
+ | 8
|
-64
+ | 64
|
-3/1
+ | 3/1
|
-50
+ | 50
|
-2
+ | 200
|
-2
+ | 2
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.4xlarge.8
+ | s3.4xlarge.8
|
-16
+ | 16
|
-128
+ | 128
|
-6/2
+ | 6/2
|
-100
+ | 100
|
-4
+ | 200
|
-2
+ | 4
|
-KVM
+ | 2
+ |
+60
+ |
+KVM
|
-s3.8xlarge.8
+ | s3.8xlarge.8
|
-32
+ | 32
|
-256
+ | 256
|
-8/2
+ | 8/2
|
-200
+ | 200
|
-8
+ | 200
|
-4
+ | 8
|
-KVM
+ | 4
+ |
+60
+ |
+KVM
|
@@ -3834,7 +3935,7 @@
Memory-optimizedFor more details, see Memory-optimized ECSs.
- Table 12 M9 ECS specificationsFlavor
+Table 12 M9 ECS specificationsFlavor
|
vCPUs
|
@@ -3995,7 +4096,7 @@
128
|
-1024
+ | 1,024
|
100/80
|
@@ -4016,7 +4117,7 @@
192
|
-1504
+ | 1,504
|
120/102
|
diff --git a/docs/ecs/umn/en-us_topic_0244854543.html b/docs/ecs/umn/en-us_topic_0244854543.html
index 83fa1785c..2d1896b6c 100644
--- a/docs/ecs/umn/en-us_topic_0244854543.html
+++ b/docs/ecs/umn/en-us_topic_0244854543.html
@@ -18,7 +18,7 @@
- In the Services window, restart Remote Desktop Services or the ECS.
- Use "IP address:Port" to remotely access the ECS.
LinuxThe following procedure uses an ECS running CentOS 7.3 as an example. The default login port of a Linux ECS is 22. To change it to port 2020, for example, do as follows:
- - Modify the security group rule.
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, select Elastic Cloud Server.
- On the ECS list, click the name of an ECS for which you want to modify the security group rule.
- On the ECS details page, click the security group in the Security Groups area to go to the security group details page.
- On the Inbound Rules tab, click Add Rule. In the displayed dialog box, set Protocol & Port as follows:
- Protocols: TCP (Custom ports)
- Port: 2020
+- Modify the security group rule.
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Under Computing, click Elastic Cloud Server.
- On the ECS list, click the name of an ECS for which you want to modify the security group rule.
- On the ECS details page, click the security group in the Security Groups area to go to the security group details page.
- On the Inbound Rules tab, click Add Rule. In the displayed dialog box, set Protocol & Port as follows:
- Protocols: TCP (Custom ports)
- Port: 2020
For details, see "Adding a Security Group Rule" in the Virtual Private Cloud User Guide.
- Log in to the ECS.
- Run the following command to edit the sshd configuration file:
vi /etc/ssh/sshd_config
|---|
|
|---|
|
|---|
|
|---|
|
|---|
|
|---|
|
|---|
|
|---|
| 
