diff --git a/docs/ecs/umn/ALL_META.TXT.json b/docs/ecs/umn/ALL_META.TXT.json
index f0e764d90..df0fac406 100644
--- a/docs/ecs/umn/ALL_META.TXT.json
+++ b/docs/ecs/umn/ALL_META.TXT.json
@@ -197,7 +197,7 @@
"node_id":"en-us_topic_0035550301.xml",
"product_code":"ecs",
"code":"11",
- "des":"M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced computing, security, and stability. Each M7n ECS can have a maximum number of 96 vC",
+ "des":"M9 ECSs use the Intel ® Xeon ® Scalable processors and KVM architecture to provide enhanced compute, network, and security performance to fulfill the high-performance and",
"doc_type":"usermanual",
"kw":"Memory-optimized ECSs,ECS Specifications,User Guide",
"search_title":"",
@@ -938,7 +938,7 @@
"node_id":"en-us_topic_0092494943.xml",
"product_code":"ecs",
"code":"50",
- "des":"Only a running ECS can be logged in to.Login usernames, passwords, and constraints vary depending on OSs running on the ECSs created using a public image. For details, se",
+ "des":"Only a running ECS can be logged in to.For ECSs created using public images, the login usernames, passwords, and constraints vary depending on OSs running on the ECSs. Fo",
"doc_type":"usermanual",
"kw":"Login Overview (Windows),Logging In to a Windows ECS,User Guide",
"search_title":"",
@@ -978,7 +978,7 @@
"code":"52",
"des":"This section describes how to use the remote login tool MSTSC to log in to a Windows ECS from a local computer.The target ECS is running.You have obtained the password fo",
"doc_type":"usermanual",
- "kw":"Logging In to a Windows ECS Using MSTSC,Logging In to a Windows ECS,User Guide",
+ "kw":"Logging In to a Windows ECS from a Windows Server,Logging In to a Windows ECS,User Guide",
"search_title":"",
"metedata":[
{
@@ -987,7 +987,7 @@
"opensource":"false;true"
}
],
- "title":"Logging In to a Windows ECS Using MSTSC",
+ "title":"Logging In to a Windows ECS from a Windows Server",
"githuburl":""
},
{
@@ -995,9 +995,9 @@
"node_id":"en-us_topic_0275383051.xml",
"product_code":"ecs",
"code":"53",
- "des":"This section describes how to log in to a Windows ECS from a Linux computer.The target ECS is running.The ECS must have an EIP bound.Access to port 3389 is allowed in the",
+ "des":"This section describes how to log in to a Windows ECS from a Linux server.The target ECS is running.The ECS must have an EIP bound.Access to port 3389 is allowed in the i",
"doc_type":"usermanual",
- "kw":"Logging In to a Windows ECS from a Linux Computer,Logging In to a Windows ECS,User Guide",
+ "kw":"Logging In to a Windows ECS from a Linux Server,Logging In to a Windows ECS,User Guide",
"search_title":"",
"metedata":[
{
@@ -1006,7 +1006,7 @@
"opensource":"false;true"
}
],
- "title":"Logging In to a Windows ECS from a Linux Computer",
+ "title":"Logging In to a Windows ECS from a Linux Server",
"githuburl":""
},
{
@@ -1033,7 +1033,7 @@
"node_id":"en-us_topic_0013771089.xml",
"product_code":"ecs",
"code":"55",
- "des":"Only a running ECS can be logged in to.For ECSs created using public images, login usernames, passwords, and constraints vary depending on OSs running on the ECSs. For de",
+ "des":"Only a running ECS can be logged in to.For ECSs created using public images, the login usernames, passwords, and constraints vary depending on OSs running on the ECSs. Fo",
"doc_type":"usermanual",
"kw":"Login Overview (Linux),Logging In to a Linux ECS,User Guide",
"search_title":"",
@@ -1071,7 +1071,7 @@
"node_id":"en-us_topic_0017955380.xml",
"product_code":"ecs",
"code":"57",
- "des":"This section describes how to use an SSH key pair to remotely log in to a Linux ECS from a Windows and a Linux server, respectively.You have obtained the private key file",
+ "des":"Key pairs (SSH key pairs) are a set of security credentials for identity authentication when you remotely log in to ECSs.A key pair consists of a public key and a private",
"doc_type":"usermanual",
"kw":"Logging In to a Linux ECS Using an SSH Key Pair,Logging In to a Linux ECS,User Guide",
"search_title":"",
@@ -1090,7 +1090,7 @@
"node_id":"en-us_topic_0017955633.xml",
"product_code":"ecs",
"code":"58",
- "des":"This section describes how to remotely log in to a Linux ECS using an SSH password from a Windows and a Linux server, respectively.Logging in to a Linux ECS using SSH pas",
+ "des":"This section describes how to use an SSH password to remotely log in to a Linux ECS from a Windows and a Linux server, respectively.Logging in to a Linux ECS using SSH pa",
"doc_type":"usermanual",
"kw":"Logging In to a Linux ECS Using an SSH Password,Logging In to a Linux ECS,User Guide",
"search_title":"",
@@ -1261,9 +1261,9 @@
"node_id":"en-us_topic_0042400609.xml",
"product_code":"ecs",
"code":"67",
- "des":"ECS metadata includes basic information of an ECS on the cloud platform, such as the ECS ID, hostname, and network information. ECS metadata can be obtained using either ",
+ "des":"ECS metadata is a special API that can be locally accessed in the ECS OS. It contains basic ECS details, such as the cloud server ID, hostname, and network details. With ",
"doc_type":"usermanual",
- "kw":"Obtaining Metadata,Obtaining Metadata and Passing User Data,User Guide",
+ "kw":"Obtaining ECS Details Using Metadata,Obtaining Metadata and Passing User Data,User Guide",
"search_title":"",
"metedata":[
{
@@ -1272,7 +1272,7 @@
"opensource":"false;true"
}
],
- "title":"Obtaining Metadata",
+ "title":"Obtaining ECS Details Using Metadata",
"githuburl":""
},
{
@@ -2306,9 +2306,9 @@
"node_id":"en-us_topic_0035643949.xml",
"product_code":"ecs",
"code":"122",
- "des":"Passwords are used to log in to ECSs. If you select the password login mode when creating an ECS, you can use the username and password to log in to your ECS. The passwor",
+ "des":"Passwords are used to log in to ECSs. If you select the password login mode when creating an ECS, you can use the username and password to log in to the ECS. The password",
"doc_type":"usermanual",
- "kw":"Application Scenarios for Using Passwords,Password Reset,User Guide",
+ "kw":"Overview of Password Reset,Password Reset,User Guide",
"search_title":"",
"metedata":[
{
@@ -2317,7 +2317,7 @@
"opensource":"false;true"
}
],
- "title":"Application Scenarios for Using Passwords",
+ "title":"Overview of Password Reset",
"githuburl":""
},
{
@@ -2327,7 +2327,7 @@
"code":"123",
"des":"This section describes how to reset the password for logging in to an ECS in the OS when the password is about to expire, the password is forgotten, or you are logging in",
"doc_type":"usermanual",
- "kw":"Resetting the Password for Logging In to an ECS in the OS,Password Reset,User Guide",
+ "kw":"Resetting the Password in the ECS OS,Password Reset,User Guide",
"search_title":"",
"metedata":[
{
@@ -2336,7 +2336,7 @@
"opensource":"false;true"
}
],
- "title":"Resetting the Password for Logging In to an ECS in the OS",
+ "title":"Resetting the Password in the ECS OS",
"githuburl":""
},
{
@@ -2384,7 +2384,7 @@
"code":"126",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
- "kw":"Obtaining and Deleting the Password of a Windows ECS",
+ "kw":"Obtaining and Deleting the Password for Logging In to a Windows ECS",
"search_title":"",
"metedata":[
{
@@ -2393,7 +2393,7 @@
"opensource":"false;true"
}
],
- "title":"Obtaining and Deleting the Password of a Windows ECS",
+ "title":"Obtaining and Deleting the Password for Logging In to a Windows ECS",
"githuburl":""
},
{
@@ -2403,7 +2403,7 @@
"code":"127",
"des":"Password authentication is required to log in to a Windows ECS. You must use the private key bound to the ECS when the ECS was created to obtain the administrator passwor",
"doc_type":"usermanual",
- "kw":"Obtaining the Password for Logging In to a Windows ECS,Obtaining and Deleting the Password of a Wind",
+ "kw":"Obtaining the Password for Logging In to a Windows ECS,Obtaining and Deleting the Password for Loggi",
"search_title":"",
"metedata":[
{
@@ -2420,9 +2420,9 @@
"node_id":"en-us_topic_0031107267.xml",
"product_code":"ecs",
"code":"128",
- "des":"After you obtain the initial password, it is a good practice to delete it to ensure system security.Deleting the initial password does not affect ECS operation or login. ",
+ "des":"After obtaining the initial password, you are advised to delete it from the system to ensure security.Deleting the initial password does not affect ECS running or login.O",
"doc_type":"usermanual",
- "kw":"Deleting the Initial Password for Logging In to a Windows ECS,Obtaining and Deleting the Password of",
+ "kw":"Deleting the Password for Logging In to a Windows ECS,Obtaining and Deleting the Password for Loggin",
"search_title":"",
"metedata":[
{
@@ -2431,7 +2431,7 @@
"opensource":"false;true"
}
],
- "title":"Deleting the Initial Password for Logging In to a Windows ECS",
+ "title":"Deleting the Password for Logging In to a Windows ECS",
"githuburl":""
},
{
@@ -2515,7 +2515,7 @@
"node_id":"en-us_topic_0000001278734873.xml",
"product_code":"ecs",
"code":"133",
- "des":"You need to import a key pair in either of the following scenarios:Create a key pair using PuTTYgen and import the public key to the ECS.Import the public key of an exist",
+ "des":"You need to import a key pair to the ECS when you:Create a key pair using puttygen.exe.Import the public key of an existing local key pair (for example, generated using P",
"doc_type":"usermanual",
"kw":"Importing a Key Pair,Key Pairs,User Guide",
"search_title":"",
@@ -2800,7 +2800,7 @@
"node_id":"en-us_topic_0116266207.xml",
"product_code":"ecs",
"code":"148",
- "des":"After you enable Cloud Trace Service (CTS) and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records (traces",
+ "des":"Cloud Trace Service (CTS) records operations performed on cloud service resources. A record contains information such as the user who performed the operation, IP address,",
"doc_type":"usermanual",
"kw":"Viewing Traces,Audit Using CTS,User Guide",
"search_title":"",
diff --git a/docs/ecs/umn/CLASS.TXT.json b/docs/ecs/umn/CLASS.TXT.json
index 296b0e62b..aef663aeb 100644
--- a/docs/ecs/umn/CLASS.TXT.json
+++ b/docs/ecs/umn/CLASS.TXT.json
@@ -90,7 +90,7 @@
"code":"10"
},
{
- "desc":"M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced computing, security, and stability. Each M7n ECS can have a maximum number of 96 vC",
+ "desc":"M9 ECSs use the Intel ® Xeon ® Scalable processors and KVM architecture to provide enhanced compute, network, and security performance to fulfill the high-performance and",
"product_code":"ecs",
"title":"Memory-optimized ECSs",
"uri":"en-us_topic_0035550301.html",
@@ -441,7 +441,7 @@
"code":"49"
},
{
- "desc":"Only a running ECS can be logged in to.Login usernames, passwords, and constraints vary depending on OSs running on the ECSs created using a public image. For details, se",
+ "desc":"Only a running ECS can be logged in to.For ECSs created using public images, the login usernames, passwords, and constraints vary depending on OSs running on the ECSs. Fo",
"product_code":"ecs",
"title":"Login Overview (Windows)",
"uri":"en-us_topic_0092494943.html",
@@ -461,16 +461,16 @@
{
"desc":"This section describes how to use the remote login tool MSTSC to log in to a Windows ECS from a local computer.The target ECS is running.You have obtained the password fo",
"product_code":"ecs",
- "title":"Logging In to a Windows ECS Using MSTSC",
+ "title":"Logging In to a Windows ECS from a Windows Server",
"uri":"en-us_topic_0017955381.html",
"doc_type":"usermanual",
"p_code":"49",
"code":"52"
},
{
- "desc":"This section describes how to log in to a Windows ECS from a Linux computer.The target ECS is running.The ECS must have an EIP bound.Access to port 3389 is allowed in the",
+ "desc":"This section describes how to log in to a Windows ECS from a Linux server.The target ECS is running.The ECS must have an EIP bound.Access to port 3389 is allowed in the i",
"product_code":"ecs",
- "title":"Logging In to a Windows ECS from a Linux Computer",
+ "title":"Logging In to a Windows ECS from a Linux Server",
"uri":"en-us_topic_0275383051.html",
"doc_type":"usermanual",
"p_code":"49",
@@ -486,7 +486,7 @@
"code":"54"
},
{
- "desc":"Only a running ECS can be logged in to.For ECSs created using public images, login usernames, passwords, and constraints vary depending on OSs running on the ECSs. For de",
+ "desc":"Only a running ECS can be logged in to.For ECSs created using public images, the login usernames, passwords, and constraints vary depending on OSs running on the ECSs. Fo",
"product_code":"ecs",
"title":"Login Overview (Linux)",
"uri":"en-us_topic_0013771089.html",
@@ -504,7 +504,7 @@
"code":"56"
},
{
- "desc":"This section describes how to use an SSH key pair to remotely log in to a Linux ECS from a Windows and a Linux server, respectively.You have obtained the private key file",
+ "desc":"Key pairs (SSH key pairs) are a set of security credentials for identity authentication when you remotely log in to ECSs.A key pair consists of a public key and a private",
"product_code":"ecs",
"title":"Logging In to a Linux ECS Using an SSH Key Pair",
"uri":"en-us_topic_0017955380.html",
@@ -513,7 +513,7 @@
"code":"57"
},
{
- "desc":"This section describes how to remotely log in to a Linux ECS using an SSH password from a Windows and a Linux server, respectively.Logging in to a Linux ECS using SSH pas",
+ "desc":"This section describes how to use an SSH password to remotely log in to a Linux ECS from a Windows and a Linux server, respectively.Logging in to a Linux ECS using SSH pa",
"product_code":"ecs",
"title":"Logging In to a Linux ECS Using an SSH Password",
"uri":"en-us_topic_0017955633.html",
@@ -594,9 +594,9 @@
"code":"66"
},
{
- "desc":"ECS metadata includes basic information of an ECS on the cloud platform, such as the ECS ID, hostname, and network information. ECS metadata can be obtained using either ",
+ "desc":"ECS metadata is a special API that can be locally accessed in the ECS OS. It contains basic ECS details, such as the cloud server ID, hostname, and network details. With ",
"product_code":"ecs",
- "title":"Obtaining Metadata",
+ "title":"Obtaining ECS Details Using Metadata",
"uri":"en-us_topic_0042400609.html",
"doc_type":"usermanual",
"p_code":"66",
@@ -1089,9 +1089,9 @@
"code":"121"
},
{
- "desc":"Passwords are used to log in to ECSs. If you select the password login mode when creating an ECS, you can use the username and password to log in to your ECS. The passwor",
+ "desc":"Passwords are used to log in to ECSs. If you select the password login mode when creating an ECS, you can use the username and password to log in to the ECS. The password",
"product_code":"ecs",
- "title":"Application Scenarios for Using Passwords",
+ "title":"Overview of Password Reset",
"uri":"en-us_topic_0035643949.html",
"doc_type":"usermanual",
"p_code":"121",
@@ -1100,7 +1100,7 @@
{
"desc":"This section describes how to reset the password for logging in to an ECS in the OS when the password is about to expire, the password is forgotten, or you are logging in",
"product_code":"ecs",
- "title":"Resetting the Password for Logging In to an ECS in the OS",
+ "title":"Resetting the Password in the ECS OS",
"uri":"en-us_topic_0122627689.html",
"doc_type":"usermanual",
"p_code":"121",
@@ -1127,7 +1127,7 @@
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"product_code":"ecs",
- "title":"Obtaining and Deleting the Password of a Windows ECS",
+ "title":"Obtaining and Deleting the Password for Logging In to a Windows ECS",
"uri":"en-us_topic_0000001234183498.html",
"doc_type":"usermanual",
"p_code":"121",
@@ -1143,9 +1143,9 @@
"code":"127"
},
{
- "desc":"After you obtain the initial password, it is a good practice to delete it to ensure system security.Deleting the initial password does not affect ECS operation or login. ",
+ "desc":"After obtaining the initial password, you are advised to delete it from the system to ensure security.Deleting the initial password does not affect ECS running or login.O",
"product_code":"ecs",
- "title":"Deleting the Initial Password for Logging In to a Windows ECS",
+ "title":"Deleting the Password for Logging In to a Windows ECS",
"uri":"en-us_topic_0031107267.html",
"doc_type":"usermanual",
"p_code":"126",
@@ -1188,7 +1188,7 @@
"code":"132"
},
{
- "desc":"You need to import a key pair in either of the following scenarios:Create a key pair using PuTTYgen and import the public key to the ECS.Import the public key of an exist",
+ "desc":"You need to import a key pair to the ECS when you:Create a key pair using puttygen.exe.Import the public key of an existing local key pair (for example, generated using P",
"product_code":"ecs",
"title":"Importing a Key Pair",
"uri":"en-us_topic_0000001278734873.html",
@@ -1323,7 +1323,7 @@
"code":"147"
},
{
- "desc":"After you enable Cloud Trace Service (CTS) and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records (traces",
+ "desc":"Cloud Trace Service (CTS) records operations performed on cloud service resources. A record contains information such as the user who performed the operation, IP address,",
"product_code":"ecs",
"title":"Viewing Traces",
"uri":"en-us_topic_0116266207.html",
diff --git a/docs/ecs/umn/en-us_image_0000002323933930.png b/docs/ecs/umn/en-us_image_0000002323933930.png
new file mode 100644
index 000000000..1909444d2
Binary files /dev/null and b/docs/ecs/umn/en-us_image_0000002323933930.png differ
diff --git a/docs/ecs/umn/en-us_image_0000002324093734.png b/docs/ecs/umn/en-us_image_0000002324093734.png
new file mode 100644
index 000000000..1909444d2
Binary files /dev/null and b/docs/ecs/umn/en-us_image_0000002324093734.png differ
diff --git a/docs/ecs/umn/en-us_image_0000001696838310.png b/docs/ecs/umn/en-us_image_0000002359774578.png
similarity index 100%
rename from docs/ecs/umn/en-us_image_0000001696838310.png
rename to docs/ecs/umn/en-us_image_0000002359774578.png
diff --git a/docs/ecs/umn/en-us_topic_0000001143214829.html b/docs/ecs/umn/en-us_topic_0000001143214829.html
index 5374ef614..77357d705 100644
--- a/docs/ecs/umn/en-us_topic_0000001143214829.html
+++ b/docs/ecs/umn/en-us_topic_0000001143214829.html
@@ -32,7 +32,7 @@
Configuring atop for CentOS 7/8, AlmaLinux, and Rocky Linux
- Run the following command to install atop:
yum install -y atop
- - Run the following command to modify the configuration file of atop:
vi /etc/default/atop
+ - Run the following command to modify the configuration file of atop:
vi /etc/sysconfig/atop
Modify the following parameters, save the modification, and exit:
- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGINTERVAL=15
@@ -90,18 +90,18 @@ Active: active (running)
Configuring atop for Ubuntu 20 and Debian 10
- Run the following command to install atop:
apt-get install -y atop
- Run the following command to modify the configuration file of atop:
vi /etc/default/atop
Modify the following parameters, save the modification, and exit:
-- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
+- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGINTERVAL=15
LOGGENERATIONS=3
- Restart the atop service (started by default) to apply the configuration:
systemctl restart atop atopacct
- Run the following command to check the status of atop. active (running) indicates that atop is running properly.
systemctl status atop atopacct
atop.service - Atop advanced performance monitor
Loaded: loaded (/etc/init.d/atop; enable; vendor preset: enabled)
-Active: active (running)
+Active: active (running)
atopacct.service - Atop process accounting daemon
Loaded: loaded (/usr/lib/systemd/system/atopacct.service; enabled; vendor preset: enabled)
-Active: active (running)
+Active: active (running)
- Run the following command to stop atop after troubleshooting to release the system and disk resources occupied by atop:
systemctl disable atop atopacct
systemctl stop atop atopacct
@@ -109,7 +109,7 @@ Active: active (running)
Configuring atop for Ubuntu 22 and Ubuntu 24
- Run the following command to install atop:
apt-get install -y atop
- Run the following command to modify the configuration file of atop:
vi /etc/default/atop
Modify the following parameters, save the modification, and exit:
-- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
+- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGINTERVAL=15
LOGGENERATIONS=3
- Restart the atop service (started by default) to apply the configuration:
systemctl restart atop atopacct atop-rotate.timer
@@ -132,7 +132,7 @@ Loaded: loaded (/usr/lib/systemd/system/atop-rotate.timer; enabled; vendor prese
Configuring atop for Debian 11 and Debian 12
- Run the following command to install atop:
apt-get install -y atop
- Run the following command to modify the configuration file of atop:
vi /etc/default/atop
Modify the following parameters, save the modification, and exit:
-- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
+- Change the value of LOGINTERVAL to, for example, 15. The default value of LOGINTERVAL is 600, in seconds.
- Change the value of LOGGENERATIONS to, for example, 3. The default retention period of atop logs is 28 days.
LOGINTERVAL=15
LOGGENERATIONS=3
- Restart the atop service (started by default) to apply the configuration:
systemctl restart atop atopacct atop-rotate.timer
diff --git a/docs/ecs/umn/en-us_topic_0000001234183498.html b/docs/ecs/umn/en-us_topic_0000001234183498.html
index 8cc96c248..67b12e098 100644
--- a/docs/ecs/umn/en-us_topic_0000001234183498.html
+++ b/docs/ecs/umn/en-us_topic_0000001234183498.html
@@ -1,13 +1,13 @@
-Obtaining and Deleting the Password of a Windows ECS
+Obtaining and Deleting the Password for Logging In to a Windows ECS
diff --git a/docs/ecs/umn/en-us_topic_0000001234335274.html b/docs/ecs/umn/en-us_topic_0000001234335274.html
index 1a961f636..4f518819b 100644
--- a/docs/ecs/umn/en-us_topic_0000001234335274.html
+++ b/docs/ecs/umn/en-us_topic_0000001234335274.html
@@ -24,7 +24,7 @@
- Save the private key, for example, kp-123.pem, locally.
-- After you have saved the key pair, import your public key to the ECS by referring to Importing a Key Pair.
+
- After the public key file and private key file are saved, import the public key to the system by referring to Importing a Key Pair.
diff --git a/docs/ecs/umn/en-us_topic_0000001278335673.html b/docs/ecs/umn/en-us_topic_0000001278335673.html
index a27d553c8..245257620 100644
--- a/docs/ecs/umn/en-us_topic_0000001278335673.html
+++ b/docs/ecs/umn/en-us_topic_0000001278335673.html
@@ -2,11 +2,11 @@
Application Scenarios for Using Key Pairs
Key Pairs
Key pairs (SSH key pairs) are a set of security credentials for identity authentication when you remotely log in to ECSs.
-
A key pair consists of a public key and a private key. Key Pair Service (KPS) stores the public key and you store the private key. If you have imported a public key into a Linux ECS, you can use the corresponding private key, rather than a password, to log in to the ECS. You do not need to worry about password interception, cracking, or leakage.
+
A key pair consists of a public key and a private key. Key Pair Service (KPS) stores the public key and you store the private key. If you have bound a public key to a Linux ECS, you can use the corresponding private key, rather than a password, to log in to the ECS. You do not need to worry about password interception, cracking, or leakage.
Scenarios
When purchasing an ECS, you are advised to select the key pair login mode. For Windows ECSs, key pairs are required to decrypt the passwords so that you can use the decrypted password to log in.
diff --git a/docs/ecs/umn/en-us_topic_0000001278350057.html b/docs/ecs/umn/en-us_topic_0000001278350057.html
index b35a94b98..657887a08 100644
--- a/docs/ecs/umn/en-us_topic_0000001278350057.html
+++ b/docs/ecs/umn/en-us_topic_0000001278350057.html
@@ -3,7 +3,7 @@
(Recommended) Creating a Key Pair on the Management Console
Scenarios
You can create a key pair on the management console. After the key pair is created, the public key is automatically stored in the system, and the private key is stored in your local computer. After a key pair is created for an ECS on the management console, ensure that you store your private key in a secure place. Without a private key, you will not be able to log in to the ECS.
-
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.
- In the navigation pane on the left, choose Key Pair.
- On the displayed page, click Create Key Pair.
- Enter a key pair name.
A key pair name consists of two parts: KeyPair and four random digits (KeyPair-xxxx).
+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 navigation pane on the left, choose Key Pair.
- On the displayed page, click Create Key Pair.
- Enter a key pair name.
A key pair name consists of two parts: KeyPair and four random digits (KeyPair-xxxx).
- Click OK.
- Manually or automatically download a .pem private key file with the name that you specify as the key name. Store it in a secure place and click OK.
This is the only chance for you to save the private key file. Keep it secure. You'll need to provide the key pair name when you create an ECS, and the corresponding private key each time you connect to the ECS through SSH.
diff --git a/docs/ecs/umn/en-us_topic_0000001278734873.html b/docs/ecs/umn/en-us_topic_0000001278734873.html
index 0b4f7cac3..d50579c3e 100644
--- a/docs/ecs/umn/en-us_topic_0000001278734873.html
+++ b/docs/ecs/umn/en-us_topic_0000001278734873.html
@@ -1,9 +1,9 @@
Importing a Key Pair
-
Scenarios
You need to import a key pair in either of the following scenarios:
-
- Create a key pair using PuTTYgen and import the public key to the ECS.
-
- Import the public key of an existing key pair to the ECS to let the system maintain your public key.
If the public key of the existing key pair is stored by clicking Save public key on PuTTY Key Generator, the public key cannot be imported to the management console.
+
Scenarios
You need to import a key pair to the ECS when you:
+
- Create a key pair using puttygen.exe.
+
- Import the public key of an existing local key pair (for example, generated using PuTTYgen) to let the system maintain your public key.
diff --git a/docs/ecs/umn/en-us_topic_0013771089.html b/docs/ecs/umn/en-us_topic_0013771089.html
index cd3b366a4..83a91b6dc 100644
--- a/docs/ecs/umn/en-us_topic_0013771089.html
+++ b/docs/ecs/umn/en-us_topic_0013771089.html
@@ -1,7 +1,7 @@
Login Overview (Linux)
-
Constraints
+
Login Modes
You can choose from a variety of login modes based on your local OS type.
diff --git a/docs/ecs/umn/en-us_topic_0017955380.html b/docs/ecs/umn/en-us_topic_0017955380.html
index ce00adf62..a0b39cb93 100644
--- a/docs/ecs/umn/en-us_topic_0017955380.html
+++ b/docs/ecs/umn/en-us_topic_0017955380.html
@@ -1,9 +1,12 @@
Logging In to a Linux ECS Using an SSH Key Pair
-
Scenarios
This section describes how to use an SSH key pair to remotely log in to a Linux ECS from a Windows and a Linux server, respectively.
+
Scenarios
Key pairs (SSH key pairs) are a set of security credentials for identity authentication when you remotely log in to ECSs.
+
A key pair consists of a public key and a private key. Key Pair Service (KPS) stores the public key and you store the private key. If you have bound a public key to a Linux ECS, you can use the corresponding private key, rather than a password, to log in to the ECS. You do not need to worry about password interception, cracking, or leakage.
+
For details, see Application Scenarios for Using Key Pairs.
+
This section describes how to use an SSH key pair to remotely log in to a Linux ECS from a Windows and a Linux server, respectively.
-
Prerequisites
+
- You have configured the inbound rules of the security group. For details, see Configuring Security Group Rules.
- The network connection between the login tool (PuTTY) and the target ECS is normal. For example, the default port 22 is not blocked by the firewall.
Logging In to a Linux ECS from a Local Windows Server
You have two methods to log in to a Linux ECS from a local Windows server.
@@ -16,14 +19,14 @@
Figure 1 Importing the private key file
- In the Actions area, click Save private key.
- Save the converted private key, for example, kp-123.ppk, to the local computer.
- Double-click PUTTY.EXE. The PuTTY Configuration page is displayed.
- Choose Session and enter the EIP of the ECS under Host Name (or IP address).
Figure 2 Configuring the EIP
- Choose Connection > Data. Enter the image username in Auto-login username.
Figure 3 Entering the username
-
- If a public image is used, see Public Image Introduction for the image username.
- If a private image is used, use the username of the private image.
+
- Choose Connection > SSH > Auth > Credentials. In the configuration item Private key file for authentication, click Browse and select the private key converted in step 6.
Figure 4 Importing the private key file
- Click Open to log in to the ECS.
Method 2: Use Xshell to log in to the ECS.
- Start the Xshell tool.
- Run the following command using the EIP to remotely log in to the ECS through SSH:
ssh Username@EIP
-
- If a public image is used, see Public Image Introduction for the image username.
- If a private image is used, use the username of the private image.
+
- (Optional) If the system displays the SSH Security Warning dialog box, click Accept & Save.
Figure 5 SSH Security Warning
- Select Public Key and click Browse beside the user key text box.
- In the user key dialog box, click Import.
- Select the locally stored key file and click Open.
- Click OK to log in to the ECS.
@@ -32,7 +35,7 @@
In the preceding command, replace path with the actual path where the key file is saved.
- Run the following command to log in to the ECS:
ssh -i /path/kp-123.pem Default username@EIP
-For example, if the default username is root and the EIP is 123.123.123.123, run the following command:
+For example, if the default username is root and the EIP is 123.123.123.123, run the following command:
ssh -i /path/kp-123.pem root@123.123.123.123
In the preceding command:
- path refers to the path under which the key file is stored.
- EIP is the EIP bound to the ECS.
diff --git a/docs/ecs/umn/en-us_topic_0017955381.html b/docs/ecs/umn/en-us_topic_0017955381.html
index 12c4d6035..342403ca9 100644
--- a/docs/ecs/umn/en-us_topic_0017955381.html
+++ b/docs/ecs/umn/en-us_topic_0017955381.html
@@ -1,26 +1,25 @@
-
Logging In to a Windows ECS Using MSTSC
+
Logging In to a Windows ECS from a Windows Server
Scenarios
This section describes how to use the remote login tool MSTSC to log in to a Windows ECS from a local computer.
Prerequisites
-
- Access to port 3389 is allowed in the inbound direction of the security group which the ECS belongs to. For details, see Configuring Security Group Rules.
- The network connection between the login tool and the target ECS is normal. For example, the default port 3389 is not blocked by the firewall.
- Remote Desktop Protocol (RDP) needs to be enabled on the target ECS. For ECSs created using public images, RDP has been enabled by default. For instructions about how to enable RDP, see Enabling RDP.
+
- Access to port 3389 is allowed in the inbound direction of the security group that the ECS belongs to. For details, see Configuring Security Group Rules.
- The network connection between the login tool and the target ECS is normal. For example, the default port 3389 is not blocked by the firewall.
- Remote Desktop Protocol (RDP) needs to be enabled on the target ECS. For ECSs created using public images, RDP has been enabled by default. For instructions about how to enable RDP, see Enabling RDP.
Logging In to a Windows ECS Using MSTSC
If your local server runs Windows, you can use the remote desktop connection tool MSTSC delivered with the Windows OS to log in to a Windows ECS.
- Click the start menu on the local server.
- In the Search programs and files text box, enter mstsc.
- In the Remote Desktop Connection dialog box, click Show Options.
Figure 1 Showing options
- Enter the EIP and username (Administrator by default) of the target ECS.
If you do not want to enter the username and password in follow-up logins, select Allow me to save credentials.
Figure 2 Remote Desktop Connection
- - (Optional) To use local server resources in a remote session, configure parameters on the Local Resources tab.
To copy data from the local server to your ECS, select
Clipboard.
Figure 3 Clipboard
+
- (Optional) To use local server resources in a remote session, configure parameters on the Local Resources tab.
To copy data from the local server to your ECS, select
Clipboard.
Figure 3 Selecting the clipboard
-To copy files from the local server to your ECS, click
More and select your desired disks.
Figure 4 Drives
+
To copy files from the local server to your ECS, click
More and select your desired disks.
Figure 4 Selecting drives
- (Optional) Click the Display tab and then adjust the size of the remote desktop.
Figure 5 Adjusting the size of the desktop
- - Click Connect and enter the login password as prompted to log in to the ECS.
To ensure system security, change the login password after you log in to the ECS for the first time.
- - (Optional) Copy local files to the Windows ECS using clipboard. If the file size is greater than 2 GB, an error will occur.
To resolve this issue, see troubleshooting cases.
+ - Click Connect and enter the login password as prompted to log in to the ECS.
To ensure system security, change the login password after you log in to the ECS for the first time.
-Enabling RDP
For your first login, use VNC to log in and enable RDP for your ECS. Then, use MSTSC to log in.
By default, RDP has been enabled on the ECSs created using a public image.
+
Enabling RDP
For your first login, use VNC to log in and enable RDP for your ECS. Then, use MSTSC to log in.
RDP is enabled by default for ECSs created using public images.
- Log in to the Windows ECS using VNC.
For details, see Logging In to a Windows ECS Using VNC.
- Click Start in the task bar and choose Control Panel > System and Security > System > Remote settings.
The System Properties dialog box is displayed.
diff --git a/docs/ecs/umn/en-us_topic_0017955633.html b/docs/ecs/umn/en-us_topic_0017955633.html
index 66004a9fe..b2a9e842a 100644
--- a/docs/ecs/umn/en-us_topic_0017955633.html
+++ b/docs/ecs/umn/en-us_topic_0017955633.html
@@ -1,12 +1,12 @@
Logging In to a Linux ECS Using an SSH Password
-Scenarios
This section describes how to remotely log in to a Linux ECS using an SSH password from a Windows and a Linux server, respectively.
+
Scenarios
This section describes how to use an SSH password to remotely log in to a Linux ECS from a Windows and a Linux server, respectively.
Logging in to a Linux ECS using SSH password authentication is disabled by default. If you require password authentication, configure it after logging in to the ECS. To ensure system security, reset the common user password for logging in to the Linux ECS after configuring SSH password authentication.
-
Prerequisites
- The target ECS is running.
- You have bound an EIP to the ECS. For details, see Binding an EIP.
-
- Access to port 22 is allowed in the inbound direction of the security group which the ECS belongs to. For details, see Configuring Security Group Rules.
- The network connection between the login tool (PuTTY) and the target ECS is normal. For example, the default port 22 is not blocked by the firewall.
- You have obtained the SSH login permission and reset the common user password for logging in to the Linux ECS. For details, see Configuring the Login Permission Using SSH Password Authentication.
+
Prerequisites
- The target ECS is running.
- You have bound an EIP to the ECS. For details, see Binding an EIP.
+
- Access to port 22 is allowed in the inbound direction of the security group that the ECS belongs to. For details, see Configuring Security Group Rules.
- The network connection between the login tool (PuTTY) and the target ECS is normal. For example, the default port 22 is not blocked by the firewall.
- You have obtained the SSH login permission and reset the common user password for logging in to the Linux ECS. For details, see Configuring the Login Permission Using SSH Password Authentication.
Configuring the Login Permission Using SSH Password Authentication
Assigning the remote login permission using SSH key authentication
- Use the SSH key to log in to the Linux ECS. For details, see Logging In to a Linux ECS Using an SSH Key Pair.
- Run the following command to change the value of PasswordAuthentication in /etc/ssh/sshd_config to yes:
sudo vi /etc/ssh/sshd_config
@@ -29,10 +29,11 @@
Logging In to a Linux ECS from a Local Windows Server
To log in to a Linux ECS from a local Windows server, perform the operations below.
The following operations use PuTTY as an example to log in to the ECS.
- Visit the following website and download PuTTY and PuTTYgen:
https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
- - Run PuTTY.
- Choose Session.
- Host Name (or IP address): Enter the EIP bound to the ECS.
- Port: Enter 22.
- Connection type: Click SSH.
- Saved Sessions: Enter the task name, which can be clicked for remote connection when you use PuTTY next time.
Figure 1 Session
+ - Run PuTTY.
- Choose Session.
- Host Name (or IP address): Enter the EIP bound to the ECS.
- Port: Enter 22.
- Connection type: Click SSH.
- Saved Sessions: Enter the task name, which can be clicked for remote connection when you use PuTTY next time.
Figure 1 Session
- Choose Window. Then, select UTF-8 for Received data assumed to be in which character set: in Translation.
- Click Open.
If you log in to the ECS for the first time, PuTTY displays a security warning dialog box, asking you whether to accept the ECS security certificate. Click Yes to save the certificate to your local registry.
- - After the SSH connection to the ECS is set up, enter the username and password as prompted to log in to the ECS.
+ - After the SSH connection to the ECS is set up, enter the username and password as prompted to log in to the ECS.
+
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:
ssh xx.xx.xx.xx
@@ -43,7 +44,8 @@ ECDSA key fingerprint is SHA256:rnKuzrUSYS03MCoaxx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'xx.xx.xx.xx' (ECDSA) to the list of known hosts.
- - Enter the password for logging in to ECS.
+
- Enter the password for logging in to ECS.
+
diff --git a/docs/ecs/umn/en-us_topic_0021426802.html b/docs/ecs/umn/en-us_topic_0021426802.html
index 0f94aa737..6ab9ae3e8 100644
--- a/docs/ecs/umn/en-us_topic_0021426802.html
+++ b/docs/ecs/umn/en-us_topic_0021426802.html
@@ -1,6 +1,6 @@
-
Resetting the Password for Logging In to a Windows ECS
+
Resetting the Password for Logging In to a Windows ECS
Scenarios
You can reset your ECS password if:
- The password is forgotten.
- The password has expired.
The method described in this section can only be used to change the password of a local Windows account, but not the password of a domain account.
@@ -12,7 +12,7 @@
Download the ntfs-3g and chntpw software packages of the version required by the temporary ECS OS.
-
Procedure
- Stop the original ECS and detach the system disk.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, click Elastic Cloud Server.
- Stop the original Windows ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the Windows ECS. Otherwise, password reset may fail.
+
Procedure
- Stop the original ECS and detach the system disk.
- Log in to the management console.
- Click
in the upper left corner and select a region and project. - Under Computing, click Elastic Cloud Server.
- Stop the original Windows ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the Windows ECS. Otherwise, password reset may fail.
- Locate the row containing the system disk to be detached and click Detach to detach the system disk from the ECS.
- Attach the system disk to the temporary ECS.
- On the temporary ECS details page, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the system disk detached in step 1.e and attach it to the temporary ECS.
- Remotely log in to the temporary ECS.
- Run the following command to view the directory of the system disk detached from the original Windows ECS now attached to the temporary ECS:
fdisk -l
@@ -44,7 +44,7 @@ Write hive files? (y/n) [n] : y
0<SAM> - OK
- Stop the temporary ECS, detach the system disk, and attach the system disk to the original Windows ECS.
- Stop the temporary ECS, go to the ECS details page, and click the Disks tab.
- Click Detach to detach the data disk temporarily attached in step 2.b.
- On the original Windows ECS details page, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the data disk detached in step 4.b and attach it to the original ECS as the system disk.
- - Start the original Windows ECS and set a new login password.
- Click Start to start the original Windows ECS. After the status becomes Running, click Remote Login in the Operation column.
- Click Start. Enter CMD in the search box and press Enter.
- Run the following command to set a new password. The new password must meet the password complexity requirements described in Application Scenarios for Using Passwords.
net user Administrator New password
+ - Start the original Windows ECS and set a new login password.
- Click Start to start the original Windows ECS. After the status becomes Running, click Remote Login in the Operation column.
- Click Start. Enter CMD in the search box and press Enter.
- Run the following command to set a new password. The new password must meet the password complexity requirements described in Overview of Password Reset.
net user Administrator new-password
diff --git a/docs/ecs/umn/en-us_topic_0021427650.html b/docs/ecs/umn/en-us_topic_0021427650.html
index 9812700da..988b3abea 100644
--- a/docs/ecs/umn/en-us_topic_0021427650.html
+++ b/docs/ecs/umn/en-us_topic_0021427650.html
@@ -1,6 +1,6 @@
-
Resetting the Password for Logging In to a Linux ECS
+
Resetting the Password for Logging In to a Linux ECS
Scenarios
Keep your password secure. Reset the password if:
- The password is forgotten.
- The password has expired.
This section describes how to reset the password of user root. After resetting the password, you can log in to the ECS, and change the private key or reset the password of a non-root user.
@@ -9,7 +9,7 @@
Procedure
- Download the script for resetting the password and upload the script to the temporary ECS.
Contact customer service to obtain the password reset script. Use a connection tool, such as WinSCP, to upload the obtained changepasswd.sh script to the temporary ECS.
To download WinSCP, log in at https://winscp.net/.
- - Stop the original Linux ECS, detach the system disk from it, and attach the system disk to the temporary ECS.
- Log in to the management console.
- Click
in the upper left corner and select your region and project. - Under Computing, click Elastic Cloud Server.
- Stop the original ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the original ECS. Otherwise, password reset may fail.
+
- Stop the original Linux ECS, detach the system disk from it, and attach the system disk to the temporary 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.
- Stop the original ECS, switch to the page providing details about the ECS, and click the Disks tab.
Do not forcibly stop the original ECS. Otherwise, password reset may fail.
- Locate the row containing the system disk to be detached and click Detach to detach the system disk from the ECS.
- Attach the system disk to the temporary ECS.
- On the page providing details about the temporary ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the system disk detached in step 2.e and attach it to the temporary ECS.
@@ -25,8 +25,8 @@
- (Optional) Enable remote root login for non-root users.
vi /etc/ssh/sshd_config
Modify the following settings:
-- Change PasswordAuthentication no to PasswordAuthentication yes.
Alternatively, uncomment PasswordAuthentication yes.
- - Change PermitRootLogin no to PermitRootLogin yes.
Alternatively, uncomment PermitRootLogin yes.
+- Change PasswordAuthentication no to PasswordAuthentication yes.
Alternatively, delete the comment tag (#) before PasswordAuthentication yes.
+ - Change PermitRootLogin no to PermitRootLogin yes.
Alternatively, delete the comment tag (#) before PermitRootLogin yes.
- Change the value of AllowUsers to root.
Search for AllowUsers in the file. If AllowUsers is missing, add AllowUsers root at the end of the file.
- Stop the temporary ECS, detach the system disk, attach the system disk to the original Linux ECS, and restart the original Linux ECS.
- Stop the temporary ECS, switch to the page providing details about the ECS, and click the Disks tab.
- Click Detach to detach the data disk temporarily attached in step 3.
- On the page providing details about the original Linux ECS, click the Disks tab.
- Click Attach Disk. In the displayed dialog box, select the data disk detached in 6.b.
diff --git a/docs/ecs/umn/en-us_topic_0027268511.html b/docs/ecs/umn/en-us_topic_0027268511.html
index 470ea191c..e3047d7b2 100644
--- a/docs/ecs/umn/en-us_topic_0027268511.html
+++ b/docs/ecs/umn/en-us_topic_0027268511.html
@@ -6,7 +6,7 @@
-Login Notes
- When you log in to the ECS using VNC, four types of keyboards will be used. These are described in Table 1.
+
Login Notes
- When you log in to the ECS using VNC, four types of keyboards will be used, as described in Table 1.
Table 1 Keyboard typesKeyboard Type
|
Description
@@ -61,7 +61,7 @@
|
ECS OS Keyboard
|
-Permission
+ | Supported
|
@@ -718,9 +718,9 @@
Log In to a Windows ECS Using a Non-English Keyboard
- Log in to the management console.
- Click
in the upper left corner and select a region and project. - Under Computing, click Elastic Cloud Server.
- Obtain the password for logging in to the ECS.
Before logging in to the ECS, you must have the login password.
For instructions about how to obtain the password for logging in to a Windows ECS, see Obtaining the Password for Logging In to a Windows ECS.
- - In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID, and click
for search. - Locate the row containing the ECS and click Remote Login in the Operation column.
- In the displayed Configure Keyboard Layout for Remote Login dialog box, select the keyboard that suits your language.
- When logging in to the ECS using VNC for the first time, select the default English keyboard. The ECS OS uses the English keyboard by default.
- If you have changed the keyboard language of the ECS OS, select the keyboard language to which you have changed.
+ - In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID, and click
for search. - Locate the row containing the ECS and click Remote Login in the Operation column.
- In the displayed Configure Keyboard Layout for Remote Login dialog box, select the keyboard that suits your language.
- When logging in to the ECS using VNC for the first time, select the default English keyboard. The ECS OS uses the English keyboard by default.
- If you have changed the keyboard language of the ECS OS, select the keyboard language to which you have changed.
Figure 5 Keyboard layout configuration
-
- Click Remote Login.
- (Optional) If you have changed the system language, in the displayed dialog box, click Remote Login.
Figure 6 Remote Login
+
- Click Remote Login.
- (Optional) If you have changed the system language, in the displayed dialog box, click Remote Login.
Figure 6 Remote Login
- (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.
Figure 7 Send CtrlAltDel
- (Optional) If you need your cursor to be displayed on the remote login page, click Local Cursor.
Figure 8 Local Cursor
- Enter the ECS password as prompted.
- When logging in to the ECS using VNC for the first time, use the English keyboard to enter the password. After you have logged in to the ECS, see Changing the OS Keyboard Language to change the keyboard language of the ECS OS. You can then select the keyboard language and enter the password the next time you log in.
- If you have changed the keyboard language of the ECS OS, ensure that the keyboard language in use, the keyboard language selected in step 7, and the changed OS keyboard language are all the same.
diff --git a/docs/ecs/umn/en-us_topic_0030878383.html b/docs/ecs/umn/en-us_topic_0030878383.html
index 0025647bd..278700a03 100644
--- a/docs/ecs/umn/en-us_topic_0030878383.html
+++ b/docs/ecs/umn/en-us_topic_0030878383.html
@@ -11,11 +11,11 @@
- Configure required parameters.
You can click + to add more inbound rules.
Figure 1 Adding inbound rules
-Table 1 Inbound rule parameter descriptionParameter
+Table 1 Inbound rule parameter descriptionParameter
|
-Description
+ | Description
|
-Example Value
+ | Example Value
|
@@ -29,7 +29,7 @@
Action
|
-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
@@ -48,7 +48,7 @@
| The network protocol and port used to match traffic in a security group rule.
- The network protocol used to match traffic in a security group rule.
Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.
- |
Protocol: TCP
@@ -81,9 +81,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
|
@@ -110,7 +110,7 @@
The network protocol and port used to match traffic in a security group rule.
- The network protocol used to match traffic in a security group rule.
Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.
-
+- The port or port range over which traffic can leave your ECS. The value can be from 1 to 65535.
|
Protocol: TCP
22, 22-30
diff --git a/docs/ecs/umn/en-us_topic_0030888079.html b/docs/ecs/umn/en-us_topic_0030888079.html
index 97a91f374..71299fbcc 100644
--- a/docs/ecs/umn/en-us_topic_0030888079.html
+++ b/docs/ecs/umn/en-us_topic_0030888079.html
@@ -8,9 +8,9 @@
- Logging In to a Windows ECS Using VNC
-- Logging In to a Windows ECS Using MSTSC
+ - Logging In to a Windows ECS from a Windows Server
-- Logging In to a Windows ECS from a Linux Computer
+ - Logging In to a Windows ECS from a Linux Server
diff --git a/docs/ecs/umn/en-us_topic_0031073513.html b/docs/ecs/umn/en-us_topic_0031073513.html
index f1c4ce233..ed95a9c6d 100644
--- a/docs/ecs/umn/en-us_topic_0031073513.html
+++ b/docs/ecs/umn/en-us_topic_0031073513.html
@@ -4,15 +4,15 @@
diff --git a/docs/ecs/umn/en-us_topic_0031107266.html b/docs/ecs/umn/en-us_topic_0031107266.html
index 5ddf8629b..dd03498f8 100644
--- a/docs/ecs/umn/en-us_topic_0031107266.html
+++ b/docs/ecs/umn/en-us_topic_0031107266.html
@@ -1,7 +1,7 @@
Obtaining the Password for Logging In to a Windows ECS
- ScenariosPassword authentication is required to log in to a Windows ECS. You must use the private key bound to the ECS when the ECS was created to obtain the administrator password generated during the ECS creation. The administrator user is Administrator or the user configured using Cloudbase-Init. This password is randomly generated, offering high security.
+ ScenariosPassword authentication is required to log in to a Windows ECS. You must use the private key bound to the ECS when the ECS was created to obtain the administrator password generated during the ECS creation. The administrator user is Administrator or the user configured using Cloudbase-Init. This password is randomly generated, which is secure.
You can obtain the initial password for logging in to a Windows ECS through the management console or APIs. For details, see this section.
PrerequisitesYou have obtained the private key file (.pem file) which was generated during the ECS creation.
@@ -10,7 +10,7 @@
- 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 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.
@@ -21,7 +21,7 @@
diff --git a/docs/ecs/umn/en-us_topic_0031107267.html b/docs/ecs/umn/en-us_topic_0031107267.html
index b9953d334..1317e0ef1 100644
--- a/docs/ecs/umn/en-us_topic_0031107267.html
+++ b/docs/ecs/umn/en-us_topic_0031107267.html
@@ -1,8 +1,10 @@
-Deleting the Initial Password for Logging In to a Windows ECS
-ScenariosAfter you obtain the initial password, it is a good practice to delete it to ensure system security.
- Deleting the initial password does not affect ECS operation or login. Once deleted, the password cannot be retrieved. Before you delete a password, it is a good practice to record it.
+ Deleting the Password for Logging In to a Windows ECS
+ ScenariosAfter obtaining the initial password, you are advised to delete it from the system to ensure security.
+ Deleting the initial password does not affect ECS running or login.
+ 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.
Figure 1 Delete Password
@@ -11,7 +13,7 @@
diff --git a/docs/ecs/umn/en-us_topic_0032380449.html b/docs/ecs/umn/en-us_topic_0032380449.html
index 12d1a0d4b..d8ddaa186 100644
--- a/docs/ecs/umn/en-us_topic_0032380449.html
+++ b/docs/ecs/umn/en-us_topic_0032380449.html
@@ -9,7 +9,7 @@
- Windows
- The image that is used to create ECSs must have Cloudbase-Init installed.
- The user data to be specified must be less than or equal to 32 KB.
- If user data is uploaded as text, the data can contain only ASCII characters. If user data is uploaded using a file, the file can contain any characters and the file size cannot exceed 32 KB.
- The image that is used to create ECSs must be a public image, a private image created based on a public image, or a private image with Cloudbase-Init installed.
- DHCP must be enabled on the VPC network, and port 80 must be enabled for the security group in the outbound direction.
- Injecting User Data- Create a user data script that complies with user data script specifications. For details, see Helpful Links.
- When creating an ECS, set Advanced Options to Configure now, and paste the content of the user data script to the User Data text box or upload the user data file.
You can inject user data to an ECS as text or as a file.
+ Injecting User Data- Create a user-data script that complies with user-data script specifications. For details, see Helpful Links.
- When creating an ECS, set Advanced Options to Configure now, and paste the content of the user data script to the User Data text box or upload the user data file.
You can inject user data to an ECS as text or as a file.
Text: Copy the content of the user data script to the text box.
File: Save the user data script to a text file and then upload the file.
@@ -71,7 +71,7 @@ echo "Hello, the time is now $(date -R)" | tee /root/output.txt
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 user data script.
#cloud-config
bootcmd:
@@ -129,7 +129,7 @@ echo "Hello, Powershell Test" > C:\aaaa.txt
Case 1This case illustrates how to inject user data to simplify Linux ECS configurations.
- To enable syntax highlighting, display line numbers, and set the tab stop to 4 for Vim, create a .vimrc configuration file and inject it into the /root/.vimrc directory during ECS creation. After the ECS is created, vim is automatically configured based on your requirements. This improves ECS configuration efficiency, especially in batch ECS creation scenarios.
+ In Vim, to enable syntax highlighting, display line numbers, and set tab to 4 spaces, create a .vimrc script and inject it into the /root/.vimrc directory during ECS creation. After the ECS is created, vim is automatically configured based on your requirements. This improves ECS configuration efficiency, especially in batch ECS creation scenarios.
User data example:
#cloud-config
write_files:
diff --git a/docs/ecs/umn/en-us_topic_0035550301.html b/docs/ecs/umn/en-us_topic_0035550301.html
index 515930cc5..8e5c6ab65 100644
--- a/docs/ecs/umn/en-us_topic_0035550301.html
+++ b/docs/ecs/umn/en-us_topic_0035550301.html
@@ -1,602 +1,868 @@
Memory-optimized ECSs
-Overview- M7n ECSs use the third-generation Intel® Xeon® Scalable processors to provide enhanced computing, 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 computing applications.
- 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 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.
+ Overview- M9 ECSs use the Intel ® Xeon ® Scalable processors and KVM architecture 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 computing, 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 computing applications.
- 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 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.
Specifications
- Table 1 M7n ECS specificationsFlavor
+Table 1 M9 ECS specificationsFlavor
|
-vCPUs
+ | vCPUs
|
-Memory
+ | Memory
+(GiB)
+ |
+Max./Assured Network Bandwidth
+(Gbit/s)
+ |
+PPS
+(10,000)
+ |
+Network Connections
+(10,000)
+ |
+Max. NIC Queues
+ |
+Max. NICs
+ |
+Max. Supplementary NICs
+ |
+Max. EVS Disk Bandwidth (Gbit/s)
+(Gbit/s)
+ |
+Max. EVS Disk IOPS (10,000)
+ |
+Virtualization
+ |
+
+
+m9.large.8
+ |
+2
+ |
+16
+ |
+20/3
+ |
+100
+ |
+75
+ |
+2
+ |
+2
+ |
+16
+ |
+11
+ |
+11
+ |
+KVM
+ |
+
+m9.xlarge.8
+ |
+4
+ |
+32
+ |
+20/5
+ |
+160
+ |
+200
+ |
+4
+ |
+3
+ |
+32
+ |
+11
+ |
+11
+ |
+
+m9.2xlarge.8
+ |
+8
+ |
+64
+ |
+20/8
+ |
+200
+ |
+300
+ |
+8
+ |
+8
+ |
+64
+ |
+11
+ |
+11
+ |
+
+m9.4xlarge.8
+ |
+16
+ |
+128
+ |
+30/12
+ |
+350
+ |
+400
+ |
+16
+ |
+8
+ |
+128
+ |
+11
+ |
+11
+ |
+
+m9.8xlarge.8
+ |
+32
+ |
+256
+ |
+40/25
+ |
+700
+ |
+600
+ |
+32
+ |
+8
+ |
+256
+ |
+11
+ |
+11
+ |
+
+m9.16xlarge.8
+ |
+64
+ |
+512
+ |
+60/40
+ |
+1,000
+ |
+700
+ |
+64
+ |
+8
+ |
+256
+ |
+21
+ |
+23
+ |
+
+m9.32xlarge.8
+ |
+128
+ |
+1024
+ |
+100/80
+ |
+2,000
+ |
+1,000
+ |
+64
+ |
+10
+ |
+256
+ |
+43
+ |
+46
+ |
+
+m9.48xlarge.8
+ |
+192
+ |
+1504
+ |
+120/102
+ |
+4,000
+ |
+1,000
+ |
+64
+ |
+12
+ |
+256
+ |
+64
+ |
+70
+ |
+
+
+
+
+
+Table 2 M7n ECS specificationsFlavor
+ |
+vCPUs
+ |
+Memory
(GiB)
|
-Max./Assured Bandwidth
+ | Max./Assured Network Bandwidth
(Gbit/s)
|
-Max. PPS
+ | PPS
(10,000)
|
-Max. NIC Queues
+ | Network Connections
+(10,000)
|
-Max. NICs
+ | Max. NIC Queues
|
-EVS Basic Bandwidth/Burst Bandwidth
+ | Max. NICs
+ |
+Max./Assured EVS Disk Bandwidth
(Gbit/s)
|
-Virtualization
+ | Max. EVS Disk IOPS (10,000)
+ |
+Virtualization
|
-m7n.large.8
+ | m7n.large.8
|
-2
+ | 2
|
-16
+ | 16
|
-4/0.8
+ | 4/0.8
|
-40
+ | 40
|
-2
+ | 50
|
-2
+ | 2
|
-1.5/6
+ | 2
|
-KVM
+ | 6/1.5
+ |
+16
+ |
+KVM
|
-m7n.xlarge.8
+ | m7n.xlarge.8
|
-4
+ | 4
|
-32
+ | 32
|
-8/1.6
+ | 8/1.6
|
-80
+ | 80
|
-2
+ | 50
|
-3
+ | 2
|
-2/6
+ | 3
|
-KVM
+ | 6/2
+ |
+16
+ |
+KVM
|
-m7n.2xlarge.8
+ | m7n.2xlarge.8
|
-8
+ | 8
|
-64
+ | 64
|
-15/3
+ | 15/3
|
-150
+ | 150
|
-4
+ | 100
|
-4
+ | 4
|
-3/6
+ | 4
|
-KVM
+ | 6/3
+ |
+16
+ |
+KVM
|
-m7n.3xlarge.8
+ | m7n.3xlarge.8
|
-12
+ | 12
|
-96
+ | 96
|
-17/5
+ | 17/5
|
-200
+ | 200
|
-4
+ | 150
|
-6
+ | 4
|
-4/6
+ | 6
|
-KVM
+ | 6/4
+ |
+16
+ |
+KVM
|
-m7n.4xlarge.8
+ | m7n.4xlarge.8
|
-16
+ | 16
|
-128
+ | 128
|
-20/6
+ | 20/6
|
-280
+ | 280
|
-8
+ | 150
|
-8
+ | 8
|
-5/6
+ | 8
|
-KVM
+ | 6/5
+ |
+16
+ |
+KVM
|
-m7n.6xlarge.8
+ | m7n.6xlarge.8
|
-24
+ | 24
|
-192
+ | 192
|
-25/9
+ | 25/9
|
-400
+ | 400
|
-8
+ | 200
|
-8
+ | 8
|
-6/None
+ | 8
|
-KVM
+ | None/6
+ |
+16
+ |
+KVM
|
-m7n.8xlarge.8
+ | m7n.8xlarge.8
|
-32
+ | 32
|
-256
+ | 256
|
-30/12
+ | 30/12
|
-550
+ | 550
|
-16
+ | 300
|
-8
+ | 16
|
-8/None
+ | 8
|
-KVM
+ | None/8
+ |
+16
+ |
+KVM
|
-m7n.12xlarge.8
+ | m7n.12xlarge.8
|
-48
+ | 48
|
-384
+ | 384
|
-35/18
+ | 35/18
|
-750
+ | 750
|
-16
+ | 400
|
-8
+ | 16
|
-12/None
+ | 8
|
-KVM
+ | None/12
+ |
+16
+ |
+KVM
|
-m7n.16xlarge.8
+ | m7n.16xlarge.8
|
-64
+ | 64
|
-512
+ | 512
|
-36/24
+ | 36/24
|
-800
+ | 800
|
-28
+ | 500
|
-8
+ | 28
|
-16/None
+ | 8
|
-KVM
+ | None/16
+ |
+16
+ |
+KVM
|
-m7n.24xlarge.8
+ | m7n.24xlarge.8
|
-96
+ | 96
|
-768
+ | 768
|
-40/36
+ | 40/36
|
-850
+ | 850
|
-32
+ | 800
|
-8
+ | 32
|
-24/None
+ | 8
|
-KVM
+ | None/24
+ |
+22.5
+ |
+KVM
|
-Table 2 M4 ECS specificationsFlavor
+Table 3 M4 ECS specificationsFlavor
|
-vCPUs
+ | vCPUs
|
-Memory
+ | Memory
(GiB)
|
-Max./Assured Bandwidth
+ | Max./Assured Network Bandwidth
(Gbit/s)
|
-Max. PPS
+ | PPS
(10,000)
|
-Max. NIC Queues
+ | Max. NIC Queues
|
-Max. NICs
+ | Max. NICs
|
-Virtualization
+ | Virtualization
|
-Hardware
+ | Hardware
|
-m4.medium.8
+ | m4.medium.8
|
-1
+ | 1
|
-8
+ | 8
|
-2/0.6
+ | 2/0.6
|
-20
+ | 20
|
-2
+ | 2
|
-2
+ | 2
|
-KVM
+ | KVM
|
-CPU: Intel® Xeon® Cascade Lake 6266
+ | CPU: Intel® Xeon® Cascade Lake 6266
|
-m4.large.8
+ | m4.large.8
|
-2
+ | 2
|
-16
+ | 16
|
-4/1.2
+ | 4/1.2
|
-40
+ | 40
|
-2
+ | 2
|
-2
+ | 2
|
-KVM
+ | KVM
|
-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 3 M3 ECS specificationsFlavor
+Table 4 M3 ECS specificationsFlavor
|
-vCPUs
+ | vCPUs
|
-Memory
+ | Memory
(GiB)
|
-Max./Assured Bandwidth
+ | Max./Assured Network Bandwidth
(Gbit/s)
|
-Max. PPS
+ | PPS
(10,000)
|
-Max. NIC Queues
+ | Max. NIC Queues
|
-Max. NICs
+ | Max. NICs
|
-EVS Basic Bandwidth
+ | EVS Basic Bandwidth
(Gbit/s)
|
-Virtualization
+ | Virtualization
|
-Hardware
+ | Hardware
|
-m3.medium.8
+ | m3.medium.8
|
-1
+ | 1
|
-8
+ | 8
|
-0.75/0.3
+ | 0.75/0.3
|
-15
+ | 15
|
-2
+ | 2
|
-12
+ | 12
|
-0.5
+ | 0.5
|
-KVM
+ | KVM
|
-CPU: Intel® Xeon® Skylake 6151
+ | CPU: Intel® Xeon® Skylake 6151
|
-m3.large.8
+ | m3.large.8
|
-2
+ | 2
|
-16
+ | 16
|
-1.5/0.6
+ | 1.5/0.6
|
-30
+ | 30
|
-2
+ | 2
|
-12
+ | 12
|
-1
+ | 1
|
-KVM
+ | KVM
|
-m3.xlarge.8
+ | m3.xlarge.8
|
-4
+ | 4
|
-32
+ | 32
|
-3/1.1
+ | 3/1.1
|
-50
+ | 50
|
-2
+ | 2
|
-12
+ | 12
|
-1.5.
+ | 1.5.
|
-KVM
+ | KVM
|
-m3.2xlarge.8
+ | m3.2xlarge.8
|
-8
+ | 8
|
-64
+ | 64
|
-5/2
+ | 5/2
|
-90
+ | 90
|
-4
+ | 4
|
-12
+ | 12
|
-2
+ | 2
|
-KVM
+ | KVM
|
-m3.4xlarge.8
+ | m3.4xlarge.8
|
-16
+ | 16
|
-128
+ | 128
|
-10/4.5
+ | 10/4.5
|
-130
+ | 130
|
-4
+ | 4
|
-12
+ | 12
|
-3
+ | 3
|
-KVM
+ | KVM
|
-m3.8xlarge.8
+ | m3.8xlarge.8
|
-32
+ | 32
|
-256
+ | 256
|
-15/9
+ | 15/9
|
-260
+ | 260
|
-8
+ | 8
|
-12
+ | 12
|
-4
+ | 4
|
-KVM
+ | KVM
|
-m3.15xlarge.8
+ | m3.15xlarge.8
|
-60
+ | 60
|
-512
+ | 512
|
-17/17
+ | 17/17
|
-500
+ | 500
|
-16
+ | 16
|
-12
+ | 12
|
-8
+ | 8
|
-KVM
+ | KVM
|
@@ -605,9 +871,9 @@
Scenarios- High-performance relational (MySQL) and NoSQL (MongoDB and Cassandra) databases
- Distributed web scale cache stores that provide in-memory caching of key-value type data (Memcached and Redis)
- Applications processing big unstructured data in real time (financial services, Hadoop/Spark clusters)
- High-performance computing (HPC) and electronic design automation (EDA)
-NotesTable 4 lists the OSs supported by memory-optimized ECSs.
+ NotesTable 5 lists the OSs supported by memory-optimized ECSs.
- Table 4 Supported OS versionsOS
+Table 5 Supported OS versionsOS
|
Version
|
diff --git a/docs/ecs/umn/en-us_topic_0035643949.html b/docs/ecs/umn/en-us_topic_0035643949.html
index 50d57e755..98044aff3 100644
--- a/docs/ecs/umn/en-us_topic_0035643949.html
+++ b/docs/ecs/umn/en-us_topic_0035643949.html
@@ -1,48 +1,51 @@
-Application Scenarios for Using Passwords
-Passwords are used to log in to ECSs. If you select the password login mode when creating an ECS, you can use the username and password to log in to your ECS. The password is very important. Keep it secure.
- You can reset the password when:
- - You forgot the password.
- The password has expired.
- You selected Set password later during the ECS creation.
- Table 1 provides guidance on how to reset your password in different scenarios.
+ Overview of Password Reset
+ What Is a Password?Passwords are used to log in to ECSs. If you select the password login mode when creating an ECS, you can use the username and password to log in to the ECS. The password is very important. Keep it secure.
+ You can set a password when creating an ECS. If you do not set a password during the creation or if the password is lost or expired, you can reset the password.
+ You can reset the password in any of the following scenarios: - The password is lost.
- The password has expired.
- You intend to change the initial password at the first login.
- You selected Set password later or Key pair for Login Mode during ECS creation.
+
+
+ Password Reset ScenariosTable 1 describes the methods of resetting passwords for ECSs.
- Table 1 Resetting a passwordScenario
+
-BackgroundTable 2 shows the ECS password complexity requirements.
+
+Password Complexity RequirementsTable 2 shows the ECS password complexity requirements.
- Table 2 Password complexity requirementsParameter
+Table 2 Password complexity requirementsParameter
|
-Requirement
+ | Requirement
|
-Password
+ | Password
|
-- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
+- Consists of 8 to 26 characters.
- Contains at least three of the following character types:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters: $!@%-_=+[]:./^,{}?
- Cannot contain the username or the username spelled backwards.
- Cannot contain more than two consecutive characters in the same sequence as they appear in the username. (This requirement applies only to Windows ECSs.)
|
|
diff --git a/docs/ecs/umn/en-us_topic_0041169567.html b/docs/ecs/umn/en-us_topic_0041169567.html
index 1fe2807e2..704c33359 100644
--- a/docs/ecs/umn/en-us_topic_0041169567.html
+++ b/docs/ecs/umn/en-us_topic_0041169567.html
@@ -8,7 +8,19 @@
-2025-06-16
+ | 2025-08-20
+ |
+Modified the following content:
+Added M9 ECSs in Memory-optimized ECSs.
+ |
+
+2025-08-06
+ |
+Modified the following content:
+Added C9 ECSs in Dedicated General-Purpose ECSs.
+ |
+
+2025-06-16
|
Modified the following content:
Added pi5e.2xlarge.4 and pi5e.12xlarge.4 to GPU-accelerated ECSs.
@@ -200,7 +212,7 @@
| 2022-04-20
|
Optimized the content in "Passwords and Key Pairs".
-- Added the following content:
+
|
@@ -342,7 +354,7 @@
2019-03-06
|
Modified the following content:
-
+
|
2019-03-05
@@ -476,7 +488,7 @@
| 2018-07-31
|
Added the following content:
-
+
Modified the following content:
|
@@ -716,7 +728,7 @@
Added the following content:
Modified the following content:
-
+
|
2016-09-30
diff --git a/docs/ecs/umn/en-us_topic_0042400609.html b/docs/ecs/umn/en-us_topic_0042400609.html
index 883e41e5c..1ae14f3fc 100644
--- a/docs/ecs/umn/en-us_topic_0042400609.html
+++ b/docs/ecs/umn/en-us_topic_0042400609.html
@@ -1,22 +1,24 @@
-Obtaining Metadata
-ScenariosECS metadata includes basic information of an ECS on the cloud platform, such as the ECS ID, hostname, and network information. ECS metadata can be obtained using either OpenStack or EC2 compatible APIs, as shown in Table 1. The following describes the URI and methods of using the supported ECS metadata.
+ Obtaining ECS Details Using Metadata
+ ScenariosECS metadata is a special API that can be locally accessed in the ECS OS. It contains basic ECS details, such as the cloud server ID, hostname, and network details. With ECS metadata, you can exchange basic information in an ECS and configure and manage the ECS OS and applications more conveniently and securely. Metadata allows you to configure information in the OS during initialization and obtain ECS information during service running.
+ ECS metadata supports OpenStack and EC2 compatible types, as shown in Table 1.
+ The following describes the URI and methods of using the supported ECS metadata.
NotesIf the metadata contains sensitive data, take appropriate measures to protect the sensitive data, for example, controlling access permissions and encrypting the data.
- Perform the following configuration on the firewall:
- - Windows
If you need to assign permissions only to the administrator to access custom data, enable the firewall as an administrator and run the following commands in PowerShell:
+Example configurations on the firewall are listed below:
+- Windows
To only allow the administrator to access custom data, enable the firewall as the administrator and run the following commands in PowerShell:
PS C:\>$RejectPrincipal = New-Object -TypeName System.Security.Principal.NTAccount ("Everyone")
PS C:\>$RejectPrincipalSID = $RejectPrincipal.Translate([System.Security.Principal.SecurityIdentifier]).Value
PS C:\>$ExceptPrincipal = New-Object -TypeName System.Security.Principal.NTAccount ("Administrator")
PS C:\>$ExceptPrincipalSID = $ExceptPrincipal.Translate([System.Security.Principal.SecurityIdentifier]).Value
PS C:\>$PrincipalSDDL = "O:LSD:(D;;CC;;;$ExceptPrincipalSID)(A;;CC;;;$RejectPrincipalSID)"
PS C:\>New-NetFirewallRule -DisplayName "Reject metadata service for $($RejectPrincipal.Value), exception: $($ExceptPrincipal.Value)" -Action block -Direction out -Protocol TCP -RemoteAddress 169.254.169.254 -LocalUser $PrincipalSDDL
- - Linux
If you need to assign permissions only to user root to access custom data, run the following command as user root:
+ - Linux
To only allow user root to access custom data, run the following command as user root:
iptables --append OUTPUT --proto tcp --destination 169.254.169.254 --match owner ! --uid-owner root --jump REJECT
- ECS Metadata TypesTable 1 does not contain the following EC2-compatible metadata items: ami-id, ami-launch-index, ami-manifest-path, block-device-mapping/, instance-action, instance-id, reservation-id, ramdisk-id, and kernel-id. These metadata items are meaningless and are not recommended.
+ ECS Metadata TypesTable 1 does not contain the following EC2-compatible metadata items: ami-id, ami-launch-index, ami-manifest-path, block-device-mapping, instance-action, instance-id, reservation-id, ramdisk-id, and kernel-id. These metadata items are meaningless and not recommended.
Table 1 ECS metadata typesMetadata Type
|
@@ -29,7 +31,7 @@
|---|
OpenStack
|
-/meta_data.json
+ | /openstack/latest/meta_data.json
|
Displays ECS metadata.
For the key fields in the ECS metadata, see Table 2.
@@ -37,7 +39,7 @@
|
OpenStack
|
-/password
+ | /openstack/latest/password
|
Displays the password for logging in to an ECS.
This metadata is used by Cloudbase-Init to store ciphertext passwords during initialization of key-pair-authenticated Windows ECSs.
@@ -45,23 +47,23 @@
|
OpenStack
|
-/user_data
+ | /openstack/latest/user_data
|
Displays ECS user data.
-This metadata allows you to specify scripts and configuration files for initializing ECSs. For details, see Injecting User Data.
+You can specify scripts and configuration files for ECS initialization as required. User-defined data is read and parsed by software such as Cloud-Init or Cloudbase-Init. For details, see Injecting User Data.
For password-authenticated Linux ECSs, this metadata is used to save password injection scripts.
|
OpenStack
|
-/network_data.json
+ | /openstack/latest/network_data.json
|
Displays ECS network information.
|
OpenStack
|
-/securitykey
+ | /openstack/latest/securitykey
|
Obtains temporary AKs and SKs.
Before enabling an ECS to obtain a temporary AK and SK, authorize agency permissions to the op_svc_ecs account and ECSs in IAM.
@@ -70,76 +72,76 @@
|
-EC2-compatible
+ | EC2 compatible
|
-/meta-data/hostname
+ | /latest/meta-data/hostname
|
Displays the name of the host accommodating an ECS.
To remove the suffix .novalocal from an ECS, see:
Is an ECS Hostname with Suffix .novalocal Normal?
|
-EC2-compatible
+ | EC2 compatible
|
-/meta-data/local-hostname
+ | /latest/meta-data/local-hostname
|
-The meaning of this field is the same as that of hostname.
+ | Has the same meaning as hostname.
|
-EC2-compatible
+ | EC2 compatible
|
-/meta-data/public-hostname
+ | /latest/meta-data/public-hostname
|
-The meaning of this field is the same as that of hostname.
+ | Has the same meaning as hostname.
|
-EC2-compatible
+ | EC2 compatible
|
-/meta-data/instance-type
+ | /latest/meta-data/instance-type
|
Displays an ECS flavor.
|
-EC2-compatible
+ | EC2 compatible
|
-/meta-data/local-ipv4
+ | /latest/meta-data/local-ipv4
|
Displays the fixed IP address of an ECS.
If there are multiple NICs, only the IP address of the primary NIC is displayed.
|
-EC2-compatible
+ | EC2 compatible
|
-/meta-data/placement/availability-zone
+ | /latest/meta-data/placement/availability-zone
|
Displays the AZ accommodating an ECS.
|
-EC2-compatible
+ | EC2 compatible
|
-/meta-data/public-ipv4
+ | /latest/meta-data/public-ipv4
|
Displays the EIP bound to the ECS.
If there are multiple NICs, only the EIP of the primary NIC is displayed.
|
-EC2-compatible
+ | EC2 compatible
|
-/meta-data/public-keys/0/openssh-key
+ | /latest/meta-data/public-keys/0/openssh-key
|
Displays the public key of an ECS.
|
-EC2-compatible
+ | EC2 compatible
|
-/user-data
+ | /latest/user-data
|
-Displays ECS user data.
+ | Displays ECS user data. It is used the same way as user-data in the OpenStack metadata type.
|
-EC2-compatible
+ | EC2 compatible
|
-/meta-data/security-groups
+ | /latest/meta-data/security-groups
|
Displays the security group of an ECS.
|
@@ -148,7 +150,7 @@
- Table 2 Metadata key fieldsParameter
+Table 2 metadata key fieldsParameter
|
Type
|
@@ -197,7 +199,7 @@
Metadata (OpenStack Metadata API)This API is used to query ECS metadata.
- URI
/169.254.169.254/openstack/latest/meta_data.json
- - Usage method
Supports GET requests.
+ - Usage method
GET request
- Example
To use cURL to view Linux ECS metadata, run the following command:
curl http://169.254.169.254/openstack/latest/meta_data.json
To use Invoke-RestMethod to view Windows ECS metadata, run the following command:
@@ -227,12 +229,13 @@
User Data (OpenStack Metadata API)This API is used to query ECS user data. The value is configured only when you create an ECS. It cannot be changed after the configuration.
- URI
/169.254.169.254/openstack/latest/user_data
- - Usage method
Supports GET requests.
+ - Usage method
GET request
- Example
Linux:
curl http://169.254.169.254/openstack/latest/user_data
Windows:
Invoke-RestMethod http://169.254.169.254/openstack/latest/user_data
-ICAgICAgDQoiQSBjbG91ZCBkb2VzIG5vdCBrbm93IHdoeSBpdCBtb3ZlcyBpbiBqdXN0IHN1Y2ggYSBkaXJlY3Rpb24gYW5kIGF0IHN1Y2ggYSBzcGVlZC4uLkl0IGZlZWxzIGFuIGltcHVsc2lvbi4uLnRoaXMgaXMgdGhlIHBsYWNlIHRvIGdvIG5vdy4gQnV0IHRoZSBza3kga25vd3MgdGhlIHJlYXNvbnMgYW5kIHRoZSBwYXR0ZXJucyBiZWhpbmQgYWxsIGNsb3VkcywgYW5kIHlvdSB3aWxsIGtub3csIHRvbywgd2hlbiB5b3UgbGlmdCB5b3Vyc2VsZiBoaWdoIGVub3VnaCB0byBzZWUgYmV5b25kIGhvcml6b25zLiINCg0KLVJpY2hhcmQgQmFjaA==
+#!/bin/bash
+echo "Hello, the time is now $(date -R)" | tee /root/output.txt
If user data was not passed to the ECS during ECS creation, the query result is 404. Figure 1 404 Not Found
@@ -289,17 +292,18 @@
User Data (EC2 Compatible API)This API is used to query ECS user data. The value is configured only when you create an ECS. It cannot be changed after the configuration.
- URI
/169.254.169.254/latest/user-data
- - Usage method
Supports GET requests.
+ - Usage method
GET request
- Example
Linux:
curl http://169.254.169.254/latest/user-data
Windows:
Invoke-RestMethod http://169.254.169.254/latest/user-data
-ICAgICAgDQoiQSBjbG91ZCBkb2VzIG5vdCBrbm93IHdoeSBpdCBtb3ZlcyBpbiBqdXN0IHN1Y2ggYSBkaXJlY3Rpb24gYW5kIGF0IHN1Y2ggYSBzcGVlZC4uLkl0IGZlZWxzIGFuIGltcHVsc2lvbi4uLnRoaXMgaXMgdGhlIHBsYWNlIHRvIGdvIG5vdy4gQnV0IHRoZSBza3kga25vd3MgdGhlIHJlYXNvbnMgYW5kIHRoZSBwYXR0ZXJucyBiZWhpbmQgYWxsIGNsb3VkcywgYW5kIHlvdSB3aWxsIGtub3csIHRvbywgd2hlbiB5b3UgbGlmdCB5b3Vyc2VsZiBoaWdoIGVub3VnaCB0byBzZWUgYmV5b25kIGhvcml6b25zLiINCg0KLVJpY2hhcmQgQmFjaA==
+#!/bin/bash
+echo "Hello, the time is now $(date -R)" | tee /root/output.txt
Hostname (EC2 Compatible API)This API is used to query the name of the host accommodating an ECS. The .novalocal suffix will be added later.
Instance Type (EC2 Compatible API)This API is used to query an ECS flavor.
Local IPv4 (EC2 Compatible API)This API is used to query the fixed IP address of an ECS. If there are multiple NICs, only the IP address of the primary NIC is displayed.
Availability Zone (EC2 Compatible API)This API is used to query the AZ accommodating an ECS.
Public IPv4 (EC2 Compatible API)This API is used to query the EIP bound to an ECS. If there are multiple NICs, only the EIP of the primary NIC is displayed.
Public Keys (EC2 Compatible API)This API is used to query the public key of an ECS.
- URI
/169.254.169.254/latest/meta-data/public-keys/0/openssh-key
- - Usage method
Supports GET requests.
+ - Usage method
GET request
- Example
Linux:
curl http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key
Windows:
diff --git a/docs/ecs/umn/en-us_topic_0048642616.html b/docs/ecs/umn/en-us_topic_0048642616.html
index 26b0b3a02..2ea44e880 100644
--- a/docs/ecs/umn/en-us_topic_0048642616.html
+++ b/docs/ecs/umn/en-us_topic_0048642616.html
@@ -10,7 +10,7 @@
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 Metadata.
+ - 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 AS
diff --git a/docs/ecs/umn/en-us_topic_0091224748.html b/docs/ecs/umn/en-us_topic_0091224748.html
index f1e7ce8e3..03b8d8013 100644
--- a/docs/ecs/umn/en-us_topic_0091224748.html
+++ b/docs/ecs/umn/en-us_topic_0091224748.html
@@ -6,6 +6,7 @@
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 packets per second (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.
X1e ECSs deliver powerful and stable compute. They use Intel® Xeon® Scalable processors and high-performance networks to provide high performance and stability for enterprise-grade applications.
+ C9 ECSs use the next-generation processors and KVM virtualization to provide enhanced computing, network, and security performance for high-load scenarios such as databases, gaming, and HPC.
Scenarios- C7n ECSs are suitable for:
- Medium- and heavy-load enterprise applications with strict requirements on computing and network performance, such as web applications, e-commerce platforms, short video platforms, online games, and insurance and finance.
@@ -13,410 +14,539 @@
- 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
- X1e ECSs are suitable for:
- Small- and medium-sized databases that require high stability
- Cache and search clusters
- Enterprise-grade applications
+ - C9 ECSs are suitable for:
- Databases that require high performance and low latency
- Gaming applications that require high performance and stability
- High-performance computing (HPC) applications such as electronic design automation (EDA) and scientific computing
- Internet communication that requires high PPS, such as on-screen comments and real-time voice
Specifications
- Table 1 C7n ECS specificationsFlavor
+Table 1 C7n ECS specificationsFlavor
|
-vCPUs
+ | vCPUs
|
-Memory
+ | Memory
(GiB)
|
-Max./Assured Bandwidth
+ | Max./Assured Bandwidth
(Gbit/s)
|
-Max. PPS
+ | PPS
(10,000)
|
-Max. NIC Queues
+ | Network Connections
+(10,000)
|
-Max. NICs
+ | Max. NIC Queues
|
-Max. Supplementary NICs
+ | Max. NICs
|
-Virtualization
+ | Max. Supplementary NICs
+ |
+Max./Assured EVS Disk Bandwidth
+(Gbit/s)
+ |
+Max. EVS Disk IOPS (10,000)
+ |
+Virtualization
|
-c7n.large.2
+ | c7n.large.2
|
-2
+ | 2
|
-4
+ | 4
|
-4/0.8
+ | 4/0.8
|
-40
+ | 40
|
-2
+ | 50
|
-2
+ | 2
|
-16
+ | 2
|
-KVM
+ | 16
+ |
+6/1.5
+ |
+16
+ |
+KVM
|
-c7n.xlarge.2
+ | c7n.xlarge.2
|
-4
+ | 4
|
-8
+ | 8
|
-8/1.6
+ | 8/1.6
|
-80
+ | 80
|
-2
+ | 50
|
-3
+ | 2
|
-32
+ | 3
|
-KVM
+ | 32
+ |
+6/2
+ |
+16
+ |
+KVM
|
-c7n.2xlarge.2
+ | c7n.2xlarge.2
|
-8
+ | 8
|
-16
+ | 16
|
-15/3
+ | 15/3
|
-150
+ | 150
|
-4
+ | 100
|
-4
+ | 4
|
-64
+ | 4
|
-KVM
+ | 64
+ |
+6/3
+ |
+16
+ |
+KVM
|
-c7n.3xlarge.2
+ | c7n.3xlarge.2
|
-12
+ | 12
|
-24
+ | 24
|
-17/5
+ | 17/5
|
-200
+ | 200
|
-4
+ | 150
|
-6
+ | 4
|
-96
+ | 6
|
-KVM
+ | 96
+ |
+6/4
+ |
+16
+ |
+KVM
|
-c7n.4xlarge.2
+ | c7n.4xlarge.2
|
-16
+ | 16
|
-32
+ | 32
|
-20/6
+ | 20/6
|
-280
+ | 280
|
-8
+ | 150
|
-8
+ | 8
|
-128
+ | 8
|
-KVM
+ | 128
+ |
+6/5
+ |
+16
+ |
+KVM
|
-c7n.6xlarge.2
+ | c7n.6xlarge.2
|
-24
+ | 24
|
-48
+ | 48
|
-25/9
+ | 25/9
|
-400
+ | 400
|
-8
+ | 200
|
-8
+ | 8
|
-192
+ | 8
|
-KVM
+ | 192
+ |
+None/6
+ |
+16
+ |
+KVM
|
-c7n.8xlarge.2
+ | c7n.8xlarge.2
|
-32
+ | 32
|
-64
+ | 64
|
-30/12
+ | 30/12
|
-550
+ | 550
|
-16
+ | 300
|
-8
+ | 16
|
-256
+ | 8
|
-KVM
+ | 256
+ |
+None/8
+ |
+16
+ |
+KVM
|
-c7n.12xlarge.2
+ | c7n.12xlarge.2
|
-48
+ | 48
|
-96
+ | 96
|
-35/18
+ | 35/18
|
-750
+ | 750
|
-16
+ | 400
|
-8
+ | 16
|
-256
+ | 8
|
-KVM
+ | 256
+ |
+None/12
+ |
+16
+ |
+KVM
|
-c7n.16xlarge.2
+ | c7n.16xlarge.2
|
-64
+ | 64
|
-128
+ | 128
|
-36/24
+ | 36/24
|
-800
+ | 800
|
-28
+ | 500
|
-8
+ | 28
|
-256
+ | 8
|
-KVM
+ | 256
+ |
+None/16
+ |
+16
+ |
+KVM
|
-c7n.24xlarge.2
+ | c7n.24xlarge.2
|
-96
+ | 96
|
-192
+ | 192
|
-40/36
+ | 40/36
|
-850
+ | 850
|
-32
+ | 800
|
-8
+ | 32
|
-256
+ | 8
|
-KVM
+ | 256
+ |
+None/24
+ |
+22.5
+ |
+KVM
|
-c7n.large.4
+ | c7n.large.4
|
-2
+ | 2
|
-8
+ | 8
|
-4/0.8
+ | 4/0.8
|
-40
+ | 40
|
-2
+ | 50
|
-2
+ | 2
|
-16
+ | 2
|
-KVM
+ | 16
+ |
+6/1.5
+ |
+16
+ |
+KVM
|
-c7n.xlarge.4
+ | c7n.xlarge.4
|
-4
+ | 4
|
-16
+ | 16
|
-8/1.6
+ | 8/1.6
|
-80
+ | 80
|
-2
+ | 50
|
-3
+ | 2
|
-32
+ | 3
|
-KVM
+ | 32
+ |
+6/2
+ |
+16
+ |
+KVM
|
-c7n.2xlarge.4
+ | c7n.2xlarge.4
|
-8
+ | 8
|
-32
+ | 32
|
-15/3
+ | 15/3
|
-150
+ | 150
|
-4
+ | 100
|
-4
+ | 4
|
-64
+ | 4
|
-KVM
+ | 64
+ |
+6/3
+ |
+16
+ |
+KVM
|
-c7n.3xlarge.4
+ | c7n.3xlarge.4
|
-12
+ | 12
|
-48
+ | 48
|
-17/5
+ | 17/5
|
-200
+ | 200
|
-4
+ | 150
|
-6
+ | 4
|
-96
+ | 6
|
-KVM
+ | 96
+ |
+6/4
+ |
+16
+ |
+KVM
|
-c7n.4xlarge.4
+ | c7n.4xlarge.4
|
-16
+ | 16
|
-64
+ | 64
|
-20/6
+ | 20/6
|
-280
+ | 280
|
-8
+ | 150
|
-8
+ | 8
|
-128
+ | 8
|
-KVM
+ | 128
+ |
+6/5
+ |
+16
+ |
+KVM
|
-c7n.6xlarge.4
+ | c7n.6xlarge.4
|
-24
+ | 24
|
-96
+ | 96
|
-25/9
+ | 25/9
|
-400
+ | 400
|
-8
+ | 200
|
-8
+ | 8
|
-192
+ | 8
|
-KVM
+ | 192
+ |
+None/6
+ |
+16
+ |
+KVM
|
-c7n.8xlarge.4
+ | c7n.8xlarge.4
|
-32
+ | 32
|
-128
+ | 128
|
-30/12
+ | 30/12
|
-550
+ | 550
|
-16
+ | 300
|
-8
+ | 16
|
-256
+ | 8
|
-KVM
+ | 256
+ |
+None/8
+ |
+16
+ |
+KVM
|
-c7n.12xlarge.4
+ | c7n.12xlarge.4
|
-48
+ | 48
|
-192
+ | 192
|
-35/18
+ | 35/18
|
-750
+ | 750
|
-16
+ | 400
|
-8
+ | 16
|
-256
+ | 8
|
-KVM
+ | 256
+ |
+None/12
+ |
+16
+ |
+KVM
|
-c7n.16xlarge.4
+ | c7n.16xlarge.4
|
-64
+ | 64
|
-256
+ | 256
|
-36/24
+ | 36/24
|
-800
+ | 800
|
-28
+ | 500
|
-8
+ | 28
|
-256
+ | 8
|
-KVM
+ | 256
+ |
+None/16
+ |
+16
+ |
+KVM
|
-c7n.24xlarge.4
+ | c7n.24xlarge.4
|
-96
+ | 96
|
-384
+ | 384
|
-40/36
+ | 40/36
|
-850
+ | 850
|
-32
+ | 800
|
-8
+ | 32
|
-256
+ | 8
|
-KVM
+ | 256
+ |
+None/24
+ |
+22.5
+ |
+KVM
|
@@ -433,7 +563,7 @@
Max./Assured Bandwidth
(Gbit/s)
|
-Max. PPS
+ | PPS
(10,000)
|
Max. NIC Queues
@@ -477,7 +607,7 @@
| Max./Assured Bandwidth
(Gbit/s)
|
-Max. PPS
+ | PPS
(10,000)
|
Max. NIC Queues
@@ -778,7 +908,7 @@
| Max./Assured Bandwidth
(Gbit/s)
|
-Max. PPS
+ | PPS
(10,000)
|
Max. NIC Queues
@@ -1038,7 +1168,7 @@
| Max./Assured Bandwidth
(Gbit/s)
|
-Max. PPS
+ | PPS
(10,000)
|
Max. NICs
@@ -1275,10 +1405,413 @@
|
-
-NotesTable 6 lists the OSs supported by dedicated general-purpose ECSs.
- Table 6 Supported OS versionsOS
+Table 6 C9 ECS specificationsFlavor
+ |
+vCPUs
+ |
+Memory
+(GiB)
+ |
+Max./Assured Bandwidth
+(Gbit/s)
+ |
+PPS
+(10,000)
+ |
+Network Connections (10,000)
+ |
+Max. NIC Queues
+ |
+Max. NICs
+ |
+Max. Supplementary NICs
+ |
+Max. EVS Disk Bandwidth (Gbit/s)
+ |
+Max. EVS Disk IOPS (10,000)
+ |
+Virtualization
+ |
+
+
+c9.large.2
+ |
+2
+ |
+4
+ |
+20/3
+ |
+100
+ |
+75
+ |
+2
+ |
+2
+ |
+16
+ |
+11
+ |
+11
+ |
+KVM
+ |
+
+c9.xlarge.2
+ |
+4
+ |
+8
+ |
+20/5
+ |
+160
+ |
+200
+ |
+4
+ |
+3
+ |
+32
+ |
+11
+ |
+11
+ |
+
+c9.2xlarge.2
+ |
+8
+ |
+16
+ |
+20/8
+ |
+200
+ |
+300
+ |
+8
+ |
+8
+ |
+64
+ |
+11
+ |
+11
+ |
+
+c9.4xlarge.2
+ |
+16
+ |
+32
+ |
+30/12
+ |
+350
+ |
+400
+ |
+16
+ |
+8
+ |
+128
+ |
+11
+ |
+11
+ |
+
+c9.8xlarge.2
+ |
+32
+ |
+64
+ |
+40/25
+ |
+700
+ |
+600
+ |
+32
+ |
+8
+ |
+256
+ |
+11
+ |
+11
+ |
+
+c9.16xlarge.2
+ |
+64
+ |
+128
+ |
+60/40
+ |
+1,400
+ |
+700
+ |
+64
+ |
+8
+ |
+256
+ |
+21
+ |
+23
+ |
+
+c9.32xlarge.2
+ |
+128
+ |
+256
+ |
+100/80
+ |
+2,000
+ |
+1,000
+ |
+64
+ |
+10
+ |
+256
+ |
+43
+ |
+46
+ |
+
+c9.48xlarge.2
+ |
+192
+ |
+376
+ |
+120/102
+ |
+4,000
+ |
+1,000
+ |
+64
+ |
+12
+ |
+256
+ |
+64
+ |
+70
+ |
+
+c9.large.4
+ |
+2
+ |
+8
+ |
+20/3
+ |
+100
+ |
+75
+ |
+2
+ |
+2
+ |
+16
+ |
+11
+ |
+11
+ |
+
+c9.xlarge.4
+ |
+4
+ |
+16
+ |
+20/5
+ |
+160
+ |
+200
+ |
+4
+ |
+3
+ |
+32
+ |
+11
+ |
+11
+ |
+
+c9.2xlarge.4
+ |
+8
+ |
+32
+ |
+20/8
+ |
+200
+ |
+300
+ |
+8
+ |
+8
+ |
+64
+ |
+11
+ |
+11
+ |
+
+c9.4xlarge.4
+ |
+16
+ |
+64
+ |
+30/12
+ |
+350
+ |
+400
+ |
+16
+ |
+8
+ |
+128
+ |
+11
+ |
+11
+ |
+
+c9.8xlarge.4
+ |
+32
+ |
+128
+ |
+40/25
+ |
+700
+ |
+600
+ |
+32
+ |
+8
+ |
+256
+ |
+11
+ |
+11
+ |
+
+c9.16xlarge.4
+ |
+64
+ |
+256
+ |
+60/40
+ |
+1,400
+ |
+700
+ |
+64
+ |
+8
+ |
+256
+ |
+21
+ |
+23
+ |
+
+c9.32xlarge.4
+ |
+128
+ |
+512
+ |
+100/80
+ |
+2,000
+ |
+1,000
+ |
+64
+ |
+10
+ |
+256
+ |
+43
+ |
+46
+ |
+
+c9.48xlarge.4
+ |
+192
+ |
+752
+ |
+120/102
+ |
+4,000
+ |
+1,000
+ |
+64
+ |
+12
+ |
+256
+ |
+64
+ |
+70
+ |
+
+
+
+
+
+NotesTable 7 lists the OSs supported by dedicated general-purpose ECSs.
+
+ Table 7 Supported OS versionsOS
|
Version
|
diff --git a/docs/ecs/umn/en-us_topic_0092494193.html b/docs/ecs/umn/en-us_topic_0092494193.html
index 4505679b8..c787d8281 100644
--- a/docs/ecs/umn/en-us_topic_0092494193.html
+++ b/docs/ecs/umn/en-us_topic_0092494193.html
@@ -6,7 +6,7 @@
- Obtain the password.
Use the password obtaining function provided by the management console to decrypt the key file to obtain a password.
For details, see Obtaining the Password for Logging In to a Windows ECS.
- Select a login method and log in to the ECS.
diff --git a/docs/ecs/umn/en-us_topic_0092494943.html b/docs/ecs/umn/en-us_topic_0092494943.html
index b451de110..6d4a2b596 100644
--- a/docs/ecs/umn/en-us_topic_0092494943.html
+++ b/docs/ecs/umn/en-us_topic_0092494943.html
@@ -1,12 +1,12 @@
Login Overview (Windows)
-
|---|
|
|---|
|
|---|
|---|
|
|---|
| |
|---|
|
|---|
|---|
|
|---|
|
|---|
|
|---|
|
|---|
|
|---|
|
|---|
| | |
|---|