@alicloud/ecs20140526 3.0.2 → 3.0.4

package/dist/client.d.ts

@@ -396,6 +396,7 @@ export declare class ApplyAutoSnapshotPolicyResponse extends $tea.Model {
     });
 }
 export declare class AssignIpv6AddressesRequest extends $tea.Model {
+    clientToken?: string;
     ipv6Address?: string[];
     ipv6AddressCount?: number;
     ipv6Prefix?: string[];
@@ -2708,6 +2709,7 @@ export declare class CreateLaunchTemplateVersionRequest extends $tea.Model {
     });
 }
 export declare class CreateLaunchTemplateVersionResponseBody extends $tea.Model {
+    launchTemplateId?: string;
     launchTemplateVersionNumber?: number;
     requestId?: string;
     static names(): {
@@ -4533,6 +4535,7 @@ export declare class DeleteLaunchTemplateRequest extends $tea.Model {
     });
 }
 export declare class DeleteLaunchTemplateResponseBody extends $tea.Model {
+    launchTemplateId?: string;
     requestId?: string;
     static names(): {
         [key: string]: string;
@@ -4580,6 +4583,7 @@ export declare class DeleteLaunchTemplateVersionRequest extends $tea.Model {
     });
 }
 export declare class DeleteLaunchTemplateVersionResponseBody extends $tea.Model {
+    launchTemplateVersions?: DeleteLaunchTemplateVersionResponseBodyLaunchTemplateVersions;
     requestId?: string;
     static names(): {
         [key: string]: string;
@@ -7764,6 +7768,7 @@ export declare class DescribeInstanceAttributeResponseBody extends $tea.Model {
     dedicatedHostAttribute?: DescribeInstanceAttributeResponseBodyDedicatedHostAttribute;
     description?: string;
     eipAddress?: DescribeInstanceAttributeResponseBodyEipAddress;
+    enableJumboFrame?: boolean;
     expiredTime?: string;
     hostName?: string;
     imageId?: string;
@@ -13897,6 +13902,7 @@ export declare class ModifyInstanceAttributeRequest extends $tea.Model {
     creditSpecification?: string;
     deletionProtection?: boolean;
     description?: string;
+    enableJumboFrame?: boolean;
     hostName?: string;
     instanceId?: string;
     instanceName?: string;
@@ -14469,6 +14475,7 @@ export declare class ModifyLaunchTemplateDefaultVersionRequest extends $tea.Mode
     });
 }
 export declare class ModifyLaunchTemplateDefaultVersionResponseBody extends $tea.Model {
+    launchTemplateId?: string;
     requestId?: string;
     static names(): {
         [key: string]: string;
@@ -17024,6 +17031,7 @@ export declare class RunInstancesRequest extends $tea.Model {
     httpTokens?: string;
     imageFamily?: string;
     imageId?: string;
+    imageOptions?: RunInstancesRequestImageOptions;
     instanceChargeType?: string;
     instanceName?: string;
     instanceType?: string;
@@ -17041,6 +17049,7 @@ export declare class RunInstancesRequest extends $tea.Model {
     minAmount?: number;
     networkInterface?: RunInstancesRequestNetworkInterface[];
     networkInterfaceQueueNumber?: number;
+    networkOptions?: RunInstancesRequestNetworkOptions;
     ownerAccount?: string;
     ownerId?: number;
     password?: string;
@@ -17268,7 +17277,6 @@ export declare class StartInstanceRequest extends $tea.Model {
     ownerId?: number;
     resourceOwnerAccount?: string;
     resourceOwnerId?: number;
-    sourceRegionId?: string;
     static names(): {
         [key: string]: string;
     };
@@ -18275,6 +18283,7 @@ export declare class CreateAutoProvisioningGroupRequestLaunchConfigurationTag ex
 }
 export declare class CreateAutoProvisioningGroupRequestLaunchConfiguration extends $tea.Model {
     arn?: CreateAutoProvisioningGroupRequestLaunchConfigurationArn[];
+    autoReleaseTime?: string;
     creditSpecification?: string;
     dataDisk?: CreateAutoProvisioningGroupRequestLaunchConfigurationDataDisk[];
     deploymentSetId?: string;
@@ -19144,6 +19153,31 @@ export declare class DeleteActivationResponseBodyActivation extends $tea.Model {
         [key: string]: any;
     });
 }
+export declare class DeleteLaunchTemplateVersionResponseBodyLaunchTemplateVersionsLaunchTemplateVersion extends $tea.Model {
+    launchTemplateId?: string;
+    launchTemplateVersionNumber?: number;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
+export declare class DeleteLaunchTemplateVersionResponseBodyLaunchTemplateVersions extends $tea.Model {
+    launchTemplateVersion?: DeleteLaunchTemplateVersionResponseBodyLaunchTemplateVersionsLaunchTemplateVersion[];
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class DeleteRouteEntryRequestNextHopList extends $tea.Model {
     nextHopId?: string;
     nextHopType?: string;
@@ -20521,6 +20555,7 @@ export declare class DescribeDedicatedHostsResponseBodyDedicatedHostsDedicatedHo
 }
 export declare class DescribeDedicatedHostsResponseBodyDedicatedHostsDedicatedHostInstancesInstance extends $tea.Model {
     instanceId?: string;
+    instanceOwnerId?: number;
     instanceType?: string;
     socketId?: string;
     static names(): {
@@ -20644,7 +20679,7 @@ export declare class DescribeDedicatedHostsResponseBodyDedicatedHostsDedicatedHo
     });
 }
 export declare class DescribeDedicatedHostsResponseBodyDedicatedHostsDedicatedHost extends $tea.Model {
-    schedulerOptions: DescribeDedicatedHostsResponseBodyDedicatedHostsDedicatedHostSchedulerOptions;
+    schedulerOptions?: DescribeDedicatedHostsResponseBodyDedicatedHostsDedicatedHostSchedulerOptions;
     actionOnMaintenance?: string;
     autoPlacement?: string;
     autoReleaseTime?: string;
@@ -20656,6 +20691,7 @@ export declare class DescribeDedicatedHostsResponseBodyDedicatedHostsDedicatedHo
     dedicatedHostClusterId?: string;
     dedicatedHostId?: string;
     dedicatedHostName?: string;
+    dedicatedHostOwnerId?: number;
     dedicatedHostType?: string;
     description?: string;
     expiredTime?: string;
@@ -22653,6 +22689,8 @@ export declare class DescribeInstanceHistoryEventsResponseBodyInstanceSystemEven
     });
 }
 export declare class DescribeInstanceHistoryEventsResponseBodyInstanceSystemEventSetInstanceSystemEventTypeExtendedAttribute extends $tea.Model {
+    canAccept?: string;
+    code?: string;
     device?: string;
     diskId?: string;
     hostId?: string;
@@ -22660,6 +22698,9 @@ export declare class DescribeInstanceHistoryEventsResponseBodyInstanceSystemEven
     inactiveDisks?: DescribeInstanceHistoryEventsResponseBodyInstanceSystemEventSetInstanceSystemEventTypeExtendedAttributeInactiveDisks;
     migrationOptions?: DescribeInstanceHistoryEventsResponseBodyInstanceSystemEventSetInstanceSystemEventTypeExtendedAttributeMigrationOptions;
     onlineRepairPolicy?: string;
+    punishDomain?: string;
+    punishType?: string;
+    punishUrl?: string;
     rack?: string;
     static names(): {
         [key: string]: string;
@@ -24155,7 +24196,7 @@ export declare class DescribeLaunchTemplateVersionsResponseBodyLaunchTemplateVer
     });
 }
 export declare class DescribeLaunchTemplateVersionsResponseBodyLaunchTemplateVersionSetsLaunchTemplateVersionSetLaunchTemplateData extends $tea.Model {
-    systemDisk: DescribeLaunchTemplateVersionsResponseBodyLaunchTemplateVersionSetsLaunchTemplateVersionSetLaunchTemplateDataSystemDisk;
+    systemDisk?: DescribeLaunchTemplateVersionsResponseBodyLaunchTemplateVersionSetsLaunchTemplateVersionSetLaunchTemplateDataSystemDisk;
     autoReleaseTime?: string;
     dataDisks?: DescribeLaunchTemplateVersionsResponseBodyLaunchTemplateVersionSetsLaunchTemplateVersionSetLaunchTemplateDataDataDisks;
     deploymentSetId?: string;
@@ -28206,6 +28247,18 @@ export declare class RunInstancesRequestDataDisk extends $tea.Model {
         [key: string]: any;
     });
 }
+export declare class RunInstancesRequestImageOptions extends $tea.Model {
+    loginAsNonRoot?: boolean;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class RunInstancesRequestNetworkInterface extends $tea.Model {
     description?: string;
     instanceType?: string;
@@ -28230,6 +28283,18 @@ export declare class RunInstancesRequestNetworkInterface extends $tea.Model {
         [key: string]: any;
     });
 }
+export declare class RunInstancesRequestNetworkOptions extends $tea.Model {
+    enableJumboFrame?: boolean;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class RunInstancesRequestTag extends $tea.Model {
     key?: string;
     value?: string;
@@ -28534,10 +28599,9 @@ export default class Client extends OpenApi {
      */
     assignIpv6Addresses(request: AssignIpv6AddressesRequest): Promise<AssignIpv6AddressesResponse>;
     /**
-      * ## Description
-      * *   The ENI to which you want to assign secondary private IP addresses must be in the Available (Available) or InUse (InUse) state.
-      * *   When you assign secondary private IP addresses to a primary ENI, the instance to which the ENI is attached must be in the Running (Running) or Stopped (Stopped) state.
-      * *   When an ENI is in the Available (Available) state, you can assign up to 50 secondary private IP addresses to it. When an ENI is attached to an instance, the number of secondary private IP addresses that can be assigned to the ENI is subject to the instance type. For more information, see [Instance families](~~25378~~).
+      * *   The ENI to which you want to assign secondary private IP addresses must be in the Available or InUse state.
+      * *   When you assign secondary private IP addresses to 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 assign up to 50 secondary private IP addresses to it. When an ENI is attached to an instance, the number of secondary private IP addresses that can be assigned to the ENI is subject to the instance type. For more information, see [Instance families](~~25378~~).
       * *   After you call this operation for an ENI, you can obtain the secondary private IP addresses that are assigned to the ENI from the response.
       *
       * @param request AssignPrivateIpAddressesRequest
@@ -28546,10 +28610,9 @@ export default class Client extends OpenApi {
      */
     assignPrivateIpAddressesWithOptions(request: AssignPrivateIpAddressesRequest, runtime: $Util.RuntimeOptions): Promise<AssignPrivateIpAddressesResponse>;
     /**
-      * ## Description
-      * *   The ENI to which you want to assign secondary private IP addresses must be in the Available (Available) or InUse (InUse) state.
-      * *   When you assign secondary private IP addresses to a primary ENI, the instance to which the ENI is attached must be in the Running (Running) or Stopped (Stopped) state.
-      * *   When an ENI is in the Available (Available) state, you can assign up to 50 secondary private IP addresses to it. When an ENI is attached to an instance, the number of secondary private IP addresses that can be assigned to the ENI is subject to the instance type. For more information, see [Instance families](~~25378~~).
+      * *   The ENI to which you want to assign secondary private IP addresses must be in the Available or InUse state.
+      * *   When you assign secondary private IP addresses to 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 assign up to 50 secondary private IP addresses to it. When an ENI is attached to an instance, the number of secondary private IP addresses that can be assigned to the ENI is subject to the instance type. For more information, see [Instance families](~~25378~~).
       * *   After you call this operation for an ENI, you can obtain the secondary private IP addresses that are assigned to the ENI from the response.
       *
       * @param request AssignPrivateIpAddressesRequest
@@ -28681,7 +28744,8 @@ export default class Client extends OpenApi {
       * *   You can attach multiple ENIs to a single instance. For more information, see [ENI overview](~~58496~~).
       * *   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 this operation is called to attach an ENI, you can check the status or events of the ENI to determine whether the ENI is attached. The following figure shows the transitions between the states of the ENI.
-      * ![](https://static-aliyun-doc.oss-cn-hangzhou.aliyuncs.com/file-manage-files/zh-CN/20221124/esgu/AttachNetworkInterface.jpg) 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 fails to be attached.
+      * ![](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 fails to be attached.
       * **For information about examples on how to call this operation, see** [Attach an ENI](~~471550~~).
       *
       * @param request AttachNetworkInterfaceRequest
@@ -28697,7 +28761,8 @@ export default class Client extends OpenApi {
       * *   You can attach multiple ENIs to a single instance. For more information, see [ENI overview](~~58496~~).
       * *   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 this operation is called to attach an ENI, you can check the status or events of the ENI to determine whether the ENI is attached. The following figure shows the transitions between the states of the ENI.
-      * ![](https://static-aliyun-doc.oss-cn-hangzhou.aliyuncs.com/file-manage-files/zh-CN/20221124/esgu/AttachNetworkInterface.jpg) 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 fails to be attached.
+      * ![](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 fails to be attached.
       * **For information about examples on how to call this operation, see** [Attach an ENI](~~471550~~).
       *
       * @param request AttachNetworkInterfaceRequest
@@ -28705,56 +28770,47 @@ export default class Client extends OpenApi {
      */
     attachNetworkInterface(request: AttachNetworkInterfaceRequest): Promise<AttachNetworkInterfaceResponse>;
     /**
-      * In the security group-related API documents, inbound traffic refers to the traffic sent by the source and received by the destination.
+      * ## Description
       * When you call this operation, take note of the following items:
-      * - The total number of outbound and inbound rules in each security group cannot exceed 200. For more information, see the "Security group limits" section in [Limits](~~25412#SecurityGroupQuota1~~).
-      * - The valid value of Priority ranges from 1 to 100. A smaller value indicates a higher priority.
-      * - When multiple security group rules have the same priority, drop rules take precedence.
-      * - The source can be a CIDR block specified by SourceCidrIp, Ipv6SourceCidrIp, or SourcePrefixListId or can be Elastic Compute Service (ECS) instances in a security group specified by SourceGroupId.
-      * - For advanced security groups, security groups cannot be used as authorization objects.
-      * - For each basic security group, a maximum of 20 security groups can be used as authorization objects.
-      * - If the specified security group rule already exists, the call to AuthorizeSecurityGroup is successful but no security group rule is created.
-      * - The `Permissions.N` prefix is added to some parameters to generate new parameters. Original parameters and corresponding parameters prefixed with Permissions.N cannot be specified together. We recommend that you use parameters prefixed with `Permissions.N`.
-      * - You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.
-      *     - Parameters used to specify an inbound security group rule that controls access from a specific CIDR block: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and SourceCidrIp. For a security group of the Virtual Private Cloud (VPC) type, you must set the NicType parameter to intranet. For a security group of the classic network type, you can set the NicType parameter to either internet or intranet. Sample request:
-      *         ```
-      *                 http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
-      *                 &SecurityGroupId=sg-bp67acfmxazb4p****
-      *                 &Permissions.1.SourceCidrIp=10.0.0.0/8
-      *                 &Permissions.1.IpProtocol=TCP
-      *                 &Permissions.1.PortRange=22/22
-      *                 &Permissions.1.NicType=intranet
-      *                 &Permissions.1.Policy=Accept
-      *                 &<Common request parameters>
-      *
-      *         ```
-      *     - Parameters used to specify an inbound security group rule that controls access from a security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceGroupOwnerAccount, and SourceGroupId. In this case, you must set the NicType parameter to intranet. For mutual access between security groups in the classic network, you can allow or deny another security group within the same region access to your security group. The security group that is allowed access to your security group can belong to your own Alibaba Cloud account or another Alibaba Cloud account specified by the SourceGroupOwnerAccount parameter. For mutual access between security groups in VPCs, you can allow or deny another security group within the same VPC access to your security group. Sample request:
-      *         ```
-      *                 http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
-      *                 &SecurityGroupId=sg-bp67acfmxazb4p****
-      *                 &Permissions.1.SourceGroupId=sg-1651FBB**
-      *                 &Permissions.1.SourceGroupOwnerAccount=test@aliyun.com
-      *                 &Permissions.1.IpProtocol=TCP
-      *                 &Permissions.1.PortRange=22/22
-      *                 &Permissions.1.NicType=intranet
-      *                 &Permissions.1.Policy=Drop
-      *                 &<Common request parameters>
-      *
-      *         ```
-      *     - Parameters used to specify an inbound security group rule that controls access from a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and SourcePrefixListId. In this case, prefix lists support only security groups in VPCs. NicType must be set to intranet. Sample request:
-      *         ```
-      *                 http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
-      *                 &SecurityGroupId=sg-bp67acfmxazb4p****
-      *                 &Permissions.1.SourcePrefixListId=pl-x1j1k5ykzqlixdcy****
-      *                 &Permissions.1.SourceGroupOwnerAccount=test@aliyun.com
-      *                 &Permissions.1.IpProtocol=TCP
-      *                 &Permissions.1.PortRange=22/22
-      *                 &Permissions.1.NicType=intranet
-      *                 &Permissions.1.Policy=Drop
-      *                 &<Common request parameters>
-      *
-      *         ```
-      * - For information about examples on security group rule settings, see [Security groups for different use cases](~~25475~~) and [Security group quintuple rules](~~97439~~).
+      * *   The total number of inbound and outbound security group rules in each security group cannot exceed 200. For more information, see the "Security group limits" section in [Limits](~~25412#SecurityGroupQuota1~~).
+      * *   The valid value of Priority ranges from 1 to 100. A smaller value indicates a higher priority.
+      * *   When multiple security group rules have the same priority, drop rules take precedence.
+      * *   The source can be a CIDR block specified by SourceCidrIp, Ipv6SourceCidrIp, or SourcePrefixListId or can be Elastic Compute Service (ECS) instances in a security group specified by SourceGroupId.
+      * *   For advanced security groups, security groups cannot be used as authorization objects.
+      * *   For each basic security group, a maximum of 20 security groups can be used as authorization objects.
+      * *   If the specified security group rule exists in the security group, the call is successful but no security group rule is created.
+      * *   The `Permissions.N` prefix is added to some parameters to generate new parameters. Original parameters and corresponding parameters prefixed with Permissions.N cannot be specified together. We recommend that you use parameters prefixed with `Permissions.N`.
+      * *   You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.
+      *     *   Parameters used to specify a security group rule that controls access from a specified CIDR block: IpProtocol, PortRange, SourcePortRange, NicType, Policy, and SourceCidrIp. For a security group of the Virtual Private Cloud (VPC) type, you must set the NicType parameter to intranet. For a security group of the classic network type, you can set the NicType parameter to either internet or intranet. Sample request:
+      *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
+      *             &SecurityGroupId=sg-bp67acfmxazb4p****
+      *             &Permissions.1.SourceCidrIp=10.0.0.0/8
+      *             &Permissions.1.IpProtocol=TCP
+      *             &Permissions.1.PortRange=22/22
+      *             &Permissions.1.NicType=intranet
+      *             &Permissions.1.Policy=Accept
+      *             &<Common request parameters>
+      *     *   Parameters used to specify a security group rule that controls access from a security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceGroupOwnerAccount, and SourceGroupId. In this case, you must set the NicType parameter to intranet. To allow mutual access between security groups in the classic network, you can allow or deny another security group within the same region access to your security group. The security group that is allowed access to your security group can belong to your own Alibaba Cloud account or another Alibaba Cloud account specified by the SourceGroupOwnerAccount parameter. To allow mutual access between security groups in VPCs, you can allow or deny another security group within the same VPC access to your security group. Sample request:
+      *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
+      *             &SecurityGroupId=sg-bp67acfmxazb4p****
+      *             &Permissions.1.SourceGroupId=sg-1651FBB**
+      *             &Permissions.1.SourceGroupOwnerAccount=test@aliyun.com
+      *             &Permissions.1.IpProtocol=TCP
+      *             &Permissions.1.PortRange=22/22
+      *             &Permissions.1.NicType=intranet
+      *             &Permissions.1.Policy=Drop
+      *             &<Common request parameters>
+      *     *   Parameters used to specify a security group rule that controls access from a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and DestPrefixListId. In this case, prefix lists support only security groups in VPCs. NicType must be set to intranet. Sample request:
+      *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
+      *             &SecurityGroupId=sg-bp67acfmxazb4p****
+      *             &Permissions.1.SourcePrefixListId=pl-x1j1k5ykzqlixdcy****
+      *             &Permissions.1.SourceGroupOwnerAccount=test@aliyun.com
+      *             &Permissions.1.IpProtocol=TCP
+      *             &Permissions.1.PortRange=22/22
+      *             &Permissions.1.NicType=intranet
+      *             &Permissions.1.Policy=Drop
+      *             &<Common request parameters>
+      * *   For information about examples on security group rule settings, see [Security groups for different use cases](~~25475~~) and [Security group quintuple rules](~~97439~~).
       *
       * @param request AuthorizeSecurityGroupRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -28762,74 +28818,66 @@ export default class Client extends OpenApi {
      */
     authorizeSecurityGroupWithOptions(request: AuthorizeSecurityGroupRequest, runtime: $Util.RuntimeOptions): Promise<AuthorizeSecurityGroupResponse>;
     /**
-      * In the security group-related API documents, inbound traffic refers to the traffic sent by the source and received by the destination.
+      * ## Description
       * When you call this operation, take note of the following items:
-      * - The total number of outbound and inbound rules in each security group cannot exceed 200. For more information, see the "Security group limits" section in [Limits](~~25412#SecurityGroupQuota1~~).
-      * - The valid value of Priority ranges from 1 to 100. A smaller value indicates a higher priority.
-      * - When multiple security group rules have the same priority, drop rules take precedence.
-      * - The source can be a CIDR block specified by SourceCidrIp, Ipv6SourceCidrIp, or SourcePrefixListId or can be Elastic Compute Service (ECS) instances in a security group specified by SourceGroupId.
-      * - For advanced security groups, security groups cannot be used as authorization objects.
-      * - For each basic security group, a maximum of 20 security groups can be used as authorization objects.
-      * - If the specified security group rule already exists, the call to AuthorizeSecurityGroup is successful but no security group rule is created.
-      * - The `Permissions.N` prefix is added to some parameters to generate new parameters. Original parameters and corresponding parameters prefixed with Permissions.N cannot be specified together. We recommend that you use parameters prefixed with `Permissions.N`.
-      * - You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.
-      *     - Parameters used to specify an inbound security group rule that controls access from a specific CIDR block: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and SourceCidrIp. For a security group of the Virtual Private Cloud (VPC) type, you must set the NicType parameter to intranet. For a security group of the classic network type, you can set the NicType parameter to either internet or intranet. Sample request:
-      *         ```
-      *                 http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
-      *                 &SecurityGroupId=sg-bp67acfmxazb4p****
-      *                 &Permissions.1.SourceCidrIp=10.0.0.0/8
-      *                 &Permissions.1.IpProtocol=TCP
-      *                 &Permissions.1.PortRange=22/22
-      *                 &Permissions.1.NicType=intranet
-      *                 &Permissions.1.Policy=Accept
-      *                 &<Common request parameters>
-      *
-      *         ```
-      *     - Parameters used to specify an inbound security group rule that controls access from a security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceGroupOwnerAccount, and SourceGroupId. In this case, you must set the NicType parameter to intranet. For mutual access between security groups in the classic network, you can allow or deny another security group within the same region access to your security group. The security group that is allowed access to your security group can belong to your own Alibaba Cloud account or another Alibaba Cloud account specified by the SourceGroupOwnerAccount parameter. For mutual access between security groups in VPCs, you can allow or deny another security group within the same VPC access to your security group. Sample request:
-      *         ```
-      *                 http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
-      *                 &SecurityGroupId=sg-bp67acfmxazb4p****
-      *                 &Permissions.1.SourceGroupId=sg-1651FBB**
-      *                 &Permissions.1.SourceGroupOwnerAccount=test@aliyun.com
-      *                 &Permissions.1.IpProtocol=TCP
-      *                 &Permissions.1.PortRange=22/22
-      *                 &Permissions.1.NicType=intranet
-      *                 &Permissions.1.Policy=Drop
-      *                 &<Common request parameters>
-      *
-      *         ```
-      *     - Parameters used to specify an inbound security group rule that controls access from a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and SourcePrefixListId. In this case, prefix lists support only security groups in VPCs. NicType must be set to intranet. Sample request:
-      *         ```
-      *                 http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
-      *                 &SecurityGroupId=sg-bp67acfmxazb4p****
-      *                 &Permissions.1.SourcePrefixListId=pl-x1j1k5ykzqlixdcy****
-      *                 &Permissions.1.SourceGroupOwnerAccount=test@aliyun.com
-      *                 &Permissions.1.IpProtocol=TCP
-      *                 &Permissions.1.PortRange=22/22
-      *                 &Permissions.1.NicType=intranet
-      *                 &Permissions.1.Policy=Drop
-      *                 &<Common request parameters>
-      *
-      *         ```
-      * - For information about examples on security group rule settings, see [Security groups for different use cases](~~25475~~) and [Security group quintuple rules](~~97439~~).
+      * *   The total number of inbound and outbound security group rules in each security group cannot exceed 200. For more information, see the "Security group limits" section in [Limits](~~25412#SecurityGroupQuota1~~).
+      * *   The valid value of Priority ranges from 1 to 100. A smaller value indicates a higher priority.
+      * *   When multiple security group rules have the same priority, drop rules take precedence.
+      * *   The source can be a CIDR block specified by SourceCidrIp, Ipv6SourceCidrIp, or SourcePrefixListId or can be Elastic Compute Service (ECS) instances in a security group specified by SourceGroupId.
+      * *   For advanced security groups, security groups cannot be used as authorization objects.
+      * *   For each basic security group, a maximum of 20 security groups can be used as authorization objects.
+      * *   If the specified security group rule exists in the security group, the call is successful but no security group rule is created.
+      * *   The `Permissions.N` prefix is added to some parameters to generate new parameters. Original parameters and corresponding parameters prefixed with Permissions.N cannot be specified together. We recommend that you use parameters prefixed with `Permissions.N`.
+      * *   You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.
+      *     *   Parameters used to specify a security group rule that controls access from a specified CIDR block: IpProtocol, PortRange, SourcePortRange, NicType, Policy, and SourceCidrIp. For a security group of the Virtual Private Cloud (VPC) type, you must set the NicType parameter to intranet. For a security group of the classic network type, you can set the NicType parameter to either internet or intranet. Sample request:
+      *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
+      *             &SecurityGroupId=sg-bp67acfmxazb4p****
+      *             &Permissions.1.SourceCidrIp=10.0.0.0/8
+      *             &Permissions.1.IpProtocol=TCP
+      *             &Permissions.1.PortRange=22/22
+      *             &Permissions.1.NicType=intranet
+      *             &Permissions.1.Policy=Accept
+      *             &<Common request parameters>
+      *     *   Parameters used to specify a security group rule that controls access from a security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceGroupOwnerAccount, and SourceGroupId. In this case, you must set the NicType parameter to intranet. To allow mutual access between security groups in the classic network, you can allow or deny another security group within the same region access to your security group. The security group that is allowed access to your security group can belong to your own Alibaba Cloud account or another Alibaba Cloud account specified by the SourceGroupOwnerAccount parameter. To allow mutual access between security groups in VPCs, you can allow or deny another security group within the same VPC access to your security group. Sample request:
+      *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
+      *             &SecurityGroupId=sg-bp67acfmxazb4p****
+      *             &Permissions.1.SourceGroupId=sg-1651FBB**
+      *             &Permissions.1.SourceGroupOwnerAccount=test@aliyun.com
+      *             &Permissions.1.IpProtocol=TCP
+      *             &Permissions.1.PortRange=22/22
+      *             &Permissions.1.NicType=intranet
+      *             &Permissions.1.Policy=Drop
+      *             &<Common request parameters>
+      *     *   Parameters used to specify a security group rule that controls access from a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and DestPrefixListId. In this case, prefix lists support only security groups in VPCs. NicType must be set to intranet. Sample request:
+      *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroup
+      *             &SecurityGroupId=sg-bp67acfmxazb4p****
+      *             &Permissions.1.SourcePrefixListId=pl-x1j1k5ykzqlixdcy****
+      *             &Permissions.1.SourceGroupOwnerAccount=test@aliyun.com
+      *             &Permissions.1.IpProtocol=TCP
+      *             &Permissions.1.PortRange=22/22
+      *             &Permissions.1.NicType=intranet
+      *             &Permissions.1.Policy=Drop
+      *             &<Common request parameters>
+      * *   For information about examples on security group rule settings, see [Security groups for different use cases](~~25475~~) and [Security group quintuple rules](~~97439~~).
       *
       * @param request AuthorizeSecurityGroupRequest
       * @return AuthorizeSecurityGroupResponse
      */
     authorizeSecurityGroup(request: AuthorizeSecurityGroupRequest): Promise<AuthorizeSecurityGroupResponse>;
     /**
+      * ## Description
       * When you call this operation, take note of the following items:
-      * *   The total number of outbound and inbound rules in each security group cannot exceed 200. For more information, see the "Security group limits" section in [Limits](~~25412#SecurityGroupQuota1~~).
+      * *   The total number of inbound and outbound security group rules in each security group cannot exceed 200. For more information, see the "Security group limits" section in [](~~25412#SecurityGroupQuota1~~).
       * *   You can set Policy to accept or drop for each security group rule to allow or deny access.
-      * *   The valid values of Priority range from 1 to 100. A smaller value indicates a higher priority.
+      * *   The valid value of Priority ranges from 1 to 100. A smaller value indicates a higher priority.
       * *   When several security group rules have the same priority, drop rules take precedence.
-      * *   In each rule, the destination can be a CIDR block specified by DestCidrIp, Ipv6DestCidrIp, or DestPrefixListId or can be Elastic Compute Service (ECS) instances in a security group specified by DestGroupId.
-      * *   Security groups cannot be referenced as authorization objects (destinations or sources) in rules of advanced security groups.
-      * *   Up to 20 security groups can be referenced as authorization objects in rules of each basic security group.
-      * *   If the specified security group rule exists in the security group, the call to AuthorizeSecurityGroupEgress is successful but no security group rule is created.
-      * *   Parameters and their `Permissions.N`-prefixed counterparts cannot be specified at the same time. We recommend that you use the `Permissions.N`-prefixed parameters.
+      * *   The destination can be a CIDR block specified by DestCidrIp, Ipv6DestCidrIp, or DestPrefixListId or can be Elastic Compute Service (ECS) instances in a security group specified by DestGroupId.
+      * *   For advanced security groups, security groups cannot be used as authorization objects.
+      * *   For each basic security group, a maximum of 20 security groups can be used as authorization objects.
+      * *   If the specified security group rule exists in the security group, the call is successful but no security group rule is created.
+      * *   The `Permissions.N` prefix is added to some parameters to generate new parameters. Original parameters and corresponding parameters prefixed with Permissions.N cannot be specified together. We recommend that you use parameters prefixed with `Permissions.N`.
       * *   You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.
-      *     *   Parameters used to specify an outbound security group rule that controls access to a CIDR block: SecurityGroupId, Permissions.N.IpProtocol, Permissions.N.PortRange, Permissions.N.SourcePortRange, Permissions.N.NicType, Permissions.N.Policy, and Permissions.N.DestCidrIp. Permissions.N.SourcePortRange is an optional parameter. Sample request:
+      *     *   Parameters used to specify a security group rule that controls access to a specified CIDR block: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and DestCidrIp. Sample request:
       *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroupEgress
       *             &SecurityGroupId=sg-bp67acfmxazb4ph***
       *             &Permissions.1.IpProtocol=ICMP
@@ -28838,7 +28886,7 @@ export default class Client extends OpenApi {
       *             &Permissions.1.NicType=intranet
       *             &Permissions.1.Policy=Accept
       *             &<Common request parameters>
-      *     *   Parameters used to specify an outbound security group rule that controls access to a security group: SecurityGroupId, Permissions.N.IpProtocol, Permissions.N.PortRange, Permissions.N.SourcePortRange, Permissions.N.NicType, Permissions.N.Policy, Permissions.N.DestGroupOwnerAccount, and Permissions.N.DestGroupId. Permissions.N.SourcePortRange is an optional parameter. Sample request:
+      *     *   Parameters used to specify a security group rule that controls access to a security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, DestGroupOwnerAccount, and DestGroupId. Sample request:
       *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroupEgress
       *             &SecurityGroupId=sg-bp67acfmxazb4ph***
       *             &Permissions.1.DestGroupId=sg-bp67acfmxazb4pi***
@@ -28848,7 +28896,7 @@ export default class Client extends OpenApi {
       *             &Permissions.1.NicType=intranet
       *             &Permissions.1.Policy=Drop
       *             &<Common request parameters>
-      *     *   Parameters used to specify an outbound security group rule that controls access to a prefix list: SecurityGroupId, Permissions.N.IpProtocol, Permissions.N.PortRange, Permissions.N.SourcePortRange, Permissions.N.NicType, Permissions.N.Policy, and Permissions.N.DestPrefixListId. Permissions.N.SourcePortRange is an optional parameter. In this case, prefix lists support only security groups in virtual private clouds (VPCs). Permissions.N.NicType must be set to intranet. Sample request:
+      *     *   Parameters used to specify a security group rule that controls access to a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and DestPrefixListId. In this case, prefix lists support only security groups in virtual private clouds (VPCs). NicType must be set to intranet. Sample request:
       *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroupEgress
       *             &SecurityGroupId=sg-bp67acfmxazb4ph***
       *             &Permissions.1.DestPrefixListId=pl-x1j1k5ykzqlixdcy****
@@ -28865,18 +28913,19 @@ export default class Client extends OpenApi {
      */
     authorizeSecurityGroupEgressWithOptions(request: AuthorizeSecurityGroupEgressRequest, runtime: $Util.RuntimeOptions): Promise<AuthorizeSecurityGroupEgressResponse>;
     /**
+      * ## Description
       * When you call this operation, take note of the following items:
-      * *   The total number of outbound and inbound rules in each security group cannot exceed 200. For more information, see the "Security group limits" section in [Limits](~~25412#SecurityGroupQuota1~~).
+      * *   The total number of inbound and outbound security group rules in each security group cannot exceed 200. For more information, see the "Security group limits" section in [](~~25412#SecurityGroupQuota1~~).
       * *   You can set Policy to accept or drop for each security group rule to allow or deny access.
-      * *   The valid values of Priority range from 1 to 100. A smaller value indicates a higher priority.
+      * *   The valid value of Priority ranges from 1 to 100. A smaller value indicates a higher priority.
       * *   When several security group rules have the same priority, drop rules take precedence.
-      * *   In each rule, the destination can be a CIDR block specified by DestCidrIp, Ipv6DestCidrIp, or DestPrefixListId or can be Elastic Compute Service (ECS) instances in a security group specified by DestGroupId.
-      * *   Security groups cannot be referenced as authorization objects (destinations or sources) in rules of advanced security groups.
-      * *   Up to 20 security groups can be referenced as authorization objects in rules of each basic security group.
-      * *   If the specified security group rule exists in the security group, the call to AuthorizeSecurityGroupEgress is successful but no security group rule is created.
-      * *   Parameters and their `Permissions.N`-prefixed counterparts cannot be specified at the same time. We recommend that you use the `Permissions.N`-prefixed parameters.
+      * *   The destination can be a CIDR block specified by DestCidrIp, Ipv6DestCidrIp, or DestPrefixListId or can be Elastic Compute Service (ECS) instances in a security group specified by DestGroupId.
+      * *   For advanced security groups, security groups cannot be used as authorization objects.
+      * *   For each basic security group, a maximum of 20 security groups can be used as authorization objects.
+      * *   If the specified security group rule exists in the security group, the call is successful but no security group rule is created.
+      * *   The `Permissions.N` prefix is added to some parameters to generate new parameters. Original parameters and corresponding parameters prefixed with Permissions.N cannot be specified together. We recommend that you use parameters prefixed with `Permissions.N`.
       * *   You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.
-      *     *   Parameters used to specify an outbound security group rule that controls access to a CIDR block: SecurityGroupId, Permissions.N.IpProtocol, Permissions.N.PortRange, Permissions.N.SourcePortRange, Permissions.N.NicType, Permissions.N.Policy, and Permissions.N.DestCidrIp. Permissions.N.SourcePortRange is an optional parameter. Sample request:
+      *     *   Parameters used to specify a security group rule that controls access to a specified CIDR block: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and DestCidrIp. Sample request:
       *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroupEgress
       *             &SecurityGroupId=sg-bp67acfmxazb4ph***
       *             &Permissions.1.IpProtocol=ICMP
@@ -28885,7 +28934,7 @@ export default class Client extends OpenApi {
       *             &Permissions.1.NicType=intranet
       *             &Permissions.1.Policy=Accept
       *             &<Common request parameters>
-      *     *   Parameters used to specify an outbound security group rule that controls access to a security group: SecurityGroupId, Permissions.N.IpProtocol, Permissions.N.PortRange, Permissions.N.SourcePortRange, Permissions.N.NicType, Permissions.N.Policy, Permissions.N.DestGroupOwnerAccount, and Permissions.N.DestGroupId. Permissions.N.SourcePortRange is an optional parameter. Sample request:
+      *     *   Parameters used to specify a security group rule that controls access to a security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, DestGroupOwnerAccount, and DestGroupId. Sample request:
       *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroupEgress
       *             &SecurityGroupId=sg-bp67acfmxazb4ph***
       *             &Permissions.1.DestGroupId=sg-bp67acfmxazb4pi***
@@ -28895,7 +28944,7 @@ export default class Client extends OpenApi {
       *             &Permissions.1.NicType=intranet
       *             &Permissions.1.Policy=Drop
       *             &<Common request parameters>
-      *     *   Parameters used to specify an outbound security group rule that controls access to a prefix list: SecurityGroupId, Permissions.N.IpProtocol, Permissions.N.PortRange, Permissions.N.SourcePortRange, Permissions.N.NicType, Permissions.N.Policy, and Permissions.N.DestPrefixListId. Permissions.N.SourcePortRange is an optional parameter. In this case, prefix lists support only security groups in virtual private clouds (VPCs). Permissions.N.NicType must be set to intranet. Sample request:
+      *     *   Parameters used to specify a security group rule that controls access to a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, and DestPrefixListId. In this case, prefix lists support only security groups in virtual private clouds (VPCs). NicType must be set to intranet. Sample request:
       *             http(s)://ecs.aliyuncs.com/?Action=AuthorizeSecurityGroupEgress
       *             &SecurityGroupId=sg-bp67acfmxazb4ph***
       *             &Permissions.1.DestPrefixListId=pl-x1j1k5ykzqlixdcy****
@@ -28914,7 +28963,7 @@ export default class Client extends OpenApi {
     cancelAutoSnapshotPolicy(request: CancelAutoSnapshotPolicyRequest): Promise<CancelAutoSnapshotPolicyResponse>;
     /**
       * When you call this operation, take note of the following items:
-      * *   After you cancel the image copy task, the image copy created in the destination region is deleted, and the source image remains unchanged.
+      * *   After you cancel an image copy task, the image copy created in the destination region is deleted, and the copied image remains unchanged.
       * *   If the image copy task is complete, the CancelCopyImage operation fails and an error is returned.
       *
       * @param request CancelCopyImageRequest
@@ -28924,7 +28973,7 @@ export default class Client extends OpenApi {
     cancelCopyImageWithOptions(request: CancelCopyImageRequest, runtime: $Util.RuntimeOptions): Promise<CancelCopyImageResponse>;
     /**
       * When you call this operation, take note of the following items:
-      * *   After you cancel the image copy task, the image copy created in the destination region is deleted, and the source image remains unchanged.
+      * *   After you cancel an image copy task, the image copy created in the destination region is deleted, and the copied image remains unchanged.
       * *   If the image copy task is complete, the CancelCopyImage operation fails and an error is returned.
       *
       * @param request CancelCopyImageRequest
@@ -28983,7 +29032,7 @@ export default class Client extends OpenApi {
     /**
       * After a public IP address is converted into an EIP, the EIP is billed separately. Make sure that you understand the billing methods of EIPs. For more information, see [Billing overview](~~122035~~).
       * Before you call this operation, make sure that the following requirements are met:
-      * *   The instance is in the **Stopped** (`Stopped`) or **Running** (`Running`) state.
+      * *   The instance is in the `Stopped` or `Running` state.
       * *   No EIPs are associated with the instance.
       * *   The instance has no configuration change tasks that have not taken effect.
       * *   The public bandwidth of the instance is not 0 Mbit/s.
@@ -28998,7 +29047,7 @@ export default class Client extends OpenApi {
     /**
       * After a public IP address is converted into an EIP, the EIP is billed separately. Make sure that you understand the billing methods of EIPs. For more information, see [Billing overview](~~122035~~).
       * Before you call this operation, make sure that the following requirements are met:
-      * *   The instance is in the **Stopped** (`Stopped`) or **Running** (`Running`) state.
+      * *   The instance is in the `Stopped` or `Running` state.
       * *   No EIPs are associated with the instance.
       * *   The instance has no configuration change tasks that have not taken effect.
       * *   The public bandwidth of the instance is not 0 Mbit/s.
@@ -29010,13 +29059,13 @@ export default class Client extends OpenApi {
      */
     convertNatPublicIpToEip(request: ConvertNatPublicIpToEipRequest): Promise<ConvertNatPublicIpToEipResponse>;
     /**
-      * After you copy a custom image to the destination region, you can use the image copy to create Elastic Compute Service (ECS) instances by calling the RunInstances operation or replace the system disks of instances by calling the ReplaceSystemDisk operation in the destination region.
-      * When you call this operation, take note of the following items:
-      * *   Only custom images that are in the `Available` state can be copied.
-      * *   You can only copy images within your own Alibaba Cloud account. Images cannot be copied from one account to another.
-      * *   When an image is being copied, you cannot delete the image copy by calling the [DeleteImage](~~25537~~) operation, but you can cancel the running copy task by calling the [CancelCopyImage](~~25539~~) operation.
-      * *   A single region can have only one image copy task running at a time. Other image copy tasks queue up for the current task to complete before they run in sequence.
-      * *   You can set the `ResourceGroupId` parameter to specify the resource group to which the image copy belongs. If you do not set the `ResourceGroupId` parameter, the image copy belongs to the default resource group.
+      * After you copy a custom image (source image) to the destination region, you can use the image copy to create ECS instances by calling the RunInstances operation or replace the system disks of ECS instances by calling the ReplaceSystemDisk operation in the destination region.
+      * Before you call the CopyImage operation, take note of the following items:
+      * *   You can copy only custom images that are in the `Available` state.
+      * *   Custom images that you want to copy must belong to your Alibaba Cloud account or be shared with you by others, and cannot be copied across accounts.
+      * *   When an image is being copied, the copied image cannot be deleted by calling the [DeleteImage](~~25537~~) operation. However, you can cancel the running copying task by calling the [CancelCopyImage](~~25539~~) operation.
+      * *   A region can have only one image copying task running at a time. Other image copying tasks queue up for the current task to complete before the tasks run in sequence.
+      * *   You can configure the `ResourceGroupId` parameter to specify the resource group to which to assign the image copy. If you do not configure the `ResourceGroupId` parameter, the image copy is assigned to the default resource group.
       *
       * @param request CopyImageRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -29024,22 +29073,21 @@ export default class Client extends OpenApi {
      */
     copyImageWithOptions(request: CopyImageRequest, runtime: $Util.RuntimeOptions): Promise<CopyImageResponse>;
     /**
-      * After you copy a custom image to the destination region, you can use the image copy to create Elastic Compute Service (ECS) instances by calling the RunInstances operation or replace the system disks of instances by calling the ReplaceSystemDisk operation in the destination region.
-      * When you call this operation, take note of the following items:
-      * *   Only custom images that are in the `Available` state can be copied.
-      * *   You can only copy images within your own Alibaba Cloud account. Images cannot be copied from one account to another.
-      * *   When an image is being copied, you cannot delete the image copy by calling the [DeleteImage](~~25537~~) operation, but you can cancel the running copy task by calling the [CancelCopyImage](~~25539~~) operation.
-      * *   A single region can have only one image copy task running at a time. Other image copy tasks queue up for the current task to complete before they run in sequence.
-      * *   You can set the `ResourceGroupId` parameter to specify the resource group to which the image copy belongs. If you do not set the `ResourceGroupId` parameter, the image copy belongs to the default resource group.
+      * After you copy a custom image (source image) to the destination region, you can use the image copy to create ECS instances by calling the RunInstances operation or replace the system disks of ECS instances by calling the ReplaceSystemDisk operation in the destination region.
+      * Before you call the CopyImage operation, take note of the following items:
+      * *   You can copy only custom images that are in the `Available` state.
+      * *   Custom images that you want to copy must belong to your Alibaba Cloud account or be shared with you by others, and cannot be copied across accounts.
+      * *   When an image is being copied, the copied image cannot be deleted by calling the [DeleteImage](~~25537~~) operation. However, you can cancel the running copying task by calling the [CancelCopyImage](~~25539~~) operation.
+      * *   A region can have only one image copying task running at a time. Other image copying tasks queue up for the current task to complete before the tasks run in sequence.
+      * *   You can configure the `ResourceGroupId` parameter to specify the resource group to which to assign the image copy. If you do not configure the `ResourceGroupId` parameter, the image copy is assigned to the default resource group.
       *
       * @param request CopyImageRequest
       * @return CopyImageResponse
      */
     copyImage(request: CopyImageRequest): Promise<CopyImageResponse>;
     /**
-      * ## Description
       * When you call this operation, take note of the following items:
-      * *   New snapshots, which are the copies of source snapshots, cannot be used to roll back the disks for which the source snapshots were created.
+      * *   New snapshots (copies) cannot be used to roll back disks from which the source snapshots (originals) were created.
       * *   Encrypted snapshots cannot be copied.
       * *   Local snapshots cannot be copied.
       *
@@ -29049,9 +29097,8 @@ export default class Client extends OpenApi {
      */
     copySnapshotWithOptions(request: CopySnapshotRequest, runtime: $Util.RuntimeOptions): Promise<CopySnapshotResponse>;
     /**
-      * ## Description
       * When you call this operation, take note of the following items:
-      * *   New snapshots, which are the copies of source snapshots, cannot be used to roll back the disks for which the source snapshots were created.
+      * *   New snapshots (copies) cannot be used to roll back disks from which the source snapshots (originals) were created.
       * *   Encrypted snapshots cannot be copied.
       * *   Local snapshots cannot be copied.
       *
@@ -29143,9 +29190,9 @@ export default class Client extends OpenApi {
      */
     createAutoSnapshotPolicy(request: CreateAutoSnapshotPolicyRequest): Promise<CreateAutoSnapshotPolicyResponse>;
     /**
-      * When you create a capacity reservation, you can specify attributes such as a zone and an instance type. The system uses a private pool to reserve resources that match the specified attributes. For more information, see [Overview of Immediate Capacity Reservation](~~193633~~).
+      * When you create a capacity reservation, you can specify attributes such as a zone and an instance type. Then, the system uses a private pool to reserve resources that match the specified attributes. For more information, see [Overview of Immediate Capacity Reservation](~~193633~~).
       * *   Currently, only immediate capacity reservations are supported. Immediate capacity reservations take effect as soon as they are purchased. After you purchase an immediate capacity reservation, the specified instance type is billed on a pay-as-you-go basis regardless of whether the capacity reservation is actually used to create pay-as-you-go instances. Billing stops until you manually release the capacity reservation or until the capacity reservation expires and is automatically released.
-      *     *   You can call the [CreateInstance](~~25499~~) or [RunInstances](~~63440~~) operation to specify private pool attributes when you create instances. You can also call the [ModifyInstanceAttachmentAttributes](~~190006~~) operation to modify the attributes of a private pool. When an instance matches a private pool associated with a capacity reservation, you are charged based on the configurations of the instance such as the instance type, disks, and public bandwidth.
+      *     *   You can call the [CreateInstance](~~25499~~) or [RunInstances](~~63440~~) operation to specify private pool attributes when you create instances. You can also call the [ModifyInstanceAttachmentAttributes](~~190006~~) operation to modify the attributes of a private pool. When an instance matches a private pool associated with a capacity reservation, you are charged based on the configurations of the instance, such as the instance type, disks, and public bandwidth.
       *     *   Before a capacity reservation is used to create pay-as-you-go instances, you are charged only for the specified instance type.
       * *   Savings plans or regional reserved instances can be applied to offset the hourly bills of the unused capacity of immediate capacity reservations and the hourly bills of the instances that are matched to immediate capacity reservations. Zonal reserved instances cannot be applied to offset these bills. We recommend that you purchase reserved instances or savings plans before you purchase immediate capacity reservations. This way, you can have guaranteed access to resources for free within the coverage of the reserved instances or savings plans.
       * > The CreateCapacityReservation operation can be called to create only immediate capacity reservations. You can use the ECS console to create immediate or scheduled capacity reservations. For more information, see [Overview](~~193626#section-oil-qh5-xvx~~).
@@ -29156,9 +29203,9 @@ export default class Client extends OpenApi {
      */
     createCapacityReservationWithOptions(request: CreateCapacityReservationRequest, runtime: $Util.RuntimeOptions): Promise<CreateCapacityReservationResponse>;
     /**
-      * When you create a capacity reservation, you can specify attributes such as a zone and an instance type. The system uses a private pool to reserve resources that match the specified attributes. For more information, see [Overview of Immediate Capacity Reservation](~~193633~~).
+      * When you create a capacity reservation, you can specify attributes such as a zone and an instance type. Then, the system uses a private pool to reserve resources that match the specified attributes. For more information, see [Overview of Immediate Capacity Reservation](~~193633~~).
       * *   Currently, only immediate capacity reservations are supported. Immediate capacity reservations take effect as soon as they are purchased. After you purchase an immediate capacity reservation, the specified instance type is billed on a pay-as-you-go basis regardless of whether the capacity reservation is actually used to create pay-as-you-go instances. Billing stops until you manually release the capacity reservation or until the capacity reservation expires and is automatically released.
-      *     *   You can call the [CreateInstance](~~25499~~) or [RunInstances](~~63440~~) operation to specify private pool attributes when you create instances. You can also call the [ModifyInstanceAttachmentAttributes](~~190006~~) operation to modify the attributes of a private pool. When an instance matches a private pool associated with a capacity reservation, you are charged based on the configurations of the instance such as the instance type, disks, and public bandwidth.
+      *     *   You can call the [CreateInstance](~~25499~~) or [RunInstances](~~63440~~) operation to specify private pool attributes when you create instances. You can also call the [ModifyInstanceAttachmentAttributes](~~190006~~) operation to modify the attributes of a private pool. When an instance matches a private pool associated with a capacity reservation, you are charged based on the configurations of the instance, such as the instance type, disks, and public bandwidth.
       *     *   Before a capacity reservation is used to create pay-as-you-go instances, you are charged only for the specified instance type.
       * *   Savings plans or regional reserved instances can be applied to offset the hourly bills of the unused capacity of immediate capacity reservations and the hourly bills of the instances that are matched to immediate capacity reservations. Zonal reserved instances cannot be applied to offset these bills. We recommend that you purchase reserved instances or savings plans before you purchase immediate capacity reservations. This way, you can have guaranteed access to resources for free within the coverage of the reserved instances or savings plans.
       * > The CreateCapacityReservation operation can be called to create only immediate capacity reservations. You can use the ECS console to create immediate or scheduled capacity reservations. For more information, see [Overview](~~193626#section-oil-qh5-xvx~~).
@@ -29316,19 +29363,18 @@ export default class Client extends OpenApi {
     createHpcClusterWithOptions(request: CreateHpcClusterRequest, runtime: $Util.RuntimeOptions): Promise<CreateHpcClusterResponse>;
     createHpcCluster(request: CreateHpcClusterRequest): Promise<CreateHpcClusterResponse>;
     /**
-      * ## Description
-      * When you call this operation, take note of the following points:
-      * *   The created custom image can be used only when it is in the Available (Available) state.
-      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}` when you query the information of the instance, the instance is locked for security reasons and all operations are prohibited on it.
-      * You can call the CreateImage operation to create a custom image by using one of the following methods. The following request parameters are sorted by priority: `InstanceId` > `DiskDeviceMapping` > `SnapshotId`. If your request contains two or more parameters, the custom image is created based on the parameter that has a higher priority by default.
-      * *   **Method 1**: Create a custom image from an instance. You need to only specify the instance ID (`InstanceId`). The instance must be in the Running (`Running`) or Stopped (`Stopped`) state. After the CreateImage operation is called, a snapshot is created for each disk of the instance. When you create a custom image from a running instance, some cache data may not be written to the disks. As a result, the data of the created custom image may be slightly inconsistent with that of the instance. We recommend that you create custom images from instances after you stop the instances ([StopInstances](~~155372~~)).
-      * *   **Method 2**: Create a custom image from the system disk snapshot of an instance. You need to only specify the ID of the system disk snapshot (`SnapshotId`). The specified snapshot cannot be created on or before July 15, 2013.
-      * *   **Method 3**: Create a custom image from multiple disk snapshots. You must specify the data mapping between the disks and the snapshots (`DiskDeviceMapping`).
+      * When you call this operation, take note of the following items:
+      * *   You can use the created custom image only if the image is in the Available (Available) state.
+      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}`, the instance is locked to ensure security. No operations are allowed on the instance.
+      * You can call the CreateImage operation to create a custom image by using one of the following methods. The following request parameters are sorted by priority: `InstanceId` > `DiskDeviceMapping` > `SnapshotId`. If your request contains two or more of these parameters, the custom image is created based on the parameter that has a higher priority.
+      * *   **Method 1**: Create a custom image from an instance. You need to only specify the ID of the instance by using the `InstanceId` parameter. The instance must be in the Running (`Running`) or Stopped (`Stopped`) state. After you call the CreateImage operation, a snapshot is created for each disk of the instance. When you create a custom image from a running instance, specific cache data may not be written to the disks. In this case, the data of the custom image may be slightly different from the data of the instance. We recommend that you create custom images from instances after you stop the instances by calling the [StopInstances](~~155372~~) operation.
+      * *   **Method 2**: Create a custom image from the system disk snapshot of an instance. You need to only specify the ID of the system disk snapshot by using the `SnapshotId` parameter. The specified system disk snapshot must be created after July 15, 2013.
+      * *   **Method 3**: Create a custom image from multiple disk snapshots. You must specify the data mapping between the disks and the snapshots by calling the `DiskDeviceMapping` operation.
       * When you use Method 3 to create a custom image, take note of the following items:
       * *   You can specify only one system disk snapshot. The device name of the system disk must be /dev/xvda.
       * *   You can specify multiple data disk snapshots. The device names of the data disks are unique and in alphabetical order from /dev/xvdb to /dev/xvdz.
-      * *   `SnapshotId` may not be specified. In this case, an empty data disk with a specified size is created.
-      * *   The specified snapshot cannot be created on or before July 15, 2013.
+      * *   You can leave the `SnapshotId` parameter empty. In this case, an empty data disk that has a specified size is created.
+      * *   The specified disk snapshot must be created after July 15, 2013.
       *
       * @param request CreateImageRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -29336,19 +29382,18 @@ export default class Client extends OpenApi {
      */
     createImageWithOptions(request: CreateImageRequest, runtime: $Util.RuntimeOptions): Promise<CreateImageResponse>;
     /**
-      * ## Description
-      * When you call this operation, take note of the following points:
-      * *   The created custom image can be used only when it is in the Available (Available) state.
-      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}` when you query the information of the instance, the instance is locked for security reasons and all operations are prohibited on it.
-      * You can call the CreateImage operation to create a custom image by using one of the following methods. The following request parameters are sorted by priority: `InstanceId` > `DiskDeviceMapping` > `SnapshotId`. If your request contains two or more parameters, the custom image is created based on the parameter that has a higher priority by default.
-      * *   **Method 1**: Create a custom image from an instance. You need to only specify the instance ID (`InstanceId`). The instance must be in the Running (`Running`) or Stopped (`Stopped`) state. After the CreateImage operation is called, a snapshot is created for each disk of the instance. When you create a custom image from a running instance, some cache data may not be written to the disks. As a result, the data of the created custom image may be slightly inconsistent with that of the instance. We recommend that you create custom images from instances after you stop the instances ([StopInstances](~~155372~~)).
-      * *   **Method 2**: Create a custom image from the system disk snapshot of an instance. You need to only specify the ID of the system disk snapshot (`SnapshotId`). The specified snapshot cannot be created on or before July 15, 2013.
-      * *   **Method 3**: Create a custom image from multiple disk snapshots. You must specify the data mapping between the disks and the snapshots (`DiskDeviceMapping`).
+      * When you call this operation, take note of the following items:
+      * *   You can use the created custom image only if the image is in the Available (Available) state.
+      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}`, the instance is locked to ensure security. No operations are allowed on the instance.
+      * You can call the CreateImage operation to create a custom image by using one of the following methods. The following request parameters are sorted by priority: `InstanceId` > `DiskDeviceMapping` > `SnapshotId`. If your request contains two or more of these parameters, the custom image is created based on the parameter that has a higher priority.
+      * *   **Method 1**: Create a custom image from an instance. You need to only specify the ID of the instance by using the `InstanceId` parameter. The instance must be in the Running (`Running`) or Stopped (`Stopped`) state. After you call the CreateImage operation, a snapshot is created for each disk of the instance. When you create a custom image from a running instance, specific cache data may not be written to the disks. In this case, the data of the custom image may be slightly different from the data of the instance. We recommend that you create custom images from instances after you stop the instances by calling the [StopInstances](~~155372~~) operation.
+      * *   **Method 2**: Create a custom image from the system disk snapshot of an instance. You need to only specify the ID of the system disk snapshot by using the `SnapshotId` parameter. The specified system disk snapshot must be created after July 15, 2013.
+      * *   **Method 3**: Create a custom image from multiple disk snapshots. You must specify the data mapping between the disks and the snapshots by calling the `DiskDeviceMapping` operation.
       * When you use Method 3 to create a custom image, take note of the following items:
       * *   You can specify only one system disk snapshot. The device name of the system disk must be /dev/xvda.
       * *   You can specify multiple data disk snapshots. The device names of the data disks are unique and in alphabetical order from /dev/xvdb to /dev/xvdz.
-      * *   `SnapshotId` may not be specified. In this case, an empty data disk with a specified size is created.
-      * *   The specified snapshot cannot be created on or before July 15, 2013.
+      * *   You can leave the `SnapshotId` parameter empty. In this case, an empty data disk that has a specified size is created.
+      * *   The specified disk snapshot must be created after July 15, 2013.
       *
       * @param request CreateImageRequest
       * @return CreateImageResponse
@@ -29380,16 +29425,15 @@ export default class Client extends OpenApi {
      */
     createImageComponent(request: CreateImageComponentRequest): Promise<CreateImageComponentResponse>;
     /**
-      * ## Description
-      * You can use image templates to customize image content and create images across regions and accounts. When you call this operation, take note of the following items:
+      * You can use image templates to specify custom image content and create images across regions and accounts. When you create an image template, take note of the following items:
       * *   You can create only custom image templates.
-      * *   You can configure only public, custom, or shared Linux images or image families as the source images to create custom image templates.
-      * *   When you use an image template to create an image, you must create an intermediate Elastic Compute Service (ECS) instance to help create the image. The intermediate instance is billed on a pay-as-you-go basis. For more information, see [Pay-as-you-go](~~40653~~).
+      * *   You can specify only public, custom, or shared Linux images or image families as source images when you create image templates.
+      * *   When you use an image template to create an image, you must create an intermediate instance. You are charged for the intermediate instance based on the pay-as-you-go billing method. For more information, see [Pay-as-you-go](~~40653~~).
       * For the `BuildContent` parameter that specifies the content of image templates, take note of the following items:
-      * *   If the `BuildContent` value contains `FROM` commands, the values of `BaseImageType` that specifies the type of the source image and `BaseImage` that specifies the source image are overridden by the `FROM` commands.
-      * *   If the `BuildContent` value does not contain `FROM` commands, the system adds the `FROM` command that consists of the `BaseImageType` and `BaseImage` values to the first line of the template content in the format of `<BaseImageType>:<BaseImage>`.
-      * *   You can use Dockerfile to edit the content of image templates and then pass the edited content into the `BuildContent` parameter. The content cannot be greater than 16 KB in size, and can contain up to 127 commands. For information about the commands that are supported, see [Commands supported by Image Builder](~~200206~~).
-      * You can use image components to create image templates in the ECS console, but cannot call API operations to use image components to create image templates. For more information, see [Overview](~~197410~~).
+      * *   If the value of the `BuildContent` parameter contains `FROM` commands, the `FROM` commands override the values of the `BaseImageType` parameter that specifies the type of the source image and the `BaseImage` parameter that specifies the source image.
+      * *   If the value of the `BuildContent` parameter does not contain `FROM` commands, the system creates a `FROM` command that consists of the values of the `BaseImageType` and `BaseImage` parameters in the `<BaseImageType>:<BaseImage>` format and adds the command to the first line of the image template content.
+      * *   You can use Dockerfile to modify the content of image templates and pass the modified content to the `BuildContent` parameter. The content cannot exceed 16 KB in size and can contain up to 127 commands. For information about the commands that are supported by image templates, see [Description of commands supported by Image Builder](~~200206~~).
+      * You can use image components to create image templates in the Elastic Compute Service (ECS) console. You cannot call API operations to use image components to create image templates. For more information, see [Overview of creating an image](~~197410~~).
       *
       * @param request CreateImagePipelineRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -29397,16 +29441,15 @@ export default class Client extends OpenApi {
      */
     createImagePipelineWithOptions(request: CreateImagePipelineRequest, runtime: $Util.RuntimeOptions): Promise<CreateImagePipelineResponse>;
     /**
-      * ## Description
-      * You can use image templates to customize image content and create images across regions and accounts. When you call this operation, take note of the following items:
+      * You can use image templates to specify custom image content and create images across regions and accounts. When you create an image template, take note of the following items:
       * *   You can create only custom image templates.
-      * *   You can configure only public, custom, or shared Linux images or image families as the source images to create custom image templates.
-      * *   When you use an image template to create an image, you must create an intermediate Elastic Compute Service (ECS) instance to help create the image. The intermediate instance is billed on a pay-as-you-go basis. For more information, see [Pay-as-you-go](~~40653~~).
+      * *   You can specify only public, custom, or shared Linux images or image families as source images when you create image templates.
+      * *   When you use an image template to create an image, you must create an intermediate instance. You are charged for the intermediate instance based on the pay-as-you-go billing method. For more information, see [Pay-as-you-go](~~40653~~).
       * For the `BuildContent` parameter that specifies the content of image templates, take note of the following items:
-      * *   If the `BuildContent` value contains `FROM` commands, the values of `BaseImageType` that specifies the type of the source image and `BaseImage` that specifies the source image are overridden by the `FROM` commands.
-      * *   If the `BuildContent` value does not contain `FROM` commands, the system adds the `FROM` command that consists of the `BaseImageType` and `BaseImage` values to the first line of the template content in the format of `<BaseImageType>:<BaseImage>`.
-      * *   You can use Dockerfile to edit the content of image templates and then pass the edited content into the `BuildContent` parameter. The content cannot be greater than 16 KB in size, and can contain up to 127 commands. For information about the commands that are supported, see [Commands supported by Image Builder](~~200206~~).
-      * You can use image components to create image templates in the ECS console, but cannot call API operations to use image components to create image templates. For more information, see [Overview](~~197410~~).
+      * *   If the value of the `BuildContent` parameter contains `FROM` commands, the `FROM` commands override the values of the `BaseImageType` parameter that specifies the type of the source image and the `BaseImage` parameter that specifies the source image.
+      * *   If the value of the `BuildContent` parameter does not contain `FROM` commands, the system creates a `FROM` command that consists of the values of the `BaseImageType` and `BaseImage` parameters in the `<BaseImageType>:<BaseImage>` format and adds the command to the first line of the image template content.
+      * *   You can use Dockerfile to modify the content of image templates and pass the modified content to the `BuildContent` parameter. The content cannot exceed 16 KB in size and can contain up to 127 commands. For information about the commands that are supported by image templates, see [Description of commands supported by Image Builder](~~200206~~).
+      * You can use image components to create image templates in the Elastic Compute Service (ECS) console. You cannot call API operations to use image components to create image templates. For more information, see [Overview of creating an image](~~197410~~).
       *
       * @param request CreateImagePipelineRequest
       * @return CreateImagePipelineResponse
@@ -29517,12 +29560,13 @@ export default class Client extends OpenApi {
      */
     createKeyPair(request: CreateKeyPairRequest): Promise<CreateKeyPairResponse>;
     /**
+      * ## Description
       * Launch templates contain preset configurations used to create instances, such as the region, image ID, instance type, security group ID, and public bandwidth settings. If a specific parameter is not included in a launch template, you must manually specify the parameter when you use the launch template to create an instance.
       * After you create a launch template (`CreateLaunchTemplate`), its version number is set to 1 by default. You can create multiple versions (`CreateLaunchTemplateVersion`) for the launch template. Version numbers start from 1 and increment by one. If you do not specify a template version number when you use a launch template to create instances ([RunInstances](~~63440~~)), the default version is used.
       * When you call this operation, take note of the following items:
-      * * You can create up to 30 launch templates in each region. Each launch template can have up to 30 versions.
-      * * Most parameters in launch templates are optional. When you create a launch template, ECS does not verify the existence or validity of specified parameter values. The validity of the parameter values are verified only when you use the launch template to create instances.
-      * * If you set a specific parameter in a launch template, you cannot filter out this parameter when you use the launch template to create instances ([RunInstances](~~63440~~)). For example, if you set the `HostName` parameter to LocalHost in a launch template and do not specify the `HostName` parameter when you call the `RunInstances` operation to create instances from the launch template, the instance hostname is still `LocalHost`. If you want to overwrite the `LocalHost` value of HostName provided by the launch template, you can set `HostName` to MyHost or another value when you call the `RunInstances` operation.
+      * *   You can create up to 30 launch templates in each region. Each launch template can have up to 30 versions.
+      * *   Most parameters in launch templates are optional. When you create a launch template, ECS does not verify the existence or validity of specified parameter values. The validity of the parameter values are verified only when you use the launch template to create instances.
+      * *   If you set a specific parameter in a launch template, you cannot filter out this parameter when you use the launch template to create instances ([RunInstances](~~63440~~)). For example, if you set the `HostName` parameter to LocalHost in a launch template and do not set the `HostName` parameter when you call the `RunInstances` operation to create instances from the launch template, the created instance still has a hostname of `LocalHost`. If you want to overwrite the `LocalHost` value of HostName provided by the launch template, you can set `HostName` to MyHost or another value when you call the `RunInstances` operation.
       *
       * @param request CreateLaunchTemplateRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -29530,18 +29574,20 @@ export default class Client extends OpenApi {
      */
     createLaunchTemplateWithOptions(request: CreateLaunchTemplateRequest, runtime: $Util.RuntimeOptions): Promise<CreateLaunchTemplateResponse>;
     /**
+      * ## Description
       * Launch templates contain preset configurations used to create instances, such as the region, image ID, instance type, security group ID, and public bandwidth settings. If a specific parameter is not included in a launch template, you must manually specify the parameter when you use the launch template to create an instance.
       * After you create a launch template (`CreateLaunchTemplate`), its version number is set to 1 by default. You can create multiple versions (`CreateLaunchTemplateVersion`) for the launch template. Version numbers start from 1 and increment by one. If you do not specify a template version number when you use a launch template to create instances ([RunInstances](~~63440~~)), the default version is used.
       * When you call this operation, take note of the following items:
-      * * You can create up to 30 launch templates in each region. Each launch template can have up to 30 versions.
-      * * Most parameters in launch templates are optional. When you create a launch template, ECS does not verify the existence or validity of specified parameter values. The validity of the parameter values are verified only when you use the launch template to create instances.
-      * * If you set a specific parameter in a launch template, you cannot filter out this parameter when you use the launch template to create instances ([RunInstances](~~63440~~)). For example, if you set the `HostName` parameter to LocalHost in a launch template and do not specify the `HostName` parameter when you call the `RunInstances` operation to create instances from the launch template, the instance hostname is still `LocalHost`. If you want to overwrite the `LocalHost` value of HostName provided by the launch template, you can set `HostName` to MyHost or another value when you call the `RunInstances` operation.
+      * *   You can create up to 30 launch templates in each region. Each launch template can have up to 30 versions.
+      * *   Most parameters in launch templates are optional. When you create a launch template, ECS does not verify the existence or validity of specified parameter values. The validity of the parameter values are verified only when you use the launch template to create instances.
+      * *   If you set a specific parameter in a launch template, you cannot filter out this parameter when you use the launch template to create instances ([RunInstances](~~63440~~)). For example, if you set the `HostName` parameter to LocalHost in a launch template and do not set the `HostName` parameter when you call the `RunInstances` operation to create instances from the launch template, the created instance still has a hostname of `LocalHost`. If you want to overwrite the `LocalHost` value of HostName provided by the launch template, you can set `HostName` to MyHost or another value when you call the `RunInstances` operation.
       *
       * @param request CreateLaunchTemplateRequest
       * @return CreateLaunchTemplateResponse
      */
     createLaunchTemplate(request: CreateLaunchTemplateRequest): Promise<CreateLaunchTemplateResponse>;
     /**
+      * ## Description
       * If you want to modify the parameters of a launch template version, you can create another version with different parameter settings for the launch template. A maximum of 30 versions can be created for each launch template.
       *
       * @param request CreateLaunchTemplateVersionRequest
@@ -29550,6 +29596,7 @@ export default class Client extends OpenApi {
      */
     createLaunchTemplateVersionWithOptions(request: CreateLaunchTemplateVersionRequest, runtime: $Util.RuntimeOptions): Promise<CreateLaunchTemplateVersionResponse>;
     /**
+      * ## Description
       * If you want to modify the parameters of a launch template version, you can create another version with different parameter settings for the launch template. A maximum of 30 versions can be created for each launch template.
       *
       * @param request CreateLaunchTemplateVersionRequest
@@ -29679,8 +29726,8 @@ export default class Client extends OpenApi {
      */
     createRouterInterface(request: CreateRouterInterfaceRequest): Promise<CreateRouterInterfaceResponse>;
     /**
-      * When you call this operation, take note of the following points:
-      * *   You can create up to 100 security groups within a single Alibaba Cloud region.
+      * When you call this operation, take note of the following items:
+      * *   You can create up to 100 security groups in each Alibaba Cloud region.
       * *   To create a security group of the Virtual Private Cloud (VPC) type, you must specify the VpcId parameter.
       *
       * @param request CreateSecurityGroupRequest
@@ -29689,8 +29736,8 @@ export default class Client extends OpenApi {
      */
     createSecurityGroupWithOptions(request: CreateSecurityGroupRequest, runtime: $Util.RuntimeOptions): Promise<CreateSecurityGroupResponse>;
     /**
-      * When you call this operation, take note of the following points:
-      * *   You can create up to 100 security groups within a single Alibaba Cloud region.
+      * When you call this operation, take note of the following items:
+      * *   You can create up to 100 security groups in each Alibaba Cloud region.
       * *   To create a security group of the Virtual Private Cloud (VPC) type, you must specify the VpcId parameter.
       *
       * @param request CreateSecurityGroupRequest
@@ -29698,10 +29745,10 @@ export default class Client extends OpenApi {
      */
     createSecurityGroup(request: CreateSecurityGroupRequest): Promise<CreateSecurityGroupResponse>;
     /**
-      * You can use the ECS console, call the [](~~63962~~)operation, or use CloudMonitor to view the scheduled simulated system events.
-      * The following section describes the lifecycle of a simulated system event:
+      * You can use the ECS console, call [ECS API](~~63962~~) operations, or use CloudMonitor to view the scheduled simulated system events.
+      * A simulated system event can transition between the following lifecycle states:
       * *   Scheduled: The state of the simulated system event is automatically changed to Scheduled after it is scheduled.
-      * *   Executed: The state of the simulated system event is automatically changed to Executed at the scheduled time specified by the NotBefore parameter if no manual intervention is involved.
+      * *   Executed: The state of the simulated system event is automatically changed to Executed at the time specified by the NotBefore parameter if no manual intervention is involved.
       * *   Canceled: The state of the simulated system event is changed to Canceled if you cancel the event by calling the [CancelSimulatedSystemEvents](~~88808~~) operation.
       * *   Avoided: The state of the simulated system event generated from maintenance-triggered instance restart can be changed to Avoided if you restart the instance before the scheduled time of the simulated system event. The maintenance-triggered instance restart is indicated by the SystemMaintenance.Reboot value. For more information, see [RebootInstance](~~25502~~).
       *
@@ -29711,10 +29758,10 @@ export default class Client extends OpenApi {
      */
     createSimulatedSystemEventsWithOptions(request: CreateSimulatedSystemEventsRequest, runtime: $Util.RuntimeOptions): Promise<CreateSimulatedSystemEventsResponse>;
     /**
-      * You can use the ECS console, call the [](~~63962~~)operation, or use CloudMonitor to view the scheduled simulated system events.
-      * The following section describes the lifecycle of a simulated system event:
+      * You can use the ECS console, call [ECS API](~~63962~~) operations, or use CloudMonitor to view the scheduled simulated system events.
+      * A simulated system event can transition between the following lifecycle states:
       * *   Scheduled: The state of the simulated system event is automatically changed to Scheduled after it is scheduled.
-      * *   Executed: The state of the simulated system event is automatically changed to Executed at the scheduled time specified by the NotBefore parameter if no manual intervention is involved.
+      * *   Executed: The state of the simulated system event is automatically changed to Executed at the time specified by the NotBefore parameter if no manual intervention is involved.
       * *   Canceled: The state of the simulated system event is changed to Canceled if you cancel the event by calling the [CancelSimulatedSystemEvents](~~88808~~) operation.
       * *   Avoided: The state of the simulated system event generated from maintenance-triggered instance restart can be changed to Avoided if you restart the instance before the scheduled time of the simulated system event. The maintenance-triggered instance restart is indicated by the SystemMaintenance.Reboot value. For more information, see [RebootInstance](~~25502~~).
       *
@@ -29723,23 +29770,21 @@ export default class Client extends OpenApi {
      */
     createSimulatedSystemEvents(request: CreateSimulatedSystemEventsRequest): Promise<CreateSimulatedSystemEventsResponse>;
     /**
-      * ## Description
       * The local snapshot feature is replaced by the instant access feature.
-      * *   If you have used the local snapshot feature before December 14, 2020, you can use the `Category` or `InstantAccess` parameter as expected and must take note of the following items:
+      * *   If you used the local snapshot feature before December 14, 2020, you can use the `Category` or `InstantAccess` parameter as expected and must take note of the following items:
       *     *   The `Category` and `InstantAccess` parameters cannot be specified at the same time.
-      *     *   If neither of the `Category` and `InstantAccess` parameters is specified, normal snapshots are created.
-      * *   If you have not used the local snapshot feature before December 14, 2020, you can use the `InstantAccess` parameter and cannot use the `Category` parameter.
-      * For more information, see [Snapshot service upgrade and addition of a new billable item on December 14, 2020](https://help.aliyun.com/noticelist/articleid/1060755542.html).
-      * In the following scenarios, you cannot create snapshots for a disk:
+      *     *   If you do not specify the `Category` or `InstantAccess` parameter, regular snapshots are created.
+      * *   If you did not use the local snapshot feature before December 14, 2020, you can use the `InstantAccess` parameter but cannot use the `Category` parameter.
+      * You cannot create snapshots for a disk in the following scenarios:
       * *   The number of manual snapshots of the disk has reached 256.
       * *   A snapshot is being created for the disk.
-      * *   The Elastic Compute Service (ECS) instance to which the disk is attached has never been started.
+      * *   The instance to which the disk is attached has never been started.
       * *   The ECS instance to which the disk is attached is not in the **Stopped** (`Stopped`) or **Running** (`Running`) state.
-      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}` when you query the information of the instance, the instance is locked for security reasons and all operations are prohibited on it.
+      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}`, the instance is locked for security reasons. No operations are allowed on the instance.
       * When you create a snapshot, take note of the following items:
       * *   If a snapshot is being created, you cannot use this snapshot to create a custom image by calling the [CreateImage](~~25535~~) operation.
-      * *   When a snapshot is being created for a disk that is attached to an ECS instance, do not change the instance state.
-      * *   You can create snapshots for a disk that is in the **Expired** (`Expired`) state. If the release time scheduled for a disk arrives when a snapshot is being created for the disk, the snapshot is in the **Creating** (`Creating`) state and is deleted when the disk is released.
+      * *   When a snapshot is being created for a disk that is attached to an instance, do not change the instance state.
+      * *   You can create snapshots for a disk that is in the **Expired** (`Expired`) state. If the release time that is scheduled for a disk arrives when a snapshot is being created for the disk, the snapshot is in the **Creating** (`Creating`) state and is deleted when the disk is released.
       *
       * @param request CreateSnapshotRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -29747,32 +29792,29 @@ export default class Client extends OpenApi {
      */
     createSnapshotWithOptions(request: CreateSnapshotRequest, runtime: $Util.RuntimeOptions): Promise<CreateSnapshotResponse>;
     /**
-      * ## Description
       * The local snapshot feature is replaced by the instant access feature.
-      * *   If you have used the local snapshot feature before December 14, 2020, you can use the `Category` or `InstantAccess` parameter as expected and must take note of the following items:
+      * *   If you used the local snapshot feature before December 14, 2020, you can use the `Category` or `InstantAccess` parameter as expected and must take note of the following items:
       *     *   The `Category` and `InstantAccess` parameters cannot be specified at the same time.
-      *     *   If neither of the `Category` and `InstantAccess` parameters is specified, normal snapshots are created.
-      * *   If you have not used the local snapshot feature before December 14, 2020, you can use the `InstantAccess` parameter and cannot use the `Category` parameter.
-      * For more information, see [Snapshot service upgrade and addition of a new billable item on December 14, 2020](https://help.aliyun.com/noticelist/articleid/1060755542.html).
-      * In the following scenarios, you cannot create snapshots for a disk:
+      *     *   If you do not specify the `Category` or `InstantAccess` parameter, regular snapshots are created.
+      * *   If you did not use the local snapshot feature before December 14, 2020, you can use the `InstantAccess` parameter but cannot use the `Category` parameter.
+      * You cannot create snapshots for a disk in the following scenarios:
       * *   The number of manual snapshots of the disk has reached 256.
       * *   A snapshot is being created for the disk.
-      * *   The Elastic Compute Service (ECS) instance to which the disk is attached has never been started.
+      * *   The instance to which the disk is attached has never been started.
       * *   The ECS instance to which the disk is attached is not in the **Stopped** (`Stopped`) or **Running** (`Running`) state.
-      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}` when you query the information of the instance, the instance is locked for security reasons and all operations are prohibited on it.
+      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}`, the instance is locked for security reasons. No operations are allowed on the instance.
       * When you create a snapshot, take note of the following items:
       * *   If a snapshot is being created, you cannot use this snapshot to create a custom image by calling the [CreateImage](~~25535~~) operation.
-      * *   When a snapshot is being created for a disk that is attached to an ECS instance, do not change the instance state.
-      * *   You can create snapshots for a disk that is in the **Expired** (`Expired`) state. If the release time scheduled for a disk arrives when a snapshot is being created for the disk, the snapshot is in the **Creating** (`Creating`) state and is deleted when the disk is released.
+      * *   When a snapshot is being created for a disk that is attached to an instance, do not change the instance state.
+      * *   You can create snapshots for a disk that is in the **Expired** (`Expired`) state. If the release time that is scheduled for a disk arrives when a snapshot is being created for the disk, the snapshot is in the **Creating** (`Creating`) state and is deleted when the disk is released.
       *
       * @param request CreateSnapshotRequest
       * @return CreateSnapshotResponse
      */
     createSnapshot(request: CreateSnapshotRequest): Promise<CreateSnapshotResponse>;
     /**
-      * ## Description
-      * You can specify `InstanceId` to create a snapshot-consistent group for the specified disks in an instance. You can also specify `DiskId.N` to create a snapshot-consistent group for multiple disks that are attached to multiple instances within the same zone.
-      * > You cannot specify both `DiskId.N` and `ExcludeDiskId.N`. If `InstanceId` is set, you can use `DiskId.N` to specify only disks attached to the instance specified by InstanceId. You cannot use DiskId.N to specify disks attached to multiple instances.
+      * You can specify `InstanceId` to create a snapshot-consistent group for the specified disks of the instance. You can also specify `DiskId.N` to create a snapshot-consistent group for multiple disks that are attached to multiple instances within the same zone.
+      * > You cannot specify both `DiskId.N` and `ExcludeDiskId.N`. If `InstanceId` is specified, `DiskId.N` is only used to specify the disks that are attached to the instance specified by InstanceId.
       * When you call this operation, take note of the following items:
       * *   The disk for which you want to create a snapshot must be in the **In Use** (`In_use`) or **Unattached** (`Available`) state.
       *     *   If the disk is in the **In Use** (`In_use`) state, the instance to which the disk is attached must be in the **Running** (`Running`) or **Stopped** (`Stopped`) state.
@@ -29780,7 +29822,7 @@ export default class Client extends OpenApi {
       * *   The snapshot-consistent group feature can be used to create snapshots only for enhanced SSDs (ESSDs).
       * *   A single snapshot-consistent group can contain snapshots of up to 16 disks including the system disk and data disks and cannot exceed 32 TiB in size.
       * *   Snapshots that you created by using the snapshot-consistent group feature are retained until they are deleted. We recommend that you delete unnecessary snapshots on a regular basis to prevent them from incurring excessive fees.
-      * *   Snapshot-consistent groups cannot be created for disks that have the multi-attach feature enabled. If disks that have the multi-attach feature enabled are attached to an instance, you must set the `ExcludeDiskId.N` parameter to exclude these disks.
+      * *   Snapshot-consistent groups cannot be created for disks that have the multi-attach feature enabled. If disks that have the multi-attach feature enabled are attached to the instance for which you want to create a snapshot-consistent group, you must set the `ExcludeDiskId.N` parameter to exclude these disks.
       * For information about the snapshot-consistent group feature and its billing, see [Create a snapshot-consistent group](~~199625~~).
       *
       * @param request CreateSnapshotGroupRequest
@@ -29789,9 +29831,8 @@ export default class Client extends OpenApi {
      */
     createSnapshotGroupWithOptions(request: CreateSnapshotGroupRequest, runtime: $Util.RuntimeOptions): Promise<CreateSnapshotGroupResponse>;
     /**
-      * ## Description
-      * You can specify `InstanceId` to create a snapshot-consistent group for the specified disks in an instance. You can also specify `DiskId.N` to create a snapshot-consistent group for multiple disks that are attached to multiple instances within the same zone.
-      * > You cannot specify both `DiskId.N` and `ExcludeDiskId.N`. If `InstanceId` is set, you can use `DiskId.N` to specify only disks attached to the instance specified by InstanceId. You cannot use DiskId.N to specify disks attached to multiple instances.
+      * You can specify `InstanceId` to create a snapshot-consistent group for the specified disks of the instance. You can also specify `DiskId.N` to create a snapshot-consistent group for multiple disks that are attached to multiple instances within the same zone.
+      * > You cannot specify both `DiskId.N` and `ExcludeDiskId.N`. If `InstanceId` is specified, `DiskId.N` is only used to specify the disks that are attached to the instance specified by InstanceId.
       * When you call this operation, take note of the following items:
       * *   The disk for which you want to create a snapshot must be in the **In Use** (`In_use`) or **Unattached** (`Available`) state.
       *     *   If the disk is in the **In Use** (`In_use`) state, the instance to which the disk is attached must be in the **Running** (`Running`) or **Stopped** (`Stopped`) state.
@@ -29799,7 +29840,7 @@ export default class Client extends OpenApi {
       * *   The snapshot-consistent group feature can be used to create snapshots only for enhanced SSDs (ESSDs).
       * *   A single snapshot-consistent group can contain snapshots of up to 16 disks including the system disk and data disks and cannot exceed 32 TiB in size.
       * *   Snapshots that you created by using the snapshot-consistent group feature are retained until they are deleted. We recommend that you delete unnecessary snapshots on a regular basis to prevent them from incurring excessive fees.
-      * *   Snapshot-consistent groups cannot be created for disks that have the multi-attach feature enabled. If disks that have the multi-attach feature enabled are attached to an instance, you must set the `ExcludeDiskId.N` parameter to exclude these disks.
+      * *   Snapshot-consistent groups cannot be created for disks that have the multi-attach feature enabled. If disks that have the multi-attach feature enabled are attached to the instance for which you want to create a snapshot-consistent group, you must set the `ExcludeDiskId.N` parameter to exclude these disks.
       * For information about the snapshot-consistent group feature and its billing, see [Create a snapshot-consistent group](~~199625~~).
       *
       * @param request CreateSnapshotGroupRequest
@@ -29807,7 +29848,6 @@ export default class Client extends OpenApi {
      */
     createSnapshotGroup(request: CreateSnapshotGroupRequest): Promise<CreateSnapshotGroupResponse>;
     /**
-      * ## Description
       * A storage set can distribute disks or Shared Block Storage devices to different locations. You can specify the number of partitions in a storage set. A larger number of partitions indicate more discrete distribution of disks or Shared Block Storage devices.
       * When you call this operation, take note of the following items:
       * *   A limitation exists on the number of storage sets that you can create in a region. You can call the [DescribeAccountAttributes](~~73772~~) operation to query the allowed number of storage sets in a region.
@@ -29819,7 +29859,6 @@ export default class Client extends OpenApi {
      */
     createStorageSetWithOptions(request: CreateStorageSetRequest, runtime: $Util.RuntimeOptions): Promise<CreateStorageSetResponse>;
     /**
-      * ## Description
       * A storage set can distribute disks or Shared Block Storage devices to different locations. You can specify the number of partitions in a storage set. A larger number of partitions indicate more discrete distribution of disks or Shared Block Storage devices.
       * When you call this operation, take note of the following items:
       * *   A limitation exists on the number of storage sets that you can create in a region. You can call the [DescribeAccountAttributes](~~73772~~) operation to query the allowed number of storage sets in a region.
@@ -30086,14 +30125,14 @@ export default class Client extends OpenApi {
      */
     deleteInstance(request: DeleteInstanceRequest): Promise<DeleteInstanceResponse>;
     /**
-      * *   After an instance is released, all the physical resources used by the instance are recycled. Relevant data is erased and cannot be restored.
+      * *   After an instance is released, all the physical resources used by the instance are recycled. Relevant data is erased and cannot be recovered.
       * *   Disks attached to the instance:
       *     *   The disks for which `DeleteWithInstance` is set to false are retained as pay-as-you-go disks.
       *     *   The disks for which `DeleteWithInstance` is set to true are released along with the instance.
       *     *   For disks for which `DeleteAutoSnapshot` is set to false, the automatic snapshots of the disks are retained.
       *     *   For disks for which `DeleteAutoSnapshot` is set to true, the automatic snapshots of the disks are released.
       *     *   Manual snapshots of the disks are retained.
-      *     *   If `OperationLocks` in the DeleteInstances response contains `"LockReason" : "security"` for an instance, the instance is locked for security reasons. Even if the `DeleteWithInstance` parameter is set to `false` for the data disks that are attached to the instance, the parameter is ignored and the data disks are released along with the instance. For more information, see [API behavior when an instance is locked for security reasons](~~25695~~).
+      *     *   If `OperationLocks` in the DescribeInstances response contains `"LockReason" : "security"` for an instance, the instance is locked for security reasons. Even if the `DeleteWithInstance` parameter is set to `false` for the data disks that are attached to the instance, this parameter is ignored and the data disks are released along with the instance. For more information, see [API behavior when an instance is locked for security reasons](~~25695~~).
       *
       * @param request DeleteInstancesRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -30101,14 +30140,14 @@ export default class Client extends OpenApi {
      */
     deleteInstancesWithOptions(request: DeleteInstancesRequest, runtime: $Util.RuntimeOptions): Promise<DeleteInstancesResponse>;
     /**
-      * *   After an instance is released, all the physical resources used by the instance are recycled. Relevant data is erased and cannot be restored.
+      * *   After an instance is released, all the physical resources used by the instance are recycled. Relevant data is erased and cannot be recovered.
       * *   Disks attached to the instance:
       *     *   The disks for which `DeleteWithInstance` is set to false are retained as pay-as-you-go disks.
       *     *   The disks for which `DeleteWithInstance` is set to true are released along with the instance.
       *     *   For disks for which `DeleteAutoSnapshot` is set to false, the automatic snapshots of the disks are retained.
       *     *   For disks for which `DeleteAutoSnapshot` is set to true, the automatic snapshots of the disks are released.
       *     *   Manual snapshots of the disks are retained.
-      *     *   If `OperationLocks` in the DeleteInstances response contains `"LockReason" : "security"` for an instance, the instance is locked for security reasons. Even if the `DeleteWithInstance` parameter is set to `false` for the data disks that are attached to the instance, the parameter is ignored and the data disks are released along with the instance. For more information, see [API behavior when an instance is locked for security reasons](~~25695~~).
+      *     *   If `OperationLocks` in the DescribeInstances response contains `"LockReason" : "security"` for an instance, the instance is locked for security reasons. Even if the `DeleteWithInstance` parameter is set to `false` for the data disks that are attached to the instance, this parameter is ignored and the data disks are released along with the instance. For more information, see [API behavior when an instance is locked for security reasons](~~25695~~).
       *
       * @param request DeleteInstancesRequest
       * @return DeleteInstancesResponse
@@ -30157,8 +30196,15 @@ export default class Client extends OpenApi {
       * *   The ENI must be in the Available state.
       * *   If the ENI is bound to an ECS instance, you must unbind the ENI from the ECS instance ([DetachNetworkInterface](~~58514~~)) before you can delete the ENI.
       * *   After an ENI is deleted:
-      *     *   The primary private IP address of the ENI is automatically released.
+      *     *   All the private IP addresses (including primary and secondary private IP addresses) of the ENI are automatically released.
       *     *   The ENI is automatically removed from its security groups.
+      * *   This operation is an asynchronous operation. After this operation is called to delete an ENI, you can check the state or events of the ENI to determine whether the ENI is deleted. The following figure shows the transitions between the states of the ENI.
+      *
+      *     ![](https://static-aliyun-doc.oss-cn-hangzhou.aliyuncs.com/file-manage-files/en-US/20230223/krcd/DeleteNetworkInterface.png)
+      *     *   If the ENI is in the Deleting state, the ENI deletion request is sent and the ENI is being deleted.
+      *     *   If the ENI is not found, the ENI is deleted.
+      *     *   If the ENI is stuck in the Deleting state, the ENI fails to be deleted and you can re-initiate the request to delete the ENI.
+      * For information about examples on how to call this operation, see [Delete an ENI](~~471553~~).
       *
       * @param request DeleteNetworkInterfaceRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -30170,8 +30216,15 @@ export default class Client extends OpenApi {
       * *   The ENI must be in the Available state.
       * *   If the ENI is bound to an ECS instance, you must unbind the ENI from the ECS instance ([DetachNetworkInterface](~~58514~~)) before you can delete the ENI.
       * *   After an ENI is deleted:
-      *     *   The primary private IP address of the ENI is automatically released.
+      *     *   All the private IP addresses (including primary and secondary private IP addresses) of the ENI are automatically released.
       *     *   The ENI is automatically removed from its security groups.
+      * *   This operation is an asynchronous operation. After this operation is called to delete an ENI, you can check the state or events of the ENI to determine whether the ENI is deleted. The following figure shows the transitions between the states of the ENI.
+      *
+      *     ![](https://static-aliyun-doc.oss-cn-hangzhou.aliyuncs.com/file-manage-files/en-US/20230223/krcd/DeleteNetworkInterface.png)
+      *     *   If the ENI is in the Deleting state, the ENI deletion request is sent and the ENI is being deleted.
+      *     *   If the ENI is not found, the ENI is deleted.
+      *     *   If the ENI is stuck in the Deleting state, the ENI fails to be deleted and you can re-initiate the request to delete the ENI.
+      * For information about examples on how to call this operation, see [Delete an ENI](~~471553~~).
       *
       * @param request DeleteNetworkInterfaceRequest
       * @return DeleteNetworkInterfaceResponse
@@ -30270,11 +30323,10 @@ export default class Client extends OpenApi {
      */
     deleteSecurityGroup(request: DeleteSecurityGroupRequest): Promise<DeleteSecurityGroupResponse>;
     /**
-      * ## Description
       * When you call this operation, take note of the following items:
-      * *   If the specified snapshot ID does not exist, the request is ignored.
-      * *   A snapshot that has been used to create custom images cannot be deleted. The snapshot can be deleted only after the created custom images are deleted ([DeleteImage](~~25537~~)).
-      * *   A snapshot that has been used to create disks cannot be deleted. If you do want to delete the snapshot, set the `Force` parameter to true to force delete the snapshot. The disks created from the snapshot cannot be re-initialized after the snapshot is force deleted.
+      * *   If the specified snapshot does not exist, the request is ignored.
+      * *   If the specified snapshot has been used to create custom images, the snapshot cannot be deleted. You must call the [DeleteImage](~~25537~~) operation to delete the custom images before you can delete the snapshot.
+      * *   If the specified snapshot has been used to create disks and the `Force` parameter is not specified or is set to `false`, the snapshot cannot be deleted directly. If you want to delete the snapshot, set the `Force` parameter to true to forcefully delete the snapshot. The disks created from the snapshot cannot be re-initialized after the snapshot is forcefully deleted.
       *
       * @param request DeleteSnapshotRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -30282,11 +30334,10 @@ export default class Client extends OpenApi {
      */
     deleteSnapshotWithOptions(request: DeleteSnapshotRequest, runtime: $Util.RuntimeOptions): Promise<DeleteSnapshotResponse>;
     /**
-      * ## Description
       * When you call this operation, take note of the following items:
-      * *   If the specified snapshot ID does not exist, the request is ignored.
-      * *   A snapshot that has been used to create custom images cannot be deleted. The snapshot can be deleted only after the created custom images are deleted ([DeleteImage](~~25537~~)).
-      * *   A snapshot that has been used to create disks cannot be deleted. If you do want to delete the snapshot, set the `Force` parameter to true to force delete the snapshot. The disks created from the snapshot cannot be re-initialized after the snapshot is force deleted.
+      * *   If the specified snapshot does not exist, the request is ignored.
+      * *   If the specified snapshot has been used to create custom images, the snapshot cannot be deleted. You must call the [DeleteImage](~~25537~~) operation to delete the custom images before you can delete the snapshot.
+      * *   If the specified snapshot has been used to create disks and the `Force` parameter is not specified or is set to `false`, the snapshot cannot be deleted directly. If you want to delete the snapshot, set the `Force` parameter to true to forcefully delete the snapshot. The disks created from the snapshot cannot be re-initialized after the snapshot is forcefully deleted.
       *
       * @param request DeleteSnapshotRequest
       * @return DeleteSnapshotResponse
@@ -30562,7 +30613,20 @@ export default class Client extends OpenApi {
       * @return DescribeDemandsResponse
      */
     describeDemands(request: DescribeDemandsRequest): Promise<DescribeDemandsResponse>;
+    /**
+      * For more information about instance families, see [Instance families](~~25378~~).
+      *
+      * @param request DescribeDeploymentSetSupportedInstanceTypeFamilyRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return DescribeDeploymentSetSupportedInstanceTypeFamilyResponse
+     */
     describeDeploymentSetSupportedInstanceTypeFamilyWithOptions(request: DescribeDeploymentSetSupportedInstanceTypeFamilyRequest, runtime: $Util.RuntimeOptions): Promise<DescribeDeploymentSetSupportedInstanceTypeFamilyResponse>;
+    /**
+      * For more information about instance families, see [Instance families](~~25378~~).
+      *
+      * @param request DescribeDeploymentSetSupportedInstanceTypeFamilyRequest
+      * @return DescribeDeploymentSetSupportedInstanceTypeFamilyResponse
+     */
     describeDeploymentSetSupportedInstanceTypeFamily(request: DescribeDeploymentSetSupportedInstanceTypeFamilyRequest): Promise<DescribeDeploymentSetSupportedInstanceTypeFamilyResponse>;
     describeDeploymentSetsWithOptions(request: DescribeDeploymentSetsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeDeploymentSetsResponse>;
     describeDeploymentSets(request: DescribeDeploymentSetsRequest): Promise<DescribeDeploymentSetsResponse>;
@@ -30628,22 +30692,7 @@ export default class Client extends OpenApi {
       * @return DescribeDisksResponse
      */
     describeDisks(request: DescribeDisksRequest): Promise<DescribeDisksResponse>;
-    /**
-      * *   The full status information of an EBS device includes the lifecycle status provided by the `Status` parameter, health status provided by the `HealthStatus` parameter, and event type provided by the `EventType` parameter of the EBS device. You can filter the results based on these parameters.
-      * *   The release time, scheduled execution time, and actual execution time of each EBS device event are identical. If you specify a period of time by using the `EventTime.Start` and `EventTime.End` parameters, all events that occurred within this period are queried. You can query events that occurred within the last seven days.
-      *
-      * @param request DescribeDisksFullStatusRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeDisksFullStatusResponse
-     */
     describeDisksFullStatusWithOptions(request: DescribeDisksFullStatusRequest, runtime: $Util.RuntimeOptions): Promise<DescribeDisksFullStatusResponse>;
-    /**
-      * *   The full status information of an EBS device includes the lifecycle status provided by the `Status` parameter, health status provided by the `HealthStatus` parameter, and event type provided by the `EventType` parameter of the EBS device. You can filter the results based on these parameters.
-      * *   The release time, scheduled execution time, and actual execution time of each EBS device event are identical. If you specify a period of time by using the `EventTime.Start` and `EventTime.End` parameters, all events that occurred within this period are queried. You can query events that occurred within the last seven days.
-      *
-      * @param request DescribeDisksFullStatusRequest
-      * @return DescribeDisksFullStatusResponse
-     */
     describeDisksFullStatus(request: DescribeDisksFullStatusRequest): Promise<DescribeDisksFullStatusResponse>;
     /**
       * @deprecated
@@ -30676,7 +30725,7 @@ export default class Client extends OpenApi {
      */
     describeEipMonitorData(request: DescribeEipMonitorDataRequest): Promise<DescribeEipMonitorDataResponse>;
     /**
-      * When an elasticity assurance expires, data about the association between instances and the private pool generated by the elasticity assurance becomes invalid. If you call this operation to query the expired elasticity assurance, no value is returned.
+      * When an elasticity assurance expires, data about the association between instances and the private pool generated by the elasticity assurance becomes invalid. When you call this operation to query the expired elasticity assurance, no value is returned.
       *
       * @param request DescribeElasticityAssuranceInstancesRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -30684,7 +30733,7 @@ export default class Client extends OpenApi {
      */
     describeElasticityAssuranceInstancesWithOptions(request: DescribeElasticityAssuranceInstancesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeElasticityAssuranceInstancesResponse>;
     /**
-      * When an elasticity assurance expires, data about the association between instances and the private pool generated by the elasticity assurance becomes invalid. If you call this operation to query the expired elasticity assurance, no value is returned.
+      * When an elasticity assurance expires, data about the association between instances and the private pool generated by the elasticity assurance becomes invalid. When you call this operation to query the expired elasticity assurance, no value is returned.
       *
       * @param request DescribeElasticityAssuranceInstancesRequest
       * @return DescribeElasticityAssuranceInstancesResponse
@@ -30692,7 +30741,26 @@ export default class Client extends OpenApi {
     describeElasticityAssuranceInstances(request: DescribeElasticityAssuranceInstancesRequest): Promise<DescribeElasticityAssuranceInstancesResponse>;
     describeElasticityAssurancesWithOptions(request: DescribeElasticityAssurancesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeElasticityAssurancesResponse>;
     describeElasticityAssurances(request: DescribeElasticityAssurancesRequest): Promise<DescribeElasticityAssurancesResponse>;
+    /**
+      * ## Description
+      * The monitored data includes traffic sent and received over the internal network, the number of packets sent and received by the secondary ENI, and the number of dropped packets sent and received by the secondary ENI. Specific information may be missing from the returned monitored data. This is because the system cannot obtain the relevant information. For example, if the instance to which the secondary ENI is bound is in the Stopped state, or if the secondary ENI is not bound to an instance and is in the Available state, the monitored data of the secondary ENI cannot be obtained. When you call this operation, take note of the following items:
+      * *   Up to 400 monitored data entries can be returned at a time. If the value calculated by using the (EndTime - StartTime)/Period formula is greater than 400, an error is returned.
+      * *   Only the monitored data within the last 30 days can be queried. If the value of the StartTime parameter is earlier than 30 days from the time when you call this operation, an error is returned.
+      *
+      * @param request DescribeEniMonitorDataRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return DescribeEniMonitorDataResponse
+     */
     describeEniMonitorDataWithOptions(request: DescribeEniMonitorDataRequest, runtime: $Util.RuntimeOptions): Promise<DescribeEniMonitorDataResponse>;
+    /**
+      * ## Description
+      * The monitored data includes traffic sent and received over the internal network, the number of packets sent and received by the secondary ENI, and the number of dropped packets sent and received by the secondary ENI. Specific information may be missing from the returned monitored data. This is because the system cannot obtain the relevant information. For example, if the instance to which the secondary ENI is bound is in the Stopped state, or if the secondary ENI is not bound to an instance and is in the Available state, the monitored data of the secondary ENI cannot be obtained. When you call this operation, take note of the following items:
+      * *   Up to 400 monitored data entries can be returned at a time. If the value calculated by using the (EndTime - StartTime)/Period formula is greater than 400, an error is returned.
+      * *   Only the monitored data within the last 30 days can be queried. If the value of the StartTime parameter is earlier than 30 days from the time when you call this operation, an error is returned.
+      *
+      * @param request DescribeEniMonitorDataRequest
+      * @return DescribeEniMonitorDataResponse
+     */
     describeEniMonitorData(request: DescribeEniMonitorDataRequest): Promise<DescribeEniMonitorDataResponse>;
     /**
       * @deprecated
@@ -30779,29 +30847,17 @@ export default class Client extends OpenApi {
       * @return DescribeImagePipelineExecutionsResponse
      */
     describeImagePipelineExecutions(request: DescribeImagePipelineExecutionsRequest): Promise<DescribeImagePipelineExecutionsResponse>;
-    /**
-      * You can use `NextToken` to configure the query token. Set the value to the `NextToken` value that is returned in the last call to the `DescribeImagePipelines` operation. Then, use `MaxResults` to specify the maximum number of entries to return on each page.
-      *
-      * @param request DescribeImagePipelinesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeImagePipelinesResponse
-     */
     describeImagePipelinesWithOptions(request: DescribeImagePipelinesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeImagePipelinesResponse>;
-    /**
-      * You can use `NextToken` to configure the query token. Set the value to the `NextToken` value that is returned in the last call to the `DescribeImagePipelines` operation. Then, use `MaxResults` to specify the maximum number of entries to return on each page.
-      *
-      * @param request DescribeImagePipelinesRequest
-      * @return DescribeImagePipelinesResponse
-     */
     describeImagePipelines(request: DescribeImagePipelinesRequest): Promise<DescribeImagePipelinesResponse>;
     describeImageSharePermissionWithOptions(request: DescribeImageSharePermissionRequest, runtime: $Util.RuntimeOptions): Promise<DescribeImageSharePermissionResponse>;
     describeImageSharePermission(request: DescribeImageSharePermissionRequest): Promise<DescribeImageSharePermissionResponse>;
     describeImageSupportInstanceTypesWithOptions(request: DescribeImageSupportInstanceTypesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeImageSupportInstanceTypesResponse>;
     describeImageSupportInstanceTypes(request: DescribeImageSupportInstanceTypesRequest): Promise<DescribeImageSupportInstanceTypesResponse>;
     /**
-      * * You can query your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images from other Alibaba Cloud accounts.
-      * * This operation supports paged query. The response contains the total number of available images and the images on the returned page. By default, ten entries are displayed on each page.
-      * * When you call an API operation by using Alibaba Cloud CLI, you must specify request parameter values of different data types in the required formats. For more information, see [Parameter format overview](~~110340~~).
+      * ## Description
+      * *   You can query public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, custom images in your repository, and shared images from other Alibaba Cloud accounts.
+      * *   This is a paginated query. The response contains the total number of available images and the images on the returned page. By default, 10 entries are displayed on each page.
+      * *   When you call an API operation by using Alibaba Cloud CLI, you must specify request parameter values of different data types in required formats. For more information, see [Parameter format overview](~~110340~~).
       *
       * @param request DescribeImagesRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -30809,9 +30865,10 @@ export default class Client extends OpenApi {
      */
     describeImagesWithOptions(request: DescribeImagesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeImagesResponse>;
     /**
-      * * You can query your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images from other Alibaba Cloud accounts.
-      * * This operation supports paged query. The response contains the total number of available images and the images on the returned page. By default, ten entries are displayed on each page.
-      * * When you call an API operation by using Alibaba Cloud CLI, you must specify request parameter values of different data types in the required formats. For more information, see [Parameter format overview](~~110340~~).
+      * ## Description
+      * *   You can query public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, custom images in your repository, and shared images from other Alibaba Cloud accounts.
+      * *   This is a paginated query. The response contains the total number of available images and the images on the returned page. By default, 10 entries are displayed on each page.
+      * *   When you call an API operation by using Alibaba Cloud CLI, you must specify request parameter values of different data types in required formats. For more information, see [Parameter format overview](~~110340~~).
       *
       * @param request DescribeImagesRequest
       * @return DescribeImagesResponse
@@ -30834,20 +30891,7 @@ export default class Client extends OpenApi {
       * @return DescribeInstanceAttachmentAttributesResponse
      */
     describeInstanceAttachmentAttributes(request: DescribeInstanceAttachmentAttributesRequest): Promise<DescribeInstanceAttachmentAttributesResponse>;
-    /**
-      * @deprecated
-      *
-      * @param request DescribeInstanceAttributeRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeInstanceAttributeResponse
-     */
     describeInstanceAttributeWithOptions(request: DescribeInstanceAttributeRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInstanceAttributeResponse>;
-    /**
-      * @deprecated
-      *
-      * @param request DescribeInstanceAttributeRequest
-      * @return DescribeInstanceAttributeResponse
-     */
     describeInstanceAttribute(request: DescribeInstanceAttributeRequest): Promise<DescribeInstanceAttributeResponse>;
     /**
       * *   Before you configure auto-renewal or manual renewal for subscription instances, you can query the auto-renewal status of the instances.
@@ -30867,6 +30911,7 @@ export default class Client extends OpenApi {
      */
     describeInstanceAutoRenewAttribute(request: DescribeInstanceAutoRenewAttributeRequest): Promise<DescribeInstanceAutoRenewAttributeResponse>;
     /**
+      * ## Description
       * *   You can query system events that were finished within the last 30 days. The time range for querying unfinished system events is unlimited.
       * *   You can also specify the InstanceEventCycleStatus.N parameter to query the system events that are in the Scheduled, Executing, or Inquiring state.
       *
@@ -30876,6 +30921,7 @@ export default class Client extends OpenApi {
      */
     describeInstanceHistoryEventsWithOptions(request: DescribeInstanceHistoryEventsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInstanceHistoryEventsResponse>;
     /**
+      * ## Description
       * *   You can query system events that were finished within the last 30 days. The time range for querying unfinished system events is unlimited.
       * *   You can also specify the InstanceEventCycleStatus.N parameter to query the system events that are in the Scheduled, Executing, or Inquiring state.
       *
@@ -30886,7 +30932,7 @@ export default class Client extends OpenApi {
     /**
       * This operation is used to query the specified maintenance policy of an instance, which contains the following maintenance attributes:
       * *   Maintenance window: the time period that you specify for maintenance.
-      * *   Maintenance action: the action that you specify in response to instance shutdown.
+      * *   Maintenance action: the policy that you specify in response to instance shutdown.
       *
       * @param request DescribeInstanceMaintenanceAttributesRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -30896,7 +30942,7 @@ export default class Client extends OpenApi {
     /**
       * This operation is used to query the specified maintenance policy of an instance, which contains the following maintenance attributes:
       * *   Maintenance window: the time period that you specify for maintenance.
-      * *   Maintenance action: the action that you specify in response to instance shutdown.
+      * *   Maintenance action: the policy that you specify in response to instance shutdown.
       *
       * @param request DescribeInstanceMaintenanceAttributesRequest
       * @return DescribeInstanceMaintenanceAttributesResponse
@@ -30959,22 +31005,7 @@ export default class Client extends OpenApi {
       * @return DescribeInstanceRamRoleResponse
      */
     describeInstanceRamRole(request: DescribeInstanceRamRoleRequest): Promise<DescribeInstanceRamRoleResponse>;
-    /**
-      * * For information about the lifecycle states of an ECS instance, see [Instance states](~~25687~~).
-      * * You can also call this operation to query the list of ECS instances.
-      *
-      * @param request DescribeInstanceStatusRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeInstanceStatusResponse
-     */
     describeInstanceStatusWithOptions(request: DescribeInstanceStatusRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInstanceStatusResponse>;
-    /**
-      * * For information about the lifecycle states of an ECS instance, see [Instance states](~~25687~~).
-      * * You can also call this operation to query the list of ECS instances.
-      *
-      * @param request DescribeInstanceStatusRequest
-      * @return DescribeInstanceStatusResponse
-     */
     describeInstanceStatus(request: DescribeInstanceStatusRequest): Promise<DescribeInstanceStatusResponse>;
     /**
       * >  The DescribeInstanceTopology operation is in invitational preview and is not commercially available.
@@ -30993,30 +31024,7 @@ export default class Client extends OpenApi {
     describeInstanceTopology(request: DescribeInstanceTopologyRequest): Promise<DescribeInstanceTopologyResponse>;
     describeInstanceTypeFamiliesWithOptions(request: DescribeInstanceTypeFamiliesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInstanceTypeFamiliesResponse>;
     describeInstanceTypeFamilies(request: DescribeInstanceTypeFamiliesRequest): Promise<DescribeInstanceTypeFamiliesResponse>;
-    /**
-      * ## Description
-      * Before you call this operation, take note of the following items:
-      * *   The MaxResults parameter specifies the maximum number of entries to return on each page. The maximum value of this parameter is changed from 1600 to 100. If you called this operation in 2022, you can continue to use 1600 as the maximum value of MaxResults until November 15, 2023. As of November 15, 2023, only 100 can be used as the maximum value of MaxResults. If you do not specify the NextToken parameter when you call the DescribeInstanceTypes operation, only the first page of results that contains up to 100 entries is returned. If you want to retrieve more results, specify the NextToken parameter to perform paged queries, or specify filter conditions to filter results. For information about the best practices for using DescribeInstanceTypes, see [Compare the specifications of instance types](https://help.aliyun.com/practice_detail/461278) .
-      * *   We recommend that you specify the MaxResults and NextToken parameters to perform paged queries. The first time you call the DescribeInstanceTypes operation, specify MaxResults to limit the maximum number of entries to return in the call. If the number of entries to return exceeds the specified value of MaxResults, the response includes a NextToken value. You can set NextToken to the return value and specify MaxResults in your next request to DescribeInstanceTypes to retrieve the next page of results.
-      * *   The DescribeInstanceTypes operation is used to query only the specifications and performance information of instance types. To query instance types that are available in a specific region, call the [DescribeAvailableResource](~~66186~~) operation.
-      * *   To use special instance types such as instance types that are unavailable for purchase, [submit a ticket](https://selfservice.console.aliyun.com/ticket/createIndex.htm).
-      *
-      * @param request DescribeInstanceTypesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeInstanceTypesResponse
-     */
     describeInstanceTypesWithOptions(request: DescribeInstanceTypesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInstanceTypesResponse>;
-    /**
-      * ## Description
-      * Before you call this operation, take note of the following items:
-      * *   The MaxResults parameter specifies the maximum number of entries to return on each page. The maximum value of this parameter is changed from 1600 to 100. If you called this operation in 2022, you can continue to use 1600 as the maximum value of MaxResults until November 15, 2023. As of November 15, 2023, only 100 can be used as the maximum value of MaxResults. If you do not specify the NextToken parameter when you call the DescribeInstanceTypes operation, only the first page of results that contains up to 100 entries is returned. If you want to retrieve more results, specify the NextToken parameter to perform paged queries, or specify filter conditions to filter results. For information about the best practices for using DescribeInstanceTypes, see [Compare the specifications of instance types](https://help.aliyun.com/practice_detail/461278) .
-      * *   We recommend that you specify the MaxResults and NextToken parameters to perform paged queries. The first time you call the DescribeInstanceTypes operation, specify MaxResults to limit the maximum number of entries to return in the call. If the number of entries to return exceeds the specified value of MaxResults, the response includes a NextToken value. You can set NextToken to the return value and specify MaxResults in your next request to DescribeInstanceTypes to retrieve the next page of results.
-      * *   The DescribeInstanceTypes operation is used to query only the specifications and performance information of instance types. To query instance types that are available in a specific region, call the [DescribeAvailableResource](~~66186~~) operation.
-      * *   To use special instance types such as instance types that are unavailable for purchase, [submit a ticket](https://selfservice.console.aliyun.com/ticket/createIndex.htm).
-      *
-      * @param request DescribeInstanceTypesRequest
-      * @return DescribeInstanceTypesResponse
-     */
     describeInstanceTypes(request: DescribeInstanceTypesRequest): Promise<DescribeInstanceTypesResponse>;
     /**
       * @deprecated
@@ -31033,7 +31041,50 @@ export default class Client extends OpenApi {
       * @return DescribeInstanceVncPasswdResponse
      */
     describeInstanceVncPasswd(request: DescribeInstanceVncPasswdRequest): Promise<DescribeInstanceVncPasswdResponse>;
+    /**
+      * When you call this operation, take note of the following items:
+      * *   The URL returned is valid only for 15 seconds. If a connection is not established within 15 seconds after a successful query, the URL expires and you must query it again.
+      * *   The **KeepAlive** time of a connection to a VNC management terminal is 60 seconds. If you do not interact with the VNC management terminal within 60 seconds, the VNC management terminal is automatically disconnected.
+      * *   When the VNC management terminal is disconnected, you can only reconnect to the VNC management terminal up to 30 times a minute.
+      * *   You need to add `vncUrl`, `instanceId`, `isWindows`, and `password` parameters at the end of the URL `https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.8/index.html?`. Separate each parameter with an ampersand (`&`).`` Where,
+      *     *   `vncUrl:` the `VncUrl` value returned after a successful query.
+      *     *   `instanceId:` the ID of your instance.
+      *     *   `isWindows:` specifies whether the operating system of the instance is Windows. Set the parameter to `true` if the operating system is Windows. Set the parameter to `false` if the operating system is not Windows.
+      *     *   `password:` Optional. A six-character password used to connect to the VNC management terminal. It can contain digits and letters. You do not need to enter your password again when the connection is being established if you set this parameter.
+      *         Example:
+      *         ```
+      *         ```
+      * <https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.8/index.html?vncUrl=ws%3A%2F%\\\\*\\\\*\\\\*\\\\*&instanceId=i-wz9hhwq5a6tm\\\\*\\\\*\\\\*\\\\*&isWindows=true> \\`\\`\\`
+      *     or:
+      *         ```
+      * <https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.8/index.html?vncUrl=ws%3A%2F%\\\\*\\\\*\\\\*\\\\*&instanceId=i-wz9hhwq5a6tm\\\\*\\\\*\\\\*\\\\*&isWindows=true&password=\\\\*\\\\*\\\\*\\\\>\\* \\`\\`\\`
+      *
+      * @param request DescribeInstanceVncUrlRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return DescribeInstanceVncUrlResponse
+     */
     describeInstanceVncUrlWithOptions(request: DescribeInstanceVncUrlRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInstanceVncUrlResponse>;
+    /**
+      * When you call this operation, take note of the following items:
+      * *   The URL returned is valid only for 15 seconds. If a connection is not established within 15 seconds after a successful query, the URL expires and you must query it again.
+      * *   The **KeepAlive** time of a connection to a VNC management terminal is 60 seconds. If you do not interact with the VNC management terminal within 60 seconds, the VNC management terminal is automatically disconnected.
+      * *   When the VNC management terminal is disconnected, you can only reconnect to the VNC management terminal up to 30 times a minute.
+      * *   You need to add `vncUrl`, `instanceId`, `isWindows`, and `password` parameters at the end of the URL `https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.8/index.html?`. Separate each parameter with an ampersand (`&`).`` Where,
+      *     *   `vncUrl:` the `VncUrl` value returned after a successful query.
+      *     *   `instanceId:` the ID of your instance.
+      *     *   `isWindows:` specifies whether the operating system of the instance is Windows. Set the parameter to `true` if the operating system is Windows. Set the parameter to `false` if the operating system is not Windows.
+      *     *   `password:` Optional. A six-character password used to connect to the VNC management terminal. It can contain digits and letters. You do not need to enter your password again when the connection is being established if you set this parameter.
+      *         Example:
+      *         ```
+      *         ```
+      * <https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.8/index.html?vncUrl=ws%3A%2F%\\\\*\\\\*\\\\*\\\\*&instanceId=i-wz9hhwq5a6tm\\\\*\\\\*\\\\*\\\\*&isWindows=true> \\`\\`\\`
+      *     or:
+      *         ```
+      * <https://g.alicdn.com/aliyun/ecs-console-vnc2/0.0.8/index.html?vncUrl=ws%3A%2F%\\\\*\\\\*\\\\*\\\\*&instanceId=i-wz9hhwq5a6tm\\\\*\\\\*\\\\*\\\\*&isWindows=true&password=\\\\*\\\\*\\\\*\\\\>\\* \\`\\`\\`
+      *
+      * @param request DescribeInstanceVncUrlRequest
+      * @return DescribeInstanceVncUrlResponse
+     */
     describeInstanceVncUrl(request: DescribeInstanceVncUrlRequest): Promise<DescribeInstanceVncUrlResponse>;
     /**
       * * You can specify multiple request parameters to be queried. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions. However, if InstanceIds is set to an empty JSON array, it is regarded as a valid filter condition and an empty result is returned.
@@ -31062,26 +31113,24 @@ export default class Client extends OpenApi {
       * @return DescribeInstancesResponse
      */
     describeInstances(request: DescribeInstancesRequest): Promise<DescribeInstancesResponse>;
-    describeInstancesFullStatusWithOptions(request: DescribeInstancesFullStatusRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInstancesFullStatusResponse>;
-    describeInstancesFullStatus(request: DescribeInstancesFullStatusRequest): Promise<DescribeInstancesFullStatusResponse>;
     /**
-      * ## Description
-      * *   After you run a command, the command may not succeed or return the expected results. You can call this operation to query the actual execution results.
-      * *   You can query the information about command executions within the last four weeks. A maximum of 100,000 pieces of execution information can be retained.
+      * The response includes instance states and instance system events in the Scheduled state.
+      * If a period is specified, events are queried based on the specified period.
       *
-      * @param request DescribeInvocationResultsRequest
+      * @param request DescribeInstancesFullStatusRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeInvocationResultsResponse
+      * @return DescribeInstancesFullStatusResponse
      */
-    describeInvocationResultsWithOptions(request: DescribeInvocationResultsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInvocationResultsResponse>;
+    describeInstancesFullStatusWithOptions(request: DescribeInstancesFullStatusRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInstancesFullStatusResponse>;
     /**
-      * ## Description
-      * *   After you run a command, the command may not succeed or return the expected results. You can call this operation to query the actual execution results.
-      * *   You can query the information about command executions within the last four weeks. A maximum of 100,000 pieces of execution information can be retained.
+      * The response includes instance states and instance system events in the Scheduled state.
+      * If a period is specified, events are queried based on the specified period.
       *
-      * @param request DescribeInvocationResultsRequest
-      * @return DescribeInvocationResultsResponse
+      * @param request DescribeInstancesFullStatusRequest
+      * @return DescribeInstancesFullStatusResponse
      */
+    describeInstancesFullStatus(request: DescribeInstancesFullStatusRequest): Promise<DescribeInstancesFullStatusResponse>;
+    describeInvocationResultsWithOptions(request: DescribeInvocationResultsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeInvocationResultsResponse>;
     describeInvocationResults(request: DescribeInvocationResultsRequest): Promise<DescribeInvocationResultsResponse>;
     /**
       * *   After you run a command, the command may not succeed or return the expected results. You can call this operation to query the execution results.
@@ -31142,29 +31191,14 @@ export default class Client extends OpenApi {
     describeNetworkInterfaceAttribute(request: DescribeNetworkInterfaceAttributeRequest): Promise<DescribeNetworkInterfaceAttributeResponse>;
     describeNetworkInterfacePermissionsWithOptions(request: DescribeNetworkInterfacePermissionsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeNetworkInterfacePermissionsResponse>;
     describeNetworkInterfacePermissions(request: DescribeNetworkInterfacePermissionsRequest): Promise<DescribeNetworkInterfacePermissionsResponse>;
+    describeNetworkInterfacesWithOptions(request: DescribeNetworkInterfacesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeNetworkInterfacesResponse>;
+    describeNetworkInterfaces(request: DescribeNetworkInterfacesRequest): Promise<DescribeNetworkInterfacesResponse>;
     /**
-      * The `DescribeNetworkInterfaces` operation supports multiple pagination mechanisms. We recommend that you set `MaxResults` to specify the maximum number of entries to return in each request. The returned value of `NextToken` is a pagination token, which can be used in the next request to retrieve a new page of results. When you perform the next request, 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.
-      * > If you specify `MaxResults` or `NextToken`, the system returns results based on the preceding pagination mechanism. Otherwise, the system paginates the results based on the `PageNumber` and `PageSize` parameters.
+      * @deprecated
       *
-      * @param request DescribeNetworkInterfacesRequest
+      * @param request DescribeNewProjectEipMonitorDataRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeNetworkInterfacesResponse
-     */
-    describeNetworkInterfacesWithOptions(request: DescribeNetworkInterfacesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeNetworkInterfacesResponse>;
-    /**
-      * The `DescribeNetworkInterfaces` operation supports multiple pagination mechanisms. We recommend that you set `MaxResults` to specify the maximum number of entries to return in each request. The returned value of `NextToken` is a pagination token, which can be used in the next request to retrieve a new page of results. When you perform the next request, 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.
-      * > If you specify `MaxResults` or `NextToken`, the system returns results based on the preceding pagination mechanism. Otherwise, the system paginates the results based on the `PageNumber` and `PageSize` parameters.
-      *
-      * @param request DescribeNetworkInterfacesRequest
-      * @return DescribeNetworkInterfacesResponse
-     */
-    describeNetworkInterfaces(request: DescribeNetworkInterfacesRequest): Promise<DescribeNetworkInterfacesResponse>;
-    /**
-      * @deprecated
-      *
-      * @param request DescribeNewProjectEipMonitorDataRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeNewProjectEipMonitorDataResponse
+      * @return DescribeNewProjectEipMonitorDataResponse
      */
     describeNewProjectEipMonitorDataWithOptions(request: DescribeNewProjectEipMonitorDataRequest, runtime: $Util.RuntimeOptions): Promise<DescribeNewProjectEipMonitorDataResponse>;
     /**
@@ -31193,22 +31227,7 @@ export default class Client extends OpenApi {
     describePrefixListAssociations(request: DescribePrefixListAssociationsRequest): Promise<DescribePrefixListAssociationsResponse>;
     describePrefixListAttributesWithOptions(request: DescribePrefixListAttributesRequest, runtime: $Util.RuntimeOptions): Promise<DescribePrefixListAttributesResponse>;
     describePrefixListAttributes(request: DescribePrefixListAttributesRequest): Promise<DescribePrefixListAttributesResponse>;
-    /**
-      * ## Description
-      * You can specify the `AddressFamily`, `PrefixListId.N`, and `PrefixListName` request parameters to be queried. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
-      *
-      * @param request DescribePrefixListsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribePrefixListsResponse
-     */
     describePrefixListsWithOptions(request: DescribePrefixListsRequest, runtime: $Util.RuntimeOptions): Promise<DescribePrefixListsResponse>;
-    /**
-      * ## Description
-      * You can specify the `AddressFamily`, `PrefixListId.N`, and `PrefixListName` request parameters to be queried. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
-      *
-      * @param request DescribePrefixListsRequest
-      * @return DescribePrefixListsResponse
-     */
     describePrefixLists(request: DescribePrefixListsRequest): Promise<DescribePrefixListsResponse>;
     describePriceWithOptions(request: DescribePriceRequest, runtime: $Util.RuntimeOptions): Promise<DescribePriceResponse>;
     describePrice(request: DescribePriceRequest): Promise<DescribePriceResponse>;
@@ -31229,28 +31248,7 @@ export default class Client extends OpenApi {
       * @return DescribeRegionsResponse
      */
     describeRegions(request: DescribeRegionsRequest): Promise<DescribeRegionsResponse>;
-    /**
-      * ## Description
-      * *   You can call this operation to query the price for renewing a subscription instance for a specific period of time or to a synchronized expiration date.
-      * *   Take note of the following items:
-      *     *   If you set only the required parameters, the price for renewing a specified instance for one month is queried by default.
-      *     *   The renewal period-related parameter pair (`Period` and `PeriodUnit`) and the synchronized expiration date-related parameter (`ExpectedRenewDay`) are mutually exclusive. You cannot set these parameters together to query the prices for renewing a specified instance for a period of time and to a synchronized expiration date at the same time.
-      *
-      * @param request DescribeRenewalPriceRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeRenewalPriceResponse
-     */
     describeRenewalPriceWithOptions(request: DescribeRenewalPriceRequest, runtime: $Util.RuntimeOptions): Promise<DescribeRenewalPriceResponse>;
-    /**
-      * ## Description
-      * *   You can call this operation to query the price for renewing a subscription instance for a specific period of time or to a synchronized expiration date.
-      * *   Take note of the following items:
-      *     *   If you set only the required parameters, the price for renewing a specified instance for one month is queried by default.
-      *     *   The renewal period-related parameter pair (`Period` and `PeriodUnit`) and the synchronized expiration date-related parameter (`ExpectedRenewDay`) are mutually exclusive. You cannot set these parameters together to query the prices for renewing a specified instance for a period of time and to a synchronized expiration date at the same time.
-      *
-      * @param request DescribeRenewalPriceRequest
-      * @return DescribeRenewalPriceResponse
-     */
     describeRenewalPrice(request: DescribeRenewalPriceRequest): Promise<DescribeRenewalPriceResponse>;
     describeReservedInstanceAutoRenewAttributeWithOptions(request: DescribeReservedInstanceAutoRenewAttributeRequest, runtime: $Util.RuntimeOptions): Promise<DescribeReservedInstanceAutoRenewAttributeResponse>;
     describeReservedInstanceAutoRenewAttribute(request: DescribeReservedInstanceAutoRenewAttributeRequest): Promise<DescribeReservedInstanceAutoRenewAttributeResponse>;
@@ -31315,9 +31313,9 @@ export default class Client extends OpenApi {
     describeSecurityGroupReferences(request: DescribeSecurityGroupReferencesRequest): Promise<DescribeSecurityGroupReferencesResponse>;
     /**
       * Before you call this operation, take note of the following items:
-      * *   The basic information of security groups includes their IDs and descriptions. In the response, security groups are displayed in descending order of their IDs.
-      * *   We recommend that you use the NextToken and MaxResults parameters for a paged query. During a paged query, when you call the DescribeSecurityGroups 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, which can be used in the next call to retrieve a new page of results. When you call the DescribeSecurityGroups 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. If the return value of NextToken is empty, the current page of results is the last page and no more results are to be returned.
-      * *   When you use Alibaba Cloud CLI to call an API operation, you must specify request parameter values of different data types in required formats. For more information, see [Parameter format overview](~~110340~~).
+      * *   The basic information of security groups includes the IDs and descriptions. The response returns security groups in descending order based on their IDs.
+      * *   We recommend that you use the NextToken and MaxResults parameters for a paged query. We recommend that you use the MaxResults parameter to specify the maximum number of entries to return in each request. The returned value of NextToken is a pagination token, which can be used in the next request to retrieve a new page of results. When you perform the next request, set the NextToken parameter to the NextToken value that is returned in the previous call and use the MaxResults parameter to specify the maximum number of entries to return in this request. If the returned value of the NextToken parameter is empty, the current page of results is the last page and no more results are to be returned.
+      * *   When you use Alibaba Cloud CLI to call an API operation, you must specify request parameter values of different data types in the required formats. For more information, see [Parameter format overview](~~110340~~).
       *
       * @param request DescribeSecurityGroupsRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -31326,9 +31324,9 @@ export default class Client extends OpenApi {
     describeSecurityGroupsWithOptions(request: DescribeSecurityGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeSecurityGroupsResponse>;
     /**
       * Before you call this operation, take note of the following items:
-      * *   The basic information of security groups includes their IDs and descriptions. In the response, security groups are displayed in descending order of their IDs.
-      * *   We recommend that you use the NextToken and MaxResults parameters for a paged query. During a paged query, when you call the DescribeSecurityGroups 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, which can be used in the next call to retrieve a new page of results. When you call the DescribeSecurityGroups 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. If the return value of NextToken is empty, the current page of results is the last page and no more results are to be returned.
-      * *   When you use Alibaba Cloud CLI to call an API operation, you must specify request parameter values of different data types in required formats. For more information, see [Parameter format overview](~~110340~~).
+      * *   The basic information of security groups includes the IDs and descriptions. The response returns security groups in descending order based on their IDs.
+      * *   We recommend that you use the NextToken and MaxResults parameters for a paged query. We recommend that you use the MaxResults parameter to specify the maximum number of entries to return in each request. The returned value of NextToken is a pagination token, which can be used in the next request to retrieve a new page of results. When you perform the next request, set the NextToken parameter to the NextToken value that is returned in the previous call and use the MaxResults parameter to specify the maximum number of entries to return in this request. If the returned value of the NextToken parameter is empty, the current page of results is the last page and no more results are to be returned.
+      * *   When you use Alibaba Cloud CLI to call an API operation, you must specify request parameter values of different data types in the required formats. For more information, see [Parameter format overview](~~110340~~).
       *
       * @param request DescribeSecurityGroupsRequest
       * @return DescribeSecurityGroupsResponse
@@ -31354,7 +31352,6 @@ export default class Client extends OpenApi {
      */
     describeSendFileResults(request: DescribeSendFileResultsRequest): Promise<DescribeSendFileResultsResponse>;
     /**
-      * ## Description
       * You can specify multiple request parameters such as `InstanceId`, `SnapshotGroupId.N`, and `Status.N` to be queried. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
       *
       * @param request DescribeSnapshotGroupsRequest
@@ -31363,31 +31360,13 @@ export default class Client extends OpenApi {
      */
     describeSnapshotGroupsWithOptions(request: DescribeSnapshotGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeSnapshotGroupsResponse>;
     /**
-      * ## Description
       * You can specify multiple request parameters such as `InstanceId`, `SnapshotGroupId.N`, and `Status.N` to be queried. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
       *
       * @param request DescribeSnapshotGroupsRequest
       * @return DescribeSnapshotGroupsResponse
      */
     describeSnapshotGroups(request: DescribeSnapshotGroupsRequest): Promise<DescribeSnapshotGroupsResponse>;
-    /**
-      * When you call this operation, take note of the following items:
-      * *   You can specify multiple request parameters such as `RegionId`, `DiskIds`, and `InstanceId` to be queried. Specified parameters have logical AND relations.
-      * *   Only the specified parameters are used as filter conditions. If the `DiskIds` and `SnapshotLinkIds` parameters are set to empty JSON arrays, they are regarded as valid filter conditions and an empty result is returned.
-      *
-      * @param request DescribeSnapshotLinksRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeSnapshotLinksResponse
-     */
     describeSnapshotLinksWithOptions(request: DescribeSnapshotLinksRequest, runtime: $Util.RuntimeOptions): Promise<DescribeSnapshotLinksResponse>;
-    /**
-      * When you call this operation, take note of the following items:
-      * *   You can specify multiple request parameters such as `RegionId`, `DiskIds`, and `InstanceId` to be queried. Specified parameters have logical AND relations.
-      * *   Only the specified parameters are used as filter conditions. If the `DiskIds` and `SnapshotLinkIds` parameters are set to empty JSON arrays, they are regarded as valid filter conditions and an empty result is returned.
-      *
-      * @param request DescribeSnapshotLinksRequest
-      * @return DescribeSnapshotLinksResponse
-     */
     describeSnapshotLinks(request: DescribeSnapshotLinksRequest): Promise<DescribeSnapshotLinksResponse>;
     /**
       * When you call this operation, take note of the following items:
@@ -31411,6 +31390,7 @@ export default class Client extends OpenApi {
     describeSnapshotPackageWithOptions(request: DescribeSnapshotPackageRequest, runtime: $Util.RuntimeOptions): Promise<DescribeSnapshotPackageResponse>;
     describeSnapshotPackage(request: DescribeSnapshotPackageRequest): Promise<DescribeSnapshotPackageResponse>;
     /**
+      * ## Description
       * You can specify multiple request parameters such as `InstanceId`, `DiskId`, and `SnapshotIds` to be queried. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
       * When you use Alibaba Cloud CLI to call an API operation, you must specify request parameter values of different data types in required formats. For more information, see [Parameter format overview](~~110340~~).
       *
@@ -31420,6 +31400,7 @@ export default class Client extends OpenApi {
      */
     describeSnapshotsWithOptions(request: DescribeSnapshotsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeSnapshotsResponse>;
     /**
+      * ## Description
       * You can specify multiple request parameters such as `InstanceId`, `DiskId`, and `SnapshotIds` to be queried. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
       * When you use Alibaba Cloud CLI to call an API operation, you must specify request parameter values of different data types in required formats. For more information, see [Parameter format overview](~~110340~~).
       *
@@ -31443,15 +31424,15 @@ export default class Client extends OpenApi {
      */
     describeSnapshotsUsage(request: DescribeSnapshotsUsageRequest): Promise<DescribeSnapshotsUsageResponse>;
     /**
-      * * You can call this operation to query information that is generated for preemptible instances in the last 30 days and select suitable instance types based on the query results. The information that you can query by calling this operation includes:
-      *     * Average release rate of preemptible instances
-      *     * Percentage of the average preemptible instance price relative to the pay-as-you-go instance price
-      *     * Average preemptible instance price that is calculated based on the preceding percentage
-      * * This operation is applicable only to I/O optimized preemptible instances that are located in virtual private clouds (VPCs).
-      * * You can use one of the following methods to query information that is generated for preemptible instances in the last 30 days:
-      *     * Set the `Cores` and `Memory` parameters or the `MinCores` and `MinMemory` parameters to query information about instance types that have the specified number of vCPUs and memory size.
-      *     * Set the `InstanceTypes.N` parameter to query information of the specified instance types.
-      *     * Set the `Cores` and `Memory` parameters or the `MinCores` and `MinMemory` parameters, and set the `InstanceTypeFamily` or `InstanceFamilyLevel` parameter to query information of the instance types that have the specified number of vCPUs and memory size within the specified instance family or at the specified instance family level.
+      * *   You can call this operation to query information that is generated for preemptible instances in the last 30 days and select suitable instance types based on the returned results. The information that you can query by calling this operation includes:
+      *     *   Average release rate of preemptible instances.
+      *     *   The discount rate of the average preemptible instance price relative to the pay-as-you-go instance price.
+      *     *   Average preemptible instance price that is calculated based on the preceding percentage.
+      * *   This operation is applicable only to I/O optimized preemptible instances that are located in virtual private clouds (VPCs).
+      * *   You can use one of the following methods to specify instance types:
+      *     *   Set the `Cores` and `Memory` parameters or the `MinCores` and `MinMemory` parameters to query information of instance types that have the specified number of vCPUs and memory size.
+      *     *   Set the `InstanceTypes.N parameter` to query information of the specified instance types.
+      *     *   Set the `Cores` and `Memory` parameters or the `MinCores` and `MinMemory` parameters, and set the `InstanceTypeFamily` or `InstanceFamilyLevel` parameter to query information of the instance types that have the specified number of vCPUs and memory size within the specified instance family or at the specified instance family level.
       *
       * @param request DescribeSpotAdviceRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -31459,15 +31440,15 @@ export default class Client extends OpenApi {
      */
     describeSpotAdviceWithOptions(request: DescribeSpotAdviceRequest, runtime: $Util.RuntimeOptions): Promise<DescribeSpotAdviceResponse>;
     /**
-      * * You can call this operation to query information that is generated for preemptible instances in the last 30 days and select suitable instance types based on the query results. The information that you can query by calling this operation includes:
-      *     * Average release rate of preemptible instances
-      *     * Percentage of the average preemptible instance price relative to the pay-as-you-go instance price
-      *     * Average preemptible instance price that is calculated based on the preceding percentage
-      * * This operation is applicable only to I/O optimized preemptible instances that are located in virtual private clouds (VPCs).
-      * * You can use one of the following methods to query information that is generated for preemptible instances in the last 30 days:
-      *     * Set the `Cores` and `Memory` parameters or the `MinCores` and `MinMemory` parameters to query information about instance types that have the specified number of vCPUs and memory size.
-      *     * Set the `InstanceTypes.N` parameter to query information of the specified instance types.
-      *     * Set the `Cores` and `Memory` parameters or the `MinCores` and `MinMemory` parameters, and set the `InstanceTypeFamily` or `InstanceFamilyLevel` parameter to query information of the instance types that have the specified number of vCPUs and memory size within the specified instance family or at the specified instance family level.
+      * *   You can call this operation to query information that is generated for preemptible instances in the last 30 days and select suitable instance types based on the returned results. The information that you can query by calling this operation includes:
+      *     *   Average release rate of preemptible instances.
+      *     *   The discount rate of the average preemptible instance price relative to the pay-as-you-go instance price.
+      *     *   Average preemptible instance price that is calculated based on the preceding percentage.
+      * *   This operation is applicable only to I/O optimized preemptible instances that are located in virtual private clouds (VPCs).
+      * *   You can use one of the following methods to specify instance types:
+      *     *   Set the `Cores` and `Memory` parameters or the `MinCores` and `MinMemory` parameters to query information of instance types that have the specified number of vCPUs and memory size.
+      *     *   Set the `InstanceTypes.N parameter` to query information of the specified instance types.
+      *     *   Set the `Cores` and `Memory` parameters or the `MinCores` and `MinMemory` parameters, and set the `InstanceTypeFamily` or `InstanceFamilyLevel` parameter to query information of the instance types that have the specified number of vCPUs and memory size within the specified instance family or at the specified instance family level.
       *
       * @param request DescribeSpotAdviceRequest
       * @return DescribeSpotAdviceResponse
@@ -31481,20 +31462,7 @@ export default class Client extends OpenApi {
     describeStorageSetDetails(request: DescribeStorageSetDetailsRequest): Promise<DescribeStorageSetDetailsResponse>;
     describeStorageSetsWithOptions(request: DescribeStorageSetsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeStorageSetsResponse>;
     describeStorageSets(request: DescribeStorageSetsRequest): Promise<DescribeStorageSetsResponse>;
-    /**
-      * If a tag key is specified and no tag values are specified, all tags that contain the tag key are returned. If a tag key-value pair is specified, only tags that exactly match the key-value pair are returned.
-      *
-      * @param request DescribeTagsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeTagsResponse
-     */
     describeTagsWithOptions(request: DescribeTagsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeTagsResponse>;
-    /**
-      * If a tag key is specified and no tag values are specified, all tags that contain the tag key are returned. If a tag key-value pair is specified, only tags that exactly match the key-value pair are returned.
-      *
-      * @param request DescribeTagsRequest
-      * @return DescribeTagsResponse
-     */
     describeTags(request: DescribeTagsRequest): Promise<DescribeTagsResponse>;
     describeTaskAttributeWithOptions(request: DescribeTaskAttributeRequest, runtime: $Util.RuntimeOptions): Promise<DescribeTaskAttributeResponse>;
     describeTaskAttribute(request: DescribeTaskAttributeRequest): Promise<DescribeTaskAttributeResponse>;
@@ -31609,53 +31577,53 @@ export default class Client extends OpenApi {
       * @return DescribeVpcsResponse
      */
     describeVpcs(request: DescribeVpcsRequest): Promise<DescribeVpcsResponse>;
-    describeZonesWithOptions(request: DescribeZonesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeZonesResponse>;
-    describeZones(request: DescribeZonesRequest): Promise<DescribeZonesResponse>;
-    detachClassicLinkVpcWithOptions(request: DetachClassicLinkVpcRequest, runtime: $Util.RuntimeOptions): Promise<DetachClassicLinkVpcResponse>;
-    detachClassicLinkVpc(request: DetachClassicLinkVpcRequest): Promise<DetachClassicLinkVpcResponse>;
-    detachDiskWithOptions(request: DetachDiskRequest, runtime: $Util.RuntimeOptions): Promise<DetachDiskResponse>;
-    detachDisk(request: DetachDiskRequest): Promise<DetachDiskResponse>;
-    detachInstanceRamRoleWithOptions(request: DetachInstanceRamRoleRequest, runtime: $Util.RuntimeOptions): Promise<DetachInstanceRamRoleResponse>;
-    detachInstanceRamRole(request: DetachInstanceRamRoleRequest): Promise<DetachInstanceRamRoleResponse>;
     /**
-      * When you call this operation, take note of the following items:
-      * *   After you detach an SSH key pair from an instance, you must call the [RebootInstance](~~25502~~) operation to restart the instance for the detach operation to take effect.
-      * *   The username and password authentication method is automatically selected for an instance after you unbind an SSH key pair from the instance.
+      * 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](~~66186~~) operation.
       *
-      * @param request DetachKeyPairRequest
+      * @param request DescribeZonesRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return DetachKeyPairResponse
+      * @return DescribeZonesResponse
      */
-    detachKeyPairWithOptions(request: DetachKeyPairRequest, runtime: $Util.RuntimeOptions): Promise<DetachKeyPairResponse>;
+    describeZonesWithOptions(request: DescribeZonesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeZonesResponse>;
     /**
-      * When you call this operation, take note of the following items:
-      * *   After you detach an SSH key pair from an instance, you must call the [RebootInstance](~~25502~~) operation to restart the instance for the detach operation to take effect.
-      * *   The username and password authentication method is automatically selected for an instance after you unbind an SSH key pair from the instance.
+      * 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](~~66186~~) operation.
       *
-      * @param request DetachKeyPairRequest
-      * @return DetachKeyPairResponse
+      * @param request DescribeZonesRequest
+      * @return DescribeZonesResponse
      */
-    detachKeyPair(request: DetachKeyPairRequest): Promise<DetachKeyPairResponse>;
+    describeZones(request: DescribeZonesRequest): Promise<DescribeZonesResponse>;
+    detachClassicLinkVpcWithOptions(request: DetachClassicLinkVpcRequest, runtime: $Util.RuntimeOptions): Promise<DetachClassicLinkVpcResponse>;
+    detachClassicLinkVpc(request: DetachClassicLinkVpcRequest): Promise<DetachClassicLinkVpcResponse>;
     /**
       * When you call this operation, take note of the following items:
-      * * The primary ENIs of ECS instances cannot be unbound.
-      * * The ENI must be in the Detaching (Detaching) or InUse (InUse) state.
-      * * The instance must be in the Running (Running) or Stopped (Stopped) state.
+      * *   The disk you want to detach must be in the `In_Use` state.
+      * *   The instance from which you want to detach a data disk must be in the `Running` or `Stopped`state.********
+      * *   The instance from which you want to detach the system disk must be in the `Stopped` state.****
+      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}`, the instance is locked for security reasons. No operations are allowed on the instance.``
+      * *   DetachDisk is an asynchronous operation. It takes about one minute for a disk to be detached from an instance after the operation is called.
       *
-      * @param request DetachNetworkInterfaceRequest
+      * @param request DetachDiskRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return DetachNetworkInterfaceResponse
+      * @return DetachDiskResponse
      */
-    detachNetworkInterfaceWithOptions(request: DetachNetworkInterfaceRequest, runtime: $Util.RuntimeOptions): Promise<DetachNetworkInterfaceResponse>;
+    detachDiskWithOptions(request: DetachDiskRequest, runtime: $Util.RuntimeOptions): Promise<DetachDiskResponse>;
     /**
       * When you call this operation, take note of the following items:
-      * * The primary ENIs of ECS instances cannot be unbound.
-      * * The ENI must be in the Detaching (Detaching) or InUse (InUse) state.
-      * * The instance must be in the Running (Running) or Stopped (Stopped) state.
+      * *   The disk you want to detach must be in the `In_Use` state.
+      * *   The instance from which you want to detach a data disk must be in the `Running` or `Stopped`state.********
+      * *   The instance from which you want to detach the system disk must be in the `Stopped` state.****
+      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}`, the instance is locked for security reasons. No operations are allowed on the instance.``
+      * *   DetachDisk is an asynchronous operation. It takes about one minute for a disk to be detached from an instance after the operation is called.
       *
-      * @param request DetachNetworkInterfaceRequest
-      * @return DetachNetworkInterfaceResponse
+      * @param request DetachDiskRequest
+      * @return DetachDiskResponse
      */
+    detachDisk(request: DetachDiskRequest): Promise<DetachDiskResponse>;
+    detachInstanceRamRoleWithOptions(request: DetachInstanceRamRoleRequest, runtime: $Util.RuntimeOptions): Promise<DetachInstanceRamRoleResponse>;
+    detachInstanceRamRole(request: DetachInstanceRamRoleRequest): Promise<DetachInstanceRamRoleResponse>;
+    detachKeyPairWithOptions(request: DetachKeyPairRequest, runtime: $Util.RuntimeOptions): Promise<DetachKeyPairResponse>;
+    detachKeyPair(request: DetachKeyPairRequest): Promise<DetachKeyPairResponse>;
+    detachNetworkInterfaceWithOptions(request: DetachNetworkInterfaceRequest, runtime: $Util.RuntimeOptions): Promise<DetachNetworkInterfaceResponse>;
     detachNetworkInterface(request: DetachNetworkInterfaceRequest): Promise<DetachNetworkInterfaceResponse>;
     disableActivationWithOptions(request: DisableActivationRequest, runtime: $Util.RuntimeOptions): Promise<DisableActivationResponse>;
     disableActivation(request: DisableActivationRequest): Promise<DisableActivationResponse>;
@@ -31719,7 +31687,98 @@ export default class Client extends OpenApi {
       * @return EnablePhysicalConnectionResponse
      */
     enablePhysicalConnection(request: EnablePhysicalConnectionRequest): Promise<EnablePhysicalConnectionResponse>;
+    /**
+      * Before you export a custom image, complete the following operations:
+      * *   Understand the prerequisites and precautions. For more information, see [Export images](~~58181~~).
+      * *   Use Resource Access Management (RAM) to create a RAM role for ECS and grant ECS the permissions to write data to OSS. Perform the following steps:
+      *     1.  Create a role named `AliyunECSImageExportDefaultRole` and configure the following trust policy for the role:
+      *              {
+      *                "Statement": [
+      *                  {
+      *                    "Action": "sts:AssumeRole",
+      *                    "Effect": "Allow",
+      *                    "Principal": {
+      *                      "Service": [
+      *                        "ecs.aliyuncs.com"
+      *                      ]
+      *                    }
+      *                  }
+      *                ],
+      *                "Version": "1"
+      *              }
+      *     2.  Attach the `AliyunECSImageExportRolePolicy` system policy to the `AliyunECSImageExportDefaultRole` role. This policy is the default policy that grants ECS the permissions to export images. For more information, go to the [Cloud Resource Access Authorization](https://ram.console.aliyun.com/?spm=5176.2020520101.0.0.64c64df5dfpmdY#/role/authorize?request=%7B%22Requests%22:%20%7B%22request1%22:%20%7B%22RoleName%22:%20%22AliyunECSImageImportDefaultRole%22,%20%22TemplateId%22:%20%22ECSImportRole%22%7D,%20%22request2%22:%20%7B%22RoleName%22:%20%22AliyunECSImageExportDefaultRole%22,%20%22TemplateId%22:%20%22ECSExportRole%22%7D%7D,%20%22ReturnUrl%22:%20%22https:%2F%2Fecs.console.aliyun.com%2F%22,%20%22Service%22:%20%22ECS%22%7D) page. You can also create a custom policy that contains the following content and attach the policy to the role:
+      *              {
+      *                "Version": "1",
+      *                "Statement": [
+      *                  {
+      *                    "Action": [
+      *                      "oss:GetObject",
+      *                      "oss:PutObject",
+      *                      "oss:DeleteObject",
+      *                      "oss:GetBucketLocation",
+      *                      "oss:GetBucketInfo",
+      *                      "oss:AbortMultipartUpload",
+      *                      "oss:ListMultipartUploads",
+      *                      "oss:ListParts"
+      *                    ],
+      *                    "Resource": "*",
+      *                    "Effect": "Allow"
+      *                  }
+      *                ]
+      *              }
+      * After you export a custom image, the following situation occurs:
+      * The custom image is stored in the specified OSS bucket. You can download the custom image. For more information, see [Download objects](~~31912~~).
+      *
+      * @param request ExportImageRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ExportImageResponse
+     */
     exportImageWithOptions(request: ExportImageRequest, runtime: $Util.RuntimeOptions): Promise<ExportImageResponse>;
+    /**
+      * Before you export a custom image, complete the following operations:
+      * *   Understand the prerequisites and precautions. For more information, see [Export images](~~58181~~).
+      * *   Use Resource Access Management (RAM) to create a RAM role for ECS and grant ECS the permissions to write data to OSS. Perform the following steps:
+      *     1.  Create a role named `AliyunECSImageExportDefaultRole` and configure the following trust policy for the role:
+      *              {
+      *                "Statement": [
+      *                  {
+      *                    "Action": "sts:AssumeRole",
+      *                    "Effect": "Allow",
+      *                    "Principal": {
+      *                      "Service": [
+      *                        "ecs.aliyuncs.com"
+      *                      ]
+      *                    }
+      *                  }
+      *                ],
+      *                "Version": "1"
+      *              }
+      *     2.  Attach the `AliyunECSImageExportRolePolicy` system policy to the `AliyunECSImageExportDefaultRole` role. This policy is the default policy that grants ECS the permissions to export images. For more information, go to the [Cloud Resource Access Authorization](https://ram.console.aliyun.com/?spm=5176.2020520101.0.0.64c64df5dfpmdY#/role/authorize?request=%7B%22Requests%22:%20%7B%22request1%22:%20%7B%22RoleName%22:%20%22AliyunECSImageImportDefaultRole%22,%20%22TemplateId%22:%20%22ECSImportRole%22%7D,%20%22request2%22:%20%7B%22RoleName%22:%20%22AliyunECSImageExportDefaultRole%22,%20%22TemplateId%22:%20%22ECSExportRole%22%7D%7D,%20%22ReturnUrl%22:%20%22https:%2F%2Fecs.console.aliyun.com%2F%22,%20%22Service%22:%20%22ECS%22%7D) page. You can also create a custom policy that contains the following content and attach the policy to the role:
+      *              {
+      *                "Version": "1",
+      *                "Statement": [
+      *                  {
+      *                    "Action": [
+      *                      "oss:GetObject",
+      *                      "oss:PutObject",
+      *                      "oss:DeleteObject",
+      *                      "oss:GetBucketLocation",
+      *                      "oss:GetBucketInfo",
+      *                      "oss:AbortMultipartUpload",
+      *                      "oss:ListMultipartUploads",
+      *                      "oss:ListParts"
+      *                    ],
+      *                    "Resource": "*",
+      *                    "Effect": "Allow"
+      *                  }
+      *                ]
+      *              }
+      * After you export a custom image, the following situation occurs:
+      * The custom image is stored in the specified OSS bucket. You can download the custom image. For more information, see [Download objects](~~31912~~).
+      *
+      * @param request ExportImageRequest
+      * @return ExportImageResponse
+     */
     exportImage(request: ExportImageRequest): Promise<ExportImageResponse>;
     /**
       * @deprecated
@@ -31736,71 +31795,124 @@ export default class Client extends OpenApi {
       * @return ExportSnapshotResponse
      */
     exportSnapshot(request: ExportSnapshotRequest): Promise<ExportSnapshotResponse>;
-    /**
-      * *   ECS is a virtualized cloud-based service and cannot be connected to display devices. However, Alibaba Cloud caches system command outputs for the last start, restart, or shutdown of ECS instances. You can call the GetInstanceConsoleOutput operation to obtain the command outputs.
-      * *   The command outputs of instances that use the retired instance types cannot be obtained. For more information, see [Retired instance types](~~55263~~).
-      * *   The command outputs of Windows instances cannot be obtained.
-      *
-      * @param request GetInstanceConsoleOutputRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return GetInstanceConsoleOutputResponse
-     */
     getInstanceConsoleOutputWithOptions(request: GetInstanceConsoleOutputRequest, runtime: $Util.RuntimeOptions): Promise<GetInstanceConsoleOutputResponse>;
-    /**
-      * *   ECS is a virtualized cloud-based service and cannot be connected to display devices. However, Alibaba Cloud caches system command outputs for the last start, restart, or shutdown of ECS instances. You can call the GetInstanceConsoleOutput operation to obtain the command outputs.
-      * *   The command outputs of instances that use the retired instance types cannot be obtained. For more information, see [Retired instance types](~~55263~~).
-      * *   The command outputs of Windows instances cannot be obtained.
-      *
-      * @param request GetInstanceConsoleOutputRequest
-      * @return GetInstanceConsoleOutputResponse
-     */
     getInstanceConsoleOutput(request: GetInstanceConsoleOutputRequest): Promise<GetInstanceConsoleOutputResponse>;
     getInstanceScreenshotWithOptions(request: GetInstanceScreenshotRequest, runtime: $Util.RuntimeOptions): Promise<GetInstanceScreenshotResponse>;
     getInstanceScreenshot(request: GetInstanceScreenshotRequest): Promise<GetInstanceScreenshotResponse>;
-    importImageWithOptions(request: ImportImageRequest, runtime: $Util.RuntimeOptions): Promise<ImportImageResponse>;
-    importImage(request: ImportImageRequest): Promise<ImportImageResponse>;
     /**
       * When you call this operation, take note of the following items:
-      * * A maximum of 500 key pairs can be created in each region.
-      * * The key pair that you wan to import must support one of the following encryption methods:
-      *     * rsa
-      *     * dsa
-      *     * ssh-rsa
-      *     * ssh-dss
-      *     * ecdsa
-      *     * ssh-rsa-cert-v00@openssh.com
-      *     * ssh-dss-cert-v00@openssh.com
-      *     * ssh-rsa-cert-v01@openssh.com
-      *     * ssh-dss-cert-v01@openssh.com
-      *     * ecdsa-sha2-nistp256-cert-v01@openssh.com
-      *     * ecdsa-sha2-nistp384-cert-v01@openssh.com
-      *     * ecdsa-sha2-nistp521-cert-v01@openssh.com
-      *
-      * @param request ImportKeyPairRequest
+      * *   Before you can import an image, you must upload the image to an Object Storage Service (OSS) bucket. For more information, see [Upload objects](~~31886~~).
+      * *   In some scenarios, you may want to create a custom image from an existing server and create an ECS instance from the image. The source server can be a physical server, a virtual machine, or a cloud host. However, you must make sure that the virtio driver is installed on the source server, otherwise the ECS instance created from the resulting image may be unable to start. For more information, see [Install the virtio driver](~~62423~~).
+      * *   If this is the first time you import images to ECS, you must use Resource Access Management (RAM) to grant ECS the permissions to access your OSS buckets. Otherwise, the `NoSetRoletoECSServiceAcount` error code is returned when you call the ImportImage operation. The [Cloud Resource Access Authorization](https://ram.console.aliyun.com/?spm=5176.2020520101image.0.0.2ffa4df57kSoHX#/role/authorize?request=%7B%22Requests%22%3A%20%7B%22request1%22%3A%20%7B%22RoleName%22%3A%20%22AliyunECSImageImportDefaultRole%22%2C%20%22TemplateId%22%3A%20%22ECSImportRole%22%7D%2C%20%22request2%22%3A%20%7B%22RoleName%22%3A%20%22AliyunECSImageExportDefaultRole%22%2C%20%22TemplateId%22%3A%20%22ECSExportRole%22%7D%7D%2C%20%22ReturnUrl%22%3A%20%22https%3A//ecs.console.aliyun.com/%22%2C%20%22Service%22%3A%20%22ECS%22%7D) page of the RAM console provides a convenient push-button authorization function for this operation. You can also perform the authorization by using a RAM role and RAM policies. The following examples show the policies and permissions required for some steps in the authorization procedure. For more information, see [Control access to resources by using RAM users](~~25481~~).
+      *     1.  Create a role named `AliyunECSImageImportDefaultRole`. You must use this exact name. Otherwise, the image cannot be imported. Configure the following trust policy for the role:
+      *             {
+      *             	"Statement": [
+      *             	{
+      *             		"Action": "sts:AssumeRole",
+      *             		"Effect": "Allow",
+      *             		"Principal": {
+      *             		"Service": [
+      *             			"ecs.aliyuncs.com"
+      *             		]
+      *             		}
+      *             	}
+      *             ],
+      *             	"Version": "1"
+      *             }
+      *     2.  Attach the `AliyunECSImageImportRolePolicy` system policy to the role. You can also create a custom policy that contains the following content and attach the policy to the role:
+      *         ```
+      *         {
+      *         	"Version": "1",
+      *         	"Statement": [
+      *         	{
+      *         		"Action": [
+      *         				"oss:GetObject",
+      *         				"oss:GetBucketLocation",
+      *         				"oss:GetBucketInfo"
+      *         	],
+      *         			"Resource": "*",
+      *         			"Effect": "Allow"
+      *         			}
+      *         	]
+      *         }
+      *         ```
+      * *   You cannot delete an image that is being imported. However, you can call the [CancelTask](~~25624~~) operation to cancel the image import task.
+      * *   Make sure that the image is imported to the same region where the OSS bucket resides.
+      * *   The valid values of N in the `DiskDeviceMapping.N` parameter range from 1 to 17. When N is set to 1, the disk is a system disk. When N is set to a value from 2 to 17, the disk is a data disk.
+      * *   When you set the `Architecture` parameter to `arm64` or when you set the `Platform` parameter to `CentOS Stream`, `Anolis`, `AlmaLinux`, `UOS`, `Kylin`, or `Rocky Linux`, take note of the following items:
+      *     *   If you need to set the password or modify the key pair for the imported image, make sure that the image meets the following requirements:
+      *         *   The kernel of the operating system supports the `CONFIG_FW_CFG_SYSFS` feature. By default, this feature is supported by Linux community kernel 4.6 and later and CentOS kernel 3.10.0-826.el7 and later. You can run the `grep -nr CONFIG_FW_CFG_SYSFS /boot/config-$(uname -r)` command on the source server of the image. If the command output contains `CONFIG_FW_CFG_SYSFS=y`, the operating system kernel in this image supports the `CONFIG_FW_CFG_SYSFS` feature.
+      *         *   The operating system is installed with the latest version of Alibaba Cloud cloud-init. The version of cloud-init 19.1 must be 19.1.3 or later. The version of cloud-init 0.7.6a in some early versions of operating systems must be 0.7.6a15 or later. For more information, see [Install cloud-init](~~57803~~).
+      *         *   The operating system supports the SHA-512 encryption algorithm.
+      *     *   If you want use the imported image to resize disks and file systems, make sure that the image meets the following requirements:
+      *         *   The kernel version of the operating system is later than 3.6.
+      *         *   The image supports the growpart command. The `cloud-utils-growpart` package is required to use this command. The methods for installing this package vary based on the operating systems. For more information, see [Resize partitions and file systems of Linux system disks](~~111738~~).
+      *         *   The image must support the resize2fs command. The`e2fsprogs` package is required to use this command. By default, the package is installed on the operating system. If the package is not installed, install it.
+      *         *   The operating system is installed with the latest version of Alibaba Cloud cloud-init. The version of cloud-init 19.1 must be 19.1.3 or later. The version of cloud-init 0.7.6a in some early versions of operating systems must be 0.7.6a15 or later. For more information, see [Install cloud-init](~~57803~~).
+      * *   If the image that you want to import uses the ARM64 architecture, you must set the real-time clock (RTC) to use the Coordinated Universal Time (UTC) time standard. For more information, see [Linux time and time zones](https://icms.alibaba-inc.com/content/ecs/image?l=1\\&m=4656\\&n=3385033).
+      *
+      * @param request ImportImageRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return ImportKeyPairResponse
+      * @return ImportImageResponse
      */
-    importKeyPairWithOptions(request: ImportKeyPairRequest, runtime: $Util.RuntimeOptions): Promise<ImportKeyPairResponse>;
+    importImageWithOptions(request: ImportImageRequest, runtime: $Util.RuntimeOptions): Promise<ImportImageResponse>;
     /**
       * When you call this operation, take note of the following items:
-      * * A maximum of 500 key pairs can be created in each region.
-      * * The key pair that you wan to import must support one of the following encryption methods:
-      *     * rsa
-      *     * dsa
-      *     * ssh-rsa
-      *     * ssh-dss
-      *     * ecdsa
-      *     * ssh-rsa-cert-v00@openssh.com
-      *     * ssh-dss-cert-v00@openssh.com
-      *     * ssh-rsa-cert-v01@openssh.com
-      *     * ssh-dss-cert-v01@openssh.com
-      *     * ecdsa-sha2-nistp256-cert-v01@openssh.com
-      *     * ecdsa-sha2-nistp384-cert-v01@openssh.com
-      *     * ecdsa-sha2-nistp521-cert-v01@openssh.com
-      *
-      * @param request ImportKeyPairRequest
-      * @return ImportKeyPairResponse
+      * *   Before you can import an image, you must upload the image to an Object Storage Service (OSS) bucket. For more information, see [Upload objects](~~31886~~).
+      * *   In some scenarios, you may want to create a custom image from an existing server and create an ECS instance from the image. The source server can be a physical server, a virtual machine, or a cloud host. However, you must make sure that the virtio driver is installed on the source server, otherwise the ECS instance created from the resulting image may be unable to start. For more information, see [Install the virtio driver](~~62423~~).
+      * *   If this is the first time you import images to ECS, you must use Resource Access Management (RAM) to grant ECS the permissions to access your OSS buckets. Otherwise, the `NoSetRoletoECSServiceAcount` error code is returned when you call the ImportImage operation. The [Cloud Resource Access Authorization](https://ram.console.aliyun.com/?spm=5176.2020520101image.0.0.2ffa4df57kSoHX#/role/authorize?request=%7B%22Requests%22%3A%20%7B%22request1%22%3A%20%7B%22RoleName%22%3A%20%22AliyunECSImageImportDefaultRole%22%2C%20%22TemplateId%22%3A%20%22ECSImportRole%22%7D%2C%20%22request2%22%3A%20%7B%22RoleName%22%3A%20%22AliyunECSImageExportDefaultRole%22%2C%20%22TemplateId%22%3A%20%22ECSExportRole%22%7D%7D%2C%20%22ReturnUrl%22%3A%20%22https%3A//ecs.console.aliyun.com/%22%2C%20%22Service%22%3A%20%22ECS%22%7D) page of the RAM console provides a convenient push-button authorization function for this operation. You can also perform the authorization by using a RAM role and RAM policies. The following examples show the policies and permissions required for some steps in the authorization procedure. For more information, see [Control access to resources by using RAM users](~~25481~~).
+      *     1.  Create a role named `AliyunECSImageImportDefaultRole`. You must use this exact name. Otherwise, the image cannot be imported. Configure the following trust policy for the role:
+      *             {
+      *             	"Statement": [
+      *             	{
+      *             		"Action": "sts:AssumeRole",
+      *             		"Effect": "Allow",
+      *             		"Principal": {
+      *             		"Service": [
+      *             			"ecs.aliyuncs.com"
+      *             		]
+      *             		}
+      *             	}
+      *             ],
+      *             	"Version": "1"
+      *             }
+      *     2.  Attach the `AliyunECSImageImportRolePolicy` system policy to the role. You can also create a custom policy that contains the following content and attach the policy to the role:
+      *         ```
+      *         {
+      *         	"Version": "1",
+      *         	"Statement": [
+      *         	{
+      *         		"Action": [
+      *         				"oss:GetObject",
+      *         				"oss:GetBucketLocation",
+      *         				"oss:GetBucketInfo"
+      *         	],
+      *         			"Resource": "*",
+      *         			"Effect": "Allow"
+      *         			}
+      *         	]
+      *         }
+      *         ```
+      * *   You cannot delete an image that is being imported. However, you can call the [CancelTask](~~25624~~) operation to cancel the image import task.
+      * *   Make sure that the image is imported to the same region where the OSS bucket resides.
+      * *   The valid values of N in the `DiskDeviceMapping.N` parameter range from 1 to 17. When N is set to 1, the disk is a system disk. When N is set to a value from 2 to 17, the disk is a data disk.
+      * *   When you set the `Architecture` parameter to `arm64` or when you set the `Platform` parameter to `CentOS Stream`, `Anolis`, `AlmaLinux`, `UOS`, `Kylin`, or `Rocky Linux`, take note of the following items:
+      *     *   If you need to set the password or modify the key pair for the imported image, make sure that the image meets the following requirements:
+      *         *   The kernel of the operating system supports the `CONFIG_FW_CFG_SYSFS` feature. By default, this feature is supported by Linux community kernel 4.6 and later and CentOS kernel 3.10.0-826.el7 and later. You can run the `grep -nr CONFIG_FW_CFG_SYSFS /boot/config-$(uname -r)` command on the source server of the image. If the command output contains `CONFIG_FW_CFG_SYSFS=y`, the operating system kernel in this image supports the `CONFIG_FW_CFG_SYSFS` feature.
+      *         *   The operating system is installed with the latest version of Alibaba Cloud cloud-init. The version of cloud-init 19.1 must be 19.1.3 or later. The version of cloud-init 0.7.6a in some early versions of operating systems must be 0.7.6a15 or later. For more information, see [Install cloud-init](~~57803~~).
+      *         *   The operating system supports the SHA-512 encryption algorithm.
+      *     *   If you want use the imported image to resize disks and file systems, make sure that the image meets the following requirements:
+      *         *   The kernel version of the operating system is later than 3.6.
+      *         *   The image supports the growpart command. The `cloud-utils-growpart` package is required to use this command. The methods for installing this package vary based on the operating systems. For more information, see [Resize partitions and file systems of Linux system disks](~~111738~~).
+      *         *   The image must support the resize2fs command. The`e2fsprogs` package is required to use this command. By default, the package is installed on the operating system. If the package is not installed, install it.
+      *         *   The operating system is installed with the latest version of Alibaba Cloud cloud-init. The version of cloud-init 19.1 must be 19.1.3 or later. The version of cloud-init 0.7.6a in some early versions of operating systems must be 0.7.6a15 or later. For more information, see [Install cloud-init](~~57803~~).
+      * *   If the image that you want to import uses the ARM64 architecture, you must set the real-time clock (RTC) to use the Coordinated Universal Time (UTC) time standard. For more information, see [Linux time and time zones](https://icms.alibaba-inc.com/content/ecs/image?l=1\\&m=4656\\&n=3385033).
+      *
+      * @param request ImportImageRequest
+      * @return ImportImageResponse
      */
+    importImage(request: ImportImageRequest): Promise<ImportImageResponse>;
+    importKeyPairWithOptions(request: ImportKeyPairRequest, runtime: $Util.RuntimeOptions): Promise<ImportKeyPairResponse>;
     importKeyPair(request: ImportKeyPairRequest): Promise<ImportKeyPairResponse>;
     /**
       * @deprecated
@@ -31817,109 +31929,55 @@ export default class Client extends OpenApi {
       * @return ImportSnapshotResponse
      */
     importSnapshot(request: ImportSnapshotRequest): Promise<ImportSnapshotResponse>;
-    installCloudAssistantWithOptions(request: InstallCloudAssistantRequest, runtime: $Util.RuntimeOptions): Promise<InstallCloudAssistantResponse>;
-    installCloudAssistant(request: InstallCloudAssistantRequest): Promise<InstallCloudAssistantResponse>;
     /**
-      * *   The ECS instances on which to run the Cloud Assistant command must meet the following requirements. If you specify multiple ECS instances and one of the instances does not meet the requirements for running the command, the call fails. Specify instances that meet the requirements and call the InvokeCommand operation again.
-      *     *   The network type is Virtual Private Cloud (VPC). For more information, see [What is a VPC?](~~34217~~)
-      *     *   The instances are in the Running (`Running`) state.
-      *     *   The Cloud Assistant client is installed on the instances. For more information, see [Install the Cloud Assistant client](~~64921~~).
-      *     *   Before you run PowerShell commands, make sure that the instances have the PowerShell module configured.
-      * *   If `Timed` is set to false, the command is run only once.
-      * *   If `Timed` is set to true, the command is run on a schedule.
-      *     *   The schedule is specified by the `Frequency` parameter. The results of each execution of a command do not affect the next execution of the command.
-      *     *   If you want to specify a schedule by using a cron expression, you can set a time zone based on your requirements. If you do not set a time zone, the schedule is based on the system time of the instance. Make sure that the time or time zone of the instance meets your business requirements. For more information, see [Configure the NTP service and time zone for Linux instances](~~92803~~) or [Configure the NTP service for Windows instances](~~51890~~).
-      *     To ensure that scheduled tasks can run as expected, make sure that the version of the Cloud Assistant client is not earlier than the following ones. A scheduled task can run a command at a specified interval, only once at a specified time, or at designated times based on a cron expression with a specified year or time zone. If the ClientNeedUpgrade error code is returned, you must upgrade the Cloud Assistant client to the latest version. For more information, see [Update or disable updates for the Cloud Assistant client](~~134383~~).
-      *           - Linux: 2.2.3.282
-      *           - Windows: 2.1.3.282
-      * *   Command executions may fail due to instance status exceptions, network exceptions, or exceptions on the Cloud Assistant client. If an execution fails, no execution information is generated.
-      * *   If you enable the custom parameter feature by setting EnableParameter to true when you create a command, you must specify custom parameters (`Parameters`) when you run the command.
+      * After you call the InstallCloudAssistant operation and then the [RebootInstance](~~25502~~) operation, the Cloud Assistant client is installed and takes effect.
       *
-      * @param tmpReq InvokeCommandRequest
+      * @param request InstallCloudAssistantRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return InvokeCommandResponse
+      * @return InstallCloudAssistantResponse
      */
-    invokeCommandWithOptions(tmpReq: InvokeCommandRequest, runtime: $Util.RuntimeOptions): Promise<InvokeCommandResponse>;
+    installCloudAssistantWithOptions(request: InstallCloudAssistantRequest, runtime: $Util.RuntimeOptions): Promise<InstallCloudAssistantResponse>;
     /**
-      * *   The ECS instances on which to run the Cloud Assistant command must meet the following requirements. If you specify multiple ECS instances and one of the instances does not meet the requirements for running the command, the call fails. Specify instances that meet the requirements and call the InvokeCommand operation again.
-      *     *   The network type is Virtual Private Cloud (VPC). For more information, see [What is a VPC?](~~34217~~)
-      *     *   The instances are in the Running (`Running`) state.
-      *     *   The Cloud Assistant client is installed on the instances. For more information, see [Install the Cloud Assistant client](~~64921~~).
-      *     *   Before you run PowerShell commands, make sure that the instances have the PowerShell module configured.
-      * *   If `Timed` is set to false, the command is run only once.
-      * *   If `Timed` is set to true, the command is run on a schedule.
-      *     *   The schedule is specified by the `Frequency` parameter. The results of each execution of a command do not affect the next execution of the command.
-      *     *   If you want to specify a schedule by using a cron expression, you can set a time zone based on your requirements. If you do not set a time zone, the schedule is based on the system time of the instance. Make sure that the time or time zone of the instance meets your business requirements. For more information, see [Configure the NTP service and time zone for Linux instances](~~92803~~) or [Configure the NTP service for Windows instances](~~51890~~).
-      *     To ensure that scheduled tasks can run as expected, make sure that the version of the Cloud Assistant client is not earlier than the following ones. A scheduled task can run a command at a specified interval, only once at a specified time, or at designated times based on a cron expression with a specified year or time zone. If the ClientNeedUpgrade error code is returned, you must upgrade the Cloud Assistant client to the latest version. For more information, see [Update or disable updates for the Cloud Assistant client](~~134383~~).
-      *           - Linux: 2.2.3.282
-      *           - Windows: 2.1.3.282
-      * *   Command executions may fail due to instance status exceptions, network exceptions, or exceptions on the Cloud Assistant client. If an execution fails, no execution information is generated.
-      * *   If you enable the custom parameter feature by setting EnableParameter to true when you create a command, you must specify custom parameters (`Parameters`) when you run the command.
+      * After you call the InstallCloudAssistant operation and then the [RebootInstance](~~25502~~) operation, the Cloud Assistant client is installed and takes effect.
       *
-      * @param request InvokeCommandRequest
-      * @return InvokeCommandResponse
+      * @param request InstallCloudAssistantRequest
+      * @return InstallCloudAssistantResponse
      */
+    installCloudAssistant(request: InstallCloudAssistantRequest): Promise<InstallCloudAssistantResponse>;
+    invokeCommandWithOptions(tmpReq: InvokeCommandRequest, runtime: $Util.RuntimeOptions): Promise<InvokeCommandResponse>;
     invokeCommand(request: InvokeCommandRequest): Promise<InvokeCommandResponse>;
-    /**
-      * ## Description
-      * A resource is a cloud service entity that you create in Alibaba Cloud, such as an ECS instance, elastic network interface (ENI), or image. A resource group is a collection of infrastructure for projects, environments, or stacks. In a resource group, you can manage resources and monitor and run tasks in a centralized manner without switching between Alibaba Cloud services.
-      *
-      * @param request JoinResourceGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return JoinResourceGroupResponse
-     */
     joinResourceGroupWithOptions(request: JoinResourceGroupRequest, runtime: $Util.RuntimeOptions): Promise<JoinResourceGroupResponse>;
-    /**
-      * ## Description
-      * A resource is a cloud service entity that you create in Alibaba Cloud, such as an ECS instance, elastic network interface (ENI), or image. A resource group is a collection of infrastructure for projects, environments, or stacks. In a resource group, you can manage resources and monitor and run tasks in a centralized manner without switching between Alibaba Cloud services.
-      *
-      * @param request JoinResourceGroupRequest
-      * @return JoinResourceGroupResponse
-     */
     joinResourceGroup(request: JoinResourceGroupRequest): Promise<JoinResourceGroupResponse>;
     joinSecurityGroupWithOptions(request: JoinSecurityGroupRequest, runtime: $Util.RuntimeOptions): Promise<JoinSecurityGroupResponse>;
     joinSecurityGroup(request: JoinSecurityGroupRequest): Promise<JoinSecurityGroupResponse>;
-    leaveSecurityGroupWithOptions(request: LeaveSecurityGroupRequest, runtime: $Util.RuntimeOptions): Promise<LeaveSecurityGroupResponse>;
-    leaveSecurityGroup(request: LeaveSecurityGroupRequest): Promise<LeaveSecurityGroupResponse>;
     /**
-      * Before you call this operation to query the states of Cloud Assistant plug-ins on ECS instances, make sure that the versions of the Cloud Assistant client installed on the instances are not earlier than the following ones:
-      * - 2.2.3.344 for Linux instances
-      * - 2.1.3.344 for Windows instances
+      * > This operation is not recommended. We recommend that you call the [ModifyInstanceAttribute](~~25503~~) operation to add instances to or remove instances from a security group, and call the [ModifyNetworkInterfaceAttribute](~~58513~~) operation to add ENIs to or remove ENIs from a security group.
+      * When you call this operation, take note of the following items:
+      * *   Before you remove an instance from a security group, the instance must be in the **Stopped** (Stopped) or **Running** (Running) state.
+      * *   An instance must belong to at least one security group. Therefore, if the instance to be removed belongs to only a single security group, the LeaveSecurityGroup request fails.
+      * *   An instance and an ENI cannot be removed from a security group at the same time. The `InstanceId` and `NetworkInterfaceId` parameters cannot be specified at the same time.
       *
-      * @param request ListPluginStatusRequest
+      * @param request LeaveSecurityGroupRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return ListPluginStatusResponse
+      * @return LeaveSecurityGroupResponse
      */
-    listPluginStatusWithOptions(request: ListPluginStatusRequest, runtime: $Util.RuntimeOptions): Promise<ListPluginStatusResponse>;
+    leaveSecurityGroupWithOptions(request: LeaveSecurityGroupRequest, runtime: $Util.RuntimeOptions): Promise<LeaveSecurityGroupResponse>;
     /**
-      * Before you call this operation to query the states of Cloud Assistant plug-ins on ECS instances, make sure that the versions of the Cloud Assistant client installed on the instances are not earlier than the following ones:
-      * - 2.2.3.344 for Linux instances
-      * - 2.1.3.344 for Windows instances
+      * > This operation is not recommended. We recommend that you call the [ModifyInstanceAttribute](~~25503~~) operation to add instances to or remove instances from a security group, and call the [ModifyNetworkInterfaceAttribute](~~58513~~) operation to add ENIs to or remove ENIs from a security group.
+      * When you call this operation, take note of the following items:
+      * *   Before you remove an instance from a security group, the instance must be in the **Stopped** (Stopped) or **Running** (Running) state.
+      * *   An instance must belong to at least one security group. Therefore, if the instance to be removed belongs to only a single security group, the LeaveSecurityGroup request fails.
+      * *   An instance and an ENI cannot be removed from a security group at the same time. The `InstanceId` and `NetworkInterfaceId` parameters cannot be specified at the same time.
       *
-      * @param request ListPluginStatusRequest
-      * @return ListPluginStatusResponse
+      * @param request LeaveSecurityGroupRequest
+      * @return LeaveSecurityGroupResponse
      */
+    leaveSecurityGroup(request: LeaveSecurityGroupRequest): Promise<LeaveSecurityGroupResponse>;
+    listPluginStatusWithOptions(request: ListPluginStatusRequest, runtime: $Util.RuntimeOptions): Promise<ListPluginStatusResponse>;
     listPluginStatus(request: ListPluginStatusRequest): Promise<ListPluginStatusResponse>;
     listTagResourcesWithOptions(request: ListTagResourcesRequest, runtime: $Util.RuntimeOptions): Promise<ListTagResourcesResponse>;
     listTagResources(request: ListTagResourcesRequest): Promise<ListTagResourcesResponse>;
-    /**
-      * Before you call this operation, take note of the following items:
-      * *   If you modify the capacity or capacity-related settings of an auto provisioning group, the group executes a scheduling task once after the group is modified.
-      * *   You cannot modify an auto provisioning group when the group is being deleted.
-      *
-      * @param request ModifyAutoProvisioningGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyAutoProvisioningGroupResponse
-     */
     modifyAutoProvisioningGroupWithOptions(request: ModifyAutoProvisioningGroupRequest, runtime: $Util.RuntimeOptions): Promise<ModifyAutoProvisioningGroupResponse>;
-    /**
-      * Before you call this operation, take note of the following items:
-      * *   If you modify the capacity or capacity-related settings of an auto provisioning group, the group executes a scheduling task once after the group is modified.
-      * *   You cannot modify an auto provisioning group when the group is being deleted.
-      *
-      * @param request ModifyAutoProvisioningGroupRequest
-      * @return ModifyAutoProvisioningGroupResponse
-     */
     modifyAutoProvisioningGroup(request: ModifyAutoProvisioningGroupRequest): Promise<ModifyAutoProvisioningGroupResponse>;
     /**
       * @deprecated
@@ -31957,90 +32015,88 @@ export default class Client extends OpenApi {
     modifyCapacityReservation(request: ModifyCapacityReservationRequest): Promise<ModifyCapacityReservationResponse>;
     modifyCommandWithOptions(request: ModifyCommandRequest, runtime: $Util.RuntimeOptions): Promise<ModifyCommandResponse>;
     modifyCommand(request: ModifyCommandRequest): Promise<ModifyCommandResponse>;
-    /**
-      * ## Description
-      * *   All the Elastic Compute Service (ECS) instances that are hosted on a dedicated host must be in the Stopped (`Stopped`) state before you can modify the CPU overcommit ratio of the dedicated host.
-      * *   Modifications to the CPU overcommit ratio of a dedicated host do not affect the operation of the dedicated host. After the CPU overcommit ratio is modified, the number of allocated vCPUs on the dedicated host cannot exceed the new total number of vCPUs. Otherwise, ECS instances that use the excess vCPUs cannot start.
-      *
-      * @param request ModifyDedicatedHostAttributeRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyDedicatedHostAttributeResponse
-     */
     modifyDedicatedHostAttributeWithOptions(request: ModifyDedicatedHostAttributeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDedicatedHostAttributeResponse>;
-    /**
-      * ## Description
-      * *   All the Elastic Compute Service (ECS) instances that are hosted on a dedicated host must be in the Stopped (`Stopped`) state before you can modify the CPU overcommit ratio of the dedicated host.
-      * *   Modifications to the CPU overcommit ratio of a dedicated host do not affect the operation of the dedicated host. After the CPU overcommit ratio is modified, the number of allocated vCPUs on the dedicated host cannot exceed the new total number of vCPUs. Otherwise, ECS instances that use the excess vCPUs cannot start.
-      *
-      * @param request ModifyDedicatedHostAttributeRequest
-      * @return ModifyDedicatedHostAttributeResponse
-     */
     modifyDedicatedHostAttribute(request: ModifyDedicatedHostAttributeRequest): Promise<ModifyDedicatedHostAttributeResponse>;
     modifyDedicatedHostAutoReleaseTimeWithOptions(request: ModifyDedicatedHostAutoReleaseTimeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDedicatedHostAutoReleaseTimeResponse>;
     modifyDedicatedHostAutoReleaseTime(request: ModifyDedicatedHostAutoReleaseTimeRequest): Promise<ModifyDedicatedHostAutoReleaseTimeResponse>;
-    /**
-      * ## Description
-      * *   If you enable auto-renewal for your subscription dedicated host, the dedicated host is automatically renewed nine days before expiration. The renewal fees are automatically paid at 08:00:00 (UTC+8). If the fees are not paid, they are paid at the same point in time the next day. Automatic payment stops after the fees are paid or after the dedicated host expires and is locked. Make sure that you have sufficient balance within your account.
-      * *   Subscription dedicated hosts can be automatically renewed along with the subscription Elastic Compute Service (ECS) instances hosted on the dedicated hosts. For more information, see the description of the AutoRenewWithEcs parameter.
-      *
-      * @param request ModifyDedicatedHostAutoRenewAttributeRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyDedicatedHostAutoRenewAttributeResponse
-     */
     modifyDedicatedHostAutoRenewAttributeWithOptions(request: ModifyDedicatedHostAutoRenewAttributeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDedicatedHostAutoRenewAttributeResponse>;
-    /**
-      * ## Description
-      * *   If you enable auto-renewal for your subscription dedicated host, the dedicated host is automatically renewed nine days before expiration. The renewal fees are automatically paid at 08:00:00 (UTC+8). If the fees are not paid, they are paid at the same point in time the next day. Automatic payment stops after the fees are paid or after the dedicated host expires and is locked. Make sure that you have sufficient balance within your account.
-      * *   Subscription dedicated hosts can be automatically renewed along with the subscription Elastic Compute Service (ECS) instances hosted on the dedicated hosts. For more information, see the description of the AutoRenewWithEcs parameter.
-      *
-      * @param request ModifyDedicatedHostAutoRenewAttributeRequest
-      * @return ModifyDedicatedHostAutoRenewAttributeResponse
-     */
     modifyDedicatedHostAutoRenewAttribute(request: ModifyDedicatedHostAutoRenewAttributeRequest): Promise<ModifyDedicatedHostAutoRenewAttributeResponse>;
     modifyDedicatedHostClusterAttributeWithOptions(request: ModifyDedicatedHostClusterAttributeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDedicatedHostClusterAttributeResponse>;
     modifyDedicatedHostClusterAttribute(request: ModifyDedicatedHostClusterAttributeRequest): Promise<ModifyDedicatedHostClusterAttributeResponse>;
     modifyDedicatedHostsChargeTypeWithOptions(request: ModifyDedicatedHostsChargeTypeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDedicatedHostsChargeTypeResponse>;
     modifyDedicatedHostsChargeType(request: ModifyDedicatedHostsChargeTypeRequest): Promise<ModifyDedicatedHostsChargeTypeResponse>;
+    /**
+      * You can call this operation to modify the demand information about instance types. Alibaba Cloud provides the requested resources based on your demand. You can file demands only for I/O optimized instance types and instances of the virtual private cloud (VPC) type. Parameters except `DemandName` and `DemandDescription` can be modified only for demands that are in the Rejected state.
+      * > This operation is in internal preview and has not been officially released. We recommend that you do not use this operation.
+      *
+      * @param request ModifyDemandRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ModifyDemandResponse
+     */
     modifyDemandWithOptions(request: ModifyDemandRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDemandResponse>;
+    /**
+      * You can call this operation to modify the demand information about instance types. Alibaba Cloud provides the requested resources based on your demand. You can file demands only for I/O optimized instance types and instances of the virtual private cloud (VPC) type. Parameters except `DemandName` and `DemandDescription` can be modified only for demands that are in the Rejected state.
+      * > This operation is in internal preview and has not been officially released. We recommend that you do not use this operation.
+      *
+      * @param request ModifyDemandRequest
+      * @return ModifyDemandResponse
+     */
     modifyDemand(request: ModifyDemandRequest): Promise<ModifyDemandResponse>;
     modifyDeploymentSetAttributeWithOptions(request: ModifyDeploymentSetAttributeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDeploymentSetAttributeResponse>;
     modifyDeploymentSetAttribute(request: ModifyDeploymentSetAttributeRequest): Promise<ModifyDeploymentSetAttributeResponse>;
     modifyDiagnosticMetricSetWithOptions(request: ModifyDiagnosticMetricSetRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDiagnosticMetricSetResponse>;
     modifyDiagnosticMetricSet(request: ModifyDiagnosticMetricSetRequest): Promise<ModifyDiagnosticMetricSetResponse>;
+    /**
+      * *   When you call this operation to modify the attributes of a disk, if you set the DeleteWithInstance parameter to false and the instance to which the disk is attached is locked for security reasons, the DeleteWithInstance parameter of the disk is ignored and the disk is released together with the instance. If `"LockReason" : "security"` is included in the response when you query the information about an instance, the instance is locked for security reasons.
+      * *   You can use the `DiskIds.N` parameter to specify multiple disks. This way, you can modify the attributes of the disks at the same time, including names, descriptions, and whether to release the disks together with the associated instances.
+      *
+      * @param request ModifyDiskAttributeRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ModifyDiskAttributeResponse
+     */
     modifyDiskAttributeWithOptions(request: ModifyDiskAttributeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDiskAttributeResponse>;
+    /**
+      * *   When you call this operation to modify the attributes of a disk, if you set the DeleteWithInstance parameter to false and the instance to which the disk is attached is locked for security reasons, the DeleteWithInstance parameter of the disk is ignored and the disk is released together with the instance. If `"LockReason" : "security"` is included in the response when you query the information about an instance, the instance is locked for security reasons.
+      * *   You can use the `DiskIds.N` parameter to specify multiple disks. This way, you can modify the attributes of the disks at the same time, including names, descriptions, and whether to release the disks together with the associated instances.
+      *
+      * @param request ModifyDiskAttributeRequest
+      * @return ModifyDiskAttributeResponse
+     */
     modifyDiskAttribute(request: ModifyDiskAttributeRequest): Promise<ModifyDiskAttributeResponse>;
+    modifyDiskChargeTypeWithOptions(request: ModifyDiskChargeTypeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDiskChargeTypeResponse>;
+    modifyDiskChargeType(request: ModifyDiskChargeTypeRequest): Promise<ModifyDiskChargeTypeResponse>;
     /**
       * ## Description
-      * After you change the billing method, automatic payment is enabled by default. Make sure that you have sufficient balance in your account. Otherwise, your order becomes invalid and must be canceled. If your account balance is insufficient, you can set the AutoPay parameter to false to generate an unpaid order. Then, you can log on to the [ECS console](https://ecs.console.aliyun.com/) to pay for the order.
       * When you call this operation, take note of the following items:
-      * *   You can change the billing method from subscription to pay-as-you-go for subscription disks that are attached to a subscription instance.
-      * *   You can change the billing method from pay-as-you-go to subscription for pay-as-you-go data disks that are attached to a subscription or pay-as-you-go instance.
-      * *   The instance cannot be in the Stopped state due to overdue payments.
-      * *   You can change the billing method for each disk three times at most. A maximum of three refunds can be made for price differences for a single instance.
-      * *   The price difference is refunded to the payment account you used. Coupons that have been redeemed are not refundable.
-      * *   You cannot change the billing method of a disk again within five minutes after the billing method is changed.
-      *
-      * @param request ModifyDiskChargeTypeRequest
+      * *   To modify the performance level of an ESSD, take note of the following items:
+      *     *   For a subscription ESSD, you can only upgrade its performance level.
+      *     *   For a pay-as-you-go ESSD, You can upgrade or downgrade its performance level. However, you cannot downgrade the performance level to PL0.
+      *     *   The ESSD must be in the **In Use** (In_Use) or **Unattached** (Available) state.
+      *     *   If the ESSD is attached to an ECS instance, the instance must be in the **Running** (Running) or **Stopped** (Stopped) state. The instance cannot be in the Expired state or stopped due to an overdue payment.
+      *     *   If you cannot upgrade the performance level of the ESSD due to its capacity, resize the ESSD by calling the [ResizeDisk](~~25522~~) operation and then try again. For more information, see [Enhanced SSDs](~~122389~~).
+      * *   For more information about the limits on changing the category of a disk, see the "Limits" section of the [Change the category of a disk](~~161980~~) topic.
+      * The new disk category or performance level takes effect immediately after this operation is executed. Alibaba Cloud calculates the bill based on the new disk category and performance level.
+      *
+      * @param request ModifyDiskSpecRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyDiskChargeTypeResponse
+      * @return ModifyDiskSpecResponse
      */
-    modifyDiskChargeTypeWithOptions(request: ModifyDiskChargeTypeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDiskChargeTypeResponse>;
+    modifyDiskSpecWithOptions(request: ModifyDiskSpecRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDiskSpecResponse>;
     /**
       * ## Description
-      * After you change the billing method, automatic payment is enabled by default. Make sure that you have sufficient balance in your account. Otherwise, your order becomes invalid and must be canceled. If your account balance is insufficient, you can set the AutoPay parameter to false to generate an unpaid order. Then, you can log on to the [ECS console](https://ecs.console.aliyun.com/) to pay for the order.
       * When you call this operation, take note of the following items:
-      * *   You can change the billing method from subscription to pay-as-you-go for subscription disks that are attached to a subscription instance.
-      * *   You can change the billing method from pay-as-you-go to subscription for pay-as-you-go data disks that are attached to a subscription or pay-as-you-go instance.
-      * *   The instance cannot be in the Stopped state due to overdue payments.
-      * *   You can change the billing method for each disk three times at most. A maximum of three refunds can be made for price differences for a single instance.
-      * *   The price difference is refunded to the payment account you used. Coupons that have been redeemed are not refundable.
-      * *   You cannot change the billing method of a disk again within five minutes after the billing method is changed.
-      *
-      * @param request ModifyDiskChargeTypeRequest
-      * @return ModifyDiskChargeTypeResponse
+      * *   To modify the performance level of an ESSD, take note of the following items:
+      *     *   For a subscription ESSD, you can only upgrade its performance level.
+      *     *   For a pay-as-you-go ESSD, You can upgrade or downgrade its performance level. However, you cannot downgrade the performance level to PL0.
+      *     *   The ESSD must be in the **In Use** (In_Use) or **Unattached** (Available) state.
+      *     *   If the ESSD is attached to an ECS instance, the instance must be in the **Running** (Running) or **Stopped** (Stopped) state. The instance cannot be in the Expired state or stopped due to an overdue payment.
+      *     *   If you cannot upgrade the performance level of the ESSD due to its capacity, resize the ESSD by calling the [ResizeDisk](~~25522~~) operation and then try again. For more information, see [Enhanced SSDs](~~122389~~).
+      * *   For more information about the limits on changing the category of a disk, see the "Limits" section of the [Change the category of a disk](~~161980~~) topic.
+      * The new disk category or performance level takes effect immediately after this operation is executed. Alibaba Cloud calculates the bill based on the new disk category and performance level.
+      *
+      * @param request ModifyDiskSpecRequest
+      * @return ModifyDiskSpecResponse
      */
-    modifyDiskChargeType(request: ModifyDiskChargeTypeRequest): Promise<ModifyDiskChargeTypeResponse>;
-    modifyDiskSpecWithOptions(request: ModifyDiskSpecRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDiskSpecResponse>;
     modifyDiskSpec(request: ModifyDiskSpecRequest): Promise<ModifyDiskSpecResponse>;
     /**
       * @deprecated
@@ -32108,7 +32164,40 @@ export default class Client extends OpenApi {
       * @return ModifyImageShareGroupPermissionResponse
      */
     modifyImageShareGroupPermission(request: ModifyImageShareGroupPermissionRequest): Promise<ModifyImageShareGroupPermissionResponse>;
+    /**
+      * When you call this operation, take note of the following items:
+      * *   You can share only your custom images with other Alibaba Cloud accounts.
+      * *   You can share a custom image with up to 10 Alibaba Cloud accounts in a request. You can specify up to 10 Alibaba Cloud account IDs by using the AddAccount.N parameter or the RemoveAccount.N parameter. If you specify more than 10 account IDs, the parameter value does not take effect.
+      * *   You can share a custom image with up to 50 Alibaba Cloud accounts in total.
+      * *   After you create an instance from a shared custom image by calling the [RunInstances](~~63440~~) operation, you cannot call the [ReInitDisk](~~25519~~) operation to reinitialize the system disk of the instance if the image owner unshares the image or calls the [DeleteImage](~~25537~~) operation to delete the image.
+      * To publish or unpublish a community image, take note of the following items:
+      * *   Alibaba Cloud provides only the platform where the community images can be published and managed. The owner of a community image is responsible for the quality and updates of the image. Make sure that you read and agree to the Community Image Agreement. Otherwise, you cannot publish community images. For more information, see [Publish a community image](~~208370~~)
+      * *   You cannot publish encrypted images as community images.
+      * *   All community images are publicly available. All Alibaba Cloud accounts that reside in the same region as a community image can access the image.
+      * *   You cannot share, export, or copy community images.
+      * *   After a community image is unpublished, the image is no longer available to Alibaba Cloud accounts. If you share a custom image with specific Alibaba cloud accounts and then publish the image as a community image, the image is still shared with the accounts.
+      *
+      * @param request ModifyImageSharePermissionRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ModifyImageSharePermissionResponse
+     */
     modifyImageSharePermissionWithOptions(request: ModifyImageSharePermissionRequest, runtime: $Util.RuntimeOptions): Promise<ModifyImageSharePermissionResponse>;
+    /**
+      * When you call this operation, take note of the following items:
+      * *   You can share only your custom images with other Alibaba Cloud accounts.
+      * *   You can share a custom image with up to 10 Alibaba Cloud accounts in a request. You can specify up to 10 Alibaba Cloud account IDs by using the AddAccount.N parameter or the RemoveAccount.N parameter. If you specify more than 10 account IDs, the parameter value does not take effect.
+      * *   You can share a custom image with up to 50 Alibaba Cloud accounts in total.
+      * *   After you create an instance from a shared custom image by calling the [RunInstances](~~63440~~) operation, you cannot call the [ReInitDisk](~~25519~~) operation to reinitialize the system disk of the instance if the image owner unshares the image or calls the [DeleteImage](~~25537~~) operation to delete the image.
+      * To publish or unpublish a community image, take note of the following items:
+      * *   Alibaba Cloud provides only the platform where the community images can be published and managed. The owner of a community image is responsible for the quality and updates of the image. Make sure that you read and agree to the Community Image Agreement. Otherwise, you cannot publish community images. For more information, see [Publish a community image](~~208370~~)
+      * *   You cannot publish encrypted images as community images.
+      * *   All community images are publicly available. All Alibaba Cloud accounts that reside in the same region as a community image can access the image.
+      * *   You cannot share, export, or copy community images.
+      * *   After a community image is unpublished, the image is no longer available to Alibaba Cloud accounts. If you share a custom image with specific Alibaba cloud accounts and then publish the image as a community image, the image is still shared with the accounts.
+      *
+      * @param request ModifyImageSharePermissionRequest
+      * @return ModifyImageSharePermissionResponse
+     */
     modifyImageSharePermission(request: ModifyImageSharePermissionRequest): Promise<ModifyImageSharePermissionResponse>;
     modifyInstanceAttachmentAttributesWithOptions(request: ModifyInstanceAttachmentAttributesRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceAttachmentAttributesResponse>;
     modifyInstanceAttachmentAttributes(request: ModifyInstanceAttachmentAttributesRequest): Promise<ModifyInstanceAttachmentAttributesResponse>;
@@ -32116,42 +32205,28 @@ export default class Client extends OpenApi {
     modifyInstanceAttribute(request: ModifyInstanceAttributeRequest): Promise<ModifyInstanceAttributeResponse>;
     modifyInstanceAutoReleaseTimeWithOptions(request: ModifyInstanceAutoReleaseTimeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceAutoReleaseTimeResponse>;
     modifyInstanceAutoReleaseTime(request: ModifyInstanceAutoReleaseTimeRequest): Promise<ModifyInstanceAutoReleaseTimeResponse>;
-    modifyInstanceAutoRenewAttributeWithOptions(request: ModifyInstanceAutoRenewAttributeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceAutoRenewAttributeResponse>;
-    modifyInstanceAutoRenewAttribute(request: ModifyInstanceAutoRenewAttributeRequest): Promise<ModifyInstanceAutoRenewAttributeResponse>;
     /**
-      * Before you call this operation, make sure that you understand the billing methods and pricing schedule of ECS. For more information, see the [Elastic Compute Service](https://www.alibabacloud.com/product/ecs#pricing) product page.
-      * When you call this operation, take note of the following items:
-      * * The instances must be in the **Running** (`Running`) or **Stopped** (`Stopped`) state, and you have no overdue payments for them.
-      * * After you change the billing method, automatic payment is enabled by default. Make sure that you have sufficient balance in your account. Otherwise, your order becomes invalid and is canceled. If your account balance is insufficient, you can set the `AutoPay` parameter to `false` to generate an unpaid order. Then, you can log on to the [ECS console](https://ecs.console.aliyun.com/) to pay for the order.
-      * * **Change the billing method from subscription to pay-as-you-go**:
-      *     * Your ECS usage determines whether the billing method of an instance can be changed from subscription to pay-as-you-go.
-      *     * After you change the billing method of an instance from subscription to pay-as-you-go, the new billing method remains in effect for the remaining lifecycle of the instance. The price difference is refunded to the payment account that you used. Vouchers that have been redeemed are not refundable.
-      *     * **Refund rule**: You have a quota for the total refund amount each month, and unused balance of this quota is not carried forward into the next month. After you use up the refund quota of the current month, you can change the billing method only when the next month arrives. The refund amount incurred when you change the billing method is calculated based on the following formula: **Number of vCPUs × (Number of remaining days × 24 ± Number of remaining or elapsed hours)**.
-      * * **Change the billing method from pay-as-you-go to subscription**:
-      *     * You can change the billing method of all data disks attached to an instance from pay-as-you-go to subscription.
-      *     * This operation cannot be called for a pay-as-you-go instance that has an automatic release time set.
-      *
-      * @param request ModifyInstanceChargeTypeRequest
+      * Before you call this operation, make sure that you understand the billing methods and pricing schedule of Elastic Compute Service (ECS). For more information, see the [Elastic Compute Service](https://www.aliyun.com/price/product#/ecs/detail) product page.
+      * *   The payment for auto-renewal is first deducted automatically at 08:00:00 (UTC+8) nine days before the instance expires.
+      * *   If the subscription period of a new instance is one week, the renewal payment is automatically deducted on the day the instance is created.
+      * *   If the first deduction attempt fails, Alibaba Cloud attempts to deduct the payment each day until the payment is deducted or until the instance is locked after the nine-day period ends. Make sure that your account balance or credit balance is sufficient.
+      *
+      * @param request ModifyInstanceAutoRenewAttributeRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyInstanceChargeTypeResponse
+      * @return ModifyInstanceAutoRenewAttributeResponse
      */
-    modifyInstanceChargeTypeWithOptions(request: ModifyInstanceChargeTypeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceChargeTypeResponse>;
+    modifyInstanceAutoRenewAttributeWithOptions(request: ModifyInstanceAutoRenewAttributeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceAutoRenewAttributeResponse>;
     /**
-      * Before you call this operation, make sure that you understand the billing methods and pricing schedule of ECS. For more information, see the [Elastic Compute Service](https://www.alibabacloud.com/product/ecs#pricing) product page.
-      * When you call this operation, take note of the following items:
-      * * The instances must be in the **Running** (`Running`) or **Stopped** (`Stopped`) state, and you have no overdue payments for them.
-      * * After you change the billing method, automatic payment is enabled by default. Make sure that you have sufficient balance in your account. Otherwise, your order becomes invalid and is canceled. If your account balance is insufficient, you can set the `AutoPay` parameter to `false` to generate an unpaid order. Then, you can log on to the [ECS console](https://ecs.console.aliyun.com/) to pay for the order.
-      * * **Change the billing method from subscription to pay-as-you-go**:
-      *     * Your ECS usage determines whether the billing method of an instance can be changed from subscription to pay-as-you-go.
-      *     * After you change the billing method of an instance from subscription to pay-as-you-go, the new billing method remains in effect for the remaining lifecycle of the instance. The price difference is refunded to the payment account that you used. Vouchers that have been redeemed are not refundable.
-      *     * **Refund rule**: You have a quota for the total refund amount each month, and unused balance of this quota is not carried forward into the next month. After you use up the refund quota of the current month, you can change the billing method only when the next month arrives. The refund amount incurred when you change the billing method is calculated based on the following formula: **Number of vCPUs × (Number of remaining days × 24 ± Number of remaining or elapsed hours)**.
-      * * **Change the billing method from pay-as-you-go to subscription**:
-      *     * You can change the billing method of all data disks attached to an instance from pay-as-you-go to subscription.
-      *     * This operation cannot be called for a pay-as-you-go instance that has an automatic release time set.
-      *
-      * @param request ModifyInstanceChargeTypeRequest
-      * @return ModifyInstanceChargeTypeResponse
+      * Before you call this operation, make sure that you understand the billing methods and pricing schedule of Elastic Compute Service (ECS). For more information, see the [Elastic Compute Service](https://www.aliyun.com/price/product#/ecs/detail) product page.
+      * *   The payment for auto-renewal is first deducted automatically at 08:00:00 (UTC+8) nine days before the instance expires.
+      * *   If the subscription period of a new instance is one week, the renewal payment is automatically deducted on the day the instance is created.
+      * *   If the first deduction attempt fails, Alibaba Cloud attempts to deduct the payment each day until the payment is deducted or until the instance is locked after the nine-day period ends. Make sure that your account balance or credit balance is sufficient.
+      *
+      * @param request ModifyInstanceAutoRenewAttributeRequest
+      * @return ModifyInstanceAutoRenewAttributeResponse
      */
+    modifyInstanceAutoRenewAttribute(request: ModifyInstanceAutoRenewAttributeRequest): Promise<ModifyInstanceAutoRenewAttributeResponse>;
+    modifyInstanceChargeTypeWithOptions(request: ModifyInstanceChargeTypeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceChargeTypeResponse>;
     modifyInstanceChargeType(request: ModifyInstanceChargeTypeRequest): Promise<ModifyInstanceChargeTypeResponse>;
     /**
       * When you call this operation for an ECS instance, take note of the following items:
@@ -32184,13 +32259,126 @@ export default class Client extends OpenApi {
     modifyInstanceMaintenanceAttributes(request: ModifyInstanceMaintenanceAttributesRequest): Promise<ModifyInstanceMaintenanceAttributesResponse>;
     modifyInstanceMetadataOptionsWithOptions(request: ModifyInstanceMetadataOptionsRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceMetadataOptionsResponse>;
     modifyInstanceMetadataOptions(request: ModifyInstanceMetadataOptionsRequest): Promise<ModifyInstanceMetadataOptionsResponse>;
+    /**
+      * When you call this operation, take note of the following items:
+      * *   As of November 27, 2020, the maximum bandwidth value available for you to create ECS instances or to change ECS instance configurations is subject to throttling policies for your account. To increase the maximum bandwidth value, submit a ticket. The following throttling policies apply:
+      *     *   Within a single region, the sum of actual peak bandwidths of all ECS instances that use the pay-by-traffic billing method for network usage cannot exceed 5 Gbit/s.
+      *     *   Within a single region, the sum of actual peak bandwidths of all ECS instances that use the pay-by-bandwidth billing method for network usage cannot exceed 50 Gbit/s.
+      * *   If you upgrade the outbound public bandwidth (InternetMaxBandwidthOut) of a subscription (PrePaid) instance from 0 Mbit/s when you modify the bandwidth configurations of the instance, a public IP address is automatically assigned to the instance.
+      * *   If you upgrade the outbound public bandwidth (InternetMaxBandwidthOut) of a pay-as-you-go (PostPaid) instance from 0 Mbit/s when you modify the bandwidth configurations of the instance, no public IP address is automatically assigned to the instance. You must call the [AllocatePublicIpAddress](~~25544~~) operation to assign a public IP address to the instance.
+      * *   An instance in the classic network must be in the Stopped state before you can upgrade the outbound public bandwidth (InternetMaxBandwidthOut) of the instance from 0 Mbit/s.
+      * *   After the bandwidth is upgraded, AutoPay is set to true by default and the payment is automatically made. Maintain a sufficient account balance. Otherwise, your order becomes invalid and must be canceled. If your account balance is insufficient, you can set AutoPay to false. When you call the ModifyInstanceNetworkSpec operation, an unpaid order is generated. Then, you can log on to the ECS console to pay for the order.
+      * *   The price difference is refunded to the payment account that you used. Vouchers or coupons that have been redeemed cannot be returned.
+      *
+      * @param request ModifyInstanceNetworkSpecRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ModifyInstanceNetworkSpecResponse
+     */
     modifyInstanceNetworkSpecWithOptions(request: ModifyInstanceNetworkSpecRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceNetworkSpecResponse>;
+    /**
+      * When you call this operation, take note of the following items:
+      * *   As of November 27, 2020, the maximum bandwidth value available for you to create ECS instances or to change ECS instance configurations is subject to throttling policies for your account. To increase the maximum bandwidth value, submit a ticket. The following throttling policies apply:
+      *     *   Within a single region, the sum of actual peak bandwidths of all ECS instances that use the pay-by-traffic billing method for network usage cannot exceed 5 Gbit/s.
+      *     *   Within a single region, the sum of actual peak bandwidths of all ECS instances that use the pay-by-bandwidth billing method for network usage cannot exceed 50 Gbit/s.
+      * *   If you upgrade the outbound public bandwidth (InternetMaxBandwidthOut) of a subscription (PrePaid) instance from 0 Mbit/s when you modify the bandwidth configurations of the instance, a public IP address is automatically assigned to the instance.
+      * *   If you upgrade the outbound public bandwidth (InternetMaxBandwidthOut) of a pay-as-you-go (PostPaid) instance from 0 Mbit/s when you modify the bandwidth configurations of the instance, no public IP address is automatically assigned to the instance. You must call the [AllocatePublicIpAddress](~~25544~~) operation to assign a public IP address to the instance.
+      * *   An instance in the classic network must be in the Stopped state before you can upgrade the outbound public bandwidth (InternetMaxBandwidthOut) of the instance from 0 Mbit/s.
+      * *   After the bandwidth is upgraded, AutoPay is set to true by default and the payment is automatically made. Maintain a sufficient account balance. Otherwise, your order becomes invalid and must be canceled. If your account balance is insufficient, you can set AutoPay to false. When you call the ModifyInstanceNetworkSpec operation, an unpaid order is generated. Then, you can log on to the ECS console to pay for the order.
+      * *   The price difference is refunded to the payment account that you used. Vouchers or coupons that have been redeemed cannot be returned.
+      *
+      * @param request ModifyInstanceNetworkSpecRequest
+      * @return ModifyInstanceNetworkSpecResponse
+     */
     modifyInstanceNetworkSpec(request: ModifyInstanceNetworkSpecRequest): Promise<ModifyInstanceNetworkSpecResponse>;
     modifyInstanceSpecWithOptions(request: ModifyInstanceSpecRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceSpecResponse>;
     modifyInstanceSpec(request: ModifyInstanceSpecRequest): Promise<ModifyInstanceSpecResponse>;
+    /**
+      * *   The password must be six characters in length and can contain only uppercase letters, lowercase letters, and digits.
+      * *   After you modify the VNC password of an instance, take note of the following items:
+      *     *   If the instance is I/O optimized, the new password takes effect immediately.
+      *     *   If the instance is non-I/O optimized, you must [restart the instance](~~25440~~) by using the ECS console or by calling the [RebootInstance](~~25502~~) operation for the new password to take effect.
+      *
+      * @param request ModifyInstanceVncPasswdRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ModifyInstanceVncPasswdResponse
+     */
     modifyInstanceVncPasswdWithOptions(request: ModifyInstanceVncPasswdRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceVncPasswdResponse>;
+    /**
+      * *   The password must be six characters in length and can contain only uppercase letters, lowercase letters, and digits.
+      * *   After you modify the VNC password of an instance, take note of the following items:
+      *     *   If the instance is I/O optimized, the new password takes effect immediately.
+      *     *   If the instance is non-I/O optimized, you must [restart the instance](~~25440~~) by using the ECS console or by calling the [RebootInstance](~~25502~~) operation for the new password to take effect.
+      *
+      * @param request ModifyInstanceVncPasswdRequest
+      * @return ModifyInstanceVncPasswdResponse
+     */
     modifyInstanceVncPasswd(request: ModifyInstanceVncPasswdRequest): Promise<ModifyInstanceVncPasswdResponse>;
+    /**
+      * The instance must be in the **Stopped** state.``
+      * *   When you call this operation to modify the private IP address or vSwitch of an instance, take note of the following items:
+      *     *   If the instance is newly created, you must restart the instance before you can call this operation.
+      *     *   After you modify the private IP address or vSwitch of an instance, you must restart the instance before you can call this operation again.
+      * *   When you call this operation to modify the VPC of an instance, take note of the following items:
+      *     *   **Instance:**
+      *         *   The instance cannot be associated with Server Load Balancer (SLB) instances.
+      *         *   The instance cannot be in the Locked, To Be Released, Expired, Expired and Being Recycled, or Overdue and Being Recycled state. For more information, see [ECS instance lifecycle](~~25380~~).
+      *         *   The instance cannot be in-use or used in conjunction with other cloud services. For example, the instance cannot be in the process of being migrated or having its VPC changed, or the databases deployed on the instance cannot be managed by Data Transmission Service (DTS).
+      *     *   **Network:**
+      *         *   The cut-through mode or multi-elastic IP address (EIP) to elastic network interface (ENI) mode must be disabled.
+      *         *   The instance cannot be associated with a high-availability virtual IP address (HAVIP).
+      *         *   The vSwitch of the instance cannot be associated with a custom route table.
+      *         *   The instance cannot have Global Accelerator (GA) activated.
+      *         *   The instance cannot have secondary ENIs bound.
+      *         *   The instance cannot have IPv6 addresses assigned.
+      *         *   The primary ENI of the instance cannot be associated with multiple IP addresses.
+      *         *   The vSwitch specified by the VSwitchId parameter must belong to the new VPC.
+      *         *   The new and original vSwitches must reside within the same zone.
+      *         *   If the private IP address of the primary ENI is specified, the private IP address must be available and within the CIDR block of the vSwitch. If the private IP address is not specified, the system randomly assigns one. The available IP addresses in the CIDR block of the new vSwitch must be sufficient.
+      *         *   If advanced features are enabled in the new VPC, take note of the instance families that do not support advanced VPC features. For more information, see [Instance families that do not support advanced VPC features](~~163466~~).
+      *         *   The Alibaba Cloud account that owns the new VPC cannot share the VPC with other accounts.
+      *     *   **Security group (SecurityGroupId.N):**
+      *         *   All security groups must be of the same type.
+      *         *   The valid values of N depend on the maximum number of security groups to which an instance can belong. For more information, see [Limits](~~25412~~).
+      *         *   The specified security groups must belong to the new VPC.
+      *         *   You can switch the instance to a security group of a different type. If you want to switch an instance to a security group of a different type, you must understand the differences between the rule configurations of the two security group types to avoid impacts on the instance network. For more information, see [Overview](~~25387~~).
+      *
+      * @param request ModifyInstanceVpcAttributeRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ModifyInstanceVpcAttributeResponse
+     */
     modifyInstanceVpcAttributeWithOptions(request: ModifyInstanceVpcAttributeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyInstanceVpcAttributeResponse>;
+    /**
+      * The instance must be in the **Stopped** state.``
+      * *   When you call this operation to modify the private IP address or vSwitch of an instance, take note of the following items:
+      *     *   If the instance is newly created, you must restart the instance before you can call this operation.
+      *     *   After you modify the private IP address or vSwitch of an instance, you must restart the instance before you can call this operation again.
+      * *   When you call this operation to modify the VPC of an instance, take note of the following items:
+      *     *   **Instance:**
+      *         *   The instance cannot be associated with Server Load Balancer (SLB) instances.
+      *         *   The instance cannot be in the Locked, To Be Released, Expired, Expired and Being Recycled, or Overdue and Being Recycled state. For more information, see [ECS instance lifecycle](~~25380~~).
+      *         *   The instance cannot be in-use or used in conjunction with other cloud services. For example, the instance cannot be in the process of being migrated or having its VPC changed, or the databases deployed on the instance cannot be managed by Data Transmission Service (DTS).
+      *     *   **Network:**
+      *         *   The cut-through mode or multi-elastic IP address (EIP) to elastic network interface (ENI) mode must be disabled.
+      *         *   The instance cannot be associated with a high-availability virtual IP address (HAVIP).
+      *         *   The vSwitch of the instance cannot be associated with a custom route table.
+      *         *   The instance cannot have Global Accelerator (GA) activated.
+      *         *   The instance cannot have secondary ENIs bound.
+      *         *   The instance cannot have IPv6 addresses assigned.
+      *         *   The primary ENI of the instance cannot be associated with multiple IP addresses.
+      *         *   The vSwitch specified by the VSwitchId parameter must belong to the new VPC.
+      *         *   The new and original vSwitches must reside within the same zone.
+      *         *   If the private IP address of the primary ENI is specified, the private IP address must be available and within the CIDR block of the vSwitch. If the private IP address is not specified, the system randomly assigns one. The available IP addresses in the CIDR block of the new vSwitch must be sufficient.
+      *         *   If advanced features are enabled in the new VPC, take note of the instance families that do not support advanced VPC features. For more information, see [Instance families that do not support advanced VPC features](~~163466~~).
+      *         *   The Alibaba Cloud account that owns the new VPC cannot share the VPC with other accounts.
+      *     *   **Security group (SecurityGroupId.N):**
+      *         *   All security groups must be of the same type.
+      *         *   The valid values of N depend on the maximum number of security groups to which an instance can belong. For more information, see [Limits](~~25412~~).
+      *         *   The specified security groups must belong to the new VPC.
+      *         *   You can switch the instance to a security group of a different type. If you want to switch an instance to a security group of a different type, you must understand the differences between the rule configurations of the two security group types to avoid impacts on the instance network. For more information, see [Overview](~~25387~~).
+      *
+      * @param request ModifyInstanceVpcAttributeRequest
+      * @return ModifyInstanceVpcAttributeResponse
+     */
     modifyInstanceVpcAttribute(request: ModifyInstanceVpcAttributeRequest): Promise<ModifyInstanceVpcAttributeResponse>;
     modifyLaunchTemplateDefaultVersionWithOptions(request: ModifyLaunchTemplateDefaultVersionRequest, runtime: $Util.RuntimeOptions): Promise<ModifyLaunchTemplateDefaultVersionResponse>;
     modifyLaunchTemplateDefaultVersion(request: ModifyLaunchTemplateDefaultVersionRequest): Promise<ModifyLaunchTemplateDefaultVersionResponse>;
@@ -32213,32 +32401,7 @@ export default class Client extends OpenApi {
       * @return ModifyPhysicalConnectionAttributeResponse
      */
     modifyPhysicalConnectionAttribute(request: ModifyPhysicalConnectionAttributeRequest): Promise<ModifyPhysicalConnectionAttributeResponse>;
-    /**
-      * ## Description
-      * *   The specified CIDR block must be valid. For example, 10.0.0.0/8 is a valid CIDR block while 10.0.0.1/8 is not. For more information, see the [What is CIDR?](https://www.alibabacloud.com/help/doc-detail/40637.htm#section-jua-0tj-q5m) section in Network FAQ.
-      * *   When you add or delete an entry, you cannot specify duplicate CIDR blocks. Examples:
-      *     *   For IPv4 CIDR blocks, you cannot specify the 10.0.0.0/8 CIDR block in two entries. You cannot specify the 10.0.0.1/32 CIDR block in one entry and the 10.0.0.1 CIDR block in another entry. These two CIDR blocks are the same.
-      *     *   For IPv6 CIDR blocks, you cannot specify the 2001:fd01:0:0:0:0:0:0/32 CIDR block in one entry and the 2001:fd01::/32 CIDR block in another entry. These two CIDR blocks are the same.
-      * *   The CIDR block in an entry to be added cannot the same as that in an entry to be deleted. For example, when you add an entry in which the 10.0.0.0/8 CIDR block is specified, the entry to be deleted cannot have the 10.0.0.0/8 CIDR block specified.
-      * *   If you want to modify the description of an entry, you must specify the CIDR block (`AddEntry.N.Cidr`) and new description (`AddEntry.N.Description`) in the entry.
-      *
-      * @param request ModifyPrefixListRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyPrefixListResponse
-     */
     modifyPrefixListWithOptions(request: ModifyPrefixListRequest, runtime: $Util.RuntimeOptions): Promise<ModifyPrefixListResponse>;
-    /**
-      * ## Description
-      * *   The specified CIDR block must be valid. For example, 10.0.0.0/8 is a valid CIDR block while 10.0.0.1/8 is not. For more information, see the [What is CIDR?](https://www.alibabacloud.com/help/doc-detail/40637.htm#section-jua-0tj-q5m) section in Network FAQ.
-      * *   When you add or delete an entry, you cannot specify duplicate CIDR blocks. Examples:
-      *     *   For IPv4 CIDR blocks, you cannot specify the 10.0.0.0/8 CIDR block in two entries. You cannot specify the 10.0.0.1/32 CIDR block in one entry and the 10.0.0.1 CIDR block in another entry. These two CIDR blocks are the same.
-      *     *   For IPv6 CIDR blocks, you cannot specify the 2001:fd01:0:0:0:0:0:0/32 CIDR block in one entry and the 2001:fd01::/32 CIDR block in another entry. These two CIDR blocks are the same.
-      * *   The CIDR block in an entry to be added cannot the same as that in an entry to be deleted. For example, when you add an entry in which the 10.0.0.0/8 CIDR block is specified, the entry to be deleted cannot have the 10.0.0.0/8 CIDR block specified.
-      * *   If you want to modify the description of an entry, you must specify the CIDR block (`AddEntry.N.Cidr`) and new description (`AddEntry.N.Description`) in the entry.
-      *
-      * @param request ModifyPrefixListRequest
-      * @return ModifyPrefixListResponse
-     */
     modifyPrefixList(request: ModifyPrefixListRequest): Promise<ModifyPrefixListResponse>;
     modifyPrepayInstanceSpecWithOptions(request: ModifyPrepayInstanceSpecRequest, runtime: $Util.RuntimeOptions): Promise<ModifyPrepayInstanceSpecResponse>;
     modifyPrepayInstanceSpec(request: ModifyPrepayInstanceSpecRequest): Promise<ModifyPrepayInstanceSpecResponse>;
@@ -32246,30 +32409,7 @@ export default class Client extends OpenApi {
     modifyReservedInstanceAttribute(request: ModifyReservedInstanceAttributeRequest): Promise<ModifyReservedInstanceAttributeResponse>;
     modifyReservedInstanceAutoRenewAttributeWithOptions(request: ModifyReservedInstanceAutoRenewAttributeRequest, runtime: $Util.RuntimeOptions): Promise<ModifyReservedInstanceAutoRenewAttributeResponse>;
     modifyReservedInstanceAutoRenewAttribute(request: ModifyReservedInstanceAutoRenewAttributeRequest): Promise<ModifyReservedInstanceAutoRenewAttributeResponse>;
-    /**
-      * ## Description
-      * When you call this operation, take note of the following items:
-      * *   For information about limits on reserved instances, see the "Limits" section in [Overview](~~100370~~).
-      * *   If you call this operation to split a reserved instance, make sure that you fully understand the limits on splitting a reserved instance. For more information, see [Split a reserved instance](~~100375~~).
-      * *   If you call this operation to merge reserved instances, make sure that you fully understand the limits on merging reserved instances. For more information, see [Merge reserved instances](~~132229~~).
-      * *   If you call this operation to modify a reserved instance, make sure that you fully understand the limits on and methods of modifying a reserved instance. For more information, see [Modify a reserved instance](~~132230~~).
-      *
-      * @param request ModifyReservedInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyReservedInstancesResponse
-     */
     modifyReservedInstancesWithOptions(request: ModifyReservedInstancesRequest, runtime: $Util.RuntimeOptions): Promise<ModifyReservedInstancesResponse>;
-    /**
-      * ## Description
-      * When you call this operation, take note of the following items:
-      * *   For information about limits on reserved instances, see the "Limits" section in [Overview](~~100370~~).
-      * *   If you call this operation to split a reserved instance, make sure that you fully understand the limits on splitting a reserved instance. For more information, see [Split a reserved instance](~~100375~~).
-      * *   If you call this operation to merge reserved instances, make sure that you fully understand the limits on merging reserved instances. For more information, see [Merge reserved instances](~~132229~~).
-      * *   If you call this operation to modify a reserved instance, make sure that you fully understand the limits on and methods of modifying a reserved instance. For more information, see [Modify a reserved instance](~~132230~~).
-      *
-      * @param request ModifyReservedInstancesRequest
-      * @return ModifyReservedInstancesResponse
-     */
     modifyReservedInstances(request: ModifyReservedInstancesRequest): Promise<ModifyReservedInstancesResponse>;
     /**
       * @deprecated
@@ -32392,26 +32532,34 @@ export default class Client extends OpenApi {
       * @return ModifyVpcAttributeResponse
      */
     modifyVpcAttribute(request: ModifyVpcAttributeRequest): Promise<ModifyVpcAttributeResponse>;
+    purchaseReservedInstancesOfferingWithOptions(request: PurchaseReservedInstancesOfferingRequest, runtime: $Util.RuntimeOptions): Promise<PurchaseReservedInstancesOfferingResponse>;
+    purchaseReservedInstancesOffering(request: PurchaseReservedInstancesOfferingRequest): Promise<PurchaseReservedInstancesOfferingResponse>;
+    purchaseStorageCapacityUnitWithOptions(request: PurchaseStorageCapacityUnitRequest, runtime: $Util.RuntimeOptions): Promise<PurchaseStorageCapacityUnitResponse>;
+    purchaseStorageCapacityUnit(request: PurchaseStorageCapacityUnitRequest): Promise<PurchaseStorageCapacityUnitResponse>;
     /**
-      * *   Before you call this operation, make sure that you understand how reserved instances are billed. For more information, see [Reserved instances](~~100371~~).
-      * *   Before you purchase a reserved instance, you can call the [DescribeAvailableResource](~~66186~~) operation to query available instance resources.
+      * When you call this operation, take note of the following points:
+      * *   The instance must be in the **Expired** (`Stopped`) or **Overdue and Being Recycled** (`Stopped`) state.
+      * *   To continue using instances in these states, you must reactivate the instances within 15 days of settling any overdue payments. If you do not reactivate the instance within the aforementioned time, data on the instance can no longer be recovered. This operation may fail on pay-as-you-go instance of the Virtual Private Cloud (VPC) type. To solve this problem, try again several minutes later or [submit a ticket](https://selfservice.console.aliyun.com/ticket/createIndex.htm).
+      * *   After you settle all overdue payments, make sure that the total of your balance, vouchers, and coupons within your Alibaba Cloud account is 100 RMB or more. Otherwise, you may not be able to reactivate the instance. For more information, see [Reboot an instance](~~34374~~).
+      * *   After the operation is called, the instance enters the `Starting` state.
+      * *   You cannot call this operation on ECS instances that are locked for security reasons. An instance is locked for security reasons if `OperationLocks` in the response returned when you query information of the instance contains `"LockReason": "security"`. For more information, see [API behavior when an instance is locked for security reasons](~~25695~~).
       *
-      * @param request PurchaseReservedInstancesOfferingRequest
+      * @param request ReActivateInstancesRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return PurchaseReservedInstancesOfferingResponse
+      * @return ReActivateInstancesResponse
      */
-    purchaseReservedInstancesOfferingWithOptions(request: PurchaseReservedInstancesOfferingRequest, runtime: $Util.RuntimeOptions): Promise<PurchaseReservedInstancesOfferingResponse>;
+    reActivateInstancesWithOptions(request: ReActivateInstancesRequest, runtime: $Util.RuntimeOptions): Promise<ReActivateInstancesResponse>;
     /**
-      * *   Before you call this operation, make sure that you understand how reserved instances are billed. For more information, see [Reserved instances](~~100371~~).
-      * *   Before you purchase a reserved instance, you can call the [DescribeAvailableResource](~~66186~~) operation to query available instance resources.
+      * When you call this operation, take note of the following points:
+      * *   The instance must be in the **Expired** (`Stopped`) or **Overdue and Being Recycled** (`Stopped`) state.
+      * *   To continue using instances in these states, you must reactivate the instances within 15 days of settling any overdue payments. If you do not reactivate the instance within the aforementioned time, data on the instance can no longer be recovered. This operation may fail on pay-as-you-go instance of the Virtual Private Cloud (VPC) type. To solve this problem, try again several minutes later or [submit a ticket](https://selfservice.console.aliyun.com/ticket/createIndex.htm).
+      * *   After you settle all overdue payments, make sure that the total of your balance, vouchers, and coupons within your Alibaba Cloud account is 100 RMB or more. Otherwise, you may not be able to reactivate the instance. For more information, see [Reboot an instance](~~34374~~).
+      * *   After the operation is called, the instance enters the `Starting` state.
+      * *   You cannot call this operation on ECS instances that are locked for security reasons. An instance is locked for security reasons if `OperationLocks` in the response returned when you query information of the instance contains `"LockReason": "security"`. For more information, see [API behavior when an instance is locked for security reasons](~~25695~~).
       *
-      * @param request PurchaseReservedInstancesOfferingRequest
-      * @return PurchaseReservedInstancesOfferingResponse
+      * @param request ReActivateInstancesRequest
+      * @return ReActivateInstancesResponse
      */
-    purchaseReservedInstancesOffering(request: PurchaseReservedInstancesOfferingRequest): Promise<PurchaseReservedInstancesOfferingResponse>;
-    purchaseStorageCapacityUnitWithOptions(request: PurchaseStorageCapacityUnitRequest, runtime: $Util.RuntimeOptions): Promise<PurchaseStorageCapacityUnitResponse>;
-    purchaseStorageCapacityUnit(request: PurchaseStorageCapacityUnitRequest): Promise<PurchaseStorageCapacityUnitResponse>;
-    reActivateInstancesWithOptions(request: ReActivateInstancesRequest, runtime: $Util.RuntimeOptions): Promise<ReActivateInstancesResponse>;
     reActivateInstances(request: ReActivateInstancesRequest): Promise<ReActivateInstancesResponse>;
     reInitDiskWithOptions(request: ReInitDiskRequest, runtime: $Util.RuntimeOptions): Promise<ReInitDiskResponse>;
     reInitDisk(request: ReInitDiskRequest): Promise<ReInitDiskResponse>;
@@ -32437,11 +32585,10 @@ export default class Client extends OpenApi {
      */
     rebootInstance(request: RebootInstanceRequest): Promise<RebootInstanceResponse>;
     /**
-      * ## Description
-      * *   The ECS instances to be restarted must be in the **Running** (`Running`) state.
-      * *   Batch operations are supported. You can use the `BatchOptimization` parameter to specify the batch operation mode.
-      * *   Instances can be forcibly restarted. A forced restart (`ForceStop`) is equivalent to powering off traditional servers to restart them. This operation can cause data loss if data in the instance is not written to Elastic Block Storage devices.
-      * *   If the response contains`{"OperationLocks": {"LockReason" : "security"}}` when you query information of an instance, the instance is locked for security reasons and all operations are prohibited on the instance.
+      * *   The ECS instances to which you want to restart are in the **Running** (`Running`) state.
+      * *   You can restart multiple instances at a time and use the `BatchOptimization` parameter to specify the batch operation mode.
+      * *   Instances can be forcefully restarted. A force restart (`ForceStop`) is equivalent to powering off traditional servers to restart them. This operation may lead to data loss if data in the instance operating system is not written to block storage devices.
+      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}` when you query the information of the instance, the instance is locked for security reasons and all operations are prohibited on it.
       *
       * @param request RebootInstancesRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -32449,11 +32596,10 @@ export default class Client extends OpenApi {
      */
     rebootInstancesWithOptions(request: RebootInstancesRequest, runtime: $Util.RuntimeOptions): Promise<RebootInstancesResponse>;
     /**
-      * ## Description
-      * *   The ECS instances to be restarted must be in the **Running** (`Running`) state.
-      * *   Batch operations are supported. You can use the `BatchOptimization` parameter to specify the batch operation mode.
-      * *   Instances can be forcibly restarted. A forced restart (`ForceStop`) is equivalent to powering off traditional servers to restart them. This operation can cause data loss if data in the instance is not written to Elastic Block Storage devices.
-      * *   If the response contains`{"OperationLocks": {"LockReason" : "security"}}` when you query information of an instance, the instance is locked for security reasons and all operations are prohibited on the instance.
+      * *   The ECS instances to which you want to restart are in the **Running** (`Running`) state.
+      * *   You can restart multiple instances at a time and use the `BatchOptimization` parameter to specify the batch operation mode.
+      * *   Instances can be forcefully restarted. A force restart (`ForceStop`) is equivalent to powering off traditional servers to restart them. This operation may lead to data loss if data in the instance operating system is not written to block storage devices.
+      * *   If the response contains `{"OperationLocks": {"LockReason" : "security"}}` when you query the information of the instance, the instance is locked for security reasons and all operations are prohibited on it.
       *
       * @param request RebootInstancesRequest
       * @return RebootInstancesResponse
@@ -32480,20 +32626,7 @@ export default class Client extends OpenApi {
     redeployInstance(request: RedeployInstanceRequest): Promise<RedeployInstanceResponse>;
     releaseCapacityReservationWithOptions(request: ReleaseCapacityReservationRequest, runtime: $Util.RuntimeOptions): Promise<ReleaseCapacityReservationResponse>;
     releaseCapacityReservation(request: ReleaseCapacityReservationRequest): Promise<ReleaseCapacityReservationResponse>;
-    /**
-      * Before you release a pay-as-you-go dedicated host, make sure that no Elastic Compute Service (ECS) instances are deployed on the dedicated host.
-      *
-      * @param request ReleaseDedicatedHostRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ReleaseDedicatedHostResponse
-     */
     releaseDedicatedHostWithOptions(request: ReleaseDedicatedHostRequest, runtime: $Util.RuntimeOptions): Promise<ReleaseDedicatedHostResponse>;
-    /**
-      * Before you release a pay-as-you-go dedicated host, make sure that no Elastic Compute Service (ECS) instances are deployed on the dedicated host.
-      *
-      * @param request ReleaseDedicatedHostRequest
-      * @return ReleaseDedicatedHostResponse
-     */
     releaseDedicatedHost(request: ReleaseDedicatedHostRequest): Promise<ReleaseDedicatedHostResponse>;
     /**
       * @deprecated
@@ -32531,50 +32664,30 @@ export default class Client extends OpenApi {
     removeTags(request: RemoveTagsRequest): Promise<RemoveTagsResponse>;
     renewDedicatedHostsWithOptions(request: RenewDedicatedHostsRequest, runtime: $Util.RuntimeOptions): Promise<RenewDedicatedHostsResponse>;
     renewDedicatedHosts(request: RenewDedicatedHostsRequest): Promise<RenewDedicatedHostsResponse>;
-    renewInstanceWithOptions(request: RenewInstanceRequest, runtime: $Util.RuntimeOptions): Promise<RenewInstanceResponse>;
-    renewInstance(request: RenewInstanceRequest): Promise<RenewInstanceResponse>;
-    renewReservedInstancesWithOptions(request: RenewReservedInstancesRequest, runtime: $Util.RuntimeOptions): Promise<RenewReservedInstancesResponse>;
-    renewReservedInstances(request: RenewReservedInstancesRequest): Promise<RenewReservedInstancesResponse>;
     /**
-      * When you call this operation, take note of the following items:
-      * *   You must specify `ImageId` or `DiskId`. If both `ImageId` and `DiskId` are specified, only `DiskId` takes effect.
-      * > You can configure the `DiskId` parameter to replace the operating system of an instance. This feature is in invitational preview. To use this feature, [submit a ticket](https://selfservice.console.aliyun.com/ticket/createIndex).
-      * *   The category of the system disk cannot be changed.
-      * *   The billing method of the system disk cannot be changed.
-      * *   The instance must be in the Stopped (`Stopped`) state.
-      *     **
-      *     **Note**This item is applicable only to instances that reside in virtual private clouds (VPCs). If the instance is a pay-as-you-go instance and economical mode is enabled for the instance, you must set the stop mode to standard mode when you stop the instance. This ensures that the required resources are available for the instance to start after the system disk is replaced. For more information, see [StopInstance](~~25501~~).
-      * *   The instance must not be locked for security reasons. If the value of `OperationLocks` in the DescribeInstances response contains `"LockReason": "security"` for an instance, the instance is locked for security reasons. For more information, see [API behavior when an instance is locked for security reasons](~~25695~~).
-      * *   You cannot have unpaid orders for the instance.
-      * *   You can configure the `SystemDisk.Size` parameter to specify the capacity of the new system disk.
-      * After you call this operation, you can use one of the following methods to check whether the system disk is replaced:
-      * *   Call the [DescribeDisks](~~25514~~) operation to query the state of the new system disk. If the new system disk is in the In_use state, the system disk is replaced.
-      * *   Call the [DescribeInstances](~~25506~~) operation to query the state of the instance whose system disk is replaced. If the `OperationLocks` response parameter is empty, the system disk is replaced.
-      *
-      * @param request ReplaceSystemDiskRequest
+      * *   Before you call this operation, make sure that you are familiar with the billing methods and pricing schedule of ECS. For more information, see the [Elastic Compute Service](https://www.alibabacloud.com/product/ecs#pricing) product page.
+      * *   You can call this operation to renew a subscription ECS instance for a period of time or to a synchronized expiration date.
+      * *   You cannot renew a subscription instance for a specific period of time and to a synchronized expiration date at the same time by calling this operation. The parameter pair (`Period` and `PeriodUnit`) that is related to the renewal period and the `ExpectedRenewDay` parameter are mutually exclusive.
+      * *   Your account must have sufficient credits.
+      *
+      * @param request RenewInstanceRequest
       * @param runtime runtime options for this request RuntimeOptions
-      * @return ReplaceSystemDiskResponse
+      * @return RenewInstanceResponse
      */
-    replaceSystemDiskWithOptions(request: ReplaceSystemDiskRequest, runtime: $Util.RuntimeOptions): Promise<ReplaceSystemDiskResponse>;
+    renewInstanceWithOptions(request: RenewInstanceRequest, runtime: $Util.RuntimeOptions): Promise<RenewInstanceResponse>;
     /**
-      * When you call this operation, take note of the following items:
-      * *   You must specify `ImageId` or `DiskId`. If both `ImageId` and `DiskId` are specified, only `DiskId` takes effect.
-      * > You can configure the `DiskId` parameter to replace the operating system of an instance. This feature is in invitational preview. To use this feature, [submit a ticket](https://selfservice.console.aliyun.com/ticket/createIndex).
-      * *   The category of the system disk cannot be changed.
-      * *   The billing method of the system disk cannot be changed.
-      * *   The instance must be in the Stopped (`Stopped`) state.
-      *     **
-      *     **Note**This item is applicable only to instances that reside in virtual private clouds (VPCs). If the instance is a pay-as-you-go instance and economical mode is enabled for the instance, you must set the stop mode to standard mode when you stop the instance. This ensures that the required resources are available for the instance to start after the system disk is replaced. For more information, see [StopInstance](~~25501~~).
-      * *   The instance must not be locked for security reasons. If the value of `OperationLocks` in the DescribeInstances response contains `"LockReason": "security"` for an instance, the instance is locked for security reasons. For more information, see [API behavior when an instance is locked for security reasons](~~25695~~).
-      * *   You cannot have unpaid orders for the instance.
-      * *   You can configure the `SystemDisk.Size` parameter to specify the capacity of the new system disk.
-      * After you call this operation, you can use one of the following methods to check whether the system disk is replaced:
-      * *   Call the [DescribeDisks](~~25514~~) operation to query the state of the new system disk. If the new system disk is in the In_use state, the system disk is replaced.
-      * *   Call the [DescribeInstances](~~25506~~) operation to query the state of the instance whose system disk is replaced. If the `OperationLocks` response parameter is empty, the system disk is replaced.
-      *
-      * @param request ReplaceSystemDiskRequest
-      * @return ReplaceSystemDiskResponse
+      * *   Before you call this operation, make sure that you are familiar with the billing methods and pricing schedule of ECS. For more information, see the [Elastic Compute Service](https://www.alibabacloud.com/product/ecs#pricing) product page.
+      * *   You can call this operation to renew a subscription ECS instance for a period of time or to a synchronized expiration date.
+      * *   You cannot renew a subscription instance for a specific period of time and to a synchronized expiration date at the same time by calling this operation. The parameter pair (`Period` and `PeriodUnit`) that is related to the renewal period and the `ExpectedRenewDay` parameter are mutually exclusive.
+      * *   Your account must have sufficient credits.
+      *
+      * @param request RenewInstanceRequest
+      * @return RenewInstanceResponse
      */
+    renewInstance(request: RenewInstanceRequest): Promise<RenewInstanceResponse>;
+    renewReservedInstancesWithOptions(request: RenewReservedInstancesRequest, runtime: $Util.RuntimeOptions): Promise<RenewReservedInstancesResponse>;
+    renewReservedInstances(request: RenewReservedInstancesRequest): Promise<RenewReservedInstancesResponse>;
+    replaceSystemDiskWithOptions(request: ReplaceSystemDiskRequest, runtime: $Util.RuntimeOptions): Promise<ReplaceSystemDiskResponse>;
     replaceSystemDisk(request: ReplaceSystemDiskRequest): Promise<ReplaceSystemDiskResponse>;
     reportInstancesStatusWithOptions(request: ReportInstancesStatusRequest, runtime: $Util.RuntimeOptions): Promise<ReportInstancesStatusResponse>;
     reportInstancesStatus(request: ReportInstancesStatusRequest): Promise<ReportInstancesStatusResponse>;
@@ -32586,24 +32699,119 @@ export default class Client extends OpenApi {
     resizeDisk(request: ResizeDiskRequest): Promise<ResizeDiskResponse>;
     revokeSecurityGroupWithOptions(request: RevokeSecurityGroupRequest, runtime: $Util.RuntimeOptions): Promise<RevokeSecurityGroupResponse>;
     revokeSecurityGroup(request: RevokeSecurityGroupRequest): Promise<RevokeSecurityGroupResponse>;
+    /**
+      * ## Description
+      * In the security group-related API documents, outbound traffic refers to the traffic sent by the source and received by the destination.
+      * When you call this operation, take note of the following items:
+      * *   The `Permissions.N` prefix is added to some parameters to generate new parameters. Original parameters and corresponding parameters prefixed with Permissions.N cannot be specified together. We recommend that you use parameters prefixed with `Permissions.N`.
+      * *   If the specified outbound security group rule does not exist, the call to RevokeSecurityGroupEgress is successful but no security group rule is deleted.
+      * *   You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.
+      *     *   Parameters used to delete an outbound security group rule that controls access to a specified CIDR block: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, DestCidrIp, and SourceCidrIp (optional).
+      *         ```
+      *                 http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
+      *                 &SecurityGroupId=sg-bp67acfmxazb4ph***
+      *                 &Permissions.1.IpProtocol=TCP
+      *                 &Permissions.1.DestCidrIp=10.0.0.0/8
+      *                 &Permissions.1.PortRange=-22/22
+      *                 &Permissions.1.NicType=intranet
+      *                 &Permissions.1.Policy=accept
+      *                 &<Common request parameters>
+      *
+      *         ```
+      *     *   Parameters used to delete an outbound security group rule that controls access to another security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceCidrIp (optional), and DestGroupId.
+      *         ```
+      *                 http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
+      *                 &SecurityGroupId=sg-bp67acfmxazb4ph***
+      *                 &Permissions.1.DestGroupId=sg-bp67acfmxa123b****
+      *                 &Permissions.1.IpProtocol=TCP
+      *                 &Permissions.1.PortRange=22/22
+      *                 &Permissions.1.NicType=intranet
+      *                 &Permissions.1.Policy=accept
+      *                 &<Common request parameters>
+      *
+      *         ```
+      *     *   Parameters used to delete an outbound security group rule that controls access to a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceCidrIp (optional), and DestPrefixListId.
+      *         ```
+      *                 http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
+      *                 &SecurityGroupId=sg-bp67acfmxazb4ph***
+      *                 &Permissions.1.IpProtocol=TCP
+      *                 &Permissions.1.DestPrefixListId=pl-x1j1k5ykzqlixdcy****
+      *                 &Permissions.1.PortRange=-22/22
+      *                 &Permissions.1.NicType=intranet
+      *                 &Permissions.1.Policy=accept
+      *                 &<Common request parameters>
+      *
+      *         ```
+      *
+      * @param request RevokeSecurityGroupEgressRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return RevokeSecurityGroupEgressResponse
+     */
     revokeSecurityGroupEgressWithOptions(request: RevokeSecurityGroupEgressRequest, runtime: $Util.RuntimeOptions): Promise<RevokeSecurityGroupEgressResponse>;
+    /**
+      * ## Description
+      * In the security group-related API documents, outbound traffic refers to the traffic sent by the source and received by the destination.
+      * When you call this operation, take note of the following items:
+      * *   The `Permissions.N` prefix is added to some parameters to generate new parameters. Original parameters and corresponding parameters prefixed with Permissions.N cannot be specified together. We recommend that you use parameters prefixed with `Permissions.N`.
+      * *   If the specified outbound security group rule does not exist, the call to RevokeSecurityGroupEgress is successful but no security group rule is deleted.
+      * *   You can determine a security group rule by specifying one of the following groups of parameters. You cannot determine a security group rule by specifying only one parameter.
+      *     *   Parameters used to delete an outbound security group rule that controls access to a specified CIDR block: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, DestCidrIp, and SourceCidrIp (optional).
+      *         ```
+      *                 http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
+      *                 &SecurityGroupId=sg-bp67acfmxazb4ph***
+      *                 &Permissions.1.IpProtocol=TCP
+      *                 &Permissions.1.DestCidrIp=10.0.0.0/8
+      *                 &Permissions.1.PortRange=-22/22
+      *                 &Permissions.1.NicType=intranet
+      *                 &Permissions.1.Policy=accept
+      *                 &<Common request parameters>
+      *
+      *         ```
+      *     *   Parameters used to delete an outbound security group rule that controls access to another security group: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceCidrIp (optional), and DestGroupId.
+      *         ```
+      *                 http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
+      *                 &SecurityGroupId=sg-bp67acfmxazb4ph***
+      *                 &Permissions.1.DestGroupId=sg-bp67acfmxa123b****
+      *                 &Permissions.1.IpProtocol=TCP
+      *                 &Permissions.1.PortRange=22/22
+      *                 &Permissions.1.NicType=intranet
+      *                 &Permissions.1.Policy=accept
+      *                 &<Common request parameters>
+      *
+      *         ```
+      *     *   Parameters used to delete an outbound security group rule that controls access to a prefix list: IpProtocol, PortRange, SourcePortRange (optional), NicType, Policy, SourceCidrIp (optional), and DestPrefixListId.
+      *         ```
+      *                 http(s)://ecs.aliyuncs.com/?Action=RevokeSecurityGroupEgress
+      *                 &SecurityGroupId=sg-bp67acfmxazb4ph***
+      *                 &Permissions.1.IpProtocol=TCP
+      *                 &Permissions.1.DestPrefixListId=pl-x1j1k5ykzqlixdcy****
+      *                 &Permissions.1.PortRange=-22/22
+      *                 &Permissions.1.NicType=intranet
+      *                 &Permissions.1.Policy=accept
+      *                 &<Common request parameters>
+      *
+      *         ```
+      *
+      * @param request RevokeSecurityGroupEgressRequest
+      * @return RevokeSecurityGroupEgressResponse
+     */
     revokeSecurityGroupEgress(request: RevokeSecurityGroupEgressRequest): Promise<RevokeSecurityGroupEgressResponse>;
     /**
-      * Unlike the [CreateCommand](~~64844~~) and [InvokeCommand](~~64841~~) operation, RunCommand can be used to create and run a command within a single request.
-      * When you call this operation, take note of the following item:
+      * Compared with the [CreateCommand](~~64844~~) and [InvokeCommand](~~64841~~) operations, you can call the RunCommand operation once to create and run a command.
+      * When you call this operation, take note of the following items:
       * *   The instances on which you want to run a command must reside in a virtual private cloud (VPC).
       * *   The instances must be in the `Running` state.
       * *   The Cloud Assistant client must be installed on the instances. For more information, see [InstallCloudAssistant](~~85916~~).
       * *   Before you run a PowerShell command on a Windows instance, make sure that the PowerShell module is installed on the instance.
-      * *   If you want to specify a schedule by using a cron expression, you can set a time zone based on your requirements. If you do not set a time zone, the schedule is based on the system time of the instance. Make sure that the time or time zone of the instance meets your business requirements. For information about time zones, see [Configure the NTP service for ECS instances that run CentOS 6](~~92803~~) or [Configure the NTP service for Windows instances](~~51890~~).
-      * *   You can specify the `TimeOut` parameter to set the timeout period for executions of the command on instances. If an execution times out, the Cloud Assistant client forcefully terminates the command process.
-      *     *   When the one-time execution of a command times out, the execution state ([InvokeRecordStatus](~~64845~~)) of the command becomes Failed.
-      *     *   For a scheduled task, the timeout period takes effect on each execution of the command. The timeout of one execution does not affect the subsequent executions of the command. When a scheduled execution of a command times out, the execution state ([InvokeRecordStatus](~~64845~~)) of the command becomes Failed.
-      *     To ensure that scheduled tasks can run as expected, make sure that the version of the Cloud Assistant client is not earlier than the following ones. A scheduled task can run a command at a specified interval, only once at a specified time, or at designated times based on a cron expression with a specified year or time zone. If the `ClientNeedUpgrade` error code is returned, you must upgrade the Cloud Assistant client to the latest version. For more information, see [Update or disable updates for the Cloud Assistant client](~~134383~~).
+      * *   If you want to specify a schedule by using a cron expression, you can specify a time zone based on your business requirements. If you do not specify a time zone, the schedule is determined by the system time of the instance. Make sure that the time or time zone of the instance meets your business requirements. For information about time zones, see [Configure the NTP service for ECS instances that run CentOS 6](~~92803~~) or [Configure the NTP service for Windows instances](~~51890~~).
+      * *   You can specify the `TimeOut` parameter to specify a timeout period for executions of the command on instances. If an execution times out, the Cloud Assistant client forcibly terminates the command process.
+      *     *   If the one-time execution of a command times out, the execution state of the command changes to Failed. You can call the [InvokeRecordStatus](~~64845~~) operation to query the command execution state.
+      *     *   For a scheduled task, the timeout period takes effect on each execution of the command. When a command execution times out, the subsequent executions of the command are not affected. If a scheduled execution of a command times out, the execution state of the command changes to Failed. You can call the [InvokeRecordStatus](~~64845~~) operation to query the command execution state.
+      *     To ensure that scheduled tasks can run as expected, make sure that the version of the Cloud Assistant client is not earlier than the following versions. A scheduled task can run a command at a specific interval, only once at a specific time, or at specific times based on a cron expression that includes a specific year or time zone. If the `ClientNeedUpgrade` error code is returned, you must update the Cloud Assistant client to the latest version. For more information, see [Upgrade or disable upgrades for the Cloud Assistant client](~~134383~~).
       *           - Linux: 2.2.3.282
       *           - Windows: 2.1.3.282
       * *   Command executions may fail due to instance status exceptions, network exceptions, or exceptions on the Cloud Assistant client. If an execution fails, no execution information is generated.
-      * *   When `EnableParameter` is set to true, the custom parameter feature is enabled. When you set the `CommandContent` parameter, you can define custom parameters in the `{{parameter}}` format. Then, when the command is run, the key-value pairs of the custom parameters are passed in.
+      * *   If you set the `EnableParameter` parameter to true, the custom parameter feature is enabled. If you specify the `CommandContent` parameter, you can specify custom parameters in the `{{parameter}}` format. After the command is run, the key-value pairs of the custom parameters are passed in.
       * *   You can retain up to 500 to 10,000 Cloud Assistant commands in each region based on your ECS usage. You can call the [DescribeAccountAttribute](~~73772~~) operation to query quotas.
       *
       * @param tmpReq RunCommandRequest
@@ -32612,108 +32820,30 @@ export default class Client extends OpenApi {
      */
     runCommandWithOptions(tmpReq: RunCommandRequest, runtime: $Util.RuntimeOptions): Promise<RunCommandResponse>;
     /**
-      * Unlike the [CreateCommand](~~64844~~) and [InvokeCommand](~~64841~~) operation, RunCommand can be used to create and run a command within a single request.
-      * When you call this operation, take note of the following item:
+      * Compared with the [CreateCommand](~~64844~~) and [InvokeCommand](~~64841~~) operations, you can call the RunCommand operation once to create and run a command.
+      * When you call this operation, take note of the following items:
       * *   The instances on which you want to run a command must reside in a virtual private cloud (VPC).
       * *   The instances must be in the `Running` state.
       * *   The Cloud Assistant client must be installed on the instances. For more information, see [InstallCloudAssistant](~~85916~~).
       * *   Before you run a PowerShell command on a Windows instance, make sure that the PowerShell module is installed on the instance.
-      * *   If you want to specify a schedule by using a cron expression, you can set a time zone based on your requirements. If you do not set a time zone, the schedule is based on the system time of the instance. Make sure that the time or time zone of the instance meets your business requirements. For information about time zones, see [Configure the NTP service for ECS instances that run CentOS 6](~~92803~~) or [Configure the NTP service for Windows instances](~~51890~~).
-      * *   You can specify the `TimeOut` parameter to set the timeout period for executions of the command on instances. If an execution times out, the Cloud Assistant client forcefully terminates the command process.
-      *     *   When the one-time execution of a command times out, the execution state ([InvokeRecordStatus](~~64845~~)) of the command becomes Failed.
-      *     *   For a scheduled task, the timeout period takes effect on each execution of the command. The timeout of one execution does not affect the subsequent executions of the command. When a scheduled execution of a command times out, the execution state ([InvokeRecordStatus](~~64845~~)) of the command becomes Failed.
-      *     To ensure that scheduled tasks can run as expected, make sure that the version of the Cloud Assistant client is not earlier than the following ones. A scheduled task can run a command at a specified interval, only once at a specified time, or at designated times based on a cron expression with a specified year or time zone. If the `ClientNeedUpgrade` error code is returned, you must upgrade the Cloud Assistant client to the latest version. For more information, see [Update or disable updates for the Cloud Assistant client](~~134383~~).
+      * *   If you want to specify a schedule by using a cron expression, you can specify a time zone based on your business requirements. If you do not specify a time zone, the schedule is determined by the system time of the instance. Make sure that the time or time zone of the instance meets your business requirements. For information about time zones, see [Configure the NTP service for ECS instances that run CentOS 6](~~92803~~) or [Configure the NTP service for Windows instances](~~51890~~).
+      * *   You can specify the `TimeOut` parameter to specify a timeout period for executions of the command on instances. If an execution times out, the Cloud Assistant client forcibly terminates the command process.
+      *     *   If the one-time execution of a command times out, the execution state of the command changes to Failed. You can call the [InvokeRecordStatus](~~64845~~) operation to query the command execution state.
+      *     *   For a scheduled task, the timeout period takes effect on each execution of the command. When a command execution times out, the subsequent executions of the command are not affected. If a scheduled execution of a command times out, the execution state of the command changes to Failed. You can call the [InvokeRecordStatus](~~64845~~) operation to query the command execution state.
+      *     To ensure that scheduled tasks can run as expected, make sure that the version of the Cloud Assistant client is not earlier than the following versions. A scheduled task can run a command at a specific interval, only once at a specific time, or at specific times based on a cron expression that includes a specific year or time zone. If the `ClientNeedUpgrade` error code is returned, you must update the Cloud Assistant client to the latest version. For more information, see [Upgrade or disable upgrades for the Cloud Assistant client](~~134383~~).
       *           - Linux: 2.2.3.282
       *           - Windows: 2.1.3.282
       * *   Command executions may fail due to instance status exceptions, network exceptions, or exceptions on the Cloud Assistant client. If an execution fails, no execution information is generated.
-      * *   When `EnableParameter` is set to true, the custom parameter feature is enabled. When you set the `CommandContent` parameter, you can define custom parameters in the `{{parameter}}` format. Then, when the command is run, the key-value pairs of the custom parameters are passed in.
+      * *   If you set the `EnableParameter` parameter to true, the custom parameter feature is enabled. If you specify the `CommandContent` parameter, you can specify custom parameters in the `{{parameter}}` format. After the command is run, the key-value pairs of the custom parameters are passed in.
       * *   You can retain up to 500 to 10,000 Cloud Assistant commands in each region based on your ECS usage. You can call the [DescribeAccountAttribute](~~73772~~) operation to query quotas.
       *
       * @param request RunCommandRequest
       * @return RunCommandResponse
      */
     runCommand(request: RunCommandRequest): Promise<RunCommandResponse>;
-    /**
-      * * **Preparations**:
-      *     * The real-name verification is complete. For more information, see [Real-name verification](~~48263~~).
-      *     * Cost estimation: Learn about the billing methods of ECS resources. For more information, see [Billing overview](~~25398~~).
-      *     * Instance type selection: Call the [DescribeInstanceTypes](~~25620~~) operation to query the performance data of instance types, or see [Best practices for instance type selection](~~58291~~) to learn about how to select instance types.
-      *     * Query for available resources: Call the [DescribeAvailableResource](~~66186~~) operation to query available resources in a specific region or zone.
-      *     * Network planning: Make sure that you have security groups available for use. For more information, see [CreateSecurityGroup](~~25553~~). Before you create an instance of the Virtual Private Cloud (VPC) type, create a VPC in the region where you want to create the instance. For more information, see [Create a VPC](~~65430~~).
-      * * **Precautions**:
-      *     * You can create a maximum of 100 instances at a time.
-      *     * You can use the `AutoReleaseTime` parameter to set the time when you want the instances to be automatically released.
-      *     * After instances are created, you can call the [DescribeInstances](~~25506~~) operation to check their states.
-      *     * By default, instances automatically start after they are created. Instances are ready for use when they are in the Running (`Running`) state.
-      *     * As of November 27, 2020, the maximum bandwidth value available for you to create ECS instances or to change ECS instance configurations is subject to the throttling policy for your account. To increase the maximum bandwidth value, submit a ticket. The throttling policy imposes the following constraints: Within a single region, the total maximum bandwidth value of all instances that use the pay-by-traffic billing method for network usage cannot exceed 5 Gbit/s and that of all instances that use the pay-by-bandwidth billing method for network usage cannot exceed 50 Gbit/s.
-      *     * Different from the [CreateInstance](~~25499~~) operation, the `RunInstances` operation allows the system to assign public IP addresses to the new instances if you set the `InternetMaxBandwidthOut` parameter to a value greater than 0.
-      *     * When you call the RunInstances operation to create an instance, you can use one of the following methods to bind a primary elastic network interface (ENI) to the instance. Note that you can use only one of the methods to configure the primary ENI in each call. Otherwise, the call fails and an error message is returned. Specify parameters such as `SecurityGroupId`, `VSwitchId`, `PrivateIpAddress`, `NetworkInterfaceQueueNumber`, and `Ipv6AddressCount` to configure the primary ENI. Specify parameters that start with `NetworkInterface.N.` to configure the primary and secondary ENIs. If `NetworkInterface.N.InstanceType` is set to `Primary`, the primary ENI is bound to the instance. If `NetworkInterface.N.InstanceType` is set to `Secondary` or left empty, a secondary ENI is bound to the instance.
-      *     * After you call this operation, an error is returned if a parameter is invalid or if available resources are insufficient. For more information, see the "Error codes" section of this topic.
-      * > If the `QuotaExceed.ElasticQuota` error is returned when you call this operation, you have reached the maximum number of instances of the specified instance type that can be created within the specified region or the maximum number of vCPUs for all instance types in a zone. You can go to the [ECS console](https://ecs.console.aliyun.com/?spm=a2c8b.12215451.favorites.decs.5e3a336aMGTtzy#/privileges/quota) or [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas) to request a quota increase.
-      * * **Best practices**:
-      *     * We recommend that you use auto provisioning groups in the following scenarios: Resources are insufficient to create more than 100 instances at a time, you want to quickly create instances regardless of resource configurations such as instance types or zones, or you want to create instances to consume a specific total number of vCPUs regardless of the number of the instances. You can call the [CreateAutoProvisioningGroup](~~122738~~) operation to create an auto provisioning group to deploy an instance cluster across different billing methods, instance families, and zones. For more information, see [Use auto provisioning group-related API operations to create multiple ECS instances at the same time](~~200772~~).
-      *     * You can call the `RunInstances` operation to batch create instances. To better manage and search for these instances, we recommend that you specify tags for the instances by using the `Tag.N.Key` and `Tag.N.Value` parameters. You can also append incremental suffixes (`UniqueSuffix`) to the hostname (`HostName`) and to the instance name (`InstanceName`).
-      *     * A launch template contains parameters required to create an instance so that you do not have to specify these parameters every time you create instances. You can call the [CreateLaunchTemplate](~~74686~~) operation to create a launch template. Then, in your request to call the `RunInstances` operation, you can specify the `LaunchTemplateId` and `LaunchTemplateVersion` parameters to use the launch template.
-      *     * When you create an instance in the [ECS console](https://ecs.console.aliyun.com/), you can view the best practices for calling the `RunInstances` operation. In the Preview step, click View Open API in the Configurations Selected section. In the dialog box that appears, the left-side **API Workflow** section shows the operations and request parameters that are related to the `RunInstances` operation. The right-side section shows SDK examples for the **Java** and **Python** programming languages.
-      *
-      * @param request RunInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return RunInstancesResponse
-     */
     runInstancesWithOptions(request: RunInstancesRequest, runtime: $Util.RuntimeOptions): Promise<RunInstancesResponse>;
-    /**
-      * * **Preparations**:
-      *     * The real-name verification is complete. For more information, see [Real-name verification](~~48263~~).
-      *     * Cost estimation: Learn about the billing methods of ECS resources. For more information, see [Billing overview](~~25398~~).
-      *     * Instance type selection: Call the [DescribeInstanceTypes](~~25620~~) operation to query the performance data of instance types, or see [Best practices for instance type selection](~~58291~~) to learn about how to select instance types.
-      *     * Query for available resources: Call the [DescribeAvailableResource](~~66186~~) operation to query available resources in a specific region or zone.
-      *     * Network planning: Make sure that you have security groups available for use. For more information, see [CreateSecurityGroup](~~25553~~). Before you create an instance of the Virtual Private Cloud (VPC) type, create a VPC in the region where you want to create the instance. For more information, see [Create a VPC](~~65430~~).
-      * * **Precautions**:
-      *     * You can create a maximum of 100 instances at a time.
-      *     * You can use the `AutoReleaseTime` parameter to set the time when you want the instances to be automatically released.
-      *     * After instances are created, you can call the [DescribeInstances](~~25506~~) operation to check their states.
-      *     * By default, instances automatically start after they are created. Instances are ready for use when they are in the Running (`Running`) state.
-      *     * As of November 27, 2020, the maximum bandwidth value available for you to create ECS instances or to change ECS instance configurations is subject to the throttling policy for your account. To increase the maximum bandwidth value, submit a ticket. The throttling policy imposes the following constraints: Within a single region, the total maximum bandwidth value of all instances that use the pay-by-traffic billing method for network usage cannot exceed 5 Gbit/s and that of all instances that use the pay-by-bandwidth billing method for network usage cannot exceed 50 Gbit/s.
-      *     * Different from the [CreateInstance](~~25499~~) operation, the `RunInstances` operation allows the system to assign public IP addresses to the new instances if you set the `InternetMaxBandwidthOut` parameter to a value greater than 0.
-      *     * When you call the RunInstances operation to create an instance, you can use one of the following methods to bind a primary elastic network interface (ENI) to the instance. Note that you can use only one of the methods to configure the primary ENI in each call. Otherwise, the call fails and an error message is returned. Specify parameters such as `SecurityGroupId`, `VSwitchId`, `PrivateIpAddress`, `NetworkInterfaceQueueNumber`, and `Ipv6AddressCount` to configure the primary ENI. Specify parameters that start with `NetworkInterface.N.` to configure the primary and secondary ENIs. If `NetworkInterface.N.InstanceType` is set to `Primary`, the primary ENI is bound to the instance. If `NetworkInterface.N.InstanceType` is set to `Secondary` or left empty, a secondary ENI is bound to the instance.
-      *     * After you call this operation, an error is returned if a parameter is invalid or if available resources are insufficient. For more information, see the "Error codes" section of this topic.
-      * > If the `QuotaExceed.ElasticQuota` error is returned when you call this operation, you have reached the maximum number of instances of the specified instance type that can be created within the specified region or the maximum number of vCPUs for all instance types in a zone. You can go to the [ECS console](https://ecs.console.aliyun.com/?spm=a2c8b.12215451.favorites.decs.5e3a336aMGTtzy#/privileges/quota) or [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas) to request a quota increase.
-      * * **Best practices**:
-      *     * We recommend that you use auto provisioning groups in the following scenarios: Resources are insufficient to create more than 100 instances at a time, you want to quickly create instances regardless of resource configurations such as instance types or zones, or you want to create instances to consume a specific total number of vCPUs regardless of the number of the instances. You can call the [CreateAutoProvisioningGroup](~~122738~~) operation to create an auto provisioning group to deploy an instance cluster across different billing methods, instance families, and zones. For more information, see [Use auto provisioning group-related API operations to create multiple ECS instances at the same time](~~200772~~).
-      *     * You can call the `RunInstances` operation to batch create instances. To better manage and search for these instances, we recommend that you specify tags for the instances by using the `Tag.N.Key` and `Tag.N.Value` parameters. You can also append incremental suffixes (`UniqueSuffix`) to the hostname (`HostName`) and to the instance name (`InstanceName`).
-      *     * A launch template contains parameters required to create an instance so that you do not have to specify these parameters every time you create instances. You can call the [CreateLaunchTemplate](~~74686~~) operation to create a launch template. Then, in your request to call the `RunInstances` operation, you can specify the `LaunchTemplateId` and `LaunchTemplateVersion` parameters to use the launch template.
-      *     * When you create an instance in the [ECS console](https://ecs.console.aliyun.com/), you can view the best practices for calling the `RunInstances` operation. In the Preview step, click View Open API in the Configurations Selected section. In the dialog box that appears, the left-side **API Workflow** section shows the operations and request parameters that are related to the `RunInstances` operation. The right-side section shows SDK examples for the **Java** and **Python** programming languages.
-      *
-      * @param request RunInstancesRequest
-      * @return RunInstancesResponse
-     */
     runInstances(request: RunInstancesRequest): Promise<RunInstancesResponse>;
-    /**
-      * * The instances to which to send a file must be in the Running (`Running`) state.
-      * * The Cloud Assistant client must be installed on the instances. For information about how to install the Cloud Assistant client, see [InstallCloudAssistant](~~85916~~).
-      * * Only the Cloud Assistant client versions that are later than the following ones support file sending. If the `ClientNeedUpgrade` error code is returned, you must upgrade the Cloud Assistant client to the latest version. For more information, see [Update or disable updates for the Cloud Assistant client](~~134383~~).
-      *     * For Linux instances, the version of the Cloud Assistant client must be later than 1.0.2.569.
-      *     * For Windows instances, the version of the Cloud Assistant client must be later than 1.0.0.149.
-      * * The file to be sent must not exceed 32 KB in size after it is encoded in Base64.
-      * * The file may fail to be sent due to exceptions on the instances, network, or the Cloud Assistance client. Call the [DescribeSendFileResults](~~~~) operation to troubleshoot the issues.
-      *
-      * @param request SendFileRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return SendFileResponse
-     */
     sendFileWithOptions(request: SendFileRequest, runtime: $Util.RuntimeOptions): Promise<SendFileResponse>;
-    /**
-      * * The instances to which to send a file must be in the Running (`Running`) state.
-      * * The Cloud Assistant client must be installed on the instances. For information about how to install the Cloud Assistant client, see [InstallCloudAssistant](~~85916~~).
-      * * Only the Cloud Assistant client versions that are later than the following ones support file sending. If the `ClientNeedUpgrade` error code is returned, you must upgrade the Cloud Assistant client to the latest version. For more information, see [Update or disable updates for the Cloud Assistant client](~~134383~~).
-      *     * For Linux instances, the version of the Cloud Assistant client must be later than 1.0.2.569.
-      *     * For Windows instances, the version of the Cloud Assistant client must be later than 1.0.0.149.
-      * * The file to be sent must not exceed 32 KB in size after it is encoded in Base64.
-      * * The file may fail to be sent due to exceptions on the instances, network, or the Cloud Assistance client. Call the [DescribeSendFileResults](~~~~) operation to troubleshoot the issues.
-      *
-      * @param request SendFileRequest
-      * @return SendFileResponse
-     */
     sendFile(request: SendFileRequest): Promise<SendFileResponse>;
     /**
       * @deprecated
@@ -32744,20 +32874,7 @@ export default class Client extends OpenApi {
     stopInstances(request: StopInstancesRequest): Promise<StopInstancesResponse>;
     stopInvocationWithOptions(request: StopInvocationRequest, runtime: $Util.RuntimeOptions): Promise<StopInvocationResponse>;
     stopInvocation(request: StopInvocationRequest): Promise<StopInvocationResponse>;
-    /**
-      * Before you add tags to a resource, Alibaba Cloud checks the number of existing tags of the resource. If the maximum number of tags is reached, an error message is returned. For more information, see the "Tag limits" section in [Limits](~~25412~~).
-      *
-      * @param request TagResourcesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return TagResourcesResponse
-     */
     tagResourcesWithOptions(request: TagResourcesRequest, runtime: $Util.RuntimeOptions): Promise<TagResourcesResponse>;
-    /**
-      * Before you add tags to a resource, Alibaba Cloud checks the number of existing tags of the resource. If the maximum number of tags is reached, an error message is returned. For more information, see the "Tag limits" section in [Limits](~~25412~~).
-      *
-      * @param request TagResourcesRequest
-      * @return TagResourcesResponse
-     */
     tagResources(request: TagResourcesRequest): Promise<TagResourcesResponse>;
     /**
       * @deprecated
@@ -32789,9 +32906,41 @@ export default class Client extends OpenApi {
       * @return TerminateVirtualBorderRouterResponse
      */
     terminateVirtualBorderRouter(request: TerminateVirtualBorderRouterRequest): Promise<TerminateVirtualBorderRouterResponse>;
+    /**
+      * When you call this operation, take note of the following items:
+      * *   The ENI must be in the **Available** (Available) or **InUse** (InUse) state.
+      * *   If the ENI is 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.
+      *
+      * @param request UnassignIpv6AddressesRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return UnassignIpv6AddressesResponse
+     */
     unassignIpv6AddressesWithOptions(request: UnassignIpv6AddressesRequest, runtime: $Util.RuntimeOptions): Promise<UnassignIpv6AddressesResponse>;
+    /**
+      * When you call this operation, take note of the following items:
+      * *   The ENI must be in the **Available** (Available) or **InUse** (InUse) state.
+      * *   If the ENI is 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.
+      *
+      * @param request UnassignIpv6AddressesRequest
+      * @return UnassignIpv6AddressesResponse
+     */
     unassignIpv6Addresses(request: UnassignIpv6AddressesRequest): Promise<UnassignIpv6AddressesResponse>;
+    /**
+      * *   The ENI from which to unassign secondary private IP addresses must be in the **Available** (Available) or **InUse** (InUse) state.
+      * *   If the ENI is 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.
+      *
+      * @param request UnassignPrivateIpAddressesRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return UnassignPrivateIpAddressesResponse
+     */
     unassignPrivateIpAddressesWithOptions(request: UnassignPrivateIpAddressesRequest, runtime: $Util.RuntimeOptions): Promise<UnassignPrivateIpAddressesResponse>;
+    /**
+      * *   The ENI from which to unassign secondary private IP addresses must be in the **Available** (Available) or **InUse** (InUse) state.
+      * *   If the ENI is 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.
+      *
+      * @param request UnassignPrivateIpAddressesRequest
+      * @return UnassignPrivateIpAddressesResponse
+     */
     unassignPrivateIpAddresses(request: UnassignPrivateIpAddressesRequest): Promise<UnassignPrivateIpAddressesResponse>;
     /**
       * @deprecated