@alicloud/ecs20140526 7.8.6 → 7.9.1

package/dist/client.js

@@ -137,7 +137,7 @@ class Client extends openapi_core_1.default {
         return openapi_core_2.OpenApiUtil.getEndpointRules(productId, regionId, endpointRule, network, suffix);
     }
     /**
-     * Invoke AcceptInquiredSystemEvent to accept and authorize the execution of a system event operation. For a system event in the Inquiring status, this operation accepts the default action of the system event and authorizes the system to execute the default action.
+     * Accepts and authorizes the execution of a system event operation. For system events in the Inquiring state, this operation accepts the default action of the system event and authorizes the system to execute the default action.
      *
      * @param request - AcceptInquiredSystemEventRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -187,7 +187,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.AcceptInquiredSystemEventResponse({}));
     }
     /**
-     * Invoke AcceptInquiredSystemEvent to accept and authorize the execution of a system event operation. For a system event in the Inquiring status, this operation accepts the default action of the system event and authorizes the system to execute the default action.
+     * Accepts and authorizes the execution of a system event operation. For system events in the Inquiring state, this operation accepts the default action of the system event and authorizes the system to execute the default action.
      *
      * @param request - AcceptInquiredSystemEventRequest
      * @returns AcceptInquiredSystemEventResponse
@@ -746,9 +746,9 @@ class Client extends openapi_core_1.default {
      * You can specify IPv6 addresses from the CIDR block of the vSwitch to which the Elastic Network Interface (ENI) belongs, or specify the number of IPv6 addresses for automatic creation. Note the following items:
      * - The vSwitch to which the ENI belongs must have IPv6 enabled. For more information, see [Enable an IPv6 CIDR block for an existing vSwitch](https://help.aliyun.com/document_detail/98923.html).
      * - The ENI must be in the Active (Available) or InUse state.
-     * - When you operate on a primary ENI, the instance to which the ENI is attached must be in the Running or Stopped state.
-     * - The number of IPv6 addresses that can be allocated to a single ENI depends on the instance type of the instance to which the ENI is attached.
-     *     - If the ENI is in the Active (Available) state, up to 10 IPv6 addresses can be allocated.
+     * - When you operate a primary ENI, the instance to which the network interface controller (NIC) is attached must be in the Running or Stopped state.
+     * - The number of IPv6 addresses that can be allocated to a single network interface controller (NIC) depends on the instance type of the instance to which the ENI is attached.
+     *     - If the ENI is in the Active (Available) state, you can allocate up to 10 IPv6 addresses to it.
      *     - If the ENI is attached to an instance, the number of IPv6 addresses that can be allocated is limited by the instance type. For more information, see [Instance family](https://help.aliyun.com/document_detail/25378.html).
      * - After you successfully invoke this operation, you can obtain the allocated IPv6 address information from the response.
      *
@@ -819,9 +819,9 @@ class Client extends openapi_core_1.default {
      * You can specify IPv6 addresses from the CIDR block of the vSwitch to which the Elastic Network Interface (ENI) belongs, or specify the number of IPv6 addresses for automatic creation. Note the following items:
      * - The vSwitch to which the ENI belongs must have IPv6 enabled. For more information, see [Enable an IPv6 CIDR block for an existing vSwitch](https://help.aliyun.com/document_detail/98923.html).
      * - The ENI must be in the Active (Available) or InUse state.
-     * - When you operate on a primary ENI, the instance to which the ENI is attached must be in the Running or Stopped state.
-     * - The number of IPv6 addresses that can be allocated to a single ENI depends on the instance type of the instance to which the ENI is attached.
-     *     - If the ENI is in the Active (Available) state, up to 10 IPv6 addresses can be allocated.
+     * - When you operate a primary ENI, the instance to which the network interface controller (NIC) is attached must be in the Running or Stopped state.
+     * - The number of IPv6 addresses that can be allocated to a single network interface controller (NIC) depends on the instance type of the instance to which the ENI is attached.
+     *     - If the ENI is in the Active (Available) state, you can allocate up to 10 IPv6 addresses to it.
      *     - If the ENI is attached to an instance, the number of IPv6 addresses that can be allocated is limited by the instance type. For more information, see [Instance family](https://help.aliyun.com/document_detail/25378.html).
      * - After you successfully invoke this operation, you can obtain the allocated IPv6 address information from the response.
      *
@@ -833,14 +833,14 @@ class Client extends openapi_core_1.default {
         return await this.assignIpv6AddressesWithOptions(request, runtime);
     }
     /**
-     * Assigns secondary private IP addresses to an elastic network interface (ENI). You can specify available private IP addresses within the CIDR block of the vSwitch that is connected to the ENI. Alternatively, you can specify the number of private IP addresses that are automatically assigned from the CIDR block of the vSwitch to the ENI.
+     * Allocates one or more secondary private IP addresses to an Elastic Network Interface (ENI). You can specify available private IP addresses from the vSwitch to which the ENI belongs, or automatically allocate private IP addresses by specifying the number of private endpoint addresses.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * - The ENI to which you want to assign IP prefixes must be in the Available (Available) or InUse (InUse) state.
-     * - When you assign private IP addresses to a primary ENI, the Elastic Compute Service (ECS) instance to which the ENI is attached must be in the Running (Running) or Stopped (Stopped) state.
-     * - When an ENI is in the Available state, you can assign up to 49 secondary private IP addresses to the ENI. When an ENI is attached to an instance, the number of secondary private IP addresses that can be assigned to the ENI varies based on the instance type. For more information, see [Overview of instance families](https://help.aliyun.com/document_detail/25378.html).
-     * - After the operation is called, you can obtain the assigned secondary private IP addresses from the response.
+     * ## Operation description
+     * - Only ENIs in the Available or InUse state are supported.
+     * - When you operate a primary ENI, the instance to which the ENI is attached must be in the Running or Stopped state.
+     * - When an ENI is in the Available state, you can allocate up to 49 secondary private IP addresses to it. After the ENI is attached to an instance, the number of secondary private IP addresses that can be allocated is limited by the instance type. For more information, see [Instance families](https://help.aliyun.com/document_detail/25378.html).
+     * - After you call this operation, you can obtain the allocated secondary private IP address information from the response.
      *
      * @param request - AssignPrivateIpAddressesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -902,14 +902,14 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.AssignPrivateIpAddressesResponse({}));
     }
     /**
-     * Assigns secondary private IP addresses to an elastic network interface (ENI). You can specify available private IP addresses within the CIDR block of the vSwitch that is connected to the ENI. Alternatively, you can specify the number of private IP addresses that are automatically assigned from the CIDR block of the vSwitch to the ENI.
+     * Allocates one or more secondary private IP addresses to an Elastic Network Interface (ENI). You can specify available private IP addresses from the vSwitch to which the ENI belongs, or automatically allocate private IP addresses by specifying the number of private endpoint addresses.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * - The ENI to which you want to assign IP prefixes must be in the Available (Available) or InUse (InUse) state.
-     * - When you assign private IP addresses to a primary ENI, the Elastic Compute Service (ECS) instance to which the ENI is attached must be in the Running (Running) or Stopped (Stopped) state.
-     * - When an ENI is in the Available state, you can assign up to 49 secondary private IP addresses to the ENI. When an ENI is attached to an instance, the number of secondary private IP addresses that can be assigned to the ENI varies based on the instance type. For more information, see [Overview of instance families](https://help.aliyun.com/document_detail/25378.html).
-     * - After the operation is called, you can obtain the assigned secondary private IP addresses from the response.
+     * ## Operation description
+     * - Only ENIs in the Available or InUse state are supported.
+     * - When you operate a primary ENI, the instance to which the ENI is attached must be in the Running or Stopped state.
+     * - When an ENI is in the Available state, you can allocate up to 49 secondary private IP addresses to it. After the ENI is attached to an instance, the number of secondary private IP addresses that can be allocated is limited by the instance type. For more information, see [Instance families](https://help.aliyun.com/document_detail/25378.html).
+     * - After you call this operation, you can obtain the allocated secondary private IP address information from the response.
      *
      * @param request - AssignPrivateIpAddressesRequest
      * @returns AssignPrivateIpAddressesResponse
@@ -1356,21 +1356,22 @@ class Client extends openapi_core_1.default {
         return await this.attachKeyPairWithOptions(request, runtime);
     }
     /**
-     * Attaches an elastic network interface (ENI) to an Elastic Compute Service (ECS) instance that resides in a virtual private cloud (VPC). When you call this operation, you can specify parameters, such as NetworkInterfaceId, InstanceId, and NetworkCardIndex, in the request.
+     * Calls the AttachNetworkInterface operation to attach an Elastic Network Interface (ENI) to a VPC-connected ECS instance. You can specify parameters such as NetworkInterfaceId, InstanceId, and NetworkCardIndex.
      *
      * @remarks
-     * Take note of the following items:
-     * - The ENI must be in the **Available** state. You can attach an ENI to only one instance that resides in the same zone and VPC as the ENI.
-     * - The instance must be in the Running or Stopped state. When you attach ENIs to instances of specific instance types, make sure that the instances are in the Stopped state. For more information, see the "Instance types of the ECS instances that must be in the Stopped (Stopped) state" section in the [Bind an ENI](https://help.aliyun.com/document_detail/58503.html) topic.
-     * > If the last start time of the instance (including the start time of the instance if it is a new instance, the last restart time of the instance, and the last reactivation time of the instance) is before April 1st, 2018 and the instance is in the Running state, you must call the RebootInstance operation to restart the instance. If you do not call the RebootInstance operation to restart the instance, you cannot attach the ENI to the instance.
-     * - You can attach multiple ENIs to one instance. For more information, see [ENI overview](https://help.aliyun.com/document_detail/58496.html).
-     * - The vSwitch to which the ENI is connected must be in the same zone and VPC as the vSwitch to which the instance is connected.
-     * - This operation is an asynchronous operation. After you call this operation to attach an ENI, you can view the status or events of the ENI to check whether the ENI is attached. The following figure shows the transitions between the statuses of the ENI.
-     *   ![](https://static-aliyun-doc.oss-cn-hangzhou.aliyuncs.com/file-manage-files/en-US/20230223/vqky/AttachNetworkInterface.png)
-     * * If the ENI is in the Attaching state, the ENI attachment request is sent and the ENI is being attached to the specified instance.
-     * * If the ENI is in the InUse state, the ENI is attached to the specified instance.
-     * * If the ENI is in the Available state, the ENI failed to be attached.
-     * **For examples on how to call this operation, see** [Attach an ENI](https://help.aliyun.com/document_detail/471550.html).
+     * When you call this operation, take note of the following items:
+     * - The Elastic Network Interface (ENI) must be in the **active** (`Available`) state. An ENI can be attached to only one instance that resides in the same zone and VPC as the network interface controller (NIC).
+     * - The ECS instance must be in the Running or Stopped state. Some ECS instance types require the ECS instance to be in the Stopped state when you attach an Elastic Network Interface (ENI). For more information, see the section about ECS instance types that require the ECS instance to be stopped in [Attach an ENI](https://help.aliyun.com/document_detail/58503.html).
+     *     > If the instance was last started before April 1, 2018 (including but not limited to starting a newly purchased instance, restarting, or powering on), you must invoke RebootInstance to restart the instance that has been in the Running state. Otherwise, the network interface controller (NIC) cannot be attached.
+     * - Multiple Elastic Network Interfaces (ENIs) can be attached to a single instance at the same time. For more information, see [ENI overview](https://help.aliyun.com/document_detail/58496.html).
+     *
+     * - The vSwitch to which the network interface controller (NIC) belongs must be in the same zone and VPC as the instance.
+     * - This is an asynchronous operation. After a successful invocation, you can check the Elastic Network Interface (ENI) status or listen for network interface controller (NIC) operation events to obtain the result. The ENI state machine is shown in the following figure:
+     * ![](https://static-aliyun-doc.oss-cn-hangzhou.aliyuncs.com/file-manage-files/zh-CN/20221124/esgu/AttachNetworkInterface.jpg)
+     *     - Attaching indicates that the request to attach the ENI was sent successfully and the ENI is being attached to the ECS instance.
+     *     - InUse indicates that the ENI has been attached to the ECS instance.
+     *     - Available indicates that the ENI failed to be attached to the ECS instance.
+     * **For details, see** [Attach a network interface controller (NIC)](https://help.aliyun.com/document_detail/471550.html).
      *
      * @param request - AttachNetworkInterfaceRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1429,21 +1430,22 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.AttachNetworkInterfaceResponse({}));
     }
     /**
-     * Attaches an elastic network interface (ENI) to an Elastic Compute Service (ECS) instance that resides in a virtual private cloud (VPC). When you call this operation, you can specify parameters, such as NetworkInterfaceId, InstanceId, and NetworkCardIndex, in the request.
+     * Calls the AttachNetworkInterface operation to attach an Elastic Network Interface (ENI) to a VPC-connected ECS instance. You can specify parameters such as NetworkInterfaceId, InstanceId, and NetworkCardIndex.
      *
      * @remarks
-     * Take note of the following items:
-     * - The ENI must be in the **Available** state. You can attach an ENI to only one instance that resides in the same zone and VPC as the ENI.
-     * - The instance must be in the Running or Stopped state. When you attach ENIs to instances of specific instance types, make sure that the instances are in the Stopped state. For more information, see the "Instance types of the ECS instances that must be in the Stopped (Stopped) state" section in the [Bind an ENI](https://help.aliyun.com/document_detail/58503.html) topic.
-     * > If the last start time of the instance (including the start time of the instance if it is a new instance, the last restart time of the instance, and the last reactivation time of the instance) is before April 1st, 2018 and the instance is in the Running state, you must call the RebootInstance operation to restart the instance. If you do not call the RebootInstance operation to restart the instance, you cannot attach the ENI to the instance.
-     * - You can attach multiple ENIs to one instance. For more information, see [ENI overview](https://help.aliyun.com/document_detail/58496.html).
-     * - The vSwitch to which the ENI is connected must be in the same zone and VPC as the vSwitch to which the instance is connected.
-     * - This operation is an asynchronous operation. After you call this operation to attach an ENI, you can view the status or events of the ENI to check whether the ENI is attached. The following figure shows the transitions between the statuses of the ENI.
-     *   ![](https://static-aliyun-doc.oss-cn-hangzhou.aliyuncs.com/file-manage-files/en-US/20230223/vqky/AttachNetworkInterface.png)
-     * * If the ENI is in the Attaching state, the ENI attachment request is sent and the ENI is being attached to the specified instance.
-     * * If the ENI is in the InUse state, the ENI is attached to the specified instance.
-     * * If the ENI is in the Available state, the ENI failed to be attached.
-     * **For examples on how to call this operation, see** [Attach an ENI](https://help.aliyun.com/document_detail/471550.html).
+     * When you call this operation, take note of the following items:
+     * - The Elastic Network Interface (ENI) must be in the **active** (`Available`) state. An ENI can be attached to only one instance that resides in the same zone and VPC as the network interface controller (NIC).
+     * - The ECS instance must be in the Running or Stopped state. Some ECS instance types require the ECS instance to be in the Stopped state when you attach an Elastic Network Interface (ENI). For more information, see the section about ECS instance types that require the ECS instance to be stopped in [Attach an ENI](https://help.aliyun.com/document_detail/58503.html).
+     *     > If the instance was last started before April 1, 2018 (including but not limited to starting a newly purchased instance, restarting, or powering on), you must invoke RebootInstance to restart the instance that has been in the Running state. Otherwise, the network interface controller (NIC) cannot be attached.
+     * - Multiple Elastic Network Interfaces (ENIs) can be attached to a single instance at the same time. For more information, see [ENI overview](https://help.aliyun.com/document_detail/58496.html).
+     *
+     * - The vSwitch to which the network interface controller (NIC) belongs must be in the same zone and VPC as the instance.
+     * - This is an asynchronous operation. After a successful invocation, you can check the Elastic Network Interface (ENI) status or listen for network interface controller (NIC) operation events to obtain the result. The ENI state machine is shown in the following figure:
+     * ![](https://static-aliyun-doc.oss-cn-hangzhou.aliyuncs.com/file-manage-files/zh-CN/20221124/esgu/AttachNetworkInterface.jpg)
+     *     - Attaching indicates that the request to attach the ENI was sent successfully and the ENI is being attached to the ECS instance.
+     *     - InUse indicates that the ENI has been attached to the ECS instance.
+     *     - Available indicates that the ENI failed to be attached to the ECS instance.
+     * **For details, see** [Attach a network interface controller (NIC)](https://help.aliyun.com/document_detail/471550.html).
      *
      * @param request - AttachNetworkInterfaceRequest
      * @returns AttachNetworkInterfaceResponse
@@ -1453,54 +1455,54 @@ class Client extends openapi_core_1.default {
         return await this.attachNetworkInterfaceWithOptions(request, runtime);
     }
     /**
-     * Creates inbound security group rules in a security group. You can use the created rules to allow or deny inbound traffic from other objects to Elastic Compute Service (ECS) instances in the security group for fine-grained network access control.
+     * Adds one or more inbound rules to a security group. You can use this operation to specify inbound access permissions for a security group, allowing or denying other devices from sending inbound traffic to instances in the security group, which enables fine-grained network access control.
      *
      * @remarks
-     * ### 使用须知
-     * - **数量限制：** 单张弹性网卡关联的所有安全组的规则（包括入方向规则与出方向规则）数量之和不能超过 1000。具体限制请参见[安全组使用限制](~~25412#SecurityGroupQuota1~~)。
-     * - **优先级设置：** 安全组入方向规则优先级（Priority）可选范围为 1\\~100。数字越小，代表优先级越高，优先级相同的安全组规则，优先以拒绝访问（drop）的规则为准。
-     * ### 注意事项
-     * 如果指定的安全组规则已存在，此次调用成功，但不会增加规则。
-     * ### 规则确定方式
-     * 确定一条安全组入方向规则必要的一组相关参数：
-     * - 源端设置：选择 SourceCidrIp（IPv4 地址）、Ipv6SourceCidrIp（IPv6 地址）、SourcetPrefixListId（前缀列表 ID）、SourceGroupId（源端安全组）中的一项。
-     * - 目的端口范围：PortRange。
-     * - 协议类型：IpProtocol。
-     * - 权限策略：Policy。
-     * > 企业安全组不支持授权其他安全组访问，普通安全组支持授权的安全组数量最多为 20 个。
-     * ### 请求示例
-     * 假设要在杭州地域下指定安全组中增加几条不同源端的入方向规则：
-     * - 增加指定 IP 地址段的访问权限。
-     *   ```
-     *   "RegionId":"cn-hangzhou", //设置地域
-     *   "SecurityGroupId":"sg-bp67acfmxazb4p****", //设置安全组
-     *   "Permissions":[
-     *        {
-     *          "SourceCidrIp":"10.0.0.0/8", //设置源端 IPv4 地址
-     *          "PortRange":"22/22", //设置端口范围
-     *          "IpProtocol":"TCP", //设置协议类型
-     *          "Policy":"Accept" //设置访问策略
-     *        }
-     *   ]
-     *   ```
-     * - 增加一条其他安全组和一条前缀列表的访问权限。
-     *   ```
-     *   "RegionId":"cn-hangzhou",
-     *   "SecurityGroupId":"sg-bp67acfmxazb4p****",
-     *   "Permissions":[
-     *        {
-     *          "SourceGroupId":"sg-bp17vs63txqxbd****", //设置源端安全组
-     *          "PortRange":"22/22",
-     *          "IpProtocol":"TCP",
-     *          "Policy":"Drop"
-     *        },{
-     *          "SourcePrefixListId":"pl-x1j1k5ykzqlixdcy****", //设置源端前缀列表
-     *          "PortRange":"22/22",
-     *          "IpProtocol":"TCP",
-     *          "Policy":"Drop"
-     *        }
-     *   ]
-     *   ```
+     * ### Before you begin
+     * - **Quantity limit:** The total number of security group rules (including inbound rules and outbound rules) across all security groups associated with a single network interface controller (NIC) cannot exceed 1,000. For more information, see [Security group limits](~~25412#SecurityGroupQuota1~~).
+     * - **Priority settings:** The priority (Priority) of inbound security group rules ranges from 1 to 100. A smaller number indicates a higher priority. If two security group rules have the same priority, the deny (drop) rule takes precedence. Access is denied first.
+     * ### Notes
+     * If the specified security group rule already exists, the call succeeds but no rule is added.
+     * ### How to determine a rule
+     * The following parameters are required to determine an inbound security group rule:
+     * - Source settings: Specify one of the following: SourceCidrIp (IPv4 address), Ipv6SourceCidrIp (IPv6 address), SourcePrefixListId (prefix list ID), or SourceGroupId (source security group).
+     * - Destination port range: PortRange.
+     * - Protocol type: IpProtocol.
+     * - Access policy: Policy.
+     * > Advanced security groups do not support authorization for access from other security groups. Basic security groups support a maximum of 20 authorized security groups.
+     * ### Request examples
+     * The following examples show how to add inbound rules with different sources to a security group in the China (Hangzhou) region:
+     *   - Add access permissions for a specified IP address range.
+     *     ```
+     *     "RegionId":"cn-hangzhou", // Specify the region.
+     *     "SecurityGroupId":"sg-bp67acfmxazb4p****", // Specify the security group.
+     *     "Permissions":[
+     *          {
+     *            "SourceCidrIp":"10.0.0.0/8", // Specify the source IPv4 address.
+     *            "PortRange":"22/22", // Specify the port range.
+     *            "IpProtocol":"TCP", // Specify the protocol type.
+     *            "Policy":"Accept" // Specify the access policy.
+     *          }
+     *     ]
+     *     ```
+     *   - Add access permissions for another security group and a prefix list.
+     *     ```
+     *     "RegionId":"cn-hangzhou",
+     *     "SecurityGroupId":"sg-bp67acfmxazb4p****",
+     *     "Permissions":[
+     *          {
+     *            "SourceGroupId":"sg-bp17vs63txqxbd****", // Specify the source security group.
+     *            "PortRange":"22/22",
+     *            "IpProtocol":"TCP",
+     *            "Policy":"Drop"
+     *          },{
+     *            "SourcePrefixListId":"pl-x1j1k5ykzqlixdcy****", // Specify the source prefix list.
+     *            "PortRange":"22/22",
+     *            "IpProtocol":"TCP",
+     *            "Policy":"Drop"
+     *          }
+     *     ]
+     *     ```
      *
      * @param request - AuthorizeSecurityGroupRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1607,54 +1609,54 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.AuthorizeSecurityGroupResponse({}));
     }
     /**
-     * Creates inbound security group rules in a security group. You can use the created rules to allow or deny inbound traffic from other objects to Elastic Compute Service (ECS) instances in the security group for fine-grained network access control.
+     * Adds one or more inbound rules to a security group. You can use this operation to specify inbound access permissions for a security group, allowing or denying other devices from sending inbound traffic to instances in the security group, which enables fine-grained network access control.
      *
      * @remarks
-     * ### 使用须知
-     * - **数量限制：** 单张弹性网卡关联的所有安全组的规则（包括入方向规则与出方向规则）数量之和不能超过 1000。具体限制请参见[安全组使用限制](~~25412#SecurityGroupQuota1~~)。
-     * - **优先级设置：** 安全组入方向规则优先级（Priority）可选范围为 1\\~100。数字越小，代表优先级越高，优先级相同的安全组规则，优先以拒绝访问（drop）的规则为准。
-     * ### 注意事项
-     * 如果指定的安全组规则已存在，此次调用成功，但不会增加规则。
-     * ### 规则确定方式
-     * 确定一条安全组入方向规则必要的一组相关参数：
-     * - 源端设置：选择 SourceCidrIp（IPv4 地址）、Ipv6SourceCidrIp（IPv6 地址）、SourcetPrefixListId（前缀列表 ID）、SourceGroupId（源端安全组）中的一项。
-     * - 目的端口范围：PortRange。
-     * - 协议类型：IpProtocol。
-     * - 权限策略：Policy。
-     * > 企业安全组不支持授权其他安全组访问，普通安全组支持授权的安全组数量最多为 20 个。
-     * ### 请求示例
-     * 假设要在杭州地域下指定安全组中增加几条不同源端的入方向规则：
-     * - 增加指定 IP 地址段的访问权限。
-     *   ```
-     *   "RegionId":"cn-hangzhou", //设置地域
-     *   "SecurityGroupId":"sg-bp67acfmxazb4p****", //设置安全组
-     *   "Permissions":[
-     *        {
-     *          "SourceCidrIp":"10.0.0.0/8", //设置源端 IPv4 地址
-     *          "PortRange":"22/22", //设置端口范围
-     *          "IpProtocol":"TCP", //设置协议类型
-     *          "Policy":"Accept" //设置访问策略
-     *        }
-     *   ]
-     *   ```
-     * - 增加一条其他安全组和一条前缀列表的访问权限。
-     *   ```
-     *   "RegionId":"cn-hangzhou",
-     *   "SecurityGroupId":"sg-bp67acfmxazb4p****",
-     *   "Permissions":[
-     *        {
-     *          "SourceGroupId":"sg-bp17vs63txqxbd****", //设置源端安全组
-     *          "PortRange":"22/22",
-     *          "IpProtocol":"TCP",
-     *          "Policy":"Drop"
-     *        },{
-     *          "SourcePrefixListId":"pl-x1j1k5ykzqlixdcy****", //设置源端前缀列表
-     *          "PortRange":"22/22",
-     *          "IpProtocol":"TCP",
-     *          "Policy":"Drop"
-     *        }
-     *   ]
-     *   ```
+     * ### Before you begin
+     * - **Quantity limit:** The total number of security group rules (including inbound rules and outbound rules) across all security groups associated with a single network interface controller (NIC) cannot exceed 1,000. For more information, see [Security group limits](~~25412#SecurityGroupQuota1~~).
+     * - **Priority settings:** The priority (Priority) of inbound security group rules ranges from 1 to 100. A smaller number indicates a higher priority. If two security group rules have the same priority, the deny (drop) rule takes precedence. Access is denied first.
+     * ### Notes
+     * If the specified security group rule already exists, the call succeeds but no rule is added.
+     * ### How to determine a rule
+     * The following parameters are required to determine an inbound security group rule:
+     * - Source settings: Specify one of the following: SourceCidrIp (IPv4 address), Ipv6SourceCidrIp (IPv6 address), SourcePrefixListId (prefix list ID), or SourceGroupId (source security group).
+     * - Destination port range: PortRange.
+     * - Protocol type: IpProtocol.
+     * - Access policy: Policy.
+     * > Advanced security groups do not support authorization for access from other security groups. Basic security groups support a maximum of 20 authorized security groups.
+     * ### Request examples
+     * The following examples show how to add inbound rules with different sources to a security group in the China (Hangzhou) region:
+     *   - Add access permissions for a specified IP address range.
+     *     ```
+     *     "RegionId":"cn-hangzhou", // Specify the region.
+     *     "SecurityGroupId":"sg-bp67acfmxazb4p****", // Specify the security group.
+     *     "Permissions":[
+     *          {
+     *            "SourceCidrIp":"10.0.0.0/8", // Specify the source IPv4 address.
+     *            "PortRange":"22/22", // Specify the port range.
+     *            "IpProtocol":"TCP", // Specify the protocol type.
+     *            "Policy":"Accept" // Specify the access policy.
+     *          }
+     *     ]
+     *     ```
+     *   - Add access permissions for another security group and a prefix list.
+     *     ```
+     *     "RegionId":"cn-hangzhou",
+     *     "SecurityGroupId":"sg-bp67acfmxazb4p****",
+     *     "Permissions":[
+     *          {
+     *            "SourceGroupId":"sg-bp17vs63txqxbd****", // Specify the source security group.
+     *            "PortRange":"22/22",
+     *            "IpProtocol":"TCP",
+     *            "Policy":"Drop"
+     *          },{
+     *            "SourcePrefixListId":"pl-x1j1k5ykzqlixdcy****", // Specify the source prefix list.
+     *            "PortRange":"22/22",
+     *            "IpProtocol":"TCP",
+     *            "Policy":"Drop"
+     *          }
+     *     ]
+     *     ```
      *
      * @param request - AuthorizeSecurityGroupRequest
      * @returns AuthorizeSecurityGroupResponse
@@ -1664,54 +1666,54 @@ class Client extends openapi_core_1.default {
         return await this.authorizeSecurityGroupWithOptions(request, runtime);
     }
     /**
-     * Creates outbound rules in a security group. You can use the created rules to allow or deny outbound traffic from Elastic Compute Service (ECS) instances in the security group to other objects for fine-grained network access control.
+     * Adds one or more outbound rules to a security group. You can use this operation to specify outbound access permissions for a security group, allowing or denying instances in the security group from sending outbound traffic to other devices, which enables fine-grained network access control.
      *
      * @remarks
-     * ### 使用须知
-     * - **数量限制：** 单张弹性网卡关联的所有安全组的规则（包括入方向规则与出方向规则）数量之和不能超过 1000。具体限制请参见[安全组使用限制](~~25412#SecurityGroupQuota1~~)。
-     * - **优先级设置：** 安全组出方向规则优先级（Priority）可选范围为 1\\~100。数字越小，代表优先级越高，优先级相同的安全组规则，优先以拒绝访问（drop）的规则为准。
-     * ### 注意事项
-     * 如果指定的安全组规则已存在，此次调用成功，但不会增加规则。
-     * ### 规则确定方式
-     * 确定一条安全组出方向规则必要的一组相关参数：
-     * - 目的端设置：选择 DestCidrIp（IPv4 地址）、Ipv6DestCidrIp（IPv6 地址）、DestPrefixListId（前缀列表 ID）、DestGroupId（目的端安全组）中的一项。
-     * - 目的端口范围：PortRange。
-     * - 协议类型：IpProtocol。
-     * - 权限策略：Policy。
-     * > 企业安全组不支持授权其他安全组访问，普通安全组支持授权的安全组数量最多为 20 个。
-     * ### 请求示例
-     * 假设要在杭州地域下指定安全组中增加几条不同目的端的出方向规则：
-     * - 增加指定 IP 地址段的访问权限。
-     *   ```
-     *   "RegionId":"cn-hangzhou",  //设置地域
-     *   "SecurityGroupId":"sg-bp17vs63txqxbds9***", //设置安全组
-     *   "Permissions":[
-     *        {
-     *          "DestCidrIp":"10.0.0.0/8", //设置目的端 IPv4 地址
-     *          "PortRange":"-1/-1", //设置端口范围
-     *          "IpProtocol":"ICMP", //设置协议类型
-     *          "Policy":"Accept" //设置访问策略
-     *        }
-     *   ]
-     *   ```
-     * - 增加一条其他安全组和一条前缀列表的访问权限。
-     *   ```
-     *   "RegionId":"cn-hangzhou",
-     *   "SecurityGroupId":"sg-bp17vs63txqxbds9***",
-     *   "Permissions":[
-     *        {
-     *          "DestGroupId":"sg-bp67acfmxazb4pi***", //设置目的端安全组
-     *          "PortRange":"22/22",
-     *          "IpProtocol":"TCP",
-     *          "Policy":"Drop"
-     *        },{
-     *          "DestPrefixListId":"pl-x1j1k5ykzqlixdcy****", //设置目的端前缀列表
-     *          "PortRange":"22/22",
-     *          "IpProtocol":"TCP",
-     *          "Policy":"Drop"
-     *        }
-     *   ]
-     *   ```
+     * ### Before you begin
+     * - **Quantity limit:** The total number of rules (including both inbound rules and outbound rules) across all security groups associated with a single network interface controller (NIC) cannot exceed 1,000. For more information, see [Security group limits](~~25412#SecurityGroupQuota1~~).
+     * - **Priority settings:** The priority (Priority) of outbound security group rules ranges from 1 to 100. A smaller number indicates a higher priority. If two security group rules have the same priority, the deny (drop) rule takes precedence.
+     * ### Notes
+     * If the specified security group rule already exists, the call succeeds but no rule is added.
+     * ### How to determine a rule
+     * The following parameters are required to determine an outbound rule:
+     * - Destination settings: Specify one of the following: DestCidrIp (IPv4 address), Ipv6DestCidrIp (IPv6 address), DestPrefixListId (prefix list ID), or DestGroupId (destination security group).
+     * - Destination port range: PortRange.
+     * - Protocol type: IpProtocol.
+     * - Access policy: Policy.
+     * > Advanced security groups do not support authorization of other security groups for access. Custom security groups support a maximum of 20 authorized security groups.
+     * ### Request examples
+     * The following examples show how to add outbound rules with different destinations to a security group in the China (Hangzhou) region:
+     *   - Add access permissions for a specified IP address range.
+     *     ```
+     *     "RegionId":"ap-southeast-1",  // Specify the region.
+     *     "SecurityGroupId":"sg-bp17vs63txqxbds9***", // Specify the security group.
+     *     "Permissions":[
+     *          {
+     *            "DestCidrIp":"10.0.0.0/8", // Specify the destination IPv4 address.
+     *            "PortRange":"-1/-1", // Specify the port range.
+     *            "IpProtocol":"ICMP", // Specify the protocol type.
+     *            "Policy":"Accept" // Specify the access policy.
+     *          }
+     *     ]
+     *     ```
+     *   - Add access permissions for another security group and a prefix list.
+     *     ```
+     *     "RegionId":"ap-southeast-1",
+     *     "SecurityGroupId":"sg-bp17vs63txqxbds9***",
+     *     "Permissions":[
+     *          {
+     *            "DestGroupId":"sg-bp67acfmxazb4pi***", // Specify the destination security group.
+     *            "PortRange":"22/22",
+     *            "IpProtocol":"TCP",
+     *            "Policy":"Drop"
+     *          },{
+     *            "DestPrefixListId":"pl-x1j1k5ykzqlixdcy****", // Specify the destination prefix list.
+     *            "PortRange":"22/22",
+     *            "IpProtocol":"TCP",
+     *            "Policy":"Drop"
+     *          }
+     *     ]
+     *     ```
      *
      * @param request - AuthorizeSecurityGroupEgressRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1818,54 +1820,54 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.AuthorizeSecurityGroupEgressResponse({}));
     }
     /**
-     * Creates outbound rules in a security group. You can use the created rules to allow or deny outbound traffic from Elastic Compute Service (ECS) instances in the security group to other objects for fine-grained network access control.
+     * Adds one or more outbound rules to a security group. You can use this operation to specify outbound access permissions for a security group, allowing or denying instances in the security group from sending outbound traffic to other devices, which enables fine-grained network access control.
      *
      * @remarks
-     * ### 使用须知
-     * - **数量限制：** 单张弹性网卡关联的所有安全组的规则（包括入方向规则与出方向规则）数量之和不能超过 1000。具体限制请参见[安全组使用限制](~~25412#SecurityGroupQuota1~~)。
-     * - **优先级设置：** 安全组出方向规则优先级（Priority）可选范围为 1\\~100。数字越小，代表优先级越高，优先级相同的安全组规则，优先以拒绝访问（drop）的规则为准。
-     * ### 注意事项
-     * 如果指定的安全组规则已存在，此次调用成功，但不会增加规则。
-     * ### 规则确定方式
-     * 确定一条安全组出方向规则必要的一组相关参数：
-     * - 目的端设置：选择 DestCidrIp（IPv4 地址）、Ipv6DestCidrIp（IPv6 地址）、DestPrefixListId（前缀列表 ID）、DestGroupId（目的端安全组）中的一项。
-     * - 目的端口范围：PortRange。
-     * - 协议类型：IpProtocol。
-     * - 权限策略：Policy。
-     * > 企业安全组不支持授权其他安全组访问，普通安全组支持授权的安全组数量最多为 20 个。
-     * ### 请求示例
-     * 假设要在杭州地域下指定安全组中增加几条不同目的端的出方向规则：
-     * - 增加指定 IP 地址段的访问权限。
-     *   ```
-     *   "RegionId":"cn-hangzhou",  //设置地域
-     *   "SecurityGroupId":"sg-bp17vs63txqxbds9***", //设置安全组
-     *   "Permissions":[
-     *        {
-     *          "DestCidrIp":"10.0.0.0/8", //设置目的端 IPv4 地址
-     *          "PortRange":"-1/-1", //设置端口范围
-     *          "IpProtocol":"ICMP", //设置协议类型
-     *          "Policy":"Accept" //设置访问策略
-     *        }
-     *   ]
-     *   ```
-     * - 增加一条其他安全组和一条前缀列表的访问权限。
-     *   ```
-     *   "RegionId":"cn-hangzhou",
-     *   "SecurityGroupId":"sg-bp17vs63txqxbds9***",
-     *   "Permissions":[
-     *        {
-     *          "DestGroupId":"sg-bp67acfmxazb4pi***", //设置目的端安全组
-     *          "PortRange":"22/22",
-     *          "IpProtocol":"TCP",
-     *          "Policy":"Drop"
-     *        },{
-     *          "DestPrefixListId":"pl-x1j1k5ykzqlixdcy****", //设置目的端前缀列表
-     *          "PortRange":"22/22",
-     *          "IpProtocol":"TCP",
-     *          "Policy":"Drop"
-     *        }
-     *   ]
-     *   ```
+     * ### Before you begin
+     * - **Quantity limit:** The total number of rules (including both inbound rules and outbound rules) across all security groups associated with a single network interface controller (NIC) cannot exceed 1,000. For more information, see [Security group limits](~~25412#SecurityGroupQuota1~~).
+     * - **Priority settings:** The priority (Priority) of outbound security group rules ranges from 1 to 100. A smaller number indicates a higher priority. If two security group rules have the same priority, the deny (drop) rule takes precedence.
+     * ### Notes
+     * If the specified security group rule already exists, the call succeeds but no rule is added.
+     * ### How to determine a rule
+     * The following parameters are required to determine an outbound rule:
+     * - Destination settings: Specify one of the following: DestCidrIp (IPv4 address), Ipv6DestCidrIp (IPv6 address), DestPrefixListId (prefix list ID), or DestGroupId (destination security group).
+     * - Destination port range: PortRange.
+     * - Protocol type: IpProtocol.
+     * - Access policy: Policy.
+     * > Advanced security groups do not support authorization of other security groups for access. Custom security groups support a maximum of 20 authorized security groups.
+     * ### Request examples
+     * The following examples show how to add outbound rules with different destinations to a security group in the China (Hangzhou) region:
+     *   - Add access permissions for a specified IP address range.
+     *     ```
+     *     "RegionId":"ap-southeast-1",  // Specify the region.
+     *     "SecurityGroupId":"sg-bp17vs63txqxbds9***", // Specify the security group.
+     *     "Permissions":[
+     *          {
+     *            "DestCidrIp":"10.0.0.0/8", // Specify the destination IPv4 address.
+     *            "PortRange":"-1/-1", // Specify the port range.
+     *            "IpProtocol":"ICMP", // Specify the protocol type.
+     *            "Policy":"Accept" // Specify the access policy.
+     *          }
+     *     ]
+     *     ```
+     *   - Add access permissions for another security group and a prefix list.
+     *     ```
+     *     "RegionId":"ap-southeast-1",
+     *     "SecurityGroupId":"sg-bp17vs63txqxbds9***",
+     *     "Permissions":[
+     *          {
+     *            "DestGroupId":"sg-bp67acfmxazb4pi***", // Specify the destination security group.
+     *            "PortRange":"22/22",
+     *            "IpProtocol":"TCP",
+     *            "Policy":"Drop"
+     *          },{
+     *            "DestPrefixListId":"pl-x1j1k5ykzqlixdcy****", // Specify the destination prefix list.
+     *            "PortRange":"22/22",
+     *            "IpProtocol":"TCP",
+     *            "Policy":"Drop"
+     *          }
+     *     ]
+     *     ```
      *
      * @param request - AuthorizeSecurityGroupEgressRequest
      * @returns AuthorizeSecurityGroupEgressResponse
@@ -1993,10 +1995,10 @@ class Client extends openapi_core_1.default {
         return await this.cancelCopyImageWithOptions(request, runtime);
     }
     /**
-     * Cancels an image building task.
+     * Cancels an image build task.
      *
      * @remarks
-     * Before you call the CancelImagePipelineExecution operation, make sure that the image building task to be canceled is in the BUILDING, PREPARING, or REPAIRING state.
+     * Before you call this operation, make sure that the image build task you want to cancel is in the PREPARING, REPAIRING, or BUILDING state.
      *
      * @param request - CancelImagePipelineExecutionRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -2046,10 +2048,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CancelImagePipelineExecutionResponse({}));
     }
     /**
-     * Cancels an image building task.
+     * Cancels an image build task.
      *
      * @remarks
-     * Before you call the CancelImagePipelineExecution operation, make sure that the image building task to be canceled is in the BUILDING, PREPARING, or REPAIRING state.
+     * Before you call this operation, make sure that the image build task you want to cancel is in the PREPARING, REPAIRING, or BUILDING state.
      *
      * @param request - CancelImagePipelineExecutionRequest
      * @returns CancelImagePipelineExecutionResponse
@@ -2232,29 +2234,29 @@ class Client extends openapi_core_1.default {
         return await this.cancelTaskWithOptions(request, runtime);
     }
     /**
-     * Cloud disk cloning allows you to quickly create a new cloud disk in the same availability zone containing the same data as the source disk. You can customize the new disk\\"s capacity, type, and encryption attributes. After attaching the disk to an instance, you can use it to rapidly replicate business data or scale your services horizontally.
+     * Disk cloning allows you to quickly create a new disk with the same data as the source disk in the same zone. The new disk supports custom capacity, type, and encryption attributes. After the new disk is attached to an instance, you can quickly replicate business data or horizontally scale your services.
      *
      * @remarks
-     * > The cloud disk cloning feature is free. However, the resulting destination disk is billed based on block storage rules. Charges vary by disk type and can include capacity, provisioned performance, and burst performance. Billing for all items begins at creation—except for burst performance fees, which are charged only after a burst occurs—and applies regardless of whether the disk is attached to an instance.
-     * ### Usage
-     * - This is an asynchronous operation. After a successful call, call the DescribeTasks operation with the returned taskGroupId to query the task\\"s status.
+     * > The disk cloning feature itself is free of charge, but the new disk generated by cloning is billed based on block storage billing rules. Billable items vary by disk type and include disk capacity fees, provisioned performance fees, and performance burst fees. Except for performance burst fees, which are billed after a burst occurs, all other fees start to accrue after the disk is created, regardless of whether the disk is attached to an instance.
+     * ### How to use
+     * - This is an asynchronous operation. After a successful call, use the taskGroupId and call the DescribeTasks operation to obtain the execution result.
      * ### Features
-     * - You can only clone ESSD cloud disks (cloud_essd, cloud_auto, cloud_essd_entry, and cloud_regional_disk_auto) to create a `destination disk`, which must also be an ESSD type.
-     *   - A non-zone-redundant cloud disk can only be cloned to a non-zone-redundant disk. A zone-redundant cloud disk can only be cloned to another zone-redundant cloud disk.
-     *   - Local disks and elastic ephemeral disks do not support cloning and cannot be used as either a source disk or a destination disk.
-     * - You can specify the type and performance level for the `destination disk`.
-     * - You can specify the capacity for the `destination disk`, but its capacity must be greater than or equal to that of the `source disk`.
-     * - You can configure provisioned performance and burst performance for the `destination disk`, provided that the destination disk type supports these features.
-     * - You can enable encryption and change the encryption key for the `destination disk`. If the `source disk` is encrypted, the destination disk must also be encrypted. However, you can use a different encryption key.
-     * - You can use a subscription cloud disk as the `source disk`. The disk can still be used as a `source disk` even after its subscription expires.
-     * - A `destination disk` created by cloning cannot be re-initialized.
-     * - While you cannot clone entire storage sets or dedicated storage clusters, you can use a disk from within them as a `source disk`. The resulting destination disk is a standalone disk and will not belong to the original storage set or cluster.
-     * - `source disk` status requirements
-     *   - The `source disk` must be "In Use", and its attached instance must be "Running" or "Stopped".
-     *   - The `source disk` must be "Available" and have been attached to an instance at least once.
-     *   - A disk undergoing a configuration modification cannot be used as a `source disk`.
-     *   - A disk that is being scaled up cannot be used as a `source disk`.
-     * - As cloud disk cloning is not supported for hibernated instances, a disk attached to a hibernated instance cannot be used as a `source disk`.
+     * - Cloning supports only ESSD series disks (cloud_essd, cloud_auto, cloud_essd_entry, cloud_regional_disk_auto) as the source, and the `new disk` can only be an ESSD series disk type.
+     *   - Non-regional disks can only be cloned to non-regional disk types. Regional disks can only be cloned to regional disk types.
+     *   - Local disks and elastic ephemeral disks cannot be cloned or used as clone sources.
+     * - You can specify the `new disk` type and performance level (PL) during cloning.
+     * - You can specify the `new disk` capacity during cloning, but the new disk capacity must be greater than or equal to the `source disk` capacity.
+     * - You can configure provisioned performance and performance burst for the `new disk`, provided that the destination disk type supports provisioned performance and performance burst.
+     * - You can specify encryption for the `new disk` and change the encryption key. If the `source disk` is encrypted, you cannot clone it into an unencrypted disk, but you can change the encryption key.
+     * - You can use a subscription disk as the `source disk`. Even if the subscription disk has expired, it can still be used as the `source disk`.
+     * - The `new disk` created by cloning does not support reinitialization.
+     * - Cloning does not support storage sets or dedicated block storage clusters, but disks in them can be used as the `source disk`. The cloned disk will not be in the storage set or dedicated block storage cluster.
+     * - `Source disk` status restrictions:
+     *   - The `source disk` status is "In Use" and the corresponding instance status is "Running" or "Stopped".
+     *   - The `source disk` status is "Available" and the disk has been previously attached.
+     *   - A disk undergoing a specification change cannot be used as the `source disk`.
+     *   - A disk undergoing expansion cannot be used as the `source disk`.
+     * - Disk cloning is not supported for instance hibernation scenarios. If a disk is on a hibernated instance, it cannot be used as the `source disk`.
      *
      * @param request - CloneDisksRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -2334,29 +2336,29 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CloneDisksResponse({}));
     }
     /**
-     * Cloud disk cloning allows you to quickly create a new cloud disk in the same availability zone containing the same data as the source disk. You can customize the new disk\\"s capacity, type, and encryption attributes. After attaching the disk to an instance, you can use it to rapidly replicate business data or scale your services horizontally.
+     * Disk cloning allows you to quickly create a new disk with the same data as the source disk in the same zone. The new disk supports custom capacity, type, and encryption attributes. After the new disk is attached to an instance, you can quickly replicate business data or horizontally scale your services.
      *
      * @remarks
-     * > The cloud disk cloning feature is free. However, the resulting destination disk is billed based on block storage rules. Charges vary by disk type and can include capacity, provisioned performance, and burst performance. Billing for all items begins at creation—except for burst performance fees, which are charged only after a burst occurs—and applies regardless of whether the disk is attached to an instance.
-     * ### Usage
-     * - This is an asynchronous operation. After a successful call, call the DescribeTasks operation with the returned taskGroupId to query the task\\"s status.
+     * > The disk cloning feature itself is free of charge, but the new disk generated by cloning is billed based on block storage billing rules. Billable items vary by disk type and include disk capacity fees, provisioned performance fees, and performance burst fees. Except for performance burst fees, which are billed after a burst occurs, all other fees start to accrue after the disk is created, regardless of whether the disk is attached to an instance.
+     * ### How to use
+     * - This is an asynchronous operation. After a successful call, use the taskGroupId and call the DescribeTasks operation to obtain the execution result.
      * ### Features
-     * - You can only clone ESSD cloud disks (cloud_essd, cloud_auto, cloud_essd_entry, and cloud_regional_disk_auto) to create a `destination disk`, which must also be an ESSD type.
-     *   - A non-zone-redundant cloud disk can only be cloned to a non-zone-redundant disk. A zone-redundant cloud disk can only be cloned to another zone-redundant cloud disk.
-     *   - Local disks and elastic ephemeral disks do not support cloning and cannot be used as either a source disk or a destination disk.
-     * - You can specify the type and performance level for the `destination disk`.
-     * - You can specify the capacity for the `destination disk`, but its capacity must be greater than or equal to that of the `source disk`.
-     * - You can configure provisioned performance and burst performance for the `destination disk`, provided that the destination disk type supports these features.
-     * - You can enable encryption and change the encryption key for the `destination disk`. If the `source disk` is encrypted, the destination disk must also be encrypted. However, you can use a different encryption key.
-     * - You can use a subscription cloud disk as the `source disk`. The disk can still be used as a `source disk` even after its subscription expires.
-     * - A `destination disk` created by cloning cannot be re-initialized.
-     * - While you cannot clone entire storage sets or dedicated storage clusters, you can use a disk from within them as a `source disk`. The resulting destination disk is a standalone disk and will not belong to the original storage set or cluster.
-     * - `source disk` status requirements
-     *   - The `source disk` must be "In Use", and its attached instance must be "Running" or "Stopped".
-     *   - The `source disk` must be "Available" and have been attached to an instance at least once.
-     *   - A disk undergoing a configuration modification cannot be used as a `source disk`.
-     *   - A disk that is being scaled up cannot be used as a `source disk`.
-     * - As cloud disk cloning is not supported for hibernated instances, a disk attached to a hibernated instance cannot be used as a `source disk`.
+     * - Cloning supports only ESSD series disks (cloud_essd, cloud_auto, cloud_essd_entry, cloud_regional_disk_auto) as the source, and the `new disk` can only be an ESSD series disk type.
+     *   - Non-regional disks can only be cloned to non-regional disk types. Regional disks can only be cloned to regional disk types.
+     *   - Local disks and elastic ephemeral disks cannot be cloned or used as clone sources.
+     * - You can specify the `new disk` type and performance level (PL) during cloning.
+     * - You can specify the `new disk` capacity during cloning, but the new disk capacity must be greater than or equal to the `source disk` capacity.
+     * - You can configure provisioned performance and performance burst for the `new disk`, provided that the destination disk type supports provisioned performance and performance burst.
+     * - You can specify encryption for the `new disk` and change the encryption key. If the `source disk` is encrypted, you cannot clone it into an unencrypted disk, but you can change the encryption key.
+     * - You can use a subscription disk as the `source disk`. Even if the subscription disk has expired, it can still be used as the `source disk`.
+     * - The `new disk` created by cloning does not support reinitialization.
+     * - Cloning does not support storage sets or dedicated block storage clusters, but disks in them can be used as the `source disk`. The cloned disk will not be in the storage set or dedicated block storage cluster.
+     * - `Source disk` status restrictions:
+     *   - The `source disk` status is "In Use" and the corresponding instance status is "Running" or "Stopped".
+     *   - The `source disk` status is "Available" and the disk has been previously attached.
+     *   - A disk undergoing a specification change cannot be used as the `source disk`.
+     *   - A disk undergoing expansion cannot be used as the `source disk`.
+     * - Disk cloning is not supported for instance hibernation scenarios. If a disk is on a hibernated instance, it cannot be used as the `source disk`.
      *
      * @param request - CloneDisksRequest
      * @returns CloneDisksResponse
@@ -2693,12 +2695,12 @@ class Client extends openapi_core_1.default {
         return await this.copySnapshotWithOptions(request, runtime);
     }
     /**
-     * This API is used to create an activation code, which is used to register non-Alibaba Cloud servers as Alibaba Cloud managed instances.
+     * Creates an activation code that is used to register non-Alibaba Cloud servers as Alibaba Cloud managed instances.
      *
      * @remarks
-     * ## API Guide
-     * After you register a non-Alibaba Cloud server as an Alibaba Cloud managed instance by using an activation code, you can use various online services provided by Alibaba Cloud on the managed instance (such as Cloud Assistant, CloudOps Orchestration Service, and Alibaba Cloud DevOps).
-     * The operating system of the non-Alibaba Cloud server must meet one of the following versions, and the server must be able to access the Internet to be registered as an Alibaba Cloud managed instance.
+     * ## Operation description
+     * After you use an activation code to register a non-Alibaba Cloud server as an Alibaba Cloud managed instance, you can use various online services provided by Alibaba Cloud in the managed instance, such as Cloud Assistant, CloudOps Orchestration Service, and Alibaba Cloud DevOps.
+     * The operating system of the non-Elastic Compute Service (ECS) server must meet the following version requirements, and the server must have Internet access to be registered as an Alibaba Cloud managed instance.
      * - Alibaba Cloud Linux 2/3 and later
      * - CentOS 6/7/8 and later
      * - Debian 8/9/10 and later
@@ -2707,9 +2709,9 @@ class Client extends openapi_core_1.default {
      * - OpenSUSE
      * - RedHat 5/6/7 and later
      * - SUSE Linux Enterprise Server 11/12/15 and later
-     * - Windows Server 2012/2016/2019 and later
-     * In each Alibaba Cloud Region, you can have up to 5,000 activation codes for managed instances. When the number of activation codes exceeds 1,000, you must maintain an activation code usage rate greater than 50% to continue creating new activation codes.
-     * > You can click **Register New Instance** on the **Managed Instances** tab of the **ECS Cloud Assistant** page to view activation code usage data.
+     * - Window Server 2012/2016/2019 and later
+     * In each Alibaba Cloud region, you can have up to 10 managed instance activation codes. Each activation code can be used to register up to 10 instances, and each activation code is valid for up to 4 hours.
+     * > On the **ECS Cloud Assistant** page, click the **Managed Instances** tab, and then click **Register New Instance** to view the usage data of activation codes.
      *
      * @param request - CreateActivationRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -2777,12 +2779,12 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateActivationResponse({}));
     }
     /**
-     * This API is used to create an activation code, which is used to register non-Alibaba Cloud servers as Alibaba Cloud managed instances.
+     * Creates an activation code that is used to register non-Alibaba Cloud servers as Alibaba Cloud managed instances.
      *
      * @remarks
-     * ## API Guide
-     * After you register a non-Alibaba Cloud server as an Alibaba Cloud managed instance by using an activation code, you can use various online services provided by Alibaba Cloud on the managed instance (such as Cloud Assistant, CloudOps Orchestration Service, and Alibaba Cloud DevOps).
-     * The operating system of the non-Alibaba Cloud server must meet one of the following versions, and the server must be able to access the Internet to be registered as an Alibaba Cloud managed instance.
+     * ## Operation description
+     * After you use an activation code to register a non-Alibaba Cloud server as an Alibaba Cloud managed instance, you can use various online services provided by Alibaba Cloud in the managed instance, such as Cloud Assistant, CloudOps Orchestration Service, and Alibaba Cloud DevOps.
+     * The operating system of the non-Elastic Compute Service (ECS) server must meet the following version requirements, and the server must have Internet access to be registered as an Alibaba Cloud managed instance.
      * - Alibaba Cloud Linux 2/3 and later
      * - CentOS 6/7/8 and later
      * - Debian 8/9/10 and later
@@ -2791,9 +2793,9 @@ class Client extends openapi_core_1.default {
      * - OpenSUSE
      * - RedHat 5/6/7 and later
      * - SUSE Linux Enterprise Server 11/12/15 and later
-     * - Windows Server 2012/2016/2019 and later
-     * In each Alibaba Cloud Region, you can have up to 5,000 activation codes for managed instances. When the number of activation codes exceeds 1,000, you must maintain an activation code usage rate greater than 50% to continue creating new activation codes.
-     * > You can click **Register New Instance** on the **Managed Instances** tab of the **ECS Cloud Assistant** page to view activation code usage data.
+     * - Window Server 2012/2016/2019 and later
+     * In each Alibaba Cloud region, you can have up to 10 managed instance activation codes. Each activation code can be used to register up to 10 instances, and each activation code is valid for up to 4 hours.
+     * > On the **ECS Cloud Assistant** page, click the **Managed Instances** tab, and then click **Register New Instance** to view the usage data of activation codes.
      *
      * @param request - CreateActivationRequest
      * @returns CreateActivationResponse
@@ -2803,13 +2805,13 @@ class Client extends openapi_core_1.default {
         return await this.createActivationWithOptions(request, runtime);
     }
     /**
-     * Create an auto provisioning group.
+     * Creates an auto provisioning group.
      *
      * @remarks
-     * - Auto provisioning is a solution that uses spot instances and pay-as-you-go instances to quickly deploy instance clusters. It supports one-click deployment of instance clusters across billing methods, zones, and instance families. For more information, see [Use the auto provisioning group API to create multiple ECS instances](https://help.aliyun.com/document_detail/200772.html).
-     * - Auto provisioning schedules and maintains compute resources through provisioning groups. Use auto provisioning groups to provide stable computing power and mitigate instability caused by the spot instance reclamation mechanism.
-     * - Auto provisioning is a free feature. You pay only for the instance resources created through the auto provisioning group. For more information, see [Spot instance billing](https://help.aliyun.com/document_detail/52088.html) and [Pay-as-you-go](https://help.aliyun.com/document_detail/40653.html).
-     * - When you specify both a launch template (`LaunchTemplateId`) and launch configuration parameters (`LaunchConfiguration.*`), the system prioritizes the launch template.
+     * - Auto provisioning is a solution that uses spot instances and pay-as-you-go instances to quickly deploy instance clusters. It supports one-click deployment of instance clusters across billing methods, zones, and instance families. For more information, see [Use the auto provisioning group API to create ECS instances in batches](https://help.aliyun.com/document_detail/200772.html).
+     * - Auto provisioning uses provisioning groups to schedule and maintain compute resources. You can use an auto provisioning group to steadily provide computing power and mitigate the instability caused by the reclaim mechanism of spot instances.
+     * - Auto provisioning is a free feature, but you are charged for the instance resources created by the auto provisioning group. For more information, see [Spot instance billing](https://help.aliyun.com/document_detail/52088.html) and [Pay-as-you-go](https://help.aliyun.com/document_detail/40653.html).
+     * - If you specify both a launch template (`LaunchTemplateId`) and launch configuration information (`LaunchConfiguration.*`), the launch template takes precedence.
      *
      * @param tmpReq - CreateAutoProvisioningGroupRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -2951,13 +2953,13 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateAutoProvisioningGroupResponse({}));
     }
     /**
-     * Create an auto provisioning group.
+     * Creates an auto provisioning group.
      *
      * @remarks
-     * - Auto provisioning is a solution that uses spot instances and pay-as-you-go instances to quickly deploy instance clusters. It supports one-click deployment of instance clusters across billing methods, zones, and instance families. For more information, see [Use the auto provisioning group API to create multiple ECS instances](https://help.aliyun.com/document_detail/200772.html).
-     * - Auto provisioning schedules and maintains compute resources through provisioning groups. Use auto provisioning groups to provide stable computing power and mitigate instability caused by the spot instance reclamation mechanism.
-     * - Auto provisioning is a free feature. You pay only for the instance resources created through the auto provisioning group. For more information, see [Spot instance billing](https://help.aliyun.com/document_detail/52088.html) and [Pay-as-you-go](https://help.aliyun.com/document_detail/40653.html).
-     * - When you specify both a launch template (`LaunchTemplateId`) and launch configuration parameters (`LaunchConfiguration.*`), the system prioritizes the launch template.
+     * - Auto provisioning is a solution that uses spot instances and pay-as-you-go instances to quickly deploy instance clusters. It supports one-click deployment of instance clusters across billing methods, zones, and instance families. For more information, see [Use the auto provisioning group API to create ECS instances in batches](https://help.aliyun.com/document_detail/200772.html).
+     * - Auto provisioning uses provisioning groups to schedule and maintain compute resources. You can use an auto provisioning group to steadily provide computing power and mitigate the instability caused by the reclaim mechanism of spot instances.
+     * - Auto provisioning is a free feature, but you are charged for the instance resources created by the auto provisioning group. For more information, see [Spot instance billing](https://help.aliyun.com/document_detail/52088.html) and [Pay-as-you-go](https://help.aliyun.com/document_detail/40653.html).
+     * - If you specify both a launch template (`LaunchTemplateId`) and launch configuration information (`LaunchConfiguration.*`), the launch template takes precedence.
      *
      * @param request - CreateAutoProvisioningGroupRequest
      * @returns CreateAutoProvisioningGroupResponse
@@ -3172,23 +3174,23 @@ class Client extends openapi_core_1.default {
         return await this.createCapacityReservationWithOptions(request, runtime);
     }
     /**
-     * Create a Cloud Assistant command of the Shell, PowerShell, or Bat script type.
+     * Creates a Cloud Assistant command of the Shell, PowerShell, or Bat script type.
      *
      * @remarks
-     * ## API Guide
-     * - You can create commands of the following types:
-     *   - Bat scripts (RunBatScript) for Windows instances.
-     *   - PowerShell scripts (RunPowerShellScript) for Windows instances.
-     *   - Shell scripts (RunShellScript) for Linux instances.
-     * - You can specify the Timeout parameter to set the maximum timeout duration (in seconds) for command execution on an ECS instance. If the command execution times out, the [Cloud Assistant Agent](https://help.aliyun.com/document_detail/64921.html) forcibly terminates the command process by canceling its PID.
-     *   - For one-time execution, if the command times out, the execution status ([InvokeRecordStatus](https://help.aliyun.com/document_detail/64845.html)) for the specified ECS instance changes to Failed.
-     *   - For scheduled execution:
-     *     - The timeout setting applies to each individual execution record.
-     *     - If a specific execution times out, the status of that execution record ([InvokeRecordStatus](https://help.aliyun.com/document_detail/64845.html)) changes to Failed.
-     *     - Whether the previous execution timed out does not affect the next execution.
-     * - Within a Region, you can retain between 500 and 50,000 Cloud Assistant commands. You can request a quota increase. For details on how to query and upgrade your quota, see [Quota Management](https://help.aliyun.com/document_detail/184116.html).
-     * - You can use the WorkingDir parameter to specify the execution path for the command. For Linux instances, the default path is the home directory of the root user, specifically the `/root` folder. For Windows instances, the default path is the directory where the Cloud Assistant Agent process resides, such as `C:\\Windows\\System32`.
-     * - You can enable the Custom Parameter feature by setting EnableParameter=true. In the CommandContent, you can represent custom parameters using the `{{parameter}}` syntax. When running the command ([InvokeCommand](https://help.aliyun.com/document_detail/64841.html)), you pass key-value pairs for these custom parameters. For example, if you create a command `echo {{name}}` during command creation, and then pass the key-value pair `<name, Jack>` via the Parameters parameter in InvokeCommand, the custom parameter is automatically replaced, resulting in the new command `echo Jack`, which is then executed on the instance.
+     * ## Operation description
+     * - You can create the following types of commands:
+     *     - Bat scripts for Windows instances (RunBatScript).
+     *     - PowerShell scripts for Windows instances (RunPowerShellScript).
+     *     - Shell scripts for Linux instances (RunShellScript).
+     * - You can specify the Timeout parameter to set the maximum timeout period for a command to run on an ECS instance. If the command times out, [Cloud Assistant Agent](https://help.aliyun.com/document_detail/64921.html) forcefully terminates the command process by canceling the PID of the command.
+     *     - For a one-time execution, after the command times out, the execution status ([InvokeRecordStatus](https://help.aliyun.com/document_detail/64845.html)) of the command on the specified ECS instance changes to Failed.
+     *     - For a scheduled execution:
+     *         - The timeout period takes effect for each execution record.
+     *         - After a specific execution times out, the status ([InvokeRecordStatus](https://help.aliyun.com/document_detail/64845.html)) of that execution record changes to Failed.
+     *         - The timeout of a previous execution does not affect the next execution.
+     * - You can retain up to 500 to 50,000 Cloud Assistant commands in a region. You can also request a quota increase. For information about how to query and increase quotas, refer to [Quota management](https://help.aliyun.com/document_detail/184116.html).
+     * - You can specify the WorkingDir parameter to set the execution path of a command. For Linux instances, the default path is the home directory of the root user, which is `/root`. For Windows instances, the default path is the directory where the Cloud Assistant Agent process is located, such as `C:\\Windows\\System32`.
+     * - You can set EnableParameter to true to enable the custom parameter feature. When you set CommandContent, you can define custom parameters in the {{parameter}} format and pass in custom parameter key-value pairs when you run the command by calling [InvokeCommand](https://help.aliyun.com/document_detail/64841.html). For example, if you create the command `echo {{name}}` and pass in the key-value pair `<name, Jack>` through the Parameters parameter when you call InvokeCommand, the custom parameter is automatically replaced. The resulting command `echo Jack` is then run on the instance.
      *
      * @param request - CreateCommandRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -3268,23 +3270,23 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateCommandResponse({}));
     }
     /**
-     * Create a Cloud Assistant command of the Shell, PowerShell, or Bat script type.
+     * Creates a Cloud Assistant command of the Shell, PowerShell, or Bat script type.
      *
      * @remarks
-     * ## API Guide
-     * - You can create commands of the following types:
-     *   - Bat scripts (RunBatScript) for Windows instances.
-     *   - PowerShell scripts (RunPowerShellScript) for Windows instances.
-     *   - Shell scripts (RunShellScript) for Linux instances.
-     * - You can specify the Timeout parameter to set the maximum timeout duration (in seconds) for command execution on an ECS instance. If the command execution times out, the [Cloud Assistant Agent](https://help.aliyun.com/document_detail/64921.html) forcibly terminates the command process by canceling its PID.
-     *   - For one-time execution, if the command times out, the execution status ([InvokeRecordStatus](https://help.aliyun.com/document_detail/64845.html)) for the specified ECS instance changes to Failed.
-     *   - For scheduled execution:
-     *     - The timeout setting applies to each individual execution record.
-     *     - If a specific execution times out, the status of that execution record ([InvokeRecordStatus](https://help.aliyun.com/document_detail/64845.html)) changes to Failed.
-     *     - Whether the previous execution timed out does not affect the next execution.
-     * - Within a Region, you can retain between 500 and 50,000 Cloud Assistant commands. You can request a quota increase. For details on how to query and upgrade your quota, see [Quota Management](https://help.aliyun.com/document_detail/184116.html).
-     * - You can use the WorkingDir parameter to specify the execution path for the command. For Linux instances, the default path is the home directory of the root user, specifically the `/root` folder. For Windows instances, the default path is the directory where the Cloud Assistant Agent process resides, such as `C:\\Windows\\System32`.
-     * - You can enable the Custom Parameter feature by setting EnableParameter=true. In the CommandContent, you can represent custom parameters using the `{{parameter}}` syntax. When running the command ([InvokeCommand](https://help.aliyun.com/document_detail/64841.html)), you pass key-value pairs for these custom parameters. For example, if you create a command `echo {{name}}` during command creation, and then pass the key-value pair `<name, Jack>` via the Parameters parameter in InvokeCommand, the custom parameter is automatically replaced, resulting in the new command `echo Jack`, which is then executed on the instance.
+     * ## Operation description
+     * - You can create the following types of commands:
+     *     - Bat scripts for Windows instances (RunBatScript).
+     *     - PowerShell scripts for Windows instances (RunPowerShellScript).
+     *     - Shell scripts for Linux instances (RunShellScript).
+     * - You can specify the Timeout parameter to set the maximum timeout period for a command to run on an ECS instance. If the command times out, [Cloud Assistant Agent](https://help.aliyun.com/document_detail/64921.html) forcefully terminates the command process by canceling the PID of the command.
+     *     - For a one-time execution, after the command times out, the execution status ([InvokeRecordStatus](https://help.aliyun.com/document_detail/64845.html)) of the command on the specified ECS instance changes to Failed.
+     *     - For a scheduled execution:
+     *         - The timeout period takes effect for each execution record.
+     *         - After a specific execution times out, the status ([InvokeRecordStatus](https://help.aliyun.com/document_detail/64845.html)) of that execution record changes to Failed.
+     *         - The timeout of a previous execution does not affect the next execution.
+     * - You can retain up to 500 to 50,000 Cloud Assistant commands in a region. You can also request a quota increase. For information about how to query and increase quotas, refer to [Quota management](https://help.aliyun.com/document_detail/184116.html).
+     * - You can specify the WorkingDir parameter to set the execution path of a command. For Linux instances, the default path is the home directory of the root user, which is `/root`. For Windows instances, the default path is the directory where the Cloud Assistant Agent process is located, such as `C:\\Windows\\System32`.
+     * - You can set EnableParameter to true to enable the custom parameter feature. When you set CommandContent, you can define custom parameters in the {{parameter}} format and pass in custom parameter key-value pairs when you run the command by calling [InvokeCommand](https://help.aliyun.com/document_detail/64841.html). For example, if you create the command `echo {{name}}` and pass in the key-value pair `<name, Jack>` through the Parameters parameter when you call InvokeCommand, the custom parameter is automatically replaced. The resulting command `echo Jack` is then run on the instance.
      *
      * @param request - CreateCommandRequest
      * @returns CreateCommandResponse
@@ -3557,14 +3559,14 @@ class Client extends openapi_core_1.default {
      * Creates a pay-as-you-go or subscription data disk.
      *
      * @remarks
-     * - When creating a disk, you can enable the multi-attach feature (`MultiAttach`). We recommend that you understand this feature and its usage restrictions first. For more information, see [NVMe support for ESSDs](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
-     * - Supported disk types: basic disk, ultra disk, standard SSD, ESSD, ESSD Entry disk, ESSD zone-redundant disk, ESSD AutoPL disk, elastic ephemeral disk - standard, and elastic ephemeral disk - premium.
-     * - Creating a disk requires real-name verification. Go to [Real-name verification](https://account.console.aliyun.com/#/auth/home) in account information.
-     * - Creating a disk involves resource billing. We recommend that you understand the billing methods of ECS in advance. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
-     * - Default settings when creating a disk:
-     *   - Automatic snapshots of the disk are deleted when the disk is deleted, that is, `DeleteAutoSnapshot` is set to `true`. You can call [DescribeDisks](https://help.aliyun.com/document_detail/2679767.html) to query this parameter and call [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to modify it.
-     *   - When creating an ESSD, if you do not set the disk performance level, the default is PL1. You can modify the disk performance level through [ModifyDiskSpec](https://help.aliyun.com/document_detail/123780.html).
-     *   - The billing method is pay-as-you-go, that is, the default `Portable` attribute is `true`.
+     * - When you create a disk, you can enable the multi-attach feature (`MultiAttach`). Learn about this attribute and its limits before you use it. For more information, see [ESSD cloud disks that support NVMe](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
+     * - The following disk types can be created: basic disks, ultra disks, standard SSDs, enterprise SSDs, ESSD Entry disks, regional Enterprise SSDs (ESSDs), ESSD AutoPL disks, elastic ephemeral disks - Standard Edition, and elastic ephemeral disks - Premium Edition.
+     * - To create a disk, complete [real-name registration](https://account.console.aliyun.com/#/auth/home).
+     * - Creating a disk incurs fees. Learn about the billing method of Elastic Compute Service (ECS) in advance. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
+     * - Default settings when you create a disk:
+     *   - Automatic snapshots of the disk are deleted when the disk is deleted. That is, `DeleteAutoSnapshot` is set to `true`. You can call [DescribeDisks](https://help.aliyun.com/document_detail/2679767.html) to query the parameter settings, and call [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to modify the property.
+     *   - When you create an enterprise SSD, if you do not configure a performance level, the default level is PL1. You can call [ModifyDiskSpec](https://help.aliyun.com/document_detail/123780.html) to change the performance level.
+     *   - The billing method is pay-as-you-go, which means the `Portable` property defaults to `true`.
      *
      * @param request - CreateDiskRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -3674,14 +3676,14 @@ class Client extends openapi_core_1.default {
      * Creates a pay-as-you-go or subscription data disk.
      *
      * @remarks
-     * - When creating a disk, you can enable the multi-attach feature (`MultiAttach`). We recommend that you understand this feature and its usage restrictions first. For more information, see [NVMe support for ESSDs](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
-     * - Supported disk types: basic disk, ultra disk, standard SSD, ESSD, ESSD Entry disk, ESSD zone-redundant disk, ESSD AutoPL disk, elastic ephemeral disk - standard, and elastic ephemeral disk - premium.
-     * - Creating a disk requires real-name verification. Go to [Real-name verification](https://account.console.aliyun.com/#/auth/home) in account information.
-     * - Creating a disk involves resource billing. We recommend that you understand the billing methods of ECS in advance. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
-     * - Default settings when creating a disk:
-     *   - Automatic snapshots of the disk are deleted when the disk is deleted, that is, `DeleteAutoSnapshot` is set to `true`. You can call [DescribeDisks](https://help.aliyun.com/document_detail/2679767.html) to query this parameter and call [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to modify it.
-     *   - When creating an ESSD, if you do not set the disk performance level, the default is PL1. You can modify the disk performance level through [ModifyDiskSpec](https://help.aliyun.com/document_detail/123780.html).
-     *   - The billing method is pay-as-you-go, that is, the default `Portable` attribute is `true`.
+     * - When you create a disk, you can enable the multi-attach feature (`MultiAttach`). Learn about this attribute and its limits before you use it. For more information, see [ESSD cloud disks that support NVMe](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
+     * - The following disk types can be created: basic disks, ultra disks, standard SSDs, enterprise SSDs, ESSD Entry disks, regional Enterprise SSDs (ESSDs), ESSD AutoPL disks, elastic ephemeral disks - Standard Edition, and elastic ephemeral disks - Premium Edition.
+     * - To create a disk, complete [real-name registration](https://account.console.aliyun.com/#/auth/home).
+     * - Creating a disk incurs fees. Learn about the billing method of Elastic Compute Service (ECS) in advance. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
+     * - Default settings when you create a disk:
+     *   - Automatic snapshots of the disk are deleted when the disk is deleted. That is, `DeleteAutoSnapshot` is set to `true`. You can call [DescribeDisks](https://help.aliyun.com/document_detail/2679767.html) to query the parameter settings, and call [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to modify the property.
+     *   - When you create an enterprise SSD, if you do not configure a performance level, the default level is PL1. You can call [ModifyDiskSpec](https://help.aliyun.com/document_detail/123780.html) to change the performance level.
+     *   - The billing method is pay-as-you-go, which means the `Portable` property defaults to `true`.
      *
      * @param request - CreateDiskRequest
      * @returns CreateDiskResponse
@@ -3944,7 +3946,7 @@ class Client extends openapi_core_1.default {
         return await this.createHaVipWithOptions(request, runtime);
     }
     /**
-     * Creates a high performance computing (HPC) cluster.
+     * Creates an HPC cluster by calling CreateHpcCluster.
      *
      * @param request - CreateHpcClusterRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -3997,7 +3999,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateHpcClusterResponse({}));
     }
     /**
-     * Creates a high performance computing (HPC) cluster.
+     * Creates an HPC cluster by calling CreateHpcCluster.
      *
      * @param request - CreateHpcClusterRequest
      * @returns CreateHpcClusterResponse
@@ -4007,26 +4009,25 @@ class Client extends openapi_core_1.default {
         return await this.createHpcClusterWithOptions(request, runtime);
     }
     /**
-     * Create a custom image. You can then use the image to create ECS instances (`RunInstances`) or replace the system disk of an instance (`ReplaceSystemDisk`).
+     * Creates a custom image. You can use the created custom image to create ECS instances (RunInstances) or replace the system disk of an instance (ReplaceSystemDisk).
      *
      * @remarks
-     * ### Usage notes
-     * - This operation is asynchronous. A successful request returns an image ID, but the image is not created immediately. You can call [DescribeImage](https://help.aliyun.com/document_detail/2679797.html) to query the image status. The image is ready for use when its status changes to `Available`. For more information, see [Overview of custom images](https://help.aliyun.com/document_detail/172789.html).
-     * - If the response to a query for ECS instance information contains `{"OperationLocks": {"LockReason" : "security"}}`, you cannot create a custom image from the instance.
-     * - We recommend configuring the image check parameter `DetectionStrategy` when you create an image. This helps the system optimize your image. For more information, see [Overview of image check](https://help.aliyun.com/document_detail/439819.html).
-     * This operation provides three methods to create a custom image. The request parameters are prioritized as follows: InstanceId > DiskDeviceMapping > SnapshotId. If your request includes two or more of these parameters, the operation creates the image based on the parameter with the highest priority.
+     * ### Before you begin
+     * - This is an asynchronous operation. After a request to create a custom image is sent, the image ID is returned. However, the image creation is not immediately complete. Call [DescribeImage](https://help.aliyun.com/document_detail/2679797.html) to query the image information. When the status in the response is `Available`, the image is created and ready for use. For more information, see [Custom image overview](https://help.aliyun.com/document_detail/172789.html).
+     * - When you query ECS instance information, if the response contains {"OperationLocks": {"LockReason" : "security"}}, you cannot create a custom image.
+     * - Configure the image detection parameter `DetectionStrategy` when creating an image to help the system optimize your image. For more information, see [Image detection overview](https://help.aliyun.com/document_detail/439819.html).
+     * The following describes three methods to create a custom image by calling this operation. The priority of request parameters is: InstanceId > DiskDeviceMapping > SnapshotId. If your request contains two or more of these parameters, the image is created based on the parameter with the highest priority.
      * - **Create a custom image from an instance**: Specify the instance ID (`InstanceId`).
-     *   - The instance must be in the `Running` or `Stopped` state.
-     *   - A successful call creates a new snapshot for each cloud disk of the instance.
-     *   >Notice:
-     *   Data cached in memory on a running instance may not be written to disk. This can cause data inconsistencies between the custom image and the instance. We recommend stopping the instance by calling [StopInstances](https://help.aliyun.com/document_detail/155372.html) before creating an image.
-     *
-     * - **Create a custom image from a snapshot (snapshots created on or before July 15, 2013, cannot be used).**
-     *   - **Create a custom image from a system disk snapshot**: Specify only the snapshot ID of the instance\\"s system disk (`SnapshotId`).
-     *   - **Create a custom image from a system disk snapshot and data disk snapshots**: Map the snapshots to disks by using the `DiskDeviceMapping` parameter.
-     *     - You can specify only one system disk snapshot.
-     *     - You can specify up to 16 data disk snapshots. If you do not specify `DiskDeviceMapping.N.SnapshotId`, the system creates an empty data disk with the default capacity.
-     * > When you release an instance, the system retains its system disk and converts it to a pay-as-you-go data disk. You cannot use snapshots of this disk to create custom images. If you need a custom image, create it before you release the instance.
+     *   - The instance must be in the Running (`Running`) or Stopped (`Stopped`) state.
+     *   - After the operation is called, a new snapshot is created for each disk of the instance.
+     *   >Notice: Because a running instance may have cached data that has not been written to disks, the data of the created custom image may be inconsistent with the instance data. Stop the instance ([StopInstances](https://help.aliyun.com/document_detail/155372.html)) before creating the image.
+     * - **Create a custom image from a snapshot (the specified snapshot cannot be one created on or before July 15, 2013.)**
+     *   - **Create a custom image from a system disk snapshot**: Specify only the snapshot ID of the instance system disk (`SnapshotId`).
+     *   - **Create a custom image from system disk and data disk snapshots**: Establish data associations among multiple disks (`DiskDeviceMapping`).
+     *     -  Only one system disk snapshot can be specified.
+     *     -  You can specify multiple data disk snapshots, up to a maximum of 16. If `DiskDeviceMapping.N.SnapshotId` is not specified, an empty data disk with the default capacity is created.
+     *
+     * > When an instance is released, the system disk is retained as a pay-as-you-go data disk. Snapshots created from this disk do not support creating custom images. Create a custom image before releasing the instance as needed.
      *
      * @param request - CreateImageRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -4115,26 +4116,25 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateImageResponse({}));
     }
     /**
-     * Create a custom image. You can then use the image to create ECS instances (`RunInstances`) or replace the system disk of an instance (`ReplaceSystemDisk`).
+     * Creates a custom image. You can use the created custom image to create ECS instances (RunInstances) or replace the system disk of an instance (ReplaceSystemDisk).
      *
      * @remarks
-     * ### Usage notes
-     * - This operation is asynchronous. A successful request returns an image ID, but the image is not created immediately. You can call [DescribeImage](https://help.aliyun.com/document_detail/2679797.html) to query the image status. The image is ready for use when its status changes to `Available`. For more information, see [Overview of custom images](https://help.aliyun.com/document_detail/172789.html).
-     * - If the response to a query for ECS instance information contains `{"OperationLocks": {"LockReason" : "security"}}`, you cannot create a custom image from the instance.
-     * - We recommend configuring the image check parameter `DetectionStrategy` when you create an image. This helps the system optimize your image. For more information, see [Overview of image check](https://help.aliyun.com/document_detail/439819.html).
-     * This operation provides three methods to create a custom image. The request parameters are prioritized as follows: InstanceId > DiskDeviceMapping > SnapshotId. If your request includes two or more of these parameters, the operation creates the image based on the parameter with the highest priority.
+     * ### Before you begin
+     * - This is an asynchronous operation. After a request to create a custom image is sent, the image ID is returned. However, the image creation is not immediately complete. Call [DescribeImage](https://help.aliyun.com/document_detail/2679797.html) to query the image information. When the status in the response is `Available`, the image is created and ready for use. For more information, see [Custom image overview](https://help.aliyun.com/document_detail/172789.html).
+     * - When you query ECS instance information, if the response contains {"OperationLocks": {"LockReason" : "security"}}, you cannot create a custom image.
+     * - Configure the image detection parameter `DetectionStrategy` when creating an image to help the system optimize your image. For more information, see [Image detection overview](https://help.aliyun.com/document_detail/439819.html).
+     * The following describes three methods to create a custom image by calling this operation. The priority of request parameters is: InstanceId > DiskDeviceMapping > SnapshotId. If your request contains two or more of these parameters, the image is created based on the parameter with the highest priority.
      * - **Create a custom image from an instance**: Specify the instance ID (`InstanceId`).
-     *   - The instance must be in the `Running` or `Stopped` state.
-     *   - A successful call creates a new snapshot for each cloud disk of the instance.
-     *   >Notice:
-     *   Data cached in memory on a running instance may not be written to disk. This can cause data inconsistencies between the custom image and the instance. We recommend stopping the instance by calling [StopInstances](https://help.aliyun.com/document_detail/155372.html) before creating an image.
-     *
-     * - **Create a custom image from a snapshot (snapshots created on or before July 15, 2013, cannot be used).**
-     *   - **Create a custom image from a system disk snapshot**: Specify only the snapshot ID of the instance\\"s system disk (`SnapshotId`).
-     *   - **Create a custom image from a system disk snapshot and data disk snapshots**: Map the snapshots to disks by using the `DiskDeviceMapping` parameter.
-     *     - You can specify only one system disk snapshot.
-     *     - You can specify up to 16 data disk snapshots. If you do not specify `DiskDeviceMapping.N.SnapshotId`, the system creates an empty data disk with the default capacity.
-     * > When you release an instance, the system retains its system disk and converts it to a pay-as-you-go data disk. You cannot use snapshots of this disk to create custom images. If you need a custom image, create it before you release the instance.
+     *   - The instance must be in the Running (`Running`) or Stopped (`Stopped`) state.
+     *   - After the operation is called, a new snapshot is created for each disk of the instance.
+     *   >Notice: Because a running instance may have cached data that has not been written to disks, the data of the created custom image may be inconsistent with the instance data. Stop the instance ([StopInstances](https://help.aliyun.com/document_detail/155372.html)) before creating the image.
+     * - **Create a custom image from a snapshot (the specified snapshot cannot be one created on or before July 15, 2013.)**
+     *   - **Create a custom image from a system disk snapshot**: Specify only the snapshot ID of the instance system disk (`SnapshotId`).
+     *   - **Create a custom image from system disk and data disk snapshots**: Establish data associations among multiple disks (`DiskDeviceMapping`).
+     *     -  Only one system disk snapshot can be specified.
+     *     -  You can specify multiple data disk snapshots, up to a maximum of 16. If `DiskDeviceMapping.N.SnapshotId` is not specified, an empty data disk with the default capacity is created.
+     *
+     * > When an instance is released, the system disk is retained as a pay-as-you-go data disk. Snapshots created from this disk do not support creating custom images. Create a custom image before releasing the instance as needed.
      *
      * @param request - CreateImageRequest
      * @returns CreateImageResponse
@@ -4144,13 +4144,13 @@ class Client extends openapi_core_1.default {
         return await this.createImageWithOptions(request, runtime);
     }
     /**
-     * Creates an image component. Image components store commonly used build template commands for image building.
+     * Creates an image component. Image components are used to store commonly used build template commands for image building.
      *
      * @remarks
      * ## Operation description
      * Before you create an image component, take note of the following items:
-     * - You can create only custom image components.
-     * - Component version numbers must be unique for components with the same name. When you use a component in a template, you can reference it by name and version number.
+     * - Only custom image components can be created.
+     * - Component version numbers must be unique for the same component name. When using a component in a template, you can reference it by name and version number.
      * - The content size of an image component cannot exceed 16 KB. For details about supported commands, see [Commands supported by Image Builder](https://help.aliyun.com/document_detail/200206.html).
      * For more information, see [Image Builder overview](https://help.aliyun.com/document_detail/197410.html).
      *
@@ -4226,13 +4226,13 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateImageComponentResponse({}));
     }
     /**
-     * Creates an image component. Image components store commonly used build template commands for image building.
+     * Creates an image component. Image components are used to store commonly used build template commands for image building.
      *
      * @remarks
      * ## Operation description
      * Before you create an image component, take note of the following items:
-     * - You can create only custom image components.
-     * - Component version numbers must be unique for components with the same name. When you use a component in a template, you can reference it by name and version number.
+     * - Only custom image components can be created.
+     * - Component version numbers must be unique for the same component name. When using a component in a template, you can reference it by name and version number.
      * - The content size of an image component cannot exceed 16 KB. For details about supported commands, see [Commands supported by Image Builder](https://help.aliyun.com/document_detail/200206.html).
      * For more information, see [Image Builder overview](https://help.aliyun.com/document_detail/197410.html).
      *
@@ -4392,31 +4392,32 @@ class Client extends openapi_core_1.default {
         return await this.createImagePipelineWithOptions(request, runtime);
     }
     /**
-     * Use this API to create a single subscription or pay-as-you-go Alibaba Cloud ECS instance. You can configure parameters to customize the instance.
+     * Creates a subscription or pay-as-you-go Elastic Compute Service (ECS) instance with customizable parameters.
      *
      * @remarks
-     * > This API is deprecated. We recommend that you use the [RunInstances](https://help.aliyun.com/document_detail/2679677.html) API instead.
+     * > This operation is no longer maintained. Use [RunInstances](https://help.aliyun.com/document_detail/2679677.html) instead.
      * <props="china">
-     * **Before using this API, ensure you understand the billing methods and [Pricing](https://www.aliyun.com/price/product#/ecs/detail) of ECS.**
+     * **Before you call this operation, make sure that you fully understand the billing methods and [pricing](https://www.aliyun.com/price/product#/ecs/detail) of ECS.**
      * <props="intl">
-     * **Before using this API, ensure you understand the billing methods and [Pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS.**
-     * A successful call to this API returns an instance ID, but the instance is created asynchronously. Call [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) to query the instance\\"s status. The instance is successfully created when its status becomes `Stopped`. You can then call [StartInstance](https://help.aliyun.com/document_detail/2679679.html) to start the instance.
-     * ### Usage notes
+     * **Before you call this operation, make sure that you fully understand the billing methods and [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS.**
+     * This is an asynchronous operation. After a request to create an instance is sent, the instance ID is returned. The instance is not immediately created. Call [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) to query the instance status. When the status is `Stopped`, the instance is created. Then you can call [StartInstance](https://help.aliyun.com/document_detail/2679679.html) to start the instance.
+     * ### Before you begin
      * <props="china">
-     * - Make sure that your account has passed real-name verification. For more information, see [Account real-name verification](https://help.aliyun.com/document_detail/48263.html).
-     * - Creating an instance incurs charges. Make sure that you understand the billing methods for ECS. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
-     * - Ensure you do not exceed your quotas for the total number of instances or vCPUs. For more information, see [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas).
-     * - Before creating a VPC-type instance, you must [create a VPC](https://help.aliyun.com/document_detail/65430.html) in the same region.
-     * ### Precautions
-     * - Calling this API does not trigger system notifications (such as SMS messages, emails, or in-site messages) to indicate that the instance is successfully created.
-     * - If the billing method for the instance is subscription (`PrePaid`), your available coupons are automatically used at checkout.
-     * - Instances with 512 MiB of memory support only Windows Server images from the semiannual channel. Instances with 4 GiB or more of memory do not support 32-bit operating system images.
-     * - Instances created with this API are not assigned a public IP address. If the public bandwidth is greater than 0, you can call [AllocatePublicIpAddress](https://help.aliyun.com/document_detail/25544.html) to assign one. If the public bandwidth is 0, you must first call [ModifyInstanceNetworkSpec](https://help.aliyun.com/document_detail/2679879.html) to adjust the bandwidth, and then call [AllocatePublicIpAddress](https://help.aliyun.com/document_detail/25544.html) to assign a public IP address.
-     * > A single Alibaba Cloud account has a limit on the total peak public bandwidth for all pay-by-bandwidth resources within a region. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
+     * - Make sure that your account has passed real-name registration. For more information, see [Real-name registration documentation](https://help.aliyun.com/document_detail/48263.html).
+     * - Creating an instance incurs charges. Make sure that you understand the billable methods of Elastic Computing Service (ECS). For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
+     *
+     * - Make sure that the total number of instances or the total number of vCPUs across all instance types does not exceed the quota. For more information, see [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas).
+     * - Before creating a VPC-connected instance, create a VPC in the corresponding region. For more information, see [Create a VPC](https://help.aliyun.com/document_detail/65430.html).
+     * ### Before you begin
+     * - When you invoke this operation, the system does not send notifications (including text messages, emails, or internal messages) about instance creation.
+     * - If the billable methods of the instance is subscription (`PrePaid`), active coupon in your account are used by default during payment.
+     * - If the instance memory is 512 MiB, you cannot use Windows Server images except through the half-year channel. If the instance memory is 4 GiB or more, you cannot use 32-bit operating system images.
+     * - Instances created by invoking this operation are not assigned Internet IP addresses. If the public bandwidth is greater than 0, invoke [AllocatePublicIpAddress](https://help.aliyun.com/document_detail/25544.html) to assign a public IP address. If the public bandwidth is 0, invoke [ModifyInstanceNetworkSpec](https://help.aliyun.com/document_detail/2679879.html) to adjust the bandwidth and then invoke [AllocatePublicIpAddress](https://help.aliyun.com/document_detail/25544.html) to assign a public IP address.
+     * > In a single region, the total peak pay-by-bandwidth Internet bandwidth for a single Alibaba Cloud account is limited. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
      * ### Recommendations
-     * - **Select an instance type**: See [Instance type families](https://help.aliyun.com/document_detail/25378.html), call [DescribeInstanceTypes](https://help.aliyun.com/document_detail/25620.html) to view the performance data of your target instance type, or see [Select an instance type](https://help.aliyun.com/document_detail/58291.html) for guidance on how to select an instance type.
-     * - **Check resource availability**: Call [DescribeAvailableResource](https://help.aliyun.com/document_detail/66186.html) to check the availability of resources in a specific region or zone.
-     * - **User data**: If your instance meets the requirements described in [Use instance user data](https://help.aliyun.com/document_detail/49121.html), you can pass user data to it. The `UserData` parameter is sent unencrypted. We recommend that you do not pass confidential information, such as passwords and private keys, in plaintext. If you must pass such information, encrypt and then Base64-encode it before passing it. The instance can then decrypt and use the data.
+     * - **Instance type selection**: See [Instance family](https://help.aliyun.com/document_detail/25378.html) or invoke [DescribeInstanceTypes](https://help.aliyun.com/document_detail/25620.html) to query the performance data of the target instance type. You can also see [Settings for instance type selection](https://help.aliyun.com/document_detail/58291.html) to learn how to select an instance type.
+     * - **Check active resources**: Invoke [DescribeAvailableResource](https://help.aliyun.com/document_detail/66186.html) to query active resources in a specific region or zone.
+     * - **User data**: If the instance meets the requirements for [instance user data](https://help.aliyun.com/document_detail/49121.html), you can pass in UserData. The `UserData` data is not encrypted when the API request is sent. Do not send confidential information such as passwords or private keys in plaintext. If you must pass in such information, encrypt it and use Base64 encoding before passing it in. Then perform decryption inside the instance.
      *
      * @param request - CreateInstanceRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -4625,31 +4626,32 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateInstanceResponse({}));
     }
     /**
-     * Use this API to create a single subscription or pay-as-you-go Alibaba Cloud ECS instance. You can configure parameters to customize the instance.
+     * Creates a subscription or pay-as-you-go Elastic Compute Service (ECS) instance with customizable parameters.
      *
      * @remarks
-     * > This API is deprecated. We recommend that you use the [RunInstances](https://help.aliyun.com/document_detail/2679677.html) API instead.
+     * > This operation is no longer maintained. Use [RunInstances](https://help.aliyun.com/document_detail/2679677.html) instead.
      * <props="china">
-     * **Before using this API, ensure you understand the billing methods and [Pricing](https://www.aliyun.com/price/product#/ecs/detail) of ECS.**
+     * **Before you call this operation, make sure that you fully understand the billing methods and [pricing](https://www.aliyun.com/price/product#/ecs/detail) of ECS.**
      * <props="intl">
-     * **Before using this API, ensure you understand the billing methods and [Pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS.**
-     * A successful call to this API returns an instance ID, but the instance is created asynchronously. Call [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) to query the instance\\"s status. The instance is successfully created when its status becomes `Stopped`. You can then call [StartInstance](https://help.aliyun.com/document_detail/2679679.html) to start the instance.
-     * ### Usage notes
+     * **Before you call this operation, make sure that you fully understand the billing methods and [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS.**
+     * This is an asynchronous operation. After a request to create an instance is sent, the instance ID is returned. The instance is not immediately created. Call [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) to query the instance status. When the status is `Stopped`, the instance is created. Then you can call [StartInstance](https://help.aliyun.com/document_detail/2679679.html) to start the instance.
+     * ### Before you begin
      * <props="china">
-     * - Make sure that your account has passed real-name verification. For more information, see [Account real-name verification](https://help.aliyun.com/document_detail/48263.html).
-     * - Creating an instance incurs charges. Make sure that you understand the billing methods for ECS. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
-     * - Ensure you do not exceed your quotas for the total number of instances or vCPUs. For more information, see [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas).
-     * - Before creating a VPC-type instance, you must [create a VPC](https://help.aliyun.com/document_detail/65430.html) in the same region.
-     * ### Precautions
-     * - Calling this API does not trigger system notifications (such as SMS messages, emails, or in-site messages) to indicate that the instance is successfully created.
-     * - If the billing method for the instance is subscription (`PrePaid`), your available coupons are automatically used at checkout.
-     * - Instances with 512 MiB of memory support only Windows Server images from the semiannual channel. Instances with 4 GiB or more of memory do not support 32-bit operating system images.
-     * - Instances created with this API are not assigned a public IP address. If the public bandwidth is greater than 0, you can call [AllocatePublicIpAddress](https://help.aliyun.com/document_detail/25544.html) to assign one. If the public bandwidth is 0, you must first call [ModifyInstanceNetworkSpec](https://help.aliyun.com/document_detail/2679879.html) to adjust the bandwidth, and then call [AllocatePublicIpAddress](https://help.aliyun.com/document_detail/25544.html) to assign a public IP address.
-     * > A single Alibaba Cloud account has a limit on the total peak public bandwidth for all pay-by-bandwidth resources within a region. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
+     * - Make sure that your account has passed real-name registration. For more information, see [Real-name registration documentation](https://help.aliyun.com/document_detail/48263.html).
+     * - Creating an instance incurs charges. Make sure that you understand the billable methods of Elastic Computing Service (ECS). For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
+     *
+     * - Make sure that the total number of instances or the total number of vCPUs across all instance types does not exceed the quota. For more information, see [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas).
+     * - Before creating a VPC-connected instance, create a VPC in the corresponding region. For more information, see [Create a VPC](https://help.aliyun.com/document_detail/65430.html).
+     * ### Before you begin
+     * - When you invoke this operation, the system does not send notifications (including text messages, emails, or internal messages) about instance creation.
+     * - If the billable methods of the instance is subscription (`PrePaid`), active coupon in your account are used by default during payment.
+     * - If the instance memory is 512 MiB, you cannot use Windows Server images except through the half-year channel. If the instance memory is 4 GiB or more, you cannot use 32-bit operating system images.
+     * - Instances created by invoking this operation are not assigned Internet IP addresses. If the public bandwidth is greater than 0, invoke [AllocatePublicIpAddress](https://help.aliyun.com/document_detail/25544.html) to assign a public IP address. If the public bandwidth is 0, invoke [ModifyInstanceNetworkSpec](https://help.aliyun.com/document_detail/2679879.html) to adjust the bandwidth and then invoke [AllocatePublicIpAddress](https://help.aliyun.com/document_detail/25544.html) to assign a public IP address.
+     * > In a single region, the total peak pay-by-bandwidth Internet bandwidth for a single Alibaba Cloud account is limited. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
      * ### Recommendations
-     * - **Select an instance type**: See [Instance type families](https://help.aliyun.com/document_detail/25378.html), call [DescribeInstanceTypes](https://help.aliyun.com/document_detail/25620.html) to view the performance data of your target instance type, or see [Select an instance type](https://help.aliyun.com/document_detail/58291.html) for guidance on how to select an instance type.
-     * - **Check resource availability**: Call [DescribeAvailableResource](https://help.aliyun.com/document_detail/66186.html) to check the availability of resources in a specific region or zone.
-     * - **User data**: If your instance meets the requirements described in [Use instance user data](https://help.aliyun.com/document_detail/49121.html), you can pass user data to it. The `UserData` parameter is sent unencrypted. We recommend that you do not pass confidential information, such as passwords and private keys, in plaintext. If you must pass such information, encrypt and then Base64-encode it before passing it. The instance can then decrypt and use the data.
+     * - **Instance type selection**: See [Instance family](https://help.aliyun.com/document_detail/25378.html) or invoke [DescribeInstanceTypes](https://help.aliyun.com/document_detail/25620.html) to query the performance data of the target instance type. You can also see [Settings for instance type selection](https://help.aliyun.com/document_detail/58291.html) to learn how to select an instance type.
+     * - **Check active resources**: Invoke [DescribeAvailableResource](https://help.aliyun.com/document_detail/66186.html) to query active resources in a specific region or zone.
+     * - **User data**: If the instance meets the requirements for [instance user data](https://help.aliyun.com/document_detail/49121.html), you can pass in UserData. The `UserData` data is not encrypted when the API request is sent. Do not send confidential information such as passwords or private keys in plaintext. If you must pass in such information, encrypt it and use Base64 encoding before passing it in. Then perform decryption inside the instance.
      *
      * @param request - CreateInstanceRequest
      * @returns CreateInstanceResponse
@@ -4724,15 +4726,15 @@ class Client extends openapi_core_1.default {
         return await this.createKeyPairWithOptions(request, runtime);
     }
     /**
-     * Create an ECS instance launch template, abbreviated as a template. An instance launch template eliminates the need to enter numerous configuration parameters each time you create an instance.
+     * Creates an ECS instance launch template. A launch template eliminates the need to configure a large number of parameters every time you create an instance.
      *
      * @remarks
-     * After you invoke CreateLaunchTemplate to create a template, Alibaba Cloud automatically generates a default version of the template with version number 1. You can subsequently create multiple versions based on this template by calling `CreateLaunchTemplateVersion`. Version numbers start from 1 and increment sequentially. If you do not specify a template version when creating an instance ([RunInstances](https://help.aliyun.com/document_detail/63440.html)), the default version is used.
-     * A launch template version includes configurations required for instance creation, such as the Region, image ID, instance type, security group ID, and Internet bandwidth. If a particular configuration is not specified in the template version, you must provide it explicitly when creating the instance.
-     * When invoking this API, note the following:
-     * - Each account can create up to 30 launch templates per Region, and each template can have up to 30 versions.
-     * - Most parameters in a launch template are optional. Alibaba Cloud does not validate the existence or validity of parameter values when you create the template. Validation occurs only when you actually create an instance.
-     * - If a configuration is set in the launch template, you cannot omit it when creating an instance ([RunInstances](https://help.aliyun.com/document_detail/63440.html)). For example, if the template sets `HostName=LocalHost`, and you leave `HostName` empty in `RunInstances`, the instance hostname will still be `LocalHost`. To overwrite the `HostName=LocalHost` setting, specify a different value such as `HostName=MyHost` in `RunInstances`.
+     * After you call CreateLaunchTemplate to create a template, a default version with version number 1 is automatically generated. You can then create multiple versions based on this template (`CreateLaunchTemplateVersion`), with version numbers incrementing sequentially from 1. If you do not specify a template version when creating instances ([RunInstances](https://help.aliyun.com/document_detail/63440.html)), the default version is used.
+     * A launch template version contains the configurations for creating instances, such as the region, image ID, instance type, security group ID, and public bandwidth. If a specific configuration is not specified in the version, you must specify it when you create instances.
+     * When you call this operation, take note of the following items:
+     * -   Each account can create up to 30 launch templates per region, and each template can have up to 30 versions.
+     * -   Most parameters in a launch template are optional. When you create a template, Alibaba Cloud does not verify the existence or validity of parameter values. The validity of parameter values is verified only when you create instances.
+     * -   If a configuration is specified in the launch template, it cannot be filtered out when you create instances ([RunInstances](https://help.aliyun.com/document_detail/63440.html)). For example, if the template specifies `HostName=LocalHost` and the `HostName` value is left empty in `RunInstances`, the hostname of the instance is still `LocalHost`. To override the `HostName=LocalHost` configuration, set `HostName=MyHost` or another value in `RunInstances`.
      *
      * @param request - CreateLaunchTemplateRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -4926,15 +4928,15 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateLaunchTemplateResponse({}));
     }
     /**
-     * Create an ECS instance launch template, abbreviated as a template. An instance launch template eliminates the need to enter numerous configuration parameters each time you create an instance.
+     * Creates an ECS instance launch template. A launch template eliminates the need to configure a large number of parameters every time you create an instance.
      *
      * @remarks
-     * After you invoke CreateLaunchTemplate to create a template, Alibaba Cloud automatically generates a default version of the template with version number 1. You can subsequently create multiple versions based on this template by calling `CreateLaunchTemplateVersion`. Version numbers start from 1 and increment sequentially. If you do not specify a template version when creating an instance ([RunInstances](https://help.aliyun.com/document_detail/63440.html)), the default version is used.
-     * A launch template version includes configurations required for instance creation, such as the Region, image ID, instance type, security group ID, and Internet bandwidth. If a particular configuration is not specified in the template version, you must provide it explicitly when creating the instance.
-     * When invoking this API, note the following:
-     * - Each account can create up to 30 launch templates per Region, and each template can have up to 30 versions.
-     * - Most parameters in a launch template are optional. Alibaba Cloud does not validate the existence or validity of parameter values when you create the template. Validation occurs only when you actually create an instance.
-     * - If a configuration is set in the launch template, you cannot omit it when creating an instance ([RunInstances](https://help.aliyun.com/document_detail/63440.html)). For example, if the template sets `HostName=LocalHost`, and you leave `HostName` empty in `RunInstances`, the instance hostname will still be `LocalHost`. To overwrite the `HostName=LocalHost` setting, specify a different value such as `HostName=MyHost` in `RunInstances`.
+     * After you call CreateLaunchTemplate to create a template, a default version with version number 1 is automatically generated. You can then create multiple versions based on this template (`CreateLaunchTemplateVersion`), with version numbers incrementing sequentially from 1. If you do not specify a template version when creating instances ([RunInstances](https://help.aliyun.com/document_detail/63440.html)), the default version is used.
+     * A launch template version contains the configurations for creating instances, such as the region, image ID, instance type, security group ID, and public bandwidth. If a specific configuration is not specified in the version, you must specify it when you create instances.
+     * When you call this operation, take note of the following items:
+     * -   Each account can create up to 30 launch templates per region, and each template can have up to 30 versions.
+     * -   Most parameters in a launch template are optional. When you create a template, Alibaba Cloud does not verify the existence or validity of parameter values. The validity of parameter values is verified only when you create instances.
+     * -   If a configuration is specified in the launch template, it cannot be filtered out when you create instances ([RunInstances](https://help.aliyun.com/document_detail/63440.html)). For example, if the template specifies `HostName=LocalHost` and the `HostName` value is left empty in `RunInstances`, the hostname of the instance is still `LocalHost`. To override the `HostName=LocalHost` configuration, set `HostName=MyHost` or another value in `RunInstances`.
      *
      * @param request - CreateLaunchTemplateRequest
      * @returns CreateLaunchTemplateResponse
@@ -4944,11 +4946,11 @@ class Client extends openapi_core_1.default {
         return await this.createLaunchTemplateWithOptions(request, runtime);
     }
     /**
-     * Create a new version under the specified ECS instance launch template for subsequent creation of ECS instances, scaling groups, or auto provisioning groups.
+     * Creates a new version in a specified ECS launch template for subsequent creation of ECS instances, elastic scaling groups, or auto provisioning groups.
      *
      * @remarks
-     * ## API Guide
-     * When you want to modify parameters of a specific version, you can do so by creating a new template version. Each launch template supports up to 30 versions.
+     * ## Operation description
+     * To modify the parameters of a specific version, create a new template version. Each instance launch template supports a maximum of 30 versions.
      *
      * @param request - CreateLaunchTemplateVersionRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -5139,11 +5141,11 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateLaunchTemplateVersionResponse({}));
     }
     /**
-     * Create a new version under the specified ECS instance launch template for subsequent creation of ECS instances, scaling groups, or auto provisioning groups.
+     * Creates a new version in a specified ECS launch template for subsequent creation of ECS instances, elastic scaling groups, or auto provisioning groups.
      *
      * @remarks
-     * ## API Guide
-     * When you want to modify parameters of a specific version, you can do so by creating a new template version. Each launch template supports up to 30 versions.
+     * ## Operation description
+     * To modify the parameters of a specific version, create a new template version. Each instance launch template supports a maximum of 30 versions.
      *
      * @param request - CreateLaunchTemplateVersionRequest
      * @returns CreateLaunchTemplateVersionResponse
@@ -6093,10 +6095,10 @@ class Client extends openapi_core_1.default {
      * Creates a security group.
      *
      * @remarks
-     * - 通过该接口创建的普通安全组组内连通策略默认是**组内互通**，您可以通过 [ModifySecurityGroupPolicy](https://help.aliyun.com/document_detail/2679846.html) 进行修改。
-     * - 通过该接口创建的企业安全组组内连通策略默认是**组内隔离**，并且不能修改。
-     * - 单个地域下，安全组的数量有限制，您最少可以创建 100 个安全组。详细信息，请参见[安全组使用限制](~~25412#SecurityGroupQuota1~~)。
-     * - 创建专有网络 VPC 类型的安全组时，您必须指定参数 VpcId。
+     * - The default internal connectivity policy for a basic security group created by this operation is **intra-group connectivity**. You can modify this policy by calling [ModifySecurityGroupPolicy](https://help.aliyun.com/document_detail/2679846.html).
+     * - The default internal connectivity policy for an advanced security group created by this operation is **internal isolation**, and this policy cannot be modified.
+     * - The number of security groups in a single region is limited. You can create a minimum of 100 security groups. For more information, see [Security group limits](~~25412#SecurityGroupQuota1~~).
+     * - To create a security group of the VPC type, you must specify the VpcId parameter.
      *
      * @param request - CreateSecurityGroupRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -6164,10 +6166,10 @@ class Client extends openapi_core_1.default {
      * Creates a security group.
      *
      * @remarks
-     * - 通过该接口创建的普通安全组组内连通策略默认是**组内互通**，您可以通过 [ModifySecurityGroupPolicy](https://help.aliyun.com/document_detail/2679846.html) 进行修改。
-     * - 通过该接口创建的企业安全组组内连通策略默认是**组内隔离**，并且不能修改。
-     * - 单个地域下，安全组的数量有限制，您最少可以创建 100 个安全组。详细信息，请参见[安全组使用限制](~~25412#SecurityGroupQuota1~~)。
-     * - 创建专有网络 VPC 类型的安全组时，您必须指定参数 VpcId。
+     * - The default internal connectivity policy for a basic security group created by this operation is **intra-group connectivity**. You can modify this policy by calling [ModifySecurityGroupPolicy](https://help.aliyun.com/document_detail/2679846.html).
+     * - The default internal connectivity policy for an advanced security group created by this operation is **internal isolation**, and this policy cannot be modified.
+     * - The number of security groups in a single region is limited. You can create a minimum of 100 security groups. For more information, see [Security group limits](~~25412#SecurityGroupQuota1~~).
+     * - To create a security group of the VPC type, you must specify the VpcId parameter.
      *
      * @param request - CreateSecurityGroupRequest
      * @returns CreateSecurityGroupResponse
@@ -7618,7 +7620,7 @@ class Client extends openapi_core_1.default {
         return await this.deleteHaVipWithOptions(request, runtime);
     }
     /**
-     * Deletes a High Performance Computing (HPC) cluster.
+     * Calls DeleteHpcCluster to delete an HPC cluster.
      *
      * @param request - DeleteHpcClusterRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -7668,7 +7670,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteHpcClusterResponse({}));
     }
     /**
-     * Deletes a High Performance Computing (HPC) cluster.
+     * Calls DeleteHpcCluster to delete an HPC cluster.
      *
      * @param request - DeleteHpcClusterRequest
      * @returns DeleteHpcClusterResponse
@@ -7812,7 +7814,7 @@ class Client extends openapi_core_1.default {
      * Deletes an image template.
      *
      * @remarks
-     * If a build task is running, you cannot directly delete the template. Wait until the build task reaches a desired state: SUCCESS, FAILED, TEST_FAILED, PARTITION_SUCCESS, or CANCELLED. You can call [DescribeImagePipelineExecutions](https://help.aliyun.com/document_detail/25609.html) to query the details of build tasks.
+     * If a build task is currently running, you cannot directly delete the template. Wait until the build task reaches a desired state: SUCCESS, FAILED, TEST_FAILED, PARTITION_SUCCESS, or CANCELLED. You can call [DescribeImagePipelineExecutions](https://help.aliyun.com/document_detail/25609.html) to query the details of build tasks.
      *
      * @param request - DeleteImagePipelineRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -7862,7 +7864,7 @@ class Client extends openapi_core_1.default {
      * Deletes an image template.
      *
      * @remarks
-     * If a build task is running, you cannot directly delete the template. Wait until the build task reaches a desired state: SUCCESS, FAILED, TEST_FAILED, PARTITION_SUCCESS, or CANCELLED. You can call [DescribeImagePipelineExecutions](https://help.aliyun.com/document_detail/25609.html) to query the details of build tasks.
+     * If a build task is currently running, you cannot directly delete the template. Wait until the build task reaches a desired state: SUCCESS, FAILED, TEST_FAILED, PARTITION_SUCCESS, or CANCELLED. You can call [DescribeImagePipelineExecutions](https://help.aliyun.com/document_detail/25609.html) to query the details of build tasks.
      *
      * @param request - DeleteImagePipelineRequest
      * @returns DeleteImagePipelineResponse
@@ -8618,10 +8620,10 @@ class Client extends openapi_core_1.default {
         return await this.deletePortRangeListWithOptions(request, runtime);
     }
     /**
-     * Deletes a specified prefix list and all entries in the prefix list.
+     * Calls DeletePrefixList to delete a specified prefix list and all entries in the prefix list.
      *
      * @remarks
-     * If a prefix list is associated with other resources, you cannot directly delete it. Dissociate the prefix list from the resources first, and then delete it. You can call [DescribePrefixListAssociations](https://help.aliyun.com/document_detail/204724.html) to query the resources that are associated with a specified prefix list.
+     * If a prefix list is associated with other resources, you cannot directly delete it. Dissociate the prefix list from the other resources first, and then delete it. You can call [DescribePrefixListAssociations](https://help.aliyun.com/document_detail/204724.html) to query the resources associated with a specified prefix list.
      *
      * @param request - DeletePrefixListRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -8668,10 +8670,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeletePrefixListResponse({}));
     }
     /**
-     * Deletes a specified prefix list and all entries in the prefix list.
+     * Calls DeletePrefixList to delete a specified prefix list and all entries in the prefix list.
      *
      * @remarks
-     * If a prefix list is associated with other resources, you cannot directly delete it. Dissociate the prefix list from the resources first, and then delete it. You can call [DescribePrefixListAssociations](https://help.aliyun.com/document_detail/204724.html) to query the resources that are associated with a specified prefix list.
+     * If a prefix list is associated with other resources, you cannot directly delete it. Dissociate the prefix list from the other resources first, and then delete it. You can call [DescribePrefixListAssociations](https://help.aliyun.com/document_detail/204724.html) to query the resources associated with a specified prefix list.
      *
      * @param request - DeletePrefixListRequest
      * @returns DeletePrefixListResponse
@@ -9661,7 +9663,7 @@ class Client extends openapi_core_1.default {
         return await this.describeAutoProvisioningGroupHistoryWithOptions(request, runtime);
     }
     /**
-     * Queries information about Elastic Compute Service (ECS) instances in an auto provisioning group.
+     * Queries information about instances in an auto provisioning group.
      *
      * @param request - DescribeAutoProvisioningGroupInstancesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -9711,7 +9713,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeAutoProvisioningGroupInstancesResponse({}));
     }
     /**
-     * Queries information about Elastic Compute Service (ECS) instances in an auto provisioning group.
+     * Queries information about instances in an auto provisioning group.
      *
      * @param request - DescribeAutoProvisioningGroupInstancesRequest
      * @returns DescribeAutoProvisioningGroupInstancesResponse
@@ -9859,7 +9861,7 @@ class Client extends openapi_core_1.default {
         return await this.describeAutoSnapshotPolicyAssociationsWithOptions(request, runtime);
     }
     /**
-     * Queries the details of automatic snapshot policies that are created in a specific region.
+     * Queries the details of automatic snapshot policies that are created in a specified region.
      *
      * @param request - DescribeAutoSnapshotPolicyExRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -9918,7 +9920,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeAutoSnapshotPolicyExResponse({}));
     }
     /**
-     * Queries the details of automatic snapshot policies that are created in a specific region.
+     * Queries the details of automatic snapshot policies that are created in a specified region.
      *
      * @param request - DescribeAutoSnapshotPolicyExRequest
      * @returns DescribeAutoSnapshotPolicyExResponse
@@ -9928,43 +9930,37 @@ class Client extends openapi_core_1.default {
         return await this.describeAutoSnapshotPolicyExWithOptions(request, runtime);
     }
     /**
-     * Use this API to check if a target resource, such as an instance type or a system disk type, has sufficient inventory in a specific availability zone before you call `RunInstances` or `ModifyInstanceSpec`.
+     * Queries the inventory status of resources in a specified zone. This operation is primarily used to check whether target resources, such as instance types and system disk types, are available in a specific zone before you create instances (RunInstances) or modify instance specifications (ModifyInstanceSpec).
      *
      * @remarks
-     * The value of the `DestinationResource` parameter determines which other parameters are required. Values with lower precedence require more parameters. You cannot use a lower-precedence value to filter for a higher-precedence resource category.
-     * - Value precedence: `Zone > IoOptimized > InstanceType = Network = ddh > SystemDisk > DataDisk`
+     * The DestinationResource parameter has different logic and requirements depending on its value. In the following ordered list, a lower-ranked value requires more parameters to be set. You cannot use a lower-ranked value to filter resources of a higher-ranked category.
+     * - Value order: `Zone > IoOptimized > InstanceType = Network = ddh > SystemDisk > DataDisk`
      * - Examples:
-     *   - If `DestinationResource` is set to `DataDisk`:
-     *     - If you set `ResourceType` to `disk`, you query for data disk types that are independent of a specific ECS instance type. You do not need to specify the `InstanceType` parameter.
-     *     - If you set `ResourceType` to `instance`, you query for data disk types to be attached to an ECS instance. Because the instance type imposes limits on compatible data disks, both the `InstanceType` and `DataDiskCategory` parameters are required.
-     *   - When `DestinationResource` is set to `SystemDisk` and `ResourceType` is set to `instance`, the `InstanceType` parameter is required because the instance type imposes limits on the system disk.
-     *   - If `DestinationResource` is set to `InstanceType`, we recommend specifying the `IoOptimized` and `InstanceType` parameters.
-     *   - To query the inventory of the `ecs.g5.large` instance type in all availability zones in the `cn-hangzhou` region: `RegionId=cn-hangzhou &DestinationResource=InstanceType &IoOptimized=optimized &InstanceType=ecs.g5.large`.
-     *   - To query for availability zones in the `cn-hangzhou` region that have `ecs.g5.large` inventory: `RegionId=cn-hangzhou &DestinationResource=Zone &IoOptimized=optimized &InstanceType=ecs.g5.large`.
+     *     - If DestinationResource is set to `DataDisk`:
+     *          - If `ResourceType` is set to `disk`, the operation queries data disk types that are not associated with a specific ECS instance type. In this case, the InstanceType parameter is optional.
+     *         - If `ResourceType` is set to `instance`, the operation queries data disk types that can be attached to an ECS instance. Because instance types impose restrictions on data disks, you must specify both `InstanceType` and `DataDiskCategory`.
+     *     - If DestinationResource is set to `SystemDisk` and `ResourceType` is set to `instance`, you must specify the InstanceType parameter because ECS instance types impose restrictions on system disks.
+     *     - If DestinationResource is set to `InstanceType`, specify the IoOptimized and InstanceType parameters.
+     *     - Query the inventory of ecs.g5.large across all zones in a specified region: `RegionId=ap-southeast-1 &DestinationResource=InstanceType &IoOptimized=optimized &InstanceType=ecs.g5.large`.
+     *     - Query the zones in a specified region where ecs.g5.large is available: `RegionId=ap-southeast-1 &DestinationResource=Zone &IoOptimized=optimized &InstanceType=ecs.g5.large`.
      * <details>
-     * <summary>
-     * Query for availability zones in the China (Hangzhou) region that have the `ecs.g5.large` instance type.
-     * </summary>
+     * <summary>Query the zones in the China (Hangzhou) region where the ecs.g5.large instance type is available.</summary>
      * ```
      * "RegionId": "cn-hangzhou",
-     * "DestinationResource": "Zone",
+     * "DestinationResource": "Zone"，
      * "InstanceType": "ecs.g5.large"
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query the inventory of the `ecs.g5.large` instance type across all availability zones in the China (Hangzhou) region.
-     * </summary>
+     * <summary>Query the inventory of the ecs.g5.large instance type across all zones in the China (Hangzhou) region.</summary>
      * ```
      * "RegionId": "cn-hangzhou",
-     * "DestinationResource": "InstanceType",
+     * "DestinationResource": "InstanceType"，
      * "InstanceType": "ecs.g5.large"
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query the inventory of `cloud_efficiency` data disks in availability zone b of the China (Hangzhou) region, independent of any ECS instance type.
-     * </summary>
+     * <summary>[Purchase only a data disk] Query the inventory of the cloud_efficiency data disk type in Zone B of the China (Hangzhou) region.</summary>
      * ```
      * "RegionId": "cn-hangzhou",
      * "ZoneId": "cn-hangzhou-b",
@@ -9973,9 +9969,7 @@ class Client extends openapi_core_1.default {
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query the inventory of `cloud_essd` system disks for the `ecs.g7.large` instance type in availability zone b of the China (Hangzhou) region.
-     * </summary>
+     * <summary>[Purchase an ECS instance and a system disk] Query the inventory of the ecs.g7.large instance type with the cloud_essd system disk type in Zone B of the China (Hangzhou) region.</summary>
      * ```
      * "RegionId": "cn-hangzhou",
      * "ZoneId": "cn-hangzhou-b",
@@ -10070,43 +10064,37 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeAvailableResourceResponse({}));
     }
     /**
-     * Use this API to check if a target resource, such as an instance type or a system disk type, has sufficient inventory in a specific availability zone before you call `RunInstances` or `ModifyInstanceSpec`.
+     * Queries the inventory status of resources in a specified zone. This operation is primarily used to check whether target resources, such as instance types and system disk types, are available in a specific zone before you create instances (RunInstances) or modify instance specifications (ModifyInstanceSpec).
      *
      * @remarks
-     * The value of the `DestinationResource` parameter determines which other parameters are required. Values with lower precedence require more parameters. You cannot use a lower-precedence value to filter for a higher-precedence resource category.
-     * - Value precedence: `Zone > IoOptimized > InstanceType = Network = ddh > SystemDisk > DataDisk`
+     * The DestinationResource parameter has different logic and requirements depending on its value. In the following ordered list, a lower-ranked value requires more parameters to be set. You cannot use a lower-ranked value to filter resources of a higher-ranked category.
+     * - Value order: `Zone > IoOptimized > InstanceType = Network = ddh > SystemDisk > DataDisk`
      * - Examples:
-     *   - If `DestinationResource` is set to `DataDisk`:
-     *     - If you set `ResourceType` to `disk`, you query for data disk types that are independent of a specific ECS instance type. You do not need to specify the `InstanceType` parameter.
-     *     - If you set `ResourceType` to `instance`, you query for data disk types to be attached to an ECS instance. Because the instance type imposes limits on compatible data disks, both the `InstanceType` and `DataDiskCategory` parameters are required.
-     *   - When `DestinationResource` is set to `SystemDisk` and `ResourceType` is set to `instance`, the `InstanceType` parameter is required because the instance type imposes limits on the system disk.
-     *   - If `DestinationResource` is set to `InstanceType`, we recommend specifying the `IoOptimized` and `InstanceType` parameters.
-     *   - To query the inventory of the `ecs.g5.large` instance type in all availability zones in the `cn-hangzhou` region: `RegionId=cn-hangzhou &DestinationResource=InstanceType &IoOptimized=optimized &InstanceType=ecs.g5.large`.
-     *   - To query for availability zones in the `cn-hangzhou` region that have `ecs.g5.large` inventory: `RegionId=cn-hangzhou &DestinationResource=Zone &IoOptimized=optimized &InstanceType=ecs.g5.large`.
+     *     - If DestinationResource is set to `DataDisk`:
+     *          - If `ResourceType` is set to `disk`, the operation queries data disk types that are not associated with a specific ECS instance type. In this case, the InstanceType parameter is optional.
+     *         - If `ResourceType` is set to `instance`, the operation queries data disk types that can be attached to an ECS instance. Because instance types impose restrictions on data disks, you must specify both `InstanceType` and `DataDiskCategory`.
+     *     - If DestinationResource is set to `SystemDisk` and `ResourceType` is set to `instance`, you must specify the InstanceType parameter because ECS instance types impose restrictions on system disks.
+     *     - If DestinationResource is set to `InstanceType`, specify the IoOptimized and InstanceType parameters.
+     *     - Query the inventory of ecs.g5.large across all zones in a specified region: `RegionId=ap-southeast-1 &DestinationResource=InstanceType &IoOptimized=optimized &InstanceType=ecs.g5.large`.
+     *     - Query the zones in a specified region where ecs.g5.large is available: `RegionId=ap-southeast-1 &DestinationResource=Zone &IoOptimized=optimized &InstanceType=ecs.g5.large`.
      * <details>
-     * <summary>
-     * Query for availability zones in the China (Hangzhou) region that have the `ecs.g5.large` instance type.
-     * </summary>
+     * <summary>Query the zones in the China (Hangzhou) region where the ecs.g5.large instance type is available.</summary>
      * ```
      * "RegionId": "cn-hangzhou",
-     * "DestinationResource": "Zone",
+     * "DestinationResource": "Zone"，
      * "InstanceType": "ecs.g5.large"
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query the inventory of the `ecs.g5.large` instance type across all availability zones in the China (Hangzhou) region.
-     * </summary>
+     * <summary>Query the inventory of the ecs.g5.large instance type across all zones in the China (Hangzhou) region.</summary>
      * ```
      * "RegionId": "cn-hangzhou",
-     * "DestinationResource": "InstanceType",
+     * "DestinationResource": "InstanceType"，
      * "InstanceType": "ecs.g5.large"
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query the inventory of `cloud_efficiency` data disks in availability zone b of the China (Hangzhou) region, independent of any ECS instance type.
-     * </summary>
+     * <summary>[Purchase only a data disk] Query the inventory of the cloud_efficiency data disk type in Zone B of the China (Hangzhou) region.</summary>
      * ```
      * "RegionId": "cn-hangzhou",
      * "ZoneId": "cn-hangzhou-b",
@@ -10115,9 +10103,7 @@ class Client extends openapi_core_1.default {
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query the inventory of `cloud_essd` system disks for the `ecs.g7.large` instance type in availability zone b of the China (Hangzhou) region.
-     * </summary>
+     * <summary>[Purchase an ECS instance and a system disk] Query the inventory of the ecs.g7.large instance type with the cloud_essd system disk type in Zone B of the China (Hangzhou) region.</summary>
      * ```
      * "RegionId": "cn-hangzhou",
      * "ZoneId": "cn-hangzhou-b",
@@ -11604,14 +11590,14 @@ class Client extends openapi_core_1.default {
         return await this.describeDiskMonitorDataWithOptions(request, runtime);
     }
     /**
-     * Queries information about one or more created block storage devices, including disks, local disks, and elastic ephemeral disks.
+     * Queries information about one or more created block storage devices, including cloud disks, local disks, and elastic ephemeral disks.
      *
      * @remarks
-     * - The request parameters RegionId, ZoneId, DiskIds, and InstanceId are filters. The logical relationship among these parameters is AND.
-     * - The DiskIds request parameter is a JSON format array. If DiskIds is not specified, the filter does not take effect. If DiskIds is set to an empty JSON array, the filter is considered valid and an empty result is returned.
-     * - Token-based paged query is supported. Set NextToken to the NextToken value returned in the previous call of DescribeDisks, and set MaxResults to specify the maximum number of entries per page.
-     * - A disk with the multi-attach feature enabled can be attached to multiple instances. You can check the Attachment list in the response to view all attachment information of the disk.
-     * When you call an API operation by using Cloud Assistant CLI, specify request parameters of different data types in the required formats. For more information, see [Parameter format of CLI](https://help.aliyun.com/document_detail/110340.html).
+     * - The request parameters RegionId, ZoneId, DiskIds, and InstanceId are filters. These parameters have a logical AND relationship.
+     * - The DiskIds request parameter is a JSON format array. If this parameter is empty, the filter does not take effect. However, if DiskIds is an empty array, the filter is considered valid and an empty result is returned.
+     * - Token-based paged query is supported. Set the NextToken parameter to specify the query token. Its value is the NextToken value returned in the previous call of DescribeDisks. Use MaxResults to settings the maximum number of entries per page.
+     * - A cloud disk with the multi-attach feature enabled can be attached to multiple instances. You can view all attachment information for the disk from the Attachment list in the response.
+     * When you invoke an API operation by using Cloud Assistant CLI, specify request parameters of different data types in the required formats. For more information, see [Parameter format overview](https://help.aliyun.com/document_detail/110340.html).
      *
      * @param request - DescribeDisksRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -11739,14 +11725,14 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeDisksResponse({}));
     }
     /**
-     * Queries information about one or more created block storage devices, including disks, local disks, and elastic ephemeral disks.
+     * Queries information about one or more created block storage devices, including cloud disks, local disks, and elastic ephemeral disks.
      *
      * @remarks
-     * - The request parameters RegionId, ZoneId, DiskIds, and InstanceId are filters. The logical relationship among these parameters is AND.
-     * - The DiskIds request parameter is a JSON format array. If DiskIds is not specified, the filter does not take effect. If DiskIds is set to an empty JSON array, the filter is considered valid and an empty result is returned.
-     * - Token-based paged query is supported. Set NextToken to the NextToken value returned in the previous call of DescribeDisks, and set MaxResults to specify the maximum number of entries per page.
-     * - A disk with the multi-attach feature enabled can be attached to multiple instances. You can check the Attachment list in the response to view all attachment information of the disk.
-     * When you call an API operation by using Cloud Assistant CLI, specify request parameters of different data types in the required formats. For more information, see [Parameter format of CLI](https://help.aliyun.com/document_detail/110340.html).
+     * - The request parameters RegionId, ZoneId, DiskIds, and InstanceId are filters. These parameters have a logical AND relationship.
+     * - The DiskIds request parameter is a JSON format array. If this parameter is empty, the filter does not take effect. However, if DiskIds is an empty array, the filter is considered valid and an empty result is returned.
+     * - Token-based paged query is supported. Set the NextToken parameter to specify the query token. Its value is the NextToken value returned in the previous call of DescribeDisks. Use MaxResults to settings the maximum number of entries per page.
+     * - A cloud disk with the multi-attach feature enabled can be attached to multiple instances. You can view all attachment information for the disk from the Attachment list in the response.
+     * When you invoke an API operation by using Cloud Assistant CLI, specify request parameters of different data types in the required formats. For more information, see [Parameter format overview](https://help.aliyun.com/document_detail/110340.html).
      *
      * @param request - DescribeDisksRequest
      * @returns DescribeDisksResponse
@@ -12489,7 +12475,7 @@ class Client extends openapi_core_1.default {
      * Queries the details of one or more image components.
      *
      * @remarks
-     * You can set `NextToken` to the value of `NextToken` returned in the previous call to DescribeImageComponents, and set `MaxResults` to specify the maximum number of entries per page for the query.
+     * You can set NextToken to the value of NextToken returned by the previous call to DescribeImageComponents, and set MaxResults to specify the maximum number of entries per page.
      *
      * @param request - DescribeImageComponentsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -12569,7 +12555,7 @@ class Client extends openapi_core_1.default {
      * Queries the details of one or more image components.
      *
      * @remarks
-     * You can set `NextToken` to the value of `NextToken` returned in the previous call to DescribeImageComponents, and set `MaxResults` to specify the maximum number of entries per page for the query.
+     * You can set NextToken to the value of NextToken returned by the previous call to DescribeImageComponents, and set MaxResults to specify the maximum number of entries per page.
      *
      * @param request - DescribeImageComponentsRequest
      * @returns DescribeImageComponentsResponse
@@ -12923,13 +12909,13 @@ class Client extends openapi_core_1.default {
         return await this.describeImageSupportInstanceTypesWithOptions(request, runtime);
     }
     /**
-     * Specify parameters such as ImageId, image usage scenario, and Filter to query the list of image resources you can use.
+     * Queries the list of available image resources based on specified parameters such as ImageId, image usage scenarios, and filter conditions.
      *
      * @remarks
-     * - The image resources you can query include your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images actively shared with you by other Alibaba Cloud users.
-     * - Paged query is supported. The query results include the total number of usable image resources and the image resources on the current page. The default number of entries per page is 10.
-     * - When invoking the API through the Alibaba Cloud command-line interface (CLI), the values of request parameters of different data types must comply with format requirements. For more information, see [CLI Parameter Format Description](https://help.aliyun.com/document_detail/110340.html).
-     * - When querying official Alibaba Cloud images or shared images (where ImageOwnerAlias is set to system or others), RAM authentication rules are ignored for this request. For more information, see [Authentication Rules](https://help.aliyun.com/document_detail/25497.html).
+     * - Image resources that you can query include your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images that other Alibaba Cloud users have shared with you.
+     * - Paging is supported. The query results include the total number of available image resources and the image resources on the current page. The default number of entries per page is 10.
+     * - When you invoke an API operation by using Cloud Assistant CLI, request parameters of different data types must comply with format requirements. For more information, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
+     * - When you query images provided by Alibaba Cloud or shared images (ImageOwnerAlias is set to system or others), the request can bypass RAM authentication rules. For more information, see [Authentication rules](https://help.aliyun.com/document_detail/25497.html).
      *
      * @param request - DescribeImagesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -13036,13 +13022,13 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeImagesResponse({}));
     }
     /**
-     * Specify parameters such as ImageId, image usage scenario, and Filter to query the list of image resources you can use.
+     * Queries the list of available image resources based on specified parameters such as ImageId, image usage scenarios, and filter conditions.
      *
      * @remarks
-     * - The image resources you can query include your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images actively shared with you by other Alibaba Cloud users.
-     * - Paged query is supported. The query results include the total number of usable image resources and the image resources on the current page. The default number of entries per page is 10.
-     * - When invoking the API through the Alibaba Cloud command-line interface (CLI), the values of request parameters of different data types must comply with format requirements. For more information, see [CLI Parameter Format Description](https://help.aliyun.com/document_detail/110340.html).
-     * - When querying official Alibaba Cloud images or shared images (where ImageOwnerAlias is set to system or others), RAM authentication rules are ignored for this request. For more information, see [Authentication Rules](https://help.aliyun.com/document_detail/25497.html).
+     * - Image resources that you can query include your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images that other Alibaba Cloud users have shared with you.
+     * - Paging is supported. The query results include the total number of available image resources and the image resources on the current page. The default number of entries per page is 10.
+     * - When you invoke an API operation by using Cloud Assistant CLI, request parameters of different data types must comply with format requirements. For more information, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
+     * - When you query images provided by Alibaba Cloud or shared images (ImageOwnerAlias is set to system or others), the request can bypass RAM authentication rules. For more information, see [Authentication rules](https://help.aliyun.com/document_detail/25497.html).
      *
      * @param request - DescribeImagesRequest
      * @returns DescribeImagesResponse
@@ -13122,7 +13108,7 @@ class Client extends openapi_core_1.default {
         return await this.describeInstanceAttachmentAttributesWithOptions(request, runtime);
     }
     /**
-     * This API is used to query the attribute information of a specified ECS instance.
+     * Queries the attribute information of a specified ECS instance.
      *
      * @param request - DescribeInstanceAttributeRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -13163,7 +13149,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeInstanceAttributeResponse({}));
     }
     /**
-     * This API is used to query the attribute information of a specified ECS instance.
+     * Queries the attribute information of a specified ECS instance.
      *
      * @param request - DescribeInstanceAttributeRequest
      * @returns DescribeInstanceAttributeResponse
@@ -13244,12 +13230,12 @@ class Client extends openapi_core_1.default {
         return await this.describeInstanceAutoRenewAttributeWithOptions(request, runtime);
     }
     /**
-     * Invoke the DescribeInstanceHistoryEvents API and specify parameters such as InstanceId and EventType to query system event information for a specified instance. By default, this operation queries historical system events that are in a non-active state.
+     * Queries system event information for a specified instance by calling the DescribeInstanceHistoryEvents operation. You can specify parameters such as InstanceId and EventType. By default, this operation queries historical system events in inactive states.
      *
      * @remarks
-     * - You can query completed historical system events from up to the last 30 days. There is no time limit for querying incomplete system events.
-     * - When neither the EventCycleStatus nor the InstanceEventCycleStatus parameter is specified, the query results include only system events in the Avoided (event avoided), Executed (event execution completed), Canceled (event canceled), or Failed (event execution failed) status by default.
-     * - By specifying the InstanceEventCycleStatus parameter, you can also query system events in the Scheduled (awaiting execution), Executing (execution in progress), or Inquiring (inquiry in progress) status.
+     * - You can query completed historical system events from the last 30 days. There is no time limit for querying uncompleted system events.
+     * - If neither EventCycleStatus nor InstanceEventCycleStatus is specified, the query results include only system events in the Avoided, Executed, Canceled, and Failed states by default.
+     * - By specifying the InstanceEventCycleStatus parameter, you can also query system events in the Scheduled, Executing, and Inquiring states.
      *
      * @param request - DescribeInstanceHistoryEventsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -13344,12 +13330,12 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeInstanceHistoryEventsResponse({}));
     }
     /**
-     * Invoke the DescribeInstanceHistoryEvents API and specify parameters such as InstanceId and EventType to query system event information for a specified instance. By default, this operation queries historical system events that are in a non-active state.
+     * Queries system event information for a specified instance by calling the DescribeInstanceHistoryEvents operation. You can specify parameters such as InstanceId and EventType. By default, this operation queries historical system events in inactive states.
      *
      * @remarks
-     * - You can query completed historical system events from up to the last 30 days. There is no time limit for querying incomplete system events.
-     * - When neither the EventCycleStatus nor the InstanceEventCycleStatus parameter is specified, the query results include only system events in the Avoided (event avoided), Executed (event execution completed), Canceled (event canceled), or Failed (event execution failed) status by default.
-     * - By specifying the InstanceEventCycleStatus parameter, you can also query system events in the Scheduled (awaiting execution), Executing (execution in progress), or Inquiring (inquiry in progress) status.
+     * - You can query completed historical system events from the last 30 days. There is no time limit for querying uncompleted system events.
+     * - If neither EventCycleStatus nor InstanceEventCycleStatus is specified, the query results include only system events in the Avoided, Executed, Canceled, and Failed states by default.
+     * - By specifying the InstanceEventCycleStatus parameter, you can also query system events in the Scheduled, Executing, and Inquiring states.
      *
      * @param request - DescribeInstanceHistoryEventsRequest
      * @returns DescribeInstanceHistoryEventsResponse
@@ -14161,14 +14147,14 @@ class Client extends openapi_core_1.default {
         return await this.describeInstanceVncUrlWithOptions(request, runtime);
     }
     /**
-     * This operation queries a list of instances based on specified conditions and returns detailed information about the instances.
+     * Queries a list of instances based on specified request conditions and returns the associated detailed information of the instances.
      *
      * @remarks
+     * ### Before you begin
+     * - When you invoke API operations by using Cloud Assistant CLI, make sure that request parameters of different data types are in the required formats. For more information, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
      * ### Usage notes
-     * - When you call this operation using Alibaba Cloud CLI, request parameter values of different data types must be in specific formats. For more information, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
-     * ### Recommendations
-     * - We recommend that you perform a dry run by setting the DryRun parameter to check parameter validity and authorization status.
-     * - To query the first page of results, set the `MaxResults` parameter to limit the number of entries returned. Use the `NextToken` value in the response to retrieve subsequent pages. For subsequent page queries, set the `NextToken` parameter to the value from the previous response and set `MaxResults` to limit the number of entries returned.
+     * - Send a dry run request by using the DryRun request parameter to check the validity of parameters and authorization.
+     * - When performing a paging query for the first page of results, set only `MaxResults` to limit the number of entries to return. The `NextToken` value in the response is used as the credential for querying subsequent pages. When performing a paging query for subsequent pages, set `NextToken` to the `NextToken` value obtained from the previous response and set `MaxResults` to limit the number of entries to return.
      *
      * @param request - DescribeInstancesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -14320,14 +14306,14 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeInstancesResponse({}));
     }
     /**
-     * This operation queries a list of instances based on specified conditions and returns detailed information about the instances.
+     * Queries a list of instances based on specified request conditions and returns the associated detailed information of the instances.
      *
      * @remarks
+     * ### Before you begin
+     * - When you invoke API operations by using Cloud Assistant CLI, make sure that request parameters of different data types are in the required formats. For more information, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
      * ### Usage notes
-     * - When you call this operation using Alibaba Cloud CLI, request parameter values of different data types must be in specific formats. For more information, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
-     * ### Recommendations
-     * - We recommend that you perform a dry run by setting the DryRun parameter to check parameter validity and authorization status.
-     * - To query the first page of results, set the `MaxResults` parameter to limit the number of entries returned. Use the `NextToken` value in the response to retrieve subsequent pages. For subsequent page queries, set the `NextToken` parameter to the value from the previous response and set `MaxResults` to limit the number of entries returned.
+     * - Send a dry run request by using the DryRun request parameter to check the validity of parameters and authorization.
+     * - When performing a paging query for the first page of results, set only `MaxResults` to limit the number of entries to return. The `NextToken` value in the response is used as the credential for querying subsequent pages. When performing a paging query for subsequent pages, set `NextToken` to the `NextToken` value obtained from the previous response and set `MaxResults` to limit the number of entries to return.
      *
      * @param request - DescribeInstancesRequest
      * @returns DescribeInstancesResponse
@@ -14431,22 +14417,22 @@ class Client extends openapi_core_1.default {
         return await this.describeInstancesFullStatusWithOptions(request, runtime);
     }
     /**
-     * $.parameters[11].schema.items.properties.Value.example
+     * Queries the execution results of one or more Cloud Assistant commands, which are the actual execution results on ECS instances.
      *
      * @remarks
-     * ## API Guide
-     * - After you execute a command, it does not necessarily mean that the command was successfully executed or produced the expected effect. You must use this API to check the actual execution results, and the actual output takes precedence.
-     * - You can query execution information from the last four weeks, with a maximum retention limit of 100,000 records.
-     * - You can obtain job results through [management event subscription for Cloud Assistant task status](https://help.aliyun.com/document_detail/2669130.html), which avoids frequent polling and improves efficiency.
-     * - When performing a paged query on the home page, you only need to set `MaxResults` to limit the number of returned entries. The `NextToken` in the return result serves as the credential for querying subsequent pages. When querying subsequent pages, set the `NextToken` parameter to the `NextToken` value obtained from the previous response as the query credential, and set `MaxResults` to limit the number of returned entries.
+     * ## Operation description
+     * - After you run a command, the command is not guaranteed to succeed or produce the expected results. Call this operation to view the actual execution results based on the actual output.
+     * - You can query execution information from the last 30 days. A maximum of 10,000 entries of execution information can be retained.
+     * - You can use [Cloud Assistant task status event subscription](https://help.aliyun.com/document_detail/2669130.html) to obtain task results through events, which avoids frequent polling and improves efficiency.
+     * - When paged query the first page, set only MaxResults to limit the number of entries to return. The NextToken value in the response serves as the token for querying subsequent pages. When paged query subsequent pages, set NextToken to the NextToken value obtained from the previous response and set MaxResults to limit the number of entries to return.
      * - Differences between `DescribeInvocations` and `DescribeInvocationResults`:
-     *   - When a single `RunCommand`/`InvokeCommand` invocation targets multiple instances:
-     *     - `DescribeInvocations` provides the execution status on each instance and an aggregation status across all instances.
-     *     - `DescribeInvocationResults` only provides individual execution statuses per instance, without aggregated multi-instance status.
-     *   - When a single `RunCommand`/`InvokeCommand` invocation targets one instance:
-     *     - There is little difference between `DescribeInvocations` and `DescribeInvocationResults`, and they can fully replace each other.
-     *   - When you need to view the execution history of scheduled (periodic) tasks or automatic startup tasks (`RepeatMode=Period, EveryReboot`), only `DescribeInvocationResults` can retrieve historical execution records (by specifying `IncludeHistory=true`). In contrast, `DescribeInvocations` only returns the latest task status.
-     *   - When you need to view the command content or parameters, only `DescribeInvocations` returns `CommandContent`.
+     *     - When a single `RunCommand`/`InvokeCommand` call specifies multiple instances:
+     *         - `DescribeInvocations` returns the execution status on each instance and the aggregated status across all instances.
+     *         - `DescribeInvocationResults` returns only the individual execution status on each instance, without the aggregated status across instances.
+     *     - When a single `RunCommand`/`InvokeCommand` call specifies one instance:
+     *         - `DescribeInvocations` and `DescribeInvocationResults` are largely interchangeable.
+     *     - When you want to view the execution history of scheduled (periodic) tasks or tasks that run at each system startup (`RepeatMode=Period, EveryReboot`), only `DescribeInvocationResults` can return historical execution records (you must specify `IncludeHistory=true`). `DescribeInvocations` returns only the latest task status.
+     *     - When you want to view the command content and parameters, only `DescribeInvocations` returns `CommandContent`.
      *
      * @param request - DescribeInvocationResultsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -14526,22 +14512,22 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeInvocationResultsResponse({}));
     }
     /**
-     * $.parameters[11].schema.items.properties.Value.example
+     * Queries the execution results of one or more Cloud Assistant commands, which are the actual execution results on ECS instances.
      *
      * @remarks
-     * ## API Guide
-     * - After you execute a command, it does not necessarily mean that the command was successfully executed or produced the expected effect. You must use this API to check the actual execution results, and the actual output takes precedence.
-     * - You can query execution information from the last four weeks, with a maximum retention limit of 100,000 records.
-     * - You can obtain job results through [management event subscription for Cloud Assistant task status](https://help.aliyun.com/document_detail/2669130.html), which avoids frequent polling and improves efficiency.
-     * - When performing a paged query on the home page, you only need to set `MaxResults` to limit the number of returned entries. The `NextToken` in the return result serves as the credential for querying subsequent pages. When querying subsequent pages, set the `NextToken` parameter to the `NextToken` value obtained from the previous response as the query credential, and set `MaxResults` to limit the number of returned entries.
+     * ## Operation description
+     * - After you run a command, the command is not guaranteed to succeed or produce the expected results. Call this operation to view the actual execution results based on the actual output.
+     * - You can query execution information from the last 30 days. A maximum of 10,000 entries of execution information can be retained.
+     * - You can use [Cloud Assistant task status event subscription](https://help.aliyun.com/document_detail/2669130.html) to obtain task results through events, which avoids frequent polling and improves efficiency.
+     * - When paged query the first page, set only MaxResults to limit the number of entries to return. The NextToken value in the response serves as the token for querying subsequent pages. When paged query subsequent pages, set NextToken to the NextToken value obtained from the previous response and set MaxResults to limit the number of entries to return.
      * - Differences between `DescribeInvocations` and `DescribeInvocationResults`:
-     *   - When a single `RunCommand`/`InvokeCommand` invocation targets multiple instances:
-     *     - `DescribeInvocations` provides the execution status on each instance and an aggregation status across all instances.
-     *     - `DescribeInvocationResults` only provides individual execution statuses per instance, without aggregated multi-instance status.
-     *   - When a single `RunCommand`/`InvokeCommand` invocation targets one instance:
-     *     - There is little difference between `DescribeInvocations` and `DescribeInvocationResults`, and they can fully replace each other.
-     *   - When you need to view the execution history of scheduled (periodic) tasks or automatic startup tasks (`RepeatMode=Period, EveryReboot`), only `DescribeInvocationResults` can retrieve historical execution records (by specifying `IncludeHistory=true`). In contrast, `DescribeInvocations` only returns the latest task status.
-     *   - When you need to view the command content or parameters, only `DescribeInvocations` returns `CommandContent`.
+     *     - When a single `RunCommand`/`InvokeCommand` call specifies multiple instances:
+     *         - `DescribeInvocations` returns the execution status on each instance and the aggregated status across all instances.
+     *         - `DescribeInvocationResults` returns only the individual execution status on each instance, without the aggregated status across instances.
+     *     - When a single `RunCommand`/`InvokeCommand` call specifies one instance:
+     *         - `DescribeInvocations` and `DescribeInvocationResults` are largely interchangeable.
+     *     - When you want to view the execution history of scheduled (periodic) tasks or tasks that run at each system startup (`RepeatMode=Period, EveryReboot`), only `DescribeInvocationResults` can return historical execution records (you must specify `IncludeHistory=true`). `DescribeInvocations` returns only the latest task status.
+     *     - When you want to view the command content and parameters, only `DescribeInvocations` returns `CommandContent`.
      *
      * @param request - DescribeInvocationResultsRequest
      * @returns DescribeInvocationResultsResponse
@@ -14551,21 +14537,21 @@ class Client extends openapi_core_1.default {
         return await this.describeInvocationResultsWithOptions(request, runtime);
     }
     /**
-     * Invoke the DescribeInvocations API to query the execution list and status of Cloud Assistant commands.
+     * Queries the execution list and status of Cloud Assistant commands.
      *
      * @remarks
-     * - After you execute a command, it does not necessarily mean that the command has run successfully or produced the expected effect. You must check the actual execution result through the API return value, and the actual output result takes precedence.
-     * - You can query execution information from the past four weeks, with a maximum retention limit of 100,000 records.
-     * - You can subscribe to [Cloud Assistant task status event notifications](https://help.aliyun.com/document_detail/2669130.html) to obtain task results via events, avoiding frequent polling and thereby improving efficiency.
-     * - When performing a paged query on the home page, you only need to set `MaxResults` to limit the number of returned entries. The `NextToken` in the return result serves as the credential for querying subsequent pages. When querying subsequent pages, set the `NextToken` parameter to the `NextToken` obtained from the previous response as the query credential, and also set `MaxResults` to limit the number of returned entries.
+     * - After you run a command, the command does not necessarily run successfully or produce the expected results. You must check the actual execution results based on the return values of this operation. The actual output takes precedence.
+     * - You can query execution information from the last 30 days. A maximum of 10,000 execution records are retained.
+     * - You can subscribe to [Cloud Assistant task status events](https://help.aliyun.com/document_detail/2669130.html) to obtain task results through events, which avoids frequent polling and improves efficiency.
+     * - When paged query the first page, set only MaxResults to limit the number of entries to return. The NextToken value in the response serves as the token for querying subsequent pages. When paged query subsequent pages, set NextToken to the NextToken value obtained from the previous response and set MaxResults to limit the number of entries to return.
      * - Differences between `DescribeInvocations` and `DescribeInvocationResults`:
-     *   - When a single `RunCommand`/`InvokeCommand` call specifies multiple instances:
-     *     - `DescribeInvocations` provides the execution status on each instance as well as the aggregated status across all instances.
-     *     - `DescribeInvocationResults` only provides the individual execution status per instance, without the aggregated multi-instance status.
-     *   - When a single `RunCommand`/`InvokeCommand` call specifies only one instance:
-     *     - There is little difference between `DescribeInvocations` and `DescribeInvocationResults`, and they can be used interchangeably.
-     *   - When you need to view the execution history of scheduled (periodic) tasks or tasks that automatically run at system startup (`RepeatMode=Period, EveryReboot`), only `DescribeInvocationResults` can retrieve historical execution records (by specifying `IncludeHistory=true`). In contrast, `DescribeInvocations` only returns the latest task status.
-     *   - When you need to view the command content and parameters, only `DescribeInvocations` returns `CommandContent`.
+     *     - When a single `RunCommand`/`InvokeCommand` call specifies multiple instances:
+     *         - `DescribeInvocations` returns the execution status on each instance and the aggregated status across all instances.
+     *         - `DescribeInvocationResults` returns only the individual execution status on each instance, without the aggregated status.
+     *     - When a single `RunCommand`/`InvokeCommand` call specifies one instance:
+     *         - `DescribeInvocations` and `DescribeInvocationResults` are largely interchangeable.
+     *     - To view the execution details of each run for scheduled (periodic) or boot-triggered tasks (`RepeatMode=Period, EveryReboot`), only `DescribeInvocationResults` can return historical execution records (with `IncludeHistory=true` specified). `DescribeInvocations` returns only the latest task status.
+     *     - To view the command content and parameters, only `DescribeInvocations` returns `CommandContent`.
      *
      * @param request - DescribeInvocationsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -14657,21 +14643,21 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeInvocationsResponse({}));
     }
     /**
-     * Invoke the DescribeInvocations API to query the execution list and status of Cloud Assistant commands.
+     * Queries the execution list and status of Cloud Assistant commands.
      *
      * @remarks
-     * - After you execute a command, it does not necessarily mean that the command has run successfully or produced the expected effect. You must check the actual execution result through the API return value, and the actual output result takes precedence.
-     * - You can query execution information from the past four weeks, with a maximum retention limit of 100,000 records.
-     * - You can subscribe to [Cloud Assistant task status event notifications](https://help.aliyun.com/document_detail/2669130.html) to obtain task results via events, avoiding frequent polling and thereby improving efficiency.
-     * - When performing a paged query on the home page, you only need to set `MaxResults` to limit the number of returned entries. The `NextToken` in the return result serves as the credential for querying subsequent pages. When querying subsequent pages, set the `NextToken` parameter to the `NextToken` obtained from the previous response as the query credential, and also set `MaxResults` to limit the number of returned entries.
+     * - After you run a command, the command does not necessarily run successfully or produce the expected results. You must check the actual execution results based on the return values of this operation. The actual output takes precedence.
+     * - You can query execution information from the last 30 days. A maximum of 10,000 execution records are retained.
+     * - You can subscribe to [Cloud Assistant task status events](https://help.aliyun.com/document_detail/2669130.html) to obtain task results through events, which avoids frequent polling and improves efficiency.
+     * - When paged query the first page, set only MaxResults to limit the number of entries to return. The NextToken value in the response serves as the token for querying subsequent pages. When paged query subsequent pages, set NextToken to the NextToken value obtained from the previous response and set MaxResults to limit the number of entries to return.
      * - Differences between `DescribeInvocations` and `DescribeInvocationResults`:
-     *   - When a single `RunCommand`/`InvokeCommand` call specifies multiple instances:
-     *     - `DescribeInvocations` provides the execution status on each instance as well as the aggregated status across all instances.
-     *     - `DescribeInvocationResults` only provides the individual execution status per instance, without the aggregated multi-instance status.
-     *   - When a single `RunCommand`/`InvokeCommand` call specifies only one instance:
-     *     - There is little difference between `DescribeInvocations` and `DescribeInvocationResults`, and they can be used interchangeably.
-     *   - When you need to view the execution history of scheduled (periodic) tasks or tasks that automatically run at system startup (`RepeatMode=Period, EveryReboot`), only `DescribeInvocationResults` can retrieve historical execution records (by specifying `IncludeHistory=true`). In contrast, `DescribeInvocations` only returns the latest task status.
-     *   - When you need to view the command content and parameters, only `DescribeInvocations` returns `CommandContent`.
+     *     - When a single `RunCommand`/`InvokeCommand` call specifies multiple instances:
+     *         - `DescribeInvocations` returns the execution status on each instance and the aggregated status across all instances.
+     *         - `DescribeInvocationResults` returns only the individual execution status on each instance, without the aggregated status.
+     *     - When a single `RunCommand`/`InvokeCommand` call specifies one instance:
+     *         - `DescribeInvocations` and `DescribeInvocationResults` are largely interchangeable.
+     *     - To view the execution details of each run for scheduled (periodic) or boot-triggered tasks (`RepeatMode=Period, EveryReboot`), only `DescribeInvocationResults` can return historical execution records (with `IncludeHistory=true` specified). `DescribeInvocations` returns only the latest task status.
+     *     - To view the command content and parameters, only `DescribeInvocations` returns `CommandContent`.
      *
      * @param request - DescribeInvocationsRequest
      * @returns DescribeInvocationsResponse
@@ -14750,7 +14736,7 @@ class Client extends openapi_core_1.default {
         return await this.describeKeyPairsWithOptions(request, runtime);
     }
     /**
-     * Query information about ECS instance launch template versions, such as the total number of launch templates, template name, and template version number.
+     * Queries information about launch template versions of ECS instances, such as the total number of launch templates, template names, and template version numbers.
      *
      * @param request - DescribeLaunchTemplateVersionsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -14818,7 +14804,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeLaunchTemplateVersionsResponse({}));
     }
     /**
-     * Query information about ECS instance launch template versions, such as the total number of launch templates, template name, and template version number.
+     * Queries information about launch template versions of ECS instances, such as the total number of launch templates, template names, and template version numbers.
      *
      * @param request - DescribeLaunchTemplateVersionsRequest
      * @returns DescribeLaunchTemplateVersionsResponse
@@ -16045,17 +16031,18 @@ class Client extends openapi_core_1.default {
         return await this.describePrefixListsWithOptions(request, runtime);
     }
     /**
-     * Use this operation to query the latest prices for specified resources by resource type, such as ECS instances, cloud disks, dedicated hosts, Elastic Assurance, and Capacity Reservation. The response includes promotional rules, prices, and discounts.
+     * Queries the latest prices of specified resources. You can query the latest prices of ECS instances, disks, dedicated hosts, elasticity assurance services, and capacity reservation services based on resource type. The response includes promotion rules, prices, and discounts.
      *
      * @remarks
-     * Parameter settings vary depending on the resource type you are querying:
-     * - If you set `ResourceType` to `instance`, you must also specify `InstanceType`. By default, this operation returns prices for the pay-as-you-go billing method (`PostPaid`). You can specify the `PriceUnit` parameter to query prices for different ECS billing cycles.
-     * - If you set `ResourceType` to `disk`, you must also specify `DataDisk.1.Category` and `DataDisk.1.Size`. When you query prices for `disk` resources, this operation returns only pay-as-you-go prices, so the `PriceUnit` parameter must be set to `Hour`.
-     * - If you set `ResourceType` to `diskperformance`, you must also specify `DataDisk.1.Category` and `DataDisk.1.ProvisionedIops`.
-     * - If you set `ResourceType` to `ddh`, you must also specify `DedicatedHostType`.
-     * - If you set `ResourceType` to `ElasticityAssurance`, you must also specify `InstanceType`.
-     * - If you set `ResourceType` to `CapacityReservation`, you must also specify `InstanceType`.
-     * - If you set `ResourceType` to `bandwidth`, this operation returns only pay-by-traffic (`PayByTraffic`) prices.
+     * The parameter settings vary based on the resource type:
+     *   - When `ResourceType=instance`, you must also specify `InstanceType`.
+     *     By default, the price of the pay-as-you-go (`PostPaid`) billing method (`ChargeType`) is queried. You can specify the `PriceUnit` parameter to query Elastic Compute Service (ECS) prices for different billing cycles.
+     *  - When `ResourceType=disk`, you must also specify `DataDisk.1.Category` and `DataDisk.1.Size`. When you query the price of `disk` resources, only the pay-as-you-go price of disks is returned. This means that the `PriceUnit` parameter can only be set to `Hour`.
+     * - When `ResourceType=diskperformance`, you must also specify `DataDisk.1.Category` and `DataDisk.1.ProvisionedIops`.
+     *  - When `ResourceType=ddh`, you must also specify `DedicatedHostType`.
+     *  - When `ResourceType=ElasticityAssurance`, you must also specify `InstanceType`.
+     *  - When `ResourceType=CapacityReservation`, you must also specify `InstanceType`.
+     * - When `ResourceType=bandwidth`, only the pay-by-traffic (`PayByTraffic`) price is returned.
      *
      * @param request - DescribePriceRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -16180,17 +16167,18 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribePriceResponse({}));
     }
     /**
-     * Use this operation to query the latest prices for specified resources by resource type, such as ECS instances, cloud disks, dedicated hosts, Elastic Assurance, and Capacity Reservation. The response includes promotional rules, prices, and discounts.
+     * Queries the latest prices of specified resources. You can query the latest prices of ECS instances, disks, dedicated hosts, elasticity assurance services, and capacity reservation services based on resource type. The response includes promotion rules, prices, and discounts.
      *
      * @remarks
-     * Parameter settings vary depending on the resource type you are querying:
-     * - If you set `ResourceType` to `instance`, you must also specify `InstanceType`. By default, this operation returns prices for the pay-as-you-go billing method (`PostPaid`). You can specify the `PriceUnit` parameter to query prices for different ECS billing cycles.
-     * - If you set `ResourceType` to `disk`, you must also specify `DataDisk.1.Category` and `DataDisk.1.Size`. When you query prices for `disk` resources, this operation returns only pay-as-you-go prices, so the `PriceUnit` parameter must be set to `Hour`.
-     * - If you set `ResourceType` to `diskperformance`, you must also specify `DataDisk.1.Category` and `DataDisk.1.ProvisionedIops`.
-     * - If you set `ResourceType` to `ddh`, you must also specify `DedicatedHostType`.
-     * - If you set `ResourceType` to `ElasticityAssurance`, you must also specify `InstanceType`.
-     * - If you set `ResourceType` to `CapacityReservation`, you must also specify `InstanceType`.
-     * - If you set `ResourceType` to `bandwidth`, this operation returns only pay-by-traffic (`PayByTraffic`) prices.
+     * The parameter settings vary based on the resource type:
+     *   - When `ResourceType=instance`, you must also specify `InstanceType`.
+     *     By default, the price of the pay-as-you-go (`PostPaid`) billing method (`ChargeType`) is queried. You can specify the `PriceUnit` parameter to query Elastic Compute Service (ECS) prices for different billing cycles.
+     *  - When `ResourceType=disk`, you must also specify `DataDisk.1.Category` and `DataDisk.1.Size`. When you query the price of `disk` resources, only the pay-as-you-go price of disks is returned. This means that the `PriceUnit` parameter can only be set to `Hour`.
+     * - When `ResourceType=diskperformance`, you must also specify `DataDisk.1.Category` and `DataDisk.1.ProvisionedIops`.
+     *  - When `ResourceType=ddh`, you must also specify `DedicatedHostType`.
+     *  - When `ResourceType=ElasticityAssurance`, you must also specify `InstanceType`.
+     *  - When `ResourceType=CapacityReservation`, you must also specify `InstanceType`.
+     * - When `ResourceType=bandwidth`, only the pay-by-traffic (`PayByTraffic`) price is returned.
      *
      * @param request - DescribePriceRequest
      * @returns DescribePriceResponse
@@ -16200,7 +16188,7 @@ class Client extends openapi_core_1.default {
         return await this.describePriceWithOptions(request, runtime);
     }
     /**
-     * Queries alternative instance types of an instance type. This operation is in internal preview. This operation lists all alternative instance types of an instance type that has been or is planed to be retired.
+     * (Beta) Queries one or more alternative instance types based on a specified instance type. For instance types that have been or will be retired, DescribeRecommendInstanceType lists all instance types that can serve as replacements.
      *
      * @param request - DescribeRecommendInstanceTypeRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -16286,7 +16274,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeRecommendInstanceTypeResponse({}));
     }
     /**
-     * Queries alternative instance types of an instance type. This operation is in internal preview. This operation lists all alternative instance types of an instance type that has been or is planed to be retired.
+     * (Beta) Queries one or more alternative instance types based on a specified instance type. For instance types that have been or will be retired, DescribeRecommendInstanceType lists all instance types that can serve as replacements.
      *
      * @param request - DescribeRecommendInstanceTypeRequest
      * @returns DescribeRecommendInstanceTypeResponse
@@ -16691,42 +16679,42 @@ class Client extends openapi_core_1.default {
         return await this.describeResourceByTagsWithOptions(request, runtime);
     }
     /**
-     * Queries available instance types or system disk categories in a specific zone before you change the instance type or system disk category of an Elastic Compute Service (ECS) instance.
+     * Queries the inventory of instance types or system disk types in a zone before you change the instance type or system disk type of an instance.
      *
      * @remarks
-     * Examples of common scenarios in which this operation is used:
-     * ### [](#-1)Example 1: Query the instance types to which you can change the instance type of an instance.
-     * Query the instance types to which you can change the instance type of the i-bp67acfmxazb4p\\*\\*\\*\\* instance and the inventory of the queried instance types in the zone in which the instance resides.
+     * The following examples describe common change scenarios:
+     * ### Example 1: Query instance types to which the current instance can be changed
+     * Query the instance types to which instance i-bp67acfmxazb4p**** can be changed, and the inventory of the corresponding instance types in the zone where the instance resides.
      * ```
      * http(s)://ecs.aliyuncs.com/?Action=DescribeResourcesModification
-     * &RegionId=cn-hangzhou
+     * &RegionId=ap-southeast-1
      * &ResourceId=i-bp67acfmxazb4p****
      * &DestinationResource=InstanceType
      * &OperationType=Upgrade
-     * &<Common request parameters>
+     * &Common request parameters
      * ```
-     * ### [](#-2)Example 2: Query the instance types to which you can change the instance type of an instance after a system disk category change.
-     * Query the instance types to which you can change the instance type of the i-bp67acfmxazb4p\\*\\*\\*\\* instance after a system disk category change and the inventory of the queried instance types in the zone in which the instance resides.
+     * ### Example 2: Query instance types available after changing the disk type of the current instance
+     * Query the instance types to which instance i-bp67acfmxazb4p**** can be changed after the disk type is changed, and the inventory of the corresponding instance types in the zone where the instance resides.
      * ```
      * http(s)://ecs.aliyuncs.com/?Action=DescribeResourcesModification
-     * &RegionId=cn-hangzhou
+     * &RegionId=ap-southeast-1
      * &ResourceId=i-bp67acfmxazb4p****
      * &DestinationResource=InstanceType
      * &OperationType=Upgrade
      * &Conditions.0=DiskCategory
-     * &<Common request parameters>
+     * &Common request parameters
      * ```
-     * ### [](#-3)Example 3: Query the system disk categories supported by the instance type to which you want to change the instance type of an instance.
-     * Query the system disk categories supported by the instance type to which you want to change the instance type of the i-bp67acfmxazb4p\\*\\*\\*\\* instance and the inventory of the disk categories in the zone in which the instance resides. In this example, the ecs.g7.large instance type is used. To change to the instance type, you must change the system disk category of the instance to a category supported by the instance type.
-     * > You can call this operation as described in Example 2 to query the instance types to which you can change the instance type of an instance.
+     * ### Example 3: Query the disk type required by the target instance type
+     * Query the disk type required by the target instance type (for example, ecs.g7.large). The current instance i-bp67acfmxazb4p**** must be changed to this disk type before it can be changed to the target instance type. Also query the inventory of the disk type in the zone where the instance resides.
+     * > The target instance type must be obtained by using Example 2.
      * ```
      * http(s)://ecs.aliyuncs.com/?Action=DescribeResourcesModification
-     * &RegionId=cn-hangzhou
+     * &RegionId=ap-southeast-1
      * &ResourceId=i-bp67acfmxazb4p****
      * &DestinationResource=SystemDisk
      * &OperationType=Upgrade
      * &InstanceType=ecs.g7.large
-     * &<Common request parameters>
+     * &Common request parameters
      * ```
      *
      * @param request - DescribeResourcesModificationRequest
@@ -16795,42 +16783,42 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeResourcesModificationResponse({}));
     }
     /**
-     * Queries available instance types or system disk categories in a specific zone before you change the instance type or system disk category of an Elastic Compute Service (ECS) instance.
+     * Queries the inventory of instance types or system disk types in a zone before you change the instance type or system disk type of an instance.
      *
      * @remarks
-     * Examples of common scenarios in which this operation is used:
-     * ### [](#-1)Example 1: Query the instance types to which you can change the instance type of an instance.
-     * Query the instance types to which you can change the instance type of the i-bp67acfmxazb4p\\*\\*\\*\\* instance and the inventory of the queried instance types in the zone in which the instance resides.
+     * The following examples describe common change scenarios:
+     * ### Example 1: Query instance types to which the current instance can be changed
+     * Query the instance types to which instance i-bp67acfmxazb4p**** can be changed, and the inventory of the corresponding instance types in the zone where the instance resides.
      * ```
      * http(s)://ecs.aliyuncs.com/?Action=DescribeResourcesModification
-     * &RegionId=cn-hangzhou
+     * &RegionId=ap-southeast-1
      * &ResourceId=i-bp67acfmxazb4p****
      * &DestinationResource=InstanceType
      * &OperationType=Upgrade
-     * &<Common request parameters>
+     * &Common request parameters
      * ```
-     * ### [](#-2)Example 2: Query the instance types to which you can change the instance type of an instance after a system disk category change.
-     * Query the instance types to which you can change the instance type of the i-bp67acfmxazb4p\\*\\*\\*\\* instance after a system disk category change and the inventory of the queried instance types in the zone in which the instance resides.
+     * ### Example 2: Query instance types available after changing the disk type of the current instance
+     * Query the instance types to which instance i-bp67acfmxazb4p**** can be changed after the disk type is changed, and the inventory of the corresponding instance types in the zone where the instance resides.
      * ```
      * http(s)://ecs.aliyuncs.com/?Action=DescribeResourcesModification
-     * &RegionId=cn-hangzhou
+     * &RegionId=ap-southeast-1
      * &ResourceId=i-bp67acfmxazb4p****
      * &DestinationResource=InstanceType
      * &OperationType=Upgrade
      * &Conditions.0=DiskCategory
-     * &<Common request parameters>
+     * &Common request parameters
      * ```
-     * ### [](#-3)Example 3: Query the system disk categories supported by the instance type to which you want to change the instance type of an instance.
-     * Query the system disk categories supported by the instance type to which you want to change the instance type of the i-bp67acfmxazb4p\\*\\*\\*\\* instance and the inventory of the disk categories in the zone in which the instance resides. In this example, the ecs.g7.large instance type is used. To change to the instance type, you must change the system disk category of the instance to a category supported by the instance type.
-     * > You can call this operation as described in Example 2 to query the instance types to which you can change the instance type of an instance.
+     * ### Example 3: Query the disk type required by the target instance type
+     * Query the disk type required by the target instance type (for example, ecs.g7.large). The current instance i-bp67acfmxazb4p**** must be changed to this disk type before it can be changed to the target instance type. Also query the inventory of the disk type in the zone where the instance resides.
+     * > The target instance type must be obtained by using Example 2.
      * ```
      * http(s)://ecs.aliyuncs.com/?Action=DescribeResourcesModification
-     * &RegionId=cn-hangzhou
+     * &RegionId=ap-southeast-1
      * &ResourceId=i-bp67acfmxazb4p****
      * &DestinationResource=SystemDisk
      * &OperationType=Upgrade
      * &InstanceType=ecs.g7.large
-     * &<Common request parameters>
+     * &Common request parameters
      * ```
      *
      * @param request - DescribeResourcesModificationRequest
@@ -17103,7 +17091,7 @@ class Client extends openapi_core_1.default {
         return await this.describeSavingsPlanPriceWithOptions(request, runtime);
     }
     /**
-     * Queries the details of a specified security group and the security group rules of the security group.
+     * Queries the details of a specified security group, including the list of security group rules.
      *
      * @param request - DescribeSecurityGroupAttributeRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -17162,7 +17150,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeSecurityGroupAttributeResponse({}));
     }
     /**
-     * Queries the details of a specified security group and the security group rules of the security group.
+     * Queries the details of a specified security group, including the list of security group rules.
      *
      * @param request - DescribeSecurityGroupAttributeRequest
      * @returns DescribeSecurityGroupAttributeResponse
@@ -17232,14 +17220,14 @@ class Client extends openapi_core_1.default {
         return await this.describeSecurityGroupReferencesWithOptions(request, runtime);
     }
     /**
-     * This API operation is used to query a list of basic information about security groups. You can query by different parameters such as region, security group ID, and security group type.
+     * Queries the basic information about security groups. You can filter results by region, security group ID, security group type, and other parameters through parameter query.
      *
      * @remarks
-     * - **Paged queries**: We recommend that you use the `MaxResults` and `NextToken` parameters for queries.
-     *   - When the response does not contain `NextToken`, the current page is the last page and no more pages are available.
-     *   - When querying the first page, you only need to set `MaxResults` to limit the number of entries returned. The `NextToken` in the response is used as the token for querying subsequent pages.
-     *   - When querying subsequent pages, set the `NextToken` parameter to the `NextToken` value obtained from the previous response as the query token, and set `MaxResults` to limit the number of entries returned.
-     * - When calling the API through Alibaba Cloud CLI, the values of request parameters of different data types must follow certain format requirements. For more information, see [CLI parameter format description](https://help.aliyun.com/document_detail/110340.html).
+     * - **Paging query**: Use `MaxResults` and `NextToken` for paging query.
+     *   - If `NextToken` is not returned, the current page is the last page.
+     *   - For the first page, set only `MaxResults` to limit the number of entries to return. The `NextToken` value in the response is used to query subsequent pages.
+     *   - For subsequent pages, set `NextToken` to the `NextToken` value returned in the previous response and set `MaxResults` to limit the number of entries to return.
+     * - When you invoke an API operation by using Cloud Assistant CLI, specify request parameters in the required format. For more information, see [Parameter format of CLI commands](https://help.aliyun.com/document_detail/110340.html).
      *
      * @param request - DescribeSecurityGroupsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -17328,14 +17316,14 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeSecurityGroupsResponse({}));
     }
     /**
-     * This API operation is used to query a list of basic information about security groups. You can query by different parameters such as region, security group ID, and security group type.
+     * Queries the basic information about security groups. You can filter results by region, security group ID, security group type, and other parameters through parameter query.
      *
      * @remarks
-     * - **Paged queries**: We recommend that you use the `MaxResults` and `NextToken` parameters for queries.
-     *   - When the response does not contain `NextToken`, the current page is the last page and no more pages are available.
-     *   - When querying the first page, you only need to set `MaxResults` to limit the number of entries returned. The `NextToken` in the response is used as the token for querying subsequent pages.
-     *   - When querying subsequent pages, set the `NextToken` parameter to the `NextToken` value obtained from the previous response as the query token, and set `MaxResults` to limit the number of entries returned.
-     * - When calling the API through Alibaba Cloud CLI, the values of request parameters of different data types must follow certain format requirements. For more information, see [CLI parameter format description](https://help.aliyun.com/document_detail/110340.html).
+     * - **Paging query**: Use `MaxResults` and `NextToken` for paging query.
+     *   - If `NextToken` is not returned, the current page is the last page.
+     *   - For the first page, set only `MaxResults` to limit the number of entries to return. The `NextToken` value in the response is used to query subsequent pages.
+     *   - For subsequent pages, set `NextToken` to the `NextToken` value returned in the previous response and set `MaxResults` to limit the number of entries to return.
+     * - When you invoke an API operation by using Cloud Assistant CLI, specify request parameters in the required format. For more information, see [Parameter format of CLI commands](https://help.aliyun.com/document_detail/110340.html).
      *
      * @param request - DescribeSecurityGroupsRequest
      * @returns DescribeSecurityGroupsResponse
@@ -17345,13 +17333,13 @@ class Client extends openapi_core_1.default {
         return await this.describeSecurityGroupsWithOptions(request, runtime);
     }
     /**
-     * Queries the files sent by Cloud Assistant and their status.
+     * Queries the list and status of files sent by Cloud Assistant by calling DescribeSendFileResults.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * - When you send a file, the file may fail to be sent to specific Elastic Compute Service (ECS) instances. You can call this operation to check the file sending results.
-     * - You can call this operation to query the file sending records within the last six weeks.
-     * - During a paged query, when you call the DescribeSendFileResults operation to retrieve the first page of results, set `MaxResults` to specify the maximum number of entries to return in the call. The return value of `NextToken` is a pagination token that can be used in the next call to retrieve a new page of results. When you call the DescribeSendFileResults operation to retrieve a new page of results, set `NextToken` to the `NextToken` value returned in the previous call and set `MaxResults` to specify the maximum number of entries to return in this call.
+     * ## Operation description:
+     * - After you send a file, the file is not necessarily sent. You must check the actual sending result based on the return value of this operation.
+     * - You can query execution information from the last 30 days. A maximum of 10,000 entries of execution information can be retained.
+     * - When paged query the first page, set only MaxResults to limit the number of entries to return. The NextToken value returned in the result serves as the token for querying subsequent pages. When paged query subsequent pages, set NextToken to the value obtained from the previous response and set MaxResults to limit the number of entries to return.
      *
      * @param request - DescribeSendFileResultsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -17425,13 +17413,13 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeSendFileResultsResponse({}));
     }
     /**
-     * Queries the files sent by Cloud Assistant and their status.
+     * Queries the list and status of files sent by Cloud Assistant by calling DescribeSendFileResults.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * - When you send a file, the file may fail to be sent to specific Elastic Compute Service (ECS) instances. You can call this operation to check the file sending results.
-     * - You can call this operation to query the file sending records within the last six weeks.
-     * - During a paged query, when you call the DescribeSendFileResults operation to retrieve the first page of results, set `MaxResults` to specify the maximum number of entries to return in the call. The return value of `NextToken` is a pagination token that can be used in the next call to retrieve a new page of results. When you call the DescribeSendFileResults operation to retrieve a new page of results, set `NextToken` to the `NextToken` value returned in the previous call and set `MaxResults` to specify the maximum number of entries to return in this call.
+     * ## Operation description:
+     * - After you send a file, the file is not necessarily sent. You must check the actual sending result based on the return value of this operation.
+     * - You can query execution information from the last 30 days. A maximum of 10,000 entries of execution information can be retained.
+     * - When paged query the first page, set only MaxResults to limit the number of entries to return. The NextToken value returned in the result serves as the token for querying subsequent pages. When paged query subsequent pages, set NextToken to the value obtained from the previous response and set MaxResults to limit the number of entries to return.
      *
      * @param request - DescribeSendFileResultsRequest
      * @returns DescribeSendFileResultsResponse
@@ -17741,47 +17729,39 @@ class Client extends openapi_core_1.default {
         return await this.describeSnapshotPackageWithOptions(request, runtime);
     }
     /**
-     * Queries details about a cloud disk\\"s snapshots, including their status, the time remaining until completion, and the retention days for automatic snapshots.
+     * Queries the snapshot list of a disk, including snapshot status, remaining time for a snapshot being created, and automatic snapshot retention days.
      *
      * @remarks
-     * The `InstanceId`, `DiskId`, and `SnapshotIds` request parameters are optional and can be used to create a filter. The parameters are combined with a logical AND.
-     * When you call an API using Alibaba Cloud CLI, the values for request parameters of different data types must be in specific formats. For more information, see [CLI parameter format description](https://help.aliyun.com/document_detail/110340.html).
+     * InstanceId, DiskId, and SnapshotIds are not required request parameters, but you can use them to build filter logic. These parameters are evaluated by using a logical AND.
+     * When you invoke an API operation by using Cloud Assistant CLI, specify request parameter values in the required formats based on their data types. For details, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
      * Request examples:
      * <details>
-     * <summary>
-     * Query the snapshots of all cloud disks attached to an ECS instance in the China (Hangzhou) region
-     * </summary>
+     * <summary>Query the snapshot list of all disks attached to an ECS instance in the China (Hangzhou) region</summary>
      * ```
-     * RegionId:  cn-hangzhou,   // The ID of the region.
-     * InstanceId:  i-bp1fh7by6d9mw7zr****   // The ID of the instance to query.
+     * RegionId:  cn-hangzhou,   // Set the region to China (Hangzhou).
+     * InstanceId:  i-bp1fh7by6d9mw7zr****   // Set the instance ID to query.
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query the snapshots of a cloud disk in the China (Hangzhou) region
-     * </summary>
+     * <summary>Query the snapshot information of a specific disk in the China (Hangzhou) region</summary>
      * ```
-     * RegionId:  cn-hangzhou,   // The ID of the region.
-     * DiskId:   d-bp10e7ej8z743dmu****   // The ID of the cloud disk to query.
+     * RegionId:  cn-hangzhou,   // Set the region to China (Hangzhou).
+     * DiskId:   d-bp10e7ej8z743dmu****   // Set the disk ID to query.
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query two snapshots in the China (Hangzhou) region by snapshot ID
-     * </summary>
+     * <summary>Query the information of two snapshots in the China (Hangzhou) region by snapshot ID</summary>
      * ```
-     * RegionId:  cn-hangzhou,   // The ID of the region.
-     * SnapshotIds:   ["d-bp10e7ej8z743dmu****", "s-bp19vd1lorzgzt2s****"]   // The snapshot IDs to query.
+     * RegionId:  cn-hangzhou,   // Set the region to China (Hangzhou).
+     * SnapshotIds:   ["d-bp10e7ej8z743dmu****", "s-bp19vd1lorzgzt2s****"]   // Set the array of snapshot IDs to query.
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query snapshots created after a specific time in the China (Hangzhou) region
-     * </summary>
+     * <summary>Query the snapshot information created after a specific point in time in the China (Hangzhou) region</summary>
      * ```
-     * RegionId:  cn-hangzhou,   // The ID of the region.
-     * Filter.1.Key:   CreationStartTime,   // Filters by the creation start time.
-     * Filter.1.Value:   2024-11-27T00:00Z
+     * RegionId:  cn-hangzhou,   // Set the region to China (Hangzhou).
+     * Filter.1.Key:   CreationStartTime,   // Set the filter key for the creation start time.
+     * Filter.1.Value:   2024-11-27T00:00Z.
      * ```
      * </details>
      *
@@ -17884,47 +17864,39 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeSnapshotsResponse({}));
     }
     /**
-     * Queries details about a cloud disk\\"s snapshots, including their status, the time remaining until completion, and the retention days for automatic snapshots.
+     * Queries the snapshot list of a disk, including snapshot status, remaining time for a snapshot being created, and automatic snapshot retention days.
      *
      * @remarks
-     * The `InstanceId`, `DiskId`, and `SnapshotIds` request parameters are optional and can be used to create a filter. The parameters are combined with a logical AND.
-     * When you call an API using Alibaba Cloud CLI, the values for request parameters of different data types must be in specific formats. For more information, see [CLI parameter format description](https://help.aliyun.com/document_detail/110340.html).
+     * InstanceId, DiskId, and SnapshotIds are not required request parameters, but you can use them to build filter logic. These parameters are evaluated by using a logical AND.
+     * When you invoke an API operation by using Cloud Assistant CLI, specify request parameter values in the required formats based on their data types. For details, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
      * Request examples:
      * <details>
-     * <summary>
-     * Query the snapshots of all cloud disks attached to an ECS instance in the China (Hangzhou) region
-     * </summary>
+     * <summary>Query the snapshot list of all disks attached to an ECS instance in the China (Hangzhou) region</summary>
      * ```
-     * RegionId:  cn-hangzhou,   // The ID of the region.
-     * InstanceId:  i-bp1fh7by6d9mw7zr****   // The ID of the instance to query.
+     * RegionId:  cn-hangzhou,   // Set the region to China (Hangzhou).
+     * InstanceId:  i-bp1fh7by6d9mw7zr****   // Set the instance ID to query.
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query the snapshots of a cloud disk in the China (Hangzhou) region
-     * </summary>
+     * <summary>Query the snapshot information of a specific disk in the China (Hangzhou) region</summary>
      * ```
-     * RegionId:  cn-hangzhou,   // The ID of the region.
-     * DiskId:   d-bp10e7ej8z743dmu****   // The ID of the cloud disk to query.
+     * RegionId:  cn-hangzhou,   // Set the region to China (Hangzhou).
+     * DiskId:   d-bp10e7ej8z743dmu****   // Set the disk ID to query.
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query two snapshots in the China (Hangzhou) region by snapshot ID
-     * </summary>
+     * <summary>Query the information of two snapshots in the China (Hangzhou) region by snapshot ID</summary>
      * ```
-     * RegionId:  cn-hangzhou,   // The ID of the region.
-     * SnapshotIds:   ["d-bp10e7ej8z743dmu****", "s-bp19vd1lorzgzt2s****"]   // The snapshot IDs to query.
+     * RegionId:  cn-hangzhou,   // Set the region to China (Hangzhou).
+     * SnapshotIds:   ["d-bp10e7ej8z743dmu****", "s-bp19vd1lorzgzt2s****"]   // Set the array of snapshot IDs to query.
      * ```
      * </details>
      * <details>
-     * <summary>
-     * Query snapshots created after a specific time in the China (Hangzhou) region
-     * </summary>
+     * <summary>Query the snapshot information created after a specific point in time in the China (Hangzhou) region</summary>
      * ```
-     * RegionId:  cn-hangzhou,   // The ID of the region.
-     * Filter.1.Key:   CreationStartTime,   // Filters by the creation start time.
-     * Filter.1.Value:   2024-11-27T00:00Z
+     * RegionId:  cn-hangzhou,   // Set the region to China (Hangzhou).
+     * Filter.1.Key:   CreationStartTime,   // Set the filter key for the creation start time.
+     * Filter.1.Value:   2024-11-27T00:00Z.
      * ```
      * </details>
      *
@@ -18092,11 +18064,11 @@ class Client extends openapi_core_1.default {
         return await this.describeSpotAdviceWithOptions(request, runtime);
     }
     /**
-     * Queries the historical prices of spot instances within up to the previous 30 days. You can set the maximum price of a spot instance based on the historical prices.
+     * Queries the historical prices of spot instances. You can query price data from the last 30 days. The historical price data helps you set a reasonable maximum price for a spot instance.
      *
      * @remarks
-     * - This operation is applicable only to I/O optimized spot instances.
-     * - The data returned by the interface may be paginated. If the returned data contains the `NextOffset` parameter, you can set the `Offset` parameter in the request to the value of the `NextOffset` parameter for subsequent data query.
+     * - Only I/O optimized spot instances are supported.
+     * - The data returned by this operation may be paginated. If the response contains the `NextOffset` parameter, set the `Offset` request parameter to the value of `NextOffset` to query the next page of data.
      *
      * @param request - DescribeSpotPriceHistoryRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -18167,11 +18139,11 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeSpotPriceHistoryResponse({}));
     }
     /**
-     * Queries the historical prices of spot instances within up to the previous 30 days. You can set the maximum price of a spot instance based on the historical prices.
+     * Queries the historical prices of spot instances. You can query price data from the last 30 days. The historical price data helps you set a reasonable maximum price for a spot instance.
      *
      * @remarks
-     * - This operation is applicable only to I/O optimized spot instances.
-     * - The data returned by the interface may be paginated. If the returned data contains the `NextOffset` parameter, you can set the `Offset` parameter in the request to the value of the `NextOffset` parameter for subsequent data query.
+     * - Only I/O optimized spot instances are supported.
+     * - The data returned by this operation may be paginated. If the response contains the `NextOffset` parameter, set the `Offset` request parameter to the value of `NextOffset` to query the next page of data.
      *
      * @param request - DescribeSpotPriceHistoryRequest
      * @returns DescribeSpotPriceHistoryResponse
@@ -18603,10 +18575,10 @@ class Client extends openapi_core_1.default {
         return await this.describeTasksWithOptions(request, runtime);
     }
     /**
-     * Queries the session records of Elastic Compute Service (ECS) Session Manager.
+     * Queries the session history of Session Manager.
      *
      * @remarks
-     * You can query the session records of Session Manager that were generated in the last four weeks.
+     * You can query Session Manager session records created within the last 30 days. A maximum of 1,000 successful records are retained.
      *
      * @param request - DescribeTerminalSessionsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -18659,10 +18631,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeTerminalSessionsResponse({}));
     }
     /**
-     * Queries the session records of Elastic Compute Service (ECS) Session Manager.
+     * Queries the session history of Session Manager.
      *
      * @remarks
-     * You can query the session records of Session Manager that were generated in the last four weeks.
+     * You can query Session Manager session records created within the last 30 days. A maximum of 1,000 successful records are retained.
      *
      * @param request - DescribeTerminalSessionsRequest
      * @returns DescribeTerminalSessionsResponse
@@ -19200,11 +19172,10 @@ class Client extends openapi_core_1.default {
         return await this.describeVscsWithOptions(request, runtime);
     }
     /**
-     * Queries Alibaba Cloud regions. You can specify parameters, such as InstanceChargeType and ResourceType, in the request.
+     * Queries the list of active zones based on parameters such as region ID and billing method.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * When you call this operation, only a list of zones and some resource information of each zone are returned. If you want to query instance types and disk categories that are available for purchase in a specific zone, we recommend that you call the [DescribeAvailableResource](https://help.aliyun.com/document_detail/66186.html) operation.
+     * DescribeZones only queries the list of zones provided by Alibaba Cloud and returns limited inventory information. To query the instance types and disk categories available for purchase in a specific zone, use [DescribeAvailableResource](https://help.aliyun.com/document_detail/66186.html).
      *
      * @param request - DescribeZonesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -19257,11 +19228,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeZonesResponse({}));
     }
     /**
-     * Queries Alibaba Cloud regions. You can specify parameters, such as InstanceChargeType and ResourceType, in the request.
+     * Queries the list of active zones based on parameters such as region ID and billing method.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * When you call this operation, only a list of zones and some resource information of each zone are returned. If you want to query instance types and disk categories that are available for purchase in a specific zone, we recommend that you call the [DescribeAvailableResource](https://help.aliyun.com/document_detail/66186.html) operation.
+     * DescribeZones only queries the list of zones provided by Alibaba Cloud and returns limited inventory information. To query the instance types and disk categories available for purchase in a specific zone, use [DescribeAvailableResource](https://help.aliyun.com/document_detail/66186.html).
      *
      * @param request - DescribeZonesRequest
      * @returns DescribeZonesResponse
@@ -20262,7 +20232,7 @@ class Client extends openapi_core_1.default {
         return await this.exportSnapshotWithOptions(request, runtime);
     }
     /**
-     * Retrieves the system command line output of an instance. The data is returned in Base64 encoding.
+     * Retrieves the system command-line output of an instance. The data is returned in Base64-encoded format.
      *
      * @remarks
      * - Elastic Compute Service (ECS) is a virtualization-based cloud server that cannot be connected to display devices or manually screenshotted. However, Alibaba Cloud caches the system command line output from the last time an instance was started, restarted, or shut down. You can invoke GetInstanceConsoleOutput to retrieve this output.
@@ -20317,7 +20287,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.GetInstanceConsoleOutputResponse({}));
     }
     /**
-     * Retrieves the system command line output of an instance. The data is returned in Base64 encoding.
+     * Retrieves the system command-line output of an instance. The data is returned in Base64-encoded format.
      *
      * @remarks
      * - Elastic Compute Service (ECS) is a virtualization-based cloud server that cannot be connected to display devices or manually screenshotted. However, Alibaba Cloud caches the system command line output from the last time an instance was started, restarted, or shut down. You can invoke GetInstanceConsoleOutput to retrieve this output.
@@ -20332,13 +20302,13 @@ class Client extends openapi_core_1.default {
         return await this.getInstanceConsoleOutputWithOptions(request, runtime);
     }
     /**
-     * Calls GetInstanceScreenshot to obtain the screenshot information of an instance.
+     * Calls GetInstanceScreenshot to retrieve the screenshot information of an instance.
      *
      * @remarks
-     * After Elastic Compute Service (ECS) returns the instance screenshot as a Base64-encoded JPG image, you must decode it yourself. You can call this operation when troubleshooting faults. Note the following items:
+     * After Elastic Compute Service (ECS) returns the instance screenshot in Base64-encoded JPG image format, you must decode it yourself. You can call this operation when troubleshooting faults. Note the following items:
      * - The instance must be in the Running state.
-     * - You cannot obtain screenshot information for [retired instance types](https://help.aliyun.com/document_detail/55263.html).
-     * - If you call this operation multiple times on the same instance, the interval between calls must be at least 10 seconds. Otherwise, the `Throttling` error code is returned.
+     * - Screenshots cannot be retrieved for [retired instance types](https://help.aliyun.com/document_detail/55263.html).
+     * - If you call this operation multiple times on the same instance, the interval between calls must be at least 10 seconds. Otherwise, the Throttling error code is returned.
      *
      * @param request - GetInstanceScreenshotRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -20388,13 +20358,13 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.GetInstanceScreenshotResponse({}));
     }
     /**
-     * Calls GetInstanceScreenshot to obtain the screenshot information of an instance.
+     * Calls GetInstanceScreenshot to retrieve the screenshot information of an instance.
      *
      * @remarks
-     * After Elastic Compute Service (ECS) returns the instance screenshot as a Base64-encoded JPG image, you must decode it yourself. You can call this operation when troubleshooting faults. Note the following items:
+     * After Elastic Compute Service (ECS) returns the instance screenshot in Base64-encoded JPG image format, you must decode it yourself. You can call this operation when troubleshooting faults. Note the following items:
      * - The instance must be in the Running state.
-     * - You cannot obtain screenshot information for [retired instance types](https://help.aliyun.com/document_detail/55263.html).
-     * - If you call this operation multiple times on the same instance, the interval between calls must be at least 10 seconds. Otherwise, the `Throttling` error code is returned.
+     * - Screenshots cannot be retrieved for [retired instance types](https://help.aliyun.com/document_detail/55263.html).
+     * - If you call this operation multiple times on the same instance, the interval between calls must be at least 10 seconds. Otherwise, the Throttling error code is returned.
      *
      * @param request - GetInstanceScreenshotRequest
      * @returns GetInstanceScreenshotResponse
@@ -23195,7 +23165,7 @@ class Client extends openapi_core_1.default {
         return await this.modifyHaVipAttributeWithOptions(request, runtime);
     }
     /**
-     * Modifies the description of an HPC cluster by calling ModifyHpcClusterAttribute.
+     * Modifies the description of an HPC cluster.
      *
      * @param request - ModifyHpcClusterAttributeRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -23251,7 +23221,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyHpcClusterAttributeResponse({}));
     }
     /**
-     * Modifies the description of an HPC cluster by calling ModifyHpcClusterAttribute.
+     * Modifies the description of an HPC cluster.
      *
      * @param request - ModifyHpcClusterAttributeRequest
      * @returns ModifyHpcClusterAttributeResponse
@@ -23578,10 +23548,10 @@ class Client extends openapi_core_1.default {
         return await this.modifyInstanceAttachmentAttributesWithOptions(request, runtime);
     }
     /**
-     * This API modifies attributes of an ECS instance, such as the password, instance name, hostname, security group, MTU, and user data.
+     * Modifies some properties of an ECS instance, including the password, instance name, hostname, security group membership, MTU, and instance user data.
      *
      * @remarks
-     * This API call is not supported for instances protected by a resource security lock. For more information, see [How resource security locks affect API calls](https://help.aliyun.com/document_detail/25695.html).
+     * Instances that are locked for security reasons do not support this operation. For more information, see [Impact of resource security locks on API calls](https://help.aliyun.com/document_detail/25695.html).
      *
      * @param request - ModifyInstanceAttributeRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -23667,10 +23637,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyInstanceAttributeResponse({}));
     }
     /**
-     * This API modifies attributes of an ECS instance, such as the password, instance name, hostname, security group, MTU, and user data.
+     * Modifies some properties of an ECS instance, including the password, instance name, hostname, security group membership, MTU, and instance user data.
      *
      * @remarks
-     * This API call is not supported for instances protected by a resource security lock. For more information, see [How resource security locks affect API calls](https://help.aliyun.com/document_detail/25695.html).
+     * Instances that are locked for security reasons do not support this operation. For more information, see [Impact of resource security locks on API calls](https://help.aliyun.com/document_detail/25695.html).
      *
      * @param request - ModifyInstanceAttributeRequest
      * @returns ModifyInstanceAttributeResponse
@@ -24302,15 +24272,14 @@ class Client extends openapi_core_1.default {
      * Modifies the bandwidth configuration of an ECS instance, allocates a public IP address, or converts the network billing method. Both upgrades and downgrades are supported.
      *
      * @remarks
-     * -  When modifying the bandwidth configuration of a subscription (PrePaid) instance, a public IP address is automatically allocated when the maximum outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value.
-     * -  When modifying the bandwidth configuration of a pay-as-you-go (PostPaid) instance, a public IP address is not automatically allocated when the maximum outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value. You need to set the `AllocatePublicIp` parameter to `true` to allocate a public IP address.
-     * -  For classic network (Classic) instances, when the maximum outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value, the instance must be in the Stopped state.
-     * > Within a single region, there is a limit on the total peak pay-by-bandwidth public bandwidth for a single Alibaba Cloud account. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
+     * -  When you modify the bandwidth configuration of a subscription (PrePaid) instance, a public IP address is automatically allocated if the outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value.
+     * -  When you modify the bandwidth configuration of a pay-as-you-go (PostPaid) instance, a public IP address is not automatically allocated if the outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value. You need to set the `AllocatePublicIp` parameter to `true` to allocate a public IP address.
+     * > In a single region, the total peak pay-by-bandwidth public bandwidth of a single Alibaba Cloud account is subject to a limit. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
      *
      * - Fees:
      *
-     *   - After upgrading bandwidth, the payment is automatically deducted by default. Make sure your payment method has sufficient balance. Otherwise, an abnormal order will be generated and can only be voided. If your account balance is insufficient, you can set the AutoPay parameter to false. In this case, an unpaid order is generated, and you can log on to the ECS console to pay for the order.
-     *   - After downgrading bandwidth, the price difference is refunded through the original payment method. Coupons that have already been used are not refunded.
+     *   - After the bandwidth is upgraded, the payment is automatically deducted by default. Make sure that your payment method has sufficient balance. Otherwise, an abnormal order is generated, and you can only cancel the order. If your account balance is insufficient, you can set the AutoPay parameter to false. In this case, a normal unpaid order is generated. You can log on to the ECS console to pay for the order.
+     *   - After the bandwidth is downgraded, the price difference is refunded to the original payment method. Vouchers that have been used are not refundable.
      *
      * @param request - ModifyInstanceNetworkSpecRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -24381,15 +24350,14 @@ class Client extends openapi_core_1.default {
      * Modifies the bandwidth configuration of an ECS instance, allocates a public IP address, or converts the network billing method. Both upgrades and downgrades are supported.
      *
      * @remarks
-     * -  When modifying the bandwidth configuration of a subscription (PrePaid) instance, a public IP address is automatically allocated when the maximum outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value.
-     * -  When modifying the bandwidth configuration of a pay-as-you-go (PostPaid) instance, a public IP address is not automatically allocated when the maximum outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value. You need to set the `AllocatePublicIp` parameter to `true` to allocate a public IP address.
-     * -  For classic network (Classic) instances, when the maximum outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value, the instance must be in the Stopped state.
-     * > Within a single region, there is a limit on the total peak pay-by-bandwidth public bandwidth for a single Alibaba Cloud account. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
+     * -  When you modify the bandwidth configuration of a subscription (PrePaid) instance, a public IP address is automatically allocated if the outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value.
+     * -  When you modify the bandwidth configuration of a pay-as-you-go (PostPaid) instance, a public IP address is not automatically allocated if the outbound public bandwidth (InternetMaxBandwidthOut) is upgraded from 0 Mbit/s to a non-zero value. You need to set the `AllocatePublicIp` parameter to `true` to allocate a public IP address.
+     * > In a single region, the total peak pay-by-bandwidth public bandwidth of a single Alibaba Cloud account is subject to a limit. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
      *
      * - Fees:
      *
-     *   - After upgrading bandwidth, the payment is automatically deducted by default. Make sure your payment method has sufficient balance. Otherwise, an abnormal order will be generated and can only be voided. If your account balance is insufficient, you can set the AutoPay parameter to false. In this case, an unpaid order is generated, and you can log on to the ECS console to pay for the order.
-     *   - After downgrading bandwidth, the price difference is refunded through the original payment method. Coupons that have already been used are not refunded.
+     *   - After the bandwidth is upgraded, the payment is automatically deducted by default. Make sure that your payment method has sufficient balance. Otherwise, an abnormal order is generated, and you can only cancel the order. If your account balance is insufficient, you can set the AutoPay parameter to false. In this case, a normal unpaid order is generated. You can log on to the ECS console to pay for the order.
+     *   - After the bandwidth is downgraded, the price difference is refunded to the original payment method. Vouchers that have been used are not refundable.
      *
      * @param request - ModifyInstanceNetworkSpecRequest
      * @returns ModifyInstanceNetworkSpecResponse
@@ -24403,18 +24371,18 @@ class Client extends openapi_core_1.default {
      *
      * @remarks
      * <props="china">.
-     * **Before you call this operation, make sure that you fully understand the billing methods and [pricing](https://www.aliyun.com/price/product#/ecs/detail) of ECS.**.
+     * **Before you use this operation, make sure that you fully understand the billing methods and [pricing](https://www.aliyun.com/price/product#/ecs/detail) of ECS.**.
      * .
      * <props="intl">.
-     * **Before you call this operation, make sure that you fully understand the billing methods and [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS.**.
+     * **Before you use this operation, make sure that you fully understand the billing methods and [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS.**.
      * .
      * Before you [change the instance type of a pay-as-you-go instance](https://help.aliyun.com/document_detail/60051.html), you can call [DescribeResourcesModification](https://help.aliyun.com/document_detail/66187.html) to query the instance types to which the current instance can be changed.
      * **Before you begin**.
      * - Your account must not have overdue payments.
-     * - Each call can modify only one configuration. You can change only the instance type or adjust only the public bandwidth in a single request.
+     * - Each call can modify only one configuration at a time. You can modify only the instance type or adjust only the public bandwidth in a single request.
      * - The instance status must be **Running** (`Running`) or **Stopped** (`Stopped`) before you can adjust the public bandwidth. The change takes effect immediately.
-     * - The instance status must be **Stopped** (`Stopped`) before you can change the instance type. After the change, you must [start the instance](https://help.aliyun.com/document_detail/25441.html) for the change to take effect.
-     * > The total peak public bandwidth billed on a pay-by-bandwidth basis in a single region for a single Alibaba Cloud account is subject to limits. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
+     * - The instance status must be **Stopped** (`Stopped`) before you can modify the instance type. After the modification, you must [start the instance](https://help.aliyun.com/document_detail/25441.html) for the change to take effect.
+     * > In a single region, the total peak pay-by-bandwidth public bandwidth for a single Alibaba Cloud account is limited. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
      *
      * @param request - ModifyInstanceSpecRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -24492,18 +24460,18 @@ class Client extends openapi_core_1.default {
      *
      * @remarks
      * <props="china">.
-     * **Before you call this operation, make sure that you fully understand the billing methods and [pricing](https://www.aliyun.com/price/product#/ecs/detail) of ECS.**.
+     * **Before you use this operation, make sure that you fully understand the billing methods and [pricing](https://www.aliyun.com/price/product#/ecs/detail) of ECS.**.
      * .
      * <props="intl">.
-     * **Before you call this operation, make sure that you fully understand the billing methods and [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS.**.
+     * **Before you use this operation, make sure that you fully understand the billing methods and [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS.**.
      * .
      * Before you [change the instance type of a pay-as-you-go instance](https://help.aliyun.com/document_detail/60051.html), you can call [DescribeResourcesModification](https://help.aliyun.com/document_detail/66187.html) to query the instance types to which the current instance can be changed.
      * **Before you begin**.
      * - Your account must not have overdue payments.
-     * - Each call can modify only one configuration. You can change only the instance type or adjust only the public bandwidth in a single request.
+     * - Each call can modify only one configuration at a time. You can modify only the instance type or adjust only the public bandwidth in a single request.
      * - The instance status must be **Running** (`Running`) or **Stopped** (`Stopped`) before you can adjust the public bandwidth. The change takes effect immediately.
-     * - The instance status must be **Stopped** (`Stopped`) before you can change the instance type. After the change, you must [start the instance](https://help.aliyun.com/document_detail/25441.html) for the change to take effect.
-     * > The total peak public bandwidth billed on a pay-by-bandwidth basis in a single region for a single Alibaba Cloud account is subject to limits. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
+     * - The instance status must be **Stopped** (`Stopped`) before you can modify the instance type. After the modification, you must [start the instance](https://help.aliyun.com/document_detail/25441.html) for the change to take effect.
+     * > In a single region, the total peak pay-by-bandwidth public bandwidth for a single Alibaba Cloud account is limited. For more information, see [Public bandwidth limits](~~25412#BandwidthQuota~~).
      *
      * @param request - ModifyInstanceSpecRequest
      * @returns ModifyInstanceSpecResponse
@@ -25121,7 +25089,7 @@ class Client extends openapi_core_1.default {
      * Updates an O&M window.
      *
      * @remarks
-     * Modifies the attributes of an O&M window. When the TargetResource parameter of an O&M window is set to associate ECS instances and an underlying hardware risk is detected that requires scheduled O&M to mitigate, the execution time of the scheduled O&M is determined based on the time range specified by the TimePeriod parameter of the O&M window. When the execution time of an O&M event is reached, the platform automatically performs the corresponding O&M operation based on the event type.
+     * Modifies the attributes of an O&M window. When the TargetResource parameter of an O&M window is set to associate ECS instances and underlying hardware risks are detected that require scheduled O&M to mitigate, the execution time of the scheduled O&M is determined based on the time range specified by the TimePeriod parameter of the O&M window. When the execution time of an O&M event is reached, the platform automatically performs the corresponding O&M operation based on the type of the O&M event.
      *
      * @param tmpReq - ModifyPlanMaintenanceWindowRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -25182,7 +25150,7 @@ class Client extends openapi_core_1.default {
      * Updates an O&M window.
      *
      * @remarks
-     * Modifies the attributes of an O&M window. When the TargetResource parameter of an O&M window is set to associate ECS instances and an underlying hardware risk is detected that requires scheduled O&M to mitigate, the execution time of the scheduled O&M is determined based on the time range specified by the TimePeriod parameter of the O&M window. When the execution time of an O&M event is reached, the platform automatically performs the corresponding O&M operation based on the event type.
+     * Modifies the attributes of an O&M window. When the TargetResource parameter of an O&M window is set to associate ECS instances and underlying hardware risks are detected that require scheduled O&M to mitigate, the execution time of the scheduled O&M is determined based on the time range specified by the TimePeriod parameter of the O&M window. When the execution time of an O&M event is reached, the platform automatically performs the corresponding O&M operation based on the type of the O&M event.
      *
      * @param request - ModifyPlanMaintenanceWindowRequest
      * @returns ModifyPlanMaintenanceWindowResponse
@@ -25351,20 +25319,24 @@ class Client extends openapi_core_1.default {
         return await this.modifyPrefixListWithOptions(request, runtime);
     }
     /**
-     * Changes the instance type of a subscription Elastic Compute Service (ECS) instance. You can upgrade or downgrade the instance type. The new instance type takes effect for the entire lifecycle of the subscription ECS instance.
+     * Modifies the instance type of a subscription ECS instance. You can upgrade or downgrade the instance type. The new instance type takes effect for the entire lifecycle of the instance.
      *
      * @remarks
-     * *Before you call this operation, make sure that you are familiar with the billing methods, [prices](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl), and [rules for unsubscribing from resources](https://help.aliyun.com/document_detail/476339.html) of ECS.**
-     * ModifyPrepayInstanceSpec is an asynchronous operation. After a request is sent, wait for 5 to 10 seconds for the instance type change to complete. Before you change the instance type of a subscription ECS instance, call the [DescribeResourcesModification](https://help.aliyun.com/document_detail/66187.html) operation to query the instance types to which you can change the instance.
-     * **Considerations**
-     * - Before you change the instance type of an expired instance, you must renew the instance.
-     * - When you downgrade the instance type of a subscription ECS instance, take note of the following items:
-     *   - The instance must be in the **Stopped** (`Stopped`) state.
-     *   - The price difference is refunded to the payment account that you used. Redeemed vouchers are not refundable.
-     *   - The new instance type takes effect only after you [start the instance](https://help.aliyun.com/document_detail/25441.html).
-     * - When you upgrade the instance type of a subscription ECS instance, take note of the following items:
-     *   - The instance must be in the **Stopped** (`Stopped`) or **Running** (`Running`) state.
-     *   - The new instance type takes effect only after you [start the instance](https://help.aliyun.com/document_detail/25441.html) or [restart the instance](https://help.aliyun.com/document_detail/25440.html).
+     * <props="china">
+     * **Before you call this operation, make sure that you fully understand the billing methods, [pricing](https://www.aliyun.com/price/product#/ecs/detail), and [downgrade refund rules](https://help.aliyun.com/document_detail/116043.html) of ECS.**
+     * <props="intl">
+     * **Before you call this operation, make sure that you fully understand the billing methods, [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl), and [downgrade refund rules](https://help.aliyun.com/document_detail/476339.html) of ECS.**
+     * This operation is asynchronous. The configuration change takes effect after approximately 5 to 10 seconds. Before you upgrade or downgrade ECS instance type of a subscription ECS instance, you can call [DescribeResourcesModification](https://help.aliyun.com/document_detail/2679954.html) to query ECS instance types to which the current instance can be changed.
+     * **Precautions**
+     *   - If the NVMe property of the source and target instance types are different (the `NvmeSupport` field returned by [DescribeInstanceTypes](https://help.aliyun.com/document_detail/2679699.html)) and the operating system is Windows (the `OSType` field returned by [DescribeInstances](https://help.aliyun.com/document_detail/2679689.html)), complete the [preventive measures](~~2978777#7de04a1c9fo50~~) before you perform the Upgrade/Downgrade.
+     *   - Expired instances cannot be changed to a different instance type. Complete the renewal and try again.
+     *   - Downgrade the instance type:
+     *     - The instance must be in the **Stopped** (`Stopped`) state.
+     *     - The price difference between the original and new instance types is refunded to your original billing method. Used vouchers are not refundable. The payer receives the refund.
+     *     - The new instance type takes effect only after you [start the instance](https://help.aliyun.com/document_detail/25441.html) after the Upgrade/Downgrade.
+     *   - Upgrade the instance type:
+     *     - The instance must be in the **Stopped** (`Stopped`) or **Running** (`Running`) state.
+     *     - The new instance type takes effect only after you [start the instance](https://help.aliyun.com/document_detail/25441.html) or [restart the instance](https://help.aliyun.com/document_detail/25440.html).
      *
      * @param request - ModifyPrepayInstanceSpecRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -25441,20 +25413,24 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyPrepayInstanceSpecResponse({}));
     }
     /**
-     * Changes the instance type of a subscription Elastic Compute Service (ECS) instance. You can upgrade or downgrade the instance type. The new instance type takes effect for the entire lifecycle of the subscription ECS instance.
+     * Modifies the instance type of a subscription ECS instance. You can upgrade or downgrade the instance type. The new instance type takes effect for the entire lifecycle of the instance.
      *
      * @remarks
-     * *Before you call this operation, make sure that you are familiar with the billing methods, [prices](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl), and [rules for unsubscribing from resources](https://help.aliyun.com/document_detail/476339.html) of ECS.**
-     * ModifyPrepayInstanceSpec is an asynchronous operation. After a request is sent, wait for 5 to 10 seconds for the instance type change to complete. Before you change the instance type of a subscription ECS instance, call the [DescribeResourcesModification](https://help.aliyun.com/document_detail/66187.html) operation to query the instance types to which you can change the instance.
-     * **Considerations**
-     * - Before you change the instance type of an expired instance, you must renew the instance.
-     * - When you downgrade the instance type of a subscription ECS instance, take note of the following items:
-     *   - The instance must be in the **Stopped** (`Stopped`) state.
-     *   - The price difference is refunded to the payment account that you used. Redeemed vouchers are not refundable.
-     *   - The new instance type takes effect only after you [start the instance](https://help.aliyun.com/document_detail/25441.html).
-     * - When you upgrade the instance type of a subscription ECS instance, take note of the following items:
-     *   - The instance must be in the **Stopped** (`Stopped`) or **Running** (`Running`) state.
-     *   - The new instance type takes effect only after you [start the instance](https://help.aliyun.com/document_detail/25441.html) or [restart the instance](https://help.aliyun.com/document_detail/25440.html).
+     * <props="china">
+     * **Before you call this operation, make sure that you fully understand the billing methods, [pricing](https://www.aliyun.com/price/product#/ecs/detail), and [downgrade refund rules](https://help.aliyun.com/document_detail/116043.html) of ECS.**
+     * <props="intl">
+     * **Before you call this operation, make sure that you fully understand the billing methods, [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl), and [downgrade refund rules](https://help.aliyun.com/document_detail/476339.html) of ECS.**
+     * This operation is asynchronous. The configuration change takes effect after approximately 5 to 10 seconds. Before you upgrade or downgrade ECS instance type of a subscription ECS instance, you can call [DescribeResourcesModification](https://help.aliyun.com/document_detail/2679954.html) to query ECS instance types to which the current instance can be changed.
+     * **Precautions**
+     *   - If the NVMe property of the source and target instance types are different (the `NvmeSupport` field returned by [DescribeInstanceTypes](https://help.aliyun.com/document_detail/2679699.html)) and the operating system is Windows (the `OSType` field returned by [DescribeInstances](https://help.aliyun.com/document_detail/2679689.html)), complete the [preventive measures](~~2978777#7de04a1c9fo50~~) before you perform the Upgrade/Downgrade.
+     *   - Expired instances cannot be changed to a different instance type. Complete the renewal and try again.
+     *   - Downgrade the instance type:
+     *     - The instance must be in the **Stopped** (`Stopped`) state.
+     *     - The price difference between the original and new instance types is refunded to your original billing method. Used vouchers are not refundable. The payer receives the refund.
+     *     - The new instance type takes effect only after you [start the instance](https://help.aliyun.com/document_detail/25441.html) after the Upgrade/Downgrade.
+     *   - Upgrade the instance type:
+     *     - The instance must be in the **Stopped** (`Stopped`) or **Running** (`Running`) state.
+     *     - The new instance type takes effect only after you [start the instance](https://help.aliyun.com/document_detail/25441.html) or [restart the instance](https://help.aliyun.com/document_detail/25440.html).
      *
      * @param request - ModifyPrepayInstanceSpecRequest
      * @returns ModifyPrepayInstanceSpecResponse
@@ -25966,12 +25942,12 @@ class Client extends openapi_core_1.default {
         return await this.modifySecurityGroupAttributeWithOptions(request, runtime);
     }
     /**
-     * Modifies an egress security group rule.
+     * Modifies an outbound security group rule.
      *
      * @remarks
-     * When modifying security group rules by specifying the security group rule ID, note the following usage limits:
-     * - Authorization objects of security group rules include IPv4 CIDR blocks (or IP addresses), IPv6 CIDR blocks (or IP addresses), security groups, and prefix lists. You cannot use this API to change the authorization object type of an existing security group rule. For example, if the original authorization object type is an IPv4 CIDR block, you can change it to another IPv4 CIDR block (or IP address), but you cannot change it to an IPv6 CIDR block (or IP address), a security group, or a prefix list.
-     * - Fields cannot be changed from non-empty to empty. If modification is needed, we recommend that you add a new rule first and then delete the current rule.
+     * When you modify a security group rule by specifying the security group rule ID, take note of the following limits:
+     * - The authorization object of a security group rule can be an IPv4 Classless Inter-Domain Routing (CIDR) block (or IP address), an IPv6 CIDR block (or IP address), a security group, or a prefix list. You cannot use this operation to change the type of the authorization object of an existing security group rule. For example, if the original authorization object type is an IPv4 CIDR block, you can change it to another IPv4 CIDR block (or IP address), but you cannot change it to an IPv6 CIDR block (or IP address), a security group, or a prefix list.
+     * - You cannot change a field value from a non-empty value to an empty value. To modify security group rules in this case, increase a new rule and then delete the current rule.
      *
      * @param request - ModifySecurityGroupEgressRuleRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -26072,12 +26048,12 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifySecurityGroupEgressRuleResponse({}));
     }
     /**
-     * Modifies an egress security group rule.
+     * Modifies an outbound security group rule.
      *
      * @remarks
-     * When modifying security group rules by specifying the security group rule ID, note the following usage limits:
-     * - Authorization objects of security group rules include IPv4 CIDR blocks (or IP addresses), IPv6 CIDR blocks (or IP addresses), security groups, and prefix lists. You cannot use this API to change the authorization object type of an existing security group rule. For example, if the original authorization object type is an IPv4 CIDR block, you can change it to another IPv4 CIDR block (or IP address), but you cannot change it to an IPv6 CIDR block (or IP address), a security group, or a prefix list.
-     * - Fields cannot be changed from non-empty to empty. If modification is needed, we recommend that you add a new rule first and then delete the current rule.
+     * When you modify a security group rule by specifying the security group rule ID, take note of the following limits:
+     * - The authorization object of a security group rule can be an IPv4 Classless Inter-Domain Routing (CIDR) block (or IP address), an IPv6 CIDR block (or IP address), a security group, or a prefix list. You cannot use this operation to change the type of the authorization object of an existing security group rule. For example, if the original authorization object type is an IPv4 CIDR block, you can change it to another IPv4 CIDR block (or IP address), but you cannot change it to an IPv6 CIDR block (or IP address), a security group, or a prefix list.
+     * - You cannot change a field value from a non-empty value to an empty value. To modify security group rules in this case, increase a new rule and then delete the current rule.
      *
      * @param request - ModifySecurityGroupEgressRuleRequest
      * @returns ModifySecurityGroupEgressRuleResponse
@@ -26164,7 +26140,7 @@ class Client extends openapi_core_1.default {
      * @remarks
      * When you modify a security group rule by specifying the security group rule ID, take note of the following limits:
      * - The authorization object of a security group rule can be an IPv4 Classless Inter-Domain Routing (CIDR) block (or IP address), an IPv6 CIDR block (or IP address), a security group, or a prefix list. You cannot use this operation to change the type of the authorization object of an existing security group rule. For example, if the original authorization object type is an IPv4 CIDR block, you can change it to another IPv4 CIDR block (or IP address), but you cannot change it to an IPv6 CIDR block (or IP address), a security group, or a prefix list.
-     * - You cannot change a field from a non-empty value to an empty value. To modify security group rules in this case, increase a new rule and then delete the current rule.
+     * - You cannot change a field value from a non-empty value to an empty value. To modify security group rules in this case, increase a new rule and then delete the current rule.
      *
      * @param request - ModifySecurityGroupRuleRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -26270,7 +26246,7 @@ class Client extends openapi_core_1.default {
      * @remarks
      * When you modify a security group rule by specifying the security group rule ID, take note of the following limits:
      * - The authorization object of a security group rule can be an IPv4 Classless Inter-Domain Routing (CIDR) block (or IP address), an IPv6 CIDR block (or IP address), a security group, or a prefix list. You cannot use this operation to change the type of the authorization object of an existing security group rule. For example, if the original authorization object type is an IPv4 CIDR block, you can change it to another IPv4 CIDR block (or IP address), but you cannot change it to an IPv6 CIDR block (or IP address), a security group, or a prefix list.
-     * - You cannot change a field from a non-empty value to an empty value. To modify security group rules in this case, increase a new rule and then delete the current rule.
+     * - You cannot change a field value from a non-empty value to an empty value. To modify security group rules in this case, increase a new rule and then delete the current rule.
      *
      * @param request - ModifySecurityGroupRuleRequest
      * @returns ModifySecurityGroupRuleResponse
@@ -26596,6 +26572,66 @@ class Client extends openapi_core_1.default {
         let runtime = new $dara.RuntimeOptions({});
         return await this.modifyStorageSetAttributeWithOptions(request, runtime);
     }
+    /**
+     * 修改计划内运维事件属性
+     *
+     * @remarks
+     * ## 接口说明
+     * - 只能修改状态为Scheduled的计划内运维事件。
+     * - 传入的NotBefore不早于当前时间。
+     * -  传入的NotBefore不晚于事件产生时初始的计划执行时间。
+     *
+     * @param request - ModifySystemEventAttributeRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifySystemEventAttributeResponse
+     */
+    async modifySystemEventAttributeWithOptions(request, runtime) {
+        request.validate();
+        let query = {};
+        if (!$dara.isNull(request.eventId)) {
+            query["EventId"] = request.eventId;
+        }
+        if (!$dara.isNull(request.instanceId)) {
+            query["InstanceId"] = request.instanceId;
+        }
+        if (!$dara.isNull(request.notBefore)) {
+            query["NotBefore"] = request.notBefore;
+        }
+        if (!$dara.isNull(request.regionId)) {
+            query["RegionId"] = request.regionId;
+        }
+        let req = new openapi_core_2.$OpenApiUtil.OpenApiRequest({
+            query: openapi_core_2.OpenApiUtil.query(query),
+        });
+        let params = new openapi_core_2.$OpenApiUtil.Params({
+            action: "ModifySystemEventAttribute",
+            version: "2014-05-26",
+            protocol: "HTTPS",
+            pathname: "/",
+            method: "POST",
+            authType: "AK",
+            style: "RPC",
+            reqBodyType: "formData",
+            bodyType: "json",
+        });
+        return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifySystemEventAttributeResponse({}));
+    }
+    /**
+     * 修改计划内运维事件属性
+     *
+     * @remarks
+     * ## 接口说明
+     * - 只能修改状态为Scheduled的计划内运维事件。
+     * - 传入的NotBefore不早于当前时间。
+     * -  传入的NotBefore不晚于事件产生时初始的计划执行时间。
+     *
+     * @param request - ModifySystemEventAttributeRequest
+     * @returns ModifySystemEventAttributeResponse
+     */
+    async modifySystemEventAttribute(request) {
+        let runtime = new $dara.RuntimeOptions({});
+        return await this.modifySystemEventAttributeWithOptions(request, runtime);
+    }
     /**
      * Modifies the default user-level attributes.
      *
@@ -28253,7 +28289,7 @@ class Client extends openapi_core_1.default {
         return await this.renewDedicatedHostsWithOptions(request, runtime);
     }
     /**
-     * Renews elasticity assurances that you purchased.
+     * Renews one or more purchased elasticity assurance services.
      *
      * @param request - RenewElasticityAssurancesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -28315,7 +28351,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.RenewElasticityAssurancesResponse({}));
     }
     /**
-     * Renews elasticity assurances that you purchased.
+     * Renews one or more purchased elasticity assurance services.
      *
      * @param request - RenewElasticityAssurancesRequest
      * @returns RenewElasticityAssurancesResponse
@@ -28954,61 +28990,57 @@ class Client extends openapi_core_1.default {
         return await this.resizeDiskWithOptions(request, runtime);
     }
     /**
-     * Deletes inbound security group rules from a specific security group.
+     * Deletes one or more inbound security group rules from a specified security group.
      *
      * @remarks
-     * > Alibaba Cloud modified verification rules for the RevokeSecurityGroup operation on July 8, 2024. When you call the RevokeSecurityGroup operation to delete a security group rule that does not exist, the "InvalidParam.SecurityGroupRuleId" error code is returned instead of a success response. Update the RevokeSecurityGroup operation to use the new verification rules with the new error code based on your business requirements.
-     * You can use one of the following groups of parameters to specify the security group rules that you want to delete:
-     * - Parameters used to specify the IDs of security group rules. We recommend that you specify the IDs of security group rules to delete the rules.
-     *   - If a specified security group rule ID does not exist, the call to RevokeSecurityGroup fails.
-     * - Parameters that start with Permissions.
-     *   - If no security group rule matches the specified parameters, the call to RevokeSecurityGroup is successful but no security group rules are deleted.
-     *   - Define an inbound security group rule by configuring the following parameters together:
-     *     - Source: You can specify one parameter from SourceCidrIp (IPv4 address), Ipv6SourceCidrIp (IPv6 address), SourcetPrefixListId (prefix list ID), and SourceGroupId (source security group ID).
-     *     - PortRange: specifies the destination port range.
-     *     - IpProtocol: specifies the protocol.
-     *     - Policy: specifies the action.
-     * > You cannot specify the IDs of security group rules and the parameters that start with Permissions in the same request.
-     * ### [](#)Sample requests
-     * - Delete a security group rule based on the rule ID:
-     * <!---->
+     * >Notice: Starting July 8, 2024, Alibaba Cloud adjusted the validation rules for this operation. When you attempt to delete a security group rule that does not exist, the operation now returns the error code "InvalidParam.SecurityGroupRuleId" instead of a success response. Update your error code handling to be compatible accordingly to avoid impact on your production workloads.
+     * You can use one of the following methods to pass parameters to delete rules:
+     * - Specify security group rule IDs to delete rules (recommended).
+     *      - If a specified security group rule ID does not exist, the API invocation fails.
+     * - Specify Permissions to delete rules.
+     *     - If no matching security group rule exists, the invocation succeeds but no rule is deleted.
+     *     - The following parameters are required to identify an inbound rule:
+     *       - Source settings: Set one of SourceCidrIp (IPv4 address), Ipv6SourceCidrIp (IPv6 address), SourcePrefixListId (prefix list ID), or SourceGroupId (source security group).
+     *       - Destination port range: PortRange.
+     *       - Protocol type: IpProtocol.
+     *       - Access policy: Policy.
+     * > You cannot specify both security group rule IDs and Permissions at the same time.
+     * ### Request examples
+     * - Delete by specifying security group rule IDs.
      * ```
-     * "SecurityGroupId":"sg-bp67acfmxazb4p****", //Specify the ID of the security group.
-     * "SecurityGroupRuleId":["sgr-bpdfmk****","sgr-bpdfmg****"] //Specify the ID of the security group rule.
+     * "SecurityGroupId":"sg-bp67acfmxazb4p****", // Specify the security group ID.
+     * "SecurityGroupRuleId":["sgr-bpdfmk****","sgr-bpdfmg****"] // Specify the security group rule IDs.
      * ```
-     * - Delete a security group rule based on an IPv4 CIDR block:
-     * <!---->
+     * - Delete by specifying an IP address range.
      * ```
      * "SecurityGroupId":"sg-bp67acfmxazb4p****",
      * "Permissions":[
      *   {
-     *     "SourceCidrIp":"10.0.0.0/8", //Specify the source IPv4 CIDR block.
-     *     "IpProtocol":"TCP", //Specify the protocol.
-     *     "PortRange":"80/80", //Specify the destination port range.
-     *     "Policy":"accept" //Specify the action.
+     *     "SourceCidrIp":"10.0.0.0/8", // Specify the source IP address range.
+     *     "IpProtocol":"TCP", // Specify the protocol type.
+     *     "PortRange":"80/80", // Specify the destination port range.
+     *     "Policy":"accept" // Specify the access policy.
      *   }
      * ]
      * ```
-     * - Delete a security group rule in which a security group is referenced:
-     * <!---->
+     * - Delete by specifying another security group.
      * ```
      * "SecurityGroupId":"sg-bp67acfmxazb4p****",
      * "Permissions":[
      *   {
-     *     "SourceGroupId":"sg-bp67acfmxa123b****", //Specify the ID of the source security group.
+     *     "SourceGroupId":"sg-bp67acfmxa123b****", // Specify the source security group ID.
      *     "IpProtocol":"TCP,"
      *     "PortRange":"80/80",
      *     "Policy":"accept"
      *   ]
      * }
      * ```
-     * - Delete a security group rule in which a prefix list is referenced:
-     * <!---->
+     * - Delete by specifying a prefix list.
      * ```
      * "SecurityGroupId":"sg-bp67acfmxazb4p****",
      * "Permissions":[
      *   {
-     *     "SourcePrefixListId":pl-x1j1k5ykzqlixdcy****", //Specify the ID of the source prefix list.
+     *     "SourcePrefixListId":pl-x1j1k5ykzqlixdcy****", // Specify the source prefix list ID.
      *     "IpProtocol":"TCP",
      *     "PortRange":"80/80",
      *     "Policy":"accept"
@@ -29121,61 +29153,57 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.RevokeSecurityGroupResponse({}));
     }
     /**
-     * Deletes inbound security group rules from a specific security group.
+     * Deletes one or more inbound security group rules from a specified security group.
      *
      * @remarks
-     * > Alibaba Cloud modified verification rules for the RevokeSecurityGroup operation on July 8, 2024. When you call the RevokeSecurityGroup operation to delete a security group rule that does not exist, the "InvalidParam.SecurityGroupRuleId" error code is returned instead of a success response. Update the RevokeSecurityGroup operation to use the new verification rules with the new error code based on your business requirements.
-     * You can use one of the following groups of parameters to specify the security group rules that you want to delete:
-     * - Parameters used to specify the IDs of security group rules. We recommend that you specify the IDs of security group rules to delete the rules.
-     *   - If a specified security group rule ID does not exist, the call to RevokeSecurityGroup fails.
-     * - Parameters that start with Permissions.
-     *   - If no security group rule matches the specified parameters, the call to RevokeSecurityGroup is successful but no security group rules are deleted.
-     *   - Define an inbound security group rule by configuring the following parameters together:
-     *     - Source: You can specify one parameter from SourceCidrIp (IPv4 address), Ipv6SourceCidrIp (IPv6 address), SourcetPrefixListId (prefix list ID), and SourceGroupId (source security group ID).
-     *     - PortRange: specifies the destination port range.
-     *     - IpProtocol: specifies the protocol.
-     *     - Policy: specifies the action.
-     * > You cannot specify the IDs of security group rules and the parameters that start with Permissions in the same request.
-     * ### [](#)Sample requests
-     * - Delete a security group rule based on the rule ID:
-     * <!---->
+     * >Notice: Starting July 8, 2024, Alibaba Cloud adjusted the validation rules for this operation. When you attempt to delete a security group rule that does not exist, the operation now returns the error code "InvalidParam.SecurityGroupRuleId" instead of a success response. Update your error code handling to be compatible accordingly to avoid impact on your production workloads.
+     * You can use one of the following methods to pass parameters to delete rules:
+     * - Specify security group rule IDs to delete rules (recommended).
+     *      - If a specified security group rule ID does not exist, the API invocation fails.
+     * - Specify Permissions to delete rules.
+     *     - If no matching security group rule exists, the invocation succeeds but no rule is deleted.
+     *     - The following parameters are required to identify an inbound rule:
+     *       - Source settings: Set one of SourceCidrIp (IPv4 address), Ipv6SourceCidrIp (IPv6 address), SourcePrefixListId (prefix list ID), or SourceGroupId (source security group).
+     *       - Destination port range: PortRange.
+     *       - Protocol type: IpProtocol.
+     *       - Access policy: Policy.
+     * > You cannot specify both security group rule IDs and Permissions at the same time.
+     * ### Request examples
+     * - Delete by specifying security group rule IDs.
      * ```
-     * "SecurityGroupId":"sg-bp67acfmxazb4p****", //Specify the ID of the security group.
-     * "SecurityGroupRuleId":["sgr-bpdfmk****","sgr-bpdfmg****"] //Specify the ID of the security group rule.
+     * "SecurityGroupId":"sg-bp67acfmxazb4p****", // Specify the security group ID.
+     * "SecurityGroupRuleId":["sgr-bpdfmk****","sgr-bpdfmg****"] // Specify the security group rule IDs.
      * ```
-     * - Delete a security group rule based on an IPv4 CIDR block:
-     * <!---->
+     * - Delete by specifying an IP address range.
      * ```
      * "SecurityGroupId":"sg-bp67acfmxazb4p****",
      * "Permissions":[
      *   {
-     *     "SourceCidrIp":"10.0.0.0/8", //Specify the source IPv4 CIDR block.
-     *     "IpProtocol":"TCP", //Specify the protocol.
-     *     "PortRange":"80/80", //Specify the destination port range.
-     *     "Policy":"accept" //Specify the action.
+     *     "SourceCidrIp":"10.0.0.0/8", // Specify the source IP address range.
+     *     "IpProtocol":"TCP", // Specify the protocol type.
+     *     "PortRange":"80/80", // Specify the destination port range.
+     *     "Policy":"accept" // Specify the access policy.
      *   }
      * ]
      * ```
-     * - Delete a security group rule in which a security group is referenced:
-     * <!---->
+     * - Delete by specifying another security group.
      * ```
      * "SecurityGroupId":"sg-bp67acfmxazb4p****",
      * "Permissions":[
      *   {
-     *     "SourceGroupId":"sg-bp67acfmxa123b****", //Specify the ID of the source security group.
+     *     "SourceGroupId":"sg-bp67acfmxa123b****", // Specify the source security group ID.
      *     "IpProtocol":"TCP,"
      *     "PortRange":"80/80",
      *     "Policy":"accept"
      *   ]
      * }
      * ```
-     * - Delete a security group rule in which a prefix list is referenced:
-     * <!---->
+     * - Delete by specifying a prefix list.
      * ```
      * "SecurityGroupId":"sg-bp67acfmxazb4p****",
      * "Permissions":[
      *   {
-     *     "SourcePrefixListId":pl-x1j1k5ykzqlixdcy****", //Specify the ID of the source prefix list.
+     *     "SourcePrefixListId":pl-x1j1k5ykzqlixdcy****", // Specify the source prefix list ID.
      *     "IpProtocol":"TCP",
      *     "PortRange":"80/80",
      *     "Policy":"accept"
@@ -29194,14 +29222,14 @@ class Client extends openapi_core_1.default {
      * Deletes one or more outbound security group rules from a specified security group.
      *
      * @remarks
-     * >Notice: On July 8, 2024, Alibaba Cloud adjusted the validation rules for this operation. When you attempt to delete a security group rule that does not exist, the operation now returns the error code "InvalidSecurityGroupRule.RuleNotExist" instead of a success response. Ensure that your application is compatible with this error code to avoid impacts on your online services.
+     * >Notice: Alibaba Cloud adjusted the validation rules for this operation on July 8, 2024. When you attempt to delete a security group rule that does not exist, the operation now returns the error code "InvalidSecurityGroupRule.RuleNotExist" instead of a success response. Update your error code handling to be compatible with this change to avoid impacts on your production workloads.
      * You can use one of the following methods to pass parameters to delete security group rules:
      * - Delete rules by specifying security group rule IDs (recommended).
-     *   - If the specified security group rule ID does not exist, an error is returned.
+     *   - If a specified security group rule ID does not exist, a fault is returned.
      * - Delete rules by specifying the Permissions parameter.
-     *     - If the matching security group rule does not exist, the invoke succeeds but no rule is deleted.
+     *     - If no matching security group rule exists, the invocation succeeds but no rule is deleted.
      *     - The following parameters are required to delete a security group rule:
-     *       - Destination settings: Specify one of DestCidrIp (IPv4 address), Ipv6DestCidrIp (IPv6 address), DestPrefixListId (prefix list ID), or DestGroupId (destination security group).
+     *       - Destination: Specify one of DestCidrIp (IPv4 address), Ipv6DestCidrIp (IPv6 address), DestPrefixListId (prefix list ID), or DestGroupId (destination security group).
      *       - Destination port range: PortRange.
      *       - Protocol type: IpProtocol.
      *       - Access policy: Policy.
@@ -29212,15 +29240,15 @@ class Client extends openapi_core_1.default {
      * "SecurityGroupId":"sg-bp67acfmxazb4p****", // Specify the security group ID.
      * "SecurityGroupRuleId":["sgr-bpdfmk****","sgr-bpdfmg****"] // Specify the security group rule IDs.
      * ```
-     * - Delete by IP address CIDR block.
+     * - Delete by IP CIDR block.
      * ```
      * "SecurityGroupId":"sg-bp67acfmxazb4ph***",
      * "Permissions":[
      *   {
      *     "IpProtocol":"TCP", // Specify the protocol type.
-     *     "DestCidrIp":"10.0.0.0/8", // Specify the destination IP address CIDR block.
+     *     "DestCidrIp":"10.0.0.0/8", // Specify the destination IP CIDR block.
      *     "PortRange":"22/22", // Specify the destination port range.
-     *     "Policy":"accept" // Specify the access policy.
+     *     "Policy":"accept" // Specify the authorization policy.
      *   }
      * ]
      * ```
@@ -29248,7 +29276,7 @@ class Client extends openapi_core_1.default {
      *     "Policy":"accept",
      *   }
      * ]
-     * ```.
+     * ```
      *
      * @param request - RevokeSecurityGroupEgressRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -29361,14 +29389,14 @@ class Client extends openapi_core_1.default {
      * Deletes one or more outbound security group rules from a specified security group.
      *
      * @remarks
-     * >Notice: On July 8, 2024, Alibaba Cloud adjusted the validation rules for this operation. When you attempt to delete a security group rule that does not exist, the operation now returns the error code "InvalidSecurityGroupRule.RuleNotExist" instead of a success response. Ensure that your application is compatible with this error code to avoid impacts on your online services.
+     * >Notice: Alibaba Cloud adjusted the validation rules for this operation on July 8, 2024. When you attempt to delete a security group rule that does not exist, the operation now returns the error code "InvalidSecurityGroupRule.RuleNotExist" instead of a success response. Update your error code handling to be compatible with this change to avoid impacts on your production workloads.
      * You can use one of the following methods to pass parameters to delete security group rules:
      * - Delete rules by specifying security group rule IDs (recommended).
-     *   - If the specified security group rule ID does not exist, an error is returned.
+     *   - If a specified security group rule ID does not exist, a fault is returned.
      * - Delete rules by specifying the Permissions parameter.
-     *     - If the matching security group rule does not exist, the invoke succeeds but no rule is deleted.
+     *     - If no matching security group rule exists, the invocation succeeds but no rule is deleted.
      *     - The following parameters are required to delete a security group rule:
-     *       - Destination settings: Specify one of DestCidrIp (IPv4 address), Ipv6DestCidrIp (IPv6 address), DestPrefixListId (prefix list ID), or DestGroupId (destination security group).
+     *       - Destination: Specify one of DestCidrIp (IPv4 address), Ipv6DestCidrIp (IPv6 address), DestPrefixListId (prefix list ID), or DestGroupId (destination security group).
      *       - Destination port range: PortRange.
      *       - Protocol type: IpProtocol.
      *       - Access policy: Policy.
@@ -29379,15 +29407,15 @@ class Client extends openapi_core_1.default {
      * "SecurityGroupId":"sg-bp67acfmxazb4p****", // Specify the security group ID.
      * "SecurityGroupRuleId":["sgr-bpdfmk****","sgr-bpdfmg****"] // Specify the security group rule IDs.
      * ```
-     * - Delete by IP address CIDR block.
+     * - Delete by IP CIDR block.
      * ```
      * "SecurityGroupId":"sg-bp67acfmxazb4ph***",
      * "Permissions":[
      *   {
      *     "IpProtocol":"TCP", // Specify the protocol type.
-     *     "DestCidrIp":"10.0.0.0/8", // Specify the destination IP address CIDR block.
+     *     "DestCidrIp":"10.0.0.0/8", // Specify the destination IP CIDR block.
      *     "PortRange":"22/22", // Specify the destination port range.
-     *     "Policy":"accept" // Specify the access policy.
+     *     "Policy":"accept" // Specify the authorization policy.
      *   }
      * ]
      * ```
@@ -29415,7 +29443,7 @@ class Client extends openapi_core_1.default {
      *     "Policy":"accept",
      *   }
      * ]
-     * ```.
+     * ```
      *
      * @param request - RevokeSecurityGroupEgressRequest
      * @returns RevokeSecurityGroupEgressResponse
@@ -30437,22 +30465,22 @@ class Client extends openapi_core_1.default {
         return await this.startInstancesWithOptions(request, runtime);
     }
     /**
-     * Invoke StartTerminalSession to create a session based on the Session Manager feature. You can establish a WebSocket session with an ECS instance by specifying its instance ID. Use the WebSocketUrl returned by the API to remotely connect to the ECS instance.
+     * Invokes StartTerminalSession to create a session based on the session management feature. You can establish a WebSocket session with an ECS instance by specifying the instance ID. The WebSocketUrl returned by this operation can be used to establish a remote connection to the ECS instance.
      *
      * @remarks
-     * ## API Guide
-     * When you customize a remote connection client through code, you can invoke this API to obtain the WebSocketUrl for remotely connecting to an ECS instance. Note the following when invoking this API:
-     * - The specified ECS instance must be in the running state.
-     * - The specified ECS instance must have the Cloud Assistant Agent installed. You can invoke [DescribeCloudAssistantStatus](https://help.aliyun.com/document_detail/87346.html) to check whether the Cloud Assistant Agent is installed on the ECS instance and to query its version number.
-     *   - If the Cloud Assistant Agent is not installed on your ECS instance, invoke [InstallCloudAssistant](https://help.aliyun.com/document_detail/85916.html) to install it.
-     *   - The Cloud Assistant Agent version must be higher than the following versions to support the Session Manager feature. To upgrade the Cloud Assistant Agent version, see [Upgrade or disable automatic upgrade of Cloud Assistant Agent](https://help.aliyun.com/document_detail/134383.html).
-     *     - Linux operating system: 2.2.3.256
-     *     - Windows operating system: 2.1.3.256
-     * - After successful invocation of this API, the WebSocketUrl remains valid for 10 minutes.
-     * - If no data transmission occurs within 3 minutes after the session is established, Cloud Assistant shuts down the connection.
-     * - Within the same Region, the number of created and active sessions cannot exceed 1,000. The number of sessions in Connection Status per ECS instance cannot exceed 20. The bandwidth limit for a single session is 200 kb/s.
-     * - The port forwarding feature currently supports TCP port forwarding only and does not support UDP.
-     * - To permanently close a session and invalidate the WebSocketUrl, invoke the EndTerminalSession API.
+     * ## Operation description
+     * When you customize a remote connection client by using code, you can invoke this operation to obtain the WebSocketUrl for establishing a remote connection to an ECS instance. Take note of the following items:
+     * - The specified ECS instance must be in the Running state.
+     * - Cloud Assistant Agent must be installed on the specified ECS instance. You can invoke [DescribeCloudAssistantStatus](https://help.aliyun.com/document_detail/87346.html) to check whether Cloud Assistant Agent is installed on the ECS instance and query the version number of Cloud Assistant Agent.
+     *     - If Cloud Assistant Agent is not installed on the ECS instance, invoke [InstallCloudAssistant](https://help.aliyun.com/document_detail/85916.html) to install it.
+     *     - The version number of Cloud Assistant Agent must be later than the following versions to support the session management feature. To upgrade Cloud Assistant Agent, see [Update or disable updates for Cloud Assistant Agent](https://help.aliyun.com/document_detail/134383.html).
+     *         - Linux operating system: 2.2.3.256
+     *         - Windows operating system: 2.1.3.256
+     * - After this operation is invoked, the WebSocketUrl is valid for 10 minutes.
+     * - After a session is established, Cloud Assistant closes the connection if no data is transmitted for 3 minutes.
+     * - In a single region, a maximum of 100 sessions can be created and active. A maximum of 20 sessions can be in the connected state for a single ECS instance. The bandwidth limit for a single session is 200 KB/s.
+     * - The port forwarding feature supports only TCP port forwarding. UDP is not supported.
+     * - To permanently shutdown a session and invalidate the WebSocketUrl, invoke the EndTerminalSession operation.
      *
      * @param tmpReq - StartTerminalSessionRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -30528,22 +30556,22 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.StartTerminalSessionResponse({}));
     }
     /**
-     * Invoke StartTerminalSession to create a session based on the Session Manager feature. You can establish a WebSocket session with an ECS instance by specifying its instance ID. Use the WebSocketUrl returned by the API to remotely connect to the ECS instance.
+     * Invokes StartTerminalSession to create a session based on the session management feature. You can establish a WebSocket session with an ECS instance by specifying the instance ID. The WebSocketUrl returned by this operation can be used to establish a remote connection to the ECS instance.
      *
      * @remarks
-     * ## API Guide
-     * When you customize a remote connection client through code, you can invoke this API to obtain the WebSocketUrl for remotely connecting to an ECS instance. Note the following when invoking this API:
-     * - The specified ECS instance must be in the running state.
-     * - The specified ECS instance must have the Cloud Assistant Agent installed. You can invoke [DescribeCloudAssistantStatus](https://help.aliyun.com/document_detail/87346.html) to check whether the Cloud Assistant Agent is installed on the ECS instance and to query its version number.
-     *   - If the Cloud Assistant Agent is not installed on your ECS instance, invoke [InstallCloudAssistant](https://help.aliyun.com/document_detail/85916.html) to install it.
-     *   - The Cloud Assistant Agent version must be higher than the following versions to support the Session Manager feature. To upgrade the Cloud Assistant Agent version, see [Upgrade or disable automatic upgrade of Cloud Assistant Agent](https://help.aliyun.com/document_detail/134383.html).
-     *     - Linux operating system: 2.2.3.256
-     *     - Windows operating system: 2.1.3.256
-     * - After successful invocation of this API, the WebSocketUrl remains valid for 10 minutes.
-     * - If no data transmission occurs within 3 minutes after the session is established, Cloud Assistant shuts down the connection.
-     * - Within the same Region, the number of created and active sessions cannot exceed 1,000. The number of sessions in Connection Status per ECS instance cannot exceed 20. The bandwidth limit for a single session is 200 kb/s.
-     * - The port forwarding feature currently supports TCP port forwarding only and does not support UDP.
-     * - To permanently close a session and invalidate the WebSocketUrl, invoke the EndTerminalSession API.
+     * ## Operation description
+     * When you customize a remote connection client by using code, you can invoke this operation to obtain the WebSocketUrl for establishing a remote connection to an ECS instance. Take note of the following items:
+     * - The specified ECS instance must be in the Running state.
+     * - Cloud Assistant Agent must be installed on the specified ECS instance. You can invoke [DescribeCloudAssistantStatus](https://help.aliyun.com/document_detail/87346.html) to check whether Cloud Assistant Agent is installed on the ECS instance and query the version number of Cloud Assistant Agent.
+     *     - If Cloud Assistant Agent is not installed on the ECS instance, invoke [InstallCloudAssistant](https://help.aliyun.com/document_detail/85916.html) to install it.
+     *     - The version number of Cloud Assistant Agent must be later than the following versions to support the session management feature. To upgrade Cloud Assistant Agent, see [Update or disable updates for Cloud Assistant Agent](https://help.aliyun.com/document_detail/134383.html).
+     *         - Linux operating system: 2.2.3.256
+     *         - Windows operating system: 2.1.3.256
+     * - After this operation is invoked, the WebSocketUrl is valid for 10 minutes.
+     * - After a session is established, Cloud Assistant closes the connection if no data is transmitted for 3 minutes.
+     * - In a single region, a maximum of 100 sessions can be created and active. A maximum of 20 sessions can be in the connected state for a single ECS instance. The bandwidth limit for a single session is 200 KB/s.
+     * - The port forwarding feature supports only TCP port forwarding. UDP is not supported.
+     * - To permanently shutdown a session and invalidate the WebSocketUrl, invoke the EndTerminalSession operation.
      *
      * @param request - StartTerminalSessionRequest
      * @returns StartTerminalSessionResponse
@@ -30553,13 +30581,13 @@ class Client extends openapi_core_1.default {
         return await this.startTerminalSessionWithOptions(request, runtime);
     }
     /**
-     * Stops an Elastic Compute Service (ECS) instance. You can specify parameters to determine whether to forcefully stop the instance and the stop mode.
+     * Stops an Elastic Compute Service (ECS) instance. You can specify different stop strategies, stop modes, and batch operation modes to stop the ECS instance.
      *
      * @remarks
-     * 该接口为异步接口，实例的停止不是立即完成的，成功调用后，实例会先进入停止中（Stoping）状态，你可以调用 [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) 查看实例状态，当返回的状态为`Stopped `时代表启动成功。
-     * ### 使用须知
-     * - 被安全锁定的实例不能通过调用该接口停止。更多信息，请参见[资源安全锁定对调用 API 的影响](https://help.aliyun.com/document_detail/25695.html)。
-     * - 开启 VPC 内实例节省停机模式后，您可以通过设置`StoppedMode=KeepCharging`开启普通停机模式，ECS 实例停止后会继续计费，并为您保留 ECS 实例规格库存和公网 IP 地址。
+     * This is an asynchronous operation. The ECS instance is not stopped immediately after a successful invocation. The ECS instance first enters the Stopping state. You can invoke [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) to query the instance status. When the returned status is `Stopped`, the ECS instance is stopped.
+     * ### Before you begin
+     * - ECS instances that are locked for security reasons cannot be stopped by invoking this operation. For more information, see [Impact of resource security locks on API calls](https://help.aliyun.com/document_detail/25695.html).
+     * - After you enable the economical mode for VPC-connected instances, you can set `StoppedMode=KeepCharging` to enable the standard stop mode. The ECS instance continues billing after it is stopped, and the ECS instance type inventory and Internet IP address are retained.
      *
      * @param request - StopInstanceRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -30615,13 +30643,13 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.StopInstanceResponse({}));
     }
     /**
-     * Stops an Elastic Compute Service (ECS) instance. You can specify parameters to determine whether to forcefully stop the instance and the stop mode.
+     * Stops an Elastic Compute Service (ECS) instance. You can specify different stop strategies, stop modes, and batch operation modes to stop the ECS instance.
      *
      * @remarks
-     * 该接口为异步接口，实例的停止不是立即完成的，成功调用后，实例会先进入停止中（Stoping）状态，你可以调用 [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) 查看实例状态，当返回的状态为`Stopped `时代表启动成功。
-     * ### 使用须知
-     * - 被安全锁定的实例不能通过调用该接口停止。更多信息，请参见[资源安全锁定对调用 API 的影响](https://help.aliyun.com/document_detail/25695.html)。
-     * - 开启 VPC 内实例节省停机模式后，您可以通过设置`StoppedMode=KeepCharging`开启普通停机模式，ECS 实例停止后会继续计费，并为您保留 ECS 实例规格库存和公网 IP 地址。
+     * This is an asynchronous operation. The ECS instance is not stopped immediately after a successful invocation. The ECS instance first enters the Stopping state. You can invoke [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) to query the instance status. When the returned status is `Stopped`, the ECS instance is stopped.
+     * ### Before you begin
+     * - ECS instances that are locked for security reasons cannot be stopped by invoking this operation. For more information, see [Impact of resource security locks on API calls](https://help.aliyun.com/document_detail/25695.html).
+     * - After you enable the economical mode for VPC-connected instances, you can set `StoppedMode=KeepCharging` to enable the standard stop mode. The ECS instance continues billing after it is stopped, and the ECS instance type inventory and Internet IP address are retained.
      *
      * @param request - StopInstanceRequest
      * @returns StopInstanceResponse
@@ -30631,13 +30659,13 @@ class Client extends openapi_core_1.default {
         return await this.stopInstanceWithOptions(request, runtime);
     }
     /**
-     * Stops Elastic Compute Service (ECS) instances. You can specify parameters to determine whether to forcefully stop the instances and the stop mode.
+     * Stops one or more ECS instances. You can specify the stop method, stop mode, and batch operation mode.
      *
      * @remarks
-     * 该接口为异步接口，实例的停止不是立即完成的，成功调用后，实例会先进入停止中（Stoping）状态，你可以调用 [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) 查看实例状态，当返回的状态为`Stopped `时代表停止成功。
-     * ### 使用须知
-     * - 停止实例后实例不可用，请确认停止实例不会对您的业务造成影响。您可以调用 [StartInstance](https://help.aliyun.com/document_detail/2679679.html) 或 [StartInstances](https://help.aliyun.com/document_detail/2679680.html) 接口启动实例。
-     * - 被安全锁定的实例不能通过调用该接口停止。更多信息，请参见[资源安全锁定对调用 API 的影响](https://help.aliyun.com/document_detail/25695.html)。
+     * This is an asynchronous operation. After a successful call, the instance enters the Stopping state. Call [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) to query the instance status. When the returned status is `Stopped`, the instance is stopped.
+     * ### Before you begin
+     * - After an instance is stopped, it becomes unavailable. Make sure that stopping the instance does not affect your business. Call [StartInstance](https://help.aliyun.com/document_detail/2679679.html) or [StartInstances](https://help.aliyun.com/document_detail/2679680.html) to start the instance.
+     * - Instances that are locked for security reasons cannot be stopped by calling this operation. For more information, see [Impacts of resource security locks on API calls](https://help.aliyun.com/document_detail/25695.html).
      *
      * @param request - StopInstancesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -30693,13 +30721,13 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.StopInstancesResponse({}));
     }
     /**
-     * Stops Elastic Compute Service (ECS) instances. You can specify parameters to determine whether to forcefully stop the instances and the stop mode.
+     * Stops one or more ECS instances. You can specify the stop method, stop mode, and batch operation mode.
      *
      * @remarks
-     * 该接口为异步接口，实例的停止不是立即完成的，成功调用后，实例会先进入停止中（Stoping）状态，你可以调用 [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) 查看实例状态，当返回的状态为`Stopped `时代表停止成功。
-     * ### 使用须知
-     * - 停止实例后实例不可用，请确认停止实例不会对您的业务造成影响。您可以调用 [StartInstance](https://help.aliyun.com/document_detail/2679679.html) 或 [StartInstances](https://help.aliyun.com/document_detail/2679680.html) 接口启动实例。
-     * - 被安全锁定的实例不能通过调用该接口停止。更多信息，请参见[资源安全锁定对调用 API 的影响](https://help.aliyun.com/document_detail/25695.html)。
+     * This is an asynchronous operation. After a successful call, the instance enters the Stopping state. Call [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) to query the instance status. When the returned status is `Stopped`, the instance is stopped.
+     * ### Before you begin
+     * - After an instance is stopped, it becomes unavailable. Make sure that stopping the instance does not affect your business. Call [StartInstance](https://help.aliyun.com/document_detail/2679679.html) or [StartInstances](https://help.aliyun.com/document_detail/2679680.html) to start the instance.
+     * - Instances that are locked for security reasons cannot be stopped by calling this operation. For more information, see [Impacts of resource security locks on API calls](https://help.aliyun.com/document_detail/25695.html).
      *
      * @param request - StopInstancesRequest
      * @returns StopInstancesResponse
@@ -30984,8 +31012,8 @@ class Client extends openapi_core_1.default {
      * @remarks
      * ## Operation description
      * When you invoke this operation, take note of the following items:
-     * - The Elastic Network Interface (ENI) must be in the **Active** (Available) or **InUse** state.
-     * - If you are operating on a primary ENI, the ECS instance to which the network interface controller (NIC) is attached must be in the **Running** or **Stopped** state.
+     * - The Elastic Network Interface (ENI) must be in the **Active** or **InUse** state.
+     * - If you are operating on a primary network interface controller (NIC), the ECS instance to which the NIC is attached must be in the **Running** or **Stopped** state.
      *
      * @param request - UnassignIpv6AddressesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -31043,8 +31071,8 @@ class Client extends openapi_core_1.default {
      * @remarks
      * ## Operation description
      * When you invoke this operation, take note of the following items:
-     * - The Elastic Network Interface (ENI) must be in the **Active** (Available) or **InUse** state.
-     * - If you are operating on a primary ENI, the ECS instance to which the network interface controller (NIC) is attached must be in the **Running** or **Stopped** state.
+     * - The Elastic Network Interface (ENI) must be in the **Active** or **InUse** state.
+     * - If you are operating on a primary network interface controller (NIC), the ECS instance to which the NIC is attached must be in the **Running** or **Stopped** state.
      *
      * @param request - UnassignIpv6AddressesRequest
      * @returns UnassignIpv6AddressesResponse