@alicloud/ess20220222 1.5.2 → 1.5.3

package/dist/client.js

@@ -38,7 +38,6 @@ exports.ModifyScalingConfigurationRequestPrivatePoolOptions = exports.ModifyScal
 exports.TagResourcesRequestTags = exports.ScaleWithAdjustmentRequestOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverridesEnvironmentVars = exports.ScaleWithAdjustmentRequestLifecycleHookContext = exports.ModifyScalingRuleRequestStepAdjustments = exports.ModifyScalingRuleRequestAlarmDimensions = exports.ModifyScalingGroupRequestLaunchTemplateOverrides = exports.ModifyScalingConfigurationShrinkRequestSpotPriceLimits = exports.ModifyScalingConfigurationShrinkRequestNetworkInterfaces = exports.ModifyScalingConfigurationShrinkRequestInstanceTypeOverrides = exports.ModifyScalingConfigurationShrinkRequestInstancePatternInfos = exports.ModifyScalingConfigurationShrinkRequestDataDisks = exports.ModifyScalingConfigurationShrinkRequestCustomPriorities = exports.ModifyScalingConfigurationShrinkRequestSystemDisk = exports.ModifyScalingConfigurationShrinkRequestPrivatePoolOptions = exports.ModifyScalingConfigurationShrinkRequestImageOptions = exports.ModifyScalingConfigurationRequestSpotPriceLimits = exports.ModifyScalingConfigurationRequestNetworkInterfaces = exports.ModifyScalingConfigurationRequestInstanceTypeOverrides = exports.ModifyScalingConfigurationRequestInstancePatternInfos = exports.ModifyScalingConfigurationRequestDataDisks = exports.ModifyScalingConfigurationRequestCustomPriorities = exports.ModifyScalingConfigurationRequestSystemDisk = void 0;
 // This file is auto-generated, don't edit it
 /**
- *
  */
 const tea_util_1 = __importStar(require("@alicloud/tea-util")), $Util = tea_util_1;
 const openapi_client_1 = __importStar(require("@alicloud/openapi-client")), $OpenApi = openapi_client_1;
@@ -1020,6 +1019,7 @@ class CreateNotificationConfigurationRequest extends $tea.Model {
             regionId: 'RegionId',
             resourceOwnerAccount: 'ResourceOwnerAccount',
             scalingGroupId: 'ScalingGroupId',
+            timeZone: 'TimeZone',
         };
     }
     static types() {
@@ -1030,6 +1030,7 @@ class CreateNotificationConfigurationRequest extends $tea.Model {
             regionId: 'string',
             resourceOwnerAccount: 'string',
             scalingGroupId: 'string',
+            timeZone: 'string',
         };
     }
     constructor(map) {
@@ -5170,6 +5171,7 @@ class ModifyNotificationConfigurationRequest extends $tea.Model {
             regionId: 'RegionId',
             resourceOwnerAccount: 'ResourceOwnerAccount',
             scalingGroupId: 'ScalingGroupId',
+            timeZone: 'TimeZone',
         };
     }
     static types() {
@@ -5180,6 +5182,7 @@ class ModifyNotificationConfigurationRequest extends $tea.Model {
             regionId: 'string',
             resourceOwnerAccount: 'string',
             scalingGroupId: 'string',
+            timeZone: 'string',
         };
     }
     constructor(map) {
@@ -9587,6 +9590,7 @@ class DescribeNotificationConfigurationsResponseBodyNotificationConfigurationMod
             notificationArn: 'NotificationArn',
             notificationTypes: 'NotificationTypes',
             scalingGroupId: 'ScalingGroupId',
+            timeZone: 'TimeZone',
         };
     }
     static types() {
@@ -9594,6 +9598,7 @@ class DescribeNotificationConfigurationsResponseBodyNotificationConfigurationMod
             notificationArn: 'string',
             notificationTypes: { 'type': 'array', 'itemType': 'string' },
             scalingGroupId: 'string',
+            timeZone: 'string',
         };
     }
     constructor(map) {
@@ -12576,15 +12581,16 @@ class Client extends openapi_client_1.default {
         return endpoint_util_1.default.getEndpointRules(productId, regionId, endpointRule, network, suffix);
     }
     /**
-     * @summary Applies a scaling configuration of the Elastic Container Instance type. If you want to create and manage scaling configurations of the Elastic Container Instance type by using a configuration file, you can call the ApplyEciScalingConfiguration operation.
+     * Applies a scaling configuration of the Elastic Container Instance type. If you want to create and manage scaling configurations of the Elastic Container Instance type by using a configuration file, you can call the ApplyEciScalingConfiguration operation.
      *
-     * @description Before you use a YAML configuration file to manage scaling configurations of the Elastic Container Instance type, you must take note of the following items:
+     * @remarks
+     * Before you use a YAML configuration file to manage scaling configurations of the Elastic Container Instance type, you must take note of the following items:
      * *   If you include a scaling configuration ID within your request, the system updates the scaling configuration based on the YAML configuration file.
      * *   If you do not include a scaling configuration ID within your request, the system creates a scaling configuration of the Elastic Container Instance type based on the YAML configuration file.
      *
-     * @param request ApplyEciScalingConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ApplyEciScalingConfigurationResponse
+     * @param request - ApplyEciScalingConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ApplyEciScalingConfigurationResponse
      */
     async applyEciScalingConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -12621,23 +12627,25 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ApplyEciScalingConfigurationResponse({}));
     }
     /**
-     * @summary Applies a scaling configuration of the Elastic Container Instance type. If you want to create and manage scaling configurations of the Elastic Container Instance type by using a configuration file, you can call the ApplyEciScalingConfiguration operation.
+     * Applies a scaling configuration of the Elastic Container Instance type. If you want to create and manage scaling configurations of the Elastic Container Instance type by using a configuration file, you can call the ApplyEciScalingConfiguration operation.
      *
-     * @description Before you use a YAML configuration file to manage scaling configurations of the Elastic Container Instance type, you must take note of the following items:
+     * @remarks
+     * Before you use a YAML configuration file to manage scaling configurations of the Elastic Container Instance type, you must take note of the following items:
      * *   If you include a scaling configuration ID within your request, the system updates the scaling configuration based on the YAML configuration file.
      * *   If you do not include a scaling configuration ID within your request, the system creates a scaling configuration of the Elastic Container Instance type based on the YAML configuration file.
      *
-     * @param request ApplyEciScalingConfigurationRequest
-     * @return ApplyEciScalingConfigurationResponse
+     * @param request - ApplyEciScalingConfigurationRequest
+     * @returns ApplyEciScalingConfigurationResponse
      */
     async applyEciScalingConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.applyEciScalingConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary 基于yaml配置进行弹性伸缩管理
+     * Creates and manages scaling groups by using configuration files. You can call the ApplyScalingGroup operation to create and manage scaling groups by using configuration files with efficiency.
      *
-     * @description You can call the ApplyScalingGroup operation to create scaling groups of the Elastic Container Instance type with ease. The resources of the scaling groups are defined in Kubernetes Deployment YAML files. You can also call this operation to extend annotations for elastic container instances in Kubernetes Deployment YAML files. For more information, see "Supported annotations" in this topic.
+     * @remarks
+     * You can call the ApplyScalingGroup operation to create scaling groups of the Elastic Container Instance type with ease. The resources of the scaling groups are defined in Kubernetes Deployment YAML files. You can also call this operation to extend annotations for elastic container instances in Kubernetes Deployment YAML files. For more information, see "Supported annotations" in this topic.
      * Mapping between YAML files and scaling groups: You can map the triplet of namespace, kind, and name in a YAML file to a scaling group name. A YAML file and a scaling group have a one-to-one mapping relationship in a region. For example, if you use the Kubernetes Deployment YAML file whose name is NGINX in the default namespace to create a scaling group in a region, the unique name of the mapped scaling group is k8s_default_Deployment_nginx.
      * You can use a Kubernetes Deployment YAML file to manage a scaling group based on the following logic:
      * * If an existing scaling group has a mapping relationship with your Kubernetes Deployment YAML file, you can update the scaling group by using the YAML file.
@@ -12671,9 +12679,9 @@ class Client extends openapi_client_1.default {
      * If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
      * |k8s.aliyun.com/eci-custom-tags|"env:test,name:alice"|The tags that you want to add to each elastic container instance. You can add up to three tags for each elastic container instance. Separate a tag key and a tag value with a colon (:). Separate multiple tags with commas (,).|
      *
-     * @param request ApplyScalingGroupRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ApplyScalingGroupResponse
+     * @param request - ApplyScalingGroupRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ApplyScalingGroupResponse
      */
     async applyScalingGroupWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -12704,9 +12712,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ApplyScalingGroupResponse({}));
     }
     /**
-     * @summary 基于yaml配置进行弹性伸缩管理
+     * Creates and manages scaling groups by using configuration files. You can call the ApplyScalingGroup operation to create and manage scaling groups by using configuration files with efficiency.
      *
-     * @description You can call the ApplyScalingGroup operation to create scaling groups of the Elastic Container Instance type with ease. The resources of the scaling groups are defined in Kubernetes Deployment YAML files. You can also call this operation to extend annotations for elastic container instances in Kubernetes Deployment YAML files. For more information, see "Supported annotations" in this topic.
+     * @remarks
+     * You can call the ApplyScalingGroup operation to create scaling groups of the Elastic Container Instance type with ease. The resources of the scaling groups are defined in Kubernetes Deployment YAML files. You can also call this operation to extend annotations for elastic container instances in Kubernetes Deployment YAML files. For more information, see "Supported annotations" in this topic.
      * Mapping between YAML files and scaling groups: You can map the triplet of namespace, kind, and name in a YAML file to a scaling group name. A YAML file and a scaling group have a one-to-one mapping relationship in a region. For example, if you use the Kubernetes Deployment YAML file whose name is NGINX in the default namespace to create a scaling group in a region, the unique name of the mapped scaling group is k8s_default_Deployment_nginx.
      * You can use a Kubernetes Deployment YAML file to manage a scaling group based on the following logic:
      * * If an existing scaling group has a mapping relationship with your Kubernetes Deployment YAML file, you can update the scaling group by using the YAML file.
@@ -12740,23 +12749,24 @@ class Client extends openapi_client_1.default {
      * If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
      * |k8s.aliyun.com/eci-custom-tags|"env:test,name:alice"|The tags that you want to add to each elastic container instance. You can add up to three tags for each elastic container instance. Separate a tag key and a tag value with a colon (:). Separate multiple tags with commas (,).|
      *
-     * @param request ApplyScalingGroupRequest
-     * @return ApplyScalingGroupResponse
+     * @param request - ApplyScalingGroupRequest
+     * @returns ApplyScalingGroupResponse
      */
     async applyScalingGroup(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.applyScalingGroupWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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 call the operation to attach an ALB server group to your scaling group, make sure that the following requirements are met:
+     * @remarks
+     * 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.
      *
-     * @param request AttachAlbServerGroupsRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return AttachAlbServerGroupsResponse
+     * @param request - AttachAlbServerGroupsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns AttachAlbServerGroupsResponse
      */
     async attachAlbServerGroupsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -12799,31 +12809,33 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new AttachAlbServerGroupsResponse({}));
     }
     /**
-     * @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.
+     * 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 call the operation to attach an ALB server group to your scaling group, make sure that the following requirements are met:
+     * @remarks
+     * 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.
      *
-     * @param request AttachAlbServerGroupsRequest
-     * @return AttachAlbServerGroupsResponse
+     * @param request - AttachAlbServerGroupsRequest
+     * @returns AttachAlbServerGroupsResponse
      */
     async attachAlbServerGroups(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.attachAlbServerGroupsWithOptions(request, runtime);
     }
     /**
-     * @summary Associates one or more ApsaraDB RDS instances with a scaling group.
+     * Associates one or more ApsaraDB RDS instances with a scaling group.
      *
-     * @description Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
+     * @remarks
+     * Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
      * *   The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
      * *   The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](https://help.aliyun.com/document_detail/41872.html).
      * *   The ApsaraDB RDS instance must be in the Running state.
      * After an ApsaraDB RDS instance is associated with the scaling group, the default IP address whitelist of the ApsaraDB RDS instance can contain no more than 1,000 IP addresses. For more information, see [Set the whitelist](https://help.aliyun.com/document_detail/43185.html).
      *
-     * @param request AttachDBInstancesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return AttachDBInstancesResponse
+     * @param request - AttachDBInstancesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns AttachDBInstancesResponse
      */
     async attachDBInstancesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -12872,25 +12884,27 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new AttachDBInstancesResponse({}));
     }
     /**
-     * @summary Associates one or more ApsaraDB RDS instances with a scaling group.
+     * Associates one or more ApsaraDB RDS instances with a scaling group.
      *
-     * @description Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
+     * @remarks
+     * Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
      * *   The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
      * *   The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](https://help.aliyun.com/document_detail/41872.html).
      * *   The ApsaraDB RDS instance must be in the Running state.
      * After an ApsaraDB RDS instance is associated with the scaling group, the default IP address whitelist of the ApsaraDB RDS instance can contain no more than 1,000 IP addresses. For more information, see [Set the whitelist](https://help.aliyun.com/document_detail/43185.html).
      *
-     * @param request AttachDBInstancesRequest
-     * @return AttachDBInstancesResponse
+     * @param request - AttachDBInstancesRequest
+     * @returns AttachDBInstancesResponse
      */
     async attachDBInstances(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.attachDBInstancesWithOptions(request, runtime);
     }
     /**
-     * @summary Adds instances to a scaling group to provide services or restarts Elastic Compute Service (ECS) instances stopped in Economical Mode to provide services. You can call the AttachInstances operation to add ECS instances, elastic container instances, or third-party instances managed by Alibaba Cloud to your scaling group to provide services. You can also call this operation to restart ECS instances stopped in Economical Mode in your scaling group to provide services.
+     * Adds instances to a scaling group to provide services or restarts Elastic Compute Service (ECS) instances stopped in Economical Mode to provide services. You can call the AttachInstances operation to add ECS instances, elastic container instances, or third-party instances managed by Alibaba Cloud to your scaling group to provide services. You can also call this operation to restart ECS instances stopped in Economical Mode in your scaling group to provide services.
      *
-     * @description Before you call this operation, take note of the following items:
+     * @remarks
+     * 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.
      * The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
@@ -12905,9 +12919,9 @@ class Client extends openapi_client_1.default {
      * If the sum of the number of instances that you want to add and the number of existing instances in the scaling group is greater than the value of the MaxSize parameter, the call fails.
      * Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
      *
-     * @param request AttachInstancesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return AttachInstancesResponse
+     * @param request - AttachInstancesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns AttachInstancesResponse
      */
     async attachInstancesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -12962,9 +12976,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new AttachInstancesResponse({}));
     }
     /**
-     * @summary Adds instances to a scaling group to provide services or restarts Elastic Compute Service (ECS) instances stopped in Economical Mode to provide services. You can call the AttachInstances operation to add ECS instances, elastic container instances, or third-party instances managed by Alibaba Cloud to your scaling group to provide services. You can also call this operation to restart ECS instances stopped in Economical Mode in your scaling group to provide services.
+     * Adds instances to a scaling group to provide services or restarts Elastic Compute Service (ECS) instances stopped in Economical Mode to provide services. You can call the AttachInstances operation to add ECS instances, elastic container instances, or third-party instances managed by Alibaba Cloud to your scaling group to provide services. You can also call this operation to restart ECS instances stopped in Economical Mode in your scaling group to provide services.
      *
-     * @description Before you call this operation, take note of the following items:
+     * @remarks
+     * 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.
      * The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
@@ -12979,17 +12994,18 @@ class Client extends openapi_client_1.default {
      * If the sum of the number of instances that you want to add and the number of existing instances in the scaling group is greater than the value of the MaxSize parameter, the call fails.
      * Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
      *
-     * @param request AttachInstancesRequest
-     * @return AttachInstancesResponse
+     * @param request - AttachInstancesRequest
+     * @returns AttachInstancesResponse
      */
     async attachInstances(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.attachInstancesWithOptions(request, runtime);
     }
     /**
-     * @summary Attaches load balancers to a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups. Load balancers help distribute the access traffic to the instances in scaling groups, which effectively improves the service performance of the scaling groups. You can call the AttachLoadBalancers operation to attach one or more load balancers to your scaling group.
+     * Attaches load balancers to a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups. Load balancers help distribute the access traffic to the instances in scaling groups, which effectively improves the service performance of the scaling groups. You can call the AttachLoadBalancers operation to attach one or more load balancers to your scaling group.
      *
-     * @description Before you call this operation, make sure that the following requirements are met:
+     * @remarks
+     * Before you call this operation, make sure that the following requirements are met:
      * *   The load balancer and the scaling group belong to the same Alibaba Cloud account and region.
      * *   The load balancer is in the `Running` state.
      * *   At least one listener is configured for the load balancer, and the health check feature is enabled for the load balancer.
@@ -12997,9 +13013,9 @@ class Client extends openapi_client_1.default {
      * *   If the network type of the scaling group is VPC, and that of the load balancer is classic network and a backend server of the load balancer uses a VPC, the scaling group and the backend server use the same VPC.
      * *   The attachment of load balancers ensures that the cumulative number of load balancers attached to the scaling group stays within the predefined maximum limit. For information about the load balancer quota, see [Limits](https://help.aliyun.com/document_detail/25863.html).
      *
-     * @param request AttachLoadBalancersRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return AttachLoadBalancersResponse
+     * @param request - AttachLoadBalancersRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns AttachLoadBalancersResponse
      */
     async attachLoadBalancersWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -13045,9 +13061,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new AttachLoadBalancersResponse({}));
     }
     /**
-     * @summary Attaches load balancers to a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups. Load balancers help distribute the access traffic to the instances in scaling groups, which effectively improves the service performance of the scaling groups. You can call the AttachLoadBalancers operation to attach one or more load balancers to your scaling group.
+     * Attaches load balancers to a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups. Load balancers help distribute the access traffic to the instances in scaling groups, which effectively improves the service performance of the scaling groups. You can call the AttachLoadBalancers operation to attach one or more load balancers to your scaling group.
      *
-     * @description Before you call this operation, make sure that the following requirements are met:
+     * @remarks
+     * Before you call this operation, make sure that the following requirements are met:
      * *   The load balancer and the scaling group belong to the same Alibaba Cloud account and region.
      * *   The load balancer is in the `Running` state.
      * *   At least one listener is configured for the load balancer, and the health check feature is enabled for the load balancer.
@@ -13055,19 +13072,19 @@ class Client extends openapi_client_1.default {
      * *   If the network type of the scaling group is VPC, and that of the load balancer is classic network and a backend server of the load balancer uses a VPC, the scaling group and the backend server use the same VPC.
      * *   The attachment of load balancers ensures that the cumulative number of load balancers attached to the scaling group stays within the predefined maximum limit. For information about the load balancer quota, see [Limits](https://help.aliyun.com/document_detail/25863.html).
      *
-     * @param request AttachLoadBalancersRequest
-     * @return AttachLoadBalancersResponse
+     * @param request - AttachLoadBalancersRequest
+     * @returns AttachLoadBalancersResponse
      */
     async attachLoadBalancers(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.attachLoadBalancersWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return AttachServerGroupsResponse
+     * @param request - AttachServerGroupsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns AttachServerGroupsResponse
      */
     async attachServerGroupsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -13110,19 +13127,20 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new AttachServerGroupsResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - AttachServerGroupsRequest
+     * @returns AttachServerGroupsResponse
      */
     async attachServerGroups(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.attachServerGroupsWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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:
+     * @remarks
+     *   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.
@@ -13138,9 +13156,9 @@ class Client extends openapi_client_1.default {
      *     **
      *     **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
-     * @return AttachVServerGroupsResponse
+     * @param request - AttachVServerGroupsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns AttachVServerGroupsResponse
      */
     async attachVServerGroupsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -13183,9 +13201,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new AttachVServerGroupsResponse({}));
     }
     /**
-     * @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.
+     * 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:
+     * @remarks
+     *   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.
@@ -13201,22 +13220,23 @@ class Client extends openapi_client_1.default {
      *     **
      *     **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
+     * @param request - AttachVServerGroupsRequest
+     * @returns AttachVServerGroupsResponse
      */
     async attachVServerGroups(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.attachVServerGroupsWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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.
+     * @remarks
+     *   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
-     * @return ChangeResourceGroupResponse
+     * @param request - ChangeResourceGroupRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ChangeResourceGroupResponse
      */
     async changeResourceGroupWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -13256,26 +13276,28 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ChangeResourceGroupResponse({}));
     }
     /**
-     * @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.
+     * 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.
+     * @remarks
+     *   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
+     * @param request - ChangeResourceGroupRequest
+     * @returns ChangeResourceGroupResponse
      */
     async changeResourceGroup(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.changeResourceGroupWithOptions(request, runtime);
     }
     /**
-     * @summary Ends the timeout period of a lifecycle hook ahead of schedule. If you have created a lifecycle hook for your scaling group, you can call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule based on your business requirements.
+     * Ends the timeout period of a lifecycle hook ahead of schedule. If you have created a lifecycle hook for your scaling group, you can call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule based on your business requirements.
      *
-     * @description When you manually cut short the timeout period of a lifecycle hook, Auto Scaling proceeds with one of the following actions based on the predefined settings: responding to the scaling request, aborting the scaling request, and initiating a rollback process.
+     * @remarks
+     * When you manually cut short the timeout period of a lifecycle hook, Auto Scaling proceeds with one of the following actions based on the predefined settings: responding to the scaling request, aborting the scaling request, and initiating a rollback process.
      *
-     * @param request CompleteLifecycleActionRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return CompleteLifecycleActionResponse
+     * @param request - CompleteLifecycleActionRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns CompleteLifecycleActionResponse
      */
     async completeLifecycleActionWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -13321,29 +13343,31 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CompleteLifecycleActionResponse({}));
     }
     /**
-     * @summary Ends the timeout period of a lifecycle hook ahead of schedule. If you have created a lifecycle hook for your scaling group, you can call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule based on your business requirements.
+     * Ends the timeout period of a lifecycle hook ahead of schedule. If you have created a lifecycle hook for your scaling group, you can call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule based on your business requirements.
      *
-     * @description When you manually cut short the timeout period of a lifecycle hook, Auto Scaling proceeds with one of the following actions based on the predefined settings: responding to the scaling request, aborting the scaling request, and initiating a rollback process.
+     * @remarks
+     * When you manually cut short the timeout period of a lifecycle hook, Auto Scaling proceeds with one of the following actions based on the predefined settings: responding to the scaling request, aborting the scaling request, and initiating a rollback process.
      *
-     * @param request CompleteLifecycleActionRequest
-     * @return CompleteLifecycleActionResponse
+     * @param request - CompleteLifecycleActionRequest
+     * @returns CompleteLifecycleActionResponse
      */
     async completeLifecycleAction(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.completeLifecycleActionWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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 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).
