@alicloud/ecs20140526 7.2.3 → 7.3.0

package/dist/client.js

@@ -99,7 +99,7 @@ class Client extends openapi_core_1.default {
         return openapi_core_2.OpenApiUtil.getEndpointRules(productId, regionId, endpointRule, network, suffix);
     }
     /**
-     * Accepts the default operation for a system event in the Inquiring state and authorizes the system to perform the operation.
+     * dubbo
      *
      * @param request - AcceptInquiredSystemEventRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -149,7 +149,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.AcceptInquiredSystemEventResponse({}));
     }
     /**
-     * Accepts the default operation for a system event in the Inquiring state and authorizes the system to perform the operation.
+     * dubbo
      *
      * @param request - AcceptInquiredSystemEventRequest
      * @returns AcceptInquiredSystemEventResponse
@@ -640,8 +640,17 @@ class Client extends openapi_core_1.default {
      * Applies an automatic snapshot policy to one or more cloud disks. You can call this operation to replace the automatic snapshot policy of a cloud disk.
      *
      * @remarks
-     *   Each disk can have only one automatic snapshot policy.
-     * *   Each automatic snapshot policy can be applied to multiple disks.
+     * ## [](#)Usage notes
+     * When you call this operation, note that:
+     * *   You can apply only one automatic snapshot policy to each disk.
+     * *   You can apply a single automatic snapshot policy to multiple disks.
+     * Feature changes:
+     * By default, only one policy can be applied to a single disk. After the feature is upgraded, a maximum of 10 automatic snapshot policies can be applied to a single disk at the same time to meet the backup requirements of multiple scenarios.
+     * If you need to apply for a whitelist to upgrade the feature, [submit a ticket](https://smartservice.console.aliyun.com/service/create-ticket).
+     * After you upgrade the feature, take note of the following:
+     * *   Each cloud disk supports up to 10 automatic snapshot policies.
+     * *   If the target cloud disk already has an automatic snapshot policy applied, calling this operation will add to the existing policy rather than replace it.
+     * > To avoid unexpected fees, cancel the automatic snapshot policies that you no longer need.
      *
      * @param request - ApplyAutoSnapshotPolicyRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -688,8 +697,17 @@ class Client extends openapi_core_1.default {
      * Applies an automatic snapshot policy to one or more cloud disks. You can call this operation to replace the automatic snapshot policy of a cloud disk.
      *
      * @remarks
-     *   Each disk can have only one automatic snapshot policy.
-     * *   Each automatic snapshot policy can be applied to multiple disks.
+     * ## [](#)Usage notes
+     * When you call this operation, note that:
+     * *   You can apply only one automatic snapshot policy to each disk.
+     * *   You can apply a single automatic snapshot policy to multiple disks.
+     * Feature changes:
+     * By default, only one policy can be applied to a single disk. After the feature is upgraded, a maximum of 10 automatic snapshot policies can be applied to a single disk at the same time to meet the backup requirements of multiple scenarios.
+     * If you need to apply for a whitelist to upgrade the feature, [submit a ticket](https://smartservice.console.aliyun.com/service/create-ticket).
+     * After you upgrade the feature, take note of the following:
+     * *   Each cloud disk supports up to 10 automatic snapshot policies.
+     * *   If the target cloud disk already has an automatic snapshot policy applied, calling this operation will add to the existing policy rather than replace it.
+     * > To avoid unexpected fees, cancel the automatic snapshot policies that you no longer need.
      *
      * @param request - ApplyAutoSnapshotPolicyRequest
      * @returns ApplyAutoSnapshotPolicyResponse
@@ -8928,7 +8946,7 @@ class Client extends openapi_core_1.default {
         return await this.describeAccessPointsWithOptions(request, runtime);
     }
     /**
-     * Queries the quotas of Elastic Compute Service (ECS) resources that you can create in an Alibaba Cloud region. For a specific region, you can query the maximum numbers of security groups, elastic network interfaces (ENIs), vCPUs for pay-as-you-go instances, vCPUs for spot instances, and dedicated hosts that you can create and the capacity quotas for pay-as-you-go disks that you can create. You can also query information such as network types or whether an account has completed real-name verification.
+     * Queries the quotas of Elastic Compute Service (ECS) resources that you can create in an Alibaba Cloud region. For a specific region, you can query the maximum numbers of security groups, elastic network interfaces (ENIs), vCPUs for pay-as-you-go instances, vCPUs for spot instances, and dedicated hosts that you can create and the capacity quotas for pay-as-you-go disks that you can create. You can also query information such as network types or whether an account has completed the account verification.
      *
      * @remarks
      * After you [create](https://account.alibabacloud.com/register/intl_register.htm) an Alibaba Cloud account, you can create a specific number of ECS instances in different regions within the account. For more information, see [Limits](https://help.aliyun.com/document_detail/25412.html).
@@ -8976,7 +8994,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeAccountAttributesResponse({}));
     }
     /**
-     * Queries the quotas of Elastic Compute Service (ECS) resources that you can create in an Alibaba Cloud region. For a specific region, you can query the maximum numbers of security groups, elastic network interfaces (ENIs), vCPUs for pay-as-you-go instances, vCPUs for spot instances, and dedicated hosts that you can create and the capacity quotas for pay-as-you-go disks that you can create. You can also query information such as network types or whether an account has completed real-name verification.
+     * Queries the quotas of Elastic Compute Service (ECS) resources that you can create in an Alibaba Cloud region. For a specific region, you can query the maximum numbers of security groups, elastic network interfaces (ENIs), vCPUs for pay-as-you-go instances, vCPUs for spot instances, and dedicated hosts that you can create and the capacity quotas for pay-as-you-go disks that you can create. You can also query information such as network types or whether an account has completed the account verification.
      *
      * @remarks
      * After you [create](https://account.alibabacloud.com/register/intl_register.htm) an Alibaba Cloud account, you can create a specific number of ECS instances in different regions within the account. For more information, see [Limits](https://help.aliyun.com/document_detail/25412.html).
@@ -9278,7 +9296,7 @@ class Client extends openapi_core_1.default {
         return await this.describeAutoProvisioningGroupsWithOptions(request, runtime);
     }
     /**
-     * 查询自动快照策略的关联关系
+     * Queries association relationships of automatic snapshot policies.
      *
      * @param request - DescribeAutoSnapshotPolicyAssociationsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -9331,7 +9349,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeAutoSnapshotPolicyAssociationsResponse({}));
     }
     /**
-     * 查询自动快照策略的关联关系
+     * Queries association relationships of automatic snapshot policies.
      *
      * @param request - DescribeAutoSnapshotPolicyAssociationsRequest
      * @returns DescribeAutoSnapshotPolicyAssociationsResponse
@@ -9410,38 +9428,7 @@ class Client extends openapi_core_1.default {
         return await this.describeAutoSnapshotPolicyExWithOptions(request, runtime);
     }
     /**
-     * Queries resources in a zone. You can query the resources available in a zone before you create Elastic Compute Service (ECS) instances by calling the RunInstances operation or before you change instance types by calling the ModifyInstanceSpec operation.
-     *
-     * @remarks
-     * The value of `DestinationResource` determines whether you need to specify additional parameters. When you select a value in the following chain for DestinationResource, the more to the right the selected value is ordered, the more parameters you must specify.
-     * *   Sequence: `Zone > IoOptimized > InstanceType = Network = ddh > SystemDisk > DataDisk`
-     * *   Examples:
-     *     *   If you set `DestinationResource` to `DataDisk`, take note of the following items:
-     *         *   If you set `ResourceType` to `disk` to query the categories of data disks regardless of whether the disks are attached to ECS instances, you can leave `InstanceType` empty.
-     *         *   If you set `ResourceType` to `instance` to query the categories of data disks that are attached to ECS instances, you must specify `InstanceType` and `DataDiskCategory` due to instance type-specific limits on data disks.
-     *     *   If you set `DestinationResource` to `SystemDisk` and `ResourceType` to `instance`, you must specify `InstanceType` due to instance type-specific limits on system disks.
-     *     *   If you set `DestinationResource` to `InstanceType`, we recommend that you specify `IoOptimized` and `InstanceType`.
-     *     *   To query the ecs.g5.large instance type in all zones of the China (Hangzhou) region, set `RegionId to cn-hangzhou, DestinationResource to InstanceType, IoOptimized to optimized, and InstanceType to ecs.g5.large`.
-     *     *   To query the zones in which the ecs.g5.large instance type is available in the China (Hangzhou) region, set `RegionId to cn-hangzhou, DestinationResource to Zone, IoOptimized to optimized, and InstanceType to ecs.g5.large`.
-     * **To query the zones in which the ecs.g5.large instance type is available in the China (Hangzhou) region, specify parameters as follows:**
-     *     "RegionId": "cn-hangzhou",
-     *     "DestinationResource": "Zone",
-     *     "InstanceType": "ecs.g5.large"
-     * **To query the ecs.g5.large instance type in all zones of the China (Hangzhou) region, specify parameters as follows:**
-     *     "RegionId": "cn-hangzhou",
-     *     "DestinationResource": "InstanceType""InstanceType": "ecs.g5.large"
-     * **To query data disks of the ultra disk category in Hangzhou Zone B regardless of whether the disks are attached to ECS instances, specify parameters as follows:**
-     *     "RegionId": "cn-hangzhou",
-     *     "ZoneId": "cn-hangzhou-b",
-     *     "ResourceType": "disk",
-     *     "DestinationResource": "DataDisk"
-     * **To query data disks purchased together with ecs.g7.large instances that reside in Hangzhou Zone B and use Enterprise SSDs (ESSDs) as system disks, specify parameters as follows:**
-     *     "RegionId": "cn-hangzhou",
-     *     "ZoneId": "cn-hangzhou-b",
-     *     "ResourceType": "instance",
-     *     "InstanceType": "ecs.g7.large",
-     *     "DestinationResource": "SystemDisk",
-     *     "SystemDiskCategory": "cloud_essd"
+     * 查询可用资源
      *
      * @param request - DescribeAvailableResourceRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -9527,38 +9514,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeAvailableResourceResponse({}));
     }
     /**
-     * Queries resources in a zone. You can query the resources available in a zone before you create Elastic Compute Service (ECS) instances by calling the RunInstances operation or before you change instance types by calling the ModifyInstanceSpec operation.
-     *
-     * @remarks
-     * The value of `DestinationResource` determines whether you need to specify additional parameters. When you select a value in the following chain for DestinationResource, the more to the right the selected value is ordered, the more parameters you must specify.
-     * *   Sequence: `Zone > IoOptimized > InstanceType = Network = ddh > SystemDisk > DataDisk`
-     * *   Examples:
-     *     *   If you set `DestinationResource` to `DataDisk`, take note of the following items:
-     *         *   If you set `ResourceType` to `disk` to query the categories of data disks regardless of whether the disks are attached to ECS instances, you can leave `InstanceType` empty.
-     *         *   If you set `ResourceType` to `instance` to query the categories of data disks that are attached to ECS instances, you must specify `InstanceType` and `DataDiskCategory` due to instance type-specific limits on data disks.
-     *     *   If you set `DestinationResource` to `SystemDisk` and `ResourceType` to `instance`, you must specify `InstanceType` due to instance type-specific limits on system disks.
-     *     *   If you set `DestinationResource` to `InstanceType`, we recommend that you specify `IoOptimized` and `InstanceType`.
-     *     *   To query the ecs.g5.large instance type in all zones of the China (Hangzhou) region, set `RegionId to cn-hangzhou, DestinationResource to InstanceType, IoOptimized to optimized, and InstanceType to ecs.g5.large`.
-     *     *   To query the zones in which the ecs.g5.large instance type is available in the China (Hangzhou) region, set `RegionId to cn-hangzhou, DestinationResource to Zone, IoOptimized to optimized, and InstanceType to ecs.g5.large`.
-     * **To query the zones in which the ecs.g5.large instance type is available in the China (Hangzhou) region, specify parameters as follows:**
-     *     "RegionId": "cn-hangzhou",
-     *     "DestinationResource": "Zone",
-     *     "InstanceType": "ecs.g5.large"
-     * **To query the ecs.g5.large instance type in all zones of the China (Hangzhou) region, specify parameters as follows:**
-     *     "RegionId": "cn-hangzhou",
-     *     "DestinationResource": "InstanceType""InstanceType": "ecs.g5.large"
-     * **To query data disks of the ultra disk category in Hangzhou Zone B regardless of whether the disks are attached to ECS instances, specify parameters as follows:**
-     *     "RegionId": "cn-hangzhou",
-     *     "ZoneId": "cn-hangzhou-b",
-     *     "ResourceType": "disk",
-     *     "DestinationResource": "DataDisk"
-     * **To query data disks purchased together with ecs.g7.large instances that reside in Hangzhou Zone B and use Enterprise SSDs (ESSDs) as system disks, specify parameters as follows:**
-     *     "RegionId": "cn-hangzhou",
-     *     "ZoneId": "cn-hangzhou-b",
-     *     "ResourceType": "instance",
-     *     "InstanceType": "ecs.g7.large",
-     *     "DestinationResource": "SystemDisk",
-     *     "SystemDiskCategory": "cloud_essd"
+     * 查询可用资源
      *
      * @param request - DescribeAvailableResourceRequest
      * @returns DescribeAvailableResourceResponse
@@ -12073,13 +12029,22 @@ class Client extends openapi_core_1.default {
         return await this.describeImageFromFamilyWithOptions(request, runtime);
     }
     /**
-     * Queries the details of an image creation task.
+     * The key of tag N of the image creation task. Valid values of N: 1 to 20.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * *   The image template that is specified by the `ImagePipelineId` parameter cannot be a deleted image template. When an image template is deleted, the corresponding image creation task is deleted.
-     * *   You must specify `ImagePipelineId` or `ExecutionId`.
-     * *   You can configure the query token by using the `NextToken` parameter. Set NextToken to the value of `NextToken` that was returned the previous call to the `DescribeImagePipelineExecutions` operation. Then, use the `MaxResults` parameter to specify the maximum number of entries to return on each page.
+     * The status of the image creation task. Valid values:
+     * *   PREPARING: Resources, such as intermediate instances, are being created.
+     * *   REPAIRING: The source image is being repaired.
+     * *   BUILDING: The user-defined commands are being run and an image is being created.
+     * *   TESTING: The user-defined test commands are being run.
+     * *   DISTRIBUTING: The created image is being copied and shared.
+     * *   RELEASING: The temporary resources generated during the image creation process are being released.
+     * *   SUCCESS The image creation task is completed.
+     * *   PARTITION_SUCCESS: The image creation task is partially completed. The image is created, but exceptions may occur when the image was copied or shared or when temporary resources were released.
+     * *   FAILED: The image creation task fails.
+     * *   TEST_FAILED: The image is created, but the test fails.
+     * *   CANCELLING: The image creation task is being canceled.
+     * *   CANCELLED: The image creation task is canceled.
      *
      * @param request - DescribeImagePipelineExecutionsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -12141,13 +12106,22 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeImagePipelineExecutionsResponse({}));
     }
     /**
-     * Queries the details of an image creation task.
+     * The key of tag N of the image creation task. Valid values of N: 1 to 20.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * *   The image template that is specified by the `ImagePipelineId` parameter cannot be a deleted image template. When an image template is deleted, the corresponding image creation task is deleted.
-     * *   You must specify `ImagePipelineId` or `ExecutionId`.
-     * *   You can configure the query token by using the `NextToken` parameter. Set NextToken to the value of `NextToken` that was returned the previous call to the `DescribeImagePipelineExecutions` operation. Then, use the `MaxResults` parameter to specify the maximum number of entries to return on each page.
+     * The status of the image creation task. Valid values:
+     * *   PREPARING: Resources, such as intermediate instances, are being created.
+     * *   REPAIRING: The source image is being repaired.
+     * *   BUILDING: The user-defined commands are being run and an image is being created.
+     * *   TESTING: The user-defined test commands are being run.
+     * *   DISTRIBUTING: The created image is being copied and shared.
+     * *   RELEASING: The temporary resources generated during the image creation process are being released.
+     * *   SUCCESS The image creation task is completed.
+     * *   PARTITION_SUCCESS: The image creation task is partially completed. The image is created, but exceptions may occur when the image was copied or shared or when temporary resources were released.
+     * *   FAILED: The image creation task fails.
+     * *   TEST_FAILED: The image is created, but the test fails.
+     * *   CANCELLING: The image creation task is being canceled.
+     * *   CANCELLED: The image creation task is canceled.
      *
      * @param request - DescribeImagePipelineExecutionsRequest
      * @returns DescribeImagePipelineExecutionsResponse
@@ -13825,22 +13799,24 @@ class Client extends openapi_core_1.default {
         return await this.describeInstancesFullStatusWithOptions(request, runtime);
     }
     /**
-     * Queries the execution results of one or more Cloud Assistant commands on Elastic Compute Service (ECS) instances.
+     * The execution status of the command. Valid values:
+     * *   Running:
+     *     *   Scheduled task: Before you stop the scheduled execution of the command, the execution state is always Running.
+     *     *   One-time task: If the command is being run on instances, the execution state is Running.
+     * *   Finished:
+     *     *   Scheduled task: The execution state can never be Finished.
+     *     *   One-time task: The execution was complete on all instances, or the execution was stopped on some instances and was complete on the other instances.
+     * *   Failed:
+     *     *   Scheduled task: The execution state can never be Failed.
+     *     *   One-time task: The execution failed on all instances.
+     * *   PartialFailed:
+     *     *   Scheduled task: The execution state can never be PartialFailed.
+     *     *   One-time task: The execution failed on some instances.
+     * *   Stopped: The task was stopped.
+     * *   Stopping: The task is being stopped.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * *   After you run a command, the command may fail to run or may return unexpected results. You can call this operation to query the execution results.
-     * *   You can query information about command executions within the last four weeks. Up to 100,000 pieces of execution information can be retained.
-     * *   You can [subscribe to Cloud Assistant task status events](https://help.aliyun.com/document_detail/2669130.html) to obtain command execution results from the events. This helps you reduce the number of times to poll API operations and improve efficiency.
-     * *   During a paged query, when you call the DescribeInvocationResults operation to retrieve the first page of results, set `MaxResults` to specify the maximum number of entries to return in the call. The return value of `NextToken` is a pagination token that can be used in the next call to retrieve a new page of results. When you call the DescribeInvocationResults operation to retrieve a new page of results, set `NextToken` to the `NextToken` value returned in the previous call and set `MaxResults` to specify the maximum number of entries to return in this call.
-     * *   Comparison between the `DescribeInvocations` and `DescribeInvocationResults` operations:
-     *     *   Scenario in which the `RunCommand` or `InvokeCommand` operation is called to run a Cloud Assistant command on multiple instances:
-     *         *   The `DescribeInvocations` operation queries the execution status of the command on each instance and the overall execution status of the command on all instances.
-     *         *   The `DescribeInvocationResults` operation queries only the execution status of the command on each instance.
-     *     *   Scenario in which the `RunCommand` or `InvokeCommand` operation is called to run a Cloud Assistant command on a single instance:
-     *         *   The `DescribeInvocations` operation is equivalent to the `DescribeInvocationResults` operation.
-     *     *   If you want to query the status of each execution for a scheduled (recurring) task or a task that is automatically executed on instance startup (`RepeatMode is set to Period or EveryReboot`), you can call only the `DescribeInvocationResults` operation and must set `IncludeHistory` to true. The `DescribeInvocations` operation queries only the most recent execution status of the command.
-     *     *   If you want to view the command content and parameters, you can call only the `DescribeInvocations` operation and check the `CommandContent` value in the response.
+     * DescribeInvocationResults
      *
      * @param request - DescribeInvocationResultsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -13920,22 +13896,24 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeInvocationResultsResponse({}));
     }
     /**
-     * Queries the execution results of one or more Cloud Assistant commands on Elastic Compute Service (ECS) instances.
+     * The execution status of the command. Valid values:
+     * *   Running:
+     *     *   Scheduled task: Before you stop the scheduled execution of the command, the execution state is always Running.
+     *     *   One-time task: If the command is being run on instances, the execution state is Running.
+     * *   Finished:
+     *     *   Scheduled task: The execution state can never be Finished.
+     *     *   One-time task: The execution was complete on all instances, or the execution was stopped on some instances and was complete on the other instances.
+     * *   Failed:
+     *     *   Scheduled task: The execution state can never be Failed.
+     *     *   One-time task: The execution failed on all instances.
+     * *   PartialFailed:
+     *     *   Scheduled task: The execution state can never be PartialFailed.
+     *     *   One-time task: The execution failed on some instances.
+     * *   Stopped: The task was stopped.
+     * *   Stopping: The task is being stopped.
      *
      * @remarks
-     * ## [](#)Usage notes
-     * *   After you run a command, the command may fail to run or may return unexpected results. You can call this operation to query the execution results.
-     * *   You can query information about command executions within the last four weeks. Up to 100,000 pieces of execution information can be retained.
-     * *   You can [subscribe to Cloud Assistant task status events](https://help.aliyun.com/document_detail/2669130.html) to obtain command execution results from the events. This helps you reduce the number of times to poll API operations and improve efficiency.
-     * *   During a paged query, when you call the DescribeInvocationResults operation to retrieve the first page of results, set `MaxResults` to specify the maximum number of entries to return in the call. The return value of `NextToken` is a pagination token that can be used in the next call to retrieve a new page of results. When you call the DescribeInvocationResults operation to retrieve a new page of results, set `NextToken` to the `NextToken` value returned in the previous call and set `MaxResults` to specify the maximum number of entries to return in this call.
-     * *   Comparison between the `DescribeInvocations` and `DescribeInvocationResults` operations:
-     *     *   Scenario in which the `RunCommand` or `InvokeCommand` operation is called to run a Cloud Assistant command on multiple instances:
-     *         *   The `DescribeInvocations` operation queries the execution status of the command on each instance and the overall execution status of the command on all instances.
-     *         *   The `DescribeInvocationResults` operation queries only the execution status of the command on each instance.
-     *     *   Scenario in which the `RunCommand` or `InvokeCommand` operation is called to run a Cloud Assistant command on a single instance:
-     *         *   The `DescribeInvocations` operation is equivalent to the `DescribeInvocationResults` operation.
-     *     *   If you want to query the status of each execution for a scheduled (recurring) task or a task that is automatically executed on instance startup (`RepeatMode is set to Period or EveryReboot`), you can call only the `DescribeInvocationResults` operation and must set `IncludeHistory` to true. The `DescribeInvocations` operation queries only the most recent execution status of the command.
-     *     *   If you want to view the command content and parameters, you can call only the `DescribeInvocations` operation and check the `CommandContent` value in the response.
+     * DescribeInvocationResults
      *
      * @param request - DescribeInvocationResultsRequest
      * @returns DescribeInvocationResultsResponse
@@ -13945,21 +13923,10 @@ class Client extends openapi_core_1.default {
         return await this.describeInvocationResultsWithOptions(request, runtime);
     }
     /**
-     * Queries the execution list and states of Cloud Assistant commands.
+     * The command type.
      *
      * @remarks
-     *   After you run a command, the command may fail to run or may return unexpected results. You can call this operation to query the execution results.
-     * *   You can query information about command executions within the last four weeks. Up to 100,000 pieces of execution information can be retained.
-     * *   You can [subscribe to Cloud Assistant task status events](https://help.aliyun.com/document_detail/2669130.html) to obtain command execution results from the events. This helps you reduce the number of times to poll API operations and improve efficiency.
-     * *   During a paged query, when you call the DescribeInvocations operation to retrieve the first page of results, set `MaxResults` to specify the maximum number of entries to return in the call. The return value of `NextToken` is a pagination token that can be used in the next call to retrieve a new page of results. When you call the DescribeInvocations operation to retrieve a new page of results, set `NextToken` to the `NextToken` value returned in the previous call and set `MaxResults` to specify the maximum number of entries to return in this call.
-     * *   Differences between the `DescribeInvocations` and `DescribeInvocationResults` operations:
-     *     *   Scenario in which the `RunCommand` or `InvokeCommand` operation is called to run a Cloud Assistant command on multiple instances:
-     *         *   The `DescribeInvocations` operation queries the execution status of the command on each instance and the overall execution status of the command on all instances.
-     *         *   The `DescribeInvocationResults` operation queries only the execution status of the command on each instance.
-     *     *   Scenario in which the `RunCommand` or `InvokeCommand` operation is called to run a Cloud Assistant command on a single instance:
-     *         *   The `DescribeInvocations` operation is equivalent to the `DescribeInvocationResults` operation.
-     *     *   If you want to query the status of each execution for a scheduled (recurring) task or a task that is automatically executed on instance startup (`RepeatMode is set to Period or EveryReboot`), you can call only the `DescribeInvocationResults` operation and must set `IncludeHistory` to true. The `DescribeInvocations` operation queries only the most recent execution status of the command.
-     *     *   If you want to view the command content and parameters, you can call only the `DescribeInvocations` operation and check the `CommandContent` value in the response.
+     * DescribeInvocations
      *
      * @param request - DescribeInvocationsRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -14051,21 +14018,10 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeInvocationsResponse({}));
     }
     /**
-     * Queries the execution list and states of Cloud Assistant commands.
+     * The command type.
      *
      * @remarks
-     *   After you run a command, the command may fail to run or may return unexpected results. You can call this operation to query the execution results.
-     * *   You can query information about command executions within the last four weeks. Up to 100,000 pieces of execution information can be retained.
-     * *   You can [subscribe to Cloud Assistant task status events](https://help.aliyun.com/document_detail/2669130.html) to obtain command execution results from the events. This helps you reduce the number of times to poll API operations and improve efficiency.
-     * *   During a paged query, when you call the DescribeInvocations operation to retrieve the first page of results, set `MaxResults` to specify the maximum number of entries to return in the call. The return value of `NextToken` is a pagination token that can be used in the next call to retrieve a new page of results. When you call the DescribeInvocations operation to retrieve a new page of results, set `NextToken` to the `NextToken` value returned in the previous call and set `MaxResults` to specify the maximum number of entries to return in this call.
-     * *   Differences between the `DescribeInvocations` and `DescribeInvocationResults` operations:
-     *     *   Scenario in which the `RunCommand` or `InvokeCommand` operation is called to run a Cloud Assistant command on multiple instances:
-     *         *   The `DescribeInvocations` operation queries the execution status of the command on each instance and the overall execution status of the command on all instances.
-     *         *   The `DescribeInvocationResults` operation queries only the execution status of the command on each instance.
-     *     *   Scenario in which the `RunCommand` or `InvokeCommand` operation is called to run a Cloud Assistant command on a single instance:
-     *         *   The `DescribeInvocations` operation is equivalent to the `DescribeInvocationResults` operation.
-     *     *   If you want to query the status of each execution for a scheduled (recurring) task or a task that is automatically executed on instance startup (`RepeatMode is set to Period or EveryReboot`), you can call only the `DescribeInvocationResults` operation and must set `IncludeHistory` to true. The `DescribeInvocations` operation queries only the most recent execution status of the command.
-     *     *   If you want to view the command content and parameters, you can call only the `DescribeInvocations` operation and check the `CommandContent` value in the response.
+     * DescribeInvocations
      *
      * @param request - DescribeInvocationsRequest
      * @returns DescribeInvocationsResponse
@@ -23090,7 +23046,7 @@ class Client extends openapi_core_1.default {
         return await this.modifyInstanceMetadataOptionsWithOptions(request, runtime);
     }
     /**
-     * Modifies the network bandwidth weight of an instance.
+     * Modifies instance network configurations.
      *
      * @remarks
      * When you call this operation, note that:
@@ -23137,7 +23093,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyInstanceNetworkOptionsResponse({}));
     }
     /**
-     * Modifies the network bandwidth weight of an instance.
+     * Modifies instance network configurations.
      *
      * @remarks
      * When you call this operation, note that:
@@ -25231,7 +25187,7 @@ class Client extends openapi_core_1.default {
         return await this.modifySnapshotGroupWithOptions(request, runtime);
     }
     /**
-     * Changes the name or modifies the description of a storage capacity unit (SCU).
+     * Modifies the name or description of a storage capacity unit (SCU).
      *
      * @param request - ModifyStorageCapacityUnitAttributeRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -25281,7 +25237,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyStorageCapacityUnitAttributeResponse({}));
     }
     /**
-     * Changes the name or modifies the description of a storage capacity unit (SCU).
+     * Modifies the name or description of a storage capacity unit (SCU).
      *
      * @param request - ModifyStorageCapacityUnitAttributeRequest
      * @returns ModifyStorageCapacityUnitAttributeResponse
@@ -25702,6 +25658,54 @@ class Client extends openapi_core_1.default {
         let runtime = new $dara.RuntimeOptions({});
         return await this.modifyVpcAttributeWithOptions(request, runtime);
     }
+    /**
+     * Activate the snapshot service.
+     *
+     * @param request - OpenSnapshotServiceRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns OpenSnapshotServiceResponse
+     */
+    async openSnapshotServiceWithOptions(request, runtime) {
+        request.validate();
+        let query = {};
+        if (!$dara.isNull(request.ownerId)) {
+            query["OwnerId"] = request.ownerId;
+        }
+        if (!$dara.isNull(request.regionId)) {
+            query["RegionId"] = request.regionId;
+        }
+        if (!$dara.isNull(request.resourceOwnerAccount)) {
+            query["ResourceOwnerAccount"] = request.resourceOwnerAccount;
+        }
+        if (!$dara.isNull(request.resourceOwnerId)) {
+            query["ResourceOwnerId"] = request.resourceOwnerId;
+        }
+        let req = new openapi_core_2.$OpenApiUtil.OpenApiRequest({
+            query: openapi_core_2.OpenApiUtil.query(query),
+        });
+        let params = new openapi_core_2.$OpenApiUtil.Params({
+            action: "OpenSnapshotService",
+            version: "2014-05-26",
+            protocol: "HTTPS",
+            pathname: "/",
+            method: "POST",
+            authType: "AK",
+            style: "RPC",
+            reqBodyType: "formData",
+            bodyType: "json",
+        });
+        return $dara.cast(await this.callApi(params, req, runtime), new $_model.OpenSnapshotServiceResponse({}));
+    }
+    /**
+     * Activate the snapshot service.
+     *
+     * @param request - OpenSnapshotServiceRequest
+     * @returns OpenSnapshotServiceResponse
+     */
+    async openSnapshotService(request) {
+        let runtime = new $dara.RuntimeOptions({});
+        return await this.openSnapshotServiceWithOptions(request, runtime);
+    }
     /**
      * Purchases an elasticity assurance that is not in the Active state and for which resources are prepared.
      *
@@ -26578,7 +26582,7 @@ class Client extends openapi_core_1.default {
         return await this.releaseCapacityReservationWithOptions(request, runtime);
     }
     /**
-     * Releases a pay-as-you-go dedicated host.
+     * Releases a pay-as-you-go Dedicated Host or an expired subscription Dedicated Host.
      *
      * @remarks
      * ## Usage notes
@@ -26609,6 +26613,9 @@ class Client extends openapi_core_1.default {
         if (!$dara.isNull(request.resourceOwnerId)) {
             query["ResourceOwnerId"] = request.resourceOwnerId;
         }
+        if (!$dara.isNull(request.terminateSubscription)) {
+            query["TerminateSubscription"] = request.terminateSubscription;
+        }
         let req = new openapi_core_2.$OpenApiUtil.OpenApiRequest({
             query: openapi_core_2.OpenApiUtil.query(query),
         });
@@ -26626,7 +26633,7 @@ class Client extends openapi_core_1.default {
         return $dara.cast(await this.callApi(params, req, runtime), new $_model.ReleaseDedicatedHostResponse({}));
     }
     /**
-     * Releases a pay-as-you-go dedicated host.
+     * Releases a pay-as-you-go Dedicated Host or an expired subscription Dedicated Host.
      *
      * @remarks
      * ## Usage notes
@@ -27187,13 +27194,11 @@ class Client extends openapi_core_1.default {
      * *   The category of the system disk cannot be changed.
      * *   Make sure that no unpaid orders are associated with the instance.
      * *   The instance must be in the `Stopped` state.
-     *
-     *     **Note** The operation is applicable only to instances of the Virtual Private Cloud (VPC) type. If the instance is a pay-as-you-go instance and default economical mode is enabled, enable standard mode when you stop the instance. This prevents the instance from being unable to restart due to insufficient ECS resources after the system disk is replaced. For more information, see [StopInstance](https://help.aliyun.com/document_detail/25501.html).
-     * *   The instance cannot be locked for security reasons. If the value of `OperationLocks` in the DescribeInstances response contains `"LockReason": "security"` for an instance, the instance is locked for security reasons. For more information, see [API behavior when an instance is locked for security reasons](https://help.aliyun.com/document_detail/25695.html).
-     * *   You can configure `SystemDisk.Size` to specify the capacity of the new system disk.
-     * After you call the ReplaceSystemDisk operation, you can use one of the following methods to check whether the system disk is replaced:
-     * *   Call the [DescribeDisks](https://help.aliyun.com/document_detail/25514.html) operation to query the status of the new system disk. If the new system disk is in the In Use state, the system disk is replaced.
-     * *   Call the [DescribeInstances](https://help.aliyun.com/document_detail/25506.html) operation to query the status of the instance whose system disk is replaced. If the `OperationLocks` parameter is empty, the system disk is replaced.
+     *     **
+     *     **Note:** The operation is applicable only to instances of the Virtual Private Cloud (VPC) type. If the instance is a pay-as-you-go instance and economical mode by default is enabled, you can enable standard mode when stopping the instance. This prevents instance restart failures caused by insufficient resources after the system disk is replaced. For more information, see [StopInstance](https://help.aliyun.com/document_detail/25501.html).
+     * *   You can use the parameter `SystemDisk.Size` to re-specify the size of the system disk (cannot be less than the original system disk capacity).
+     * *   If the `OperationLocks` parameter value of the instance contains `"LockReason": "security"`, then the ECS instance is locked for security. You cannot replace the system disk. For more information, see [API behavior when an instance is locked for security reasons](https://help.aliyun.com/document_detail/25695.html).
+     * After the system disk is replaced, you can query the status of the instance to check whether the replacement is successful by using the [DescribeInstances](https://help.aliyun.com/document_detail/25506.html) interface. If the `OperationLocks` parameter is empty, the system disk is replaced.
      *
      * @param request - ReplaceSystemDiskRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -27288,13 +27293,11 @@ class Client extends openapi_core_1.default {
      * *   The category of the system disk cannot be changed.
      * *   Make sure that no unpaid orders are associated with the instance.
      * *   The instance must be in the `Stopped` state.
-     *
-     *     **Note** The operation is applicable only to instances of the Virtual Private Cloud (VPC) type. If the instance is a pay-as-you-go instance and default economical mode is enabled, enable standard mode when you stop the instance. This prevents the instance from being unable to restart due to insufficient ECS resources after the system disk is replaced. For more information, see [StopInstance](https://help.aliyun.com/document_detail/25501.html).
-     * *   The instance cannot be locked for security reasons. If the value of `OperationLocks` in the DescribeInstances response contains `"LockReason": "security"` for an instance, the instance is locked for security reasons. For more information, see [API behavior when an instance is locked for security reasons](https://help.aliyun.com/document_detail/25695.html).
-     * *   You can configure `SystemDisk.Size` to specify the capacity of the new system disk.
-     * After you call the ReplaceSystemDisk operation, you can use one of the following methods to check whether the system disk is replaced:
-     * *   Call the [DescribeDisks](https://help.aliyun.com/document_detail/25514.html) operation to query the status of the new system disk. If the new system disk is in the In Use state, the system disk is replaced.
-     * *   Call the [DescribeInstances](https://help.aliyun.com/document_detail/25506.html) operation to query the status of the instance whose system disk is replaced. If the `OperationLocks` parameter is empty, the system disk is replaced.
+     *     **
+     *     **Note:** The operation is applicable only to instances of the Virtual Private Cloud (VPC) type. If the instance is a pay-as-you-go instance and economical mode by default is enabled, you can enable standard mode when stopping the instance. This prevents instance restart failures caused by insufficient resources after the system disk is replaced. For more information, see [StopInstance](https://help.aliyun.com/document_detail/25501.html).
+     * *   You can use the parameter `SystemDisk.Size` to re-specify the size of the system disk (cannot be less than the original system disk capacity).
+     * *   If the `OperationLocks` parameter value of the instance contains `"LockReason": "security"`, then the ECS instance is locked for security. You cannot replace the system disk. For more information, see [API behavior when an instance is locked for security reasons](https://help.aliyun.com/document_detail/25695.html).
+     * After the system disk is replaced, you can query the status of the instance to check whether the replacement is successful by using the [DescribeInstances](https://help.aliyun.com/document_detail/25506.html) interface. If the `OperationLocks` parameter is empty, the system disk is replaced.
      *
      * @param request - ReplaceSystemDiskRequest
      * @returns ReplaceSystemDiskResponse
@@ -27574,8 +27577,8 @@ class Client extends openapi_core_1.default {
      * Resizes a system disk or a data disk.
      *
      * @remarks
-     * > Before you call this operation to resize a disk, you must check the partition format of the disk. You cannot resize a master boot record (MBR) disk to a size that is larger than 2 TiB. If you resize an MBR disk to a size that is larger than 2 TiB, data may be lost. If you want to resize an MBR disk to a size that is larger than 2 TiB, we recommend performing the following steps: Create a new data disk that is larger than 2 TiB in size, partition and format the new data disk by using the GUID Partition Table (GPT) format, and then copy data from the MBR disk to the GPT data disk. For more information, see [Step 1: Resize a disk to extend the disk capacity](https://help.aliyun.com/document_detail/44986.html).
-     * *   You can resize disks of the following disk categories: basic disks (`cloud`), ultra disks (`cloud_efficiency`), standard SSDs (`cloud_ssd`), Enterprise SSDs (ESSDs) (`cloud_essd`), ESSD AutoPL disks (cloud_auto), standard elastic ephemeral disks (elastic_ephemeral_disk_standard), and premium elastic ephemeral disks (elastic_ephemeral_disk_premium).
+     * >  Before you call this operation to resize a disk, you must check the partition format of the disk. If the format is MBR, you cannot resize the file to more than 2TiB. Otherwise, data loss may occur. If you want to resize an MBR partition, we recommend creating and mounting a data disk in the GPT partition format, and then copy the existing data to the new data disk. For more information, see [Resize a disk to extend the disk capacity](https://help.aliyun.com/document_detail/44986.html).
+     * *   The disk types that can be resized include basic disks (`cloud` ), ultra disks (`cloud_efficiency` ), SSDs (`cloud_ssd` ), Enterprise SSDs (ESSDs)(`cloud_essd` ), ESSD AutoPL disks (cloud_auto), standard elastic ephemeral disks (elastic_ephemeral_disk_standard), premium elastic ephemeral disks (elastic_ephemeral_disk_premium), and Regional ESSDs (cloud_regional_disk_auto).
      * *   You cannot resize a cloud disk when a snapshot is being created for the disk. Wait until the snapshot is created before you resize the cloud disk.
      * *   You cannot call this operation to extend partitions or file systems. You must manually allocate partitions and file systems after the resize cloud disk capacity. For more information, see [Extend partitions and file systems (Linux)](~~2949817#bb3b1f02e51pj~~) and [Extend partitions and file systems (windows)](~~2932233#a9f9b78f3fujb~~).
      * *   If the multi-attach feature is enabled for a cloud disk, you can resize the disk online or offline. Make sure that the ECS instances to which the disk is attached meet the following requirements:
@@ -27637,8 +27640,8 @@ class Client extends openapi_core_1.default {
      * Resizes a system disk or a data disk.
      *
      * @remarks
-     * > Before you call this operation to resize a disk, you must check the partition format of the disk. You cannot resize a master boot record (MBR) disk to a size that is larger than 2 TiB. If you resize an MBR disk to a size that is larger than 2 TiB, data may be lost. If you want to resize an MBR disk to a size that is larger than 2 TiB, we recommend performing the following steps: Create a new data disk that is larger than 2 TiB in size, partition and format the new data disk by using the GUID Partition Table (GPT) format, and then copy data from the MBR disk to the GPT data disk. For more information, see [Step 1: Resize a disk to extend the disk capacity](https://help.aliyun.com/document_detail/44986.html).
-     * *   You can resize disks of the following disk categories: basic disks (`cloud`), ultra disks (`cloud_efficiency`), standard SSDs (`cloud_ssd`), Enterprise SSDs (ESSDs) (`cloud_essd`), ESSD AutoPL disks (cloud_auto), standard elastic ephemeral disks (elastic_ephemeral_disk_standard), and premium elastic ephemeral disks (elastic_ephemeral_disk_premium).
+     * >  Before you call this operation to resize a disk, you must check the partition format of the disk. If the format is MBR, you cannot resize the file to more than 2TiB. Otherwise, data loss may occur. If you want to resize an MBR partition, we recommend creating and mounting a data disk in the GPT partition format, and then copy the existing data to the new data disk. For more information, see [Resize a disk to extend the disk capacity](https://help.aliyun.com/document_detail/44986.html).
+     * *   The disk types that can be resized include basic disks (`cloud` ), ultra disks (`cloud_efficiency` ), SSDs (`cloud_ssd` ), Enterprise SSDs (ESSDs)(`cloud_essd` ), ESSD AutoPL disks (cloud_auto), standard elastic ephemeral disks (elastic_ephemeral_disk_standard), premium elastic ephemeral disks (elastic_ephemeral_disk_premium), and Regional ESSDs (cloud_regional_disk_auto).
      * *   You cannot resize a cloud disk when a snapshot is being created for the disk. Wait until the snapshot is created before you resize the cloud disk.
      * *   You cannot call this operation to extend partitions or file systems. You must manually allocate partitions and file systems after the resize cloud disk capacity. For more information, see [Extend partitions and file systems (Linux)](~~2949817#bb3b1f02e51pj~~) and [Extend partitions and file systems (windows)](~~2932233#a9f9b78f3fujb~~).
      * *   If the multi-attach feature is enabled for a cloud disk, you can resize the disk online or offline. Make sure that the ECS instances to which the disk is attached meet the following requirements: