@alicloud/ess20220222 1.0.4 → 1.0.5

package/dist/client.d.ts

@@ -1977,6 +1977,7 @@ export declare class DescribeScalingGroupsResponse extends $tea.Model {
 }
 export declare class DescribeScalingInstancesRequest extends $tea.Model {
     creationType?: string;
+    creationTypes?: string[];
     healthStatus?: string;
     instanceIds?: string[];
     lifecycleState?: string;
@@ -4015,6 +4016,7 @@ export declare class VerifyAuthenticationResponse extends $tea.Model {
 }
 export declare class VerifyUserRequest extends $tea.Model {
     ownerId?: number;
+    regionId?: string;
     resourceOwnerAccount?: string;
     resourceOwnerId?: number;
     static names(): {
@@ -4555,6 +4557,7 @@ export declare class CreateEciScalingConfigurationRequestVolumesDiskVolume exten
 }
 export declare class CreateEciScalingConfigurationRequestVolumesEmptyDirVolume extends $tea.Model {
     medium?: string;
+    sizeLimit?: string;
     static names(): {
         [key: string]: string;
     };
@@ -5333,6 +5336,7 @@ export declare class DescribeEciScalingConfigurationsResponseBodyScalingConfigur
     diskVolumeDiskSize?: number;
     diskVolumeFsType?: string;
     emptyDirVolumeMedium?: string;
+    emptyDirVolumeSizeLimit?: string;
     flexVolumeDriver?: string;
     flexVolumeFsType?: string;
     flexVolumeOptions?: string;
@@ -5771,6 +5775,7 @@ export declare class DescribeScalingGroupsResponseBodyScalingGroups extends $tea
     DBInstanceIds?: string[];
     defaultCooldown?: number;
     desiredCapacity?: number;
+    enableDesiredCapacity?: boolean;
     groupDeletionProtection?: boolean;
     groupType?: string;
     healthCheckType?: string;
@@ -6524,6 +6529,7 @@ export declare class ModifyEciScalingConfigurationRequestVolumesDiskVolume exten
 }
 export declare class ModifyEciScalingConfigurationRequestVolumesEmptyDirVolume extends $tea.Model {
     medium?: string;
+    sizeLimit?: string;
     static names(): {
         [key: string]: string;
     };
@@ -6901,97 +6907,19 @@ export default class Client extends OpenApi {
     getEndpoint(productId: string, regionId: string, endpointRule: string, network: string, suffix: string, endpointMap: {
         [key: string]: string;
     }, endpoint: string): string;
-    /**
-      * Associates one or more Application Load Balancer (ALB) server groups with a scaling group.
-      *
-      * @param request AttachAlbServerGroupsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachAlbServerGroupsResponse
-     */
     attachAlbServerGroupsWithOptions(request: AttachAlbServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<AttachAlbServerGroupsResponse>;
-    /**
-      * Associates one or more Application Load Balancer (ALB) server groups with a scaling group.
-      *
-      * @param request AttachAlbServerGroupsRequest
-      * @return AttachAlbServerGroupsResponse
-     */
     attachAlbServerGroups(request: AttachAlbServerGroupsRequest): Promise<AttachAlbServerGroupsResponse>;
-    /**
-      * Associates one or more ApsaraDB RDS instances with a scaling group.
-      *
-      * @param request AttachDBInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachDBInstancesResponse
-     */
     attachDBInstancesWithOptions(request: AttachDBInstancesRequest, runtime: $Util.RuntimeOptions): Promise<AttachDBInstancesResponse>;
-    /**
-      * Associates one or more ApsaraDB RDS instances with a scaling group.
-      *
-      * @param request AttachDBInstancesRequest
-      * @return AttachDBInstancesResponse
-     */
     attachDBInstances(request: AttachDBInstancesRequest): Promise<AttachDBInstancesResponse>;
-    /**
-      * Manually adds Elastic Compute Service (ECS) instances or elastic container instances to a scaling group.
-      *
-      * @param request AttachInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachInstancesResponse
-     */
     attachInstancesWithOptions(request: AttachInstancesRequest, runtime: $Util.RuntimeOptions): Promise<AttachInstancesResponse>;
-    /**
-      * Manually adds Elastic Compute Service (ECS) instances or elastic container instances to a scaling group.
-      *
-      * @param request AttachInstancesRequest
-      * @return AttachInstancesResponse
-     */
     attachInstances(request: AttachInstancesRequest): Promise<AttachInstancesResponse>;
-    /**
-      * Attaches one or more Classic Load Balancer (CLB) instances to a scaling group.
-      *
-      * @param request AttachLoadBalancersRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachLoadBalancersResponse
-     */
     attachLoadBalancersWithOptions(request: AttachLoadBalancersRequest, runtime: $Util.RuntimeOptions): Promise<AttachLoadBalancersResponse>;
-    /**
-      * Attaches one or more Classic Load Balancer (CLB) instances to a scaling group.
-      *
-      * @param request AttachLoadBalancersRequest
-      * @return AttachLoadBalancersResponse
-     */
     attachLoadBalancers(request: AttachLoadBalancersRequest): Promise<AttachLoadBalancersResponse>;
     attachServerGroupsWithOptions(request: AttachServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<AttachServerGroupsResponse>;
     attachServerGroups(request: AttachServerGroupsRequest): Promise<AttachServerGroupsResponse>;
-    /**
-      * Attaches one or more vServer groups of a Classic Load Balancer (CLB) instance to a scaling group.
-      *
-      * @param request AttachVServerGroupsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachVServerGroupsResponse
-     */
     attachVServerGroupsWithOptions(request: AttachVServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<AttachVServerGroupsResponse>;
-    /**
-      * Attaches one or more vServer groups of a Classic Load Balancer (CLB) instance to a scaling group.
-      *
-      * @param request AttachVServerGroupsRequest
-      * @return AttachVServerGroupsResponse
-     */
     attachVServerGroups(request: AttachVServerGroupsRequest): Promise<AttachVServerGroupsResponse>;
-    /**
-      * 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 is a collection of infrastructure for projects, environments, or stacks. In a resource group, you can manage resources, monitor resources, and perform operations in a centralized manner. This way, you do not need to view and check your Alibaba Cloud resources in each Alibaba Cloud service.
-      *
-      * @param request ChangeResourceGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ChangeResourceGroupResponse
-     */
     changeResourceGroupWithOptions(request: ChangeResourceGroupRequest, runtime: $Util.RuntimeOptions): Promise<ChangeResourceGroupResponse>;
-    /**
-      * 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 is a collection of infrastructure for projects, environments, or stacks. In a resource group, you can manage resources, monitor resources, and perform operations in a centralized manner. This way, you do not need to view and check your Alibaba Cloud resources in each Alibaba Cloud service.
-      *
-      * @param request ChangeResourceGroupRequest
-      * @return ChangeResourceGroupResponse
-     */
     changeResourceGroup(request: ChangeResourceGroupRequest): Promise<ChangeResourceGroupResponse>;
     /**
       * If you set the LifecycleActionResult parameter for a lifecycle hook of a scaling group to CONTINUE in the operation, Auto Scaling continues to complete the scaling activity in the scaling group after the lifecycle hook times out. If you set the LifecycleActionResult parameter to ABANDON, Auto Scaling stops the scaling activity in the scaling group after the lifecycle hook times out.
@@ -7008,28 +6936,7 @@ export default class Client extends OpenApi {
       * @return CompleteLifecycleActionResponse
      */
     completeLifecycleAction(request: CompleteLifecycleActionRequest): Promise<CompleteLifecycleActionResponse>;
-    /**
-      * *   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](~~74861~~).
-      * *   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](~~74854~~).
-      * > 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.
-      *
-      * @param request CreateAlarmRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return CreateAlarmResponse
-     */
     createAlarmWithOptions(request: CreateAlarmRequest, runtime: $Util.RuntimeOptions): Promise<CreateAlarmResponse>;
-    /**
-      * *   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](~~74861~~).
-      * *   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](~~74854~~).
-      * > 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.
-      *
-      * @param request CreateAlarmRequest
-      * @return CreateAlarmResponse
-     */
     createAlarm(request: CreateAlarmRequest): Promise<CreateAlarmResponse>;
     /**
       * A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
@@ -7069,29 +6976,16 @@ export default class Client extends OpenApi {
       * @return CreateLifecycleHookResponse
      */
     createLifecycleHook(request: CreateLifecycleHookRequest): Promise<CreateLifecycleHookResponse>;
-    /**
-      * Creates a notification.
-      *
-      * @param request CreateNotificationConfigurationRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return CreateNotificationConfigurationResponse
-     */
     createNotificationConfigurationWithOptions(request: CreateNotificationConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<CreateNotificationConfigurationResponse>;
-    /**
-      * Creates a notification.
-      *
-      * @param request CreateNotificationConfigurationRequest
-      * @return CreateNotificationConfigurationResponse
-     */
     createNotificationConfiguration(request: CreateNotificationConfigurationRequest): Promise<CreateNotificationConfigurationResponse>;
     /**
       * Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
-      * *   InstancePatternInfos: intelligent configuration mode. In this mode, you need to only specify the number of vCPUs, memory size, instance family, and maximum price. Auto Scaling selects the lowest-priced instance type based on your configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode reduces the failures of scale-outs caused by insufficient inventory of instance types.
+      * *   InstancePatternInfos: intelligent configuration mode. In this mode, you need to only specify the number of vCPUs, memory size, instance family, and maximum price. Auto Scaling selects the instance type that has the lowest price based on the configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode reduces scale-out failures caused by insufficient inventory of instance types.
       * *   InstanceType: In this mode, you must specify one instance type.
       * *   InstanceTypes: In this mode, you can specify more than one instance type.
       * *   InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
-      * *   Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines the range of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling creates ECS instances of the lowest-priced instance type. This mode is available only if the Scaling Policy parameter is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
-      * > You cannot specify InstanceType, InstanceTypes, InstanceTypeOverrides, and Cpu and Memory parameters at the same time. You can specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfo at the same time. If you specify the InstanceType and InstancePatternInfos parameters or specify the InstanceTypes and InstancePatternInfos parameters at the same time, Auto Scaling preferentially uses the instance types that are specified by the InstanceType or InstanceTypes parameter for scale-outs. If the instance types that are specified by the InstanceType or InstanceTypes parameter do not have sufficient inventory, Auto Scaling uses the instance types that are specified by the InstancePatternInfos parameter for scale-outs.
+      * *   Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines the range of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling creates ECS instances by using the lowest-priced instance type. This mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
+      * > You cannot specify InstanceType, InstanceTypes, InstanceTypeOverrides, and Cpu and Memory at the same time. You can specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfo at the same time. If you specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfos at the same time, Auto Scaling preferentially uses the instance types that are specified by InstanceType or InstanceTypes for scale-outs. If the instance types that are specified by InstanceType or InstanceTypes do not have sufficient inventory, Auto Scaling uses the instance types that are specified by InstancePatternInfos for scale-outs.
       *
       * @param tmpReq CreateScalingConfigurationRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7100,12 +6994,12 @@ export default class Client extends OpenApi {
     createScalingConfigurationWithOptions(tmpReq: CreateScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<CreateScalingConfigurationResponse>;
     /**
       * Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
-      * *   InstancePatternInfos: intelligent configuration mode. In this mode, you need to only specify the number of vCPUs, memory size, instance family, and maximum price. Auto Scaling selects the lowest-priced instance type based on your configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode reduces the failures of scale-outs caused by insufficient inventory of instance types.
+      * *   InstancePatternInfos: intelligent configuration mode. In this mode, you need to only specify the number of vCPUs, memory size, instance family, and maximum price. Auto Scaling selects the instance type that has the lowest price based on the configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode reduces scale-out failures caused by insufficient inventory of instance types.
       * *   InstanceType: In this mode, you must specify one instance type.
       * *   InstanceTypes: In this mode, you can specify more than one instance type.
       * *   InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
-      * *   Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines the range of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling creates ECS instances of the lowest-priced instance type. This mode is available only if the Scaling Policy parameter is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
-      * > You cannot specify InstanceType, InstanceTypes, InstanceTypeOverrides, and Cpu and Memory parameters at the same time. You can specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfo at the same time. If you specify the InstanceType and InstancePatternInfos parameters or specify the InstanceTypes and InstancePatternInfos parameters at the same time, Auto Scaling preferentially uses the instance types that are specified by the InstanceType or InstanceTypes parameter for scale-outs. If the instance types that are specified by the InstanceType or InstanceTypes parameter do not have sufficient inventory, Auto Scaling uses the instance types that are specified by the InstancePatternInfos parameter for scale-outs.
+      * *   Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines the range of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling creates ECS instances by using the lowest-priced instance type. This mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
+      * > You cannot specify InstanceType, InstanceTypes, InstanceTypeOverrides, and Cpu and Memory at the same time. You can specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfo at the same time. If you specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfos at the same time, Auto Scaling preferentially uses the instance types that are specified by InstanceType or InstanceTypes for scale-outs. If the instance types that are specified by InstanceType or InstanceTypes do not have sufficient inventory, Auto Scaling uses the instance types that are specified by InstancePatternInfos for scale-outs.
       *
       * @param request CreateScalingConfigurationRequest
       * @return CreateScalingConfigurationResponse
@@ -7169,7 +7063,18 @@ export default class Client extends OpenApi {
      */
     createScalingGroup(request: CreateScalingGroupRequest): Promise<CreateScalingGroupResponse>;
     /**
-      * Creates a scaling rule.
+      * A scaling rule defines a specific scaling activity, such as adding or removing N instances. If the number of Elastic Compute Service (ECS) instances in a scaling group is less than the minimum number allowed or greater than the maximum number allowed after a scaling rule is executed, Auto Scaling calculates the number of ECS instances that need to be added or removed. This ensures that the number of ECS instances can be maintained within the valid range after the scaling rule is executed. Examples:
+      * *   If your scaling group contains two ECS instances and allows up to three ECS instances, only one ECS instance is added to your scaling group after you execute a scale-out rule in which three ECS instances are specified.
+      * *   If your scaling group contains three ECS instances and requires at least two ECS instances, only one ECS instance is removed from your scaling group after you execute a scale-in rule in which five ECS instances are specified.
+      * Before you call this operation, take note of the following items:
+      * *   If you set AdjustmentType to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of AdjustmentValue must be greater than or equal to 0.
+      * *   If you set AdjustmentType to QuantityChangeInCapacity, a positive value of AdjustmentValue specifies the number of ECS instances that are added to the scaling group, and a negative value of AdjustmentValue specifies the number of ECS instances that are removed from the scaling group.
+      * *   If you set AdjustmentType to PercentChangeInCapacity, Auto Scaling uses the following formula to calculate a value, and then rounds the value to the nearest integer to obtain the number of ECS instances that need to be scaled: Value of TotalCapacity × Value of AdjustmentValue/100.
+      * *   If you specify a cooldown period for the scaling rule, the specified cooldown period takes effect after the rule is executed. Otherwise, the value of DefaultCooldown of the scaling group takes effect.
+      * *   You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
+      * *   The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
+      *     *   ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule that you want to execute.
+      *     *   CreateScheduledTask: You can call this operation to create a scheduled task. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule that you want to associate with the scheduled task.
       *
       * @param request CreateScalingRuleRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7177,96 +7082,38 @@ export default class Client extends OpenApi {
      */
     createScalingRuleWithOptions(request: CreateScalingRuleRequest, runtime: $Util.RuntimeOptions): Promise<CreateScalingRuleResponse>;
     /**
-      * Creates a scaling rule.
+      * A scaling rule defines a specific scaling activity, such as adding or removing N instances. If the number of Elastic Compute Service (ECS) instances in a scaling group is less than the minimum number allowed or greater than the maximum number allowed after a scaling rule is executed, Auto Scaling calculates the number of ECS instances that need to be added or removed. This ensures that the number of ECS instances can be maintained within the valid range after the scaling rule is executed. Examples:
+      * *   If your scaling group contains two ECS instances and allows up to three ECS instances, only one ECS instance is added to your scaling group after you execute a scale-out rule in which three ECS instances are specified.
+      * *   If your scaling group contains three ECS instances and requires at least two ECS instances, only one ECS instance is removed from your scaling group after you execute a scale-in rule in which five ECS instances are specified.
+      * Before you call this operation, take note of the following items:
+      * *   If you set AdjustmentType to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of AdjustmentValue must be greater than or equal to 0.
+      * *   If you set AdjustmentType to QuantityChangeInCapacity, a positive value of AdjustmentValue specifies the number of ECS instances that are added to the scaling group, and a negative value of AdjustmentValue specifies the number of ECS instances that are removed from the scaling group.
+      * *   If you set AdjustmentType to PercentChangeInCapacity, Auto Scaling uses the following formula to calculate a value, and then rounds the value to the nearest integer to obtain the number of ECS instances that need to be scaled: Value of TotalCapacity × Value of AdjustmentValue/100.
+      * *   If you specify a cooldown period for the scaling rule, the specified cooldown period takes effect after the rule is executed. Otherwise, the value of DefaultCooldown of the scaling group takes effect.
+      * *   You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
+      * *   The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
+      *     *   ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule that you want to execute.
+      *     *   CreateScheduledTask: You can call this operation to create a scheduled task. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule that you want to associate with the scheduled task.
       *
       * @param request CreateScalingRuleRequest
       * @return CreateScalingRuleResponse
      */
     createScalingRule(request: CreateScalingRuleRequest): Promise<CreateScalingRuleResponse>;
-    /**
-      * Creates a scheduled task.
-      *
-      * @param request CreateScheduledTaskRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return CreateScheduledTaskResponse
-     */
     createScheduledTaskWithOptions(request: CreateScheduledTaskRequest, runtime: $Util.RuntimeOptions): Promise<CreateScheduledTaskResponse>;
-    /**
-      * Creates a scheduled task.
-      *
-      * @param request CreateScheduledTaskRequest
-      * @return CreateScheduledTaskResponse
-     */
     createScheduledTask(request: CreateScheduledTaskRequest): Promise<CreateScheduledTaskResponse>;
     deactivateScalingConfigurationWithOptions(request: DeactivateScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeactivateScalingConfigurationResponse>;
     deactivateScalingConfiguration(request: DeactivateScalingConfigurationRequest): Promise<DeactivateScalingConfigurationResponse>;
     deleteAlarmWithOptions(request: DeleteAlarmRequest, runtime: $Util.RuntimeOptions): Promise<DeleteAlarmResponse>;
     deleteAlarm(request: DeleteAlarmRequest): Promise<DeleteAlarmResponse>;
-    /**
-      * Deletes a scaling configuration that is used to create elastic container instances.
-      *
-      * @param request DeleteEciScalingConfigurationRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DeleteEciScalingConfigurationResponse
-     */
     deleteEciScalingConfigurationWithOptions(request: DeleteEciScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeleteEciScalingConfigurationResponse>;
-    /**
-      * Deletes a scaling configuration that is used to create elastic container instances.
-      *
-      * @param request DeleteEciScalingConfigurationRequest
-      * @return DeleteEciScalingConfigurationResponse
-     */
     deleteEciScalingConfiguration(request: DeleteEciScalingConfigurationRequest): Promise<DeleteEciScalingConfigurationResponse>;
-    /**
-      * If you delete a lifecycle hook that is in effect in a scaling group, instances exit the Pending state in advance. You can use one of the following methods to specify the lifecycle hooks that you want to delete:
-      * *   Specify the scaling group ID of the lifecycle hook that you want to delete by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
-      * *   Specify the lifecycle hook ID by using the LifecycleHookId parameter. In this case, the ScalingGroupId parameter and the LifecycleHookName parameter are ignored.
-      *
-      * @param request DeleteLifecycleHookRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DeleteLifecycleHookResponse
-     */
     deleteLifecycleHookWithOptions(request: DeleteLifecycleHookRequest, runtime: $Util.RuntimeOptions): Promise<DeleteLifecycleHookResponse>;
-    /**
-      * If you delete a lifecycle hook that is in effect in a scaling group, instances exit the Pending state in advance. You can use one of the following methods to specify the lifecycle hooks that you want to delete:
-      * *   Specify the scaling group ID of the lifecycle hook that you want to delete by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
-      * *   Specify the lifecycle hook ID by using the LifecycleHookId parameter. In this case, the ScalingGroupId parameter and the LifecycleHookName parameter are ignored.
-      *
-      * @param request DeleteLifecycleHookRequest
-      * @return DeleteLifecycleHookResponse
-     */
     deleteLifecycleHook(request: DeleteLifecycleHookRequest): Promise<DeleteLifecycleHookResponse>;
     deleteNotificationConfigurationWithOptions(request: DeleteNotificationConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeleteNotificationConfigurationResponse>;
     deleteNotificationConfiguration(request: DeleteNotificationConfigurationRequest): Promise<DeleteNotificationConfigurationResponse>;
-    /**
-      * Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
-      *
-      * @param request DeleteScalingConfigurationRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DeleteScalingConfigurationResponse
-     */
     deleteScalingConfigurationWithOptions(request: DeleteScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeleteScalingConfigurationResponse>;
-    /**
-      * Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
-      *
-      * @param request DeleteScalingConfigurationRequest
-      * @return DeleteScalingConfigurationResponse
-     */
     deleteScalingConfiguration(request: DeleteScalingConfigurationRequest): Promise<DeleteScalingConfigurationResponse>;
-    /**
-      * Deletes a scaling group.
-      *
-      * @param request DeleteScalingGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DeleteScalingGroupResponse
-     */
     deleteScalingGroupWithOptions(request: DeleteScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<DeleteScalingGroupResponse>;
-    /**
-      * Deletes a scaling group.
-      *
-      * @param request DeleteScalingGroupRequest
-      * @return DeleteScalingGroupResponse
-     */
     deleteScalingGroup(request: DeleteScalingGroupRequest): Promise<DeleteScalingGroupResponse>;
     deleteScalingRuleWithOptions(request: DeleteScalingRuleRequest, runtime: $Util.RuntimeOptions): Promise<DeleteScalingRuleResponse>;
     deleteScalingRule(request: DeleteScalingRuleRequest): Promise<DeleteScalingRuleResponse>;
@@ -7276,41 +7123,9 @@ export default class Client extends OpenApi {
     describeAlarms(request: DescribeAlarmsRequest): Promise<DescribeAlarmsResponse>;
     describeEciScalingConfigurationsWithOptions(request: DescribeEciScalingConfigurationsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeEciScalingConfigurationsResponse>;
     describeEciScalingConfigurations(request: DescribeEciScalingConfigurationsRequest): Promise<DescribeEciScalingConfigurationsResponse>;
-    /**
-      * Queries lifecycle actions.
-      *
-      * @param request DescribeLifecycleActionsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeLifecycleActionsResponse
-     */
     describeLifecycleActionsWithOptions(request: DescribeLifecycleActionsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeLifecycleActionsResponse>;
-    /**
-      * Queries lifecycle actions.
-      *
-      * @param request DescribeLifecycleActionsRequest
-      * @return DescribeLifecycleActionsResponse
-     */
     describeLifecycleActions(request: DescribeLifecycleActionsRequest): Promise<DescribeLifecycleActionsResponse>;
-    /**
-      * You can use one of the following methods to query lifecycle hooks:
-      * *   Specify a list of lifecycle hook IDs by using the LifecycleHookIds parameter. In this case, you do not need to specify the ScalingGroupId and LifecycleHookName parameters.
-      * *   Specify the scaling group ID by using the ScalingGroupId parameter.
-      * *   Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter at the same time.
-      *
-      * @param request DescribeLifecycleHooksRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeLifecycleHooksResponse
-     */
     describeLifecycleHooksWithOptions(request: DescribeLifecycleHooksRequest, runtime: $Util.RuntimeOptions): Promise<DescribeLifecycleHooksResponse>;
-    /**
-      * You can use one of the following methods to query lifecycle hooks:
-      * *   Specify a list of lifecycle hook IDs by using the LifecycleHookIds parameter. In this case, you do not need to specify the ScalingGroupId and LifecycleHookName parameters.
-      * *   Specify the scaling group ID by using the ScalingGroupId parameter.
-      * *   Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter at the same time.
-      *
-      * @param request DescribeLifecycleHooksRequest
-      * @return DescribeLifecycleHooksResponse
-     */
     describeLifecycleHooks(request: DescribeLifecycleHooksRequest): Promise<DescribeLifecycleHooksResponse>;
     describeLimitationWithOptions(request: DescribeLimitationRequest, runtime: $Util.RuntimeOptions): Promise<DescribeLimitationResponse>;
     describeLimitation(request: DescribeLimitationRequest): Promise<DescribeLimitationResponse>;
@@ -7345,23 +7160,10 @@ export default class Client extends OpenApi {
     describeScalingConfigurations(request: DescribeScalingConfigurationsRequest): Promise<DescribeScalingConfigurationsResponse>;
     describeScalingGroupsWithOptions(request: DescribeScalingGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeScalingGroupsResponse>;
     describeScalingGroups(request: DescribeScalingGroupsRequest): Promise<DescribeScalingGroupsResponse>;
-    /**
-      * You can query ECS instances by scaling group ID, scaling configuration ID, health status, lifecycle status, and instance creation method.
-      *
-      * @param request DescribeScalingInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeScalingInstancesResponse
-     */
     describeScalingInstancesWithOptions(request: DescribeScalingInstancesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeScalingInstancesResponse>;
-    /**
-      * You can query ECS instances by scaling group ID, scaling configuration ID, health status, lifecycle status, and instance creation method.
-      *
-      * @param request DescribeScalingInstancesRequest
-      * @return DescribeScalingInstancesResponse
-     */
     describeScalingInstances(request: DescribeScalingInstancesRequest): Promise<DescribeScalingInstancesResponse>;
     /**
-      * Queries all scaling rules in a scaling group.
+      * You can specify a scaling group ID to query the information about all scaling rules in a scaling group. You can also specify the scaling rule ID, name, unique identifier, or type in the request parameters as filter conditions.
       *
       * @param request DescribeScalingRulesRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7369,81 +7171,29 @@ export default class Client extends OpenApi {
      */
     describeScalingRulesWithOptions(request: DescribeScalingRulesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeScalingRulesResponse>;
     /**
-      * Queries all scaling rules in a scaling group.
+      * You can specify a scaling group ID to query the information about all scaling rules in a scaling group. You can also specify the scaling rule ID, name, unique identifier, or type in the request parameters as filter conditions.
       *
       * @param request DescribeScalingRulesRequest
       * @return DescribeScalingRulesResponse
      */
     describeScalingRules(request: DescribeScalingRulesRequest): Promise<DescribeScalingRulesResponse>;
-    /**
-      * You can query scheduled tasks by scaling rule, task ID, or task name.
-      *
-      * @param request DescribeScheduledTasksRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeScheduledTasksResponse
-     */
     describeScheduledTasksWithOptions(request: DescribeScheduledTasksRequest, runtime: $Util.RuntimeOptions): Promise<DescribeScheduledTasksResponse>;
-    /**
-      * You can query scheduled tasks by scaling rule, task ID, or task name.
-      *
-      * @param request DescribeScheduledTasksRequest
-      * @return DescribeScheduledTasksResponse
-     */
     describeScheduledTasks(request: DescribeScheduledTasksRequest): Promise<DescribeScheduledTasksResponse>;
     detachAlbServerGroupsWithOptions(request: DetachAlbServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DetachAlbServerGroupsResponse>;
     detachAlbServerGroups(request: DetachAlbServerGroupsRequest): Promise<DetachAlbServerGroupsResponse>;
     detachDBInstancesWithOptions(request: DetachDBInstancesRequest, runtime: $Util.RuntimeOptions): Promise<DetachDBInstancesResponse>;
     detachDBInstances(request: DetachDBInstancesRequest): Promise<DetachDBInstancesResponse>;
-    /**
-      * Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
-      *
-      * @param request DetachInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DetachInstancesResponse
-     */
     detachInstancesWithOptions(request: DetachInstancesRequest, runtime: $Util.RuntimeOptions): Promise<DetachInstancesResponse>;
-    /**
-      * Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
-      *
-      * @param request DetachInstancesRequest
-      * @return DetachInstancesResponse
-     */
     detachInstances(request: DetachInstancesRequest): Promise<DetachInstancesResponse>;
     detachLoadBalancersWithOptions(request: DetachLoadBalancersRequest, runtime: $Util.RuntimeOptions): Promise<DetachLoadBalancersResponse>;
     detachLoadBalancers(request: DetachLoadBalancersRequest): Promise<DetachLoadBalancersResponse>;
     detachServerGroupsWithOptions(request: DetachServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DetachServerGroupsResponse>;
     detachServerGroups(request: DetachServerGroupsRequest): Promise<DetachServerGroupsResponse>;
-    /**
-      * Detaches one or more vServer groups of a Classic Load Balancer (CLB) instance from a scaling group.
-      *
-      * @param request DetachVServerGroupsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DetachVServerGroupsResponse
-     */
     detachVServerGroupsWithOptions(request: DetachVServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DetachVServerGroupsResponse>;
-    /**
-      * Detaches one or more vServer groups of a Classic Load Balancer (CLB) instance from a scaling group.
-      *
-      * @param request DetachVServerGroupsRequest
-      * @return DetachVServerGroupsResponse
-     */
     detachVServerGroups(request: DetachVServerGroupsRequest): Promise<DetachVServerGroupsResponse>;
     disableAlarmWithOptions(request: DisableAlarmRequest, runtime: $Util.RuntimeOptions): Promise<DisableAlarmResponse>;
     disableAlarm(request: DisableAlarmRequest): Promise<DisableAlarmResponse>;
-    /**
-      * Disables a scaling group.
-      *
-      * @param request DisableScalingGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DisableScalingGroupResponse
-     */
     disableScalingGroupWithOptions(request: DisableScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<DisableScalingGroupResponse>;
-    /**
-      * Disables a scaling group.
-      *
-      * @param request DisableScalingGroupRequest
-      * @return DisableScalingGroupResponse
-     */
     disableScalingGroup(request: DisableScalingGroupRequest): Promise<DisableScalingGroupResponse>;
     enableAlarmWithOptions(request: EnableAlarmRequest, runtime: $Util.RuntimeOptions): Promise<EnableAlarmResponse>;
     enableAlarm(request: EnableAlarmRequest): Promise<EnableAlarmResponse>;
@@ -7470,44 +7220,12 @@ export default class Client extends OpenApi {
       * @return EnableScalingGroupResponse
      */
     enableScalingGroup(request: EnableScalingGroupRequest): Promise<EnableScalingGroupResponse>;
-    /**
-      * *   If you call the operation to set an Elastic Compute Service (ECS) instance in a scaling group that is associated with a Server Load Balancer (SLB) instance to the Standby state, the weight of the ECS instance as a backend server of the SLB instance is set to 0.
-      * *   You can remove an ECS instance that is in the Standby state from a scaling group and release the instance.
-      * *   When scale-in activities are triggered by changes in the number of scaling groups or by event-triggered tasks, the ECS instances that are in the Standby state are not removed from the scaling groups.
-      * *   If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, such as in the Stopping or Restarting state, Auto Scaling does not update the health check status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health check status of the ECS instance only when the ECS instance is no longer in the Standby state.
-      *
-      * @param request EnterStandbyRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return EnterStandbyResponse
-     */
     enterStandbyWithOptions(request: EnterStandbyRequest, runtime: $Util.RuntimeOptions): Promise<EnterStandbyResponse>;
-    /**
-      * *   If you call the operation to set an Elastic Compute Service (ECS) instance in a scaling group that is associated with a Server Load Balancer (SLB) instance to the Standby state, the weight of the ECS instance as a backend server of the SLB instance is set to 0.
-      * *   You can remove an ECS instance that is in the Standby state from a scaling group and release the instance.
-      * *   When scale-in activities are triggered by changes in the number of scaling groups or by event-triggered tasks, the ECS instances that are in the Standby state are not removed from the scaling groups.
-      * *   If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, such as in the Stopping or Restarting state, Auto Scaling does not update the health check status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health check status of the ECS instance only when the ECS instance is no longer in the Standby state.
-      *
-      * @param request EnterStandbyRequest
-      * @return EnterStandbyResponse
-     */
     enterStandby(request: EnterStandbyRequest): Promise<EnterStandbyResponse>;
-    /**
-      * Executes a scaling rule.
-      *
-      * @param request ExecuteScalingRuleRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ExecuteScalingRuleResponse
-     */
     executeScalingRuleWithOptions(request: ExecuteScalingRuleRequest, runtime: $Util.RuntimeOptions): Promise<ExecuteScalingRuleResponse>;
-    /**
-      * Executes a scaling rule.
-      *
-      * @param request ExecuteScalingRuleRequest
-      * @return ExecuteScalingRuleResponse
-     */
     executeScalingRule(request: ExecuteScalingRuleRequest): Promise<ExecuteScalingRuleResponse>;
     /**
-      * If the scaling group is associated with a load balancing instance, the ECS instance weight will be set to the weight value defined in the scaling configuration.
+      * The IDs of the ECS instances. The value of this parameter can be a JSON array that consists of up to 20 instance IDs. Separate multiple instance IDs with commas (,).
       *
       * @param request ExitStandbyRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7515,7 +7233,7 @@ export default class Client extends OpenApi {
      */
     exitStandbyWithOptions(request: ExitStandbyRequest, runtime: $Util.RuntimeOptions): Promise<ExitStandbyResponse>;
     /**
-      * If the scaling group is associated with a load balancing instance, the ECS instance weight will be set to the weight value defined in the scaling configuration.
+      * The IDs of the ECS instances. The value of this parameter can be a JSON array that consists of up to 20 instance IDs. Separate multiple instance IDs with commas (,).
       *
       * @param request ExitStandbyRequest
       * @return ExitStandbyResponse
@@ -7528,7 +7246,11 @@ export default class Client extends OpenApi {
     listTagValuesWithOptions(request: ListTagValuesRequest, runtime: $Util.RuntimeOptions): Promise<ListTagValuesResponse>;
     listTagValues(request: ListTagValuesRequest): Promise<ListTagValuesResponse>;
     /**
-      * Modifies an event-triggered task.
+      * *   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 [Custom monitoring event-triggered tasks](~~74861~~).
+      * *   When you create an event-triggered task, you must specify MetricName, DimensionKey, and DimensionValue 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 in a scaling group within an Alibaba Cloud account.
+      *     *   If you set MetricType to custom, the valid values are your custom metrics.
+      *     *   For information about the metrics that are supported if you set MetricType to system, see [Event-triggered task for system monitoring](~~74854~~).
+      * > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see `DimensionKey` and `DimensionValue` in the "Request parameters" section of this topic.
       *
       * @param request ModifyAlarmRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7536,7 +7258,11 @@ export default class Client extends OpenApi {
      */
     modifyAlarmWithOptions(request: ModifyAlarmRequest, runtime: $Util.RuntimeOptions): Promise<ModifyAlarmResponse>;
     /**
-      * Modifies an event-triggered task.
+      * *   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 [Custom monitoring event-triggered tasks](~~74861~~).
+      * *   When you create an event-triggered task, you must specify MetricName, DimensionKey, and DimensionValue 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 in a scaling group within an Alibaba Cloud account.
+      *     *   If you set MetricType to custom, the valid values are your custom metrics.
+      *     *   For information about the metrics that are supported if you set MetricType to system, see [Event-triggered task for system monitoring](~~74854~~).
+      * > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see `DimensionKey` and `DimensionValue` in the "Request parameters" section of this topic.
       *
       * @param request ModifyAlarmRequest
       * @return ModifyAlarmResponse
@@ -7579,7 +7305,7 @@ export default class Client extends OpenApi {
     modifyNotificationConfigurationWithOptions(request: ModifyNotificationConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<ModifyNotificationConfigurationResponse>;
     modifyNotificationConfiguration(request: ModifyNotificationConfigurationRequest): Promise<ModifyNotificationConfigurationResponse>;
     /**
-      * If you want to change the name of a scaling configuration in a scaling group, make sure that the new name is unique within the scaling group.
+      * You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
       *
       * @param tmpReq ModifyScalingConfigurationRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7587,114 +7313,28 @@ export default class Client extends OpenApi {
      */
     modifyScalingConfigurationWithOptions(tmpReq: ModifyScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<ModifyScalingConfigurationResponse>;
     /**
-      * If you want to change the name of a scaling configuration in a scaling group, make sure that the new name is unique within the scaling group.
+      * You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
       *
       * @param request ModifyScalingConfigurationRequest
       * @return ModifyScalingConfigurationResponse
      */
     modifyScalingConfiguration(request: ModifyScalingConfigurationRequest): Promise<ModifyScalingConfigurationResponse>;
-    /**
-      * Modifies a scaling group.
-      *
-      * @param request ModifyScalingGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyScalingGroupResponse
-     */
     modifyScalingGroupWithOptions(request: ModifyScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<ModifyScalingGroupResponse>;
-    /**
-      * Modifies a scaling group.
-      *
-      * @param request ModifyScalingGroupRequest
-      * @return ModifyScalingGroupResponse
-     */
     modifyScalingGroup(request: ModifyScalingGroupRequest): Promise<ModifyScalingGroupResponse>;
     modifyScalingRuleWithOptions(request: ModifyScalingRuleRequest, runtime: $Util.RuntimeOptions): Promise<ModifyScalingRuleResponse>;
     modifyScalingRule(request: ModifyScalingRuleRequest): Promise<ModifyScalingRuleResponse>;
-    /**
-      * Modifies a scheduled task.
-      *
-      * @param request ModifyScheduledTaskRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyScheduledTaskResponse
-     */
     modifyScheduledTaskWithOptions(request: ModifyScheduledTaskRequest, runtime: $Util.RuntimeOptions): Promise<ModifyScheduledTaskResponse>;
-    /**
-      * Modifies a scheduled task.
-      *
-      * @param request ModifyScheduledTaskRequest
-      * @return ModifyScheduledTaskResponse
-     */
     modifyScheduledTask(request: ModifyScheduledTaskRequest): Promise<ModifyScheduledTaskResponse>;
-    /**
-      * Rebalances Elastic Compute Service (ECS) instances in a multi-zone scaling group across zones.
-      *
-      * @param request RebalanceInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return RebalanceInstancesResponse
-     */
     rebalanceInstancesWithOptions(request: RebalanceInstancesRequest, runtime: $Util.RuntimeOptions): Promise<RebalanceInstancesResponse>;
-    /**
-      * Rebalances Elastic Compute Service (ECS) instances in a multi-zone scaling group across zones.
-      *
-      * @param request RebalanceInstancesRequest
-      * @return RebalanceInstancesResponse
-     */
     rebalanceInstances(request: RebalanceInstancesRequest): Promise<RebalanceInstancesResponse>;
-    /**
-      * Prolongs a lifecycle hook for Elastic Compute Service (ECS) instances.
-      *
-      * @param request RecordLifecycleActionHeartbeatRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return RecordLifecycleActionHeartbeatResponse
-     */
     recordLifecycleActionHeartbeatWithOptions(request: RecordLifecycleActionHeartbeatRequest, runtime: $Util.RuntimeOptions): Promise<RecordLifecycleActionHeartbeatResponse>;
-    /**
-      * Prolongs a lifecycle hook for Elastic Compute Service (ECS) instances.
-      *
-      * @param request RecordLifecycleActionHeartbeatRequest
-      * @return RecordLifecycleActionHeartbeatResponse
-     */
     recordLifecycleActionHeartbeat(request: RecordLifecycleActionHeartbeatRequest): Promise<RecordLifecycleActionHeartbeatResponse>;
-    /**
-      * *   Before you call this operation, make sure that the following requirements are met:
-      *     *   The scaling group is in the Active state.
-      *     *   No scaling activity is in progress within the scaling group.
-      * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
-      * *   If an ECS instance is automatically created by Auto Scaling, or if an ECS instance is manually added to a scaling group and managed by the scaling group, the ECS instance is stopped in economical mode or is released after the instance is removed from the scaling group.
-      * *   If an ECS instance is manually added to a scaling group and is not managed by the scaling group, the ECS instance is not stopped or released after the instance is removed from the scaling group.
-      * *   If the difference between the number of existing ECS instances specified by the TotalCapacity parameter and the number of ECS instances that you call this operation to remove is less than the value of the MinSize parameter, the call fails.
-      * A successful call only means that Auto Scaling accepts the request. The scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
-      *
-      * @param request RemoveInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return RemoveInstancesResponse
-     */
     removeInstancesWithOptions(request: RemoveInstancesRequest, runtime: $Util.RuntimeOptions): Promise<RemoveInstancesResponse>;
-    /**
-      * *   Before you call this operation, make sure that the following requirements are met:
-      *     *   The scaling group is in the Active state.
-      *     *   No scaling activity is in progress within the scaling group.
-      * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
-      * *   If an ECS instance is automatically created by Auto Scaling, or if an ECS instance is manually added to a scaling group and managed by the scaling group, the ECS instance is stopped in economical mode or is released after the instance is removed from the scaling group.
-      * *   If an ECS instance is manually added to a scaling group and is not managed by the scaling group, the ECS instance is not stopped or released after the instance is removed from the scaling group.
-      * *   If the difference between the number of existing ECS instances specified by the TotalCapacity parameter and the number of ECS instances that you call this operation to remove is less than the value of the MinSize parameter, the call fails.
-      * A successful call only means that Auto Scaling accepts the request. The scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
-      *
-      * @param request RemoveInstancesRequest
-      * @return RemoveInstancesResponse
-     */
     removeInstances(request: RemoveInstancesRequest): Promise<RemoveInstancesResponse>;
     resumeProcessesWithOptions(request: ResumeProcessesRequest, runtime: $Util.RuntimeOptions): Promise<ResumeProcessesResponse>;
     resumeProcesses(request: ResumeProcessesRequest): Promise<ResumeProcessesResponse>;
     /**
-      * 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:
-      *     *   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 ID of the scaling activity.
       *
       * @param request ScaleWithAdjustmentRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7702,14 +7342,7 @@ export default class Client extends OpenApi {
      */
     scaleWithAdjustmentWithOptions(request: ScaleWithAdjustmentRequest, runtime: $Util.RuntimeOptions): Promise<ScaleWithAdjustmentResponse>;
     /**
-      * 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:
-      *     *   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 ID of the scaling activity.
       *
       * @param request ScaleWithAdjustmentRequest
       * @return ScaleWithAdjustmentResponse
@@ -7717,35 +7350,9 @@ export default class Client extends OpenApi {
     scaleWithAdjustment(request: ScaleWithAdjustmentRequest): Promise<ScaleWithAdjustmentResponse>;
     setGroupDeletionProtectionWithOptions(request: SetGroupDeletionProtectionRequest, runtime: $Util.RuntimeOptions): Promise<SetGroupDeletionProtectionResponse>;
     setGroupDeletionProtection(request: SetGroupDeletionProtectionRequest): Promise<SetGroupDeletionProtectionResponse>;
-    /**
-      * Configures the health check feature for Elastic Compute Service (ECS) instances.
-      *
-      * @param request SetInstanceHealthRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return SetInstanceHealthResponse
-     */
     setInstanceHealthWithOptions(request: SetInstanceHealthRequest, runtime: $Util.RuntimeOptions): Promise<SetInstanceHealthResponse>;
-    /**
-      * Configures the health check feature for Elastic Compute Service (ECS) instances.
-      *
-      * @param request SetInstanceHealthRequest
-      * @return SetInstanceHealthResponse
-     */
     setInstanceHealth(request: SetInstanceHealthRequest): Promise<SetInstanceHealthResponse>;
-    /**
-      * Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
-      *
-      * @param request SetInstancesProtectionRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return SetInstancesProtectionResponse
-     */
     setInstancesProtectionWithOptions(request: SetInstancesProtectionRequest, runtime: $Util.RuntimeOptions): Promise<SetInstancesProtectionResponse>;
-    /**
-      * Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
-      *
-      * @param request SetInstancesProtectionRequest
-      * @return SetInstancesProtectionResponse
-     */
     setInstancesProtection(request: SetInstancesProtectionRequest): Promise<SetInstancesProtectionResponse>;
     suspendProcessesWithOptions(request: SuspendProcessesRequest, runtime: $Util.RuntimeOptions): Promise<SuspendProcessesResponse>;
     suspendProcesses(request: SuspendProcessesRequest): Promise<SuspendProcessesResponse>;