+     * @remarks
+     *   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
-     * @return CreateAlarmResponse
+     * @param request - CreateAlarmRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns CreateAlarmResponse
      */
     async createAlarmWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -13422,30 +13446,32 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CreateAlarmResponse({}));
     }
     /**
-     * @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.
+     * 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 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).
+     * @remarks
+     *   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
+     * @param request - CreateAlarmRequest
+     * @returns CreateAlarmResponse
      */
     async createAlarm(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.createAlarmWithOptions(request, runtime);
     }
     /**
-     * @summary Creates a scaling configuration of the Elastic Container Instance type. Auto Scaling uses the scaling configuration as a template to create elastic container instances to meet your business requirements during scale-outs.
+     * Creates a scaling configuration of the Elastic Container Instance type. Auto Scaling uses the scaling configuration as a template to create elastic container instances to meet your business requirements during scale-outs.
      *
-     * @description A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
+     * @remarks
+     * A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
      * You can specify the Cpu and Memory parameters to determine the range of instance types. If you specify the parameters, Auto Scaling determines the available instance types based on factors such as I/O optimization requirements and zones. Auto Scaling preferentially creates elastic container instances of the instance type that is provided at the lowest price. This scaling mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
      *
-     * @param request CreateEciScalingConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return CreateEciScalingConfigurationResponse
+     * @param request - CreateEciScalingConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns CreateEciScalingConfigurationResponse
      */
     async createEciScalingConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -13614,29 +13640,31 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CreateEciScalingConfigurationResponse({}));
     }
     /**
-     * @summary Creates a scaling configuration of the Elastic Container Instance type. Auto Scaling uses the scaling configuration as a template to create elastic container instances to meet your business requirements during scale-outs.
+     * Creates a scaling configuration of the Elastic Container Instance type. Auto Scaling uses the scaling configuration as a template to create elastic container instances to meet your business requirements during scale-outs.
      *
-     * @description A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
+     * @remarks
+     * A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
      * You can specify the Cpu and Memory parameters to determine the range of instance types. If you specify the parameters, Auto Scaling determines the available instance types based on factors such as I/O optimization requirements and zones. Auto Scaling preferentially creates elastic container instances of the instance type that is provided at the lowest price. This scaling mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
      *
-     * @param request CreateEciScalingConfigurationRequest
-     * @return CreateEciScalingConfigurationResponse
+     * @param request - CreateEciScalingConfigurationRequest
+     * @returns CreateEciScalingConfigurationResponse
      */
     async createEciScalingConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.createEciScalingConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary Creates one or more lifecycle hooks in a scaling group. A lifecycle hook allows you to execute custom actions like sending notifications or automating script execution at critical stages (such as instance startup and termination) in the lifecycle of an instance. Implementing the lifecycle hook feature allows for finer control and management of instances. For example, you can verify configurations, set up custom tasks, or back up data on your instances when lifecycle hooks take effect, thus enhancing the flexibility and reliability of application deployment.
+     * Creates one or more lifecycle hooks in a scaling group. A lifecycle hook allows you to execute custom actions like sending notifications or automating script execution at critical stages (such as instance startup and termination) in the lifecycle of an instance. Implementing the lifecycle hook feature allows for finer control and management of instances. For example, you can verify configurations, set up custom tasks, or back up data on your instances when lifecycle hooks take effect, thus enhancing the flexibility and reliability of application deployment.
      *
-     * @description You can create up to six lifecycle hooks for each scaling group. After a lifecycle hook is created for a scaling group, Elastic Compute Service (ECS) instances in the scaling group waits to be added to or removed from the scaling group during scaling activities. You can use the HeartbeatTimeout parameter to specify the timeout period of the lifecycle hook. During the timeout period of a lifecycle hook, you can perform custom operations such as initialize ECS instance configurations and download ECS instance data on the ECS instances for which the lifecycle hook is applied.
+     * @remarks
+     * You can create up to six lifecycle hooks for each scaling group. After a lifecycle hook is created for a scaling group, Elastic Compute Service (ECS) instances in the scaling group waits to be added to or removed from the scaling group during scaling activities. You can use the HeartbeatTimeout parameter to specify the timeout period of the lifecycle hook. During the timeout period of a lifecycle hook, you can perform custom operations such as initialize ECS instance configurations and download ECS instance data on the ECS instances for which the lifecycle hook is applied.
      * During a scale-out activity and the timeout period of a lifecycle hook, the private IP addresses of ECS instances wait to be added to the associated whitelist that manages access to the ApsaraDB RDS instance. The ECS instances also wait to be added to the backend server group of the associated Classic Load Balancer (CLB) instance. After the lifecycle hook times out, the private IP addresses of the ECS instances are added to the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances are also added to the backend server group of the associated CLB instance. During a scale-in activity and the timeout period of a lifecycle hook, the private IP addresses of ECS instances wait to be removed from the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances also wait to be removed from the backend server group of the associated CLB instance. After the lifecycle hook times out, the private IP addresses of the ECS instances are removed from the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances are also removed from the backend server group of the associated CLB instance.
      * You can configure a notification method for a lifecycle hook. When the lifecycle hook is triggered, a notification can be sent to the specified Message Service (MNS) topic or queue, or an operation can be performed based on the specified Operation Orchestration Service (OOS) template. If you want to configure an OOS template, you must create a Resource Access Management (RAM) role for OOS. For more information, see [Grant RAM permissions to OOS](https://help.aliyun.com/document_detail/120810.html).
      * > If your scaling group has existing ECS instances and you configured an OOS template that is used to add the private IP addresses of ECS instances to or remove the private IP addresses of ECS instances from the whitelists that manage access to cloud databases that are not ApsaraDB RDS databases, you must manually add the private IP addresses of the ECS instances to or remove the private IP addresses of the ECS instances from the whitelists that manage access to the cloud databases.
      *
-     * @param request CreateLifecycleHookRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return CreateLifecycleHookResponse
+     * @param request - CreateLifecycleHookRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns CreateLifecycleHookResponse
      */
     async createLifecycleHookWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -13688,29 +13716,31 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CreateLifecycleHookResponse({}));
     }
     /**
-     * @summary Creates one or more lifecycle hooks in a scaling group. A lifecycle hook allows you to execute custom actions like sending notifications or automating script execution at critical stages (such as instance startup and termination) in the lifecycle of an instance. Implementing the lifecycle hook feature allows for finer control and management of instances. For example, you can verify configurations, set up custom tasks, or back up data on your instances when lifecycle hooks take effect, thus enhancing the flexibility and reliability of application deployment.
+     * Creates one or more lifecycle hooks in a scaling group. A lifecycle hook allows you to execute custom actions like sending notifications or automating script execution at critical stages (such as instance startup and termination) in the lifecycle of an instance. Implementing the lifecycle hook feature allows for finer control and management of instances. For example, you can verify configurations, set up custom tasks, or back up data on your instances when lifecycle hooks take effect, thus enhancing the flexibility and reliability of application deployment.
      *
-     * @description You can create up to six lifecycle hooks for each scaling group. After a lifecycle hook is created for a scaling group, Elastic Compute Service (ECS) instances in the scaling group waits to be added to or removed from the scaling group during scaling activities. You can use the HeartbeatTimeout parameter to specify the timeout period of the lifecycle hook. During the timeout period of a lifecycle hook, you can perform custom operations such as initialize ECS instance configurations and download ECS instance data on the ECS instances for which the lifecycle hook is applied.
+     * @remarks
+     * You can create up to six lifecycle hooks for each scaling group. After a lifecycle hook is created for a scaling group, Elastic Compute Service (ECS) instances in the scaling group waits to be added to or removed from the scaling group during scaling activities. You can use the HeartbeatTimeout parameter to specify the timeout period of the lifecycle hook. During the timeout period of a lifecycle hook, you can perform custom operations such as initialize ECS instance configurations and download ECS instance data on the ECS instances for which the lifecycle hook is applied.
      * During a scale-out activity and the timeout period of a lifecycle hook, the private IP addresses of ECS instances wait to be added to the associated whitelist that manages access to the ApsaraDB RDS instance. The ECS instances also wait to be added to the backend server group of the associated Classic Load Balancer (CLB) instance. After the lifecycle hook times out, the private IP addresses of the ECS instances are added to the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances are also added to the backend server group of the associated CLB instance. During a scale-in activity and the timeout period of a lifecycle hook, the private IP addresses of ECS instances wait to be removed from the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances also wait to be removed from the backend server group of the associated CLB instance. After the lifecycle hook times out, the private IP addresses of the ECS instances are removed from the whitelist that manages access to the associated ApsaraDB RDS instance. The ECS instances are also removed from the backend server group of the associated CLB instance.
      * You can configure a notification method for a lifecycle hook. When the lifecycle hook is triggered, a notification can be sent to the specified Message Service (MNS) topic or queue, or an operation can be performed based on the specified Operation Orchestration Service (OOS) template. If you want to configure an OOS template, you must create a Resource Access Management (RAM) role for OOS. For more information, see [Grant RAM permissions to OOS](https://help.aliyun.com/document_detail/120810.html).
      * > If your scaling group has existing ECS instances and you configured an OOS template that is used to add the private IP addresses of ECS instances to or remove the private IP addresses of ECS instances from the whitelists that manage access to cloud databases that are not ApsaraDB RDS databases, you must manually add the private IP addresses of the ECS instances to or remove the private IP addresses of the ECS instances from the whitelists that manage access to the cloud databases.
      *
-     * @param request CreateLifecycleHookRequest
-     * @return CreateLifecycleHookResponse
+     * @param request - CreateLifecycleHookRequest
+     * @returns CreateLifecycleHookResponse
      */
     async createLifecycleHook(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.createLifecycleHookWithOptions(request, runtime);
     }
     /**
-     * @summary Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
+     * Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
      *
-     * @description ## Description
+     * @remarks
+     * ## Description
      * You can configure CloudMonitor system events, Message Service (MNS) queues, or MNS topics to receive notifications. When a specified type of scaling activity or resource change occurs in a scaling group, Auto Scaling sends notifications by using CloudMonitor or MNS.
      *
-     * @param request CreateNotificationConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return CreateNotificationConfigurationResponse
+     * @param request - CreateNotificationConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns CreateNotificationConfigurationResponse
      */
     async createNotificationConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -13733,6 +13763,9 @@ class Client extends openapi_client_1.default {
         if (!tea_util_1.default.isUnset(request.scalingGroupId)) {
             query["ScalingGroupId"] = request.scalingGroupId;
         }
+        if (!tea_util_1.default.isUnset(request.timeZone)) {
+            query["TimeZone"] = request.timeZone;
+        }
         let req = new $OpenApi.OpenApiRequest({
             query: openapi_util_1.default.query(query),
         });
@@ -13750,22 +13783,24 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CreateNotificationConfigurationResponse({}));
     }
     /**
-     * @summary Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
+     * Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
      *
-     * @description ## Description
+     * @remarks
+     * ## Description
      * You can configure CloudMonitor system events, Message Service (MNS) queues, or MNS topics to receive notifications. When a specified type of scaling activity or resource change occurs in a scaling group, Auto Scaling sends notifications by using CloudMonitor or MNS.
      *
-     * @param request CreateNotificationConfigurationRequest
-     * @return CreateNotificationConfigurationResponse
+     * @param request - CreateNotificationConfigurationRequest
+     * @returns CreateNotificationConfigurationResponse
      */
     async createNotificationConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.createNotificationConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary Creates a scaling configuration.
+     * Creates a scaling configuration.
      *
-     * @description Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
+     * @remarks
+     * 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 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.
@@ -13773,9 +13808,9 @@ class Client extends openapi_client_1.default {
      * *   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
-     * @return CreateScalingConfigurationResponse
+     * @param tmpReq - CreateScalingConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns CreateScalingConfigurationResponse
      */
     async createScalingConfigurationWithOptions(tmpReq, runtime) {
         tea_util_1.default.validateModel(tmpReq);
@@ -13973,9 +14008,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingConfigurationResponse({}));
     }
     /**
-     * @summary Creates a scaling configuration.
+     * Creates a scaling configuration.
      *
-     * @description Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
+     * @remarks
+     * 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 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.
@@ -13983,42 +14019,43 @@ class Client extends openapi_client_1.default {
      * *   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
+     * @param request - CreateScalingConfigurationRequest
+     * @returns CreateScalingConfigurationResponse
      */
     async createScalingConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.createScalingConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary Creates a scaling group. You can call the CreateScalingGroup operation to automate the adjustment of computing power of a specific type based on your business requirements and scaling polices.
+     * Creates a scaling group. You can call the CreateScalingGroup operation to automate the adjustment of computing power of a specific type based on your business requirements and scaling polices.
      *
