@alicloud/ecs20140526 7.9.0 → 7.9.2

package/dist/client.d.ts

@@ -342,24 +342,27 @@ export default class Client extends OpenApi {
      */
     attachClassicLinkVpc(request: $_model.AttachClassicLinkVpcRequest): Promise<$_model.AttachClassicLinkVpcResponse>;
     /**
-     * Attaches a pay-as-you-go data disk or a system disk to an Elastic Compute Service (ECS) instance.
+     * Attaches a data disk or system disk to an ECS instance.
      *
      * @remarks
-     * Take note of the following items:
-     * - The ECS instance and the disk must reside in the same zone.
-     * - The disk must be in the **Unattached** (`Available`) state.
-     * - When you attach the disk as a data disk to an ECS instance, take note of the following items:
-     *   - The ECS instance must be in the **Running** (`Running`) or **Stopped** (`Stopped`) state.
-     *   - If the disk was separately purchased, the billing method of the disk must be pay-as-you-go.
-     *   - If the disk is a system disk that was detached from an ECS instance, no limits apply to the billing method of the disk.
-     *   - If the disk is an elastic ephemeral disk that was detached from an ECS instance, the disk can be attached only to the instance.
-     * - When you attach the disk as the system disk to an ECS instance, take note of the following items:
-     *   - The ECS instance must be the original instance from which the system disk was detached.
-     *   - The ECS instance must be in the **Stopped** (`Stopped`) state.
-     *   - You must configure logon credentials for the ECS instance.
-     *   - The disk cannot be an elastic ephemeral disk.
-     *   - For more information about how to attach a system disk, see [Detach or attach a system disk](https://help.aliyun.com/document_detail/146752.html).
-     * - If the response contains `{"OperationLocks": {"LockReason" : "security"}}` when you query information about an ECS instance, the instance is locked for security reasons. No operations are allowed on the instance.
+     * When you call this operation, take note of the following items:
+     * - The instance and the disk must be in the same zone.
+     * - The disk must be in the **Available** (`Available`) state.
+     * - When you attach a data disk:
+     *     - The destination ECS instance must be in the **Running** (`Running`) or **Stopped** (`Stopped`) state.
+     *     - If the disk is separately purchased, the billing method must be pay-as-you-go.
+     *     - A system disk that was uninstalled from an ECS instance can be attached as a data disk without billable methods restrictions.
+     *     - An elastic ephemeral disk that has been detached can only be re-attached to its original instance.
+     * - When you attach a system disk:
+     *     - The destination ECS instance must be the original instance from which the system disk was detached.
+     *     - The destination ECS instance must be in the **Stopped** (`Stopped`) state.
+     *     - You must specify the logon credential for the instance.
+     *     - Elastic ephemeral disks cannot be attached as system disks.
+     *     - For more information about attaching system disks, see [Detach or attach a system disk](https://help.aliyun.com/document_detail/146752.html).
+     * - When you query ECS instance information, if the response contains `{"OperationLocks": {"LockReason" : "security"}}`, all operations are prohibited.
+     * <props="china">
+     * - A disk with the multi-attach attribute enabled can only be attached to instances that support the NVMe protocol.
+     *    For more information, see [Standard SSDs that support NVMe](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
      *
      * @param request - AttachDiskRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -367,24 +370,27 @@ export default class Client extends OpenApi {
      */
     attachDiskWithOptions(request: $_model.AttachDiskRequest, runtime: $dara.RuntimeOptions): Promise<$_model.AttachDiskResponse>;
     /**
-     * Attaches a pay-as-you-go data disk or a system disk to an Elastic Compute Service (ECS) instance.
+     * Attaches a data disk or system disk to an ECS instance.
      *
      * @remarks
-     * Take note of the following items:
-     * - The ECS instance and the disk must reside in the same zone.
-     * - The disk must be in the **Unattached** (`Available`) state.
-     * - When you attach the disk as a data disk to an ECS instance, take note of the following items:
-     *   - The ECS instance must be in the **Running** (`Running`) or **Stopped** (`Stopped`) state.
-     *   - If the disk was separately purchased, the billing method of the disk must be pay-as-you-go.
-     *   - If the disk is a system disk that was detached from an ECS instance, no limits apply to the billing method of the disk.
-     *   - If the disk is an elastic ephemeral disk that was detached from an ECS instance, the disk can be attached only to the instance.
-     * - When you attach the disk as the system disk to an ECS instance, take note of the following items:
-     *   - The ECS instance must be the original instance from which the system disk was detached.
-     *   - The ECS instance must be in the **Stopped** (`Stopped`) state.
-     *   - You must configure logon credentials for the ECS instance.
-     *   - The disk cannot be an elastic ephemeral disk.
-     *   - For more information about how to attach a system disk, see [Detach or attach a system disk](https://help.aliyun.com/document_detail/146752.html).
-     * - If the response contains `{"OperationLocks": {"LockReason" : "security"}}` when you query information about an ECS instance, the instance is locked for security reasons. No operations are allowed on the instance.
+     * When you call this operation, take note of the following items:
+     * - The instance and the disk must be in the same zone.
+     * - The disk must be in the **Available** (`Available`) state.
+     * - When you attach a data disk:
+     *     - The destination ECS instance must be in the **Running** (`Running`) or **Stopped** (`Stopped`) state.
+     *     - If the disk is separately purchased, the billing method must be pay-as-you-go.
+     *     - A system disk that was uninstalled from an ECS instance can be attached as a data disk without billable methods restrictions.
+     *     - An elastic ephemeral disk that has been detached can only be re-attached to its original instance.
+     * - When you attach a system disk:
+     *     - The destination ECS instance must be the original instance from which the system disk was detached.
+     *     - The destination ECS instance must be in the **Stopped** (`Stopped`) state.
+     *     - You must specify the logon credential for the instance.
+     *     - Elastic ephemeral disks cannot be attached as system disks.
+     *     - For more information about attaching system disks, see [Detach or attach a system disk](https://help.aliyun.com/document_detail/146752.html).
+     * - When you query ECS instance information, if the response contains `{"OperationLocks": {"LockReason" : "security"}}`, all operations are prohibited.
+     * <props="china">
+     * - A disk with the multi-attach attribute enabled can only be attached to instances that support the NVMe protocol.
+     *    For more information, see [Standard SSDs that support NVMe](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
      *
      * @param request - AttachDiskRequest
      * @returns AttachDiskResponse
@@ -708,7 +714,7 @@ export default class Client extends OpenApi {
      */
     authorizeSecurityGroupEgress(request: $_model.AuthorizeSecurityGroupEgressRequest): Promise<$_model.AuthorizeSecurityGroupEgressResponse>;
     /**
-     * Cancels an auto snapshot policy for one or more disks.
+     * Cancels the automatic snapshot policy for one or more cloud disks.
      *
      * @param request - CancelAutoSnapshotPolicyRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -716,7 +722,7 @@ export default class Client extends OpenApi {
      */
     cancelAutoSnapshotPolicyWithOptions(request: $_model.CancelAutoSnapshotPolicyRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CancelAutoSnapshotPolicyResponse>;
     /**
-     * Cancels an auto snapshot policy for one or more disks.
+     * Cancels the automatic snapshot policy for one or more cloud disks.
      *
      * @param request - CancelAutoSnapshotPolicyRequest
      * @returns CancelAutoSnapshotPolicyResponse
@@ -748,10 +754,10 @@ export default class Client extends OpenApi {
      */
     cancelCopyImage(request: $_model.CancelCopyImageRequest): Promise<$_model.CancelCopyImageResponse>;
     /**
-     * Cancels an image build task.
+     * Cancels an image building task.
      *
      * @remarks
-     * Before you call this operation, make sure that the image build task you want to cancel is in the PREPARING, REPAIRING, or BUILDING state.
+     * Before you call this operation, make sure that the image building task you want to cancel is in the PREPARING, REPAIRING, or BUILDING state.
      *
      * @param request - CancelImagePipelineExecutionRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -759,10 +765,10 @@ export default class Client extends OpenApi {
      */
     cancelImagePipelineExecutionWithOptions(request: $_model.CancelImagePipelineExecutionRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CancelImagePipelineExecutionResponse>;
     /**
-     * Cancels an image build task.
+     * Cancels an image building task.
      *
      * @remarks
-     * Before you call this operation, make sure that the image build task you want to cancel is in the PREPARING, REPAIRING, or BUILDING state.
+     * Before you call this operation, make sure that the image building task you want to cancel is in the PREPARING, REPAIRING, or BUILDING state.
      *
      * @param request - CancelImagePipelineExecutionRequest
      * @returns CancelImagePipelineExecutionResponse
@@ -818,29 +824,29 @@ export default class Client extends OpenApi {
      */
     cancelTask(request: $_model.CancelTaskRequest): Promise<$_model.CancelTaskResponse>;
     /**
-     * Cloud disk cloning allows you to quickly create a new cloud disk in the same availability zone containing the same data as the source disk. You can customize the new disk\\"s capacity, type, and encryption attributes. After attaching the disk to an instance, you can use it to rapidly replicate business data or scale your services horizontally.
+     * Disk cloning allows you to quickly replicate a disk with the same data as the source disk in the same zone. The cloned disk supports custom capacity, type, and encryption attributes. After you attach the cloned disk to an instance, you can quickly replicate business data or horizontally scale services.
      *
      * @remarks
-     * > The cloud disk cloning feature is free. However, the resulting destination disk is billed based on block storage rules. Charges vary by disk type and can include capacity, provisioned performance, and burst performance. Billing for all items begins at creation—except for burst performance fees, which are charged only after a burst occurs—and applies regardless of whether the disk is attached to an instance.
-     * ### Usage
-     * - This is an asynchronous operation. After a successful call, call the DescribeTasks operation with the returned taskGroupId to query the task\\"s status.
+     * > The disk cloning feature itself is free of charge. However, the new disk generated by cloning is billed based on block storage billing rules. Billable items vary by disk type and include disk capacity fees, provisioned performance fees, and performance burst fees. Except for performance burst fees, which are billed after a burst occurs, other fees start to accrue after the disk is created, regardless of whether the disk is attached to an instance.
+     * ### Usage notes
+     * - This is an asynchronous operation. After a successful call, use the taskGroupId and call the DescribeTasks operation to query the execution result.
      * ### Features
-     * - You can only clone ESSD cloud disks (cloud_essd, cloud_auto, cloud_essd_entry, and cloud_regional_disk_auto) to create a `destination disk`, which must also be an ESSD type.
-     *   - A non-zone-redundant cloud disk can only be cloned to a non-zone-redundant disk. A zone-redundant cloud disk can only be cloned to another zone-redundant cloud disk.
-     *   - Local disks and elastic ephemeral disks do not support cloning and cannot be used as either a source disk or a destination disk.
-     * - You can specify the type and performance level for the `destination disk`.
-     * - You can specify the capacity for the `destination disk`, but its capacity must be greater than or equal to that of the `source disk`.
-     * - You can configure provisioned performance and burst performance for the `destination disk`, provided that the destination disk type supports these features.
-     * - You can enable encryption and change the encryption key for the `destination disk`. If the `source disk` is encrypted, the destination disk must also be encrypted. However, you can use a different encryption key.
-     * - You can use a subscription cloud disk as the `source disk`. The disk can still be used as a `source disk` even after its subscription expires.
-     * - A `destination disk` created by cloning cannot be re-initialized.
-     * - While you cannot clone entire storage sets or dedicated storage clusters, you can use a disk from within them as a `source disk`. The resulting destination disk is a standalone disk and will not belong to the original storage set or cluster.
-     * - `source disk` status requirements
-     *   - The `source disk` must be "In Use", and its attached instance must be "Running" or "Stopped".
-     *   - The `source disk` must be "Available" and have been attached to an instance at least once.
-     *   - A disk undergoing a configuration modification cannot be used as a `source disk`.
-     *   - A disk that is being scaled up cannot be used as a `source disk`.
-     * - As cloud disk cloning is not supported for hibernated instances, a disk attached to a hibernated instance cannot be used as a `source disk`.
+     * - Cloning supports only ESSD series disks (cloud_essd, cloud_auto, cloud_essd_entry, cloud_regional_disk_auto) as the source, and the cloned `new disk` supports only ESSD series disk types.
+     *   - Non-regional disks can be cloned only to non-regional types. Regional disks can be cloned only to regional disk types.
+     *   - Local disks and elastic ephemeral disks cannot be cloned or used as clone sources.
+     * - You can specify the `new disk` type and performance level during cloning.
+     * - You can specify the `new disk` capacity during cloning. The new disk capacity must be greater than or equal to the `source disk` capacity.
+     * - You can configure provisioned performance and performance burst for the `new disk` during cloning, provided that the destination disk type supports provisioned performance and performance burst.
+     * - You can specify encryption or change the encryption key for the `new disk` during cloning. If the `source disk` is encrypted, you cannot clone it into an unencrypted disk, but you can change the encryption key.
+     * - You can use a subscription disk as the `source disk` for cloning, even if the subscription disk has expired.
+     * - The cloned `new disk` does not support reinitialization.
+     * - Cloning does not support storage sets or dedicated block storage clusters. However, disks in these resources can be used as the `source disk`. The cloned disk will not be in the storage set or dedicated block storage cluster.
+     * - `Source disk` status restrictions:
+     *   - The `source disk` status is "In Use" and the corresponding instance status is "Running" or "Stopped".
+     *   - The `source disk` status is "Available" and the disk has been previously attached.
+     *   - Disks undergoing specification changes cannot be used as the `source disk`.
+     *   - Disks undergoing expansion cannot be used as the `source disk`.
+     * - Disk cloning is not supported for instance hibernation scenarios. If a disk is on a hibernated instance, it cannot be used as the `source disk`.
      *
      * @param request - CloneDisksRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -848,29 +854,29 @@ export default class Client extends OpenApi {
      */
     cloneDisksWithOptions(request: $_model.CloneDisksRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CloneDisksResponse>;
     /**
-     * Cloud disk cloning allows you to quickly create a new cloud disk in the same availability zone containing the same data as the source disk. You can customize the new disk\\"s capacity, type, and encryption attributes. After attaching the disk to an instance, you can use it to rapidly replicate business data or scale your services horizontally.
+     * Disk cloning allows you to quickly replicate a disk with the same data as the source disk in the same zone. The cloned disk supports custom capacity, type, and encryption attributes. After you attach the cloned disk to an instance, you can quickly replicate business data or horizontally scale services.
      *
      * @remarks
-     * > The cloud disk cloning feature is free. However, the resulting destination disk is billed based on block storage rules. Charges vary by disk type and can include capacity, provisioned performance, and burst performance. Billing for all items begins at creation—except for burst performance fees, which are charged only after a burst occurs—and applies regardless of whether the disk is attached to an instance.
-     * ### Usage
-     * - This is an asynchronous operation. After a successful call, call the DescribeTasks operation with the returned taskGroupId to query the task\\"s status.
+     * > The disk cloning feature itself is free of charge. However, the new disk generated by cloning is billed based on block storage billing rules. Billable items vary by disk type and include disk capacity fees, provisioned performance fees, and performance burst fees. Except for performance burst fees, which are billed after a burst occurs, other fees start to accrue after the disk is created, regardless of whether the disk is attached to an instance.
+     * ### Usage notes
+     * - This is an asynchronous operation. After a successful call, use the taskGroupId and call the DescribeTasks operation to query the execution result.
      * ### Features
-     * - You can only clone ESSD cloud disks (cloud_essd, cloud_auto, cloud_essd_entry, and cloud_regional_disk_auto) to create a `destination disk`, which must also be an ESSD type.
-     *   - A non-zone-redundant cloud disk can only be cloned to a non-zone-redundant disk. A zone-redundant cloud disk can only be cloned to another zone-redundant cloud disk.
-     *   - Local disks and elastic ephemeral disks do not support cloning and cannot be used as either a source disk or a destination disk.
-     * - You can specify the type and performance level for the `destination disk`.
-     * - You can specify the capacity for the `destination disk`, but its capacity must be greater than or equal to that of the `source disk`.
-     * - You can configure provisioned performance and burst performance for the `destination disk`, provided that the destination disk type supports these features.
-     * - You can enable encryption and change the encryption key for the `destination disk`. If the `source disk` is encrypted, the destination disk must also be encrypted. However, you can use a different encryption key.
-     * - You can use a subscription cloud disk as the `source disk`. The disk can still be used as a `source disk` even after its subscription expires.
-     * - A `destination disk` created by cloning cannot be re-initialized.
-     * - While you cannot clone entire storage sets or dedicated storage clusters, you can use a disk from within them as a `source disk`. The resulting destination disk is a standalone disk and will not belong to the original storage set or cluster.
-     * - `source disk` status requirements
-     *   - The `source disk` must be "In Use", and its attached instance must be "Running" or "Stopped".
-     *   - The `source disk` must be "Available" and have been attached to an instance at least once.
-     *   - A disk undergoing a configuration modification cannot be used as a `source disk`.
-     *   - A disk that is being scaled up cannot be used as a `source disk`.
-     * - As cloud disk cloning is not supported for hibernated instances, a disk attached to a hibernated instance cannot be used as a `source disk`.
+     * - Cloning supports only ESSD series disks (cloud_essd, cloud_auto, cloud_essd_entry, cloud_regional_disk_auto) as the source, and the cloned `new disk` supports only ESSD series disk types.
+     *   - Non-regional disks can be cloned only to non-regional types. Regional disks can be cloned only to regional disk types.
+     *   - Local disks and elastic ephemeral disks cannot be cloned or used as clone sources.
+     * - You can specify the `new disk` type and performance level during cloning.
+     * - You can specify the `new disk` capacity during cloning. The new disk capacity must be greater than or equal to the `source disk` capacity.
+     * - You can configure provisioned performance and performance burst for the `new disk` during cloning, provided that the destination disk type supports provisioned performance and performance burst.
+     * - You can specify encryption or change the encryption key for the `new disk` during cloning. If the `source disk` is encrypted, you cannot clone it into an unencrypted disk, but you can change the encryption key.
+     * - You can use a subscription disk as the `source disk` for cloning, even if the subscription disk has expired.
+     * - The cloned `new disk` does not support reinitialization.
+     * - Cloning does not support storage sets or dedicated block storage clusters. However, disks in these resources can be used as the `source disk`. The cloned disk will not be in the storage set or dedicated block storage cluster.
+     * - `Source disk` status restrictions:
+     *   - The `source disk` status is "In Use" and the corresponding instance status is "Running" or "Stopped".
+     *   - The `source disk` status is "Available" and the disk has been previously attached.
+     *   - Disks undergoing specification changes cannot be used as the `source disk`.
+     *   - Disks undergoing expansion cannot be used as the `source disk`.
+     * - Disk cloning is not supported for instance hibernation scenarios. If a disk is on a hibernated instance, it cannot be used as the `source disk`.
      *
      * @param request - CloneDisksRequest
      * @returns CloneDisksResponse
@@ -968,11 +974,11 @@ export default class Client extends OpenApi {
      */
     copyImage(request: $_model.CopyImageRequest): Promise<$_model.CopyImageResponse>;
     /**
-     * Copies a standard or encrypted snapshot from one region to another.
+     * Copies a standard snapshot or encrypted snapshot from one region to another.
      *
      * @remarks
-     * When you call this operation, take note of the following item:
-     * - New snapshots (snapshot copies) cannot be used to roll back the disks for which source snapshots (copied snapshots) were created.
+     * When you call this operation, take note of the following items:
+     * - The new snapshot cannot be used to roll back the cloud disk that is associated with the source snapshot.
      * - Local snapshots cannot be copied.
      *
      * @param request - CopySnapshotRequest
@@ -981,11 +987,11 @@ export default class Client extends OpenApi {
      */
     copySnapshotWithOptions(request: $_model.CopySnapshotRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CopySnapshotResponse>;
     /**
-     * Copies a standard or encrypted snapshot from one region to another.
+     * Copies a standard snapshot or encrypted snapshot from one region to another.
      *
      * @remarks
-     * When you call this operation, take note of the following item:
-     * - New snapshots (snapshot copies) cannot be used to roll back the disks for which source snapshots (copied snapshots) were created.
+     * When you call this operation, take note of the following items:
+     * - The new snapshot cannot be used to roll back the cloud disk that is associated with the source snapshot.
      * - Local snapshots cannot be copied.
      *
      * @param request - CopySnapshotRequest
@@ -1040,13 +1046,13 @@ export default class Client extends OpenApi {
      */
     createActivation(request: $_model.CreateActivationRequest): Promise<$_model.CreateActivationResponse>;
     /**
-     * Create an auto provisioning group.
+     * Creates an auto provisioning group.
      *
      * @remarks
-     * - Auto provisioning is a solution that uses spot instances and pay-as-you-go instances to quickly deploy instance clusters. It supports one-click deployment of instance clusters across billing methods, zones, and instance families. For more information, see [Use the auto provisioning group API to create multiple ECS instances](https://help.aliyun.com/document_detail/200772.html).
-     * - Auto provisioning schedules and maintains compute resources through provisioning groups. Use auto provisioning groups to provide stable computing power and mitigate instability caused by the spot instance reclamation mechanism.
-     * - Auto provisioning is a free feature. You pay only for the instance resources created through the auto provisioning group. For more information, see [Spot instance billing](https://help.aliyun.com/document_detail/52088.html) and [Pay-as-you-go](https://help.aliyun.com/document_detail/40653.html).
-     * - When you specify both a launch template (`LaunchTemplateId`) and launch configuration parameters (`LaunchConfiguration.*`), the system prioritizes the launch template.
+     * - Auto provisioning is a solution that uses spot instances and pay-as-you-go instances to quickly deploy instance clusters. It supports one-click deployment of instance clusters across billing methods, zones, and instance families. For more information, see [Use the auto provisioning group API to create ECS instances in batches](https://help.aliyun.com/document_detail/200772.html).
+     * - Auto provisioning uses provisioning groups to schedule and maintain compute resources. You can use an auto provisioning group to steadily provide computing power and mitigate the instability caused by the reclaim mechanism of spot instances.
+     * - Auto provisioning is a free feature, but you are charged for the instance resources created by the auto provisioning group. For more information, see [Spot instance billing](https://help.aliyun.com/document_detail/52088.html) and [Pay-as-you-go](https://help.aliyun.com/document_detail/40653.html).
+     * - If you specify both a launch template (`LaunchTemplateId`) and launch configuration information (`LaunchConfiguration.*`), the launch template takes precedence.
      *
      * @param tmpReq - CreateAutoProvisioningGroupRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1054,28 +1060,28 @@ export default class Client extends OpenApi {
      */
     createAutoProvisioningGroupWithOptions(tmpReq: $_model.CreateAutoProvisioningGroupRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateAutoProvisioningGroupResponse>;
     /**
-     * Create an auto provisioning group.
+     * Creates an auto provisioning group.
      *
      * @remarks
-     * - Auto provisioning is a solution that uses spot instances and pay-as-you-go instances to quickly deploy instance clusters. It supports one-click deployment of instance clusters across billing methods, zones, and instance families. For more information, see [Use the auto provisioning group API to create multiple ECS instances](https://help.aliyun.com/document_detail/200772.html).
-     * - Auto provisioning schedules and maintains compute resources through provisioning groups. Use auto provisioning groups to provide stable computing power and mitigate instability caused by the spot instance reclamation mechanism.
-     * - Auto provisioning is a free feature. You pay only for the instance resources created through the auto provisioning group. For more information, see [Spot instance billing](https://help.aliyun.com/document_detail/52088.html) and [Pay-as-you-go](https://help.aliyun.com/document_detail/40653.html).
-     * - When you specify both a launch template (`LaunchTemplateId`) and launch configuration parameters (`LaunchConfiguration.*`), the system prioritizes the launch template.
+     * - Auto provisioning is a solution that uses spot instances and pay-as-you-go instances to quickly deploy instance clusters. It supports one-click deployment of instance clusters across billing methods, zones, and instance families. For more information, see [Use the auto provisioning group API to create ECS instances in batches](https://help.aliyun.com/document_detail/200772.html).
+     * - Auto provisioning uses provisioning groups to schedule and maintain compute resources. You can use an auto provisioning group to steadily provide computing power and mitigate the instability caused by the reclaim mechanism of spot instances.
+     * - Auto provisioning is a free feature, but you are charged for the instance resources created by the auto provisioning group. For more information, see [Spot instance billing](https://help.aliyun.com/document_detail/52088.html) and [Pay-as-you-go](https://help.aliyun.com/document_detail/40653.html).
+     * - If you specify both a launch template (`LaunchTemplateId`) and launch configuration information (`LaunchConfiguration.*`), the launch template takes precedence.
      *
      * @param request - CreateAutoProvisioningGroupRequest
      * @returns CreateAutoProvisioningGroupResponse
      */
     createAutoProvisioningGroup(request: $_model.CreateAutoProvisioningGroupRequest): Promise<$_model.CreateAutoProvisioningGroupResponse>;
     /**
-     * Creates an automatic snapshot policy in a specific region. You can specify the schedule on which to create automatic snapshots, the retention period of the automatic snapshots, and whether to enable cross-region replication for the snapshots in the automatic snapshot policy. The automatic snapshot policy can be applied to create snapshots for system disks or data disks to back up disk data.
+     * Creates an automatic snapshot policy in a specified region. You can specify the repeat cycle, retention period, and cross-region backup settings for automatic snapshots to back up data on system disks or data disks.
      *
      * @remarks
-     * Before you call this operation, learn about how to [create an automatic snapshot policy](https://help.aliyun.com/document_detail/127767.html).
+     * Before you call this operation, read [Create an automatic snapshot policy](https://help.aliyun.com/document_detail/127767.html).
      * Take note of the following items:
-     * - You can create up to 100 automatic snapshot policies per region for a single Alibaba Cloud account. If the maximum number of automatic snapshots for a disk is reached and a new snapshot creation task is created, the system deletes the oldest automatic snapshot of the disk.
-     * - If the instance to which a disk is attached is being stopped or restarted, the system cannot create snapshots for the disk based on the associated automatic snapshot policy.
-     * - If cross-region snapshot replication is enabled and no encryption parameters are configured, encrypted snapshots are copied to the destination region and snapshot copies are encrypted by using the service key of the destination region. For more information about the limits on cross-region snapshot replication, see [Copy a snapshot](https://help.aliyun.com/document_detail/159441.html).
-     * After the automatic snapshot policy is created, call the [ApplyAutoSnapshotPolicy](https://help.aliyun.com/document_detail/25531.html) operation to apply the policy to disks. If you want to modify the automatic snapshot policy, call the [ModifyAutoSnapshotPolicyEx](https://help.aliyun.com/document_detail/25529.html) operation.
+     * - You can create a maximum of 100 automatic snapshot policies in a region for an Alibaba Cloud account. When the number of automatic snapshots for a disk reaches the quota limit, the system deletes the earliest automatic snapshot created by the automatic snapshot policy when a new snapshot task is initiated.
+     * - The system does not execute automatic snapshot policies when an ECS instance has a pending stop or restart task.
+     * - If cross-region snapshot replication is enabled and no encryption parameters are configured, encrypted snapshots are replicated to the destination region by using the service key of the destination region by default. For more information about cross-region snapshot replication, see [Copy a snapshot](https://help.aliyun.com/document_detail/159441.html).
+     * After you create an automatic snapshot policy, call [ApplyAutoSnapshotPolicy](https://help.aliyun.com/document_detail/25531.html) to apply the policy to disks. To modify an automatic snapshot policy, call [ModifyAutoSnapshotPolicyEx](https://help.aliyun.com/document_detail/25529.html).
      *
      * @param request - CreateAutoSnapshotPolicyRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1083,15 +1089,15 @@ export default class Client extends OpenApi {
      */
     createAutoSnapshotPolicyWithOptions(request: $_model.CreateAutoSnapshotPolicyRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateAutoSnapshotPolicyResponse>;
     /**
-     * Creates an automatic snapshot policy in a specific region. You can specify the schedule on which to create automatic snapshots, the retention period of the automatic snapshots, and whether to enable cross-region replication for the snapshots in the automatic snapshot policy. The automatic snapshot policy can be applied to create snapshots for system disks or data disks to back up disk data.
+     * Creates an automatic snapshot policy in a specified region. You can specify the repeat cycle, retention period, and cross-region backup settings for automatic snapshots to back up data on system disks or data disks.
      *
      * @remarks
-     * Before you call this operation, learn about how to [create an automatic snapshot policy](https://help.aliyun.com/document_detail/127767.html).
+     * Before you call this operation, read [Create an automatic snapshot policy](https://help.aliyun.com/document_detail/127767.html).
      * Take note of the following items:
-     * - You can create up to 100 automatic snapshot policies per region for a single Alibaba Cloud account. If the maximum number of automatic snapshots for a disk is reached and a new snapshot creation task is created, the system deletes the oldest automatic snapshot of the disk.
-     * - If the instance to which a disk is attached is being stopped or restarted, the system cannot create snapshots for the disk based on the associated automatic snapshot policy.
-     * - If cross-region snapshot replication is enabled and no encryption parameters are configured, encrypted snapshots are copied to the destination region and snapshot copies are encrypted by using the service key of the destination region. For more information about the limits on cross-region snapshot replication, see [Copy a snapshot](https://help.aliyun.com/document_detail/159441.html).
-     * After the automatic snapshot policy is created, call the [ApplyAutoSnapshotPolicy](https://help.aliyun.com/document_detail/25531.html) operation to apply the policy to disks. If you want to modify the automatic snapshot policy, call the [ModifyAutoSnapshotPolicyEx](https://help.aliyun.com/document_detail/25529.html) operation.
+     * - You can create a maximum of 100 automatic snapshot policies in a region for an Alibaba Cloud account. When the number of automatic snapshots for a disk reaches the quota limit, the system deletes the earliest automatic snapshot created by the automatic snapshot policy when a new snapshot task is initiated.
+     * - The system does not execute automatic snapshot policies when an ECS instance has a pending stop or restart task.
+     * - If cross-region snapshot replication is enabled and no encryption parameters are configured, encrypted snapshots are replicated to the destination region by using the service key of the destination region by default. For more information about cross-region snapshot replication, see [Copy a snapshot](https://help.aliyun.com/document_detail/159441.html).
+     * After you create an automatic snapshot policy, call [ApplyAutoSnapshotPolicy](https://help.aliyun.com/document_detail/25531.html) to apply the policy to disks. To modify an automatic snapshot policy, call [ModifyAutoSnapshotPolicyEx](https://help.aliyun.com/document_detail/25529.html).
      *
      * @param request - CreateAutoSnapshotPolicyRequest
      * @returns CreateAutoSnapshotPolicyResponse
@@ -1241,14 +1247,14 @@ export default class Client extends OpenApi {
      * Creates a pay-as-you-go or subscription data disk.
      *
      * @remarks
-     * - When you create a disk, you can enable the multi-attach feature (`MultiAttach`). Learn about this attribute and its limits before you use it. For more information, see [ESSD cloud disks that support NVMe](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
+     * - You can enable the multi-attach attribute (`MultiAttach`) when you create a disk. Learn about this attribute and its limits before you use it. For more information, see [ESSD cloud disks that support NVMe](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
      * - The following disk types can be created: basic disks, ultra disks, standard SSDs, enterprise SSDs, ESSD Entry disks, regional Enterprise SSDs (ESSDs), ESSD AutoPL disks, elastic ephemeral disks - Standard Edition, and elastic ephemeral disks - Premium Edition.
-     * - To create a disk, complete [real-name registration](https://account.console.aliyun.com/#/auth/home).
-     * - Creating a disk incurs fees. Learn about the billing method of Elastic Compute Service (ECS) in advance. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
+     * - Complete real-name registration before you create a disk. Go to [Real-name registration](https://account.console.aliyun.com/#/auth/home) in your account information.
+     * - Creating a disk incurs charges. Learn about the billing methods of Elastic Compute Service (ECS) in advance. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
      * - Default settings when you create a disk:
-     *   - Automatic snapshots of the disk are deleted when the disk is deleted. That is, `DeleteAutoSnapshot` is set to `true`. You can call [DescribeDisks](https://help.aliyun.com/document_detail/2679767.html) to query the parameter settings, and call [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to modify the property.
-     *   - When you create an enterprise SSD, if you do not configure a performance level, the default level is PL1. You can call [ModifyDiskSpec](https://help.aliyun.com/document_detail/123780.html) to change the performance level.
-     *   - The billing method is pay-as-you-go, which means the `Portable` property defaults to `true`.
+     *   - Automatic snapshots of the disk are deleted when the disk is deleted. That is, `DeleteAutoSnapshot` is set to `true`. You can invoke [DescribeDisks](https://help.aliyun.com/document_detail/2679767.html) to query the parameter settings, and invoke [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to modify the property.
+     *   - When you create an enterprise SSD, if you do not configure the performance level, the default level is PL1. You can invoke [ModifyDiskSpec](https://help.aliyun.com/document_detail/123780.html) to change the performance level.
+     *   - The billing method is pay-as-you-go. That is, the `Portable` property defaults to `true`.
      *
      * @param request - CreateDiskRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1259,14 +1265,14 @@ export default class Client extends OpenApi {
      * Creates a pay-as-you-go or subscription data disk.
      *
      * @remarks
-     * - When you create a disk, you can enable the multi-attach feature (`MultiAttach`). Learn about this attribute and its limits before you use it. For more information, see [ESSD cloud disks that support NVMe](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
+     * - You can enable the multi-attach attribute (`MultiAttach`) when you create a disk. Learn about this attribute and its limits before you use it. For more information, see [ESSD cloud disks that support NVMe](https://help.aliyun.com/document_detail/256487.html) and [Use the multi-attach feature](https://help.aliyun.com/document_detail/262105.html).
      * - The following disk types can be created: basic disks, ultra disks, standard SSDs, enterprise SSDs, ESSD Entry disks, regional Enterprise SSDs (ESSDs), ESSD AutoPL disks, elastic ephemeral disks - Standard Edition, and elastic ephemeral disks - Premium Edition.
-     * - To create a disk, complete [real-name registration](https://account.console.aliyun.com/#/auth/home).
-     * - Creating a disk incurs fees. Learn about the billing method of Elastic Compute Service (ECS) in advance. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
+     * - Complete real-name registration before you create a disk. Go to [Real-name registration](https://account.console.aliyun.com/#/auth/home) in your account information.
+     * - Creating a disk incurs charges. Learn about the billing methods of Elastic Compute Service (ECS) in advance. For more information, see [Billing overview](https://help.aliyun.com/document_detail/25398.html).
      * - Default settings when you create a disk:
-     *   - Automatic snapshots of the disk are deleted when the disk is deleted. That is, `DeleteAutoSnapshot` is set to `true`. You can call [DescribeDisks](https://help.aliyun.com/document_detail/2679767.html) to query the parameter settings, and call [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to modify the property.
-     *   - When you create an enterprise SSD, if you do not configure a performance level, the default level is PL1. You can call [ModifyDiskSpec](https://help.aliyun.com/document_detail/123780.html) to change the performance level.
-     *   - The billing method is pay-as-you-go, which means the `Portable` property defaults to `true`.
+     *   - Automatic snapshots of the disk are deleted when the disk is deleted. That is, `DeleteAutoSnapshot` is set to `true`. You can invoke [DescribeDisks](https://help.aliyun.com/document_detail/2679767.html) to query the parameter settings, and invoke [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to modify the property.
+     *   - When you create an enterprise SSD, if you do not configure the performance level, the default level is PL1. You can invoke [ModifyDiskSpec](https://help.aliyun.com/document_detail/123780.html) to change the performance level.
+     *   - The billing method is pay-as-you-go. That is, the `Portable` property defaults to `true`.
      *
      * @param request - CreateDiskRequest
      * @returns CreateDiskResponse
@@ -1353,26 +1359,25 @@ export default class Client extends OpenApi {
      */
     createHpcCluster(request: $_model.CreateHpcClusterRequest): Promise<$_model.CreateHpcClusterResponse>;
     /**
-     * Create a custom image. You can then use the image to create ECS instances (`RunInstances`) or replace the system disk of an instance (`ReplaceSystemDisk`).
+     * Creates a custom image. You can use the created custom image to create ECS instances (RunInstances) or replace the system disk of an instance (ReplaceSystemDisk).
      *
      * @remarks
-     * ### Usage notes
-     * - This operation is asynchronous. A successful request returns an image ID, but the image is not created immediately. You can call [DescribeImage](https://help.aliyun.com/document_detail/2679797.html) to query the image status. The image is ready for use when its status changes to `Available`. For more information, see [Overview of custom images](https://help.aliyun.com/document_detail/172789.html).
-     * - If the response to a query for ECS instance information contains `{"OperationLocks": {"LockReason" : "security"}}`, you cannot create a custom image from the instance.
-     * - We recommend configuring the image check parameter `DetectionStrategy` when you create an image. This helps the system optimize your image. For more information, see [Overview of image check](https://help.aliyun.com/document_detail/439819.html).
-     * This operation provides three methods to create a custom image. The request parameters are prioritized as follows: InstanceId > DiskDeviceMapping > SnapshotId. If your request includes two or more of these parameters, the operation creates the image based on the parameter with the highest priority.
+     * ### Before you begin
+     * - This is an asynchronous operation. After a request to create a custom image is sent, the image ID is returned. However, the image creation is not immediately complete. Call [DescribeImage](https://help.aliyun.com/document_detail/2679797.html) to query the image information. When the status in the response is `Available`, the image is created and ready for use. For more information, see [Custom image overview](https://help.aliyun.com/document_detail/172789.html).
+     * - When you query ECS instance information, if the response contains {"OperationLocks": {"LockReason" : "security"}}, you cannot create a custom image.
+     * - Configure the image detection parameter `DetectionStrategy` when creating an image to help the system optimize your image. For more information, see [Image detection overview](https://help.aliyun.com/document_detail/439819.html).
+     * The following describes three methods to create a custom image by calling this operation. The priority of request parameters is: InstanceId > DiskDeviceMapping > SnapshotId. If your request contains two or more of these parameters, the image is created based on the parameter with the highest priority.
      * - **Create a custom image from an instance**: Specify the instance ID (`InstanceId`).
-     *   - The instance must be in the `Running` or `Stopped` state.
-     *   - A successful call creates a new snapshot for each cloud disk of the instance.
-     *   >Notice:
-     *   Data cached in memory on a running instance may not be written to disk. This can cause data inconsistencies between the custom image and the instance. We recommend stopping the instance by calling [StopInstances](https://help.aliyun.com/document_detail/155372.html) before creating an image.
-     *
-     * - **Create a custom image from a snapshot (snapshots created on or before July 15, 2013, cannot be used).**
-     *   - **Create a custom image from a system disk snapshot**: Specify only the snapshot ID of the instance\\"s system disk (`SnapshotId`).
-     *   - **Create a custom image from a system disk snapshot and data disk snapshots**: Map the snapshots to disks by using the `DiskDeviceMapping` parameter.
-     *     - You can specify only one system disk snapshot.
-     *     - You can specify up to 16 data disk snapshots. If you do not specify `DiskDeviceMapping.N.SnapshotId`, the system creates an empty data disk with the default capacity.
-     * > When you release an instance, the system retains its system disk and converts it to a pay-as-you-go data disk. You cannot use snapshots of this disk to create custom images. If you need a custom image, create it before you release the instance.
+     *   - The instance must be in the Running (`Running`) or Stopped (`Stopped`) state.
+     *   - After the operation is called, a new snapshot is created for each disk of the instance.
+     *   >Notice: Because a running instance may have cached data that has not been written to disks, the data of the created custom image may be inconsistent with the instance data. Stop the instance ([StopInstances](https://help.aliyun.com/document_detail/155372.html)) before creating the image.
+     * - **Create a custom image from a snapshot (the specified snapshot cannot be one created on or before July 15, 2013.)**
+     *   - **Create a custom image from a system disk snapshot**: Specify only the snapshot ID of the instance system disk (`SnapshotId`).
+     *   - **Create a custom image from system disk and data disk snapshots**: Establish data associations among multiple disks (`DiskDeviceMapping`).
+     *     -  Only one system disk snapshot can be specified.
+     *     -  You can specify multiple data disk snapshots, up to a maximum of 16. If `DiskDeviceMapping.N.SnapshotId` is not specified, an empty data disk with the default capacity is created.
+     *
+     * > When an instance is released, the system disk is retained as a pay-as-you-go data disk. Snapshots created from this disk do not support creating custom images. Create a custom image before releasing the instance as needed.
      *
      * @param request - CreateImageRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1380,26 +1385,25 @@ export default class Client extends OpenApi {
      */
     createImageWithOptions(request: $_model.CreateImageRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateImageResponse>;
     /**
-     * Create a custom image. You can then use the image to create ECS instances (`RunInstances`) or replace the system disk of an instance (`ReplaceSystemDisk`).
+     * Creates a custom image. You can use the created custom image to create ECS instances (RunInstances) or replace the system disk of an instance (ReplaceSystemDisk).
      *
      * @remarks
-     * ### Usage notes
-     * - This operation is asynchronous. A successful request returns an image ID, but the image is not created immediately. You can call [DescribeImage](https://help.aliyun.com/document_detail/2679797.html) to query the image status. The image is ready for use when its status changes to `Available`. For more information, see [Overview of custom images](https://help.aliyun.com/document_detail/172789.html).
-     * - If the response to a query for ECS instance information contains `{"OperationLocks": {"LockReason" : "security"}}`, you cannot create a custom image from the instance.
-     * - We recommend configuring the image check parameter `DetectionStrategy` when you create an image. This helps the system optimize your image. For more information, see [Overview of image check](https://help.aliyun.com/document_detail/439819.html).
-     * This operation provides three methods to create a custom image. The request parameters are prioritized as follows: InstanceId > DiskDeviceMapping > SnapshotId. If your request includes two or more of these parameters, the operation creates the image based on the parameter with the highest priority.
+     * ### Before you begin
+     * - This is an asynchronous operation. After a request to create a custom image is sent, the image ID is returned. However, the image creation is not immediately complete. Call [DescribeImage](https://help.aliyun.com/document_detail/2679797.html) to query the image information. When the status in the response is `Available`, the image is created and ready for use. For more information, see [Custom image overview](https://help.aliyun.com/document_detail/172789.html).
+     * - When you query ECS instance information, if the response contains {"OperationLocks": {"LockReason" : "security"}}, you cannot create a custom image.
+     * - Configure the image detection parameter `DetectionStrategy` when creating an image to help the system optimize your image. For more information, see [Image detection overview](https://help.aliyun.com/document_detail/439819.html).
+     * The following describes three methods to create a custom image by calling this operation. The priority of request parameters is: InstanceId > DiskDeviceMapping > SnapshotId. If your request contains two or more of these parameters, the image is created based on the parameter with the highest priority.
      * - **Create a custom image from an instance**: Specify the instance ID (`InstanceId`).
-     *   - The instance must be in the `Running` or `Stopped` state.
-     *   - A successful call creates a new snapshot for each cloud disk of the instance.
-     *   >Notice:
-     *   Data cached in memory on a running instance may not be written to disk. This can cause data inconsistencies between the custom image and the instance. We recommend stopping the instance by calling [StopInstances](https://help.aliyun.com/document_detail/155372.html) before creating an image.
-     *
-     * - **Create a custom image from a snapshot (snapshots created on or before July 15, 2013, cannot be used).**
-     *   - **Create a custom image from a system disk snapshot**: Specify only the snapshot ID of the instance\\"s system disk (`SnapshotId`).
-     *   - **Create a custom image from a system disk snapshot and data disk snapshots**: Map the snapshots to disks by using the `DiskDeviceMapping` parameter.
-     *     - You can specify only one system disk snapshot.
-     *     - You can specify up to 16 data disk snapshots. If you do not specify `DiskDeviceMapping.N.SnapshotId`, the system creates an empty data disk with the default capacity.
-     * > When you release an instance, the system retains its system disk and converts it to a pay-as-you-go data disk. You cannot use snapshots of this disk to create custom images. If you need a custom image, create it before you release the instance.
+     *   - The instance must be in the Running (`Running`) or Stopped (`Stopped`) state.
+     *   - After the operation is called, a new snapshot is created for each disk of the instance.
+     *   >Notice: Because a running instance may have cached data that has not been written to disks, the data of the created custom image may be inconsistent with the instance data. Stop the instance ([StopInstances](https://help.aliyun.com/document_detail/155372.html)) before creating the image.
+     * - **Create a custom image from a snapshot (the specified snapshot cannot be one created on or before July 15, 2013.)**
+     *   - **Create a custom image from a system disk snapshot**: Specify only the snapshot ID of the instance system disk (`SnapshotId`).
+     *   - **Create a custom image from system disk and data disk snapshots**: Establish data associations among multiple disks (`DiskDeviceMapping`).
+     *     -  Only one system disk snapshot can be specified.
+     *     -  You can specify multiple data disk snapshots, up to a maximum of 16. If `DiskDeviceMapping.N.SnapshotId` is not specified, an empty data disk with the default capacity is created.
+     *
+     * > When an instance is released, the system disk is retained as a pay-as-you-go data disk. Snapshots created from this disk do not support creating custom images. Create a custom image before releasing the instance as needed.
      *
      * @param request - CreateImageRequest
      * @returns CreateImageResponse
@@ -1562,15 +1566,15 @@ export default class Client extends OpenApi {
      */
     createKeyPair(request: $_model.CreateKeyPairRequest): Promise<$_model.CreateKeyPairResponse>;
     /**
-     * Create an ECS instance launch template, abbreviated as a template. An instance launch template eliminates the need to enter numerous configuration parameters each time you create an instance.
+     * Creates an ECS instance launch template. A launch template eliminates the need to configure a large number of parameters every time you create an instance.
      *
      * @remarks
-     * After you invoke CreateLaunchTemplate to create a template, Alibaba Cloud automatically generates a default version of the template with version number 1. You can subsequently create multiple versions based on this template by calling `CreateLaunchTemplateVersion`. Version numbers start from 1 and increment sequentially. If you do not specify a template version when creating an instance ([RunInstances](https://help.aliyun.com/document_detail/63440.html)), the default version is used.
-     * A launch template version includes configurations required for instance creation, such as the Region, image ID, instance type, security group ID, and Internet bandwidth. If a particular configuration is not specified in the template version, you must provide it explicitly when creating the instance.
-     * When invoking this API, note the following:
-     * - Each account can create up to 30 launch templates per Region, and each template can have up to 30 versions.
-     * - Most parameters in a launch template are optional. Alibaba Cloud does not validate the existence or validity of parameter values when you create the template. Validation occurs only when you actually create an instance.
-     * - If a configuration is set in the launch template, you cannot omit it when creating an instance ([RunInstances](https://help.aliyun.com/document_detail/63440.html)). For example, if the template sets `HostName=LocalHost`, and you leave `HostName` empty in `RunInstances`, the instance hostname will still be `LocalHost`. To overwrite the `HostName=LocalHost` setting, specify a different value such as `HostName=MyHost` in `RunInstances`.
+     * After you call CreateLaunchTemplate to create a template, a default version with version number 1 is automatically generated. You can then create multiple versions based on this template (`CreateLaunchTemplateVersion`), with version numbers incrementing sequentially from 1. If you do not specify a template version when creating instances ([RunInstances](https://help.aliyun.com/document_detail/63440.html)), the default version is used.
+     * A launch template version contains the configurations for creating instances, such as the region, image ID, instance type, security group ID, and public bandwidth. If a specific configuration is not specified in the version, you must specify it when you create instances.
+     * When you call this operation, take note of the following items:
+     * -   Each account can create up to 30 launch templates per region, and each template can have up to 30 versions.
+     * -   Most parameters in a launch template are optional. When you create a template, Alibaba Cloud does not verify the existence or validity of parameter values. The validity of parameter values is verified only when you create instances.
+     * -   If a configuration is specified in the launch template, it cannot be filtered out when you create instances ([RunInstances](https://help.aliyun.com/document_detail/63440.html)). For example, if the template specifies `HostName=LocalHost` and the `HostName` value is left empty in `RunInstances`, the hostname of the instance is still `LocalHost`. To override the `HostName=LocalHost` configuration, set `HostName=MyHost` or another value in `RunInstances`.
      *
      * @param request - CreateLaunchTemplateRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1578,15 +1582,15 @@ export default class Client extends OpenApi {
      */
     createLaunchTemplateWithOptions(request: $_model.CreateLaunchTemplateRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateLaunchTemplateResponse>;
     /**
-     * Create an ECS instance launch template, abbreviated as a template. An instance launch template eliminates the need to enter numerous configuration parameters each time you create an instance.
+     * Creates an ECS instance launch template. A launch template eliminates the need to configure a large number of parameters every time you create an instance.
      *
      * @remarks
-     * After you invoke CreateLaunchTemplate to create a template, Alibaba Cloud automatically generates a default version of the template with version number 1. You can subsequently create multiple versions based on this template by calling `CreateLaunchTemplateVersion`. Version numbers start from 1 and increment sequentially. If you do not specify a template version when creating an instance ([RunInstances](https://help.aliyun.com/document_detail/63440.html)), the default version is used.
-     * A launch template version includes configurations required for instance creation, such as the Region, image ID, instance type, security group ID, and Internet bandwidth. If a particular configuration is not specified in the template version, you must provide it explicitly when creating the instance.
-     * When invoking this API, note the following:
-     * - Each account can create up to 30 launch templates per Region, and each template can have up to 30 versions.
-     * - Most parameters in a launch template are optional. Alibaba Cloud does not validate the existence or validity of parameter values when you create the template. Validation occurs only when you actually create an instance.
-     * - If a configuration is set in the launch template, you cannot omit it when creating an instance ([RunInstances](https://help.aliyun.com/document_detail/63440.html)). For example, if the template sets `HostName=LocalHost`, and you leave `HostName` empty in `RunInstances`, the instance hostname will still be `LocalHost`. To overwrite the `HostName=LocalHost` setting, specify a different value such as `HostName=MyHost` in `RunInstances`.
+     * After you call CreateLaunchTemplate to create a template, a default version with version number 1 is automatically generated. You can then create multiple versions based on this template (`CreateLaunchTemplateVersion`), with version numbers incrementing sequentially from 1. If you do not specify a template version when creating instances ([RunInstances](https://help.aliyun.com/document_detail/63440.html)), the default version is used.
+     * A launch template version contains the configurations for creating instances, such as the region, image ID, instance type, security group ID, and public bandwidth. If a specific configuration is not specified in the version, you must specify it when you create instances.
+     * When you call this operation, take note of the following items:
+     * -   Each account can create up to 30 launch templates per region, and each template can have up to 30 versions.
+     * -   Most parameters in a launch template are optional. When you create a template, Alibaba Cloud does not verify the existence or validity of parameter values. The validity of parameter values is verified only when you create instances.
+     * -   If a configuration is specified in the launch template, it cannot be filtered out when you create instances ([RunInstances](https://help.aliyun.com/document_detail/63440.html)). For example, if the template specifies `HostName=LocalHost` and the `HostName` value is left empty in `RunInstances`, the hostname of the instance is still `LocalHost`. To override the `HostName=LocalHost` configuration, set `HostName=MyHost` or another value in `RunInstances`.
      *
      * @param request - CreateLaunchTemplateRequest
      * @returns CreateLaunchTemplateResponse
@@ -1924,30 +1928,30 @@ export default class Client extends OpenApi {
      */
     createSimulatedSystemEvents(request: $_model.CreateSimulatedSystemEventsRequest): Promise<$_model.CreateSimulatedSystemEventsResponse>;
     /**
-     * Create a snapshot of a cloud disk.
-     *
-     * @remarks
-     * The instant access feature for snapshots replaces the legacy local snapshot feature. The parameters are described as follows:
-     * - If you used local snapshots before December 14, 2020, you can continue to use the `Category` parameter.
-     * - If you did not use local snapshots before December 14, 2020, no additional configuration is required. New snapshots that are created for ESSD cloud disks (ESSDs, ESSD AutoPL disks, ESSD Entry disks, and zone-redundant ESSDs) have the instant access feature enabled by default. This applies to both manual and automatic snapshots. The instant access-related parameters `InstantAccess`, `InstantAccessRetentionDays`, and `DisableInstantAccess` no longer take effect. The `DescribeSnapshots` and `DescribeSnapshotGroups` API operations return an `Available` parameter that indicates the snapshot\\"s status.
-     * Prerequisites:
-     * - The snapshot feature is enabled. For more information, see [Enable the snapshot feature](https://help.aliyun.com/document_detail/108381.html).
-     * - The cloud disk must be in the **in-use** or **available** state. Note the following points:
-     *   - If the cloud disk is in the **in-use** state, the instance to which the disk is attached must be in the **running** or **stopped** state.
-     *   - If the cloud disk is in the **available** state, you can create snapshots for it only if it has been previously attached to an ECS instance.
-     *   - When you use cloud disks to create dynamic scalable volumes or RAID arrays, we recommend that you use snapshot consistency groups and enable application-consistent snapshots to back up data. A snapshot consistency group ensures the crash consistency and write-order consistency of data written across multiple cloud disks. For more information, see [Create a snapshot consistency group](https://help.aliyun.com/document_detail/199625.html) and [Create an application-consistent snapshot](https://help.aliyun.com/document_detail/208589.html).
-     * Keep the following in mind when creating a snapshot:
-     * - Create snapshots during off-peak hours. During snapshot creation, the I/O performance of the cloud disk decreases by less than 10% and read and write operations may temporarily slow down.
-     * - You cannot use a snapshot that is being created to create a custom image ([CreateImage](https://help.aliyun.com/document_detail/25535.html)).
-     * - The snapshot does not back up incremental data generated on the cloud disk during the creation process.
-     * - If the cloud disk is attached to an ECS instance, do not change the state of the instance, such as stopping or restarting the instance, during snapshot creation. Otherwise, the snapshot creation will fail.
-     * - You cannot resize a cloud disk during snapshot creation. You can resize the cloud disk only after the snapshot is complete.
-     * - You can create a snapshot for a cloud disk that is in the **expired** (`Expired`) state. If the cloud disk is released due to expiration when the snapshot is being created, the snapshot in the **creating** (`Creating`) state is also deleted.
-     * - After a snapshot is created, you are charged for the snapshot based on its size. The fees are settled on a per-region basis. For more information, see [Snapshots](https://help.aliyun.com/document_detail/56159.html).
-     * - You cannot create a snapshot for a cloud disk in the following cases:
-     *   - The number of manual snapshots of the cloud disk has reached the upper limit. For more information, see [Limits](~~25412#SnapshotQuota1~~).
-     *   - The limit on the number of snapshots that can be created concurrently has been reached. For more information, see [Limits](~~25412#SnapshotQuota1~~).
-     *   - When you query the information of an ECS instance, if the returned data contains `{"OperationLocks": {"LockReason" : "security"}}`, all operations on the instance are prohibited.
+     * Creates a snapshot for a disk.
+     *
+     * @remarks
+     * The local snapshot feature has been replaced by the snapshot instant access feature. Metric description is as follows:
+     * - If you used local snapshots before December 14, 2020, you can use the `Category` parameter as Normal.
+     * - If you did not use local snapshots before December 14, 2020, no additional configuration is required. New snapshots created for ESSD series disks (ESSD, ESSD AutoPL, ESSD Entry, and regional ESSD) are instantly active by default, and both manual snapshots and automatic snapshots are supported. The three snapshot instant access-related parameters `InstantAccess`, `InstantAccessRetentionDays`, and `DisableInstantAccess` in API operations no longer take effect. The `DescribeSnapshots` and `DescribeSnapshotGroups` API operations will include a new response parameter named Available to describe the active status of snapshots.
+     * Before you begin:
+     * - Activate the snapshot feature. For more information, see [Activate snapshots](https://help.aliyun.com/document_detail/108381.html).
+     * - The disk must be in the **In Use** or **Unattached** state. Note the following items for different states:
+     *   - If the disk is in the **In Use** state, the instance must be in the **Running** or **Stopped** state.
+     *   - If the disk is in the **Unattached** state, the disk must have been previously attached to an ECS instance. Snapshots cannot be created for disks that have never been attached to an ECS instance.
+     *   - When a disk is used to create a dynamic extended volume or a RAID array, use a snapshot-consistent group and enable application-consistent snapshots to back up data. Snapshot-consistent groups ensure write order consistency and crash consistency for data written to multiple disks in a business system. For more information, see [Create a snapshot-consistent group](https://help.aliyun.com/document_detail/199625.html) and [Create an application-consistent snapshot](https://help.aliyun.com/document_detail/208589.html).
+     * When you create a snapshot, take note of the following items:
+     * - Avoid creating snapshots during peak business hours. When a snapshot is being created, the I/O performance of the disk decreases by up to 10%, and read and write performance may be briefly affected.
+     * - If the snapshot has not been created, it cannot be used to create a custom image ([CreateImage](https://help.aliyun.com/document_detail/25535.html)).
+     * - Incremental data generated by disk operations during snapshot creation is not backup to the snapshot.
+     * - If the disk is attached to an ECS instance, do not change the instance status during snapshot creation, such as stopping or restarting the ECS instance. Otherwise, the snapshot creation is failed.
+     * - A disk for which a snapshot is being created does not support scale-out. Wait until the snapshot is created before you execute the scale-out operation.
+     * - You can create snapshots for disks in the **Expired** (`Expired`) state. If the disk reaches its expiration release time during snapshot creation, the disk is released and the snapshot in the **Creating** (`Creating`) state is also deleted.
+     * - After a snapshot is created, the system calculates fees based on the snapshot size in each region separately. For more information, see [Snapshot billing](https://help.aliyun.com/document_detail/56159.html).
+     * - In the following scenarios, you cannot create a snapshot for the specified disk:
+     *   - The number of manual snapshots retained for the disk has reached the upper limit. For more information, see [Snapshot limits](~~25412#SnapshotQuota1~~).
+     *   - Snapshot creation has concurrency limits. Exceeding the limits causes creation failures. For more information, see [Snapshot limits](~~25412#SnapshotQuota1~~).
+     *   - When you query ECS instance information, if the returned data contains `{"OperationLocks": {"LockReason" : "security"}}`, all operations are prohibited.
      *
      * @param request - CreateSnapshotRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -1955,50 +1959,50 @@ export default class Client extends OpenApi {
      */
     createSnapshotWithOptions(request: $_model.CreateSnapshotRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateSnapshotResponse>;
     /**
-     * Create a snapshot of a cloud disk.
-     *
-     * @remarks
-     * The instant access feature for snapshots replaces the legacy local snapshot feature. The parameters are described as follows:
-     * - If you used local snapshots before December 14, 2020, you can continue to use the `Category` parameter.
-     * - If you did not use local snapshots before December 14, 2020, no additional configuration is required. New snapshots that are created for ESSD cloud disks (ESSDs, ESSD AutoPL disks, ESSD Entry disks, and zone-redundant ESSDs) have the instant access feature enabled by default. This applies to both manual and automatic snapshots. The instant access-related parameters `InstantAccess`, `InstantAccessRetentionDays`, and `DisableInstantAccess` no longer take effect. The `DescribeSnapshots` and `DescribeSnapshotGroups` API operations return an `Available` parameter that indicates the snapshot\\"s status.
-     * Prerequisites:
-     * - The snapshot feature is enabled. For more information, see [Enable the snapshot feature](https://help.aliyun.com/document_detail/108381.html).
-     * - The cloud disk must be in the **in-use** or **available** state. Note the following points:
-     *   - If the cloud disk is in the **in-use** state, the instance to which the disk is attached must be in the **running** or **stopped** state.
-     *   - If the cloud disk is in the **available** state, you can create snapshots for it only if it has been previously attached to an ECS instance.
-     *   - When you use cloud disks to create dynamic scalable volumes or RAID arrays, we recommend that you use snapshot consistency groups and enable application-consistent snapshots to back up data. A snapshot consistency group ensures the crash consistency and write-order consistency of data written across multiple cloud disks. For more information, see [Create a snapshot consistency group](https://help.aliyun.com/document_detail/199625.html) and [Create an application-consistent snapshot](https://help.aliyun.com/document_detail/208589.html).
-     * Keep the following in mind when creating a snapshot:
-     * - Create snapshots during off-peak hours. During snapshot creation, the I/O performance of the cloud disk decreases by less than 10% and read and write operations may temporarily slow down.
-     * - You cannot use a snapshot that is being created to create a custom image ([CreateImage](https://help.aliyun.com/document_detail/25535.html)).
-     * - The snapshot does not back up incremental data generated on the cloud disk during the creation process.
-     * - If the cloud disk is attached to an ECS instance, do not change the state of the instance, such as stopping or restarting the instance, during snapshot creation. Otherwise, the snapshot creation will fail.
-     * - You cannot resize a cloud disk during snapshot creation. You can resize the cloud disk only after the snapshot is complete.
-     * - You can create a snapshot for a cloud disk that is in the **expired** (`Expired`) state. If the cloud disk is released due to expiration when the snapshot is being created, the snapshot in the **creating** (`Creating`) state is also deleted.
-     * - After a snapshot is created, you are charged for the snapshot based on its size. The fees are settled on a per-region basis. For more information, see [Snapshots](https://help.aliyun.com/document_detail/56159.html).
-     * - You cannot create a snapshot for a cloud disk in the following cases:
-     *   - The number of manual snapshots of the cloud disk has reached the upper limit. For more information, see [Limits](~~25412#SnapshotQuota1~~).
-     *   - The limit on the number of snapshots that can be created concurrently has been reached. For more information, see [Limits](~~25412#SnapshotQuota1~~).
-     *   - When you query the information of an ECS instance, if the returned data contains `{"OperationLocks": {"LockReason" : "security"}}`, all operations on the instance are prohibited.
+     * Creates a snapshot for a disk.
+     *
+     * @remarks
+     * The local snapshot feature has been replaced by the snapshot instant access feature. Metric description is as follows:
+     * - If you used local snapshots before December 14, 2020, you can use the `Category` parameter as Normal.
+     * - If you did not use local snapshots before December 14, 2020, no additional configuration is required. New snapshots created for ESSD series disks (ESSD, ESSD AutoPL, ESSD Entry, and regional ESSD) are instantly active by default, and both manual snapshots and automatic snapshots are supported. The three snapshot instant access-related parameters `InstantAccess`, `InstantAccessRetentionDays`, and `DisableInstantAccess` in API operations no longer take effect. The `DescribeSnapshots` and `DescribeSnapshotGroups` API operations will include a new response parameter named Available to describe the active status of snapshots.
+     * Before you begin:
+     * - Activate the snapshot feature. For more information, see [Activate snapshots](https://help.aliyun.com/document_detail/108381.html).
+     * - The disk must be in the **In Use** or **Unattached** state. Note the following items for different states:
+     *   - If the disk is in the **In Use** state, the instance must be in the **Running** or **Stopped** state.
+     *   - If the disk is in the **Unattached** state, the disk must have been previously attached to an ECS instance. Snapshots cannot be created for disks that have never been attached to an ECS instance.
+     *   - When a disk is used to create a dynamic extended volume or a RAID array, use a snapshot-consistent group and enable application-consistent snapshots to back up data. Snapshot-consistent groups ensure write order consistency and crash consistency for data written to multiple disks in a business system. For more information, see [Create a snapshot-consistent group](https://help.aliyun.com/document_detail/199625.html) and [Create an application-consistent snapshot](https://help.aliyun.com/document_detail/208589.html).
+     * When you create a snapshot, take note of the following items:
+     * - Avoid creating snapshots during peak business hours. When a snapshot is being created, the I/O performance of the disk decreases by up to 10%, and read and write performance may be briefly affected.
+     * - If the snapshot has not been created, it cannot be used to create a custom image ([CreateImage](https://help.aliyun.com/document_detail/25535.html)).
+     * - Incremental data generated by disk operations during snapshot creation is not backup to the snapshot.
+     * - If the disk is attached to an ECS instance, do not change the instance status during snapshot creation, such as stopping or restarting the ECS instance. Otherwise, the snapshot creation is failed.
+     * - A disk for which a snapshot is being created does not support scale-out. Wait until the snapshot is created before you execute the scale-out operation.
+     * - You can create snapshots for disks in the **Expired** (`Expired`) state. If the disk reaches its expiration release time during snapshot creation, the disk is released and the snapshot in the **Creating** (`Creating`) state is also deleted.
+     * - After a snapshot is created, the system calculates fees based on the snapshot size in each region separately. For more information, see [Snapshot billing](https://help.aliyun.com/document_detail/56159.html).
+     * - In the following scenarios, you cannot create a snapshot for the specified disk:
+     *   - The number of manual snapshots retained for the disk has reached the upper limit. For more information, see [Snapshot limits](~~25412#SnapshotQuota1~~).
+     *   - Snapshot creation has concurrency limits. Exceeding the limits causes creation failures. For more information, see [Snapshot limits](~~25412#SnapshotQuota1~~).
+     *   - When you query ECS instance information, if the returned data contains `{"OperationLocks": {"LockReason" : "security"}}`, all operations are prohibited.
      *
      * @param request - CreateSnapshotRequest
      * @returns CreateSnapshotResponse
      */
     createSnapshot(request: $_model.CreateSnapshotRequest): Promise<$_model.CreateSnapshotResponse>;
     /**
-     * Creates a snapshot-consistent group for the disks of an Elastic Compute Service (ECS) instance. A snapshot-consistent group contains snapshots of one or more disks.
+     * Creates a snapshot-consistent group for disks attached to a specified ECS instance. A snapshot-consistent group contains snapshots of one or more disks.
      *
      * @remarks
-     * 您可以设置`InstanceId`为实例内的指定云盘创建快照一致性组；也可以只使用`DiskId.N`为同可用区内多台 ECS 实例挂载的多块云盘创建快照一致性组。
-     * > `DiskId.N`不可与`ExcludeDiskId.N`同时设置。此外，如果设置了`InstanceId`，则`DiskId.N`只能设置指定实例内已挂载的云盘，不再支持设置多个跨实例的云盘 ID。
-     * 创建快照一致性组时，请注意：
-     * - 待创建快照的云盘必须处于**使用中**（`In_use`）或**待挂载**（`Available`）的状态。
-     *   - 如果云盘处于**使用中**（`In_use`）的状态，则 ECS 实例状态为**运行中**（`Running`）或者**已停止**（`Stopped`）。
-     *   - 如果云盘处于**待挂载**（`Available`）的状态，则需要保证云盘有过挂载到 ECS 实例的历史操作。从未挂载过 ECS 实例的云盘不支持创建快照。
-     * - 目前快照一致性组只支持 ESSD 系列云盘（ESSD、ESSD AutoPL、ESSD Entry）。
-     * - 单个快照一致性组最多包括 16 块云盘（包括系统盘和数据盘），且总容量不超过 32 TiB。
-     * - 您自行创建的快照会一直保留，请定期删除不再需要的快照，避免快照容量持续扣费。
-     * - 开启多重挂载特性的云盘不支持创建快照一致性组。如果实例挂载了开启多重挂载特性的云盘，您需要设置`ExcludeDiskId.N`参数排除该云盘。
-     * 关于快照一致性组的功能、计费等信息，请参见[快照一致性组](https://help.aliyun.com/document_detail/199625.html)。
+     * You can set `InstanceId` to create a snapshot-consistent group for specified disks within an instance. Alternatively, you can use only `DiskId.N` to create a snapshot-consistent group for multiple disks attached to multiple ECS instances in the same zone.
+     * > `DiskId.N` and `ExcludeDiskId.N` cannot be specified at the same time. If `InstanceId` is specified, `DiskId.N` can only be set to disks attached to the specified instance and no longer supports specifying disk IDs across multiple instances.
+     * When you create a snapshot-consistent group, take note of the following items:
+     * - The disks for which you want to create snapshots must be in the **In Use** (`In_use`) or **Available** (`Available`) state.
+     *     - If a disk is in the **In Use** (`In_use`) state, the ECS instance status must be **Running** (`Running`) or **Stopped** (`Stopped`).
+     *     - If a disk is in the **Available** (`Available`) state, the disk must have been previously attached to an ECS instance. Disks that have never been attached to an ECS instance do not support snapshot creation.
+     * - Snapshot-consistent groups support only ESSD series disks (ESSD, ESSD AutoPL, and ESSD Entry).
+     * - A single snapshot-consistent group can contain up to 16 disks (including system disks and data disks), and the total capacity cannot exceed 32 TiB.
+     * - Snapshots that you manually create are retained until you delete them. Delete unnecessary snapshots on a regular basis to avoid incurring ongoing snapshot size fees.
+     * - Disks with the multi-attach attribute enabled do not support snapshot-consistent groups. If an instance has a multi-attach disk attached, set the `ExcludeDiskId.N` parameter to exclude the disk.
+     * For more information about the features and billing of snapshot-consistent groups, see [Snapshot-consistent groups](https://help.aliyun.com/document_detail/199625.html).
      *
      * @param request - CreateSnapshotGroupRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -2006,20 +2010,20 @@ export default class Client extends OpenApi {
      */
     createSnapshotGroupWithOptions(request: $_model.CreateSnapshotGroupRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateSnapshotGroupResponse>;
     /**
-     * Creates a snapshot-consistent group for the disks of an Elastic Compute Service (ECS) instance. A snapshot-consistent group contains snapshots of one or more disks.
+     * Creates a snapshot-consistent group for disks attached to a specified ECS instance. A snapshot-consistent group contains snapshots of one or more disks.
      *
      * @remarks
-     * 您可以设置`InstanceId`为实例内的指定云盘创建快照一致性组；也可以只使用`DiskId.N`为同可用区内多台 ECS 实例挂载的多块云盘创建快照一致性组。
-     * > `DiskId.N`不可与`ExcludeDiskId.N`同时设置。此外，如果设置了`InstanceId`，则`DiskId.N`只能设置指定实例内已挂载的云盘，不再支持设置多个跨实例的云盘 ID。
-     * 创建快照一致性组时，请注意：
-     * - 待创建快照的云盘必须处于**使用中**（`In_use`）或**待挂载**（`Available`）的状态。
-     *   - 如果云盘处于**使用中**（`In_use`）的状态，则 ECS 实例状态为**运行中**（`Running`）或者**已停止**（`Stopped`）。
-     *   - 如果云盘处于**待挂载**（`Available`）的状态，则需要保证云盘有过挂载到 ECS 实例的历史操作。从未挂载过 ECS 实例的云盘不支持创建快照。
-     * - 目前快照一致性组只支持 ESSD 系列云盘（ESSD、ESSD AutoPL、ESSD Entry）。
-     * - 单个快照一致性组最多包括 16 块云盘（包括系统盘和数据盘），且总容量不超过 32 TiB。
-     * - 您自行创建的快照会一直保留，请定期删除不再需要的快照，避免快照容量持续扣费。
-     * - 开启多重挂载特性的云盘不支持创建快照一致性组。如果实例挂载了开启多重挂载特性的云盘，您需要设置`ExcludeDiskId.N`参数排除该云盘。
-     * 关于快照一致性组的功能、计费等信息，请参见[快照一致性组](https://help.aliyun.com/document_detail/199625.html)。
+     * You can set `InstanceId` to create a snapshot-consistent group for specified disks within an instance. Alternatively, you can use only `DiskId.N` to create a snapshot-consistent group for multiple disks attached to multiple ECS instances in the same zone.
+     * > `DiskId.N` and `ExcludeDiskId.N` cannot be specified at the same time. If `InstanceId` is specified, `DiskId.N` can only be set to disks attached to the specified instance and no longer supports specifying disk IDs across multiple instances.
+     * When you create a snapshot-consistent group, take note of the following items:
+     * - The disks for which you want to create snapshots must be in the **In Use** (`In_use`) or **Available** (`Available`) state.
+     *     - If a disk is in the **In Use** (`In_use`) state, the ECS instance status must be **Running** (`Running`) or **Stopped** (`Stopped`).
+     *     - If a disk is in the **Available** (`Available`) state, the disk must have been previously attached to an ECS instance. Disks that have never been attached to an ECS instance do not support snapshot creation.
+     * - Snapshot-consistent groups support only ESSD series disks (ESSD, ESSD AutoPL, and ESSD Entry).
+     * - A single snapshot-consistent group can contain up to 16 disks (including system disks and data disks), and the total capacity cannot exceed 32 TiB.
+     * - Snapshots that you manually create are retained until you delete them. Delete unnecessary snapshots on a regular basis to avoid incurring ongoing snapshot size fees.
+     * - Disks with the multi-attach attribute enabled do not support snapshot-consistent groups. If an instance has a multi-attach disk attached, set the `ExcludeDiskId.N` parameter to exclude the disk.
+     * For more information about the features and billing of snapshot-consistent groups, see [Snapshot-consistent groups](https://help.aliyun.com/document_detail/199625.html).
      *
      * @param request - CreateSnapshotGroupRequest
      * @returns CreateSnapshotGroupResponse
@@ -2295,13 +2299,13 @@ export default class Client extends OpenApi {
      */
     deleteDiagnosticReports(request: $_model.DeleteDiagnosticReportsRequest): Promise<$_model.DeleteDiagnosticReportsResponse>;
     /**
-     * Releases a pay-as-you-go data disk. Supported disk types include basic disks, ultra disks, standard SSDs, and enterprise SSDs (ESSDs).
+     * Releases a pay-as-you-go data disk. Disk types include basic disks, ultra disks, standard SSDs, and enterprise SSDs.
      *
      * @remarks
      * When you invoke this operation, take note of the following items:
      * - Manual snapshots of the disk are retained.
-     * - You can invoke [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to specify whether to retain or release automatic snapshots along with the disk. Delete unnecessary snapshots promptly to maintain sufficient snapshot quota for epoch-based automatic snapshot policy execution.
-     * - The disk must be in the **Unattached** (Available) state when you release it.
+     * - You can invoke [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to configure the Settings for whether to retain or release automatic snapshots together with the disk. Delete unnecessary snapshots promptly to maintain sufficient snapshot quota for epoch-based automatic snapshot policy.
+     * - The disk must be in the Pending Attach (Available) state when you release it.
      * - If the disk with the specified ID does not exist, the request is ignored.
      *
      * @param request - DeleteDiskRequest
@@ -2310,13 +2314,13 @@ export default class Client extends OpenApi {
      */
     deleteDiskWithOptions(request: $_model.DeleteDiskRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteDiskResponse>;
     /**
-     * Releases a pay-as-you-go data disk. Supported disk types include basic disks, ultra disks, standard SSDs, and enterprise SSDs (ESSDs).
+     * Releases a pay-as-you-go data disk. Disk types include basic disks, ultra disks, standard SSDs, and enterprise SSDs.
      *
      * @remarks
      * When you invoke this operation, take note of the following items:
      * - Manual snapshots of the disk are retained.
-     * - You can invoke [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to specify whether to retain or release automatic snapshots along with the disk. Delete unnecessary snapshots promptly to maintain sufficient snapshot quota for epoch-based automatic snapshot policy execution.
-     * - The disk must be in the **Unattached** (Available) state when you release it.
+     * - You can invoke [ModifyDiskAttribute](https://help.aliyun.com/document_detail/25517.html) to configure the Settings for whether to retain or release automatic snapshots together with the disk. Delete unnecessary snapshots promptly to maintain sufficient snapshot quota for epoch-based automatic snapshot policy.
+     * - The disk must be in the Pending Attach (Available) state when you release it.
      * - If the disk with the specified ID does not exist, the request is ignored.
      *
      * @param request - DeleteDiskRequest
@@ -2809,13 +2813,13 @@ export default class Client extends OpenApi {
      */
     deleteSecurityGroup(request: $_model.DeleteSecurityGroupRequest): Promise<$_model.DeleteSecurityGroupResponse>;
     /**
-     * Deletes a specified snapshot. If you call this operation to delete a snapshot that is being created, the associated snapshot creation task is also canceled.
+     * Deletes a specified snapshot. You can also call this operation to cancel a snapshot that is being created.
      *
      * @remarks
-     * Take note of the following items:
-     * - If the snapshot does not exist, the request is ignored.
-     * - If the snapshot has been used to create custom images, the snapshot cannot be deleted. You need to call the [DeleteImage](https://help.aliyun.com/document_detail/25537.html) operation to delete the custom images before you can delete the snapshot.
-     * - If the snapshot has been used to create disks and `Force` is not specified or is set to `false`, the snapshot cannot be deleted directly. If you want to delete the snapshot, set `Force` to true to forcibly delete the snapshot. The disks created from the snapshot cannot be re-initialized after the snapshot is forcibly deleted.
+     * When you invoke this operation, note the following items:
+     * - If the specified snapshot ID does not exist, the request is ignored.
+     * - If the snapshot has been used to create a custom image, the snapshot cannot be deleted. You must first delete the custom image ([DeleteImage](https://help.aliyun.com/document_detail/25537.html)) before you can delete the snapshot.
+     * - If the snapshot has been used to create a cloud disk and the `Force` parameter is not set or is set to `Force=false`, the snapshot cannot be directly deleted. To delete the snapshot, set `Force=true` to force delete it. After the snapshot is force deleted, the corresponding cloud disk cannot be reinitialized.
      *
      * @param request - DeleteSnapshotRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -2823,23 +2827,23 @@ export default class Client extends OpenApi {
      */
     deleteSnapshotWithOptions(request: $_model.DeleteSnapshotRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteSnapshotResponse>;
     /**
-     * Deletes a specified snapshot. If you call this operation to delete a snapshot that is being created, the associated snapshot creation task is also canceled.
+     * Deletes a specified snapshot. You can also call this operation to cancel a snapshot that is being created.
      *
      * @remarks
-     * Take note of the following items:
-     * - If the snapshot does not exist, the request is ignored.
-     * - If the snapshot has been used to create custom images, the snapshot cannot be deleted. You need to call the [DeleteImage](https://help.aliyun.com/document_detail/25537.html) operation to delete the custom images before you can delete the snapshot.
-     * - If the snapshot has been used to create disks and `Force` is not specified or is set to `false`, the snapshot cannot be deleted directly. If you want to delete the snapshot, set `Force` to true to forcibly delete the snapshot. The disks created from the snapshot cannot be re-initialized after the snapshot is forcibly deleted.
+     * When you invoke this operation, note the following items:
+     * - If the specified snapshot ID does not exist, the request is ignored.
+     * - If the snapshot has been used to create a custom image, the snapshot cannot be deleted. You must first delete the custom image ([DeleteImage](https://help.aliyun.com/document_detail/25537.html)) before you can delete the snapshot.
+     * - If the snapshot has been used to create a cloud disk and the `Force` parameter is not set or is set to `Force=false`, the snapshot cannot be directly deleted. To delete the snapshot, set `Force=true` to force delete it. After the snapshot is force deleted, the corresponding cloud disk cannot be reinitialized.
      *
      * @param request - DeleteSnapshotRequest
      * @returns DeleteSnapshotResponse
      */
     deleteSnapshot(request: $_model.DeleteSnapshotRequest): Promise<$_model.DeleteSnapshotResponse>;
     /**
-     * Deletes snapshot-consistent groups.
+     * Deletes a snapshot-consistent group.
      *
      * @remarks
-     * If a disk snapshot that is contained in a snapshot-consistent group has been used to create a custom image, the disk snapshot is retained after the snapshot-consistent group is deleted. Before you can delete the disk snapshot, you must call the [DeleteImage](https://help.aliyun.com/document_detail/25537.html) operation to delete the custom image. Then, you can call the [DeleteSnapshot](https://help.aliyun.com/document_detail/25525.html) operation to delete the disk snapshot.
+     * If disk snapshots in a snapshot-consistent group have been used to create custom images, the related disk snapshots are not deleted when the snapshot-consistent group is deleted. To delete the related disk snapshots, first delete the custom images ([DeleteImage](https://help.aliyun.com/document_detail/25537.html)), and then delete the related disk snapshots ([DeleteSnapshot](https://help.aliyun.com/document_detail/25525.html)).
      *
      * @param request - DeleteSnapshotGroupRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -2847,10 +2851,10 @@ export default class Client extends OpenApi {
      */
     deleteSnapshotGroupWithOptions(request: $_model.DeleteSnapshotGroupRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteSnapshotGroupResponse>;
     /**
-     * Deletes snapshot-consistent groups.
+     * Deletes a snapshot-consistent group.
      *
      * @remarks
-     * If a disk snapshot that is contained in a snapshot-consistent group has been used to create a custom image, the disk snapshot is retained after the snapshot-consistent group is deleted. Before you can delete the disk snapshot, you must call the [DeleteImage](https://help.aliyun.com/document_detail/25537.html) operation to delete the custom image. Then, you can call the [DeleteSnapshot](https://help.aliyun.com/document_detail/25525.html) operation to delete the disk snapshot.
+     * If disk snapshots in a snapshot-consistent group have been used to create custom images, the related disk snapshots are not deleted when the snapshot-consistent group is deleted. To delete the related disk snapshots, first delete the custom images ([DeleteImage](https://help.aliyun.com/document_detail/25537.html)), and then delete the related disk snapshots ([DeleteSnapshot](https://help.aliyun.com/document_detail/25525.html)).
      *
      * @param request - DeleteSnapshotGroupRequest
      * @returns DeleteSnapshotGroupResponse
@@ -3575,7 +3579,7 @@ export default class Client extends OpenApi {
      */
     describeDiagnosticReports(request: $_model.DescribeDiagnosticReportsRequest): Promise<$_model.DescribeDiagnosticReportsResponse>;
     /**
-     * Queries the Key Management Service (KMS) key used by the Account-level Elastic Block Storage (EBS) Default Encryption feature in a region.
+     * Queries the key used for account-level default encryption of block storage.
      *
      * @param request - DescribeDiskDefaultKMSKeyIdRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -3583,14 +3587,14 @@ export default class Client extends OpenApi {
      */
     describeDiskDefaultKMSKeyIdWithOptions(request: $_model.DescribeDiskDefaultKMSKeyIdRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeDiskDefaultKMSKeyIdResponse>;
     /**
-     * Queries the Key Management Service (KMS) key used by the Account-level Elastic Block Storage (EBS) Default Encryption feature in a region.
+     * Queries the key used for account-level default encryption of block storage.
      *
      * @param request - DescribeDiskDefaultKMSKeyIdRequest
      * @returns DescribeDiskDefaultKMSKeyIdResponse
      */
     describeDiskDefaultKMSKeyId(request: $_model.DescribeDiskDefaultKMSKeyIdRequest): Promise<$_model.DescribeDiskDefaultKMSKeyIdResponse>;
     /**
-     * Queries whether account-level default encryption of Elastic Block Storage (EBS) resources is enabled in a region.
+     * Queries the service status of account-level default encryption for block storage in a specified region.
      *
      * @param request - DescribeDiskEncryptionByDefaultStatusRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -3598,7 +3602,7 @@ export default class Client extends OpenApi {
      */
     describeDiskEncryptionByDefaultStatusWithOptions(request: $_model.DescribeDiskEncryptionByDefaultStatusRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeDiskEncryptionByDefaultStatusResponse>;
     /**
-     * Queries whether account-level default encryption of Elastic Block Storage (EBS) resources is enabled in a region.
+     * Queries the service status of account-level default encryption for block storage in a specified region.
      *
      * @param request - DescribeDiskEncryptionByDefaultStatusRequest
      * @returns DescribeDiskEncryptionByDefaultStatusResponse
@@ -3995,13 +3999,13 @@ export default class Client extends OpenApi {
      */
     describeImageSupportInstanceTypes(request: $_model.DescribeImageSupportInstanceTypesRequest): Promise<$_model.DescribeImageSupportInstanceTypesResponse>;
     /**
-     * Specify parameters such as ImageId, image usage scenario, and Filter to query the list of image resources you can use.
+     * Queries the list of image resources that you can use by specifying parameters such as ImageId, image usage scenarios, and Filter conditions.
      *
      * @remarks
-     * - The image resources you can query include your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images actively shared with you by other Alibaba Cloud users.
-     * - Paged query is supported. The query results include the total number of usable image resources and the image resources on the current page. The default number of entries per page is 10.
-     * - When invoking the API through the Alibaba Cloud command-line interface (CLI), the values of request parameters of different data types must comply with format requirements. For more information, see [CLI Parameter Format Description](https://help.aliyun.com/document_detail/110340.html).
-     * - When querying official Alibaba Cloud images or shared images (where ImageOwnerAlias is set to system or others), RAM authentication rules are ignored for this request. For more information, see [Authentication Rules](https://help.aliyun.com/document_detail/25497.html).
+     * - Image resources that you can query include your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images that other Alibaba Cloud users have shared with you.
+     * - Paging is supported. The query results include the total number of available image resources and the image resources on the current page. The default number of entries per page is 10.
+     * - When you invoke an API operation by using Cloud Assistant CLI, request parameters of different data types must comply with format requirements. For more information, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
+     * - When you query images provided by Alibaba Cloud or shared images (ImageOwnerAlias is set to system or others), the request can bypass RAM authentication rules. For more information, see [Authentication rules](https://help.aliyun.com/document_detail/25497.html).
      *
      * @param request - DescribeImagesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -4009,13 +4013,13 @@ export default class Client extends OpenApi {
      */
     describeImagesWithOptions(request: $_model.DescribeImagesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeImagesResponse>;
     /**
-     * Specify parameters such as ImageId, image usage scenario, and Filter to query the list of image resources you can use.
+     * Queries the list of image resources that you can use by specifying parameters such as ImageId, image usage scenarios, and Filter conditions.
      *
      * @remarks
-     * - The image resources you can query include your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images actively shared with you by other Alibaba Cloud users.
-     * - Paged query is supported. The query results include the total number of usable image resources and the image resources on the current page. The default number of entries per page is 10.
-     * - When invoking the API through the Alibaba Cloud command-line interface (CLI), the values of request parameters of different data types must comply with format requirements. For more information, see [CLI Parameter Format Description](https://help.aliyun.com/document_detail/110340.html).
-     * - When querying official Alibaba Cloud images or shared images (where ImageOwnerAlias is set to system or others), RAM authentication rules are ignored for this request. For more information, see [Authentication Rules](https://help.aliyun.com/document_detail/25497.html).
+     * - Image resources that you can query include your custom images, public images provided by Alibaba Cloud, Alibaba Cloud Marketplace images, and shared images that other Alibaba Cloud users have shared with you.
+     * - Paging is supported. The query results include the total number of available image resources and the image resources on the current page. The default number of entries per page is 10.
+     * - When you invoke an API operation by using Cloud Assistant CLI, request parameters of different data types must comply with format requirements. For more information, see [CLI parameter format](https://help.aliyun.com/document_detail/110340.html).
+     * - When you query images provided by Alibaba Cloud or shared images (ImageOwnerAlias is set to system or others), the request can bypass RAM authentication rules. For more information, see [Authentication rules](https://help.aliyun.com/document_detail/25497.html).
      *
      * @param request - DescribeImagesRequest
      * @returns DescribeImagesResponse
@@ -4895,7 +4899,7 @@ export default class Client extends OpenApi {
      */
     describePrice(request: $_model.DescribePriceRequest): Promise<$_model.DescribePriceResponse>;
     /**
-     * （Beta）调用 DescribeRecommendInstanceType 根据一个指定的实例规格，查找一个或多个备选的实例规格。针对已经或者即将停售的实例规格，DescribeRecommendInstanceType会罗列出作为替补的所有实例规格。
+     * (Beta) Queries one or more alternative instance types based on a specified instance type. For instance types that have been or will be retired, DescribeRecommendInstanceType lists all instance types that can serve as replacements.
      *
      * @param request - DescribeRecommendInstanceTypeRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -4903,7 +4907,7 @@ export default class Client extends OpenApi {
      */
     describeRecommendInstanceTypeWithOptions(request: $_model.DescribeRecommendInstanceTypeRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeRecommendInstanceTypeResponse>;
     /**
-     * （Beta）调用 DescribeRecommendInstanceType 根据一个指定的实例规格，查找一个或多个备选的实例规格。针对已经或者即将停售的实例规格，DescribeRecommendInstanceType会罗列出作为替补的所有实例规格。
+     * (Beta) Queries one or more alternative instance types based on a specified instance type. For instance types that have been or will be retired, DescribeRecommendInstanceType lists all instance types that can serve as replacements.
      *
      * @param request - DescribeRecommendInstanceTypeRequest
      * @returns DescribeRecommendInstanceTypeResponse
@@ -5269,13 +5273,13 @@ export default class Client extends OpenApi {
      */
     describeSecurityGroups(request: $_model.DescribeSecurityGroupsRequest): Promise<$_model.DescribeSecurityGroupsResponse>;
     /**
-     * Queries the list and status of files sent by Cloud Assistant by calling DescribeSendFileResults.
+     * Queries the list and status of files sent by Cloud Assistant.
      *
      * @remarks
      * ## Operation description:
-     * - After you send a file, the file is not necessarily sent. You must check the actual sending result based on the return value of this operation.
-     * - You can query execution information from the last 30 days. A maximum of 10,000 entries of execution information can be retained.
-     * - When paged query the first page, set only MaxResults to limit the number of entries to return. The NextToken value returned in the result serves as the token for querying subsequent pages. When paged query subsequent pages, set NextToken to the value obtained from the previous response and set MaxResults to limit the number of entries to return.
+     * - After you send a file, the file is not necessarily sent successfully. You must check the actual delivery result based on the return value of this operation. The actual output prevails.
+     * - You can query execution information from the last day. A maximum of 1,000 entries of execution information can be retained.
+     * - When you execute a paging query for the first page, set only `MaxResults` to limit the number of entries returned. The `NextToken` value in the response serves as the token for querying subsequent pages. When querying subsequent pages, set the `NextToken` parameter to the value obtained from the previous response and set `MaxResults` to limit the number of entries returned.
      *
      * @param request - DescribeSendFileResultsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -5283,23 +5287,23 @@ export default class Client extends OpenApi {
      */
     describeSendFileResultsWithOptions(request: $_model.DescribeSendFileResultsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeSendFileResultsResponse>;
     /**
-     * Queries the list and status of files sent by Cloud Assistant by calling DescribeSendFileResults.
+     * Queries the list and status of files sent by Cloud Assistant.
      *
      * @remarks
      * ## Operation description:
-     * - After you send a file, the file is not necessarily sent. You must check the actual sending result based on the return value of this operation.
-     * - You can query execution information from the last 30 days. A maximum of 10,000 entries of execution information can be retained.
-     * - When paged query the first page, set only MaxResults to limit the number of entries to return. The NextToken value returned in the result serves as the token for querying subsequent pages. When paged query subsequent pages, set NextToken to the value obtained from the previous response and set MaxResults to limit the number of entries to return.
+     * - After you send a file, the file is not necessarily sent successfully. You must check the actual delivery result based on the return value of this operation. The actual output prevails.
+     * - You can query execution information from the last day. A maximum of 1,000 entries of execution information can be retained.
+     * - When you execute a paging query for the first page, set only `MaxResults` to limit the number of entries returned. The `NextToken` value in the response serves as the token for querying subsequent pages. When querying subsequent pages, set the `NextToken` parameter to the value obtained from the previous response and set `MaxResults` to limit the number of entries returned.
      *
      * @param request - DescribeSendFileResultsRequest
      * @returns DescribeSendFileResultsResponse
      */
     describeSendFileResults(request: $_model.DescribeSendFileResultsRequest): Promise<$_model.DescribeSendFileResultsResponse>;
     /**
-     * Queries the information of one or more snapshot-consistent groups, such as the status of the groups, IDs of the instances associated with the groups, and snapshot creation progress.
+     * Queries information about one or more snapshot-consistent groups, such as the status, associated instance ID, and snapshot creation progress.
      *
      * @remarks
-     * You can specify multiple request parameters to be queried, such as `InstanceId`, `SnapshotGroupId.N`, and `Status.N`. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
+     * `InstanceId`, `SnapshotGroupId.N`, and `Status.N` are not required request parameters, but they can be used to build filter logic. The parameters have a logical AND relationship.
      *
      * @param request - DescribeSnapshotGroupsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -5307,10 +5311,10 @@ export default class Client extends OpenApi {
      */
     describeSnapshotGroupsWithOptions(request: $_model.DescribeSnapshotGroupsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeSnapshotGroupsResponse>;
     /**
-     * Queries the information of one or more snapshot-consistent groups, such as the status of the groups, IDs of the instances associated with the groups, and snapshot creation progress.
+     * Queries information about one or more snapshot-consistent groups, such as the status, associated instance ID, and snapshot creation progress.
      *
      * @remarks
-     * You can specify multiple request parameters to be queried, such as `InstanceId`, `SnapshotGroupId.N`, and `Status.N`. Specified parameters have logical AND relations. Only the specified parameters are included in the filter conditions.
+     * `InstanceId`, `SnapshotGroupId.N`, and `Status.N` are not required request parameters, but they can be used to build filter logic. The parameters have a logical AND relationship.
      *
      * @param request - DescribeSnapshotGroupsRequest
      * @returns DescribeSnapshotGroupsResponse
@@ -5986,14 +5990,14 @@ export default class Client extends OpenApi {
      */
     disableActivation(request: $_model.DisableActivationRequest): Promise<$_model.DisableActivationResponse>;
     /**
-     * Disables account-level default encryption of Elastic Block Storage (EBS) resources in a region. After you disable account-level default encryption of EBS resources in a region, the encryption status of existing disks in the region does not change. When you create a disk, you can still choose to encrypt the disk.
+     * Disables the account-level default encryption for block storage in a specified region.
      *
      * @remarks
-     * - **Instructions**
-     *   - You must grant the RAM user the `AliyunECSFullAccess` permissions. For information about how to grant permissions to a RAM user, see [Grant permissions to a RAM user](https://help.aliyun.com/document_detail/116146.html).
-     * - **Considerations**
-     *   - After Account-level EBS Default Encryption is disabled, the encryption status of existing cloud disks is not affected.
-     *   - After Account-level EBS Default Encryption is disabled, you can still choose to encrypt new cloud disks when you purchase the disks.
+     * - **Before you begin**
+     *   - Resource Access Management (RAM) users require the `AliyunECSFullAccess` permission. For more information about how to perform authorization, see [Grant permissions to a RAM user](https://help.aliyun.com/document_detail/116146.html).
+     * - **Usage notes**
+     *   - After you shutdown account-level default encryption for block storage, the encryption status of existing cloud disks is not affected.
+     *   - After you shutdown account-level default encryption for block storage, you can still manually select encryption when you create cloud disks.
      *
      * @param request - DisableDiskEncryptionByDefaultRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -6001,14 +6005,14 @@ export default class Client extends OpenApi {
      */
     disableDiskEncryptionByDefaultWithOptions(request: $_model.DisableDiskEncryptionByDefaultRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DisableDiskEncryptionByDefaultResponse>;
     /**
-     * Disables account-level default encryption of Elastic Block Storage (EBS) resources in a region. After you disable account-level default encryption of EBS resources in a region, the encryption status of existing disks in the region does not change. When you create a disk, you can still choose to encrypt the disk.
+     * Disables the account-level default encryption for block storage in a specified region.
      *
      * @remarks
-     * - **Instructions**
-     *   - You must grant the RAM user the `AliyunECSFullAccess` permissions. For information about how to grant permissions to a RAM user, see [Grant permissions to a RAM user](https://help.aliyun.com/document_detail/116146.html).
-     * - **Considerations**
-     *   - After Account-level EBS Default Encryption is disabled, the encryption status of existing cloud disks is not affected.
-     *   - After Account-level EBS Default Encryption is disabled, you can still choose to encrypt new cloud disks when you purchase the disks.
+     * - **Before you begin**
+     *   - Resource Access Management (RAM) users require the `AliyunECSFullAccess` permission. For more information about how to perform authorization, see [Grant permissions to a RAM user](https://help.aliyun.com/document_detail/116146.html).
+     * - **Usage notes**
+     *   - After you shutdown account-level default encryption for block storage, the encryption status of existing cloud disks is not affected.
+     *   - After you shutdown account-level default encryption for block storage, you can still manually select encryption when you create cloud disks.
      *
      * @param request - DisableDiskEncryptionByDefaultRequest
      * @returns DisableDiskEncryptionByDefaultResponse