@alicloud/ecs20140526 7.0.0 → 7.0.1

package/dist/client.d.ts

@@ -881,6 +881,10 @@ export declare class CreateAutoProvisioningGroupRequestLaunchConfigurationArn ex
     });
 }
 export declare class CreateAutoProvisioningGroupRequestLaunchConfigurationDataDisk extends $dara.Model {
+    /**
+     * @example
+     * sp-bp67acfmxazb4p****
+     */
     autoSnapshotPolicyId?: string;
     /**
      * @remarks
@@ -1064,6 +1068,10 @@ export declare class CreateAutoProvisioningGroupRequestLaunchConfigurationDataDi
     });
 }
 export declare class CreateAutoProvisioningGroupRequestLaunchConfigurationSystemDisk extends $dara.Model {
+    /**
+     * @example
+     * sp-bp67acfmxazb4p****
+     */
     autoSnapshotPolicyId?: string;
     /**
      * @remarks
@@ -1172,6 +1180,10 @@ export declare class CreateAutoProvisioningGroupRequestLaunchConfigurationTag ex
     });
 }
 export declare class CreateAutoProvisioningGroupRequestLaunchConfigurationImageOptions extends $dara.Model {
+    /**
+     * @example
+     * false
+     */
     loginAsNonRoot?: boolean;
     static names(): {
         [key: string]: string;
@@ -1561,7 +1573,15 @@ export declare class CreateAutoProvisioningGroupRequestLaunchConfiguration exten
      * Month
      */
     periodUnit?: string;
+    /**
+     * @example
+     * 1
+     */
     spotDuration?: number;
+    /**
+     * @example
+     * Terminate
+     */
     spotInterruptionBehavior?: string;
     static names(): {
         [key: string]: string;
@@ -1639,7 +1659,7 @@ export declare class CreateAutoProvisioningGroupRequestLaunchTemplateConfig exte
     imageId?: string;
     /**
      * @remarks
-     * The instance family level of the instance type in extended configuration N. This parameter is used to filter instance types. Valid values of Nextended configuration N， Valid values:
+     * The instance family level of the instance type in extended configuration N. This parameter is used to filter instance types. Valid values of Nextended configuration N, Valid values:
      *
      * *   EntryLevel: entry level (shared instance types). Instance types of this level are the most cost-effective but may not ensure stable computing performance. Instance types of this level are suitable for scenarios in which the CPU utilization is low. For more information, see [Shared instance families](https://help.aliyun.com/document_detail/108489.html).
      * *   EnterpriseLevel: enterprise level. Instance types of this level provide stable performance and dedicated resources and are suitable for business scenarios that require high stability. For more information, see [Overview of instance families](https://help.aliyun.com/document_detail/25378.html).
@@ -1893,6 +1913,10 @@ export declare class CreateAutoProvisioningGroupShrinkRequestLaunchConfiguration
     });
 }
 export declare class CreateAutoProvisioningGroupShrinkRequestLaunchConfigurationDataDisk extends $dara.Model {
+    /**
+     * @example
+     * sp-bp67acfmxazb4p****
+     */
     autoSnapshotPolicyId?: string;
     /**
      * @remarks
@@ -2076,6 +2100,10 @@ export declare class CreateAutoProvisioningGroupShrinkRequestLaunchConfiguration
     });
 }
 export declare class CreateAutoProvisioningGroupShrinkRequestLaunchConfigurationSystemDisk extends $dara.Model {
+    /**
+     * @example
+     * sp-bp67acfmxazb4p****
+     */
     autoSnapshotPolicyId?: string;
     /**
      * @remarks
@@ -2184,6 +2212,10 @@ export declare class CreateAutoProvisioningGroupShrinkRequestLaunchConfiguration
     });
 }
 export declare class CreateAutoProvisioningGroupShrinkRequestLaunchConfigurationImageOptions extends $dara.Model {
+    /**
+     * @example
+     * false
+     */
     loginAsNonRoot?: boolean;
     static names(): {
         [key: string]: string;
@@ -2573,7 +2605,15 @@ export declare class CreateAutoProvisioningGroupShrinkRequestLaunchConfiguration
      * Month
      */
     periodUnit?: string;
+    /**
+     * @example
+     * 1
+     */
     spotDuration?: number;
+    /**
+     * @example
+     * Terminate
+     */
     spotInterruptionBehavior?: string;
     static names(): {
         [key: string]: string;
@@ -2651,7 +2691,7 @@ export declare class CreateAutoProvisioningGroupShrinkRequestLaunchTemplateConfi
     imageId?: string;
     /**
      * @remarks
-     * The instance family level of the instance type in extended configuration N. This parameter is used to filter instance types. Valid values of Nextended configuration N， Valid values:
+     * The instance family level of the instance type in extended configuration N. This parameter is used to filter instance types. Valid values of Nextended configuration N, Valid values:
      *
      * *   EntryLevel: entry level (shared instance types). Instance types of this level are the most cost-effective but may not ensure stable computing performance. Instance types of this level are suitable for scenarios in which the CPU utilization is low. For more information, see [Shared instance families](https://help.aliyun.com/document_detail/108489.html).
      * *   EnterpriseLevel: enterprise level. Instance types of this level provide stable performance and dedicated resources and are suitable for business scenarios that require high stability. For more information, see [Overview of instance families](https://help.aliyun.com/document_detail/25378.html).
@@ -5741,6 +5781,20 @@ export declare class CreatePrefixListRequestEntry extends $dara.Model {
         [key: string]: any;
     });
 }
+export declare class CreatePrefixListRequestTag extends $dara.Model {
+    key?: string;
+    value?: string;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    validate(): void;
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class CreateRouteEntryRequestNextHopList extends $dara.Model {
     nextHopId?: string;
     nextHopType?: string;
@@ -23205,6 +23259,47 @@ export declare class DescribePrefixListAttributesResponseBodyEntries extends $da
         [key: string]: any;
     });
 }
+export declare class DescribePrefixListsRequestTag extends $dara.Model {
+    key?: string;
+    value?: string;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    validate(): void;
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
+export declare class DescribePrefixListsResponseBodyPrefixListsPrefixListTagsTag extends $dara.Model {
+    tagKey?: string;
+    tagValue?: string;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    validate(): void;
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
+export declare class DescribePrefixListsResponseBodyPrefixListsPrefixListTags extends $dara.Model {
+    tag?: DescribePrefixListsResponseBodyPrefixListsPrefixListTagsTag[];
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    validate(): void;
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class DescribePrefixListsResponseBodyPrefixListsPrefixList extends $dara.Model {
     /**
      * @remarks
@@ -23265,6 +23360,8 @@ export declare class DescribePrefixListsResponseBodyPrefixListsPrefixList extend
      * PrefixListNameSample
      */
     prefixListName?: string;
+    resourceGroupId?: string;
+    tags?: DescribePrefixListsResponseBodyPrefixListsPrefixListTags;
     static names(): {
         [key: string]: string;
     };
@@ -32286,6 +32383,8 @@ export declare class RunInstancesRequestSystemDisk extends $dara.Model {
      *
      * >  The system disks of instances cannot be encrypted during instance creation in Hong Kong Zone D or Singapore Zone A.
      *
+     * >  When you use a shared encrypted image to create the disk based on an encrypted snapshot, you must set Encrypted to true to ensure that the disk uses an encryption key of your own.
+     *
      * @example
      * false
      */
@@ -32302,7 +32401,7 @@ export declare class RunInstancesRequestSystemDisk extends $dara.Model {
      * @remarks
      * The provisioned read/write IOPS of the ESSD AutoPL disk to use as the system disk. Valid values: 0 to min{50,000, 1,000 × Capacity - Baseline IOPS}.
      *
-     * Baseline IOPS = min{1,800 + 50 × Capacity, 50,000}
+     * Baseline IOPS = min{1,800 + 50 × Capacity, 50,000}.
      *
      * >  This parameter is available only if you set `SystemDisk.Category` to `cloud_auto`. For more information, see [ESSD AutoPL disks](https://help.aliyun.com/document_detail/368372.html).
      *
@@ -32378,8 +32477,8 @@ export declare class RunInstancesRequestDataDisk extends $dara.Model {
      * @remarks
      * Specifies whether to enable the performance burst feature for data disk N. Valid values:
      *
-     * *   true
-     * *   false
+     * *   true: enables the performance burst feature for the data disk.
+     * *   false: disables the performance burst feature for the data disk.
      *
      * >  This parameter is available only if you set DataDisk.N.Category to cloud_auto. For more information, see [ESSD AutoPL disks](https://help.aliyun.com/document_detail/368372.html).
      *
@@ -32391,25 +32490,25 @@ export declare class RunInstancesRequestDataDisk extends $dara.Model {
      * @remarks
      * The category of data disk N. Valid values:
      *
-     * *   cloud_efficiency: ultra disk
+     * *   cloud_efficiency: ultra disk.
      *
-     * *   cloud_ssd: standard SSD
+     * *   cloud_ssd: standard SSD.
      *
-     * *   cloud_essd: ESSD
+     * *   cloud_essd: ESSD.
      *
-     * *   cloud: basic disk
+     * *   cloud: basic disk.
      *
-     * *   cloud_auto: ESSD AutoPL disk
+     * *   cloud_auto: ESSD AutoPL disk.
      *
-     * *   cloud_essd_entry: ESSD Entry disk
+     * *   cloud_essd_entry: ESSD Entry disk.
      *
      *     **
      *
      *     **Note** This parameter can be set to `cloud_essd_entry` only when `InstanceType` is set to `ecs.u1` or `ecs.e`.
      *
-     * *   elastic_ephemeral_disk_standard: standard elastic ephemeral disk
+     * *   elastic_ephemeral_disk_standard: standard elastic ephemeral disk.
      *
-     * *   elastic_ephemeral_disk_premium: premium elastic ephemeral disk
+     * *   elastic_ephemeral_disk_premium: premium elastic ephemeral disk.
      *
      * For I/O optimized instances, the default value is cloud_efficiency. For non-I/O optimized instances, the default value is cloud.
      *
@@ -32419,10 +32518,10 @@ export declare class RunInstancesRequestDataDisk extends $dara.Model {
     category?: string;
     /**
      * @remarks
-     * Specifies whether to release data disk N when the instance is released. Valid values:
+     * Specifies whether to release data disk N when the associated instance is released. Valid values:
      *
-     * *   true
-     * *   false
+     * *   true: releases the data disk when the associated instance is released.
+     * *   false: does not release the data disk when the associated instance is released.
      *
      * Default value: true.
      *
@@ -32445,7 +32544,7 @@ export declare class RunInstancesRequestDataDisk extends $dara.Model {
      * *   1st to 25th data disks: /dev/xvd`[b-z]`.
      * *   From the 26th data disk on: /dev/xvd`[aa-zz]`. For example, the 26th data disk is named /dev/xvdaa, the 27th data disk is named /dev/xvdab, and so on.
      *
-     * >  This parameter is applicable to scenarios in which a full image is used to create instances. A full image is an image that contains an operating system, application software, and business data. For these scenarios, you can set the parameter to the mount point of data disk N contained in the full image and modify the `DataDisk.N.Size` and `DataDisk.N.Category` parameters to change the category and size of data disk N created based on the image.
+     * >  This parameter is applicable to scenarios in which a full image is used to create instances. A full image is an image that contains an operating system, application software, and business data. For these scenarios, you can set this parameter to the mount point of data disk N in the full image and modify `DataDisk.N.Size` and `DataDisk.N.Category` to change the category and size of data disk N created based on the image.
      *
      * @example
      * /dev/xvdb
@@ -32471,11 +32570,13 @@ export declare class RunInstancesRequestDataDisk extends $dara.Model {
      * @remarks
      * Specifies whether to encrypt data disk N. Valid values:
      *
-     * *   true
-     * *   false
+     * *   true: encrypts the data disk.
+     * *   false: does not encrypt the data disk.
      *
      * Default value: false.
      *
+     * >  When you use a shared encrypted image to create the disk based on an encrypted snapshot, you must set Encrypted to true to ensure that the disk uses an encryption key of your own.
+     *
      * @example
      * false
      */
@@ -32493,9 +32594,9 @@ export declare class RunInstancesRequestDataDisk extends $dara.Model {
      * The performance level of the ESSD to use as data disk N. The value of N must be the same as that in `DataDisk.N.Category` when DataDisk.N.Category is set to cloud_essd. Valid values:
      *
      * *   PL0: A single ESSD can deliver up to 10,000 random read/write IOPS.
-     * *   PL1 (default): A single ESSD can deliver up to 50000 random read/write IOPS.
-     * *   PL2: A single ESSD can deliver up to 100000 random read/write IOPS.
-     * *   PL3: A single ESSD can deliver up to 1000000 random read/write IOPS.
+     * *   PL1 (default): A single ESSD can deliver up to 50,000 random read/write IOPS.
+     * *   PL2: A single ESSD can deliver up to 100,000 random read/write IOPS.
+     * *   PL3: A single ESSD can deliver up to 1,000,000 random read/write IOPS.
      *
      * For information about ESSD performance levels, see [ESSDs](https://help.aliyun.com/document_detail/122389.html).
      *
@@ -32507,7 +32608,7 @@ export declare class RunInstancesRequestDataDisk extends $dara.Model {
      * @remarks
      * The provisioned read/write IOPS of the ESSD AutoPL disk to use as data disk N. Valid values: 0 to min{50,000, 1,000 × Capacity - Baseline IOPS}.
      *
-     * Baseline IOPS = min{1,800 + 50 × Capacity, 50,000}
+     * Baseline IOPS = min{1,800 + 50 × Capacity, 50,000}.
      *
      * >  This parameter is available only if you set DataDisk.N.Category to cloud_auto. For more information, see [ESSD AutoPL disks](https://help.aliyun.com/document_detail/368372.html).
      *
@@ -32532,7 +32633,7 @@ export declare class RunInstancesRequestDataDisk extends $dara.Model {
      *
      * *   Valid values when DataDisk.N.Category is set to cloud: 5 to 2000.
      *
-     * *   Valid values when DiskCategory is set to cloud_auto: 1 to 65536.
+     * *   Valid values when DataDisk.N.Category is set to cloud_auto: 1 to 65536.
      *
      * *   Valid values when DataDisk.N.Category is set to cloud_essd_entry: 10 to 32768.
      *
@@ -32546,7 +32647,7 @@ export declare class RunInstancesRequestDataDisk extends $dara.Model {
      * @remarks
      * The ID of the snapshot to use to create data disk N. Valid values of N: 1 to 16.
      *
-     * When the `DataDisk.N.SnapshotId` parameter is specified, the `DataDisk.N.Size` parameter is ignored. The data disk is created with the size of the specified snapshot. Use snapshots created on or after July 15, 2013. Otherwise, an error is returned and your request is rejected.
+     * When `DataDisk.N.SnapshotId` is specified, `DataDisk.N.Size` is ignored. The data disk is created with the size of the specified snapshot. Use snapshots created after July 15, 2013. Otherwise, an error is returned and your request is rejected.
      *
      * @example
      * s-bp17441ohwka0yuh****
@@ -32873,7 +32974,7 @@ export declare class RunInstancesRequestNetworkOptions extends $dara.Model {
      *
      * Default value: true.
      *
-     * >  The Jumbo Frames feature is supported by only 8th-generation or later instance types. For more information, see [MTUs](https://help.aliyun.com/document_detail/200512.html).
+     * >  The Jumbo Frames feature is supported by only 8th-generation or later instance types. For more information, see [Jumbo Frames](https://help.aliyun.com/document_detail/200512.html).
      *
      * @example
      * false
@@ -42569,8 +42670,10 @@ export declare class CreatePrefixListRequest extends $dara.Model {
      * cn-chengdu
      */
     regionId?: string;
+    resourceGroupId?: string;
     resourceOwnerAccount?: string;
     resourceOwnerId?: number;
+    tag?: CreatePrefixListRequestTag[];
     static names(): {
         [key: string]: string;
     };
@@ -58817,8 +58920,10 @@ export declare class DescribePrefixListsRequest extends $dara.Model {
      * cn-chengdu
      */
     regionId?: string;
+    resourceGroupId?: string;
     resourceOwnerAccount?: string;
     resourceOwnerId?: number;
+    tag?: DescribePrefixListsRequestTag[];
     static names(): {
         [key: string]: string;
     };
@@ -69975,7 +70080,7 @@ export declare class ModifyImageShareGroupPermissionResponse extends $dara.Model
 export declare class ModifyImageSharePermissionRequest extends $dara.Model {
     /**
      * @remarks
-     * The ID of Alibaba Cloud account N to which you want to share the custom image. Valid values of N: 1 to 10. If you specify more than 10 Alibaba Cloud account IDs, the system processes only the first 10 account IDs. The excess account IDs are ignored.
+     * The IDs of Alibaba Cloud accounts to which you want to share the custom image. Valid values of N: 1 to 10. If you specify more than 10 Alibaba Cloud account IDs, the system processes only the first 10 account IDs. The excess account IDs are ignored.
      *
      * @example
      * 1234567890
@@ -69983,7 +70088,9 @@ export declare class ModifyImageSharePermissionRequest extends $dara.Model {
     addAccount?: string[];
     /**
      * @remarks
-     * The ID of the custom image.
+     * The ID of the shared custom image.
+     *
+     * >  You can share images encrypted by using CMKs but cannot share images encrypted by using service keys. When you share an image encrypted by using a service key, an error is reported.
      *
      * This parameter is required.
      *
@@ -70026,7 +70133,7 @@ export declare class ModifyImageSharePermissionRequest extends $dara.Model {
     regionId?: string;
     /**
      * @remarks
-     * The ID of Alibaba Cloud account N from which you want to unshare the custom image. Valid values of N: 1 to 10. If you specify more than 10 Alibaba Cloud account IDs, the system processes only the first 10 account IDs. The excess account IDs are ignored.
+     * The IDs of Alibaba Cloud accounts from which you want to unshare the custom image. Valid values of N: 1 to 10. If you specify more than 10 Alibaba Cloud account IDs, the system processes only the first 10 account IDs. The excess account IDs are ignored.
      *
      * @example
      * 1234567890
@@ -75866,7 +75973,7 @@ export declare class RedeployInstanceRequest extends $dara.Model {
      *
      * Default value: false.
      *
-     * > A forced stop is equivalent to a power outage, and unsaved data may be lost. We recommend that you redeploy instances that are in the Stopped state.
+     * >  A forced stop is equivalent to a power outage and can result in loss of data that is not written to storage devices. We recommend that you redeploy instances when they are in the Stopped state.
      *
      * @example
      * false
@@ -76955,10 +77062,12 @@ export declare class ReplaceSystemDiskRequest extends $dara.Model {
      * @remarks
      * Specifies whether to encrypt the disk. Valid values:
      *
-     * *   true: encrypts the disk.
-     * *   false: does not encrypt the disk.
+     * *   true
+     * *   false
      *
-     * Default value: false
+     * Default value: false.
+     *
+     * >  When you use a shared encrypted image to create the disk based on an encrypted snapshot, you must set Encrypted to true to ensure that the disk uses an encryption key of your own.
      *
      * @example
      * false
@@ -76966,9 +77075,7 @@ export declare class ReplaceSystemDiskRequest extends $dara.Model {
     encrypted?: boolean;
     /**
      * @remarks
-     * The ID of the image to be used to replace the system disk.
-     *
-     * If the `DiskId` parameter is not specified, this parameter is required.
+     * The ID of the image used to replace the system disk. This parameter is required.
      *
      * @example
      * m-bp67acfmxazb4ph****
@@ -79701,7 +79808,7 @@ export declare class RunInstancesRequest extends $dara.Model {
 export declare class RunInstancesResponseBody extends $dara.Model {
     /**
      * @remarks
-     * The IDs of the instances (`InstanceIdSet`).
+     * The instance IDs (`InstanceIdSet`).
      */
     instanceIdSets?: RunInstancesResponseBodyInstanceIdSets;
     /**
@@ -80276,6 +80383,10 @@ export declare class StartTerminalSessionRequest extends $dara.Model {
      * ssh root@192.168.0.246
      */
     commandLine?: string;
+    /**
+     * @example
+     * Intranet
+     */
     connectionType?: string;
     /**
      * @remarks
@@ -87570,7 +87681,7 @@ export default class Client extends OpenApi {
      */
     modifyAutoProvisioningGroup(request: ModifyAutoProvisioningGroupRequest): Promise<ModifyAutoProvisioningGroupResponse>;
     /**
-     * Modifies an automatic snapshot policy.
+     * Modifies an automatic snapshot policy. For example, you can change the points in time of the day at which to create automatic snapshots, days of the week on which to create automatic snapshots, and retention period of automatic snapshots for the automatic snapshot policy.
      *
      * @remarks
      * Before you call this operation, take note of the following items:
@@ -87584,7 +87695,7 @@ export default class Client extends OpenApi {
      */
     modifyAutoSnapshotPolicyExWithOptions(request: ModifyAutoSnapshotPolicyExRequest, runtime: $dara.RuntimeOptions): Promise<ModifyAutoSnapshotPolicyExResponse>;
     /**
-     * Modifies an automatic snapshot policy.
+     * Modifies an automatic snapshot policy. For example, you can change the points in time of the day at which to create automatic snapshots, days of the week on which to create automatic snapshots, and retention period of automatic snapshots for the automatic snapshot policy.
      *
      * @remarks
      * Before you call this operation, take note of the following items:
@@ -88094,16 +88205,15 @@ export default class Client extends OpenApi {
      * @remarks
      * Before you call this operation, read [Share a custom image](https://help.aliyun.com/document_detail/25463.html).
      * When you call this operation, take note of the following sharing rules:
-     * *   You can share only the custom images that are created in your Alibaba Cloud to other Alibaba Cloud accounts.
-     * *   You can share a custom image to up to 10 Alibaba Cloud accounts at a time. You can specify up to 10 Alibaba Cloud account IDs by using the AddAccount.N or RemoveAccount.N parameter. If you specify more than 10 account IDs, the system processes only the previous 10 account IDs. The excess account IDs are ignored.
-     * *   You can share a custom image to up to 50 Alibaba Cloud accounts.
-     * *   If an Elastic Compute Service (ECS) instance was created ([RunInstances](https://help.aliyun.com/document_detail/63440.html)) from a shared image, you cannot re-initialize the instance ([ReInitDisk](https://help.aliyun.com/document_detail/25519.html)) after the image owner unshares or deletes the image ([DeleteImage](https://help.aliyun.com/document_detail/25537.html)).
+     * *   **Sharing limits**: You can share only the custom images created in your Alibaba Cloud account to other Alibaba Cloud accounts. A custom image can be shared to up to 50 Alibaba Cloud accounts. You can share a custom image to up to 10 Alibaba Cloud accounts at a time.
+     * *   **Impacts on an instance**: If an instance was created ([RunInstances](https://help.aliyun.com/document_detail/63440.html)) from a shared image, you cannot re-initialize the system disk of the instance ([ReInitDisk](https://help.aliyun.com/document_detail/25519.html)) after the image owner unshares or deletes the image ([DeleteImage](https://help.aliyun.com/document_detail/25537.html)).
+     * >  You can share images encrypted by using customer master keys (CMKs) but cannot share images encrypted by using service keys. When you share an image encrypted by using a service key, an error is reported. If you want to share an image encrypted by using a service key, call the CopyImage operation to copy the image and change the encryption key of the image copy to a CMK.
      * When you publish or unpublish a community image, take note of the following items:
-     * *   Alibaba Cloud provides only the platform on which 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 acknowledge and agree to the Community Image Agreement. Otherwise, you cannot publish community images. For more information, see [Publish a community image](https://help.aliyun.com/document_detail/208370.html).
-     * *   You cannot publish encrypted images as community images.
-     * *   Community images are publicly available. A community image is available to all Alibaba Cloud accounts in the region where the image resides.
-     * *   You cannot share, export, or copy community images.
-     * *   After you unpublish a community image, the image is no longer available to other Alibaba Cloud accounts. If an image is shared to other Alibaba Cloud accounts before it is unpublished, the image remains available to the accounts.
+     * *   **Responsibilities and agreement**: Alibaba Cloud provides only the platform on which 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 acknowledge and agree to the Community Image Agreement. Otherwise, you cannot publish community images. For more information, see [Publish a community image](https://help.aliyun.com/document_detail/208370.html).
+     * *   **Encryption limits**: You cannot publish encrypted images as community images.
+     * *   **Openness**: Community images are publicly available. A community image is available to all Alibaba Cloud accounts in the region where the image resides.
+     * *   **Feature limits**: You cannot share, export, or copy community images.
+     * *   **Unpublication impacts**: After you unpublish a community image, the image is no longer available to other Alibaba Cloud accounts. If an image is shared to other Alibaba Cloud accounts before it is unpublished, the image remains available to the accounts.
      *
      * @param request - ModifyImageSharePermissionRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -88116,16 +88226,15 @@ export default class Client extends OpenApi {
      * @remarks
      * Before you call this operation, read [Share a custom image](https://help.aliyun.com/document_detail/25463.html).
      * When you call this operation, take note of the following sharing rules:
-     * *   You can share only the custom images that are created in your Alibaba Cloud to other Alibaba Cloud accounts.
-     * *   You can share a custom image to up to 10 Alibaba Cloud accounts at a time. You can specify up to 10 Alibaba Cloud account IDs by using the AddAccount.N or RemoveAccount.N parameter. If you specify more than 10 account IDs, the system processes only the previous 10 account IDs. The excess account IDs are ignored.
-     * *   You can share a custom image to up to 50 Alibaba Cloud accounts.
-     * *   If an Elastic Compute Service (ECS) instance was created ([RunInstances](https://help.aliyun.com/document_detail/63440.html)) from a shared image, you cannot re-initialize the instance ([ReInitDisk](https://help.aliyun.com/document_detail/25519.html)) after the image owner unshares or deletes the image ([DeleteImage](https://help.aliyun.com/document_detail/25537.html)).
+     * *   **Sharing limits**: You can share only the custom images created in your Alibaba Cloud account to other Alibaba Cloud accounts. A custom image can be shared to up to 50 Alibaba Cloud accounts. You can share a custom image to up to 10 Alibaba Cloud accounts at a time.
+     * *   **Impacts on an instance**: If an instance was created ([RunInstances](https://help.aliyun.com/document_detail/63440.html)) from a shared image, you cannot re-initialize the system disk of the instance ([ReInitDisk](https://help.aliyun.com/document_detail/25519.html)) after the image owner unshares or deletes the image ([DeleteImage](https://help.aliyun.com/document_detail/25537.html)).
+     * >  You can share images encrypted by using customer master keys (CMKs) but cannot share images encrypted by using service keys. When you share an image encrypted by using a service key, an error is reported. If you want to share an image encrypted by using a service key, call the CopyImage operation to copy the image and change the encryption key of the image copy to a CMK.
      * When you publish or unpublish a community image, take note of the following items:
-     * *   Alibaba Cloud provides only the platform on which 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 acknowledge and agree to the Community Image Agreement. Otherwise, you cannot publish community images. For more information, see [Publish a community image](https://help.aliyun.com/document_detail/208370.html).
-     * *   You cannot publish encrypted images as community images.
-     * *   Community images are publicly available. A community image is available to all Alibaba Cloud accounts in the region where the image resides.
-     * *   You cannot share, export, or copy community images.
-     * *   After you unpublish a community image, the image is no longer available to other Alibaba Cloud accounts. If an image is shared to other Alibaba Cloud accounts before it is unpublished, the image remains available to the accounts.
+     * *   **Responsibilities and agreement**: Alibaba Cloud provides only the platform on which 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 acknowledge and agree to the Community Image Agreement. Otherwise, you cannot publish community images. For more information, see [Publish a community image](https://help.aliyun.com/document_detail/208370.html).
+     * *   **Encryption limits**: You cannot publish encrypted images as community images.
+     * *   **Openness**: Community images are publicly available. A community image is available to all Alibaba Cloud accounts in the region where the image resides.
+     * *   **Feature limits**: You cannot share, export, or copy community images.
+     * *   **Unpublication impacts**: After you unpublish a community image, the image is no longer available to other Alibaba Cloud accounts. If an image is shared to other Alibaba Cloud accounts before it is unpublished, the image remains available to the accounts.
      *
      * @param request - ModifyImageSharePermissionRequest
      * @returns ModifyImageSharePermissionResponse
@@ -89397,27 +89506,28 @@ export default class Client extends OpenApi {
      * Redeploys an Elastic Compute Service (ECS) instance. You can call this operation to redeploy an ECS instance when the instance receives a system event notification.
      *
      * @remarks
-     * RedeployInstance is an asynchronous operation. This operation migrates data before it restarts the instance. After the instance is redeployed, the instance enters the `Running` state. If the instance fails to be redeployed, the instance returns to the original physical server and the state before redeployment.
-     * Take note of the following items:
-     * * The instance must be in the Running or Stopped state. After the instance is redeployed, the following changes occur to the status of the instance:
-     *   * If the instance is in the `Running` state before redeployment, the instance enters the `Stopping` state.
-     *   * If the instance is in the `Stopped` state before redeployment, the instance enters the `Starting` state.
+     * ## Usage notes
+     * RedeployInstance is an asynchronous operation. The operation migrates the instance to a healthy physical server and then restarts the instance. After the instance is redeployed, it enters the Running (`Running`) state. If the instance fails to be redeployed, it returns to the original physical server and the state before the redeployment.
+     * When you call this operation, take note of the following item:
+     * * The instance must be in the Running (Running) or Stopped (Stopped) state. After the instance is redeployed, the following changes occur to the status of the instance:
+     *   * If the instance is in the Running (`Running`) state, the instance enters the Stopping (`Stopping`) state.
+     *   * If the instance is in the Stopped (`Stopped`) state, the instance enters the Starting (`Starting`) state.
      * * If an instance is deployed on a dedicated host, you cannot redeploy the instance.
-     * * If the `OperationLocks` parameter in the response of the DescribeInstances operation contains `"LockReason" : "security"` for an instance, the instance is locked for security reasons and cannot be redeployed.
-     * * If you receive notifications about simulated events that are created by calling the CreateSimulatedSystemEvent operation for an instance, you cannot redeploy the instance.
-     * * If the damaged local disk is isolated but the **SystemMaintenance.RebootAndReInitErrorDisk** event is not sent when you handle a local disk-related system event for an instance, you can still call the RedeployInstance operation to redeploy the instance. The SystemMaintenance.RebootAndReInitErrorDisk event indicates that the instance is restarted and the damaged disks are reinitialized due to system maintenance. For more information, see [System events for ECS instances equipped with local disks](https://help.aliyun.com/document_detail/107693.html).
-     * The following table describes the system events that you can handle by calling the RedeployInstance operation. The table also provides possible event status.
+     * * If `OperationLocks` in the response of the DescribeInstances operation contains `"LockReason": "security"` for an instance, the instance is locked for security reasons and cannot be redeployed.
+     * * If an instance receives notifications about simulated events that are created by calling the CreateSimulatedSystemEvent operation for the instance, you cannot call this operation to redeploy the instance.
+     * * When you handle a local disk-related system event for an instance, if the damaged local disk is isolated but the SystemMaintenance.RebootAndReInitErrorDisk (**instance restart and re-initialization of damaged disks due to system maintenance**) event is not sent, you can still call the RedeployInstance operation to redeploy the instance. For more information, see [O&#x26;M scenarios and system events for instances equipped with local disks](https://help.aliyun.com/document_detail/107693.html).
+     * The following table describes the types and states of events that you can handle by calling the RedeployInstance operation.
      * |System event|Event status|
      * |---|---|
      * |Instance restart due to system maintenance (SystemMaintenance.Reboot)|Inquiring and Scheduled|
      * |Instance redeployment due to system maintenance (SystemMaintenance.Redeploy)|Inquiring and Scheduled|
      * |Instance restart and replacement of damaged disks due to system maintenance (SystemMaintenance.RebootAndIsolateErrorDisk)|Inquiring|
      * |Instance restart and re-initialization of damaged disks due to system maintenance (SystemMaintenance.RebootAndReInitErrorDisk)|Inquiring|
-     * |Instance redeployment due to system errors (SystemFailure.Redeploy)|Inquiring and Scheduled|
-     * |For ECS instances that use only local disks: instance restart due to a system error (SystemFailure.Reboot)|Executing|
+     * |Instance redeployment due to system errors (SystemFailure.Redeploy)|Inquiring|
+     * |For ECS instances that use only local disks: instance restart due to system errors (SystemFailure.Reboot)|Executing|
      * |Isolation of damaged disks due to system maintenance (SystemMaintenance.IsolateErrorDisk)|Inquiring|
      * |Re-initialization of damaged disks due to system maintenance (SystemMaintenance.ReInitErrorDisk)|Inquiring|
-     * **Note**When instances that use local disks are redeployed, the local disks are re-initialized and data on the local disks is cleared.
+     * **Note** When the system redeploys instances equipped with local disks, the local disks are re-initialized and data on the local disks is cleared.
      *
      * @param request - RedeployInstanceRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -89428,27 +89538,28 @@ export default class Client extends OpenApi {
      * Redeploys an Elastic Compute Service (ECS) instance. You can call this operation to redeploy an ECS instance when the instance receives a system event notification.
      *
      * @remarks
-     * RedeployInstance is an asynchronous operation. This operation migrates data before it restarts the instance. After the instance is redeployed, the instance enters the `Running` state. If the instance fails to be redeployed, the instance returns to the original physical server and the state before redeployment.
-     * Take note of the following items:
-     * * The instance must be in the Running or Stopped state. After the instance is redeployed, the following changes occur to the status of the instance:
-     *   * If the instance is in the `Running` state before redeployment, the instance enters the `Stopping` state.
-     *   * If the instance is in the `Stopped` state before redeployment, the instance enters the `Starting` state.
+     * ## Usage notes
+     * RedeployInstance is an asynchronous operation. The operation migrates the instance to a healthy physical server and then restarts the instance. After the instance is redeployed, it enters the Running (`Running`) state. If the instance fails to be redeployed, it returns to the original physical server and the state before the redeployment.
+     * When you call this operation, take note of the following item:
+     * * The instance must be in the Running (Running) or Stopped (Stopped) state. After the instance is redeployed, the following changes occur to the status of the instance:
+     *   * If the instance is in the Running (`Running`) state, the instance enters the Stopping (`Stopping`) state.
+     *   * If the instance is in the Stopped (`Stopped`) state, the instance enters the Starting (`Starting`) state.
      * * If an instance is deployed on a dedicated host, you cannot redeploy the instance.
-     * * If the `OperationLocks` parameter in the response of the DescribeInstances operation contains `"LockReason" : "security"` for an instance, the instance is locked for security reasons and cannot be redeployed.
-     * * If you receive notifications about simulated events that are created by calling the CreateSimulatedSystemEvent operation for an instance, you cannot redeploy the instance.
-     * * If the damaged local disk is isolated but the **SystemMaintenance.RebootAndReInitErrorDisk** event is not sent when you handle a local disk-related system event for an instance, you can still call the RedeployInstance operation to redeploy the instance. The SystemMaintenance.RebootAndReInitErrorDisk event indicates that the instance is restarted and the damaged disks are reinitialized due to system maintenance. For more information, see [System events for ECS instances equipped with local disks](https://help.aliyun.com/document_detail/107693.html).
-     * The following table describes the system events that you can handle by calling the RedeployInstance operation. The table also provides possible event status.
+     * * If `OperationLocks` in the response of the DescribeInstances operation contains `"LockReason": "security"` for an instance, the instance is locked for security reasons and cannot be redeployed.
+     * * If an instance receives notifications about simulated events that are created by calling the CreateSimulatedSystemEvent operation for the instance, you cannot call this operation to redeploy the instance.
+     * * When you handle a local disk-related system event for an instance, if the damaged local disk is isolated but the SystemMaintenance.RebootAndReInitErrorDisk (**instance restart and re-initialization of damaged disks due to system maintenance**) event is not sent, you can still call the RedeployInstance operation to redeploy the instance. For more information, see [O&#x26;M scenarios and system events for instances equipped with local disks](https://help.aliyun.com/document_detail/107693.html).
+     * The following table describes the types and states of events that you can handle by calling the RedeployInstance operation.
      * |System event|Event status|
      * |---|---|
      * |Instance restart due to system maintenance (SystemMaintenance.Reboot)|Inquiring and Scheduled|
      * |Instance redeployment due to system maintenance (SystemMaintenance.Redeploy)|Inquiring and Scheduled|
      * |Instance restart and replacement of damaged disks due to system maintenance (SystemMaintenance.RebootAndIsolateErrorDisk)|Inquiring|
      * |Instance restart and re-initialization of damaged disks due to system maintenance (SystemMaintenance.RebootAndReInitErrorDisk)|Inquiring|
-     * |Instance redeployment due to system errors (SystemFailure.Redeploy)|Inquiring and Scheduled|
-     * |For ECS instances that use only local disks: instance restart due to a system error (SystemFailure.Reboot)|Executing|
+     * |Instance redeployment due to system errors (SystemFailure.Redeploy)|Inquiring|
+     * |For ECS instances that use only local disks: instance restart due to system errors (SystemFailure.Reboot)|Executing|
      * |Isolation of damaged disks due to system maintenance (SystemMaintenance.IsolateErrorDisk)|Inquiring|
      * |Re-initialization of damaged disks due to system maintenance (SystemMaintenance.ReInitErrorDisk)|Inquiring|
-     * **Note**When instances that use local disks are redeployed, the local disks are re-initialized and data on the local disks is cleared.
+     * **Note** When the system redeploys instances equipped with local disks, the local disks are re-initialized and data on the local disks is cleared.
      *
      * @param request - RedeployInstanceRequest
      * @returns RedeployInstanceResponse
@@ -90121,23 +90232,25 @@ export default class Client extends OpenApi {
      * Creates Elastic Compute Service (ECS) instances. This operation helps simplify the procedure to create and manage ECS instances. When you call this operation, you can choose to create multiple ECS instances at a time, automatically start the instances, and assign public IP addresses to the instances based on outbound bandwidth parameters. You can also use the features provided by the operation, such as configuring an automatic release time for instances, using a launch template, and configuring custom CPU options, to customize instance configurations for better management of instances.
      *
      * @remarks
-     * *Before you call this operation, familiarize yourself with the billing and [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS resources.**
+     * \\*\\* When you create an ECS instance, you are charged for ECS resources, including the [instance type](https://help.aliyun.com/document_detail/25398.html), [image](https://help.aliyun.com/document_detail/179021.html), [block storage](https://help.aliyun.com/document_detail/179022.html), and [public bandwidth](https://help.aliyun.com/document_detail/25411.html). Before you call this operation, familiarize yourself with the billing rules and
+     * [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS resources. \\*\\*
      * This operation is an asynchronous operation. After a request to create ECS instances is sent, ECS instance IDs are returned but the creation and startup of the instances may be incomplete. You can call the [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) operation to query the status of the instances. When the status of an instance is `Running` in the DescribeInstanceStatus response, the instance is created and started.
      * ### [](#)Considerations
-     * *   Make sure that the number of ECS instances you created or the number of vCPUs on ECS instances of all instance types you created does not exceed the corresponding quota. Go to the [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas) to view the quotas.
-     * *   Before you create ECS instances of the Virtual Private Cloud (VPC) type in a region, create a VPC in the region. For more information, see [Create a VPC](https://help.aliyun.com/document_detail/65430.html).
+     * *   If the resource inventory is insufficient to complete instance creation, Alibaba Cloud immediately sends an instance creation failure event (SystemFailure.Delete). You can call the [DescribeInstanceHistoryEvents](https://help.aliyun.com/document_detail/2679897.html) operation to check whether an instance creation failure event exists. For more information, see [System events related to instance creation failures](https://help.aliyun.com/document_detail/2545990.html).
+     * *   Make sure that the number of ECS instances you create or the number of vCPUs on ECS instances of all instance types you create does not exceed the corresponding quota. Go to the [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas) to view the quotas.
+     * *   Before you create ECS instances of the Virtual Private Cloud (VPC) type in a region, [create a VPC](https://help.aliyun.com/document_detail/65430.html) in the region.
      * ### [](#)Precautions
-     * *   If you create a subscription instance (`PrePaid`), available coupons in your account are used by default.
-     * *   You can call the RunInstances operation to create up to 100 ECS instances at a time. To create more than 100 ECS instances, we recommend that you initiate multiple requests in batches or concurrently.
+     * *   If you create a subscription instance (`PrePaid`), available coupons in your account are automatically used.
+     * *   You can call the RunInstances operation to create up to 100 ECS instances in a single request. To create more than 100 ECS instances, we recommend that you initiate multiple requests in batches or concurrently.
      * *   If you set `InternetMaxBandwidthOut` to a value greater than 0, public IP addresses are automatically assigned to the ECS instances to be created.
-     * >  For the limits on the sum of maximum public bandwidths of ECS instances that use the pay-by-bandwidth billing method for network usage per region per Alibaba Cloud account, see the [Public bandwidth limits](~~25412#BandwidthQuota~~) section of the "Limits" topic.
+     * >  For the limits on the sum of maximum public bandwidths of ECS instances that use the pay-by-bandwidth billing method for network usage per region per Alibaba Cloud account, see the [Public bandwidth](~~25412#BandwidthQuota~~) section of the "Limits and quotas on ECS" topic.
      * ### [](#)Suggestions
      * *   **Test scenarios**: Set `DryRun` to true to perform a dry run without performing the actual request.
      * *   **Release of ECS instances**: Use `AutoReleaseTime` to configure an automatic release time for ECS instances in the request to RunInstances or call the [DeleteInstances](https://help.aliyun.com/document_detail/2679710.html) operation to release the instances.
      * *   **Management and search of ECS instances**: Add tags to the ECS instances by specifying `Tag.N.Key` and `Tag.N.Value` and append incremental suffixes by specifying `UniqueSuffix` to the hostname specified by `HostName` and the instance name specified by `InstanceName`. For more information, see [Batch configure sequential names or hostnames for multiple instances](https://help.aliyun.com/document_detail/196048.html).
      * *   **Launch template**: A launch template contains the parameters required to create an ECS instance so that you do not have to specify the parameters every time you create ECS instances. You can call the [CreateLaunchTemplate](https://help.aliyun.com/document_detail/2679729.html) operation to create a launch template. Then, in the request to `RunInstances`, you can specify `LaunchTemplateId` and `LaunchTemplateVersion` to use the launch template.
      * *   **Disabling of Hyper-Threading (HT)**: In memory-intensive scenarios, set `CpuOptions.ThreadsPerCore` to 1 to disable HT and increase the memory-to-vCPU ratio.
-     * *   **Enabling of Jumbo Frames**: Set `NetworkOptions.EnableJumboFrame` to true to enable the `Jumbo Frames` feature when you create ECS instances. For more information, see [MTUs](https://help.aliyun.com/document_detail/200512.html).
+     * *   **Enabling of Jumbo Frames**: Set `NetworkOptions.EnableJumboFrame` to true to enable the `Jumbo Frames` feature when you create ECS instances. For more information, see [Jumbo Frames](https://help.aliyun.com/document_detail/200512.html).
      * ## [](#)Sample requests
      * Use a specific image to create ECS instances of a specific instance type in the China (Hangzhou) region. The instances use disks with a specific capacity as the system disk and data disks and are automatically assigned public IP addresses. The instances have user-defined names and logon passwords. The instances are assigned to a specific security group and connected to a specific vSwitch. Request parameters:
      *     RegionId:"cn-hangzhou", //Set the region ID to cn-hangzhou, which specifies the China (Hangzhou) region.
@@ -90170,7 +90283,7 @@ export default class Client extends OpenApi {
      *     Amount:10, //Set the number of ECS instances that you want to create to 10.
      *     InstanceChargeType:"PostPaid", //Set the billing method to PostPaid, which specifies the pay-as-you-go billing method.
      *     SpotStrategy:"NoSpot" //Set this parameter to NoSpot, which is the default value and specifies that the instances are created as pay-as-you-go instances.
-     * **Example: Create 20 preemptible instances that use a specified bidding policy and a protection period**
+     * **Example: Create 20 preemptible instances that use a specific bidding policy and a protection period**
      *     Amount:20, //Set the number of ECS instances that you want to create to 20.
      *     InstanceChargeType:"PostPaid",
      *     SpotStrategy:"SpotAsPriceGo", //Set the bidding policy to SpotAsPriceGo, which specifies that the instances are created as preemptible instances for which the market price at the time of purchase is automatically used as the bid price.
@@ -90191,23 +90304,25 @@ export default class Client extends OpenApi {
      * Creates Elastic Compute Service (ECS) instances. This operation helps simplify the procedure to create and manage ECS instances. When you call this operation, you can choose to create multiple ECS instances at a time, automatically start the instances, and assign public IP addresses to the instances based on outbound bandwidth parameters. You can also use the features provided by the operation, such as configuring an automatic release time for instances, using a launch template, and configuring custom CPU options, to customize instance configurations for better management of instances.
      *
      * @remarks
-     * *Before you call this operation, familiarize yourself with the billing and [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS resources.**
+     * \\*\\* When you create an ECS instance, you are charged for ECS resources, including the [instance type](https://help.aliyun.com/document_detail/25398.html), [image](https://help.aliyun.com/document_detail/179021.html), [block storage](https://help.aliyun.com/document_detail/179022.html), and [public bandwidth](https://help.aliyun.com/document_detail/25411.html). Before you call this operation, familiarize yourself with the billing rules and
+     * [pricing](https://www.alibabacloud.com/zh/pricing-calculator#/commodity/vm_intl) of ECS resources. \\*\\*
      * This operation is an asynchronous operation. After a request to create ECS instances is sent, ECS instance IDs are returned but the creation and startup of the instances may be incomplete. You can call the [DescribeInstanceStatus](https://help.aliyun.com/document_detail/2679688.html) operation to query the status of the instances. When the status of an instance is `Running` in the DescribeInstanceStatus response, the instance is created and started.
      * ### [](#)Considerations
-     * *   Make sure that the number of ECS instances you created or the number of vCPUs on ECS instances of all instance types you created does not exceed the corresponding quota. Go to the [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas) to view the quotas.
-     * *   Before you create ECS instances of the Virtual Private Cloud (VPC) type in a region, create a VPC in the region. For more information, see [Create a VPC](https://help.aliyun.com/document_detail/65430.html).
+     * *   If the resource inventory is insufficient to complete instance creation, Alibaba Cloud immediately sends an instance creation failure event (SystemFailure.Delete). You can call the [DescribeInstanceHistoryEvents](https://help.aliyun.com/document_detail/2679897.html) operation to check whether an instance creation failure event exists. For more information, see [System events related to instance creation failures](https://help.aliyun.com/document_detail/2545990.html).
+     * *   Make sure that the number of ECS instances you create or the number of vCPUs on ECS instances of all instance types you create does not exceed the corresponding quota. Go to the [Quota Center](https://quotas.console.aliyun.com/products/ecs/quotas) to view the quotas.
+     * *   Before you create ECS instances of the Virtual Private Cloud (VPC) type in a region, [create a VPC](https://help.aliyun.com/document_detail/65430.html) in the region.
      * ### [](#)Precautions
-     * *   If you create a subscription instance (`PrePaid`), available coupons in your account are used by default.
-     * *   You can call the RunInstances operation to create up to 100 ECS instances at a time. To create more than 100 ECS instances, we recommend that you initiate multiple requests in batches or concurrently.
+     * *   If you create a subscription instance (`PrePaid`), available coupons in your account are automatically used.
+     * *   You can call the RunInstances operation to create up to 100 ECS instances in a single request. To create more than 100 ECS instances, we recommend that you initiate multiple requests in batches or concurrently.
      * *   If you set `InternetMaxBandwidthOut` to a value greater than 0, public IP addresses are automatically assigned to the ECS instances to be created.
-     * >  For the limits on the sum of maximum public bandwidths of ECS instances that use the pay-by-bandwidth billing method for network usage per region per Alibaba Cloud account, see the [Public bandwidth limits](~~25412#BandwidthQuota~~) section of the "Limits" topic.
+     * >  For the limits on the sum of maximum public bandwidths of ECS instances that use the pay-by-bandwidth billing method for network usage per region per Alibaba Cloud account, see the [Public bandwidth](~~25412#BandwidthQuota~~) section of the "Limits and quotas on ECS" topic.
      * ### [](#)Suggestions
      * *   **Test scenarios**: Set `DryRun` to true to perform a dry run without performing the actual request.
      * *   **Release of ECS instances**: Use `AutoReleaseTime` to configure an automatic release time for ECS instances in the request to RunInstances or call the [DeleteInstances](https://help.aliyun.com/document_detail/2679710.html) operation to release the instances.
      * *   **Management and search of ECS instances**: Add tags to the ECS instances by specifying `Tag.N.Key` and `Tag.N.Value` and append incremental suffixes by specifying `UniqueSuffix` to the hostname specified by `HostName` and the instance name specified by `InstanceName`. For more information, see [Batch configure sequential names or hostnames for multiple instances](https://help.aliyun.com/document_detail/196048.html).
      * *   **Launch template**: A launch template contains the parameters required to create an ECS instance so that you do not have to specify the parameters every time you create ECS instances. You can call the [CreateLaunchTemplate](https://help.aliyun.com/document_detail/2679729.html) operation to create a launch template. Then, in the request to `RunInstances`, you can specify `LaunchTemplateId` and `LaunchTemplateVersion` to use the launch template.
      * *   **Disabling of Hyper-Threading (HT)**: In memory-intensive scenarios, set `CpuOptions.ThreadsPerCore` to 1 to disable HT and increase the memory-to-vCPU ratio.
-     * *   **Enabling of Jumbo Frames**: Set `NetworkOptions.EnableJumboFrame` to true to enable the `Jumbo Frames` feature when you create ECS instances. For more information, see [MTUs](https://help.aliyun.com/document_detail/200512.html).
+     * *   **Enabling of Jumbo Frames**: Set `NetworkOptions.EnableJumboFrame` to true to enable the `Jumbo Frames` feature when you create ECS instances. For more information, see [Jumbo Frames](https://help.aliyun.com/document_detail/200512.html).
      * ## [](#)Sample requests
      * Use a specific image to create ECS instances of a specific instance type in the China (Hangzhou) region. The instances use disks with a specific capacity as the system disk and data disks and are automatically assigned public IP addresses. The instances have user-defined names and logon passwords. The instances are assigned to a specific security group and connected to a specific vSwitch. Request parameters:
      *     RegionId:"cn-hangzhou", //Set the region ID to cn-hangzhou, which specifies the China (Hangzhou) region.
@@ -90240,7 +90355,7 @@ export default class Client extends OpenApi {
      *     Amount:10, //Set the number of ECS instances that you want to create to 10.
      *     InstanceChargeType:"PostPaid", //Set the billing method to PostPaid, which specifies the pay-as-you-go billing method.
      *     SpotStrategy:"NoSpot" //Set this parameter to NoSpot, which is the default value and specifies that the instances are created as pay-as-you-go instances.
-     * **Example: Create 20 preemptible instances that use a specified bidding policy and a protection period**
+     * **Example: Create 20 preemptible instances that use a specific bidding policy and a protection period**
      *     Amount:20, //Set the number of ECS instances that you want to create to 20.
      *     InstanceChargeType:"PostPaid",
      *     SpotStrategy:"SpotAsPriceGo", //Set the bidding policy to SpotAsPriceGo, which specifies that the instances are created as preemptible instances for which the market price at the time of purchase is automatically used as the bid price.