-     * @description A scaling group is a group of Elastic Compute Service (ECS) instances that can be used for similar purposes.
+     * @remarks
+     * A scaling group is a group of Elastic Compute Service (ECS) instances that can be used for similar purposes.
      * You can create only a limited number of scaling groups in a region. To check the quota of the scaling groups, go to Quota Center.
      * A scaling group does not immediately take effect after you create the scaling group. You can call the [EnableScalingGroup](https://help.aliyun.com/document_detail/25939.html) operation to enable a scaling group. You can trigger scaling events and execute scaling rules only in scaling groups that are in the Enabled state.
      * If you want to attach a Classic Load Balancer (CLB, formerly known as SLB) instance and an ApsaraDB RDS instance to the scaling group that you want to create, the scaling group, the CLB instance, and the ApsaraDB RDS instance must reside in the same region. For more information, see [Regions and zones](https://help.aliyun.com/document_detail/40654.html).
-     * If you attach a CLB instance to the scaling group that you want to create, Auto Scaling will automatically add the ECS instances in the scaling group to the backend server groups of the CLB instance. You can specify the following types of server groups to add ECS instances:
+     * If you attach a CLB instance to the scaling group that you want to create, Auto Scaling automatically adds the ECS instances in the scaling group to the backend server groups of the CLB instance. You can specify the following types of server groups to add ECS instances:
      * *   Default server group: ECS instances in this group process frontend requests. If no listeners are configured for vServer groups or primary/secondary server groups, the frontend requests are forwarded to the ECS instances in the default server group.
-     * *   vServer group: If you want to forward different requests to different backend servers, or you want to forward requests based on domain names and URLs, you can specify vServer groups.
-     * >  If you specify both the default server group and multiple server groups simultaneously, Auto Scaling will add the ECS instances in your scaling group to these server groups concurrently.
+     * *   vServer group: If you want to forward different requests to different backend servers, or you want to forward requests based on domain names or URLs, you can specify vServer groups.
+     * >  If you specify both the default server group and multiple server groups simultaneously, Auto Scaling adds the ECS instances in your scaling group to these server groups concurrently.
      * The default weight of each ECS instance as a backend server is 50. If you want to attach a CLB instance to the scaling group that you want to create, make sure that the CLB instance meets the following requirements:
      * *   The CLB instance is in the Active state. You can call the [DescribeLoadBalancers](https://help.aliyun.com/document_detail/2401696.html) operation to query the status of CLB instances.
      * *   Health check must be enabled on all listener ports configured for the CLB instance. Otherwise, the scaling group will fail to be created.
-     * If you attach Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups to the scaling group that you want to create, Auto Scaling will add the ECS instances in your scaling group to the ALB or NLB server groups to process the access requests forwarded by the corresponding ALB or NLB instances. You can attach multiple ALB or NLB server groups to a scaling group. Make sure that the ALB or NLB server groups belong to the same virtual private cloud (VPC). For more information, see [AttachAlbServerGroups](https://help.aliyun.com/document_detail/266800.html) or [AttachServerGroups](https://help.aliyun.com/document_detail/600559.html).
-     * If you attach an ApsaraDB RDS instance to the scaling group that you want to create, Auto Scaling will automatically add the private IP addresses of the ECS instances in your scaling group to the IP address whitelist of the ApsaraDB RDS instance. Before you attach an ApsaraDB RDS instance to your scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
+     * If you attach Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups to the scaling group that you want to create, Auto Scaling adds the ECS instances in your scaling group to the ALB or NLB server groups to process the access requests forwarded by the corresponding ALB or NLB instances. You can attach multiple ALB or NLB server groups to a scaling group. Make sure that the ALB or NLB server groups belong to the same virtual private cloud (VPC). For more information, see [AttachAlbServerGroups](https://help.aliyun.com/document_detail/266800.html) or [AttachServerGroups](https://help.aliyun.com/document_detail/600535.html).
+     * If you attach an ApsaraDB RDS instance to the scaling group that you want to create, Auto Scaling automatically adds the private IP addresses of the ECS instances in your scaling group to the IP address whitelist of the ApsaraDB RDS instance. Before you attach an ApsaraDB RDS instance to your scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
      * *   The ApsaraDB RDS instance is in the Running state. You can call the [DescribeDBInstances](https://help.aliyun.com/document_detail/610396.html) state to query the status of ApsaraDB RDS instances.
      * *   The number of IP addresses in the IP address whitelist of the ApsaraDB RDS instance does not reach its upper limit. For more information, see [Configure a whitelist](https://help.aliyun.com/document_detail/43185.html).
      * If you set MultiAZPolicy for the scaling group that you want to create to COST_OPTIMIZED, the following rules apply:
-     * *   If you use OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, and SpotInstancePools to specify the instance allocation mode under the cost optimization policy, Auto Scaling will prioritize the implementation of the specified instance allocation mode during scale-out events.
-     * *   If you do not specify OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, or SpotInstancePools, Auto Scaling will preferentially create instances of the lowest-priced instance type based on the cost optimization policy.
+     * *   If you use OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, and SpotInstancePools to specify the instance allocation mode under the cost optimization policy, Auto Scaling prioritizes the implementation of the specified instance allocation mode during scale-out events.
+     * *   If you do not specify OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, or SpotInstancePools, Auto Scaling preferentially creates instances of the lowest-priced instance type based on the cost optimization policy.
      * If you set `Tags.Propagate` to true, the following rules will apply:
      * *   Tags that you add to the scaling group cannot be propagated to existing instances in the scaling group. Tags that you add to the scaling group are propagated to only new instances.
      * *   If you specify instance tags in the scaling configuration that is used to create instances and propagate the tags that you add to the scaling group to the instances, all tags exist at the same time.
      * *   If the tag key that you specify in a scaling configuration and the tag key that you add to the scaling group of the scaling configuration are the same, the tag value that you specify in the scaling configuration is preferentially used.
      *
-     * @param request CreateScalingGroupRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return CreateScalingGroupResponse
+     * @param request - CreateScalingGroupRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns CreateScalingGroupResponse
      */
     async createScalingGroupWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14175,42 +14212,44 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingGroupResponse({}));
     }
     /**
-     * @summary Creates a scaling group. You can call the CreateScalingGroup operation to automate the adjustment of computing power of a specific type based on your business requirements and scaling polices.
+     * Creates a scaling group. You can call the CreateScalingGroup operation to automate the adjustment of computing power of a specific type based on your business requirements and scaling polices.
      *
-     * @description A scaling group is a group of Elastic Compute Service (ECS) instances that can be used for similar purposes.
+     * @remarks
+     * A scaling group is a group of Elastic Compute Service (ECS) instances that can be used for similar purposes.
      * You can create only a limited number of scaling groups in a region. To check the quota of the scaling groups, go to Quota Center.
      * A scaling group does not immediately take effect after you create the scaling group. You can call the [EnableScalingGroup](https://help.aliyun.com/document_detail/25939.html) operation to enable a scaling group. You can trigger scaling events and execute scaling rules only in scaling groups that are in the Enabled state.
      * If you want to attach a Classic Load Balancer (CLB, formerly known as SLB) instance and an ApsaraDB RDS instance to the scaling group that you want to create, the scaling group, the CLB instance, and the ApsaraDB RDS instance must reside in the same region. For more information, see [Regions and zones](https://help.aliyun.com/document_detail/40654.html).
-     * If you attach a CLB instance to the scaling group that you want to create, Auto Scaling will automatically add the ECS instances in the scaling group to the backend server groups of the CLB instance. You can specify the following types of server groups to add ECS instances:
+     * If you attach a CLB instance to the scaling group that you want to create, Auto Scaling automatically adds the ECS instances in the scaling group to the backend server groups of the CLB instance. You can specify the following types of server groups to add ECS instances:
      * *   Default server group: ECS instances in this group process frontend requests. If no listeners are configured for vServer groups or primary/secondary server groups, the frontend requests are forwarded to the ECS instances in the default server group.
-     * *   vServer group: If you want to forward different requests to different backend servers, or you want to forward requests based on domain names and URLs, you can specify vServer groups.
-     * >  If you specify both the default server group and multiple server groups simultaneously, Auto Scaling will add the ECS instances in your scaling group to these server groups concurrently.
+     * *   vServer group: If you want to forward different requests to different backend servers, or you want to forward requests based on domain names or URLs, you can specify vServer groups.
+     * >  If you specify both the default server group and multiple server groups simultaneously, Auto Scaling adds the ECS instances in your scaling group to these server groups concurrently.
      * The default weight of each ECS instance as a backend server is 50. If you want to attach a CLB instance to the scaling group that you want to create, make sure that the CLB instance meets the following requirements:
      * *   The CLB instance is in the Active state. You can call the [DescribeLoadBalancers](https://help.aliyun.com/document_detail/2401696.html) operation to query the status of CLB instances.
      * *   Health check must be enabled on all listener ports configured for the CLB instance. Otherwise, the scaling group will fail to be created.
-     * If you attach Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups to the scaling group that you want to create, Auto Scaling will add the ECS instances in your scaling group to the ALB or NLB server groups to process the access requests forwarded by the corresponding ALB or NLB instances. You can attach multiple ALB or NLB server groups to a scaling group. Make sure that the ALB or NLB server groups belong to the same virtual private cloud (VPC). For more information, see [AttachAlbServerGroups](https://help.aliyun.com/document_detail/266800.html) or [AttachServerGroups](https://help.aliyun.com/document_detail/600559.html).
-     * If you attach an ApsaraDB RDS instance to the scaling group that you want to create, Auto Scaling will automatically add the private IP addresses of the ECS instances in your scaling group to the IP address whitelist of the ApsaraDB RDS instance. Before you attach an ApsaraDB RDS instance to your scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
+     * If you attach Application Load Balancer (ALB) or Network Load Balancer (NLB) server groups to the scaling group that you want to create, Auto Scaling adds the ECS instances in your scaling group to the ALB or NLB server groups to process the access requests forwarded by the corresponding ALB or NLB instances. You can attach multiple ALB or NLB server groups to a scaling group. Make sure that the ALB or NLB server groups belong to the same virtual private cloud (VPC). For more information, see [AttachAlbServerGroups](https://help.aliyun.com/document_detail/266800.html) or [AttachServerGroups](https://help.aliyun.com/document_detail/600535.html).
+     * If you attach an ApsaraDB RDS instance to the scaling group that you want to create, Auto Scaling automatically adds the private IP addresses of the ECS instances in your scaling group to the IP address whitelist of the ApsaraDB RDS instance. Before you attach an ApsaraDB RDS instance to your scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
      * *   The ApsaraDB RDS instance is in the Running state. You can call the [DescribeDBInstances](https://help.aliyun.com/document_detail/610396.html) state to query the status of ApsaraDB RDS instances.
      * *   The number of IP addresses in the IP address whitelist of the ApsaraDB RDS instance does not reach its upper limit. For more information, see [Configure a whitelist](https://help.aliyun.com/document_detail/43185.html).
      * If you set MultiAZPolicy for the scaling group that you want to create to COST_OPTIMIZED, the following rules apply:
-     * *   If you use OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, and SpotInstancePools to specify the instance allocation mode under the cost optimization policy, Auto Scaling will prioritize the implementation of the specified instance allocation mode during scale-out events.
-     * *   If you do not specify OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, or SpotInstancePools, Auto Scaling will preferentially create instances of the lowest-priced instance type based on the cost optimization policy.
+     * *   If you use OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, and SpotInstancePools to specify the instance allocation mode under the cost optimization policy, Auto Scaling prioritizes the implementation of the specified instance allocation mode during scale-out events.
+     * *   If you do not specify OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, or SpotInstancePools, Auto Scaling preferentially creates instances of the lowest-priced instance type based on the cost optimization policy.
      * If you set `Tags.Propagate` to true, the following rules will apply:
      * *   Tags that you add to the scaling group cannot be propagated to existing instances in the scaling group. Tags that you add to the scaling group are propagated to only new instances.
      * *   If you specify instance tags in the scaling configuration that is used to create instances and propagate the tags that you add to the scaling group to the instances, all tags exist at the same time.
      * *   If the tag key that you specify in a scaling configuration and the tag key that you add to the scaling group of the scaling configuration are the same, the tag value that you specify in the scaling configuration is preferentially used.
      *
-     * @param request CreateScalingGroupRequest
-     * @return CreateScalingGroupResponse
+     * @param request - CreateScalingGroupRequest
+     * @returns CreateScalingGroupResponse
      */
     async createScalingGroup(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.createScalingGroupWithOptions(request, runtime);
     }
     /**
-     * @summary Creates a scaling rule. The purpose of a scaling rule varies based on its type. You can use a scaling rule to trigger a scaling activity or adjust the boundary values for a scaling group. You can call the CreateScalingRule operation to create different types of scaling rules based on your business requirements. For example, if your business requires only automatic adjustment of the boundary values for your scaling group, you can call this operation to create a predictive scaling rule.
+     * Creates a scaling rule. The purpose of a scaling rule varies based on its type. You can use a scaling rule to trigger a scaling activity or adjust the boundary values for a scaling group. You can call the CreateScalingRule operation to create different types of scaling rules based on your business requirements. For example, if your business requires only automatic adjustment of the boundary values for your scaling group, you can call this operation to create a predictive scaling rule.
      *
-     * @description A scaling rule defines the specific scaling action. For example, you can use a scaling rule to define N instances to add or remove. If the execution of a scaling rule causes the total number of Elastic Compute Service (ECS) instances or elastic container instances in the scaling group to drop below the value of MinSize or to exceed the value of MaxSize, Auto Scaling adjusts the number of instances to add or remove, which ensures that the total number of instances stays within the valid range. Take note that Auto Scaling does not adjust the number of instances that you defined in the scaling rule. Examples:
+     * @remarks
+     * A scaling rule defines the specific scaling action. For example, you can use a scaling rule to define N instances to add or remove. If the execution of a scaling rule causes the total number of Elastic Compute Service (ECS) instances or elastic container instances in the scaling group to drop below the value of MinSize or to exceed the value of MaxSize, Auto Scaling adjusts the number of instances to add or remove, which ensures that the total number of instances stays within the valid range. Take note that Auto Scaling does not adjust the number of instances that you defined in the scaling rule. Examples:
      * *   The maximum number of instances (MaxSize) that can be contained in a scaling group is 3 and the current number of instances (Total Capacity) in the scaling group is 2. In this example, the Add3 scaling rule is created to add three ECS instances to the scaling group. However, after you execute Add3, Auto Scaling adds only one ECS instance to the scaling group. In addition, the number of ECS instances to add in the Add3 scaling rule remains unchanged.
      * *   The minimum number of instances (MinSize) that must be contained in a scaling group is 2 and the current number of instances (Total Capacity) is 3. In this example, the Remove5 scaling rule is created to remove five ECS instances from the scaling group. However, after you execute Remove5, Auto Scaling only removes one ECS instance from the scaling group. In addition, the number of ECS instances to remove in the Remove5 scaling rule remains unchanged.
      * Before you call this operation, take note of the following items:
@@ -14223,9 +14262,9 @@ class Client extends openapi_client_1.default {
      *     *   ExecuteScalingRule: You can call this operation to manually execute a 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 for a scaling rule. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule for which you want to create a scheduled task.
      *
-     * @param request CreateScalingRuleRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return CreateScalingRuleResponse
+     * @param request - CreateScalingRuleRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns CreateScalingRuleResponse
      */
     async createScalingRuleWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14319,9 +14358,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingRuleResponse({}));
     }
     /**
-     * @summary Creates a scaling rule. The purpose of a scaling rule varies based on its type. You can use a scaling rule to trigger a scaling activity or adjust the boundary values for a scaling group. You can call the CreateScalingRule operation to create different types of scaling rules based on your business requirements. For example, if your business requires only automatic adjustment of the boundary values for your scaling group, you can call this operation to create a predictive scaling rule.
+     * Creates a scaling rule. The purpose of a scaling rule varies based on its type. You can use a scaling rule to trigger a scaling activity or adjust the boundary values for a scaling group. You can call the CreateScalingRule operation to create different types of scaling rules based on your business requirements. For example, if your business requires only automatic adjustment of the boundary values for your scaling group, you can call this operation to create a predictive scaling rule.
      *
-     * @description A scaling rule defines the specific scaling action. For example, you can use a scaling rule to define N instances to add or remove. If the execution of a scaling rule causes the total number of Elastic Compute Service (ECS) instances or elastic container instances in the scaling group to drop below the value of MinSize or to exceed the value of MaxSize, Auto Scaling adjusts the number of instances to add or remove, which ensures that the total number of instances stays within the valid range. Take note that Auto Scaling does not adjust the number of instances that you defined in the scaling rule. Examples:
+     * @remarks
+     * A scaling rule defines the specific scaling action. For example, you can use a scaling rule to define N instances to add or remove. If the execution of a scaling rule causes the total number of Elastic Compute Service (ECS) instances or elastic container instances in the scaling group to drop below the value of MinSize or to exceed the value of MaxSize, Auto Scaling adjusts the number of instances to add or remove, which ensures that the total number of instances stays within the valid range. Take note that Auto Scaling does not adjust the number of instances that you defined in the scaling rule. Examples:
      * *   The maximum number of instances (MaxSize) that can be contained in a scaling group is 3 and the current number of instances (Total Capacity) in the scaling group is 2. In this example, the Add3 scaling rule is created to add three ECS instances to the scaling group. However, after you execute Add3, Auto Scaling adds only one ECS instance to the scaling group. In addition, the number of ECS instances to add in the Add3 scaling rule remains unchanged.
      * *   The minimum number of instances (MinSize) that must be contained in a scaling group is 2 and the current number of instances (Total Capacity) is 3. In this example, the Remove5 scaling rule is created to remove five ECS instances from the scaling group. However, after you execute Remove5, Auto Scaling only removes one ECS instance from the scaling group. In addition, the number of ECS instances to remove in the Remove5 scaling rule remains unchanged.
      * Before you call this operation, take note of the following items:
@@ -14334,17 +14374,18 @@ class Client extends openapi_client_1.default {
      *     *   ExecuteScalingRule: You can call this operation to manually execute a 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 for a scaling rule. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule for which you want to create a scheduled task.
      *
-     * @param request CreateScalingRuleRequest
-     * @return CreateScalingRuleResponse
+     * @param request - CreateScalingRuleRequest
+     * @returns CreateScalingRuleResponse
      */
     async createScalingRule(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.createScalingRuleWithOptions(request, runtime);
     }
     /**
-     * @summary Creates a scheduled task. A scheduled task is a type of scaling task that enables automatic execution of a specific scaling rule at a specified point in time. You can call the CreateScheduledTask operation to create a scheduled task to implement automatic scaling of computing resources. This ensures your business continuity and minimizes resource costs.
+     * Creates a scheduled task. A scheduled task is a type of scaling task that enables automatic execution of a specific scaling rule at a specified point in time. You can call the CreateScheduledTask operation to create a scheduled task to implement automatic scaling of computing resources. This ensures your business continuity and minimizes resource costs.
      *
-     * @description *   If the scaling rule of a scheduled task fails to be executed due to an ongoing scaling activity in the scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the time window specified by `LaunchExpirationTime`. If the scheduled task still fails after the specified time window ends, the task is automatically skipped.
+     * @remarks
+     *   If the scaling rule of a scheduled task fails to be executed due to an ongoing scaling activity in the scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the time window specified by `LaunchExpirationTime`. If the scheduled task still fails after the specified time window ends, the task is automatically skipped.
      * *   If several scheduled tasks concurrently attempt to execute the same scaling rule within a scaling group, the following rules apply:
      *     *   Scaling groups with **Expected Number of Instances** configured: The scaling activities incurred by the scheduled tasks are parallel scaling activities. In a proximate time window, Auto Scaling can trigger several scheduled tasks and then execute multiple parallel scaling activities at the same time.
      *     *   Scaling groups with **Expected Number of Instances** not configured: The scaling activity incurred by the earliest scheduled task is executed. Considering that a scaling group allows for no more than one ongoing scaling activity simultaneously, other scheduled tasks will spontaneously invoke retries within the time window specified by `LaunchExpirationTime`. Upon completion of the first scheduled task, any retries invoked by other tasks within the time window specified by `LaunchExpirationTime` lead to continuous enforcement of the scaling rule, with each iteration generating a distinct scaling activity.
@@ -14354,9 +14395,9 @@ class Client extends openapi_client_1.default {
      *     **
      *     **Note** You cannot specify ScheduledAction and ScalingGroupId at the same time.
      *
-     * @param request CreateScheduledTaskRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return CreateScheduledTaskResponse
+     * @param request - CreateScheduledTaskRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns CreateScheduledTaskResponse
      */
     async createScheduledTaskWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14429,9 +14470,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CreateScheduledTaskResponse({}));
     }
     /**
-     * @summary Creates a scheduled task. A scheduled task is a type of scaling task that enables automatic execution of a specific scaling rule at a specified point in time. You can call the CreateScheduledTask operation to create a scheduled task to implement automatic scaling of computing resources. This ensures your business continuity and minimizes resource costs.
+     * Creates a scheduled task. A scheduled task is a type of scaling task that enables automatic execution of a specific scaling rule at a specified point in time. You can call the CreateScheduledTask operation to create a scheduled task to implement automatic scaling of computing resources. This ensures your business continuity and minimizes resource costs.
      *
-     * @description *   If the scaling rule of a scheduled task fails to be executed due to an ongoing scaling activity in the scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the time window specified by `LaunchExpirationTime`. If the scheduled task still fails after the specified time window ends, the task is automatically skipped.
+     * @remarks
+     *   If the scaling rule of a scheduled task fails to be executed due to an ongoing scaling activity in the scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the time window specified by `LaunchExpirationTime`. If the scheduled task still fails after the specified time window ends, the task is automatically skipped.
      * *   If several scheduled tasks concurrently attempt to execute the same scaling rule within a scaling group, the following rules apply:
      *     *   Scaling groups with **Expected Number of Instances** configured: The scaling activities incurred by the scheduled tasks are parallel scaling activities. In a proximate time window, Auto Scaling can trigger several scheduled tasks and then execute multiple parallel scaling activities at the same time.
      *     *   Scaling groups with **Expected Number of Instances** not configured: The scaling activity incurred by the earliest scheduled task is executed. Considering that a scaling group allows for no more than one ongoing scaling activity simultaneously, other scheduled tasks will spontaneously invoke retries within the time window specified by `LaunchExpirationTime`. Upon completion of the first scheduled task, any retries invoked by other tasks within the time window specified by `LaunchExpirationTime` lead to continuous enforcement of the scaling rule, with each iteration generating a distinct scaling activity.
@@ -14441,21 +14483,22 @@ class Client extends openapi_client_1.default {
      *     **
      *     **Note** You cannot specify ScheduledAction and ScalingGroupId at the same time.
      *
-     * @param request CreateScheduledTaskRequest
-     * @return CreateScheduledTaskResponse
+     * @param request - CreateScheduledTaskRequest
+     * @returns CreateScheduledTaskResponse
      */
     async createScheduledTask(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.createScheduledTaskWithOptions(request, runtime);
     }
     /**
-     * @summary Deactivates a scaling configuration.
+     * Deactivates a scaling configuration.
      *
-     * @description *   You can call this operation to deactivate a scaling configuration only in a disabled scaling group.
+     * @remarks
+     *   You can call this operation to deactivate a scaling configuration only in a disabled scaling group.
      *
-     * @param request DeactivateScalingConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DeactivateScalingConfigurationResponse
+     * @param request - DeactivateScalingConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DeactivateScalingConfigurationResponse
      */
     async deactivateScalingConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14489,23 +14532,24 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DeactivateScalingConfigurationResponse({}));
     }
     /**
-     * @summary Deactivates a scaling configuration.
+     * Deactivates a scaling configuration.
      *
-     * @description *   You can call this operation to deactivate a scaling configuration only in a disabled scaling group.
+     * @remarks
+     *   You can call this operation to deactivate a scaling configuration only in a disabled scaling group.
      *
-     * @param request DeactivateScalingConfigurationRequest
-     * @return DeactivateScalingConfigurationResponse
+     * @param request - DeactivateScalingConfigurationRequest
+     * @returns DeactivateScalingConfigurationResponse
      */
     async deactivateScalingConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.deactivateScalingConfigurationWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return DeleteAlarmResponse
