@alicloud/ess20220222 1.4.0 → 1.4.2

package/dist/client.d.ts

@@ -1886,11 +1886,27 @@ export declare class DescribePatternTypesRequest extends $tea.Model {
     channelId?: number;
     cores?: number;
     coresList?: number[];
+    cpuArchitectures?: string[];
     excludedInstanceType?: string[];
+    gpuSpecs?: string[];
+    instanceCategories?: string[];
     instanceFamilyLevel?: string;
+    instanceTypeFamilies?: string[];
     maxPrice?: number;
+    maximumCpuCoreCount?: number;
+    maximumGpuAmount?: number;
+    maximumMemorySize?: number;
     memory?: number;
     memoryList?: number[];
+    minimumBaselineCredit?: number;
+    minimumCpuCoreCount?: number;
+    minimumEniIpv6AddressQuantity?: number;
+    minimumEniPrivateIpAddressQuantity?: number;
+    minimumEniQuantity?: number;
+    minimumGpuAmount?: number;
+    minimumInitialCredit?: number;
+    minimumMemorySize?: number;
+    physicalProcessorModels?: string[];
     regionId?: string;
     spotStrategy?: string;
     vSwitchId?: string[];
@@ -2497,6 +2513,7 @@ export declare class DetachInstancesRequest extends $tea.Model {
     clientToken?: string;
     decreaseDesiredCapacity?: boolean;
     detachOption?: string;
+    ignoreInvalidInstance?: boolean;
     instanceIds?: string[];
     lifecycleHook?: boolean;
     ownerAccount?: string;
@@ -3885,6 +3902,7 @@ export declare class RecordLifecycleActionHeartbeatResponse extends $tea.Model {
 export declare class RemoveInstancesRequest extends $tea.Model {
     clientToken?: string;
     decreaseDesiredCapacity?: boolean;
+    ignoreInvalidInstance?: boolean;
     instanceIds?: string[];
     ownerAccount?: string;
     ownerId?: number;
@@ -5094,10 +5112,26 @@ export declare class CreateScalingConfigurationRequestInstancePatternInfos exten
     architectures?: string[];
     burstablePerformance?: string;
     cores?: number;
+    cpuArchitectures?: string[];
     excludedInstanceTypes?: string[];
+    gpuSpecs?: string[];
+    instanceCategories?: string[];
     instanceFamilyLevel?: string;
+    instanceTypeFamilies?: string[];
     maxPrice?: number;
+    maximumCpuCoreCount?: number;
+    maximumGpuAmount?: number;
+    maximumMemorySize?: number;
     memory?: number;
+    minimumBaselineCredit?: number;
+    minimumCpuCoreCount?: number;
+    minimumEniIpv6AddressQuantity?: number;
+    minimumEniPrivateIpAddressQuantity?: number;
+    minimumEniQuantity?: number;
+    minimumGpuAmount?: number;
+    minimumInitialCredit?: number;
+    minimumMemorySize?: number;
+    physicalProcessorModels?: string[];
     static names(): {
         [key: string]: string;
     };
@@ -5238,10 +5272,26 @@ export declare class CreateScalingConfigurationShrinkRequestInstancePatternInfos
     architectures?: string[];
     burstablePerformance?: string;
     cores?: number;
+    cpuArchitectures?: string[];
     excludedInstanceTypes?: string[];
+    gpuSpecs?: string[];
+    instanceCategories?: string[];
     instanceFamilyLevel?: string;
+    instanceTypeFamilies?: string[];
     maxPrice?: number;
+    maximumCpuCoreCount?: number;
+    maximumGpuAmount?: number;
+    maximumMemorySize?: number;
     memory?: number;
+    minimumBaselineCredit?: number;
+    minimumCpuCoreCount?: number;
+    minimumEniIpv6AddressQuantity?: number;
+    minimumEniPrivateIpAddressQuantity?: number;
+    minimumEniQuantity?: number;
+    minimumGpuAmount?: number;
+    minimumInitialCredit?: number;
+    minimumMemorySize?: number;
+    physicalProcessorModels?: string[];
     static names(): {
         [key: string]: string;
     };
@@ -6406,10 +6456,26 @@ export declare class DescribeScalingConfigurationsResponseBodyScalingConfigurati
     architectures?: string[];
     burstablePerformance?: string;
     cores?: number;
+    cpuArchitectures?: string[];
     excludedInstanceTypes?: string[];
+    gpuSpecs?: string[];
+    instanceCategories?: string[];
     instanceFamilyLevel?: string;
+    instanceTypeFamilies?: string[];
     maxPrice?: number;
+    maximumCpuCoreCount?: number;
+    maximumGpuAmount?: number;
+    maximumMemorySize?: number;
     memory?: number;
+    minimumBaselineCredit?: number;
+    minimumCpuCoreCount?: number;
+    minimumEniIpv6AddressQuantity?: number;
+    minimumEniPrivateIpAddressQuantity?: number;
+    minimumEniQuantity?: number;
+    minimumGpuAmount?: number;
+    minimumInitialCredit?: number;
+    minimumMemorySize?: number;
+    physicalProcessorModels?: string[];
     static names(): {
         [key: string]: string;
     };
@@ -7804,10 +7870,26 @@ export declare class ModifyScalingConfigurationRequestInstancePatternInfos exten
     architectures?: string[];
     burstablePerformance?: string;
     cores?: number;
+    cpuArchitectures?: string[];
     excludedInstanceTypes?: string[];
+    gpuSpecs?: string[];
+    instanceCategories?: string[];
     instanceFamilyLevel?: string;
+    instanceTypeFamilies?: string[];
     maxPrice?: number;
+    maximumCpuCoreCount?: number;
+    maximumGpuAmount?: number;
+    maximumMemorySize?: number;
     memory?: number;
+    minimumBaselineCredit?: number;
+    minimumCpuCoreCount?: number;
+    minimumEniIpv6AddressQuantity?: number;
+    minimumEniPrivateIpAddressQuantity?: number;
+    minimumEniQuantity?: number;
+    minimumGpuAmount?: number;
+    minimumInitialCredit?: number;
+    minimumMemorySize?: number;
+    physicalProcessorModels?: string[];
     static names(): {
         [key: string]: string;
     };
@@ -7948,10 +8030,26 @@ export declare class ModifyScalingConfigurationShrinkRequestInstancePatternInfos
     architectures?: string[];
     burstablePerformance?: string;
     cores?: number;
+    cpuArchitectures?: string[];
     excludedInstanceTypes?: string[];
+    gpuSpecs?: string[];
+    instanceCategories?: string[];
     instanceFamilyLevel?: string;
+    instanceTypeFamilies?: string[];
     maxPrice?: number;
+    maximumCpuCoreCount?: number;
+    maximumGpuAmount?: number;
+    maximumMemorySize?: number;
     memory?: number;
+    minimumBaselineCredit?: number;
+    minimumCpuCoreCount?: number;
+    minimumEniIpv6AddressQuantity?: number;
+    minimumEniPrivateIpAddressQuantity?: number;
+    minimumEniQuantity?: number;
+    minimumGpuAmount?: number;
+    minimumInitialCredit?: number;
+    minimumMemorySize?: number;
+    physicalProcessorModels?: string[];
     static names(): {
         [key: string]: string;
     };
@@ -8225,12 +8323,11 @@ export default class Client extends OpenApi {
      */
     applyScalingGroup(request: ApplyScalingGroupRequest): Promise<ApplyScalingGroupResponse>;
     /**
-     * @summary Associates Application Load Balancer (ALB) server groups with a scaling group.
+     * @summary Attaches Application Load Balancer (ALB) server groups to a scaling group. To seamlessly adjust the number of instances in response to changes in your business workload or to maintain the uninterrupted accessibility of your application, you can call the AttachAlbServerGroups operation. By attaching ALB server groups to your scaling group, this operation enables Auto Scaling to automatically tailor your computing capacity to your business needs. Furthermore, it optimizes traffic routing by dynamically allocating incoming requests based on current workload patterns, which significantly improves the stability and performance of your application.
      *
-     * @description Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
-     * *   The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
+     * @description Before you call the operation to attach an ALB server group to your scaling group, make sure that the following requirements are met:
+     * *   The scaling group and the ALB server group share the same virtual private cloud (VPC).
      * *   The ALB server group is in the Available state.
-     * *   You can associate only a limited number of ALB server groups with a scaling group. To view the quota or manually request a quota increase, go to [Quota Center](https://quotas.console.aliyun.com/products/ess/quotas).
      *
      * @param request AttachAlbServerGroupsRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8238,12 +8335,11 @@ export default class Client extends OpenApi {
      */
     attachAlbServerGroupsWithOptions(request: AttachAlbServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<AttachAlbServerGroupsResponse>;
     /**
-     * @summary Associates Application Load Balancer (ALB) server groups with a scaling group.
+     * @summary Attaches Application Load Balancer (ALB) server groups to a scaling group. To seamlessly adjust the number of instances in response to changes in your business workload or to maintain the uninterrupted accessibility of your application, you can call the AttachAlbServerGroups operation. By attaching ALB server groups to your scaling group, this operation enables Auto Scaling to automatically tailor your computing capacity to your business needs. Furthermore, it optimizes traffic routing by dynamically allocating incoming requests based on current workload patterns, which significantly improves the stability and performance of your application.
      *
-     * @description Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
-     * *   The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
+     * @description Before you call the operation to attach an ALB server group to your scaling group, make sure that the following requirements are met:
+     * *   The scaling group and the ALB server group share the same virtual private cloud (VPC).
      * *   The ALB server group is in the Available state.
-     * *   You can associate only a limited number of ALB server groups with a scaling group. To view the quota or manually request a quota increase, go to [Quota Center](https://quotas.console.aliyun.com/products/ess/quotas).
      *
      * @param request AttachAlbServerGroupsRequest
      * @return AttachAlbServerGroupsResponse
@@ -8353,7 +8449,7 @@ export default class Client extends OpenApi {
      */
     attachLoadBalancers(request: AttachLoadBalancersRequest): Promise<AttachLoadBalancersResponse>;
     /**
-     * @summary Attaches one or more server groups to a scaling group. You can attach the following server groups to a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
+     * @summary Attaches server groups to a scaling group. To seamlessly adjust the number of instances in response to changes in your business workload or to maintain the uninterrupted accessibility of your application, you can call the AttachServerGroups operation. By attaching Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups to your scaling group, this operation enables Auto Scaling to automatically tailor your computing capacity to your business needs. Furthermore, it optimizes traffic routing by dynamically allocating incoming requests based on current workload patterns, which significantly improves the stability and performance of your application.
      *
      * @param request AttachServerGroupsRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8361,29 +8457,30 @@ export default class Client extends OpenApi {
      */
     attachServerGroupsWithOptions(request: AttachServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<AttachServerGroupsResponse>;
     /**
-     * @summary Attaches one or more server groups to a scaling group. You can attach the following server groups to a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
+     * @summary Attaches server groups to a scaling group. To seamlessly adjust the number of instances in response to changes in your business workload or to maintain the uninterrupted accessibility of your application, you can call the AttachServerGroups operation. By attaching Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups to your scaling group, this operation enables Auto Scaling to automatically tailor your computing capacity to your business needs. Furthermore, it optimizes traffic routing by dynamically allocating incoming requests based on current workload patterns, which significantly improves the stability and performance of your application.
      *
      * @param request AttachServerGroupsRequest
      * @return AttachServerGroupsResponse
      */
     attachServerGroups(request: AttachServerGroupsRequest): Promise<AttachServerGroupsResponse>;
     /**
-     * @summary Associates Sever Load Balancer (SLB) vServer groups with a scaling group.
-     *
-     * @description Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
-     * *   The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
-     * *   The CLB instance and the scaling group must reside in the same region.
-     * *   The CLB instance must be in the Running state.
-     * *   The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
-     * *   The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
-     * *   If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the vServer groups of the CLB instance contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
-     * *   The vServer group that you want to attach to your scaling group must belong to the CLB instance.
-     * *   You can attach only a limited number of vServer groups to a scaling group. For information about the quota on vServer groups, see [Limits](https://help.aliyun.com/document_detail/25863.html).
-     * When you call this operation, you must specify the following parameters:
-     * *   LoadBalancerId: the ID of the CLB instance.
-     * *   VServerGroupId: the ID of the vServer group.
-     * *   Port: the port number of the vServer group.
-     * If a vServer group is attached to a scaling group by using different ports, Auto Scaling considers that more than one vServer group is attached to the scaling group. If multiple vServer groups with the same group ID and port number are specified in the request parameters, only the first vServer group is used. The other vServer groups are ignored.
+     * @summary Attaches vServer groups to a scaling group. After a Classic Load Balancer (CLB) instance is attached to your scaling group, the instances in the scaling group are automatically added as backend servers of the CLB instance. These servers then handle requests forwarded by the CLB instance, streamlining the processing of incoming traffic. To direct varying access requests to separate backend servers or to distribute requests based on domain names or URLs, you can call the AttachVServerGroups operation. This operation enables the addition of multiple vServer groups, allowing for efficient management of various backend server configurations tailored to your routing preferences.
+     *
+     * @description *   Before you call this operation, make sure that the following requirements are met:
+     *     *   The CLB instance and the scaling group belong to the same Alibaba Cloud account.
+     *     *   The CLB instance and the scaling group reside in the same region.
+     *     *   The CLB instance is in the Running state.
+     *     *   The CLB instance is configured with at least one listener. The health check feature is enabled for the CLB instance.
+     *     *   If the network type of both the CLB instance and the scaling group is virtual private cloud (VPC), they use the same VPC.
+     *     *   If the network type of the scaling group is VPC and the network type of the CLB instance is classic network, any backend server of the CLB instance within a VPC setup shares the same VPC as the scaling group.
+     *     *   The vServer groups that you want to attach to the scaling group belong to the CLB instance.
+     *     *   The operation to attach vServer groups does not result in the total number of vServer groups exceeding the predefined quota limit. For information about the vServer group quota, see [Limits](https://help.aliyun.com/document_detail/25863.html).
+     * *   When you call this operation to attach vServer groups, you must specify the following parameters:
+     *     *   LoadBalancerId: the ID of the CLB instance
+     *     *   VServerGroupId: the ID of the vServer group
+     *     *   Port: the port number of the vServer group
+     *     **
+     *     **Note** If you attempt to attach the same vServer group to a scaling group multiple times over the identical port, the system regards each attempt as a separate vServer group attachment to the scaling group. In your request, if you include the same vServer group ID coupled with the same port number multiple times, only the first configuration of the vServer group and port number pairing is considered valid. Subsequent vServer group and port number parings are disregarded.
      *
      * @param request AttachVServerGroupsRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8391,29 +8488,33 @@ export default class Client extends OpenApi {
      */
     attachVServerGroupsWithOptions(request: AttachVServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<AttachVServerGroupsResponse>;
     /**
-     * @summary Associates Sever Load Balancer (SLB) vServer groups with a scaling group.
-     *
-     * @description Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
-     * *   The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
-     * *   The CLB instance and the scaling group must reside in the same region.
-     * *   The CLB instance must be in the Running state.
-     * *   The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
-     * *   The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
-     * *   If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the vServer groups of the CLB instance contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
-     * *   The vServer group that you want to attach to your scaling group must belong to the CLB instance.
-     * *   You can attach only a limited number of vServer groups to a scaling group. For information about the quota on vServer groups, see [Limits](https://help.aliyun.com/document_detail/25863.html).
-     * When you call this operation, you must specify the following parameters:
-     * *   LoadBalancerId: the ID of the CLB instance.
-     * *   VServerGroupId: the ID of the vServer group.
-     * *   Port: the port number of the vServer group.
-     * If a vServer group is attached to a scaling group by using different ports, Auto Scaling considers that more than one vServer group is attached to the scaling group. If multiple vServer groups with the same group ID and port number are specified in the request parameters, only the first vServer group is used. The other vServer groups are ignored.
+     * @summary Attaches vServer groups to a scaling group. After a Classic Load Balancer (CLB) instance is attached to your scaling group, the instances in the scaling group are automatically added as backend servers of the CLB instance. These servers then handle requests forwarded by the CLB instance, streamlining the processing of incoming traffic. To direct varying access requests to separate backend servers or to distribute requests based on domain names or URLs, you can call the AttachVServerGroups operation. This operation enables the addition of multiple vServer groups, allowing for efficient management of various backend server configurations tailored to your routing preferences.
+     *
+     * @description *   Before you call this operation, make sure that the following requirements are met:
+     *     *   The CLB instance and the scaling group belong to the same Alibaba Cloud account.
+     *     *   The CLB instance and the scaling group reside in the same region.
+     *     *   The CLB instance is in the Running state.
+     *     *   The CLB instance is configured with at least one listener. The health check feature is enabled for the CLB instance.
+     *     *   If the network type of both the CLB instance and the scaling group is virtual private cloud (VPC), they use the same VPC.
+     *     *   If the network type of the scaling group is VPC and the network type of the CLB instance is classic network, any backend server of the CLB instance within a VPC setup shares the same VPC as the scaling group.
+     *     *   The vServer groups that you want to attach to the scaling group belong to the CLB instance.
+     *     *   The operation to attach vServer groups does not result in the total number of vServer groups exceeding the predefined quota limit. For information about the vServer group quota, see [Limits](https://help.aliyun.com/document_detail/25863.html).
+     * *   When you call this operation to attach vServer groups, you must specify the following parameters:
+     *     *   LoadBalancerId: the ID of the CLB instance
+     *     *   VServerGroupId: the ID of the vServer group
+     *     *   Port: the port number of the vServer group
+     *     **
+     *     **Note** If you attempt to attach the same vServer group to a scaling group multiple times over the identical port, the system regards each attempt as a separate vServer group attachment to the scaling group. In your request, if you include the same vServer group ID coupled with the same port number multiple times, only the first configuration of the vServer group and port number pairing is considered valid. Subsequent vServer group and port number parings are disregarded.
      *
      * @param request AttachVServerGroupsRequest
      * @return AttachVServerGroupsResponse
      */
     attachVServerGroups(request: AttachVServerGroupsRequest): Promise<AttachVServerGroupsResponse>;
     /**
-     * @summary Adds a scaling group to a resource group.
+     * @summary Changes a resource group. Resource groups are a means to categorize and manage cloud resources, such as scaling groups, based on specific objectives, permissions, or ownership. In large, multifaceted organizations that manage numerous projects and users, this feature adopts a tiered management approach, simplifying management tasks and improving the effectiveness and oversight of resource allocation. You can call the ChangeResourceGroup operation to move your scaling groups from one resource group to another resource group, which facilitates streamlined monitoring and management within the context of the new group. This operation eliminates the need for repetitive and time-consuming cross-service resource queries, thereby enhancing operational efficiency.
+     *
+     * @description *   A resource is an entity of cloud services that you create on Alibaba Cloud. For example, a scaling group is a resource.
+     * *   A resource group serves as a powerful organizational tool within your Alibaba Cloud account, enabling you to manage and monitor multiple resources collectively. It effectively addresses complexities surrounding resource categorization and permission control under a single Alibaba Cloud account, thereby enhancing management efficiency and control. For more information, see [What is resource management?](https://help.aliyun.com/document_detail/94475.html)
      *
      * @param request ChangeResourceGroupRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8421,7 +8522,10 @@ export default class Client extends OpenApi {
      */
     changeResourceGroupWithOptions(request: ChangeResourceGroupRequest, runtime: $Util.RuntimeOptions): Promise<ChangeResourceGroupResponse>;
     /**
-     * @summary Adds a scaling group to a resource group.
+     * @summary Changes a resource group. Resource groups are a means to categorize and manage cloud resources, such as scaling groups, based on specific objectives, permissions, or ownership. In large, multifaceted organizations that manage numerous projects and users, this feature adopts a tiered management approach, simplifying management tasks and improving the effectiveness and oversight of resource allocation. You can call the ChangeResourceGroup operation to move your scaling groups from one resource group to another resource group, which facilitates streamlined monitoring and management within the context of the new group. This operation eliminates the need for repetitive and time-consuming cross-service resource queries, thereby enhancing operational efficiency.
+     *
+     * @description *   A resource is an entity of cloud services that you create on Alibaba Cloud. For example, a scaling group is a resource.
+     * *   A resource group serves as a powerful organizational tool within your Alibaba Cloud account, enabling you to manage and monitor multiple resources collectively. It effectively addresses complexities surrounding resource categorization and permission control under a single Alibaba Cloud account, thereby enhancing management efficiency and control. For more information, see [What is resource management?](https://help.aliyun.com/document_detail/94475.html)
      *
      * @param request ChangeResourceGroupRequest
      * @return ChangeResourceGroupResponse
@@ -8447,13 +8551,13 @@ export default class Client extends OpenApi {
      */
     completeLifecycleAction(request: CompleteLifecycleActionRequest): Promise<CompleteLifecycleActionResponse>;
     /**
-     * @summary Creates an event-triggered task.
+     * @summary Creates event-triggered tasks. If your business encounters unexpected traffic surges or has no specific patterns, you can call the CreateAlarm operation to create an event-triggered task and associate a CloudMonitor metric with the task. This allows you to dynamically adjust the number of Elastic Compute Service (ECS) instances or elastic container instances in your scaling group and keep updated on the real-time metric data, which facilitates cloud resource management and maintenance.
      *
-     * @description *   If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
-     * *   When you create an event-triggered task, you must specify the MetricName, DimensionKey, and DimensionValue parameters to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances or elastic container instances in a scaling group within an Alibaba Cloud account.
-     *     *   If you set the MetricType parameter to custom, the valid values are your custom metrics.
-     *     *   For information about the supported metrics when you set the MetricType parameter to system, see [Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
-     * > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see the `DimensionKey` and `DimensionValue` parameters in the "Request parameters" section of this topic.
+     * @description *   If you set MetricType to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Event-triggered tasks of the custom monitoring type](https://help.aliyun.com/document_detail/74861.html).
+     * *   When you create an event-triggered task, you must specify MetricName, Dimensions.DimensionKey, and Dimensions.DimensionValue to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify user_id and scaling_group for an event-triggered task to aggregate monitoring data of all ECS instances or elastic container instances in a scaling group within an Alibaba Cloud account.
+     *     *   If you create an event-triggered task of the custom monitoring type, you can specify only custom metrics in the task.
+     *     *   If you create an event-triggered task of the system monitoring type, you can specify the system metrics described in [Event-triggered tasks of the system monitoring type](https://help.aliyun.com/document_detail/74854.html) in the task.
+     * >  user_id and scaling_group are automatically populated. You need to only specify device and state. For more information, see `Dimensions.DimensionKey` and `Dimensions.DimensionValue` in the "Request parameters" section of this topic.
      *
      * @param request CreateAlarmRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8461,13 +8565,13 @@ export default class Client extends OpenApi {
      */
     createAlarmWithOptions(request: CreateAlarmRequest, runtime: $Util.RuntimeOptions): Promise<CreateAlarmResponse>;
     /**
-     * @summary Creates an event-triggered task.
+     * @summary Creates event-triggered tasks. If your business encounters unexpected traffic surges or has no specific patterns, you can call the CreateAlarm operation to create an event-triggered task and associate a CloudMonitor metric with the task. This allows you to dynamically adjust the number of Elastic Compute Service (ECS) instances or elastic container instances in your scaling group and keep updated on the real-time metric data, which facilitates cloud resource management and maintenance.
      *
-     * @description *   If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
-     * *   When you create an event-triggered task, you must specify the MetricName, DimensionKey, and DimensionValue parameters to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances or elastic container instances in a scaling group within an Alibaba Cloud account.
-     *     *   If you set the MetricType parameter to custom, the valid values are your custom metrics.
-     *     *   For information about the supported metrics when you set the MetricType parameter to system, see [Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
-     * > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see the `DimensionKey` and `DimensionValue` parameters in the "Request parameters" section of this topic.
+     * @description *   If you set MetricType to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Event-triggered tasks of the custom monitoring type](https://help.aliyun.com/document_detail/74861.html).
+     * *   When you create an event-triggered task, you must specify MetricName, Dimensions.DimensionKey, and Dimensions.DimensionValue to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify user_id and scaling_group for an event-triggered task to aggregate monitoring data of all ECS instances or elastic container instances in a scaling group within an Alibaba Cloud account.
+     *     *   If you create an event-triggered task of the custom monitoring type, you can specify only custom metrics in the task.
+     *     *   If you create an event-triggered task of the system monitoring type, you can specify the system metrics described in [Event-triggered tasks of the system monitoring type](https://help.aliyun.com/document_detail/74854.html) in the task.
+     * >  user_id and scaling_group are automatically populated. You need to only specify device and state. For more information, see `Dimensions.DimensionKey` and `Dimensions.DimensionValue` in the "Request parameters" section of this topic.
      *
      * @param request CreateAlarmRequest
      * @return CreateAlarmResponse
@@ -8724,7 +8828,7 @@ export default class Client extends OpenApi {
      */
     deactivateScalingConfiguration(request: DeactivateScalingConfigurationRequest): Promise<DeactivateScalingConfigurationResponse>;
     /**
-     * @summary Deletes an event-triggered task.
+     * @summary Deletes an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you no longer need an event-triggered task, you can call the DeleteAlarm operation to delete it.
      *
      * @param request DeleteAlarmRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8732,18 +8836,18 @@ export default class Client extends OpenApi {
      */
     deleteAlarmWithOptions(request: DeleteAlarmRequest, runtime: $Util.RuntimeOptions): Promise<DeleteAlarmResponse>;
     /**
-     * @summary Deletes an event-triggered task.
+     * @summary Deletes an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you no longer need an event-triggered task, you can call the DeleteAlarm operation to delete it.
      *
      * @param request DeleteAlarmRequest
      * @return DeleteAlarmResponse
      */
     deleteAlarm(request: DeleteAlarmRequest): Promise<DeleteAlarmResponse>;
     /**
-     * @summary Deletes a scaling configuration that is used to create elastic container instances.
+     * @summary Deletes a scaling configuration of the Elastic Container Instance type. If the scaling configuration of a scaling group is in the Inactive state and the scaling group contains no elastic container instances created from the scaling configuration, you can call the DeleteEciScalingConfiguration operation to delete the scaling configuration to free up the scaling configuration quota.
      *
-     * @description You cannot delete a scaling configuration that is used to create elastic container instances in the following scenarios:
+     * @description You cannot call this operation to delete a scaling configuration in the following scenarios:
      * *   The scaling configuration is in the Active state.
-     * *   The scaling group contains elastic container instances that are created based on the scaling configuration.
+     * *   The scaling group contains elastic container instances created from the scaling configuration.
      *
      * @param request DeleteEciScalingConfigurationRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8751,11 +8855,11 @@ export default class Client extends OpenApi {
      */
     deleteEciScalingConfigurationWithOptions(request: DeleteEciScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeleteEciScalingConfigurationResponse>;
     /**
-     * @summary Deletes a scaling configuration that is used to create elastic container instances.
+     * @summary Deletes a scaling configuration of the Elastic Container Instance type. If the scaling configuration of a scaling group is in the Inactive state and the scaling group contains no elastic container instances created from the scaling configuration, you can call the DeleteEciScalingConfiguration operation to delete the scaling configuration to free up the scaling configuration quota.
      *
-     * @description You cannot delete a scaling configuration that is used to create elastic container instances in the following scenarios:
+     * @description You cannot call this operation to delete a scaling configuration in the following scenarios:
      * *   The scaling configuration is in the Active state.
-     * *   The scaling group contains elastic container instances that are created based on the scaling configuration.
+     * *   The scaling group contains elastic container instances created from the scaling configuration.
      *
      * @param request DeleteEciScalingConfigurationRequest
      * @return DeleteEciScalingConfigurationResponse
@@ -8785,7 +8889,7 @@ export default class Client extends OpenApi {
      */
     deleteLifecycleHook(request: DeleteLifecycleHookRequest): Promise<DeleteLifecycleHookResponse>;
     /**
-     * @summary Deletes a notification.
+     * @summary Deletes event notification rules. The event notification feature facilitates efficient issue identification and event management by automatically forwarding notifications from Auto Scaling to designated endpoints such as CloudMonitor or Message Service (MNS) topics and queues. If you no longer require an event notification rule, you can call the DeleteNotificationConfiguration operation to delete it.
      *
      * @param request DeleteNotificationConfigurationRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8793,7 +8897,7 @@ export default class Client extends OpenApi {
      */
     deleteNotificationConfigurationWithOptions(request: DeleteNotificationConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeleteNotificationConfigurationResponse>;
     /**
-     * @summary Deletes a notification.
+     * @summary Deletes event notification rules. The event notification feature facilitates efficient issue identification and event management by automatically forwarding notifications from Auto Scaling to designated endpoints such as CloudMonitor or Message Service (MNS) topics and queues. If you no longer require an event notification rule, you can call the DeleteNotificationConfiguration operation to delete it.
      *
      * @param request DeleteNotificationConfigurationRequest
      * @return DeleteNotificationConfigurationResponse
@@ -8823,11 +8927,18 @@ export default class Client extends OpenApi {
      */
     deleteScalingConfiguration(request: DeleteScalingConfigurationRequest): Promise<DeleteScalingConfigurationResponse>;
     /**
-     * @summary Deletes a scaling group.
+     * @summary Deletes a scaling group. If you want to enable policy-based automatic addition or removal of instances of a specific type to meet evolving business requirements, you can create scaling groups to manage your computing power with ease. The computing power refers to the instances that provide the computing capability. If you no longer require a scaling group, you can call the DeleteScalingGroup operation to delete it to free up the scaling group quota.
      *
-     * @description Before you delete a scaling group, take note of the following items:
-     * *   After you delete a scaling group, the scaling configuration, scaling rules, scaling activities, and scaling requests related to the scaling group are also deleted.
-     * *   After you delete a scaling group, the scheduled tasks and event-triggered tasks of the scaling group are not deleted. The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances with which the scaling group is associated are also not deleted.
+     * @description Before you call the DeleteScalingGroup operation, take note of the following items:
+     * *   If you delete a scaling group, the scaling configurations, scaling rules, scaling activities, and scaling requests related to the scaling group are also deleted.
+     * *   If you delete a scaling group, the scheduled tasks and event-triggered tasks of the scaling group are not deleted. The Server Load Balancer (SLB) instances and ApsaraDB RDS instances that are attached to the scaling group are also not deleted.
+     * *   If the scaling group that you want to delete contains ECS instances or elastic container instances that are in the In Service state, Auto Scaling stops the instances and then removes all manually added instances from the scaling group or releases all automatically created instances in the scaling group before the scaling group is deleted.
+     *     **
+     *     **Note** Before you delete a scaling group, make sure that the Deletion Protection feature is disabled. If you have enabled the Deletion Protection feature for a scaling group, disable the feature on the Modify Scaling Group page before you delete the scaling group.
+     * *   If you do not disable the Deletion Protection feature for a scaling group, you cannot delete the scaling group by using the Auto Scaling console or calling this operation. The Deletion Protection feature is an effective measure to safeguard scaling groups against unintended deletion.
+     * *   Prior to deleting a scaling group, make sure that your ECS instances within the scaling group are safeguarded against unintended release. Even if you have already enabled the Release Protection feature for the ECS instances, you must manually put these ECS instances into the Protected state. Doing so guarantees that the ECS instances will not be forcibly released during the deletion process of the scaling group, providing an extra layer of security.
+     *     **
+     *     **Note** Before you delete a scaling group, we recommend that you enable the Deletion Protection feature for ECS instances that you want to retain. This action guarantees that the ECS instances are not forcibly released after you delete the scaling group. For more information, see [SetInstancesProtection](https://help.aliyun.com/document_detail/459342.html).
      *
      * @param request DeleteScalingGroupRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8835,11 +8946,18 @@ export default class Client extends OpenApi {
      */
     deleteScalingGroupWithOptions(request: DeleteScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<DeleteScalingGroupResponse>;
     /**
-     * @summary Deletes a scaling group.
+     * @summary Deletes a scaling group. If you want to enable policy-based automatic addition or removal of instances of a specific type to meet evolving business requirements, you can create scaling groups to manage your computing power with ease. The computing power refers to the instances that provide the computing capability. If you no longer require a scaling group, you can call the DeleteScalingGroup operation to delete it to free up the scaling group quota.
      *
-     * @description Before you delete a scaling group, take note of the following items:
-     * *   After you delete a scaling group, the scaling configuration, scaling rules, scaling activities, and scaling requests related to the scaling group are also deleted.
-     * *   After you delete a scaling group, the scheduled tasks and event-triggered tasks of the scaling group are not deleted. The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances with which the scaling group is associated are also not deleted.
+     * @description Before you call the DeleteScalingGroup operation, take note of the following items:
+     * *   If you delete a scaling group, the scaling configurations, scaling rules, scaling activities, and scaling requests related to the scaling group are also deleted.
+     * *   If you delete a scaling group, the scheduled tasks and event-triggered tasks of the scaling group are not deleted. The Server Load Balancer (SLB) instances and ApsaraDB RDS instances that are attached to the scaling group are also not deleted.
+     * *   If the scaling group that you want to delete contains ECS instances or elastic container instances that are in the In Service state, Auto Scaling stops the instances and then removes all manually added instances from the scaling group or releases all automatically created instances in the scaling group before the scaling group is deleted.
+     *     **
+     *     **Note** Before you delete a scaling group, make sure that the Deletion Protection feature is disabled. If you have enabled the Deletion Protection feature for a scaling group, disable the feature on the Modify Scaling Group page before you delete the scaling group.
+     * *   If you do not disable the Deletion Protection feature for a scaling group, you cannot delete the scaling group by using the Auto Scaling console or calling this operation. The Deletion Protection feature is an effective measure to safeguard scaling groups against unintended deletion.
+     * *   Prior to deleting a scaling group, make sure that your ECS instances within the scaling group are safeguarded against unintended release. Even if you have already enabled the Release Protection feature for the ECS instances, you must manually put these ECS instances into the Protected state. Doing so guarantees that the ECS instances will not be forcibly released during the deletion process of the scaling group, providing an extra layer of security.
+     *     **
+     *     **Note** Before you delete a scaling group, we recommend that you enable the Deletion Protection feature for ECS instances that you want to retain. This action guarantees that the ECS instances are not forcibly released after you delete the scaling group. For more information, see [SetInstancesProtection](https://help.aliyun.com/document_detail/459342.html).
      *
      * @param request DeleteScalingGroupRequest
      * @return DeleteScalingGroupResponse
@@ -8861,7 +8979,7 @@ export default class Client extends OpenApi {
      */
     deleteScalingRule(request: DeleteScalingRuleRequest): Promise<DeleteScalingRuleResponse>;
     /**
-     * @summary Deletes a scheduled task.
+     * @summary Deletes scheduled tasks. For workloads with predictable patterns, you can create scheduled tasks to align with your business requirements and optimize resource utilization for cost savings. These tasks automatically ensure that sufficient computing resources are provisioned in anticipation of peak hours and efficiently release unused resources during off-peak hours, thereby streamlining operational efficiency and reducing expenses. If you no longer require a scheduled task, you can call the DeleteScheduledTask operation to delete it.
      *
      * @param request DeleteScheduledTaskRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8869,14 +8987,14 @@ export default class Client extends OpenApi {
      */
     deleteScheduledTaskWithOptions(request: DeleteScheduledTaskRequest, runtime: $Util.RuntimeOptions): Promise<DeleteScheduledTaskResponse>;
     /**
-     * @summary Deletes a scheduled task.
+     * @summary Deletes scheduled tasks. For workloads with predictable patterns, you can create scheduled tasks to align with your business requirements and optimize resource utilization for cost savings. These tasks automatically ensure that sufficient computing resources are provisioned in anticipation of peak hours and efficiently release unused resources during off-peak hours, thereby streamlining operational efficiency and reducing expenses. If you no longer require a scheduled task, you can call the DeleteScheduledTask operation to delete it.
      *
      * @param request DeleteScheduledTaskRequest
      * @return DeleteScheduledTaskResponse
      */
     deleteScheduledTask(request: DeleteScheduledTaskRequest): Promise<DeleteScheduledTaskResponse>;
     /**
-     * @summary Queries event-triggered tasks.
+     * @summary Queries event-triggered tasks. You can call the DescribeAlarms operation to learn about the configurations of event-triggered tasks and keep updated on monitoring data changes. This helps you troubleshoot system resource issues at the earliest opportunity and ensures system stability and reliability.
      *
      * @param request DescribeAlarmsRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -8884,7 +9002,7 @@ export default class Client extends OpenApi {
      */
     describeAlarmsWithOptions(request: DescribeAlarmsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeAlarmsResponse>;
     /**
-     * @summary Queries event-triggered tasks.
+     * @summary Queries event-triggered tasks. You can call the DescribeAlarms operation to learn about the configurations of event-triggered tasks and keep updated on monitoring data changes. This helps you troubleshoot system resource issues at the earliest opportunity and ensures system stability and reliability.
      *
      * @param request DescribeAlarmsRequest
      * @return DescribeAlarmsResponse
@@ -9018,7 +9136,7 @@ export default class Client extends OpenApi {
      */
     describeNotificationTypes(request: DescribeNotificationTypesRequest): Promise<DescribeNotificationTypesResponse>;
     /**
-     * @summary DescribePatternTypes
+     * @summary Filters instance types that meet your business requirements. If you create a scaling configuration by opting for the Specify Instance Type approach, you can call the DescribePatternTypes operation. This operation is designed to sift through and identify instance types that fulfill your specific business needs. It does so by examining the number of vCPUs, memory size, instance family level, and maximum budgeted expense that you specify within the scaling configuration settings.
      *
      * @param request DescribePatternTypesRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9026,14 +9144,14 @@ export default class Client extends OpenApi {
      */
     describePatternTypesWithOptions(request: DescribePatternTypesRequest, runtime: $Util.RuntimeOptions): Promise<DescribePatternTypesResponse>;
     /**
-     * @summary DescribePatternTypes
+     * @summary Filters instance types that meet your business requirements. If you create a scaling configuration by opting for the Specify Instance Type approach, you can call the DescribePatternTypes operation. This operation is designed to sift through and identify instance types that fulfill your specific business needs. It does so by examining the number of vCPUs, memory size, instance family level, and maximum budgeted expense that you specify within the scaling configuration settings.
      *
      * @param request DescribePatternTypesRequest
      * @return DescribePatternTypesResponse
      */
     describePatternTypes(request: DescribePatternTypesRequest): Promise<DescribePatternTypesResponse>;
     /**
-     * @summary Queries the regions in which Auto Scaling is available.
+     * @summary Queries regions. Before you activate Auto Scaling, you can call the DescribeRegions operation to query the regions where Auto Scaling is officially launched. This preliminary step facilitates the strategic selection of both the optimal region and availability zones for activating Auto Scaling, thereby guaranteeing the finest access speeds and operational efficiency within your chosen geographical area.
      *
      * @param request DescribeRegionsRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9041,7 +9159,7 @@ export default class Client extends OpenApi {
      */
     describeRegionsWithOptions(request: DescribeRegionsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeRegionsResponse>;
     /**
-     * @summary Queries the regions in which Auto Scaling is available.
+     * @summary Queries regions. Before you activate Auto Scaling, you can call the DescribeRegions operation to query the regions where Auto Scaling is officially launched. This preliminary step facilitates the strategic selection of both the optimal region and availability zones for activating Auto Scaling, thereby guaranteeing the finest access speeds and operational efficiency within your chosen geographical area.
      *
      * @param request DescribeRegionsRequest
      * @return DescribeRegionsResponse
@@ -9101,7 +9219,7 @@ export default class Client extends OpenApi {
      */
     describeScalingConfigurations(request: DescribeScalingConfigurationsRequest): Promise<DescribeScalingConfigurationsResponse>;
     /**
-     * @summary Queries a scaling group. You can call the DescribeScalingGroupDetail operation to query the basic information, instances, and scaling configurations of a scaling group. If you set OutputFormat to yaml, a Kubernetes Deployment file that is in the YAML format is returned.
+     * @summary Queries a scaling group. You can call the DescribeScalingGroupDetail operation to query the basic information, instances, and scaling configurations of a scaling group. If you set OutputFormat to yaml, the output is a Kubernetes Deployment file in the YAML format.
      *
      * @param request DescribeScalingGroupDetailRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9109,7 +9227,7 @@ export default class Client extends OpenApi {
      */
     describeScalingGroupDetailWithOptions(request: DescribeScalingGroupDetailRequest, runtime: $Util.RuntimeOptions): Promise<DescribeScalingGroupDetailResponse>;
     /**
-     * @summary Queries a scaling group. You can call the DescribeScalingGroupDetail operation to query the basic information, instances, and scaling configurations of a scaling group. If you set OutputFormat to yaml, a Kubernetes Deployment file that is in the YAML format is returned.
+     * @summary Queries a scaling group. You can call the DescribeScalingGroupDetail operation to query the basic information, instances, and scaling configurations of a scaling group. If you set OutputFormat to yaml, the output is a Kubernetes Deployment file in the YAML format.
      *
      * @param request DescribeScalingGroupDetailRequest
      * @return DescribeScalingGroupDetailResponse
@@ -9262,7 +9380,7 @@ export default class Client extends OpenApi {
      */
     detachLoadBalancers(request: DetachLoadBalancersRequest): Promise<DetachLoadBalancersResponse>;
     /**
-     * @summary Detaches one or more server groups from a scaling group. You can attach and detach the following server groups from a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
+     * @summary Detach server groups from a scaling group. To seamlessly adjust the number of instances in response to changes in your business workload or to maintain the uninterrupted accessibility of your application, you can call the DetachServerGroups operation. By detaching Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups from your scaling group, this operation enables Auto Scaling to automatically tailor your computing capacity to your business needs. Furthermore, it optimizes traffic routing by dynamically allocating incoming requests based on current workload patterns, which significantly improves the stability and performance of your application.
      *
      * @param request DetachServerGroupsRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9270,7 +9388,7 @@ export default class Client extends OpenApi {
      */
     detachServerGroupsWithOptions(request: DetachServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DetachServerGroupsResponse>;
     /**
-     * @summary Detaches one or more server groups from a scaling group. You can attach and detach the following server groups from a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
+     * @summary Detach server groups from a scaling group. To seamlessly adjust the number of instances in response to changes in your business workload or to maintain the uninterrupted accessibility of your application, you can call the DetachServerGroups operation. By detaching Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups from your scaling group, this operation enables Auto Scaling to automatically tailor your computing capacity to your business needs. Furthermore, it optimizes traffic routing by dynamically allocating incoming requests based on current workload patterns, which significantly improves the stability and performance of your application.
      *
      * @param request DetachServerGroupsRequest
      * @return DetachServerGroupsResponse
@@ -9306,7 +9424,9 @@ export default class Client extends OpenApi {
      */
     detachVServerGroups(request: DetachVServerGroupsRequest): Promise<DetachVServerGroupsResponse>;
     /**
-     * @summary Disables an event-triggered task.
+     * @summary Disables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you currently do not need an event-triggered task, you can call the DisableAlarm operation to disable it.
+     *
+     * @description Before you disable an event-triggered task, make sure that the task is in the `Normal`, `Alert`, or `Insufficient Data` state.
      *
      * @param request DisableAlarmRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9314,18 +9434,20 @@ export default class Client extends OpenApi {
      */
     disableAlarmWithOptions(request: DisableAlarmRequest, runtime: $Util.RuntimeOptions): Promise<DisableAlarmResponse>;
     /**
-     * @summary Disables an event-triggered task.
+     * @summary Disables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you currently do not need an event-triggered task, you can call the DisableAlarm operation to disable it.
+     *
+     * @description Before you disable an event-triggered task, make sure that the task is in the `Normal`, `Alert`, or `Insufficient Data` state.
      *
      * @param request DisableAlarmRequest
      * @return DisableAlarmResponse
      */
     disableAlarm(request: DisableAlarmRequest): Promise<DisableAlarmResponse>;
     /**
-     * @summary Disables a scaling group.
+     * @summary Disables a scaling group. If you temporarily do not require a scaling group that is in the Enabled state, you can call the DisableScalingGroup operation to disable it.
      *
      * @description Before you call this operation to disable a scaling group, take note of the following items:
-     * *   When you call this operation, ongoing scaling activities will continue until they are complete, but new activities will be rejected.
-     * *   You can disable only scaling groups that are in the Active state.
+     * *   If scaling activities are being executed in the specified scaling group when you call this operation, these activities will continue until they are complete. However, scaling activities that are triggered after this operation is called will be rejected.
+     * *   This operation can be called only when the scaling group is in the Active state.
      *
      * @param request DisableScalingGroupRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9333,18 +9455,18 @@ export default class Client extends OpenApi {
      */
     disableScalingGroupWithOptions(request: DisableScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<DisableScalingGroupResponse>;
     /**
-     * @summary Disables a scaling group.
+     * @summary Disables a scaling group. If you temporarily do not require a scaling group that is in the Enabled state, you can call the DisableScalingGroup operation to disable it.
      *
      * @description Before you call this operation to disable a scaling group, take note of the following items:
-     * *   When you call this operation, ongoing scaling activities will continue until they are complete, but new activities will be rejected.
-     * *   You can disable only scaling groups that are in the Active state.
+     * *   If scaling activities are being executed in the specified scaling group when you call this operation, these activities will continue until they are complete. However, scaling activities that are triggered after this operation is called will be rejected.
+     * *   This operation can be called only when the scaling group is in the Active state.
      *
      * @param request DisableScalingGroupRequest
      * @return DisableScalingGroupResponse
      */
     disableScalingGroup(request: DisableScalingGroupRequest): Promise<DisableScalingGroupResponse>;
     /**
-     * @summary Enables an event-triggered task.
+     * @summary Enables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you want to reuse an event-triggered task that is in the Disabled state, you can call the EnableAlarm operation to enable it.
      *
      * @param request EnableAlarmRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9352,20 +9474,21 @@ export default class Client extends OpenApi {
      */
     enableAlarmWithOptions(request: EnableAlarmRequest, runtime: $Util.RuntimeOptions): Promise<EnableAlarmResponse>;
     /**
-     * @summary Enables an event-triggered task.
+     * @summary Enables an event-triggered task. If your business pattern is unpredictable or prone to unforeseen traffic spikes, you can create event-triggered tasks by associating CloudMonitor metrics to effectively monitor fluctuations in your business workload. Upon detecting that the criteria for alerts, as specified in event-triggered tasks, are fulfilled, Auto Scaling promptly issues alerts and executes the scaling rules predefined within those tasks. This process occurs within the predefined effective time windows of the tasks, thereby facilitating the automatic increase or decrease of Elastic Compute Service (ECS) instances or elastic container instances within your scaling groups. Ultimately, this mechanism ensures the dynamic optimization of resources based on real-time workload demands. If you want to reuse an event-triggered task that is in the Disabled state, you can call the EnableAlarm operation to enable it.
      *
      * @param request EnableAlarmRequest
      * @return EnableAlarmResponse
      */
     enableAlarm(request: EnableAlarmRequest): Promise<EnableAlarmResponse>;
     /**
-     * @summary Enables a scaling group.
+     * @summary Enables a scaling group. If a scaling group is in the Disabled state and contains an instance configuration source such as a launch template or a scaling configuration, you can call the EnableScalingGroup operation to enable the scaling group. This operation permits Auto Scaling to dynamically adjust the computing power (also known as the number of instances) in the scaling group based on your business requirements.
      *
-     * @description You can call this operation to enable a scaling group that is in the Inactive state and has an instance configuration source. The instance configuration source can be a scaling configuration, a launch template, or an Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If a scaling group is not in the Inactive state or does not have an active instance configuration source, you cannot call this operation to enable the scaling group.
-     * > A scaling group can have only one active instance configuration source. When you call this operation to enable a scaling group, you can specify a scaling configuration or a launch template for the scaling group. If an instance configuration source has been configured for the scaling group before you call this operation, the scaling configuration or launch template that you specify in the request overwrites the original scaling configuration or launch template.
-     * If you specify a value for the InstanceId parameter when you call the operation, Auto Scaling checks whether the total number of ECS instances is within the range allowed in the scaling group after you call the operation.
-     * *   If the total number of ECS instances is less than the minimum number of instances allowed in the scaling group after you call the operation, Auto Scaling automatically creates the required number of pay-as-you-go ECS instances and adds the instances to the scaling group to reach the minimum number. For example, if the minimum number of instances allowed in your scaling group is five, and you specify the InstanceId parameter to add two created ECS instances to the scaling group, Auto Scaling automatically creates three instances in the scaling group after the two instances are added.
-     * *   If the value of the TotalCapactiy parameter is greater than the value of the MaxSize parameter, the call fails.
+     * @description *   You can call this operation to enable a scaling group only if the scaling group is in the Inactive state and contains an instance configuration source such as a launch temple or a scaling configuration. The instance configuration source can also be the Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If the preceding requirements are not met, the operation will fail.
+     *     **
+     *     **Note** A scaling group can have only one active instance configuration source at a time. When you call this operation to enable a scaling group, you can specify a scaling configuration or a launch template for the scaling group. If the scaling group already have an instance configuration source defined prior to your calling, the scaling configuration or launch template specified within your request will supersede the existing scaling configuration or launch template.
+     * *   If you specify InstanceId.N to add to the scaling group within your request, Auto Scaling will check whether the addition of InstanceId.N will cause the total number of ECS instances in the scaling group to fall outside the boundaries specified by MinSize and MaxSize after you call this operation.
+     *     *   If the call results in the total number of ECS instances dropping below the value of MinSize, Auto Scaling proactively creates pay-as-you-go ECS instances to ensure that the total number reaches the minimum threshold. For example, if you set MinSize to 5 when you created a scaling group and include InstanceId.N within your request to add two ECS instances when you attempt to enable the scaling group, Auto Scaling creates three more ECS instances in the scaling group after the two ECS instances are added.
+     *     *   If the call results in the total number of ECS instances exceeding the value of MaxSize, the operation fails.
      *
      * @param request EnableScalingGroupRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9373,13 +9496,14 @@ export default class Client extends OpenApi {
      */
     enableScalingGroupWithOptions(request: EnableScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<EnableScalingGroupResponse>;
     /**
-     * @summary Enables a scaling group.
+     * @summary Enables a scaling group. If a scaling group is in the Disabled state and contains an instance configuration source such as a launch template or a scaling configuration, you can call the EnableScalingGroup operation to enable the scaling group. This operation permits Auto Scaling to dynamically adjust the computing power (also known as the number of instances) in the scaling group based on your business requirements.
      *
-     * @description You can call this operation to enable a scaling group that is in the Inactive state and has an instance configuration source. The instance configuration source can be a scaling configuration, a launch template, or an Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If a scaling group is not in the Inactive state or does not have an active instance configuration source, you cannot call this operation to enable the scaling group.
-     * > A scaling group can have only one active instance configuration source. When you call this operation to enable a scaling group, you can specify a scaling configuration or a launch template for the scaling group. If an instance configuration source has been configured for the scaling group before you call this operation, the scaling configuration or launch template that you specify in the request overwrites the original scaling configuration or launch template.
-     * If you specify a value for the InstanceId parameter when you call the operation, Auto Scaling checks whether the total number of ECS instances is within the range allowed in the scaling group after you call the operation.
-     * *   If the total number of ECS instances is less than the minimum number of instances allowed in the scaling group after you call the operation, Auto Scaling automatically creates the required number of pay-as-you-go ECS instances and adds the instances to the scaling group to reach the minimum number. For example, if the minimum number of instances allowed in your scaling group is five, and you specify the InstanceId parameter to add two created ECS instances to the scaling group, Auto Scaling automatically creates three instances in the scaling group after the two instances are added.
-     * *   If the value of the TotalCapactiy parameter is greater than the value of the MaxSize parameter, the call fails.
+     * @description *   You can call this operation to enable a scaling group only if the scaling group is in the Inactive state and contains an instance configuration source such as a launch temple or a scaling configuration. The instance configuration source can also be the Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If the preceding requirements are not met, the operation will fail.
+     *     **
+     *     **Note** A scaling group can have only one active instance configuration source at a time. When you call this operation to enable a scaling group, you can specify a scaling configuration or a launch template for the scaling group. If the scaling group already have an instance configuration source defined prior to your calling, the scaling configuration or launch template specified within your request will supersede the existing scaling configuration or launch template.
+     * *   If you specify InstanceId.N to add to the scaling group within your request, Auto Scaling will check whether the addition of InstanceId.N will cause the total number of ECS instances in the scaling group to fall outside the boundaries specified by MinSize and MaxSize after you call this operation.
+     *     *   If the call results in the total number of ECS instances dropping below the value of MinSize, Auto Scaling proactively creates pay-as-you-go ECS instances to ensure that the total number reaches the minimum threshold. For example, if you set MinSize to 5 when you created a scaling group and include InstanceId.N within your request to add two ECS instances when you attempt to enable the scaling group, Auto Scaling creates three more ECS instances in the scaling group after the two ECS instances are added.
+     *     *   If the call results in the total number of ECS instances exceeding the value of MaxSize, the operation fails.
      *
      * @param request EnableScalingGroupRequest
      * @return EnableScalingGroupResponse
@@ -9482,7 +9606,10 @@ export default class Client extends OpenApi {
      */
     listTagKeys(request: ListTagKeysRequest): Promise<ListTagKeysResponse>;
     /**
-     * @summary Queries tags that are added to one or more Auto Scaling resources.
+     * @summary Queries tags. You can call the ListTagResources operation to query tags that are added to Auto Scaling resources, thereby clarifying resource utilization and facilitating efficient management. This operation aids in the automation of resource categorization and permission management processes.
+     *
+     * @description *   Specify at least one of the following request parameters: `ResourceIds` and `Tags`. `Tags.Key` and `Tags.Value` are used to specify the query objects.
+     * *   If you provide both `ResourceIds` and `Tags` in your request, the response will exclusively include Auto Scaling resources that satisfy the criteria set by these parameters, ensuring targeted and precise information retrieval.
      *
      * @param request ListTagResourcesRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9490,14 +9617,17 @@ export default class Client extends OpenApi {
      */
     listTagResourcesWithOptions(request: ListTagResourcesRequest, runtime: $Util.RuntimeOptions): Promise<ListTagResourcesResponse>;
     /**
-     * @summary Queries tags that are added to one or more Auto Scaling resources.
+     * @summary Queries tags. You can call the ListTagResources operation to query tags that are added to Auto Scaling resources, thereby clarifying resource utilization and facilitating efficient management. This operation aids in the automation of resource categorization and permission management processes.
+     *
+     * @description *   Specify at least one of the following request parameters: `ResourceIds` and `Tags`. `Tags.Key` and `Tags.Value` are used to specify the query objects.
+     * *   If you provide both `ResourceIds` and `Tags` in your request, the response will exclusively include Auto Scaling resources that satisfy the criteria set by these parameters, ensuring targeted and precise information retrieval.
      *
      * @param request ListTagResourcesRequest
      * @return ListTagResourcesResponse
      */
     listTagResources(request: ListTagResourcesRequest): Promise<ListTagResourcesResponse>;
     /**
-     * @summary Queries tag values.
+     * @summary Queries the tag keys associated with Auto Scaling resources to facilitate a deeper comprehension of those resources. By doing so, you can categorize and manage your Auto Scaling resources more efficiently.
      *
      * @param request ListTagValuesRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9505,7 +9635,7 @@ export default class Client extends OpenApi {
      */
     listTagValuesWithOptions(request: ListTagValuesRequest, runtime: $Util.RuntimeOptions): Promise<ListTagValuesResponse>;
     /**
-     * @summary Queries tag values.
+     * @summary Queries the tag keys associated with Auto Scaling resources to facilitate a deeper comprehension of those resources. By doing so, you can categorize and manage your Auto Scaling resources more efficiently.
      *
      * @param request ListTagValuesRequest
      * @return ListTagValuesResponse
@@ -9630,19 +9760,21 @@ export default class Client extends OpenApi {
      */
     modifyScalingConfiguration(request: ModifyScalingConfigurationRequest): Promise<ModifyScalingConfigurationResponse>;
     /**
-     * @summary Modifies a scaling group.
+     * @summary Modifies a scaling group. If you want to enable policy-based automatic addition or removal of instances of a specific type to meet evolving business requirements, you can modify scaling groups to adjust your computing power with ease. The computing power refers to the instances that provide the computing capability. When your scaling group cannot meet your business requirements, you can call the ModifyScalingGroup operation to modify scaling group attributes such as the maximum, minimum, and expected numbers of instances. This prevents repeated creation and configuration of scaling groups, which saves you a lot of time and resource costs.
      *
-     * @description *   You cannot call this operation to modify the settings of the following parameters:
+     * @description *   You cannot modify the following parameters by calling this operation:
      *     *   RegionId
      *     *   LoadBalancerId
-     *     > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
+     *     **
+     *     **Note** If you want to modify the load balancer settings of your scaling group, you can call the AttachLoadBalancers operation or the DetachLoadBalancers operation.
      *     *   DBInstanceId
-     *     > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
-     * *   You can modify only scaling groups that are in the Active or Inactive state.
-     * *   If you enable a new scaling configuration, Elastic Compute Service (ECS) instances that are created based on the previous scaling configuration still run as expected in the scaling group.
-     * *   If the total number of instances in the scaling group is greater than the allowed maximum number after you change the value of the MaxSize parameter, Auto Scaling automatically removes instances from the scaling group to ensure that the number of instances is within the new range.
-     * *   If the total number of instances in the scaling group is less than the allowed minimum number after you change the value of the MinSize parameter, Auto Scaling automatically adds instances to the scaling group to ensure that the number of instances is within the new range.
-     * *   If the total number of instances in the scaling group does not match the expected number of instances after you change the value of the DesiredCapacity parameter, Auto Scaling automatically adds instances to or removes instances from the scaling group to ensure that the number of instances matches the value of the DesiredCapacity parameter.
+     *     **
+     *     **Note** If you want to modify the ApsaraDB RDS instance settings of your scaling group, you can call the AttachDBInstances operation or the DetachDBInstances operation.
+     * *   You can call this operation to modify a scaling group only when the scaling group is in the `Active` or `Inactive` state.
+     * *   Enabling a new scaling configuration in the scaling group will not impact existing Elastic Compute Service (ECS) instances or elastic container instances that were provisioned based on the previous scaling configuration. These instances will continue to run as expected.
+     * *   If the modification of the MaxSize setting leads to the total number of ECS instances or elastic container instances in the scaling group exceeding the new maximum limit, Auto Scaling proactively removes the surplus instances to restore the total number to match the new maximum limit.
+     * *   If the modification of the MinSize setting leads to the total number of ECS instances or elastic container instances in the scaling group exceeding the new minimum threshold, Auto Scaling proactively adds more instances to the scaling group to ensure that the total number aligns with the new minimum threshold.
+     * *   If the modification of the DesiredCapacity setting leads to the total number of ECS instances or elastic container instances in the scaling group not matching the new desired capacity, Auto Scaling proactively adjusts the total number of instances to ensure that the total number aligns with the new desired capacity.
      *
      * @param request ModifyScalingGroupRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9650,19 +9782,21 @@ export default class Client extends OpenApi {
      */
     modifyScalingGroupWithOptions(request: ModifyScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<ModifyScalingGroupResponse>;
     /**
-     * @summary Modifies a scaling group.
+     * @summary Modifies a scaling group. If you want to enable policy-based automatic addition or removal of instances of a specific type to meet evolving business requirements, you can modify scaling groups to adjust your computing power with ease. The computing power refers to the instances that provide the computing capability. When your scaling group cannot meet your business requirements, you can call the ModifyScalingGroup operation to modify scaling group attributes such as the maximum, minimum, and expected numbers of instances. This prevents repeated creation and configuration of scaling groups, which saves you a lot of time and resource costs.
      *
-     * @description *   You cannot call this operation to modify the settings of the following parameters:
+     * @description *   You cannot modify the following parameters by calling this operation:
      *     *   RegionId
      *     *   LoadBalancerId
-     *     > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
+     *     **
+     *     **Note** If you want to modify the load balancer settings of your scaling group, you can call the AttachLoadBalancers operation or the DetachLoadBalancers operation.
      *     *   DBInstanceId
-     *     > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
-     * *   You can modify only scaling groups that are in the Active or Inactive state.
-     * *   If you enable a new scaling configuration, Elastic Compute Service (ECS) instances that are created based on the previous scaling configuration still run as expected in the scaling group.
-     * *   If the total number of instances in the scaling group is greater than the allowed maximum number after you change the value of the MaxSize parameter, Auto Scaling automatically removes instances from the scaling group to ensure that the number of instances is within the new range.
-     * *   If the total number of instances in the scaling group is less than the allowed minimum number after you change the value of the MinSize parameter, Auto Scaling automatically adds instances to the scaling group to ensure that the number of instances is within the new range.
-     * *   If the total number of instances in the scaling group does not match the expected number of instances after you change the value of the DesiredCapacity parameter, Auto Scaling automatically adds instances to or removes instances from the scaling group to ensure that the number of instances matches the value of the DesiredCapacity parameter.
+     *     **
+     *     **Note** If you want to modify the ApsaraDB RDS instance settings of your scaling group, you can call the AttachDBInstances operation or the DetachDBInstances operation.
+     * *   You can call this operation to modify a scaling group only when the scaling group is in the `Active` or `Inactive` state.
+     * *   Enabling a new scaling configuration in the scaling group will not impact existing Elastic Compute Service (ECS) instances or elastic container instances that were provisioned based on the previous scaling configuration. These instances will continue to run as expected.
+     * *   If the modification of the MaxSize setting leads to the total number of ECS instances or elastic container instances in the scaling group exceeding the new maximum limit, Auto Scaling proactively removes the surplus instances to restore the total number to match the new maximum limit.
+     * *   If the modification of the MinSize setting leads to the total number of ECS instances or elastic container instances in the scaling group exceeding the new minimum threshold, Auto Scaling proactively adds more instances to the scaling group to ensure that the total number aligns with the new minimum threshold.
+     * *   If the modification of the DesiredCapacity setting leads to the total number of ECS instances or elastic container instances in the scaling group not matching the new desired capacity, Auto Scaling proactively adjusts the total number of instances to ensure that the total number aligns with the new desired capacity.
      *
      * @param request ModifyScalingGroupRequest
      * @return ModifyScalingGroupResponse
@@ -9807,16 +9941,15 @@ export default class Client extends OpenApi {
      */
     resumeProcesses(request: ResumeProcessesRequest): Promise<ResumeProcessesResponse>;
     /**
-     * @summary Scales instances in a scaling group based on the specified scaling policy.
+     * @summary Scales instances. The ScaleWithAdjustment operation differs from the ExecuteScalingRule operation in that ScaleWithAdjust can directly scale instances without requiring you to create a scaling rule in advance.
      *
-     * @description Compared with the ExecuteScalingRule operation, the ScaleWithAdjustment operation does not require a scaling rule to be created in advance. Before you call the ScaleWithAdjustment operation, take note of the following items:
-     * *   The following conditions must be met:
+     * @description *   Before you call this operation, take note of the following items:
      *     *   The scaling group is in the Active state.
-     *     *   No scaling activities in the scaling group are in progress.
-     * *   If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
-     * *   If the addition of a specified number of Elastic Compute Service (ECS) instances to a scaling group causes the total number of ECS instances in the scaling group to exceed the maximum number of instances allowed, Auto Scaling adds only a specific number of ECS instances to ensure that the total number of instances is equal to the maximum number of instances.
-     * *   If the removal of a specified number of ECS instances from a scaling group causes the total number of ECS instances in the scaling group to drop below the minimum number of instances allowed, Auto Scaling removes only a specific number of ECS instances to ensure that the total number of instances is equal to the minimum number of instances.
-     * A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the `ScalingActivityId` parameter in the response.
+     *     *   The scaling group has no ongoing scaling activities.
+     * *   If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities before the cooldown period of the scaling group expires.
+     * *   If the addition of a specific number of Elastic Compute Service (ECS) instances to the scaling group causes the total number of ECS instances in the scaling group to exceed the maximum allowed number, Auto Scaling adds ECS instances to the scaling group until the total number of instances is equal to the maximum allowed number.
+     * *   If the removal of a specific number of ECS instances from the scaling group causes the total number of ECS instances in the scaling group to be less than the minimum allowed number, Auto Scaling removes ECS instances from the scaling group until the total number of instances is equal to the minimum allowed number.
+     * A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity based on the value of `ScalingActivityId` in the response.
      *
      * @param tmpReq ScaleWithAdjustmentRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9824,16 +9957,15 @@ export default class Client extends OpenApi {
      */
     scaleWithAdjustmentWithOptions(tmpReq: ScaleWithAdjustmentRequest, runtime: $Util.RuntimeOptions): Promise<ScaleWithAdjustmentResponse>;
     /**
-     * @summary Scales instances in a scaling group based on the specified scaling policy.
+     * @summary Scales instances. The ScaleWithAdjustment operation differs from the ExecuteScalingRule operation in that ScaleWithAdjust can directly scale instances without requiring you to create a scaling rule in advance.
      *
-     * @description Compared with the ExecuteScalingRule operation, the ScaleWithAdjustment operation does not require a scaling rule to be created in advance. Before you call the ScaleWithAdjustment operation, take note of the following items:
-     * *   The following conditions must be met:
+     * @description *   Before you call this operation, take note of the following items:
      *     *   The scaling group is in the Active state.
-     *     *   No scaling activities in the scaling group are in progress.
-     * *   If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
-     * *   If the addition of a specified number of Elastic Compute Service (ECS) instances to a scaling group causes the total number of ECS instances in the scaling group to exceed the maximum number of instances allowed, Auto Scaling adds only a specific number of ECS instances to ensure that the total number of instances is equal to the maximum number of instances.
-     * *   If the removal of a specified number of ECS instances from a scaling group causes the total number of ECS instances in the scaling group to drop below the minimum number of instances allowed, Auto Scaling removes only a specific number of ECS instances to ensure that the total number of instances is equal to the minimum number of instances.
-     * A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the `ScalingActivityId` parameter in the response.
+     *     *   The scaling group has no ongoing scaling activities.
+     * *   If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities before the cooldown period of the scaling group expires.
+     * *   If the addition of a specific number of Elastic Compute Service (ECS) instances to the scaling group causes the total number of ECS instances in the scaling group to exceed the maximum allowed number, Auto Scaling adds ECS instances to the scaling group until the total number of instances is equal to the maximum allowed number.
+     * *   If the removal of a specific number of ECS instances from the scaling group causes the total number of ECS instances in the scaling group to be less than the minimum allowed number, Auto Scaling removes ECS instances from the scaling group until the total number of instances is equal to the minimum allowed number.
+     * A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity based on the value of `ScalingActivityId` in the response.
      *
      * @param request ScaleWithAdjustmentRequest
      * @return ScaleWithAdjustmentResponse
@@ -9874,13 +10006,12 @@ export default class Client extends OpenApi {
      */
     setInstanceHealth(request: SetInstanceHealthRequest): Promise<SetInstanceHealthResponse>;
     /**
-     * @summary Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
+     * @summary Puts Elastic Compute Service (ECS) instances into the Protected state. When ECS instances are put into the Protected state, they become immune to manual deletion attempts by using the Auto Scaling console or API operations. This operation serves as a robust safeguard, efficiently preventing any inadvertent instance release that could lead to irreversible consequences.
      *
-     * @description ## Description
-     * Before you call this operation, take note of the following items:
-     * *   After you put an ECS instance into the Protected state, the ECS instance remains in the Protected state until you manually move the ECS instance out of the Protected state.
-     * *   After you put an ECS instance into the Protected state, Auto Scaling does not remove the ECS instance even if a scale-in activity caused by changes in instance quantity or event-triggered tasks occurs. In this case, you must manually move the ECS instance out of the Protected state and then release the ECS instance. For more information, see the "RemoveInstances" topic.
-     * *   After you put an ECS instance into the Protected state, Auto Scaling does not update the health status of the instance when the instance is stopped or restarted.
+     * @description Once ECS instances enter the Protected state, they become subject to the following restrictions:
+     * *   ECS instances will persist in the Protected state, unless you deliberately remove them from this state.
+     * *   Even in scenarios where automatic scale-in actions are initiated due to fluctuations in the number of ECS instances or the execution of event-triggered tasks, Auto Scaling does not remove ECS instances that are in the Protected state from their respective scaling groups. Only after being manually removed from their respective scaling groups can ECS instances that are in the Protected state be released. For more information, see [Remove an ECS instance](https://help.aliyun.com/document_detail/25955.html).
+     * *   ECS instances in the Protected state maintain their existing health status even when they undergo stopping or restarting processes.
      *
      * @param request SetInstancesProtectionRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9888,20 +10019,19 @@ export default class Client extends OpenApi {
      */
     setInstancesProtectionWithOptions(request: SetInstancesProtectionRequest, runtime: $Util.RuntimeOptions): Promise<SetInstancesProtectionResponse>;
     /**
-     * @summary Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
+     * @summary Puts Elastic Compute Service (ECS) instances into the Protected state. When ECS instances are put into the Protected state, they become immune to manual deletion attempts by using the Auto Scaling console or API operations. This operation serves as a robust safeguard, efficiently preventing any inadvertent instance release that could lead to irreversible consequences.
      *
-     * @description ## Description
-     * Before you call this operation, take note of the following items:
-     * *   After you put an ECS instance into the Protected state, the ECS instance remains in the Protected state until you manually move the ECS instance out of the Protected state.
-     * *   After you put an ECS instance into the Protected state, Auto Scaling does not remove the ECS instance even if a scale-in activity caused by changes in instance quantity or event-triggered tasks occurs. In this case, you must manually move the ECS instance out of the Protected state and then release the ECS instance. For more information, see the "RemoveInstances" topic.
-     * *   After you put an ECS instance into the Protected state, Auto Scaling does not update the health status of the instance when the instance is stopped or restarted.
+     * @description Once ECS instances enter the Protected state, they become subject to the following restrictions:
+     * *   ECS instances will persist in the Protected state, unless you deliberately remove them from this state.
+     * *   Even in scenarios where automatic scale-in actions are initiated due to fluctuations in the number of ECS instances or the execution of event-triggered tasks, Auto Scaling does not remove ECS instances that are in the Protected state from their respective scaling groups. Only after being manually removed from their respective scaling groups can ECS instances that are in the Protected state be released. For more information, see [Remove an ECS instance](https://help.aliyun.com/document_detail/25955.html).
+     * *   ECS instances in the Protected state maintain their existing health status even when they undergo stopping or restarting processes.
      *
      * @param request SetInstancesProtectionRequest
      * @return SetInstancesProtectionResponse
      */
     setInstancesProtection(request: SetInstancesProtectionRequest): Promise<SetInstancesProtectionResponse>;
     /**
-     * @summary Suspends processes in a scaling group.
+     * @summary Suspends scaling processes. This operation empowers you to selectively pause distinct scaling processes within a particular scaling group, enabling you to carry out alternative tasks and achieve more granular management over your scaling operations.
      *
      * @param request SuspendProcessesRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9909,14 +10039,22 @@ export default class Client extends OpenApi {
      */
     suspendProcessesWithOptions(request: SuspendProcessesRequest, runtime: $Util.RuntimeOptions): Promise<SuspendProcessesResponse>;
     /**
-     * @summary Suspends processes in a scaling group.
+     * @summary Suspends scaling processes. This operation empowers you to selectively pause distinct scaling processes within a particular scaling group, enabling you to carry out alternative tasks and achieve more granular management over your scaling operations.
      *
      * @param request SuspendProcessesRequest
      * @return SuspendProcessesResponse
      */
     suspendProcesses(request: SuspendProcessesRequest): Promise<SuspendProcessesResponse>;
     /**
-     * @summary Adds tags to specified Auto Scaling resources.
+     * @summary Creates and attaches tags. You can call the TagResources operation to uniformly create and attach tags to your Auto Scaling resources, streamlining resource management. This capability empowers you to categorize resources based on tags, thereby enhancing the overall efficiency of resource allocation and utilization.
+     *
+     * @description *   You can attach up to 20 tags to a scaling group.
+     *     **
+     *     **Note** Before you attach tags to a specific Auto Scaling resource, Alibaba Cloud automatically verifies the current number of tags attached to that resource. In the event the proposed addition would exceed the maximum allowed number of tags, an error message will be promptly returned after you call this operation.
+     * *   If you set `Tags.Propagate` to `true`, any tags attached to your scaling group will be automatically propagated to new instances that are subsequently created in the scaling group, without affecting existing instances.
+     * *   If both the scaling configuration and the scaling group have tags attached, and tag propagation from the scaling group is enabled, the tags of newly created instances comply with the following rules:
+     *     *   Instances set to join the scaling group will inherit the following tags: tags attached to the scaling configuration that initiates the instance creation and tags attached to the scaling group that are allowed to propagate to these instances upon instance creation.
+     *     *   If the tag keys of the scaling configuration and those attached to the scaling group and propagated to the instances are identical, the tags attached to the scaling group and propagated to the instances will be overwritten by the tags of the scaling configuration.
      *
      * @param request TagResourcesRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9924,14 +10062,22 @@ export default class Client extends OpenApi {
      */
     tagResourcesWithOptions(request: TagResourcesRequest, runtime: $Util.RuntimeOptions): Promise<TagResourcesResponse>;
     /**
-     * @summary Adds tags to specified Auto Scaling resources.
+     * @summary Creates and attaches tags. You can call the TagResources operation to uniformly create and attach tags to your Auto Scaling resources, streamlining resource management. This capability empowers you to categorize resources based on tags, thereby enhancing the overall efficiency of resource allocation and utilization.
+     *
+     * @description *   You can attach up to 20 tags to a scaling group.
+     *     **
+     *     **Note** Before you attach tags to a specific Auto Scaling resource, Alibaba Cloud automatically verifies the current number of tags attached to that resource. In the event the proposed addition would exceed the maximum allowed number of tags, an error message will be promptly returned after you call this operation.
+     * *   If you set `Tags.Propagate` to `true`, any tags attached to your scaling group will be automatically propagated to new instances that are subsequently created in the scaling group, without affecting existing instances.
+     * *   If both the scaling configuration and the scaling group have tags attached, and tag propagation from the scaling group is enabled, the tags of newly created instances comply with the following rules:
+     *     *   Instances set to join the scaling group will inherit the following tags: tags attached to the scaling configuration that initiates the instance creation and tags attached to the scaling group that are allowed to propagate to these instances upon instance creation.
+     *     *   If the tag keys of the scaling configuration and those attached to the scaling group and propagated to the instances are identical, the tags attached to the scaling group and propagated to the instances will be overwritten by the tags of the scaling configuration.
      *
      * @param request TagResourcesRequest
      * @return TagResourcesResponse
      */
     tagResources(request: TagResourcesRequest): Promise<TagResourcesResponse>;
     /**
-     * @summary Removes tags from the specified Auto Scaling resources. If you remove a tag and the tag is not added to other resources, the tag is automatically deleted.
+     * @summary Removes tags from Auto Scaling resources simultaneously. This operation streamlines resource management activities, enhances system efficiency, and mitigates potential security vulnerabilities. Once a tag is removed from a particular resource, and if it is not re-added to any other resource, the system will automatically delete the unused tag.
      *
      * @param request UntagResourcesRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9939,7 +10085,7 @@ export default class Client extends OpenApi {
      */
     untagResourcesWithOptions(request: UntagResourcesRequest, runtime: $Util.RuntimeOptions): Promise<UntagResourcesResponse>;
     /**
-     * @summary Removes tags from the specified Auto Scaling resources. If you remove a tag and the tag is not added to other resources, the tag is automatically deleted.
+     * @summary Removes tags from Auto Scaling resources simultaneously. This operation streamlines resource management activities, enhances system efficiency, and mitigates potential security vulnerabilities. Once a tag is removed from a particular resource, and if it is not re-added to any other resource, the system will automatically delete the unused tag.
      *
      * @param request UntagResourcesRequest
      * @return UntagResourcesResponse
@@ -9961,7 +10107,7 @@ export default class Client extends OpenApi {
      */
     verifyAuthentication(request: VerifyAuthenticationRequest): Promise<VerifyAuthenticationResponse>;
     /**
-     * @summary Checks whether Auto Scaling is activated.
+     * @summary Verifies whether Auto Scaling is activated. This operation guarantees that in response to shifts in business workloads or variations in incoming traffic, the system will automatically adjust resource provisioning. This auto-scaling capability enhances the overall system performance, ensuring high availability and improved flexibility to accommodate dynamic demands.
      *
      * @param request VerifyUserRequest
      * @param runtime runtime options for this request RuntimeOptions
@@ -9969,7 +10115,7 @@ export default class Client extends OpenApi {
      */
     verifyUserWithOptions(request: VerifyUserRequest, runtime: $Util.RuntimeOptions): Promise<VerifyUserResponse>;
     /**
-     * @summary Checks whether Auto Scaling is activated.
+     * @summary Verifies whether Auto Scaling is activated. This operation guarantees that in response to shifts in business workloads or variations in incoming traffic, the system will automatically adjust resource provisioning. This auto-scaling capability enhances the overall system performance, ensuring high availability and improved flexibility to accommodate dynamic demands.
      *
      * @param request VerifyUserRequest
      * @return VerifyUserResponse