+     * @param request - DeleteAlarmRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DeleteAlarmResponse
      */
     async deleteAlarmWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14539,25 +14583,26 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DeleteAlarmResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - DeleteAlarmRequest
+     * @returns DeleteAlarmResponse
      */
     async deleteAlarm(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.deleteAlarmWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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 call this operation to delete a scaling configuration in the following scenarios:
+     * @remarks
+     * 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 created from the scaling configuration.
      *
-     * @param request DeleteEciScalingConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DeleteEciScalingConfigurationResponse
+     * @param request - DeleteEciScalingConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DeleteEciScalingConfigurationResponse
      */
     async deleteEciScalingConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14594,29 +14639,31 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DeleteEciScalingConfigurationResponse({}));
     }
     /**
-     * @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.
+     * 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 call this operation to delete a scaling configuration in the following scenarios:
+     * @remarks
+     * 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 created from the scaling configuration.
      *
-     * @param request DeleteEciScalingConfigurationRequest
-     * @return DeleteEciScalingConfigurationResponse
+     * @param request - DeleteEciScalingConfigurationRequest
+     * @returns DeleteEciScalingConfigurationResponse
      */
     async deleteEciScalingConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.deleteEciScalingConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary Deletes a lifecycle hook. If you no longer require a lifecycle hook, you can call the DeleteLifecycleHook operation to delete it, which frees up the lifecycle hook quota.
+     * Deletes a lifecycle hook. If you no longer require a lifecycle hook, you can call the DeleteLifecycleHook operation to delete it, which frees up the lifecycle hook quota.
      *
-     * @description If you delete an effective lifecycle hook before its timeout period ends, the instances on which the lifecycle hook takes effect exits the Pending state ahead of schedule. You can use the following methods to delete a lifecycle hook:
+     * @remarks
+     * If you delete an effective lifecycle hook before its timeout period ends, the instances on which the lifecycle hook takes effect exits the Pending state ahead of schedule. You can use the following methods to delete a lifecycle hook:
      * *   Include `LifecycleHookId` within your request to specify the lifecycle hook that you want to delete. In this case, `ScalingGroupId` and `LifecycleHookName` are ignored.
      * *   Include `ScalingGroupId` and `LifecycleHookName` within your request to specify the lifecycle hook that you want to delete.
      *
-     * @param request DeleteLifecycleHookRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DeleteLifecycleHookResponse
+     * @param request - DeleteLifecycleHookRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DeleteLifecycleHookResponse
      */
     async deleteLifecycleHookWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14659,25 +14706,26 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DeleteLifecycleHookResponse({}));
     }
     /**
-     * @summary Deletes a lifecycle hook. If you no longer require a lifecycle hook, you can call the DeleteLifecycleHook operation to delete it, which frees up the lifecycle hook quota.
+     * Deletes a lifecycle hook. If you no longer require a lifecycle hook, you can call the DeleteLifecycleHook operation to delete it, which frees up the lifecycle hook quota.
      *
-     * @description If you delete an effective lifecycle hook before its timeout period ends, the instances on which the lifecycle hook takes effect exits the Pending state ahead of schedule. You can use the following methods to delete a lifecycle hook:
+     * @remarks
+     * If you delete an effective lifecycle hook before its timeout period ends, the instances on which the lifecycle hook takes effect exits the Pending state ahead of schedule. You can use the following methods to delete a lifecycle hook:
      * *   Include `LifecycleHookId` within your request to specify the lifecycle hook that you want to delete. In this case, `ScalingGroupId` and `LifecycleHookName` are ignored.
      * *   Include `ScalingGroupId` and `LifecycleHookName` within your request to specify the lifecycle hook that you want to delete.
      *
-     * @param request DeleteLifecycleHookRequest
-     * @return DeleteLifecycleHookResponse
+     * @param request - DeleteLifecycleHookRequest
+     * @returns DeleteLifecycleHookResponse
      */
     async deleteLifecycleHook(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.deleteLifecycleHookWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return DeleteNotificationConfigurationResponse
+     * @param request - DeleteNotificationConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DeleteNotificationConfigurationResponse
      */
     async deleteNotificationConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14714,25 +14762,26 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DeleteNotificationConfigurationResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - DeleteNotificationConfigurationRequest
+     * @returns DeleteNotificationConfigurationResponse
      */
     async deleteNotificationConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.deleteNotificationConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
+     * Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
      *
-     * @description You cannot delete a scaling configuration in one of the following scenarios:
+     * @remarks
+     * You cannot delete a scaling configuration in one of the following scenarios:
      * *   The scaling configuration in your scaling group is in the Active state.
      * *   The scaling group contains ECS instances that were created based on the scaling configuration.
      *
-     * @param request DeleteScalingConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DeleteScalingConfigurationResponse
+     * @param request - DeleteScalingConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DeleteScalingConfigurationResponse
      */
     async deleteScalingConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14766,23 +14815,25 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingConfigurationResponse({}));
     }
     /**
-     * @summary Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
+     * Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
      *
-     * @description You cannot delete a scaling configuration in one of the following scenarios:
+     * @remarks
+     * You cannot delete a scaling configuration in one of the following scenarios:
      * *   The scaling configuration in your scaling group is in the Active state.
      * *   The scaling group contains ECS instances that were created based on the scaling configuration.
      *
-     * @param request DeleteScalingConfigurationRequest
-     * @return DeleteScalingConfigurationResponse
+     * @param request - DeleteScalingConfigurationRequest
+     * @returns DeleteScalingConfigurationResponse
      */
     async deleteScalingConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.deleteScalingConfigurationWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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 call the DeleteScalingGroup operation, take note of the following items:
+     * @remarks
+     * 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.
@@ -14793,9 +14844,9 @@ class Client extends openapi_client_1.default {
      *     **
      *     **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
-     * @return DeleteScalingGroupResponse
+     * @param request - DeleteScalingGroupRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DeleteScalingGroupResponse
      */
     async deleteScalingGroupWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14835,9 +14886,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingGroupResponse({}));
     }
     /**
-     * @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.
+     * 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 call the DeleteScalingGroup operation, take note of the following items:
+     * @remarks
+     * 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.
@@ -14848,19 +14900,19 @@ class Client extends openapi_client_1.default {
      *     **
      *     **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
+     * @param request - DeleteScalingGroupRequest
+     * @returns DeleteScalingGroupResponse
      */
     async deleteScalingGroup(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.deleteScalingGroupWithOptions(request, runtime);
     }
     /**
-     * @summary Deletes a scaling rule.
+     * Deletes a scaling rule.
      *
-     * @param request DeleteScalingRuleRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DeleteScalingRuleResponse
+     * @param request - DeleteScalingRuleRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DeleteScalingRuleResponse
      */
     async deleteScalingRuleWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14897,21 +14949,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingRuleResponse({}));
     }
     /**
-     * @summary Deletes a scaling rule.
+     * Deletes a scaling rule.
      *
-     * @param request DeleteScalingRuleRequest
-     * @return DeleteScalingRuleResponse
+     * @param request - DeleteScalingRuleRequest
+     * @returns DeleteScalingRuleResponse
      */
     async deleteScalingRule(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.deleteScalingRuleWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return DeleteScheduledTaskResponse
+     * @param request - DeleteScheduledTaskRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DeleteScheduledTaskResponse
      */
     async deleteScheduledTaskWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -14948,21 +15000,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DeleteScheduledTaskResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - DeleteScheduledTaskRequest
+     * @returns DeleteScheduledTaskResponse
      */
     async deleteScheduledTask(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.deleteScheduledTaskWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return DescribeAlarmsResponse
+     * @param request - DescribeAlarmsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeAlarmsResponse
      */
     async describeAlarmsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15017,21 +15069,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeAlarmsResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - DescribeAlarmsRequest
+     * @returns DescribeAlarmsResponse
      */
     async describeAlarms(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeAlarmsWithOptions(request, runtime);
     }
     /**
-     * @summary Queries the status of scaling activities that prompt text message or email notifications.
+     * Queries the status of scaling activities that trigger text message, internal message, or email-based notifications. When you call the DescribeAlertConfiguration operation, you must specify the scaling group ID and region ID to query the status of the desired scaling activities. A scaling activity can be in one of the following states: Successful, Failed, and Rejected.
      *
-     * @param request DescribeAlertConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeAlertConfigurationResponse
+     * @param request - DescribeAlertConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeAlertConfigurationResponse
      */
     async describeAlertConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15065,21 +15117,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeAlertConfigurationResponse({}));
     }
     /**
-     * @summary Queries the status of scaling activities that prompt text message or email notifications.
+     * Queries the status of scaling activities that trigger text message, internal message, or email-based notifications. When you call the DescribeAlertConfiguration operation, you must specify the scaling group ID and region ID to query the status of the desired scaling activities. A scaling activity can be in one of the following states: Successful, Failed, and Rejected.
      *
-     * @param request DescribeAlertConfigurationRequest
-     * @return DescribeAlertConfigurationResponse
+     * @param request - DescribeAlertConfigurationRequest
+     * @returns DescribeAlertConfigurationResponse
      */
     async describeAlertConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeAlertConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary Queries the details of a scaling configuration. You can query a scaling configuration by its ID to learn about its details such as the temporary storage size, number of IPv6 addresses, and bandwidth of the elastic IP address (EIP). The scaling configuration details can be obtained as a YAML file.
+     * Queries the details of a scaling configuration. You can query a scaling configuration by its ID to learn about its details such as the temporary storage size, number of IPv6 addresses, and bandwidth of the elastic IP address (EIP). The scaling configuration details can be obtained as a YAML file.
      *
-     * @param request DescribeEciScalingConfigurationDetailRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeEciScalingConfigurationDetailResponse
+     * @param request - DescribeEciScalingConfigurationDetailRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeEciScalingConfigurationDetailResponse
      */
     async describeEciScalingConfigurationDetailWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15113,21 +15165,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationDetailResponse({}));
     }
     /**
-     * @summary Queries the details of a scaling configuration. You can query a scaling configuration by its ID to learn about its details such as the temporary storage size, number of IPv6 addresses, and bandwidth of the elastic IP address (EIP). The scaling configuration details can be obtained as a YAML file.
+     * Queries the details of a scaling configuration. You can query a scaling configuration by its ID to learn about its details such as the temporary storage size, number of IPv6 addresses, and bandwidth of the elastic IP address (EIP). The scaling configuration details can be obtained as a YAML file.
      *
-     * @param request DescribeEciScalingConfigurationDetailRequest
-     * @return DescribeEciScalingConfigurationDetailResponse
+     * @param request - DescribeEciScalingConfigurationDetailRequest
+     * @returns DescribeEciScalingConfigurationDetailResponse
      */
     async describeEciScalingConfigurationDetail(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeEciScalingConfigurationDetailWithOptions(request, runtime);
     }
     /**
-     * @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances.
+     * Queries scaling configurations of the Elastic Container Instance type. When you call the DescribeEciScalingConfigurations operation, you can specify ScalingGroupId, ScalingConfigurationIds, or ScalingConfigurationNames to query details about the desired scaling configurations, such as the instance bidding policy, instance type, image pulling policy, and load balancing weight of each elastic container instance. This can help you select a suitable template for creating elastic container instances or reference existing scaling configurations before you modify the automatic scaling policy for elastic container instances.
      *
-     * @param request DescribeEciScalingConfigurationsRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeEciScalingConfigurationsResponse
+     * @param request - DescribeEciScalingConfigurationsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeEciScalingConfigurationsResponse
      */
     async describeEciScalingConfigurationsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15179,27 +15231,28 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationsResponse({}));
     }
     /**
-     * @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances.
+     * Queries scaling configurations of the Elastic Container Instance type. When you call the DescribeEciScalingConfigurations operation, you can specify ScalingGroupId, ScalingConfigurationIds, or ScalingConfigurationNames to query details about the desired scaling configurations, such as the instance bidding policy, instance type, image pulling policy, and load balancing weight of each elastic container instance. This can help you select a suitable template for creating elastic container instances or reference existing scaling configurations before you modify the automatic scaling policy for elastic container instances.
      *
-     * @param request DescribeEciScalingConfigurationsRequest
-     * @return DescribeEciScalingConfigurationsResponse
+     * @param request - DescribeEciScalingConfigurationsRequest
+     * @returns DescribeEciScalingConfigurationsResponse
      */
     async describeEciScalingConfigurations(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeEciScalingConfigurationsWithOptions(request, runtime);
     }
     /**
-     * @summary Queries the details of a lifecycle hook. If you want to query the details of a lifecycle hook, you can call the DescribeLifecycleActions operation. For example, you can query the execution status and ID of a lifecycle hook, along with the Elastic Compute Service (ECS) instances on which the lifecycle hook takes effect. When you call this operation, you can specify parameters such as ScalingActivityId, LifecycleActionToken, and MaxResults to query the details of a lifecycle hook.
+     * Queries the details of a lifecycle hook. If you want to query the details of a lifecycle hook, you can call the DescribeLifecycleActions operation. For example, you can query the execution status and ID of a lifecycle hook, along with the Elastic Compute Service (ECS) instances on which the lifecycle hook takes effect. When you call this operation, you can specify parameters such as ScalingActivityId, LifecycleActionToken, and MaxResults to query the details of a lifecycle hook.
      *
-     * @description If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
+     * @remarks
+     * If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
      * *   If a lifecycle action is in the Pending state, Elastic Compute Service (ECS) instances are waiting to be added to a scaling group or waiting to be removed from a scaling group.
      * *   If a lifecycle action is in the Timeout state, the lifecycle hook that triggers the lifecycle action expires and ECS instances are added to or removed from a scaling group.
      * *   If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
      * If you do not specify the action to perform, such as execute a specific OOS template, after a lifecycle hook ends, you can call this operation to obtain the token of the lifecycle action that corresponds to the lifecycle hook. Then, you can specify a custom action to perform after the lifecycle hook ends.
      *
-     * @param request DescribeLifecycleActionsRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeLifecycleActionsResponse
+     * @param request - DescribeLifecycleActionsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeLifecycleActionsResponse
      */
     async describeLifecycleActionsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15242,32 +15295,34 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleActionsResponse({}));
     }
     /**
-     * @summary Queries the details of a lifecycle hook. If you want to query the details of a lifecycle hook, you can call the DescribeLifecycleActions operation. For example, you can query the execution status and ID of a lifecycle hook, along with the Elastic Compute Service (ECS) instances on which the lifecycle hook takes effect. When you call this operation, you can specify parameters such as ScalingActivityId, LifecycleActionToken, and MaxResults to query the details of a lifecycle hook.
+     * Queries the details of a lifecycle hook. If you want to query the details of a lifecycle hook, you can call the DescribeLifecycleActions operation. For example, you can query the execution status and ID of a lifecycle hook, along with the Elastic Compute Service (ECS) instances on which the lifecycle hook takes effect. When you call this operation, you can specify parameters such as ScalingActivityId, LifecycleActionToken, and MaxResults to query the details of a lifecycle hook.
      *
-     * @description If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
+     * @remarks
+     * If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
      * *   If a lifecycle action is in the Pending state, Elastic Compute Service (ECS) instances are waiting to be added to a scaling group or waiting to be removed from a scaling group.
      * *   If a lifecycle action is in the Timeout state, the lifecycle hook that triggers the lifecycle action expires and ECS instances are added to or removed from a scaling group.
      * *   If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
      * If you do not specify the action to perform, such as execute a specific OOS template, after a lifecycle hook ends, you can call this operation to obtain the token of the lifecycle action that corresponds to the lifecycle hook. Then, you can specify a custom action to perform after the lifecycle hook ends.
      *
-     * @param request DescribeLifecycleActionsRequest
-     * @return DescribeLifecycleActionsResponse
+     * @param request - DescribeLifecycleActionsRequest
+     * @returns DescribeLifecycleActionsResponse
      */
     async describeLifecycleActions(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeLifecycleActionsWithOptions(request, runtime);
     }
     /**
-     * @summary Queries lifecycle hooks. If you want to check whether the configurations of your lifecycle hooks are correct or you want to query the details of multiple lifecycle hooks at the same time, you can call the DescribeLifecycleHooks operation. You can specify lifecycle hook IDs or scaling group IDs when you call this operation. This operation returns details such as the default actions, scaling activities, Alibaba Cloud Resource Names (ARNs) of notification recipients, and timeout periods of lifecycle hooks.
+     * Queries lifecycle hooks. If you want to check whether the configurations of your lifecycle hooks are correct or you want to query the details of multiple lifecycle hooks at the same time, you can call the DescribeLifecycleHooks operation. You can specify lifecycle hook IDs or scaling group IDs when you call this operation. This operation returns details such as the default actions, scaling activities, Alibaba Cloud Resource Names (ARNs) of notification recipients, and timeout periods of lifecycle hooks.
      *
-     * @description You can use one of the following methods to query lifecycle hooks:
+     * @remarks
+     * 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
+     * @param request - DescribeLifecycleHooksRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeLifecycleHooksResponse
      */
     async describeLifecycleHooksWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15316,26 +15371,27 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleHooksResponse({}));
     }
     /**
-     * @summary Queries lifecycle hooks. If you want to check whether the configurations of your lifecycle hooks are correct or you want to query the details of multiple lifecycle hooks at the same time, you can call the DescribeLifecycleHooks operation. You can specify lifecycle hook IDs or scaling group IDs when you call this operation. This operation returns details such as the default actions, scaling activities, Alibaba Cloud Resource Names (ARNs) of notification recipients, and timeout periods of lifecycle hooks.
+     * Queries lifecycle hooks. If you want to check whether the configurations of your lifecycle hooks are correct or you want to query the details of multiple lifecycle hooks at the same time, you can call the DescribeLifecycleHooks operation. You can specify lifecycle hook IDs or scaling group IDs when you call this operation. This operation returns details such as the default actions, scaling activities, Alibaba Cloud Resource Names (ARNs) of notification recipients, and timeout periods of lifecycle hooks.
      *
-     * @description You can use one of the following methods to query lifecycle hooks:
+     * @remarks
+     * 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
+     * @param request - DescribeLifecycleHooksRequest
+     * @returns DescribeLifecycleHooksResponse
      */
     async describeLifecycleHooks(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeLifecycleHooksWithOptions(request, runtime);
     }
     /**
-     * @summary Queries resource quotas. You can call the DescribeLimitation operation to query the upper limits on resources such as scheduled tasks that can be created in a scaling group, load balancers that can be attached to a scaling group, instances that can be contained in a scaling group, and scaling configurations that can be created in a scaling group.
+     * Queries resource quotas. For example, you can call the DescribeLimitation operation to query the maximum numbers of scheduled tasks that you can create in a scaling group, load balancers that you can attach to a scaling group, instances that you can add to a scaling group, and scaling configurations that you can create in a scaling group.
      *
-     * @param request DescribeLimitationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeLimitationResponse
+     * @param request - DescribeLimitationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeLimitationResponse
      */
     async describeLimitationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15363,21 +15419,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeLimitationResponse({}));
     }
     /**
-     * @summary Queries resource quotas. You can call the DescribeLimitation operation to query the upper limits on resources such as scheduled tasks that can be created in a scaling group, load balancers that can be attached to a scaling group, instances that can be contained in a scaling group, and scaling configurations that can be created in a scaling group.
+     * Queries resource quotas. For example, you can call the DescribeLimitation operation to query the maximum numbers of scheduled tasks that you can create in a scaling group, load balancers that you can attach to a scaling group, instances that you can add to a scaling group, and scaling configurations that you can create in a scaling group.
      *
-     * @param request DescribeLimitationRequest
-     * @return DescribeLimitationResponse
+     * @param request - DescribeLimitationRequest
+     * @returns DescribeLimitationResponse
      */
     async describeLimitation(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeLimitationWithOptions(request, runtime);
     }
     /**
-     * @summary Queries notifications. If you want to learn about a notification regarding the status of a scaling event or resource changes, you can call the DescribeNotificationConfigurations operation. This operation enables you to retrieve notification details, analyze resource change data, and refine scaling policies to efficiently utilize resources and fulfill business needs.
+     * Queries notifications. If you want to learn about a notification regarding the status of a scaling event or resource changes, you can call the DescribeNotificationConfigurations operation. This operation enables you to retrieve notification details, analyze resource change data, and refine scaling policies to efficiently utilize resources and fulfill business needs.
      *
-     * @param request DescribeNotificationConfigurationsRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeNotificationConfigurationsResponse
+     * @param request - DescribeNotificationConfigurationsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeNotificationConfigurationsResponse
      */
     async describeNotificationConfigurationsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15411,21 +15467,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationConfigurationsResponse({}));
     }
     /**
-     * @summary Queries notifications. If you want to learn about a notification regarding the status of a scaling event or resource changes, you can call the DescribeNotificationConfigurations operation. This operation enables you to retrieve notification details, analyze resource change data, and refine scaling policies to efficiently utilize resources and fulfill business needs.
+     * Queries notifications. If you want to learn about a notification regarding the status of a scaling event or resource changes, you can call the DescribeNotificationConfigurations operation. This operation enables you to retrieve notification details, analyze resource change data, and refine scaling policies to efficiently utilize resources and fulfill business needs.
      *
-     * @param request DescribeNotificationConfigurationsRequest
-     * @return DescribeNotificationConfigurationsResponse
+     * @param request - DescribeNotificationConfigurationsRequest
+     * @returns DescribeNotificationConfigurationsResponse
      */
     async describeNotificationConfigurations(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeNotificationConfigurationsWithOptions(request, runtime);
     }
     /**
-     * @summary Queries notification types. You can call the DescribeNotificationTypes operation to query the types of notifications on scaling events or resource changes occurred in your scaling groups. Notifications are triggered in scenarios such as successful scale-out events, successful scale-in events, expiration of scheduled tasks, and partially successful scale-out events.
+     * Queries notification types. You can call the DescribeNotificationTypes operation to query the types of notifications on scaling events or resource changes occurred in your scaling groups. Notifications are triggered in scenarios such as successful scale-out events, successful scale-in events, expiration of scheduled tasks, and partially successful scale-out events.
      *
-     * @param request DescribeNotificationTypesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeNotificationTypesResponse
+     * @param request - DescribeNotificationTypesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeNotificationTypesResponse
      */
     async describeNotificationTypesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15453,21 +15509,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationTypesResponse({}));
     }
     /**
-     * @summary Queries notification types. You can call the DescribeNotificationTypes operation to query the types of notifications on scaling events or resource changes occurred in your scaling groups. Notifications are triggered in scenarios such as successful scale-out events, successful scale-in events, expiration of scheduled tasks, and partially successful scale-out events.
+     * Queries notification types. You can call the DescribeNotificationTypes operation to query the types of notifications on scaling events or resource changes occurred in your scaling groups. Notifications are triggered in scenarios such as successful scale-out events, successful scale-in events, expiration of scheduled tasks, and partially successful scale-out events.
      *
-     * @param request DescribeNotificationTypesRequest
-     * @return DescribeNotificationTypesResponse
+     * @param request - DescribeNotificationTypesRequest
+     * @returns DescribeNotificationTypesResponse
      */
     async describeNotificationTypes(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeNotificationTypesWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * Queries instance types. When you call the DescribePatternTypes operation, you can specify attributes such as the vSwitch ID, number of vCPUs, memory size, instance family, and maximum acceptable price to filer instance types that meet your business requirements.
      *
-     * @param request DescribePatternTypesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribePatternTypesResponse
+     * @param request - DescribePatternTypesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribePatternTypesResponse
      */
     async describePatternTypesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15489,21 +15545,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribePatternTypesResponse({}));
     }
     /**
-     * @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.
+     * Queries instance types. When you call the DescribePatternTypes operation, you can specify attributes such as the vSwitch ID, number of vCPUs, memory size, instance family, and maximum acceptable price to filer instance types that meet your business requirements.
      *
-     * @param request DescribePatternTypesRequest
-     * @return DescribePatternTypesResponse
+     * @param request - DescribePatternTypesRequest
+     * @returns DescribePatternTypesResponse
      */
     async describePatternTypes(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describePatternTypesWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return DescribeRegionsResponse
+     * @param request - DescribeRegionsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeRegionsResponse
      */
     async describeRegionsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15537,25 +15593,26 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeRegionsResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - DescribeRegionsRequest
+     * @returns DescribeRegionsResponse
      */
     async describeRegions(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeRegionsWithOptions(request, runtime);
     }
     /**
-     * @summary Queries scaling activities.
+     * Queries scaling activities.
      *
-     * @description You can specify a scaling group ID to query all scaling activities in the scaling group.
+     * @remarks
+     * You can specify a scaling group ID to query all scaling activities in the scaling group.
      * You can filter query results based on the status of scaling activities.
      * You can query scaling activities that are executed in the previous 30 days.
      *
-     * @param request DescribeScalingActivitiesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeScalingActivitiesResponse
+     * @param request - DescribeScalingActivitiesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeScalingActivitiesResponse
      */
     async describeScalingActivitiesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15607,25 +15664,26 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivitiesResponse({}));
     }
     /**
-     * @summary Queries scaling activities.
+     * Queries scaling activities.
      *
-     * @description You can specify a scaling group ID to query all scaling activities in the scaling group.
+     * @remarks
+     * You can specify a scaling group ID to query all scaling activities in the scaling group.
      * You can filter query results based on the status of scaling activities.
      * You can query scaling activities that are executed in the previous 30 days.
      *
-     * @param request DescribeScalingActivitiesRequest
-     * @return DescribeScalingActivitiesResponse
+     * @param request - DescribeScalingActivitiesRequest
+     * @returns DescribeScalingActivitiesResponse
      */
     async describeScalingActivities(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeScalingActivitiesWithOptions(request, runtime);
     }
     /**
-     * @summary Queries the details of a scaling activity. The DescribeScalingActivityDetail operation enables you to access and monitor the details of a scaling activity, which is beneficial for troubleshooting and performance analysis purposes.
+     * Queries the details of a scaling activity. The DescribeScalingActivityDetail operation enables you to access and monitor the details of a scaling activity, which is beneficial for troubleshooting and performance analysis purposes.
      *
-     * @param request DescribeScalingActivityDetailRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeScalingActivityDetailResponse
+     * @param request - DescribeScalingActivityDetailRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeScalingActivityDetailResponse
      */
     async describeScalingActivityDetailWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15659,21 +15717,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivityDetailResponse({}));
     }
     /**
-     * @summary Queries the details of a scaling activity. The DescribeScalingActivityDetail operation enables you to access and monitor the details of a scaling activity, which is beneficial for troubleshooting and performance analysis purposes.
+     * Queries the details of a scaling activity. The DescribeScalingActivityDetail operation enables you to access and monitor the details of a scaling activity, which is beneficial for troubleshooting and performance analysis purposes.
      *
-     * @param request DescribeScalingActivityDetailRequest
-     * @return DescribeScalingActivityDetailResponse
+     * @param request - DescribeScalingActivityDetailRequest
+     * @returns DescribeScalingActivityDetailResponse
      */
     async describeScalingActivityDetail(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeScalingActivityDetailWithOptions(request, runtime);
     }
     /**
-     * @summary Queries scaling configurations.
+     * Queries scaling configurations.
      *
-     * @param request DescribeScalingConfigurationsRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeScalingConfigurationsResponse
+     * @param request - DescribeScalingConfigurationsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeScalingConfigurationsResponse
      */
     async describeScalingConfigurationsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15725,21 +15783,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingConfigurationsResponse({}));
     }
     /**
-     * @summary Queries scaling configurations.
+     * Queries scaling configurations.
      *
-     * @param request DescribeScalingConfigurationsRequest
-     * @return DescribeScalingConfigurationsResponse
+     * @param request - DescribeScalingConfigurationsRequest
+     * @returns DescribeScalingConfigurationsResponse
      */
     async describeScalingConfigurations(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeScalingConfigurationsWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return DescribeScalingGroupDetailResponse
+     * @param request - DescribeScalingGroupDetailRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeScalingGroupDetailResponse
      */
     async describeScalingGroupDetailWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15773,21 +15831,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new 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, the output is a Kubernetes Deployment file in the YAML format.
+     * 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
+     * @param request - DescribeScalingGroupDetailRequest
+     * @returns DescribeScalingGroupDetailResponse
      */
     async describeScalingGroupDetail(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeScalingGroupDetailWithOptions(request, runtime);
     }
     /**
-     * @summary Queries scaling groups. If you want to query the basic information, instances, and scaling configurations of a scaling group, you can call the DescribeScalingGroups operation.
+     * Queries scaling groups. If you want to query the basic information, instances, and scaling configurations of a scaling group, you can call the DescribeScalingGroups operation.
      *
-     * @param request DescribeScalingGroupsRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeScalingGroupsResponse
+     * @param request - DescribeScalingGroupsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeScalingGroupsResponse
      */
     async describeScalingGroupsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15848,21 +15906,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupsResponse({}));
     }
     /**
-     * @summary Queries scaling groups. If you want to query the basic information, instances, and scaling configurations of a scaling group, you can call the DescribeScalingGroups operation.
+     * Queries scaling groups. If you want to query the basic information, instances, and scaling configurations of a scaling group, you can call the DescribeScalingGroups operation.
      *
-     * @param request DescribeScalingGroupsRequest
-     * @return DescribeScalingGroupsResponse
+     * @param request - DescribeScalingGroupsRequest
+     * @returns DescribeScalingGroupsResponse
      */
     async describeScalingGroups(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeScalingGroupsWithOptions(request, runtime);
     }
     /**
-     * @summary Queries the Elastic Compute Service (ECS) instances in a scaling group. If you want to flexibly filter ECS instances that meet the specified criteria and query the instance details, you can call the DescribeScalingInstances operation. This operation enables you to input custom parameters for precise query of ECS instances, helping you gain a clear understanding of the instance details and optimize scaling configurations.
+     * Queries instances in a scaling group. You can call the DescribeScalingInstances operation to query instance details such as the number of preemptible instances in the Running state, the number of Elastic Compute Service (ECS) instances, the warm-up status of ECS instances, and the lifecycle status of ECS instances in a scaling group. You can specify the desired scaling group whose instances you want to query by scaling group ID. In addition, if you want to filter instances based on conditions such as the instance health status, lifecycle status, or creation method, you can also call this operation.
      *
-     * @param request DescribeScalingInstancesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeScalingInstancesResponse
+     * @param request - DescribeScalingInstancesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeScalingInstancesResponse
      */
     async describeScalingInstancesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -15932,23 +15990,24 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingInstancesResponse({}));
     }
     /**
-     * @summary Queries the Elastic Compute Service (ECS) instances in a scaling group. If you want to flexibly filter ECS instances that meet the specified criteria and query the instance details, you can call the DescribeScalingInstances operation. This operation enables you to input custom parameters for precise query of ECS instances, helping you gain a clear understanding of the instance details and optimize scaling configurations.
+     * Queries instances in a scaling group. You can call the DescribeScalingInstances operation to query instance details such as the number of preemptible instances in the Running state, the number of Elastic Compute Service (ECS) instances, the warm-up status of ECS instances, and the lifecycle status of ECS instances in a scaling group. You can specify the desired scaling group whose instances you want to query by scaling group ID. In addition, if you want to filter instances based on conditions such as the instance health status, lifecycle status, or creation method, you can also call this operation.
      *
-     * @param request DescribeScalingInstancesRequest
-     * @return DescribeScalingInstancesResponse
+     * @param request - DescribeScalingInstancesRequest
+     * @returns DescribeScalingInstancesResponse
      */
     async describeScalingInstances(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeScalingInstancesWithOptions(request, runtime);
     }
     /**
-     * @summary Queries all scaling rules in a scaling group.
+     * Queries scaling rules. When you call this operation, you can specify the ID, name, or Alibaba Cloud Resource Name (ARN) of a scaling rule to query the details of the scaling rule. For example, you can query the adjustment method, instance warm-up period, and associated event-triggered tasks of the desired scaling rule.
      *
-     * @description You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
+     * @remarks
+     * You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
      *
-     * @param request DescribeScalingRulesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DescribeScalingRulesResponse
+     * @param request - DescribeScalingRulesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeScalingRulesResponse
      */
     async describeScalingRulesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16009,25 +16068,27 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingRulesResponse({}));
     }
     /**
-     * @summary Queries all scaling rules in a scaling group.
+     * Queries scaling rules. When you call this operation, you can specify the ID, name, or Alibaba Cloud Resource Name (ARN) of a scaling rule to query the details of the scaling rule. For example, you can query the adjustment method, instance warm-up period, and associated event-triggered tasks of the desired scaling rule.
      *
-     * @description You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
+     * @remarks
+     * You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
      *
-     * @param request DescribeScalingRulesRequest
-     * @return DescribeScalingRulesResponse
+     * @param request - DescribeScalingRulesRequest
+     * @returns DescribeScalingRulesResponse
      */
     async describeScalingRules(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeScalingRulesWithOptions(request, runtime);
     }
     /**
-     * @summary Queries scheduled tasks. A scheduled task is a predefined task that triggers the automatic execution of a scaling rule at the specified point in time. It ensures an automatic scaling of computing resources to fulfill your business demands at a minimum cost. After you create a scheduled task, you can call the DescribeScheduledTasks operation to query the details of the task, such as the execution time point and the scaling group ID. You can also call this operation to query the total number of existing scheduled tasks.
+     * Queries scheduled tasks. A scheduled task is a predefined task that triggers the automatic execution of a scaling rule at the specified point in time. It ensures an automatic scaling of computing resources to fulfill your business demands at a minimum cost. After you create a scheduled task, you can call the DescribeScheduledTasks operation to query the details of the task, such as the execution time point and the scaling group ID. You can also call this operation to query the total number of existing scheduled tasks.
      *
-     * @description You can query scheduled tasks by scaling rule, task ID, or task name.
+     * @remarks
+     * 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
+     * @param request - DescribeScheduledTasksRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DescribeScheduledTasksResponse
      */
     async describeScheduledTasksWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16094,23 +16155,24 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeScheduledTasksResponse({}));
     }
     /**
-     * @summary Queries scheduled tasks. A scheduled task is a predefined task that triggers the automatic execution of a scaling rule at the specified point in time. It ensures an automatic scaling of computing resources to fulfill your business demands at a minimum cost. After you create a scheduled task, you can call the DescribeScheduledTasks operation to query the details of the task, such as the execution time point and the scaling group ID. You can also call this operation to query the total number of existing scheduled tasks.
+     * Queries scheduled tasks. A scheduled task is a predefined task that triggers the automatic execution of a scaling rule at the specified point in time. It ensures an automatic scaling of computing resources to fulfill your business demands at a minimum cost. After you create a scheduled task, you can call the DescribeScheduledTasks operation to query the details of the task, such as the execution time point and the scaling group ID. You can also call this operation to query the total number of existing scheduled tasks.
      *
-     * @description You can query scheduled tasks by scaling rule, task ID, or task name.
+     * @remarks
+     * You can query scheduled tasks by scaling rule, task ID, or task name.
      *
-     * @param request DescribeScheduledTasksRequest
-     * @return DescribeScheduledTasksResponse
+     * @param request - DescribeScheduledTasksRequest
+     * @returns DescribeScheduledTasksResponse
      */
     async describeScheduledTasks(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.describeScheduledTasksWithOptions(request, runtime);
     }
     /**
-     * @summary Disassociates one or more Application Load Balancer (ALB) server groups from a scaling group.
+     * Detaches Application Load Balancer (ALB) server groups from a scaling group. When you call the DetachAlbServerGroups operation, you can specify the scaling group ID, ALB server group ID, and port used by Elastic Compute Service (ECS) instances in the desired ALB server group to detach one or more ALB server groups from your scaling group.
      *
-     * @param request DetachAlbServerGroupsRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DetachAlbServerGroupsResponse
+     * @param request - DetachAlbServerGroupsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DetachAlbServerGroupsResponse
      */
     async detachAlbServerGroupsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16153,21 +16215,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DetachAlbServerGroupsResponse({}));
     }
     /**
-     * @summary Disassociates one or more Application Load Balancer (ALB) server groups from a scaling group.
+     * Detaches Application Load Balancer (ALB) server groups from a scaling group. When you call the DetachAlbServerGroups operation, you can specify the scaling group ID, ALB server group ID, and port used by Elastic Compute Service (ECS) instances in the desired ALB server group to detach one or more ALB server groups from your scaling group.
      *
-     * @param request DetachAlbServerGroupsRequest
-     * @return DetachAlbServerGroupsResponse
+     * @param request - DetachAlbServerGroupsRequest
+     * @returns DetachAlbServerGroupsResponse
      */
     async detachAlbServerGroups(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.detachAlbServerGroupsWithOptions(request, runtime);
     }
     /**
-     * @summary Disassociates one or more ApsaraDB RDS instances from a scaling group.
+     * Disassociates one or more ApsaraDB RDS instances from a scaling group.
      *
-     * @param request DetachDBInstancesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DetachDBInstancesResponse
+     * @param request - DetachDBInstancesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DetachDBInstancesResponse
      */
     async detachDBInstancesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16213,19 +16275,20 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DetachDBInstancesResponse({}));
     }
     /**
-     * @summary Disassociates one or more ApsaraDB RDS instances from a scaling group.
+     * Disassociates one or more ApsaraDB RDS instances from a scaling group.
      *
-     * @param request DetachDBInstancesRequest
-     * @return DetachDBInstancesResponse
+     * @param request - DetachDBInstancesRequest
+     * @returns DetachDBInstancesResponse
      */
     async detachDBInstances(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.detachDBInstancesWithOptions(request, runtime);
     }
     /**
-     * @summary Removes instances from a scaling group. If an enabled scaling group has no ongoing scaling activities, you can call the DetachInstances operation to remove one or more Elastic Compute Service (ECS) instances, elastic container instances, or Alibaba Cloud-hosted third-party instances from the scaling group.
+     * Removes instances from a scaling group. If an enabled scaling group has no ongoing scaling activities, you can call the DetachInstances operation to remove one or more Elastic Compute Service (ECS) instances, elastic container instances, or Alibaba Cloud-hosted third-party instances from the scaling group.
      *
-     * @description *   Before you call the DetachInstances operation, make sure that the following conditions are met:
+     * @remarks
+     *   Before you call the DetachInstances operation, make sure that the following conditions are met:
      *     *   The specified scaling group is enabled.
      *     *   The specified scaling group does not have any ongoing scaling activities.
      *     **
@@ -16236,9 +16299,9 @@ class Client extends openapi_client_1.default {
      *     *   A successful call only means that Auto Scaling accepts your request. Scaling activities can be triggered as expected, but their successful execution is not guaranteed. You can query the status of a scaling activity based on the ScalingActivityId response parameter.
      *     *   The removal of ECS instances, elastic container instances, or Alibaba Cloud-hosted third-party instances must not result in the overall number of instances within the specified scaling group falling below the minimum capacity threshold (MinSize); otherwise, an error will be reported.
      *
-     * @param request DetachInstancesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DetachInstancesResponse
+     * @param request - DetachInstancesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DetachInstancesResponse
      */
     async detachInstancesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16293,9 +16356,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DetachInstancesResponse({}));
     }
     /**
-     * @summary Removes instances from a scaling group. If an enabled scaling group has no ongoing scaling activities, you can call the DetachInstances operation to remove one or more Elastic Compute Service (ECS) instances, elastic container instances, or Alibaba Cloud-hosted third-party instances from the scaling group.
+     * Removes instances from a scaling group. If an enabled scaling group has no ongoing scaling activities, you can call the DetachInstances operation to remove one or more Elastic Compute Service (ECS) instances, elastic container instances, or Alibaba Cloud-hosted third-party instances from the scaling group.
      *
-     * @description *   Before you call the DetachInstances operation, make sure that the following conditions are met:
+     * @remarks
+     *   Before you call the DetachInstances operation, make sure that the following conditions are met:
      *     *   The specified scaling group is enabled.
      *     *   The specified scaling group does not have any ongoing scaling activities.
      *     **
@@ -16306,19 +16370,19 @@ class Client extends openapi_client_1.default {
      *     *   A successful call only means that Auto Scaling accepts your request. Scaling activities can be triggered as expected, but their successful execution is not guaranteed. You can query the status of a scaling activity based on the ScalingActivityId response parameter.
      *     *   The removal of ECS instances, elastic container instances, or Alibaba Cloud-hosted third-party instances must not result in the overall number of instances within the specified scaling group falling below the minimum capacity threshold (MinSize); otherwise, an error will be reported.
      *
-     * @param request DetachInstancesRequest
-     * @return DetachInstancesResponse
+     * @param request - DetachInstancesRequest
+     * @returns DetachInstancesResponse
      */
     async detachInstances(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.detachInstancesWithOptions(request, runtime);
     }
     /**
-     * @summary Detaches Classic Load Balancer (CLB, formerly known as Server Load Balancer or SLB) instances from a scaling group. If the current CLB instance no longer meets your business requirements, you can call the DetachLoadBalancers operation to detach it from your scaling group. When you call this operation, you can use ScalingGroupId, LoadBalancer.N, and ForceDetach to specify one or more CLB instances to detach. You can also determine whether to call this operation asynchronously and whether to remove the Elastic Compute Service (ECS) instances acting as backend servers from the backend server groups of the CLB instance. You can call this operation to detach only CLB instances from a scaling group.
+     * Detaches Classic Load Balancer (CLB, formerly known as Server Load Balancer or SLB) instances from a scaling group. If the current CLB instance no longer meets your business requirements, you can call the DetachLoadBalancers operation to detach it from your scaling group. When you call this operation, you can use ScalingGroupId, LoadBalancer.N, and ForceDetach to specify one or more CLB instances to detach. You can also determine whether to call this operation asynchronously and whether to remove the Elastic Compute Service (ECS) instances acting as backend servers from the backend server groups of the CLB instance. You can call this operation to detach only CLB instances from a scaling group.
      *
-     * @param request DetachLoadBalancersRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DetachLoadBalancersResponse
+     * @param request - DetachLoadBalancersRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DetachLoadBalancersResponse
      */
     async detachLoadBalancersWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16364,21 +16428,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DetachLoadBalancersResponse({}));
     }
     /**
-     * @summary Detaches Classic Load Balancer (CLB, formerly known as Server Load Balancer or SLB) instances from a scaling group. If the current CLB instance no longer meets your business requirements, you can call the DetachLoadBalancers operation to detach it from your scaling group. When you call this operation, you can use ScalingGroupId, LoadBalancer.N, and ForceDetach to specify one or more CLB instances to detach. You can also determine whether to call this operation asynchronously and whether to remove the Elastic Compute Service (ECS) instances acting as backend servers from the backend server groups of the CLB instance. You can call this operation to detach only CLB instances from a scaling group.
+     * Detaches Classic Load Balancer (CLB, formerly known as Server Load Balancer or SLB) instances from a scaling group. If the current CLB instance no longer meets your business requirements, you can call the DetachLoadBalancers operation to detach it from your scaling group. When you call this operation, you can use ScalingGroupId, LoadBalancer.N, and ForceDetach to specify one or more CLB instances to detach. You can also determine whether to call this operation asynchronously and whether to remove the Elastic Compute Service (ECS) instances acting as backend servers from the backend server groups of the CLB instance. You can call this operation to detach only CLB instances from a scaling group.
      *
-     * @param request DetachLoadBalancersRequest
-     * @return DetachLoadBalancersResponse
+     * @param request - DetachLoadBalancersRequest
+     * @returns DetachLoadBalancersResponse
      */
     async detachLoadBalancers(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.detachLoadBalancersWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return DetachServerGroupsResponse
+     * @param request - DetachServerGroupsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DetachServerGroupsResponse
      */
     async detachServerGroupsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16421,28 +16485,29 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DetachServerGroupsResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - DetachServerGroupsRequest
+     * @returns DetachServerGroupsResponse
      */
     async detachServerGroups(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.detachServerGroupsWithOptions(request, runtime);
     }
     /**
-     * @summary Detaches vServer groups from a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups to improve service performance. If the load balancer currently attached to your scaling group is no longer needed to distribute the access traffic to the instances in your scaling group, you can call the DetachVServerGroups operation to detach one or more vServer groups of this load balancer from the scaling group.
+     * Detaches vServer groups from a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups to improve service performance. If the load balancer currently attached to your scaling group is no longer needed to distribute the access traffic to the instances in your scaling group, you can call the DetachVServerGroups operation to detach one or more vServer groups of this load balancer from the scaling group.
      *
-     * @description *   When you call the DetachVServerGroups operation, you must use the following parameters to specify the vServer groups that you want to detach from your scaling group:
+     * @remarks
+     *   When you call the DetachVServerGroups operation, you must use the following parameters to specify the vServer groups that you want to detach from your scaling group:
      *     *   LoadBalancerId: the ID of the load balancer
      *     *   VServerGroupId: the ID of the vServer group
      *     *   Port: the port number of the vServer group
      * *   When the vServer group specified by the request parameters matches that attached to your scaling group, this operation yields a favorable result. Otherwise, the request is ignored and no error is reported.
      * *   Before you call this operation, you must make sure that the load balancer has ceased routing the access traffic to the instances in the scaling group. Failure to do so may lead to service requests being dropped or lost during the detachment process.
      *
-     * @param request DetachVServerGroupsRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return DetachVServerGroupsResponse
+     * @param request - DetachVServerGroupsRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DetachVServerGroupsResponse
      */
     async detachVServerGroupsWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16485,30 +16550,32 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DetachVServerGroupsResponse({}));
     }
     /**
-     * @summary Detaches vServer groups from a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups to improve service performance. If the load balancer currently attached to your scaling group is no longer needed to distribute the access traffic to the instances in your scaling group, you can call the DetachVServerGroups operation to detach one or more vServer groups of this load balancer from the scaling group.
+     * Detaches vServer groups from a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups to improve service performance. If the load balancer currently attached to your scaling group is no longer needed to distribute the access traffic to the instances in your scaling group, you can call the DetachVServerGroups operation to detach one or more vServer groups of this load balancer from the scaling group.
      *
-     * @description *   When you call the DetachVServerGroups operation, you must use the following parameters to specify the vServer groups that you want to detach from your scaling group:
+     * @remarks
+     *   When you call the DetachVServerGroups operation, you must use the following parameters to specify the vServer groups that you want to detach from your scaling group:
      *     *   LoadBalancerId: the ID of the load balancer
      *     *   VServerGroupId: the ID of the vServer group
      *     *   Port: the port number of the vServer group
      * *   When the vServer group specified by the request parameters matches that attached to your scaling group, this operation yields a favorable result. Otherwise, the request is ignored and no error is reported.
      * *   Before you call this operation, you must make sure that the load balancer has ceased routing the access traffic to the instances in the scaling group. Failure to do so may lead to service requests being dropped or lost during the detachment process.
      *
-     * @param request DetachVServerGroupsRequest
-     * @return DetachVServerGroupsResponse
+     * @param request - DetachVServerGroupsRequest
+     * @returns DetachVServerGroupsResponse
      */
     async detachVServerGroups(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.detachVServerGroupsWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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.
+     * @remarks
+     * 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
-     * @return DisableAlarmResponse
+     * @param request - DisableAlarmRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DisableAlarmResponse
      */
     async disableAlarmWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16542,27 +16609,29 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DisableAlarmResponse({}));
     }
     /**
-     * @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.
+     * 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.
+     * @remarks
+     * 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
+     * @param request - DisableAlarmRequest
+     * @returns DisableAlarmResponse
      */
     async disableAlarm(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.disableAlarmWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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:
+     * @remarks
+     * Before you call this operation to disable a scaling group, take note of the following items:
      * *   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
-     * @return DisableScalingGroupResponse
+     * @param request - DisableScalingGroupRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns DisableScalingGroupResponse
      */
     async disableScalingGroupWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16599,25 +16668,26 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DisableScalingGroupResponse({}));
     }
     /**
-     * @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.
+     * 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:
+     * @remarks
+     * Before you call this operation to disable a scaling group, take note of the following items:
      * *   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
+     * @param request - DisableScalingGroupRequest
+     * @returns DisableScalingGroupResponse
      */
     async disableScalingGroup(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.disableScalingGroupWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return EnableAlarmResponse
+     * @param request - EnableAlarmRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns EnableAlarmResponse
      */
     async enableAlarmWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16651,28 +16721,29 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new EnableAlarmResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - EnableAlarmRequest
+     * @returns EnableAlarmResponse
      */
     async enableAlarm(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.enableAlarmWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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 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.
+     * @remarks
+     *   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
-     * @return EnableScalingGroupResponse
+     * @param request - EnableScalingGroupRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns EnableScalingGroupResponse
      */
     async enableScalingGroupWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16730,34 +16801,36 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new EnableScalingGroupResponse({}));
     }
     /**
-     * @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.
+     * 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 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.
+     * @remarks
+     *   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
+     * @param request - EnableScalingGroupRequest
+     * @returns EnableScalingGroupResponse
      */
     async enableScalingGroup(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.enableScalingGroupWithOptions(request, runtime);
     }
     /**
-     * @summary Puts an Elastic Compute Service (ECS) instance into the Standby state.
+     * Puts an Elastic Compute Service (ECS) instance into the Standby state.
      *
-     * @description ## Description
+     * @remarks
+     * ## Description
      * *   If you call the operation to put an ECS instance in a scaling group that is associated with a Classic Load Balancer (CLB) instance into the Standby state, the weight of the ECS instance as a backend server of the CLB instance is set to 0.
      * *   You can remove an instance that is in the Standby state from a scaling group, and then release the instance.
      * *   ECS instances that are in the Standby state are not removed from the scaling group during scale-in activities triggered by event-triggered tasks.
      * *   If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, for example, the ECS instance is being stopped or being restarted, Auto Scaling does not update the health status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health 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
+     * @param request - EnterStandbyRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns EnterStandbyResponse
      */
     async enterStandbyWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16797,25 +16870,27 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new EnterStandbyResponse({}));
     }
     /**
-     * @summary Puts an Elastic Compute Service (ECS) instance into the Standby state.
+     * Puts an Elastic Compute Service (ECS) instance into the Standby state.
      *
-     * @description ## Description
+     * @remarks
+     * ## Description
      * *   If you call the operation to put an ECS instance in a scaling group that is associated with a Classic Load Balancer (CLB) instance into the Standby state, the weight of the ECS instance as a backend server of the CLB instance is set to 0.
      * *   You can remove an instance that is in the Standby state from a scaling group, and then release the instance.
      * *   ECS instances that are in the Standby state are not removed from the scaling group during scale-in activities triggered by event-triggered tasks.
      * *   If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, for example, the ECS instance is being stopped or being restarted, Auto Scaling does not update the health status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health status of the ECS instance only when the ECS instance is no longer in the Standby state.
      *
-     * @param request EnterStandbyRequest
-     * @return EnterStandbyResponse
+     * @param request - EnterStandbyRequest
+     * @returns EnterStandbyResponse
      */
     async enterStandby(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.enterStandbyWithOptions(request, runtime);
     }
     /**
-     * @summary Executes a scaling rule. To adjust the number of Elastic Compute Service (ECS) instances or elastic container instances, you can manually execute a scaling rule or enable Auto Scaling to execute a scaling rule. You can call the ExecuteScalingRule operation to execute simple scaling rules or step scaling rules. Auto Scaling automatically executes target tracking scaling rules and predictive scaling rules on your behalf without requiring explicit execution calls.
+     * Executes a scaling rule. To adjust the number of Elastic Compute Service (ECS) instances or elastic container instances, you can manually execute a scaling rule or enable Auto Scaling to execute a scaling rule. You can call the ExecuteScalingRule operation to execute simple scaling rules or step scaling rules. Auto Scaling automatically executes target tracking scaling rules and predictive scaling rules on your behalf without requiring explicit execution calls.
      *
-     * @description Before you call this operation, take note of the following items:
+     * @remarks
+     * 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.
@@ -16824,9 +16899,9 @@ class Client extends openapi_client_1.default {
      * 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.
      * You can specify only a limited number of ECS instances in each adjustment. For more information, see the description of the AdjustmentValue parameter in the CreateScalingRule topic.
      *
-     * @param request ExecuteScalingRuleRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ExecuteScalingRuleResponse
+     * @param request - ExecuteScalingRuleRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ExecuteScalingRuleResponse
      */
     async executeScalingRuleWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16875,9 +16950,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ExecuteScalingRuleResponse({}));
     }
     /**
-     * @summary Executes a scaling rule. To adjust the number of Elastic Compute Service (ECS) instances or elastic container instances, you can manually execute a scaling rule or enable Auto Scaling to execute a scaling rule. You can call the ExecuteScalingRule operation to execute simple scaling rules or step scaling rules. Auto Scaling automatically executes target tracking scaling rules and predictive scaling rules on your behalf without requiring explicit execution calls.
+     * Executes a scaling rule. To adjust the number of Elastic Compute Service (ECS) instances or elastic container instances, you can manually execute a scaling rule or enable Auto Scaling to execute a scaling rule. You can call the ExecuteScalingRule operation to execute simple scaling rules or step scaling rules. Auto Scaling automatically executes target tracking scaling rules and predictive scaling rules on your behalf without requiring explicit execution calls.
      *
-     * @description Before you call this operation, take note of the following items:
+     * @remarks
+     * 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.
@@ -16886,25 +16962,26 @@ class Client extends openapi_client_1.default {
      * 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.
      * You can specify only a limited number of ECS instances in each adjustment. For more information, see the description of the AdjustmentValue parameter in the CreateScalingRule topic.
      *
-     * @param request ExecuteScalingRuleRequest
-     * @return ExecuteScalingRuleResponse
+     * @param request - ExecuteScalingRuleRequest
+     * @returns ExecuteScalingRuleResponse
      */
     async executeScalingRule(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.executeScalingRuleWithOptions(request, runtime);
     }
     /**
-     * @summary Removes an instance from the Standby state. When a scale-in event is triggered in a scaling group, Auto Scaling does not remove Elastic Compute Service (ECS) instances or elastic container instances that are in the Standby state from the scaling group. If you want to restart the instances that are in the Standby state, you can call the ExitStandby operation to remove the instances from the Standby state and put them into the In Service state.
+     * Removes an instance from the Standby state. When a scale-in event is triggered in a scaling group, Auto Scaling does not remove Elastic Compute Service (ECS) instances or elastic container instances that are in the Standby state from the scaling group. If you want to restart the instances that are in the Standby state, you can call the ExitStandby operation to remove the instances from the Standby state and put them into the In Service state.
      *
-     * @description After ECS instances or elastic container instances are removed from the Standby state, the following rules apply:
+     * @remarks
+     * After ECS instances or elastic container instances are removed from the Standby state, the following rules apply:
      * *   The ECS instances or elastic container instances enter the In Service state.
      * *   The default weight of each ECS instance or elastic container instance as a backend server of the attached load balancer is 50.
      * *   If you stop or restart the ECS instances or elastic container instances, the health check status of the instances will be updated.
      * *   When a scale-in event is triggered, Auto Scaling may remove the ECS instances or elastic container instances from the scaling group.
      *
-     * @param request ExitStandbyRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ExitStandbyResponse
+     * @param request - ExitStandbyRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ExitStandbyResponse
      */
     async exitStandbyWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -16947,27 +17024,28 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ExitStandbyResponse({}));
     }
     /**
-     * @summary Removes an instance from the Standby state. When a scale-in event is triggered in a scaling group, Auto Scaling does not remove Elastic Compute Service (ECS) instances or elastic container instances that are in the Standby state from the scaling group. If you want to restart the instances that are in the Standby state, you can call the ExitStandby operation to remove the instances from the Standby state and put them into the In Service state.
+     * Removes an instance from the Standby state. When a scale-in event is triggered in a scaling group, Auto Scaling does not remove Elastic Compute Service (ECS) instances or elastic container instances that are in the Standby state from the scaling group. If you want to restart the instances that are in the Standby state, you can call the ExitStandby operation to remove the instances from the Standby state and put them into the In Service state.
      *
-     * @description After ECS instances or elastic container instances are removed from the Standby state, the following rules apply:
+     * @remarks
+     * After ECS instances or elastic container instances are removed from the Standby state, the following rules apply:
      * *   The ECS instances or elastic container instances enter the In Service state.
      * *   The default weight of each ECS instance or elastic container instance as a backend server of the attached load balancer is 50.
      * *   If you stop or restart the ECS instances or elastic container instances, the health check status of the instances will be updated.
      * *   When a scale-in event is triggered, Auto Scaling may remove the ECS instances or elastic container instances from the scaling group.
      *
-     * @param request ExitStandbyRequest
-     * @return ExitStandbyResponse
+     * @param request - ExitStandbyRequest
+     * @returns ExitStandbyResponse
      */
     async exitStandby(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.exitStandbyWithOptions(request, runtime);
     }
     /**
-     * @summary Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.
+     * Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.
      *
-     * @param request ListTagKeysRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ListTagKeysResponse
+     * @param request - ListTagKeysRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ListTagKeysResponse
      */
     async listTagKeysWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -17007,24 +17085,25 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ListTagKeysResponse({}));
     }
     /**
-     * @summary Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.
+     * Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.
      *
-     * @param request ListTagKeysRequest
-     * @return ListTagKeysResponse
+     * @param request - ListTagKeysRequest
+     * @returns ListTagKeysResponse
      */
     async listTagKeys(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.listTagKeysWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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.
+     * @remarks
+     *   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
-     * @return ListTagResourcesResponse
+     * @param request - ListTagResourcesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ListTagResourcesResponse
      */
     async listTagResourcesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -17067,24 +17146,25 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ListTagResourcesResponse({}));
     }
     /**
-     * @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.
+     * 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.
+     * @remarks
+     *   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
+     * @param request - ListTagResourcesRequest
+     * @returns ListTagResourcesResponse
      */
     async listTagResources(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.listTagResourcesWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return ListTagValuesResponse
+     * @param request - ListTagValuesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ListTagValuesResponse
      */
     async listTagValuesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -17127,27 +17207,28 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ListTagValuesResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - ListTagValuesRequest
+     * @returns ListTagValuesResponse
      */
     async listTagValues(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.listTagValuesWithOptions(request, runtime);
     }
     /**
-     * @summary Modifies an event-triggered task.
+     * Modifies an event-triggered task.
      *
-     * @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 the custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
+     * @remarks
+     *   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 the 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 metrics that are supported if 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.
      *
-     * @param request ModifyAlarmRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ModifyAlarmResponse
+     * @param request - ModifyAlarmRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyAlarmResponse
      */
     async modifyAlarmWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -17226,27 +17307,28 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyAlarmResponse({}));
     }
     /**
-     * @summary Modifies an event-triggered task.
+     * Modifies an event-triggered task.
      *
-     * @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 the custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
+     * @remarks
+     *   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 the 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 metrics that are supported if 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.
      *
-     * @param request ModifyAlarmRequest
-     * @return ModifyAlarmResponse
+     * @param request - ModifyAlarmRequest
+     * @returns ModifyAlarmResponse
      */
     async modifyAlarm(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyAlarmWithOptions(request, runtime);
     }
     /**
-     * @summary Sets the status of scaling activities that prompt text message or email notifications.
+     * Sets the status of scaling activities that prompt text message or email notifications.
      *
-     * @param request ModifyAlertConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ModifyAlertConfigurationResponse
+     * @param request - ModifyAlertConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyAlertConfigurationResponse
      */
     async modifyAlertConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -17283,23 +17365,25 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyAlertConfigurationResponse({}));
     }
     /**
-     * @summary Sets the status of scaling activities that prompt text message or email notifications.
+     * Sets the status of scaling activities that prompt text message or email notifications.
      *
-     * @param request ModifyAlertConfigurationRequest
-     * @return ModifyAlertConfigurationResponse
+     * @param request - ModifyAlertConfigurationRequest
+     * @returns ModifyAlertConfigurationResponse
      */
     async modifyAlertConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyAlertConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary Modifies a scaling configuration for a scaling group that contains elastic container instances.
+     * Modifies scaling configurations of the Elastic Container Instance type. When you call the ModifyEciScalingConfiguration operation, you can specify the ID, name, and instance properties of the desired scaling configuration to modify information such as the instance restart policy, instance bidding policy, and elastic IP address (EIP) bandwidth.
      *
-     * @description 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.
+     * @remarks
+     *   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 call the [ModifyEciScalingConfiguration](https://help.aliyun.com/document_detail/459378.html) operation to verify the modification result.
      *
-     * @param request ModifyEciScalingConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ModifyEciScalingConfigurationResponse
+     * @param request - ModifyEciScalingConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyEciScalingConfigurationResponse
      */
     async modifyEciScalingConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -17471,23 +17555,25 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyEciScalingConfigurationResponse({}));
     }
     /**
-     * @summary Modifies a scaling configuration for a scaling group that contains elastic container instances.
+     * Modifies scaling configurations of the Elastic Container Instance type. When you call the ModifyEciScalingConfiguration operation, you can specify the ID, name, and instance properties of the desired scaling configuration to modify information such as the instance restart policy, instance bidding policy, and elastic IP address (EIP) bandwidth.
      *
-     * @description 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.
+     * @remarks
+     *   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 call the [ModifyEciScalingConfiguration](https://help.aliyun.com/document_detail/459378.html) operation to verify the modification result.
      *
-     * @param request ModifyEciScalingConfigurationRequest
-     * @return ModifyEciScalingConfigurationResponse
+     * @param request - ModifyEciScalingConfigurationRequest
+     * @returns ModifyEciScalingConfigurationResponse
      */
     async modifyEciScalingConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyEciScalingConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary Modifies the attributes of an Elastic Compute Service (ECS) instance in a scaling group. You can call the ModifyInstanceAttribute operation to modify the lifecycle management attribute of a manually added ECS instance in a scaling group.
+     * Modifies the information of an Elastic Compute Service (ECS) instance. When you call the ModifyInstanceAttribute operation, you can specify attributes such as the instance ID, scaling group ID, and region ID to modify the attributes of an ECS instance in a scaling group. You can modify only the hosting attributes of instances that are manually added to scaling groups.
      *
-     * @param request ModifyInstanceAttributeRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ModifyInstanceAttributeResponse
+     * @param request - ModifyInstanceAttributeRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyInstanceAttributeResponse
      */
     async modifyInstanceAttributeWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -17527,25 +17613,26 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyInstanceAttributeResponse({}));
     }
     /**
-     * @summary Modifies the attributes of an Elastic Compute Service (ECS) instance in a scaling group. You can call the ModifyInstanceAttribute operation to modify the lifecycle management attribute of a manually added ECS instance in a scaling group.
+     * Modifies the information of an Elastic Compute Service (ECS) instance. When you call the ModifyInstanceAttribute operation, you can specify attributes such as the instance ID, scaling group ID, and region ID to modify the attributes of an ECS instance in a scaling group. You can modify only the hosting attributes of instances that are manually added to scaling groups.
      *
-     * @param request ModifyInstanceAttributeRequest
-     * @return ModifyInstanceAttributeResponse
+     * @param request - ModifyInstanceAttributeRequest
+     * @returns ModifyInstanceAttributeResponse
      */
     async modifyInstanceAttribute(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyInstanceAttributeWithOptions(request, runtime);
     }
     /**
-     * @summary Modifies a lifecycle hook. If an existing lifecycle hook does not meet your business requirements anymore, you can call the ModifyLifecycleHook operation to modify the information such as the scaling event, timeout period, and default action of the lifecycle hook. Before you modify a lifecycle hook, you can locate the lifecycle hook by its ID, name, or scaling group.
+     * Modifies a lifecycle hook. If an existing lifecycle hook does not meet your business requirements anymore, you can call the ModifyLifecycleHook operation to modify the information such as the scaling event, timeout period, and default action of the lifecycle hook. Before you modify a lifecycle hook, you can locate the lifecycle hook by its ID, name, or scaling group.
      *
-     * @description You can use one of the following methods to locate the lifecycle hook that you want to modify:
+     * @remarks
+     * You can use one of the following methods to locate the lifecycle hook that you want to modify:
      * *   Specify LifecycleHookId. In this case, ScalingGroupId and LifecycleHookName are ignored.
      * *   Specify ScalingGroupId and LifecycleHookName. Each lifecycle hook within a scaling group has a unique name.
      *
-     * @param request ModifyLifecycleHookRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ModifyLifecycleHookResponse
+     * @param request - ModifyLifecycleHookRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyLifecycleHookResponse
      */
     async modifyLifecycleHookWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -17606,25 +17693,26 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyLifecycleHookResponse({}));
     }
     /**
-     * @summary Modifies a lifecycle hook. If an existing lifecycle hook does not meet your business requirements anymore, you can call the ModifyLifecycleHook operation to modify the information such as the scaling event, timeout period, and default action of the lifecycle hook. Before you modify a lifecycle hook, you can locate the lifecycle hook by its ID, name, or scaling group.
+     * Modifies a lifecycle hook. If an existing lifecycle hook does not meet your business requirements anymore, you can call the ModifyLifecycleHook operation to modify the information such as the scaling event, timeout period, and default action of the lifecycle hook. Before you modify a lifecycle hook, you can locate the lifecycle hook by its ID, name, or scaling group.
      *
-     * @description You can use one of the following methods to locate the lifecycle hook that you want to modify:
+     * @remarks
+     * You can use one of the following methods to locate the lifecycle hook that you want to modify:
      * *   Specify LifecycleHookId. In this case, ScalingGroupId and LifecycleHookName are ignored.
      * *   Specify ScalingGroupId and LifecycleHookName. Each lifecycle hook within a scaling group has a unique name.
      *
-     * @param request ModifyLifecycleHookRequest
-     * @return ModifyLifecycleHookResponse
+     * @param request - ModifyLifecycleHookRequest
+     * @returns ModifyLifecycleHookResponse
      */
     async modifyLifecycleHook(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyLifecycleHookWithOptions(request, runtime);
     }
     /**
-     * @summary Modifies event notification rules. Event notification rules support automatic sending of notifications to CloudMonitor, Message Service (MNS) topics, or MNS queues when a specified type of events occur. This helps you learn about the dynamics of your scaling group at the earliest opportunity and further automate resource management. If an existing event notification rule does not meet your business requirements, you can call the ModifyNotificationConfiguration operation to modify the event notification rule, without the need to create a new rule. Take not that you cannot modify the notification method of an event notification rule by calling this operation.
+     * Modifies event notification rules. Event notification rules support automatic sending of notifications to CloudMonitor, Message Service (MNS) topics, or MNS queues when a specified type of events occur. This helps you learn about the dynamics of your scaling group at the earliest opportunity and further automate resource management. If an existing event notification rule does not meet your business requirements, you can call the ModifyNotificationConfiguration operation to modify the event notification rule, without the need to create a new rule. Take not that you cannot modify the notification method of an event notification rule by calling this operation.
      *
-     * @param request ModifyNotificationConfigurationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ModifyNotificationConfigurationResponse
+     * @param request - ModifyNotificationConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyNotificationConfigurationResponse
      */
     async modifyNotificationConfigurationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -17647,6 +17735,9 @@ class Client extends openapi_client_1.default {
         if (!tea_util_1.default.isUnset(request.scalingGroupId)) {
             query["ScalingGroupId"] = request.scalingGroupId;
         }
+        if (!tea_util_1.default.isUnset(request.timeZone)) {
+            query["TimeZone"] = request.timeZone;
+        }
         let req = new $OpenApi.OpenApiRequest({
             query: openapi_util_1.default.query(query),
         });
@@ -17664,23 +17755,24 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyNotificationConfigurationResponse({}));
     }
     /**
-     * @summary Modifies event notification rules. Event notification rules support automatic sending of notifications to CloudMonitor, Message Service (MNS) topics, or MNS queues when a specified type of events occur. This helps you learn about the dynamics of your scaling group at the earliest opportunity and further automate resource management. If an existing event notification rule does not meet your business requirements, you can call the ModifyNotificationConfiguration operation to modify the event notification rule, without the need to create a new rule. Take not that you cannot modify the notification method of an event notification rule by calling this operation.
+     * Modifies event notification rules. Event notification rules support automatic sending of notifications to CloudMonitor, Message Service (MNS) topics, or MNS queues when a specified type of events occur. This helps you learn about the dynamics of your scaling group at the earliest opportunity and further automate resource management. If an existing event notification rule does not meet your business requirements, you can call the ModifyNotificationConfiguration operation to modify the event notification rule, without the need to create a new rule. Take not that you cannot modify the notification method of an event notification rule by calling this operation.
      *
-     * @param request ModifyNotificationConfigurationRequest
-     * @return ModifyNotificationConfigurationResponse
+     * @param request - ModifyNotificationConfigurationRequest
+     * @returns ModifyNotificationConfigurationResponse
      */
     async modifyNotificationConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyNotificationConfigurationWithOptions(request, runtime);
     }
     /**
-     * @summary Modifies a scaling configuration.
+     * Modifies a scaling configuration.
      *
-     * @description You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
+     * @remarks
+     * 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
-     * @return ModifyScalingConfigurationResponse
+     * @param tmpReq - ModifyScalingConfigurationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyScalingConfigurationResponse
      */
     async modifyScalingConfigurationWithOptions(tmpReq, runtime) {
         tea_util_1.default.validateModel(tmpReq);
@@ -17869,21 +17961,23 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingConfigurationResponse({}));
     }
     /**
-     * @summary Modifies a scaling configuration.
+     * Modifies a scaling configuration.
      *
-     * @description You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
+     * @remarks
+     * 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
+     * @param request - ModifyScalingConfigurationRequest
+     * @returns ModifyScalingConfigurationResponse
      */
     async modifyScalingConfiguration(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyScalingConfigurationWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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 modify the following parameters by calling this operation:
+     * @remarks
+     *   You cannot modify the following parameters by calling this operation:
      *     *   RegionId
      *     *   LoadBalancerId
      *     **
@@ -17897,9 +17991,9 @@ class Client extends openapi_client_1.default {
      * *   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
-     * @return ModifyScalingGroupResponse
+     * @param request - ModifyScalingGroupRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyScalingGroupResponse
      */
     async modifyScalingGroupWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18017,9 +18111,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingGroupResponse({}));
     }
     /**
-     * @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.
+     * 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 modify the following parameters by calling this operation:
+     * @remarks
+     *   You cannot modify the following parameters by calling this operation:
      *     *   RegionId
      *     *   LoadBalancerId
      *     **
@@ -18033,19 +18128,19 @@ class Client extends openapi_client_1.default {
      * *   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
+     * @param request - ModifyScalingGroupRequest
+     * @returns ModifyScalingGroupResponse
      */
     async modifyScalingGroup(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyScalingGroupWithOptions(request, runtime);
     }
     /**
-     * @summary Modifies a scaling rule. If an existing scaling rule cannot meet your business requirements, you can call the ModifyScalingRule operation to modify the scaling rule, without the need to create a new one. This streamlines your workflow, enhancing operational efficiency while also contributing to cost optimization by avoiding redundant steps.
+     * Modifies a scaling rule. If an existing scaling rule cannot meet your business requirements, you can call the ModifyScalingRule operation to modify the scaling rule, without the need to create a new one. This streamlines your workflow, enhancing operational efficiency while also contributing to cost optimization by avoiding redundant steps.
      *
-     * @param request ModifyScalingRuleRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ModifyScalingRuleResponse
+     * @param request - ModifyScalingRuleRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyScalingRuleResponse
      */
     async modifyScalingRuleWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18136,26 +18231,27 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingRuleResponse({}));
     }
     /**
-     * @summary Modifies a scaling rule. If an existing scaling rule cannot meet your business requirements, you can call the ModifyScalingRule operation to modify the scaling rule, without the need to create a new one. This streamlines your workflow, enhancing operational efficiency while also contributing to cost optimization by avoiding redundant steps.
+     * Modifies a scaling rule. If an existing scaling rule cannot meet your business requirements, you can call the ModifyScalingRule operation to modify the scaling rule, without the need to create a new one. This streamlines your workflow, enhancing operational efficiency while also contributing to cost optimization by avoiding redundant steps.
      *
-     * @param request ModifyScalingRuleRequest
-     * @return ModifyScalingRuleResponse
+     * @param request - ModifyScalingRuleRequest
+     * @returns ModifyScalingRuleResponse
      */
     async modifyScalingRule(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyScalingRuleWithOptions(request, runtime);
     }
     /**
-     * @summary Modifies a scheduled task. If an existing scheduled task cannot meet your business requirements, you can call the ModifyScheduledTask operation to adjust its parameter settings including the scaling rule to execute and the boundary values of your scaling group, without the need to create a new scheduled task. This operation provides a flexible way to optimize scheduled tasks.
+     * Modifies a scheduled task. If an existing scheduled task cannot meet your business requirements, you can call the ModifyScheduledTask operation to adjust its parameter settings including the scaling rule to execute and the boundary values of your scaling group, without the need to create a new scheduled task. This operation provides a flexible way to optimize scheduled tasks.
      *
-     * @description You can use the following parameters to specify the scaling method of a scheduled task:
+     * @remarks
+     * You can use the following parameters to specify the scaling method of a scheduled task:
      * *   If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
      * *   If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
      * > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
      *
-     * @param request ModifyScheduledTaskRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ModifyScheduledTaskResponse
+     * @param request - ModifyScheduledTaskRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ModifyScheduledTaskResponse
      */
     async modifyScheduledTaskWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18231,24 +18327,26 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ModifyScheduledTaskResponse({}));
     }
     /**
-     * @summary Modifies a scheduled task. If an existing scheduled task cannot meet your business requirements, you can call the ModifyScheduledTask operation to adjust its parameter settings including the scaling rule to execute and the boundary values of your scaling group, without the need to create a new scheduled task. This operation provides a flexible way to optimize scheduled tasks.
+     * Modifies a scheduled task. If an existing scheduled task cannot meet your business requirements, you can call the ModifyScheduledTask operation to adjust its parameter settings including the scaling rule to execute and the boundary values of your scaling group, without the need to create a new scheduled task. This operation provides a flexible way to optimize scheduled tasks.
      *
-     * @description You can use the following parameters to specify the scaling method of a scheduled task:
+     * @remarks
+     * You can use the following parameters to specify the scaling method of a scheduled task:
      * *   If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
      * *   If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
      * > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
      *
-     * @param request ModifyScheduledTaskRequest
-     * @return ModifyScheduledTaskResponse
+     * @param request - ModifyScheduledTaskRequest
+     * @returns ModifyScheduledTaskResponse
      */
     async modifyScheduledTask(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.modifyScheduledTaskWithOptions(request, runtime);
     }
     /**
-     * @summary Rebalances the distribution of Elastic Compute Service (ECS) instances across zones. If ECS instances are unevenly distributed across multiple zones, you can call the RebalanceInstances operation to rebalance the distribution of the ECS instances across the zones.
+     * Rebalances the distribution of Elastic Compute Service (ECS) instances across zones. If ECS instances are unevenly distributed across multiple zones, you can call the RebalanceInstances operation to rebalance the distribution of the ECS instances across the zones.
      *
-     * @description ## [](#)Usage notes
+     * @remarks
+     * ## [](#)Usage notes
      * Auto Scaling creates new ECS instances to replace the existing ECS instances to fulfill the rebalancing purpose. Auto Scaling starts the new ECS instances before stopping the existing ECS instances. The rebalancing operation does not affect the performance or service availability of your application.
      * *   This operation is supported by only multi-zone scaling groups whose `MultiAZPolicy` is set to `BALANCE`.
      * *   A rebalancing operation is required only when the distribution of the instances of a multi-zone scaling group is significantly unbalanced. In a rebalancing activity, Auto Scaling replaces up to 20 ECS instances to rectify the unbalanced distribution.
@@ -18256,9 +18354,9 @@ class Client extends openapi_client_1.default {
      *     **
      *     **Note** If the 10% increment of the maximum number of instances in a scaling group yield a non-integer value, the decimal portion is always rounded up to ensure an additional instance is accounted for. For example, you have a scaling group that holds a maximum of 15 ECS instances. During a rebalancing operation, Auto Scaling would permit the total number of instances to momentarily surpass this limit by 2, instead of the calculated 10% (which is 1.5).
      *
-     * @param request RebalanceInstancesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return RebalanceInstancesResponse
+     * @param request - RebalanceInstancesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns RebalanceInstancesResponse
      */
     async rebalanceInstancesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18298,9 +18396,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new RebalanceInstancesResponse({}));
     }
     /**
-     * @summary Rebalances the distribution of Elastic Compute Service (ECS) instances across zones. If ECS instances are unevenly distributed across multiple zones, you can call the RebalanceInstances operation to rebalance the distribution of the ECS instances across the zones.
+     * Rebalances the distribution of Elastic Compute Service (ECS) instances across zones. If ECS instances are unevenly distributed across multiple zones, you can call the RebalanceInstances operation to rebalance the distribution of the ECS instances across the zones.
      *
-     * @description ## [](#)Usage notes
+     * @remarks
+     * ## [](#)Usage notes
      * Auto Scaling creates new ECS instances to replace the existing ECS instances to fulfill the rebalancing purpose. Auto Scaling starts the new ECS instances before stopping the existing ECS instances. The rebalancing operation does not affect the performance or service availability of your application.
      * *   This operation is supported by only multi-zone scaling groups whose `MultiAZPolicy` is set to `BALANCE`.
      * *   A rebalancing operation is required only when the distribution of the instances of a multi-zone scaling group is significantly unbalanced. In a rebalancing activity, Auto Scaling replaces up to 20 ECS instances to rectify the unbalanced distribution.
@@ -18308,22 +18407,23 @@ class Client extends openapi_client_1.default {
      *     **
      *     **Note** If the 10% increment of the maximum number of instances in a scaling group yield a non-integer value, the decimal portion is always rounded up to ensure an additional instance is accounted for. For example, you have a scaling group that holds a maximum of 15 ECS instances. During a rebalancing operation, Auto Scaling would permit the total number of instances to momentarily surpass this limit by 2, instead of the calculated 10% (which is 1.5).
      *
-     * @param request RebalanceInstancesRequest
-     * @return RebalanceInstancesResponse
+     * @param request - RebalanceInstancesRequest
+     * @returns RebalanceInstancesResponse
      */
     async rebalanceInstances(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.rebalanceInstancesWithOptions(request, runtime);
     }
     /**
-     * @summary Extends the time window during which Elastic Compute Service (ECS) instances stay in a Pending state. If the current time window during which an ECS instance stays in a Pending state is not sufficient for you to complete custom operations on the ECS instance, you can call the RecordLifecycleActionHeartbeat operation to extend the time window. When you call this operation, you can specify lifecycleHookId, lifecycleActionToken, and heartbeatTimeout to extend the time window for the desired ECS instance.
+     * Extends the time window during which Elastic Compute Service (ECS) instances stay in a Pending state. If the current time window during which an ECS instance stays in a Pending state is not sufficient for you to complete custom operations on the ECS instance, you can call the RecordLifecycleActionHeartbeat operation to extend the time window. When you call this operation, you can specify lifecycleHookId, lifecycleActionToken, and heartbeatTimeout to extend the time window for the desired ECS instance.
      *
-     * @description You can call this operation only when the desired ECS instance enters a Pending state.\\
+     * @remarks
+     * You can call this operation only when the desired ECS instance enters a Pending state.\\
      * An ECS instance can stay in a Pending state for up to six hours. Each time an ECS instance enters a Pending state, you can extend the time window during which the ECS instance stays in a Pending state up to 20 times.
      *
-     * @param request RecordLifecycleActionHeartbeatRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return RecordLifecycleActionHeartbeatResponse
+     * @param request - RecordLifecycleActionHeartbeatRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns RecordLifecycleActionHeartbeatResponse
      */
     async recordLifecycleActionHeartbeatWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18366,22 +18466,24 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new RecordLifecycleActionHeartbeatResponse({}));
     }
     /**
-     * @summary Extends the time window during which Elastic Compute Service (ECS) instances stay in a Pending state. If the current time window during which an ECS instance stays in a Pending state is not sufficient for you to complete custom operations on the ECS instance, you can call the RecordLifecycleActionHeartbeat operation to extend the time window. When you call this operation, you can specify lifecycleHookId, lifecycleActionToken, and heartbeatTimeout to extend the time window for the desired ECS instance.
+     * Extends the time window during which Elastic Compute Service (ECS) instances stay in a Pending state. If the current time window during which an ECS instance stays in a Pending state is not sufficient for you to complete custom operations on the ECS instance, you can call the RecordLifecycleActionHeartbeat operation to extend the time window. When you call this operation, you can specify lifecycleHookId, lifecycleActionToken, and heartbeatTimeout to extend the time window for the desired ECS instance.
      *
-     * @description You can call this operation only when the desired ECS instance enters a Pending state.\\
+     * @remarks
+     * You can call this operation only when the desired ECS instance enters a Pending state.\\
      * An ECS instance can stay in a Pending state for up to six hours. Each time an ECS instance enters a Pending state, you can extend the time window during which the ECS instance stays in a Pending state up to 20 times.
      *
-     * @param request RecordLifecycleActionHeartbeatRequest
-     * @return RecordLifecycleActionHeartbeatResponse
+     * @param request - RecordLifecycleActionHeartbeatRequest
+     * @returns RecordLifecycleActionHeartbeatResponse
      */
     async recordLifecycleActionHeartbeat(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.recordLifecycleActionHeartbeatWithOptions(request, runtime);
     }
     /**
-     * @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
+     * Removes one or more instances from a scaling group. If your scaling group is enabled and contains no ongoing scaling activities, you can call the RemoveInstances operation to remove instances that you no longer require from the scaling group.
      *
-     * @description *   Before you call this operation, make sure that the following requirements are met:
+     * @remarks
+     *   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.
@@ -18390,9 +18492,9 @@ class Client extends openapi_client_1.default {
      * *   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
+     * @param request - RemoveInstancesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns RemoveInstancesResponse
      */
     async removeInstancesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18447,9 +18549,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new RemoveInstancesResponse({}));
     }
     /**
-     * @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
+     * Removes one or more instances from a scaling group. If your scaling group is enabled and contains no ongoing scaling activities, you can call the RemoveInstances operation to remove instances that you no longer require from the scaling group.
      *
-     * @description *   Before you call this operation, make sure that the following requirements are met:
+     * @remarks
+     *   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.
@@ -18458,19 +18561,19 @@ class Client extends openapi_client_1.default {
      * *   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
+     * @param request - RemoveInstancesRequest
+     * @returns RemoveInstancesResponse
      */
     async removeInstances(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.removeInstancesWithOptions(request, runtime);
     }
     /**
-     * @summary Resumes suspended processes in a scaling group.
+     * Resumes suspended processes in a scaling group.
      *
-     * @param request ResumeProcessesRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return ResumeProcessesResponse
+     * @param request - ResumeProcessesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ResumeProcessesResponse
      */
     async resumeProcessesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18510,19 +18613,20 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ResumeProcessesResponse({}));
     }
     /**
-     * @summary Resumes suspended processes in a scaling group.
+     * Resumes suspended processes in a scaling group.
      *
-     * @param request ResumeProcessesRequest
-     * @return ResumeProcessesResponse
+     * @param request - ResumeProcessesRequest
+     * @returns ResumeProcessesResponse
      */
     async resumeProcesses(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.resumeProcessesWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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 *   Before you call this operation, take note of the following items:
+     * @remarks
+     *   Before you call this operation, take note of the following items:
      *     *   The scaling group is in the Active state.
      *     *   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.
@@ -18530,9 +18634,9 @@ class Client extends openapi_client_1.default {
      * *   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
-     * @return ScaleWithAdjustmentResponse
+     * @param tmpReq - ScaleWithAdjustmentRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns ScaleWithAdjustmentResponse
      */
     async scaleWithAdjustmentWithOptions(tmpReq, runtime) {
         tea_util_1.default.validateModel(tmpReq);
@@ -18595,9 +18699,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new ScaleWithAdjustmentResponse({}));
     }
     /**
-     * @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.
+     * 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 *   Before you call this operation, take note of the following items:
+     * @remarks
+     *   Before you call this operation, take note of the following items:
      *     *   The scaling group is in the Active state.
      *     *   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.
@@ -18605,19 +18710,19 @@ class Client extends openapi_client_1.default {
      * *   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
+     * @param request - ScaleWithAdjustmentRequest
+     * @returns ScaleWithAdjustmentResponse
      */
     async scaleWithAdjustment(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.scaleWithAdjustmentWithOptions(request, runtime);
     }
     /**
-     * @summary Sets deletion protection for a scaling group. If you enable deletion protection for a scaling group, you cannot delete the scaling group. If you disable deletion protection for a scaling group, you can directly delete the scaling group. You can call the SetGroupDeletionProtection operation to enable or disable deletion protection.
+     * Sets deletion protection for a scaling group. If you enable deletion protection for a scaling group, you cannot delete the scaling group. If you disable deletion protection for a scaling group, you can directly delete the scaling group. You can call the SetGroupDeletionProtection operation to enable or disable deletion protection.
      *
-     * @param request SetGroupDeletionProtectionRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return SetGroupDeletionProtectionResponse
+     * @param request - SetGroupDeletionProtectionRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns SetGroupDeletionProtectionResponse
      */
     async setGroupDeletionProtectionWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18654,23 +18759,24 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new SetGroupDeletionProtectionResponse({}));
     }
     /**
-     * @summary Sets deletion protection for a scaling group. If you enable deletion protection for a scaling group, you cannot delete the scaling group. If you disable deletion protection for a scaling group, you can directly delete the scaling group. You can call the SetGroupDeletionProtection operation to enable or disable deletion protection.
+     * Sets deletion protection for a scaling group. If you enable deletion protection for a scaling group, you cannot delete the scaling group. If you disable deletion protection for a scaling group, you can directly delete the scaling group. You can call the SetGroupDeletionProtection operation to enable or disable deletion protection.
      *
-     * @param request SetGroupDeletionProtectionRequest
-     * @return SetGroupDeletionProtectionResponse
+     * @param request - SetGroupDeletionProtectionRequest
+     * @returns SetGroupDeletionProtectionResponse
      */
     async setGroupDeletionProtection(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.setGroupDeletionProtectionWithOptions(request, runtime);
     }
     /**
-     * @summary Sets instance health. At times, the automatic health check system might not sufficiently determine the precise health status of your Elastic Compute Service (ECS) instances or elastic container instances. To overcome this, you can call the SetInstanceHealth operation to swiftly pinpoint problematic instances and resolve issues. This operation is designed to more precisely align with real-world business requirements and tackle O\\&M hurdles efficiently.
+     * Sets instance health. At times, the automatic health check system might not sufficiently determine the precise health status of your Elastic Compute Service (ECS) instances or elastic container instances. To overcome this, you can call the SetInstanceHealth operation to swiftly pinpoint problematic instances and resolve issues. This operation is designed to more precisely align with real-world business requirements and tackle O\\&M hurdles efficiently.
      *
-     * @description Auto Scaling detects and removes unhealthy ECS instances or elastic container instances from the corresponding scaling groups. If you want to retain a specific instance in the corresponding scaling group, you can put the instance into the Standby or Protected state. For more information, see [EnterStandby](~~EnterStandby~~) and [SetInstancesProtection](~~SetInstancesProtection~~).
+     * @remarks
+     * Auto Scaling detects and removes unhealthy ECS instances or elastic container instances from the corresponding scaling groups. If you want to retain a specific instance in the corresponding scaling group, you can put the instance into the Standby or Protected state. For more information, see [EnterStandby](~~EnterStandby~~) and [SetInstancesProtection](~~SetInstancesProtection~~).
      *
-     * @param request SetInstanceHealthRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return SetInstanceHealthResponse
+     * @param request - SetInstanceHealthRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns SetInstanceHealthResponse
      */
     async setInstanceHealthWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18704,28 +18810,30 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new SetInstanceHealthResponse({}));
     }
     /**
-     * @summary Sets instance health. At times, the automatic health check system might not sufficiently determine the precise health status of your Elastic Compute Service (ECS) instances or elastic container instances. To overcome this, you can call the SetInstanceHealth operation to swiftly pinpoint problematic instances and resolve issues. This operation is designed to more precisely align with real-world business requirements and tackle O\\&M hurdles efficiently.
+     * Sets instance health. At times, the automatic health check system might not sufficiently determine the precise health status of your Elastic Compute Service (ECS) instances or elastic container instances. To overcome this, you can call the SetInstanceHealth operation to swiftly pinpoint problematic instances and resolve issues. This operation is designed to more precisely align with real-world business requirements and tackle O\\&M hurdles efficiently.
      *
-     * @description Auto Scaling detects and removes unhealthy ECS instances or elastic container instances from the corresponding scaling groups. If you want to retain a specific instance in the corresponding scaling group, you can put the instance into the Standby or Protected state. For more information, see [EnterStandby](~~EnterStandby~~) and [SetInstancesProtection](~~SetInstancesProtection~~).
+     * @remarks
+     * Auto Scaling detects and removes unhealthy ECS instances or elastic container instances from the corresponding scaling groups. If you want to retain a specific instance in the corresponding scaling group, you can put the instance into the Standby or Protected state. For more information, see [EnterStandby](~~EnterStandby~~) and [SetInstancesProtection](~~SetInstancesProtection~~).
      *
-     * @param request SetInstanceHealthRequest
-     * @return SetInstanceHealthResponse
+     * @param request - SetInstanceHealthRequest
+     * @returns SetInstanceHealthResponse
      */
     async setInstanceHealth(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.setInstanceHealthWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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 Once ECS instances enter the Protected state, they become subject to the following restrictions:
+     * @remarks
+     * 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
-     * @return SetInstancesProtectionResponse
+     * @param request - SetInstancesProtectionRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns SetInstancesProtectionResponse
      */
     async setInstancesProtectionWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18762,26 +18870,27 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new SetInstancesProtectionResponse({}));
     }
     /**
-     * @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.
+     * 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 Once ECS instances enter the Protected state, they become subject to the following restrictions:
+     * @remarks
+     * 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
+     * @param request - SetInstancesProtectionRequest
+     * @returns SetInstancesProtectionResponse
      */
     async setInstancesProtection(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.setInstancesProtectionWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return SuspendProcessesResponse
+     * @param request - SuspendProcessesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns SuspendProcessesResponse
      */
     async suspendProcessesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18821,19 +18930,20 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new SuspendProcessesResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - SuspendProcessesRequest
+     * @returns SuspendProcessesResponse
      */
     async suspendProcesses(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.suspendProcessesWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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.
+     * @remarks
+     *   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.
@@ -18841,9 +18951,9 @@ class Client extends openapi_client_1.default {
      *     *   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
-     * @return TagResourcesResponse
+     * @param request - TagResourcesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns TagResourcesResponse
      */
     async tagResourcesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18883,9 +18993,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new TagResourcesResponse({}));
     }
     /**
-     * @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.
+     * 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.
+     * @remarks
+     *   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.
@@ -18893,19 +19004,19 @@ class Client extends openapi_client_1.default {
      *     *   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
+     * @param request - TagResourcesRequest
+     * @returns TagResourcesResponse
      */
     async tagResources(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.tagResourcesWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return UntagResourcesResponse
+     * @param request - UntagResourcesRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns UntagResourcesResponse
      */
     async untagResourcesWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18948,21 +19059,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new UntagResourcesResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - UntagResourcesRequest
+     * @returns UntagResourcesResponse
      */
     async untagResources(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.untagResourcesWithOptions(request, runtime);
     }
     /**
-     * @summary Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
+     * Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
      *
-     * @param request VerifyAuthenticationRequest
-     * @param runtime runtime options for this request RuntimeOptions
-     * @return VerifyAuthenticationResponse
+     * @param request - VerifyAuthenticationRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns VerifyAuthenticationResponse
      */
     async verifyAuthenticationWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -18999,21 +19110,21 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new VerifyAuthenticationResponse({}));
     }
     /**
-     * @summary Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
+     * Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
      *
-     * @param request VerifyAuthenticationRequest
-     * @return VerifyAuthenticationResponse
+     * @param request - VerifyAuthenticationRequest
+     * @returns VerifyAuthenticationResponse
      */
     async verifyAuthentication(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.verifyAuthenticationWithOptions(request, runtime);
     }
     /**
-     * @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.
+     * 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
-     * @return VerifyUserResponse
+     * @param request - VerifyUserRequest
+     * @param runtime - runtime options for this request RuntimeOptions
+     * @returns VerifyUserResponse
      */
     async verifyUserWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
@@ -19047,10 +19158,10 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new VerifyUserResponse({}));
     }
     /**
-     * @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.
+     * 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
+     * @param request - VerifyUserRequest
+     * @returns VerifyUserResponse
      */
     async verifyUser(request) {
         let runtime = new $Util.RuntimeOptions({});