@alicloud/ess20220222 1.0.3 → 1.0.5

package/dist/client.d.ts

@@ -151,6 +151,7 @@ export declare class AttachLoadBalancersRequest extends $tea.Model {
     async?: boolean;
     clientToken?: string;
     forceAttach?: boolean;
+    loadBalancerConfigs?: AttachLoadBalancersRequestLoadBalancerConfigs[];
     loadBalancers?: string[];
     ownerId?: number;
     resourceOwnerAccount?: string;
@@ -618,6 +619,7 @@ export declare class CreateNotificationConfigurationResponse extends $tea.Model
     });
 }
 export declare class CreateScalingConfigurationRequest extends $tea.Model {
+    imageOptions?: CreateScalingConfigurationRequestImageOptions;
     privatePoolOptions?: CreateScalingConfigurationRequestPrivatePoolOptions;
     systemDisk?: CreateScalingConfigurationRequestSystemDisk;
     affinity?: string;
@@ -681,6 +683,7 @@ export declare class CreateScalingConfigurationRequest extends $tea.Model {
     });
 }
 export declare class CreateScalingConfigurationShrinkRequest extends $tea.Model {
+    imageOptions?: CreateScalingConfigurationShrinkRequestImageOptions;
     privatePoolOptions?: CreateScalingConfigurationShrinkRequestPrivatePoolOptions;
     systemDisk?: CreateScalingConfigurationShrinkRequestSystemDisk;
     affinity?: string;
@@ -789,6 +792,7 @@ export declare class CreateScalingGroupRequest extends $tea.Model {
     launchTemplateOverrides?: CreateScalingGroupRequestLaunchTemplateOverrides[];
     launchTemplateVersion?: string;
     lifecycleHooks?: CreateScalingGroupRequestLifecycleHooks[];
+    loadBalancerConfigs?: CreateScalingGroupRequestLoadBalancerConfigs[];
     loadBalancerIds?: string;
     maxInstanceLifetime?: number;
     maxSize?: number;
@@ -855,6 +859,7 @@ export declare class CreateScalingGroupResponse extends $tea.Model {
 export declare class CreateScalingRuleRequest extends $tea.Model {
     adjustmentType?: string;
     adjustmentValue?: number;
+    alarmDimensions?: CreateScalingRuleRequestAlarmDimensions[];
     cooldown?: number;
     disableScaleIn?: boolean;
     estimatedInstanceWarmup?: number;
@@ -1599,6 +1604,7 @@ export declare class DescribeLimitationResponseBody extends $tea.Model {
     maxNumberOfLoadBalancers?: number;
     maxNumberOfMaxSize?: number;
     maxNumberOfMinSize?: number;
+    maxNumberOfNlbServerGroup?: number;
     maxNumberOfNotificationConfigurations?: number;
     maxNumberOfScalingConfigurations?: number;
     maxNumberOfScalingGroups?: number;
@@ -1971,6 +1977,7 @@ export declare class DescribeScalingGroupsResponse extends $tea.Model {
 }
 export declare class DescribeScalingInstancesRequest extends $tea.Model {
     creationType?: string;
+    creationTypes?: string[];
     healthStatus?: string;
     instanceIds?: string[];
     lifecycleState?: string;
@@ -3129,6 +3136,7 @@ export declare class ModifyNotificationConfigurationResponse extends $tea.Model
     });
 }
 export declare class ModifyScalingConfigurationRequest extends $tea.Model {
+    imageOptions?: ModifyScalingConfigurationRequestImageOptions;
     privatePoolOptions?: ModifyScalingConfigurationRequestPrivatePoolOptions;
     systemDisk?: ModifyScalingConfigurationRequestSystemDisk;
     affinity?: string;
@@ -3188,6 +3196,7 @@ export declare class ModifyScalingConfigurationRequest extends $tea.Model {
     });
 }
 export declare class ModifyScalingConfigurationShrinkRequest extends $tea.Model {
+    imageOptions?: ModifyScalingConfigurationShrinkRequestImageOptions;
     privatePoolOptions?: ModifyScalingConfigurationShrinkRequestPrivatePoolOptions;
     systemDisk?: ModifyScalingConfigurationShrinkRequestSystemDisk;
     affinity?: string;
@@ -3343,6 +3352,7 @@ export declare class ModifyScalingGroupResponse extends $tea.Model {
 export declare class ModifyScalingRuleRequest extends $tea.Model {
     adjustmentType?: string;
     adjustmentValue?: number;
+    alarmDimensions?: ModifyScalingRuleRequestAlarmDimensions[];
     cooldown?: number;
     disableScaleIn?: boolean;
     estimatedInstanceWarmup?: number;
@@ -4006,6 +4016,7 @@ export declare class VerifyAuthenticationResponse extends $tea.Model {
 }
 export declare class VerifyUserRequest extends $tea.Model {
     ownerId?: number;
+    regionId?: string;
     resourceOwnerAccount?: string;
     resourceOwnerId?: number;
     static names(): {
@@ -4060,6 +4071,19 @@ export declare class AttachAlbServerGroupsRequestAlbServerGroups extends $tea.Mo
         [key: string]: any;
     });
 }
+export declare class AttachLoadBalancersRequestLoadBalancerConfigs extends $tea.Model {
+    loadBalancerId?: string;
+    weight?: number;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class AttachServerGroupsRequestServerGroups extends $tea.Model {
     port?: number;
     serverGroupId?: string;
@@ -4185,13 +4209,13 @@ export declare class CreateEciScalingConfigurationRequestContainersLivenessProbe
     });
 }
 export declare class CreateEciScalingConfigurationRequestContainersLivenessProbe extends $tea.Model {
-    exec: CreateEciScalingConfigurationRequestContainersLivenessProbeExec;
+    exec?: CreateEciScalingConfigurationRequestContainersLivenessProbeExec;
     failureThreshold?: number;
-    httpGet: CreateEciScalingConfigurationRequestContainersLivenessProbeHttpGet;
+    httpGet?: CreateEciScalingConfigurationRequestContainersLivenessProbeHttpGet;
     initialDelaySeconds?: number;
     periodSeconds?: number;
     successThreshold?: number;
-    tcpSocket: CreateEciScalingConfigurationRequestContainersLivenessProbeTcpSocket;
+    tcpSocket?: CreateEciScalingConfigurationRequestContainersLivenessProbeTcpSocket;
     timeoutSeconds?: number;
     static names(): {
         [key: string]: string;
@@ -4242,13 +4266,13 @@ export declare class CreateEciScalingConfigurationRequestContainersReadinessProb
     });
 }
 export declare class CreateEciScalingConfigurationRequestContainersReadinessProbe extends $tea.Model {
-    exec: CreateEciScalingConfigurationRequestContainersReadinessProbeExec;
+    exec?: CreateEciScalingConfigurationRequestContainersReadinessProbeExec;
     failureThreshold?: number;
-    httpGet: CreateEciScalingConfigurationRequestContainersReadinessProbeHttpGet;
+    httpGet?: CreateEciScalingConfigurationRequestContainersReadinessProbeHttpGet;
     initialDelaySeconds?: number;
     periodSeconds?: number;
     successThreshold?: number;
-    tcpSocket: CreateEciScalingConfigurationRequestContainersReadinessProbeTcpSocket;
+    tcpSocket?: CreateEciScalingConfigurationRequestContainersReadinessProbeTcpSocket;
     timeoutSeconds?: number;
     static names(): {
         [key: string]: string;
@@ -4273,7 +4297,7 @@ export declare class CreateEciScalingConfigurationRequestContainersSecurityConte
     });
 }
 export declare class CreateEciScalingConfigurationRequestContainersSecurityContext extends $tea.Model {
-    capability: CreateEciScalingConfigurationRequestContainersSecurityContextCapability;
+    capability?: CreateEciScalingConfigurationRequestContainersSecurityContextCapability;
     readOnlyRootFilesystem?: boolean;
     runAsUser?: number;
     static names(): {
@@ -4330,9 +4354,9 @@ export declare class CreateEciScalingConfigurationRequestContainersVolumeMounts
     });
 }
 export declare class CreateEciScalingConfigurationRequestContainers extends $tea.Model {
-    livenessProbe: CreateEciScalingConfigurationRequestContainersLivenessProbe;
-    readinessProbe: CreateEciScalingConfigurationRequestContainersReadinessProbe;
-    securityContext: CreateEciScalingConfigurationRequestContainersSecurityContext;
+    livenessProbe?: CreateEciScalingConfigurationRequestContainersLivenessProbe;
+    readinessProbe?: CreateEciScalingConfigurationRequestContainersReadinessProbe;
+    securityContext?: CreateEciScalingConfigurationRequestContainersSecurityContext;
     args?: string[];
     commands?: string[];
     cpu?: number;
@@ -4411,7 +4435,7 @@ export declare class CreateEciScalingConfigurationRequestInitContainersSecurityC
     });
 }
 export declare class CreateEciScalingConfigurationRequestInitContainersSecurityContext extends $tea.Model {
-    capability: CreateEciScalingConfigurationRequestInitContainersSecurityContextCapability;
+    capability?: CreateEciScalingConfigurationRequestInitContainersSecurityContextCapability;
     readOnlyRootFilesystem?: boolean;
     runAsUser?: number;
     static names(): {
@@ -4468,7 +4492,7 @@ export declare class CreateEciScalingConfigurationRequestInitContainersInitConta
     });
 }
 export declare class CreateEciScalingConfigurationRequestInitContainers extends $tea.Model {
-    securityContext: CreateEciScalingConfigurationRequestInitContainersSecurityContext;
+    securityContext?: CreateEciScalingConfigurationRequestInitContainersSecurityContext;
     args?: string[];
     commands?: string[];
     cpu?: number;
@@ -4533,6 +4557,7 @@ export declare class CreateEciScalingConfigurationRequestVolumesDiskVolume exten
 }
 export declare class CreateEciScalingConfigurationRequestVolumesEmptyDirVolume extends $tea.Model {
     medium?: string;
+    sizeLimit?: string;
     static names(): {
         [key: string]: string;
     };
@@ -4599,11 +4624,11 @@ export declare class CreateEciScalingConfigurationRequestVolumesConfigFileVolume
     });
 }
 export declare class CreateEciScalingConfigurationRequestVolumes extends $tea.Model {
-    diskVolume: CreateEciScalingConfigurationRequestVolumesDiskVolume;
-    emptyDirVolume: CreateEciScalingConfigurationRequestVolumesEmptyDirVolume;
-    flexVolume: CreateEciScalingConfigurationRequestVolumesFlexVolume;
-    hostPathVolume: CreateEciScalingConfigurationRequestVolumesHostPathVolume;
-    NFSVolume: CreateEciScalingConfigurationRequestVolumesNFSVolume;
+    diskVolume?: CreateEciScalingConfigurationRequestVolumesDiskVolume;
+    emptyDirVolume?: CreateEciScalingConfigurationRequestVolumesEmptyDirVolume;
+    flexVolume?: CreateEciScalingConfigurationRequestVolumesFlexVolume;
+    hostPathVolume?: CreateEciScalingConfigurationRequestVolumesHostPathVolume;
+    NFSVolume?: CreateEciScalingConfigurationRequestVolumesNFSVolume;
     configFileVolumeConfigFileToPaths?: CreateEciScalingConfigurationRequestVolumesConfigFileVolumeConfigFileToPaths[];
     configFileVolumeDefaultMode?: number;
     name?: string;
@@ -4618,6 +4643,18 @@ export declare class CreateEciScalingConfigurationRequestVolumes extends $tea.Mo
         [key: string]: any;
     });
 }
+export declare class CreateScalingConfigurationRequestImageOptions extends $tea.Model {
+    loginAsNonRoot?: boolean;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class CreateScalingConfigurationRequestPrivatePoolOptions extends $tea.Model {
     id?: string;
     matchCriteria?: string;
@@ -4722,6 +4759,18 @@ export declare class CreateScalingConfigurationRequestSpotPriceLimits extends $t
         [key: string]: any;
     });
 }
+export declare class CreateScalingConfigurationShrinkRequestImageOptions extends $tea.Model {
+    loginAsNonRoot?: boolean;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class CreateScalingConfigurationShrinkRequestPrivatePoolOptions extends $tea.Model {
     id?: string;
     matchCriteria?: string;
@@ -4871,6 +4920,19 @@ export declare class CreateScalingGroupRequestLifecycleHooks extends $tea.Model
         [key: string]: any;
     });
 }
+export declare class CreateScalingGroupRequestLoadBalancerConfigs extends $tea.Model {
+    loadBalancerId?: string;
+    weight?: number;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class CreateScalingGroupRequestServerGroups extends $tea.Model {
     port?: number;
     serverGroupId?: string;
@@ -4926,6 +4988,19 @@ export declare class CreateScalingGroupRequestVServerGroups extends $tea.Model {
         [key: string]: any;
     });
 }
+export declare class CreateScalingRuleRequestAlarmDimensions extends $tea.Model {
+    dimensionKey?: string;
+    dimensionValue?: string;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class CreateScalingRuleRequestStepAdjustments extends $tea.Model {
     metricIntervalLowerBound?: number;
     metricIntervalUpperBound?: number;
@@ -5261,6 +5336,7 @@ export declare class DescribeEciScalingConfigurationsResponseBodyScalingConfigur
     diskVolumeDiskSize?: number;
     diskVolumeFsType?: string;
     emptyDirVolumeMedium?: string;
+    emptyDirVolumeSizeLimit?: string;
     flexVolumeDriver?: string;
     flexVolumeFsType?: string;
     flexVolumeOptions?: string;
@@ -5532,7 +5608,7 @@ export declare class DescribeScalingConfigurationsResponseBodyScalingConfigurati
     });
 }
 export declare class DescribeScalingConfigurationsResponseBodyScalingConfigurations extends $tea.Model {
-    privatePoolOptions: DescribeScalingConfigurationsResponseBodyScalingConfigurationsPrivatePoolOptions;
+    privatePoolOptions?: DescribeScalingConfigurationsResponseBodyScalingConfigurationsPrivatePoolOptions;
     affinity?: string;
     cpu?: number;
     creationTime?: string;
@@ -5545,6 +5621,7 @@ export declare class DescribeScalingConfigurationsResponseBodyScalingConfigurati
     imageFamily?: string;
     imageId?: string;
     imageName?: string;
+    imageOptionsLoginAsNonRoot?: boolean;
     imageOwnerAlias?: string;
     instanceDescription?: string;
     instanceGeneration?: string;
@@ -5630,6 +5707,19 @@ export declare class DescribeScalingGroupsResponseBodyScalingGroupsLaunchTemplat
         [key: string]: any;
     });
 }
+export declare class DescribeScalingGroupsResponseBodyScalingGroupsLoadBalancerConfigs extends $tea.Model {
+    loadBalancerId?: string;
+    weight?: number;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class DescribeScalingGroupsResponseBodyScalingGroupsServerGroups extends $tea.Model {
     port?: number;
     serverGroupId?: string;
@@ -5685,6 +5775,7 @@ export declare class DescribeScalingGroupsResponseBodyScalingGroups extends $tea
     DBInstanceIds?: string[];
     defaultCooldown?: number;
     desiredCapacity?: number;
+    enableDesiredCapacity?: boolean;
     groupDeletionProtection?: boolean;
     groupType?: string;
     healthCheckType?: string;
@@ -5694,6 +5785,7 @@ export declare class DescribeScalingGroupsResponseBodyScalingGroups extends $tea
     launchTemplateOverrides?: DescribeScalingGroupsResponseBodyScalingGroupsLaunchTemplateOverrides[];
     launchTemplateVersion?: string;
     lifecycleState?: string;
+    loadBalancerConfigs?: DescribeScalingGroupsResponseBodyScalingGroupsLoadBalancerConfigs[];
     loadBalancerIds?: string[];
     maxInstanceLifetime?: number;
     maxSize?: number;
@@ -5766,6 +5858,19 @@ export declare class DescribeScalingInstancesResponseBodyScalingInstances extend
         [key: string]: any;
     });
 }
+export declare class DescribeScalingRulesResponseBodyScalingRulesAlarmDimensions extends $tea.Model {
+    dimensionKey?: string;
+    dimensionValue?: string;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class DescribeScalingRulesResponseBodyScalingRulesAlarmsDimensions extends $tea.Model {
     dimensionKey?: string;
     dimensionValue?: string;
@@ -5816,6 +5921,7 @@ export declare class DescribeScalingRulesResponseBodyScalingRulesStepAdjustments
 export declare class DescribeScalingRulesResponseBodyScalingRules extends $tea.Model {
     adjustmentType?: string;
     adjustmentValue?: number;
+    alarmDimensions?: DescribeScalingRulesResponseBodyScalingRulesAlarmDimensions[];
     alarms?: DescribeScalingRulesResponseBodyScalingRulesAlarms[];
     cooldown?: number;
     disableScaleIn?: boolean;
@@ -6051,13 +6157,13 @@ export declare class ModifyEciScalingConfigurationRequestContainersLivenessProbe
     });
 }
 export declare class ModifyEciScalingConfigurationRequestContainersLivenessProbe extends $tea.Model {
-    exec: ModifyEciScalingConfigurationRequestContainersLivenessProbeExec;
+    exec?: ModifyEciScalingConfigurationRequestContainersLivenessProbeExec;
     failureThreshold?: number;
-    httpGet: ModifyEciScalingConfigurationRequestContainersLivenessProbeHttpGet;
+    httpGet?: ModifyEciScalingConfigurationRequestContainersLivenessProbeHttpGet;
     initialDelaySeconds?: number;
     periodSeconds?: number;
     successThreshold?: number;
-    tcpSocket: ModifyEciScalingConfigurationRequestContainersLivenessProbeTcpSocket;
+    tcpSocket?: ModifyEciScalingConfigurationRequestContainersLivenessProbeTcpSocket;
     timeoutSeconds?: number;
     static names(): {
         [key: string]: string;
@@ -6108,13 +6214,13 @@ export declare class ModifyEciScalingConfigurationRequestContainersReadinessProb
     });
 }
 export declare class ModifyEciScalingConfigurationRequestContainersReadinessProbe extends $tea.Model {
-    exec: ModifyEciScalingConfigurationRequestContainersReadinessProbeExec;
+    exec?: ModifyEciScalingConfigurationRequestContainersReadinessProbeExec;
     failureThreshold?: number;
-    httpGet: ModifyEciScalingConfigurationRequestContainersReadinessProbeHttpGet;
+    httpGet?: ModifyEciScalingConfigurationRequestContainersReadinessProbeHttpGet;
     initialDelaySeconds?: number;
     periodSeconds?: number;
     successThreshold?: number;
-    tcpSocket: ModifyEciScalingConfigurationRequestContainersReadinessProbeTcpSocket;
+    tcpSocket?: ModifyEciScalingConfigurationRequestContainersReadinessProbeTcpSocket;
     timeoutSeconds?: number;
     static names(): {
         [key: string]: string;
@@ -6139,7 +6245,7 @@ export declare class ModifyEciScalingConfigurationRequestContainersSecurityConte
     });
 }
 export declare class ModifyEciScalingConfigurationRequestContainersSecurityContext extends $tea.Model {
-    capability: ModifyEciScalingConfigurationRequestContainersSecurityContextCapability;
+    capability?: ModifyEciScalingConfigurationRequestContainersSecurityContextCapability;
     readOnlyRootFilesystem?: boolean;
     runAsUser?: number;
     static names(): {
@@ -6165,7 +6271,7 @@ export declare class ModifyEciScalingConfigurationRequestContainersEnvironmentVa
     });
 }
 export declare class ModifyEciScalingConfigurationRequestContainersEnvironmentVars extends $tea.Model {
-    fieldRef: ModifyEciScalingConfigurationRequestContainersEnvironmentVarsFieldRef;
+    fieldRef?: ModifyEciScalingConfigurationRequestContainersEnvironmentVarsFieldRef;
     key?: string;
     value?: string;
     static names(): {
@@ -6208,9 +6314,9 @@ export declare class ModifyEciScalingConfigurationRequestContainersVolumeMounts
     });
 }
 export declare class ModifyEciScalingConfigurationRequestContainers extends $tea.Model {
-    livenessProbe: ModifyEciScalingConfigurationRequestContainersLivenessProbe;
-    readinessProbe: ModifyEciScalingConfigurationRequestContainersReadinessProbe;
-    securityContext: ModifyEciScalingConfigurationRequestContainersSecurityContext;
+    livenessProbe?: ModifyEciScalingConfigurationRequestContainersLivenessProbe;
+    readinessProbe?: ModifyEciScalingConfigurationRequestContainersReadinessProbe;
+    securityContext?: ModifyEciScalingConfigurationRequestContainersSecurityContext;
     args?: string[];
     commands?: string[];
     cpu?: number;
@@ -6289,7 +6395,7 @@ export declare class ModifyEciScalingConfigurationRequestInitContainersSecurityC
     });
 }
 export declare class ModifyEciScalingConfigurationRequestInitContainersSecurityContext extends $tea.Model {
-    capability: ModifyEciScalingConfigurationRequestInitContainersSecurityContextCapability;
+    capability?: ModifyEciScalingConfigurationRequestInitContainersSecurityContextCapability;
     readOnlyRootFilesystem?: boolean;
     runAsUser?: number;
     static names(): {
@@ -6315,7 +6421,7 @@ export declare class ModifyEciScalingConfigurationRequestInitContainersInitConta
     });
 }
 export declare class ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVars extends $tea.Model {
-    fieldRef: ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVarsFieldRef;
+    fieldRef?: ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVarsFieldRef;
     key?: string;
     value?: string;
     static names(): {
@@ -6358,7 +6464,7 @@ export declare class ModifyEciScalingConfigurationRequestInitContainersInitConta
     });
 }
 export declare class ModifyEciScalingConfigurationRequestInitContainers extends $tea.Model {
-    securityContext: ModifyEciScalingConfigurationRequestInitContainersSecurityContext;
+    securityContext?: ModifyEciScalingConfigurationRequestInitContainersSecurityContext;
     args?: string[];
     commands?: string[];
     cpu?: number;
@@ -6423,6 +6529,7 @@ export declare class ModifyEciScalingConfigurationRequestVolumesDiskVolume exten
 }
 export declare class ModifyEciScalingConfigurationRequestVolumesEmptyDirVolume extends $tea.Model {
     medium?: string;
+    sizeLimit?: string;
     static names(): {
         [key: string]: string;
     };
@@ -6489,11 +6596,11 @@ export declare class ModifyEciScalingConfigurationRequestVolumesConfigFileVolume
     });
 }
 export declare class ModifyEciScalingConfigurationRequestVolumes extends $tea.Model {
-    diskVolume: ModifyEciScalingConfigurationRequestVolumesDiskVolume;
-    emptyDirVolume: ModifyEciScalingConfigurationRequestVolumesEmptyDirVolume;
-    flexVolume: ModifyEciScalingConfigurationRequestVolumesFlexVolume;
-    hostPathVolume: ModifyEciScalingConfigurationRequestVolumesHostPathVolume;
-    NFSVolume: ModifyEciScalingConfigurationRequestVolumesNFSVolume;
+    diskVolume?: ModifyEciScalingConfigurationRequestVolumesDiskVolume;
+    emptyDirVolume?: ModifyEciScalingConfigurationRequestVolumesEmptyDirVolume;
+    flexVolume?: ModifyEciScalingConfigurationRequestVolumesFlexVolume;
+    hostPathVolume?: ModifyEciScalingConfigurationRequestVolumesHostPathVolume;
+    NFSVolume?: ModifyEciScalingConfigurationRequestVolumesNFSVolume;
     configFileVolumeConfigFileToPath?: ModifyEciScalingConfigurationRequestVolumesConfigFileVolumeConfigFileToPath[];
     configFileVolumeDefaultMode?: number;
     name?: string;
@@ -6508,6 +6615,18 @@ export declare class ModifyEciScalingConfigurationRequestVolumes extends $tea.Mo
         [key: string]: any;
     });
 }
+export declare class ModifyScalingConfigurationRequestImageOptions extends $tea.Model {
+    loginAsNonRoot?: boolean;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class ModifyScalingConfigurationRequestPrivatePoolOptions extends $tea.Model {
     id?: string;
     matchCriteria?: string;
@@ -6612,6 +6731,18 @@ export declare class ModifyScalingConfigurationRequestSpotPriceLimits extends $t
         [key: string]: any;
     });
 }
+export declare class ModifyScalingConfigurationShrinkRequestImageOptions extends $tea.Model {
+    loginAsNonRoot?: boolean;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class ModifyScalingConfigurationShrinkRequestPrivatePoolOptions extends $tea.Model {
     id?: string;
     matchCriteria?: string;
@@ -6730,6 +6861,19 @@ export declare class ModifyScalingGroupRequestLaunchTemplateOverrides extends $t
         [key: string]: any;
     });
 }
+export declare class ModifyScalingRuleRequestAlarmDimensions extends $tea.Model {
+    dimensionKey?: string;
+    dimensionValue?: string;
+    static names(): {
+        [key: string]: string;
+    };
+    static types(): {
+        [key: string]: any;
+    };
+    constructor(map?: {
+        [key: string]: any;
+    });
+}
 export declare class ModifyScalingRuleRequestStepAdjustments extends $tea.Model {
     metricIntervalLowerBound?: number;
     metricIntervalUpperBound?: number;
@@ -6763,100 +6907,22 @@ export default class Client extends OpenApi {
     getEndpoint(productId: string, regionId: string, endpointRule: string, network: string, suffix: string, endpointMap: {
         [key: string]: string;
     }, endpoint: string): string;
-    /**
-      * Associates one or more Application Load Balancer (ALB) server groups with a scaling group.
-      *
-      * @param request AttachAlbServerGroupsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachAlbServerGroupsResponse
-     */
     attachAlbServerGroupsWithOptions(request: AttachAlbServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<AttachAlbServerGroupsResponse>;
-    /**
-      * Associates one or more Application Load Balancer (ALB) server groups with a scaling group.
-      *
-      * @param request AttachAlbServerGroupsRequest
-      * @return AttachAlbServerGroupsResponse
-     */
     attachAlbServerGroups(request: AttachAlbServerGroupsRequest): Promise<AttachAlbServerGroupsResponse>;
-    /**
-      * Associates one or more ApsaraDB RDS instances with a scaling group.
-      *
-      * @param request AttachDBInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachDBInstancesResponse
-     */
     attachDBInstancesWithOptions(request: AttachDBInstancesRequest, runtime: $Util.RuntimeOptions): Promise<AttachDBInstancesResponse>;
-    /**
-      * Associates one or more ApsaraDB RDS instances with a scaling group.
-      *
-      * @param request AttachDBInstancesRequest
-      * @return AttachDBInstancesResponse
-     */
     attachDBInstances(request: AttachDBInstancesRequest): Promise<AttachDBInstancesResponse>;
-    /**
-      * Manually adds Elastic Compute Service (ECS) instances or elastic container instances to a scaling group.
-      *
-      * @param request AttachInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachInstancesResponse
-     */
     attachInstancesWithOptions(request: AttachInstancesRequest, runtime: $Util.RuntimeOptions): Promise<AttachInstancesResponse>;
-    /**
-      * Manually adds Elastic Compute Service (ECS) instances or elastic container instances to a scaling group.
-      *
-      * @param request AttachInstancesRequest
-      * @return AttachInstancesResponse
-     */
     attachInstances(request: AttachInstancesRequest): Promise<AttachInstancesResponse>;
-    /**
-      * Attaches one or more Classic Load Balancer (CLB) instances to a scaling group.
-      *
-      * @param request AttachLoadBalancersRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachLoadBalancersResponse
-     */
     attachLoadBalancersWithOptions(request: AttachLoadBalancersRequest, runtime: $Util.RuntimeOptions): Promise<AttachLoadBalancersResponse>;
-    /**
-      * Attaches one or more Classic Load Balancer (CLB) instances to a scaling group.
-      *
-      * @param request AttachLoadBalancersRequest
-      * @return AttachLoadBalancersResponse
-     */
     attachLoadBalancers(request: AttachLoadBalancersRequest): Promise<AttachLoadBalancersResponse>;
     attachServerGroupsWithOptions(request: AttachServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<AttachServerGroupsResponse>;
     attachServerGroups(request: AttachServerGroupsRequest): Promise<AttachServerGroupsResponse>;
-    /**
-      * Attaches one or more vServer groups of a Classic Load Balancer (CLB) instance to a scaling group.
-      *
-      * @param request AttachVServerGroupsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return AttachVServerGroupsResponse
-     */
     attachVServerGroupsWithOptions(request: AttachVServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<AttachVServerGroupsResponse>;
-    /**
-      * Attaches one or more vServer groups of a Classic Load Balancer (CLB) instance to a scaling group.
-      *
-      * @param request AttachVServerGroupsRequest
-      * @return AttachVServerGroupsResponse
-     */
     attachVServerGroups(request: AttachVServerGroupsRequest): Promise<AttachVServerGroupsResponse>;
-    /**
-      * A resource is an entity of cloud services that you create on Alibaba Cloud. For example, a scaling group is a resource. A resource group is a collection of infrastructure for projects, environments, or stacks. In a resource group, you can manage resources, monitor resources, and perform operations in a centralized manner. This way, you do not need to view and check your Alibaba Cloud resources in each Alibaba Cloud service.
-      *
-      * @param request ChangeResourceGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ChangeResourceGroupResponse
-     */
     changeResourceGroupWithOptions(request: ChangeResourceGroupRequest, runtime: $Util.RuntimeOptions): Promise<ChangeResourceGroupResponse>;
-    /**
-      * A resource is an entity of cloud services that you create on Alibaba Cloud. For example, a scaling group is a resource. A resource group is a collection of infrastructure for projects, environments, or stacks. In a resource group, you can manage resources, monitor resources, and perform operations in a centralized manner. This way, you do not need to view and check your Alibaba Cloud resources in each Alibaba Cloud service.
-      *
-      * @param request ChangeResourceGroupRequest
-      * @return ChangeResourceGroupResponse
-     */
     changeResourceGroup(request: ChangeResourceGroupRequest): Promise<ChangeResourceGroupResponse>;
     /**
-      * When you call this operation to end a lifecycle hook ahead of schedule, you can use the LifecycleActionResult parameter to specify the action that you want Auto Scaling to perform after the lifecycle hook ends. You can set the LifecycleActionResult parameter to CONTINUE or ABANDON.
+      * If you set the LifecycleActionResult parameter for a lifecycle hook of a scaling group to CONTINUE in the operation, Auto Scaling continues to complete the scaling activity in the scaling group after the lifecycle hook times out. If you set the LifecycleActionResult parameter to ABANDON, Auto Scaling stops the scaling activity in the scaling group after the lifecycle hook times out.
       *
       * @param request CompleteLifecycleActionRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -6864,34 +6930,13 @@ export default class Client extends OpenApi {
      */
     completeLifecycleActionWithOptions(request: CompleteLifecycleActionRequest, runtime: $Util.RuntimeOptions): Promise<CompleteLifecycleActionResponse>;
     /**
-      * When you call this operation to end a lifecycle hook ahead of schedule, you can use the LifecycleActionResult parameter to specify the action that you want Auto Scaling to perform after the lifecycle hook ends. You can set the LifecycleActionResult parameter to CONTINUE or ABANDON.
+      * If you set the LifecycleActionResult parameter for a lifecycle hook of a scaling group to CONTINUE in the operation, Auto Scaling continues to complete the scaling activity in the scaling group after the lifecycle hook times out. If you set the LifecycleActionResult parameter to ABANDON, Auto Scaling stops the scaling activity in the scaling group after the lifecycle hook times out.
       *
       * @param request CompleteLifecycleActionRequest
       * @return CompleteLifecycleActionResponse
      */
     completeLifecycleAction(request: CompleteLifecycleActionRequest): Promise<CompleteLifecycleActionResponse>;
-    /**
-      * *   If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using custom metrics. For more information, see [Custom monitoring event-triggered tasks](~~74861~~).
-      * *   When you create an event-triggered task, you must specify the MetricName, DimensionKey, and DimensionValue parameters to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances or elastic container instances in a scaling group within an Alibaba Cloud account.
-      *     *   If you set the MetricType parameter to custom, the valid values are your custom metrics.
-      *     *   For information about the supported metrics when you set the MetricType parameter to system, see [Event-triggered task for system monitoring](~~74854~~).
-      * > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see the `DimensionKey` and `DimensionValue` parameters in the "Request parameters" section of this topic.
-      *
-      * @param request CreateAlarmRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return CreateAlarmResponse
-     */
     createAlarmWithOptions(request: CreateAlarmRequest, runtime: $Util.RuntimeOptions): Promise<CreateAlarmResponse>;
-    /**
-      * *   If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using custom metrics. For more information, see [Custom monitoring event-triggered tasks](~~74861~~).
-      * *   When you create an event-triggered task, you must specify the MetricName, DimensionKey, and DimensionValue parameters to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances or elastic container instances in a scaling group within an Alibaba Cloud account.
-      *     *   If you set the MetricType parameter to custom, the valid values are your custom metrics.
-      *     *   For information about the supported metrics when you set the MetricType parameter to system, see [Event-triggered task for system monitoring](~~74854~~).
-      * > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see the `DimensionKey` and `DimensionValue` parameters in the "Request parameters" section of this topic.
-      *
-      * @param request CreateAlarmRequest
-      * @return CreateAlarmResponse
-     */
     createAlarm(request: CreateAlarmRequest): Promise<CreateAlarmResponse>;
     /**
       * A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
@@ -6911,10 +6956,10 @@ export default class Client extends OpenApi {
      */
     createEciScalingConfiguration(request: CreateEciScalingConfigurationRequest): Promise<CreateEciScalingConfigurationResponse>;
     /**
-      * 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](~~120810~~).
-      * > 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.
+      * You can create up to six lifecycle hooks for each scaling group. Elastic Compute Service (ECS) instances are not immediately added to or removed from scaling groups that have effective lifecycle hooks during scaling activities. The ECS instances are added to or removed from the scaling groups only after the lifecycle hooks time out. The period of time before the lifecycle hooks time out is specified by the HeartbeatTimeout parameter. Before lifecycle hooks time out, you can initialize the configurations of ECS instances and query data on the ECS instances.
+      * If lifecycle hooks take effect for scale-out activities, the private IP addresses of ECS instances are added to the IP address whitelists of the associated ApsaraDB RDS instances and the ECS instances are added to the backend server groups of the associated Server Load Balancer (SLB) instances only after the lifecycle hooks time out. If lifecycle hooks take effect for scale-in activities, the private IP addresses of ECS instances are removed from the IP address whitelists of the disassociated ApsaraDB RDS instances and the ECS instances are removed from the backend server groups of the disassociated SLB instances only after the lifecycle hooks time out.
+      * You can configure a notification method for a lifecycle hook. When the lifecycle hook takes effect, a notification can be sent by using a Message Service (MNS) topic, an MNS queue, or an Operation Orchestration Service (OOS) template. If you want to configure an OOS template, you must create a RAM role for OOS. For more information, see [Grant RAM permissions to OOS](~~120810~~).
+      * > If your scaling group contains ECS instances and you configure an OOS template to add the private IP addresses of the ECS instances to or remove the private IP addresses of the ECS instances from the IP address whitelists of cloud databases other than ApsaraDB RDS databases, you must manually add the private IP addresses of the ECS instances to the IP address whitelists of the cloud databases.
       *
       * @param request CreateLifecycleHookRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -6922,38 +6967,25 @@ export default class Client extends OpenApi {
      */
     createLifecycleHookWithOptions(request: CreateLifecycleHookRequest, runtime: $Util.RuntimeOptions): Promise<CreateLifecycleHookResponse>;
     /**
-      * 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](~~120810~~).
-      * > 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.
+      * You can create up to six lifecycle hooks for each scaling group. Elastic Compute Service (ECS) instances are not immediately added to or removed from scaling groups that have effective lifecycle hooks during scaling activities. The ECS instances are added to or removed from the scaling groups only after the lifecycle hooks time out. The period of time before the lifecycle hooks time out is specified by the HeartbeatTimeout parameter. Before lifecycle hooks time out, you can initialize the configurations of ECS instances and query data on the ECS instances.
+      * If lifecycle hooks take effect for scale-out activities, the private IP addresses of ECS instances are added to the IP address whitelists of the associated ApsaraDB RDS instances and the ECS instances are added to the backend server groups of the associated Server Load Balancer (SLB) instances only after the lifecycle hooks time out. If lifecycle hooks take effect for scale-in activities, the private IP addresses of ECS instances are removed from the IP address whitelists of the disassociated ApsaraDB RDS instances and the ECS instances are removed from the backend server groups of the disassociated SLB instances only after the lifecycle hooks time out.
+      * You can configure a notification method for a lifecycle hook. When the lifecycle hook takes effect, a notification can be sent by using a Message Service (MNS) topic, an MNS queue, or an Operation Orchestration Service (OOS) template. If you want to configure an OOS template, you must create a RAM role for OOS. For more information, see [Grant RAM permissions to OOS](~~120810~~).
+      * > If your scaling group contains ECS instances and you configure an OOS template to add the private IP addresses of the ECS instances to or remove the private IP addresses of the ECS instances from the IP address whitelists of cloud databases other than ApsaraDB RDS databases, you must manually add the private IP addresses of the ECS instances to the IP address whitelists of the cloud databases.
       *
       * @param request CreateLifecycleHookRequest
       * @return CreateLifecycleHookResponse
      */
     createLifecycleHook(request: CreateLifecycleHookRequest): Promise<CreateLifecycleHookResponse>;
-    /**
-      * Creates a notification.
-      *
-      * @param request CreateNotificationConfigurationRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return CreateNotificationConfigurationResponse
-     */
     createNotificationConfigurationWithOptions(request: CreateNotificationConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<CreateNotificationConfigurationResponse>;
-    /**
-      * Creates a notification.
-      *
-      * @param request CreateNotificationConfigurationRequest
-      * @return CreateNotificationConfigurationResponse
-     */
     createNotificationConfiguration(request: CreateNotificationConfigurationRequest): Promise<CreateNotificationConfigurationResponse>;
     /**
-      * Auto Scaling automatically scales out Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be configured in the following modes:
-      * *   InstancePatternInfo.N: intelligent configuration mode. In this mode, you need to only specify the number of vCPUs, memory size, instance family, and maximum price. The system selects an instance type that is provided at the lowest price based on your configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode helps reduce the failures of scale-out activities caused by insufficient inventory of instance types.
+      * 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.N: In this mode, you must specify multiple instance types.
-      * *   InstanceTypeOverride.N: In this mode, you must specify multiple instance types and specify weights for the instance types.
-      * *   Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines a set of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling preferentially creates ECS instances of the instance type that is provided at the lowest price. This mode is available only if the Scaling Policy parameter is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
-      * > You cannot use InstanceType, InstanceTypes, InstanceTypeOverride, and Cpu and Memory at the same time. You can use InstanceType and InstancePatternInfos or use InstanceTypes and InstancePatternInfos at the same time. If you use InstanceType and InstancePatternInfos or use InstanceTypes and InstancePatternInfos at the same time, Auto Scaling preferentially uses the instance types that are specified by InstanceType or InstanceTypes for scale-out activities. 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-out activities.
+      * *   InstanceTypes: In this mode, you can specify more than one instance type.
+      * *   InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
+      * *   Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines the range of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling creates ECS instances 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
@@ -6961,13 +6993,13 @@ export default class Client extends OpenApi {
      */
     createScalingConfigurationWithOptions(tmpReq: CreateScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<CreateScalingConfigurationResponse>;
     /**
-      * Auto Scaling automatically scales out Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be configured in the following modes:
-      * *   InstancePatternInfo.N: intelligent configuration mode. In this mode, you need to only specify the number of vCPUs, memory size, instance family, and maximum price. The system selects an instance type that is provided at the lowest price based on your configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode helps reduce the failures of scale-out activities caused by insufficient inventory of instance types.
+      * 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.N: In this mode, you must specify multiple instance types.
-      * *   InstanceTypeOverride.N: In this mode, you must specify multiple instance types and specify weights for the instance types.
-      * *   Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines a set of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling preferentially creates ECS instances of the instance type that is provided at the lowest price. This mode is available only if the Scaling Policy parameter is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
-      * > You cannot use InstanceType, InstanceTypes, InstanceTypeOverride, and Cpu and Memory at the same time. You can use InstanceType and InstancePatternInfos or use InstanceTypes and InstancePatternInfos at the same time. If you use InstanceType and InstancePatternInfos or use InstanceTypes and InstancePatternInfos at the same time, Auto Scaling preferentially uses the instance types that are specified by InstanceType or InstanceTypes for scale-out activities. 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-out activities.
+      * *   InstanceTypes: In this mode, you can specify more than one instance type.
+      * *   InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
+      * *   Cpu and Memory: In this mode, you must specify the number of vCPUs and the memory size. Auto Scaling determines the range of available instance types based on factors such as I/O optimization requirements and zones. Then, Auto Scaling creates ECS instances 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
@@ -6976,26 +7008,26 @@ export default class Client extends OpenApi {
     /**
       * A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
       * You can create only a limited number of scaling groups in a region. Go to Quota Center to check the quota of the scaling groups.
-      * A scaling group does not immediately take effect after you create it. You must call the EnableScalingGroup operation to enable a scaling group. After you enable a scaling group, Auto Scaling can execute scaling rules to trigger scaling activities in the scaling group.
-      * The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances that you want to associate with a scaling group must reside in the same region as the scaling group. CLB instances are formerly known as Server Load Balancer (SLB) instances. For more information, see the "Regions and zones" topic in ECS Product Introduction.
-      * If you associate a CLB instance with a scaling group, Auto Scaling automatically adds ECS instances in the scaling group to the backend server group of the CLB instance. You can specify a server group to which ECS instances can be added. You can add ECS instances to the following types of server groups:
+      * A scaling group does not immediately take effect after you create the scaling group. You must call the EnableScalingGroup operation to enable the scaling group. After you enable the scaling group, Auto Scaling can execute scaling rules to trigger scaling activities in the scaling group.
+      * The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances that you want to associate with a scaling group must reside in the same region as the scaling group. CLB instances are formerly known as Server Load Balancer (SLB) instances. For more information, see the "Regions and zones" topic.
+      * If you associate a CLB instance when you create a scaling group, Auto Scaling automatically adds ECS instances in the scaling group to the backend server group of the associated CLB instance. You can specify a server group to which ECS instances can be added. You can add ECS instances to the following types of server groups:
       * *   Default server group: a group of ECS instances that are used to receive requests. If you do not specify a vServer group or a primary/secondary server group for a listener, requests are forwarded to the ECS instances in the default server group.
       * *   vServer group: If you want to forward requests to backend servers that are not in the default server group or configure domain name-based or URL-based forwarding rules, you can use vServer groups.
       * > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
       * The default weight of an ECS instance that is added as a backend server of a CLB instance is 50. The CLB instance that you want to associate with your scaling group must meet the following requirements:
       * *   The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
       * *   The health check feature must be enabled on all listener ports that are configured for the CLB instance. Otherwise, the scaling group fails to be created.
-      * If you associate an Application Load Balancer (ALB) server group with a scaling group, Auto Scaling automatically adds ECS instances in the scaling group to the ALB server group to process requests distributed by the ALB instance to which the ALB server group belongs. You can specify multiple ALB server groups. The server groups must reside in the same virtual private cloud (VPC) as the scaling group. For more information, see the "AttachAlbServerGroups" topic.
+      * If you associate an Application Load Balancer (ALB) server group with a scaling group, Auto Scaling automatically adds ECS instances that are in the scaling group to the ALB server group to process requests distributed by the ALB instance to which the ALB server group belongs. You can specify multiple ALB server groups. The server groups must reside in the same virtual private cloud (VPC) as the scaling group. For more information, see the "AttachAlbServerGroups" topic.
       * If you associate an ApsaraDB RDS instance with a scaling group, Auto Scaling automatically adds the private IP addresses of the ECS instances in the scaling group to the IP address whitelist of the ApsaraDB RDS instance. The ApsaraDB RDS instance that you want to associate with your scaling group must meet the following requirements:
       * *   The ApsaraDB RDS instance must be in the Running state. You can call the DescribeDBInstances operation to query the state of the ApsaraDB RDS instance.
-      * *   The number of IP addresses in the IP address whitelist of the ApsaraDB RDS instance cannot exceed the upper limit. For more information, see the "Configure whitelists" topic in ApsaraDB RDS User Guide.
+      * *   The number of IP addresses in the IP address whitelist of the ApsaraDB RDS instance cannot exceed the upper limit. For more information, see the "Configure whitelists" topic.
       * If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
       * *   You can use the OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, and SpotInstancePools parameters to specify the instance allocation method based on the cost optimization policy. This instance allocation method is prioritized during scaling.
       * *   If you do not specify the OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, or SpotInstancePools parameter, the instance types that are provided at the lowest price are used to create instances based on the cost optimization policy.
-      * If you set the `Tags.Propagate` parameter for the scaling group to true, the following rules apply:
+      * If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules 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 that uses the scaling configuration are the same, the tag value that you specify in the scaling configuration is preferentially used.
+      * *   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
@@ -7005,33 +7037,44 @@ export default class Client extends OpenApi {
     /**
       * A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
       * You can create only a limited number of scaling groups in a region. Go to Quota Center to check the quota of the scaling groups.
-      * A scaling group does not immediately take effect after you create it. You must call the EnableScalingGroup operation to enable a scaling group. After you enable a scaling group, Auto Scaling can execute scaling rules to trigger scaling activities in the scaling group.
-      * The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances that you want to associate with a scaling group must reside in the same region as the scaling group. CLB instances are formerly known as Server Load Balancer (SLB) instances. For more information, see the "Regions and zones" topic in ECS Product Introduction.
-      * If you associate a CLB instance with a scaling group, Auto Scaling automatically adds ECS instances in the scaling group to the backend server group of the CLB instance. You can specify a server group to which ECS instances can be added. You can add ECS instances to the following types of server groups:
+      * A scaling group does not immediately take effect after you create the scaling group. You must call the EnableScalingGroup operation to enable the scaling group. After you enable the scaling group, Auto Scaling can execute scaling rules to trigger scaling activities in the scaling group.
+      * The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances that you want to associate with a scaling group must reside in the same region as the scaling group. CLB instances are formerly known as Server Load Balancer (SLB) instances. For more information, see the "Regions and zones" topic.
+      * If you associate a CLB instance when you create a scaling group, Auto Scaling automatically adds ECS instances in the scaling group to the backend server group of the associated CLB instance. You can specify a server group to which ECS instances can be added. You can add ECS instances to the following types of server groups:
       * *   Default server group: a group of ECS instances that are used to receive requests. If you do not specify a vServer group or a primary/secondary server group for a listener, requests are forwarded to the ECS instances in the default server group.
       * *   vServer group: If you want to forward requests to backend servers that are not in the default server group or configure domain name-based or URL-based forwarding rules, you can use vServer groups.
       * > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
       * The default weight of an ECS instance that is added as a backend server of a CLB instance is 50. The CLB instance that you want to associate with your scaling group must meet the following requirements:
       * *   The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
       * *   The health check feature must be enabled on all listener ports that are configured for the CLB instance. Otherwise, the scaling group fails to be created.
-      * If you associate an Application Load Balancer (ALB) server group with a scaling group, Auto Scaling automatically adds ECS instances in the scaling group to the ALB server group to process requests distributed by the ALB instance to which the ALB server group belongs. You can specify multiple ALB server groups. The server groups must reside in the same virtual private cloud (VPC) as the scaling group. For more information, see the "AttachAlbServerGroups" topic.
+      * If you associate an Application Load Balancer (ALB) server group with a scaling group, Auto Scaling automatically adds ECS instances that are in the scaling group to the ALB server group to process requests distributed by the ALB instance to which the ALB server group belongs. You can specify multiple ALB server groups. The server groups must reside in the same virtual private cloud (VPC) as the scaling group. For more information, see the "AttachAlbServerGroups" topic.
       * If you associate an ApsaraDB RDS instance with a scaling group, Auto Scaling automatically adds the private IP addresses of the ECS instances in the scaling group to the IP address whitelist of the ApsaraDB RDS instance. The ApsaraDB RDS instance that you want to associate with your scaling group must meet the following requirements:
       * *   The ApsaraDB RDS instance must be in the Running state. You can call the DescribeDBInstances operation to query the state of the ApsaraDB RDS instance.
-      * *   The number of IP addresses in the IP address whitelist of the ApsaraDB RDS instance cannot exceed the upper limit. For more information, see the "Configure whitelists" topic in ApsaraDB RDS User Guide.
+      * *   The number of IP addresses in the IP address whitelist of the ApsaraDB RDS instance cannot exceed the upper limit. For more information, see the "Configure whitelists" topic.
       * If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
       * *   You can use the OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, and SpotInstancePools parameters to specify the instance allocation method based on the cost optimization policy. This instance allocation method is prioritized during scaling.
       * *   If you do not specify the OnDemandBaseCapacity, OnDemandPercentageAboveBaseCapacity, or SpotInstancePools parameter, the instance types that are provided at the lowest price are used to create instances based on the cost optimization policy.
-      * If you set the `Tags.Propagate` parameter for the scaling group to true, the following rules apply:
+      * If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules 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 that uses the scaling configuration are the same, the tag value that you specify in the scaling configuration is preferentially used.
+      * *   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
      */
     createScalingGroup(request: CreateScalingGroupRequest): Promise<CreateScalingGroupResponse>;
     /**
-      * Creates a scaling rule.
+      * A scaling rule defines a specific scaling activity, such as adding or removing N instances. If the number of Elastic Compute Service (ECS) instances in a scaling group is less than the minimum number allowed or greater than the maximum number allowed after a scaling rule is executed, Auto Scaling calculates the number of ECS instances that need to be added or removed. This ensures that the number of ECS instances can be maintained within the valid range after the scaling rule is executed. Examples:
+      * *   If your scaling group contains two ECS instances and allows up to three ECS instances, only one ECS instance is added to your scaling group after you execute a scale-out rule in which three ECS instances are specified.
+      * *   If your scaling group contains three ECS instances and requires at least two ECS instances, only one ECS instance is removed from your scaling group after you execute a scale-in rule in which five ECS instances are specified.
+      * Before you call this operation, take note of the following items:
+      * *   If you set AdjustmentType to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of AdjustmentValue must be greater than or equal to 0.
+      * *   If you set AdjustmentType to QuantityChangeInCapacity, a positive value of AdjustmentValue specifies the number of ECS instances that are added to the scaling group, and a negative value of AdjustmentValue specifies the number of ECS instances that are removed from the scaling group.
+      * *   If you set AdjustmentType to PercentChangeInCapacity, Auto Scaling uses the following formula to calculate a value, and then rounds the value to the nearest integer to obtain the number of ECS instances that need to be scaled: Value of TotalCapacity × Value of AdjustmentValue/100.
+      * *   If you specify a cooldown period for the scaling rule, the specified cooldown period takes effect after the rule is executed. Otherwise, the value of DefaultCooldown of the scaling group takes effect.
+      * *   You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
+      * *   The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
+      *     *   ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule that you want to execute.
+      *     *   CreateScheduledTask: You can call this operation to create a scheduled task. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule that you want to associate with the scheduled task.
       *
       * @param request CreateScalingRuleRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7039,96 +7082,38 @@ export default class Client extends OpenApi {
      */
     createScalingRuleWithOptions(request: CreateScalingRuleRequest, runtime: $Util.RuntimeOptions): Promise<CreateScalingRuleResponse>;
     /**
-      * Creates a scaling rule.
+      * A scaling rule defines a specific scaling activity, such as adding or removing N instances. If the number of Elastic Compute Service (ECS) instances in a scaling group is less than the minimum number allowed or greater than the maximum number allowed after a scaling rule is executed, Auto Scaling calculates the number of ECS instances that need to be added or removed. This ensures that the number of ECS instances can be maintained within the valid range after the scaling rule is executed. Examples:
+      * *   If your scaling group contains two ECS instances and allows up to three ECS instances, only one ECS instance is added to your scaling group after you execute a scale-out rule in which three ECS instances are specified.
+      * *   If your scaling group contains three ECS instances and requires at least two ECS instances, only one ECS instance is removed from your scaling group after you execute a scale-in rule in which five ECS instances are specified.
+      * Before you call this operation, take note of the following items:
+      * *   If you set AdjustmentType to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of AdjustmentValue must be greater than or equal to 0.
+      * *   If you set AdjustmentType to QuantityChangeInCapacity, a positive value of AdjustmentValue specifies the number of ECS instances that are added to the scaling group, and a negative value of AdjustmentValue specifies the number of ECS instances that are removed from the scaling group.
+      * *   If you set AdjustmentType to PercentChangeInCapacity, Auto Scaling uses the following formula to calculate a value, and then rounds the value to the nearest integer to obtain the number of ECS instances that need to be scaled: Value of TotalCapacity × Value of AdjustmentValue/100.
+      * *   If you specify a cooldown period for the scaling rule, the specified cooldown period takes effect after the rule is executed. Otherwise, the value of DefaultCooldown of the scaling group takes effect.
+      * *   You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
+      * *   The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
+      *     *   ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule that you want to execute.
+      *     *   CreateScheduledTask: You can call this operation to create a scheduled task. In this operation, you can set ScalingRuleAri to the unique identifier of the scaling rule that you want to associate with the scheduled task.
       *
       * @param request CreateScalingRuleRequest
       * @return CreateScalingRuleResponse
      */
     createScalingRule(request: CreateScalingRuleRequest): Promise<CreateScalingRuleResponse>;
-    /**
-      * Creates a scheduled task.
-      *
-      * @param request CreateScheduledTaskRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return CreateScheduledTaskResponse
-     */
     createScheduledTaskWithOptions(request: CreateScheduledTaskRequest, runtime: $Util.RuntimeOptions): Promise<CreateScheduledTaskResponse>;
-    /**
-      * Creates a scheduled task.
-      *
-      * @param request CreateScheduledTaskRequest
-      * @return CreateScheduledTaskResponse
-     */
     createScheduledTask(request: CreateScheduledTaskRequest): Promise<CreateScheduledTaskResponse>;
     deactivateScalingConfigurationWithOptions(request: DeactivateScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeactivateScalingConfigurationResponse>;
     deactivateScalingConfiguration(request: DeactivateScalingConfigurationRequest): Promise<DeactivateScalingConfigurationResponse>;
     deleteAlarmWithOptions(request: DeleteAlarmRequest, runtime: $Util.RuntimeOptions): Promise<DeleteAlarmResponse>;
     deleteAlarm(request: DeleteAlarmRequest): Promise<DeleteAlarmResponse>;
-    /**
-      * Deletes a scaling configuration that is used to create elastic container instances.
-      *
-      * @param request DeleteEciScalingConfigurationRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DeleteEciScalingConfigurationResponse
-     */
     deleteEciScalingConfigurationWithOptions(request: DeleteEciScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeleteEciScalingConfigurationResponse>;
-    /**
-      * Deletes a scaling configuration that is used to create elastic container instances.
-      *
-      * @param request DeleteEciScalingConfigurationRequest
-      * @return DeleteEciScalingConfigurationResponse
-     */
     deleteEciScalingConfiguration(request: DeleteEciScalingConfigurationRequest): Promise<DeleteEciScalingConfigurationResponse>;
-    /**
-      * If you delete a lifecycle hook that is in effect in a scaling group, instances exit the Pending state in advance. You can use one of the following methods to specify the lifecycle hooks that you want to delete:
-      * *   Specify the scaling group ID of the lifecycle hook that you want to delete by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
-      * *   Specify the lifecycle hook ID by using the LifecycleHookId parameter. In this case, the ScalingGroupId parameter and the LifecycleHookName parameter are ignored.
-      *
-      * @param request DeleteLifecycleHookRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DeleteLifecycleHookResponse
-     */
     deleteLifecycleHookWithOptions(request: DeleteLifecycleHookRequest, runtime: $Util.RuntimeOptions): Promise<DeleteLifecycleHookResponse>;
-    /**
-      * If you delete a lifecycle hook that is in effect in a scaling group, instances exit the Pending state in advance. You can use one of the following methods to specify the lifecycle hooks that you want to delete:
-      * *   Specify the scaling group ID of the lifecycle hook that you want to delete by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
-      * *   Specify the lifecycle hook ID by using the LifecycleHookId parameter. In this case, the ScalingGroupId parameter and the LifecycleHookName parameter are ignored.
-      *
-      * @param request DeleteLifecycleHookRequest
-      * @return DeleteLifecycleHookResponse
-     */
     deleteLifecycleHook(request: DeleteLifecycleHookRequest): Promise<DeleteLifecycleHookResponse>;
     deleteNotificationConfigurationWithOptions(request: DeleteNotificationConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeleteNotificationConfigurationResponse>;
     deleteNotificationConfiguration(request: DeleteNotificationConfigurationRequest): Promise<DeleteNotificationConfigurationResponse>;
-    /**
-      * Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
-      *
-      * @param request DeleteScalingConfigurationRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DeleteScalingConfigurationResponse
-     */
     deleteScalingConfigurationWithOptions(request: DeleteScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<DeleteScalingConfigurationResponse>;
-    /**
-      * Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
-      *
-      * @param request DeleteScalingConfigurationRequest
-      * @return DeleteScalingConfigurationResponse
-     */
     deleteScalingConfiguration(request: DeleteScalingConfigurationRequest): Promise<DeleteScalingConfigurationResponse>;
-    /**
-      * Deletes a scaling group.
-      *
-      * @param request DeleteScalingGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DeleteScalingGroupResponse
-     */
     deleteScalingGroupWithOptions(request: DeleteScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<DeleteScalingGroupResponse>;
-    /**
-      * Deletes a scaling group.
-      *
-      * @param request DeleteScalingGroupRequest
-      * @return DeleteScalingGroupResponse
-     */
     deleteScalingGroup(request: DeleteScalingGroupRequest): Promise<DeleteScalingGroupResponse>;
     deleteScalingRuleWithOptions(request: DeleteScalingRuleRequest, runtime: $Util.RuntimeOptions): Promise<DeleteScalingRuleResponse>;
     deleteScalingRule(request: DeleteScalingRuleRequest): Promise<DeleteScalingRuleResponse>;
@@ -7138,41 +7123,9 @@ export default class Client extends OpenApi {
     describeAlarms(request: DescribeAlarmsRequest): Promise<DescribeAlarmsResponse>;
     describeEciScalingConfigurationsWithOptions(request: DescribeEciScalingConfigurationsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeEciScalingConfigurationsResponse>;
     describeEciScalingConfigurations(request: DescribeEciScalingConfigurationsRequest): Promise<DescribeEciScalingConfigurationsResponse>;
-    /**
-      * Queries lifecycle actions.
-      *
-      * @param request DescribeLifecycleActionsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeLifecycleActionsResponse
-     */
     describeLifecycleActionsWithOptions(request: DescribeLifecycleActionsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeLifecycleActionsResponse>;
-    /**
-      * Queries lifecycle actions.
-      *
-      * @param request DescribeLifecycleActionsRequest
-      * @return DescribeLifecycleActionsResponse
-     */
     describeLifecycleActions(request: DescribeLifecycleActionsRequest): Promise<DescribeLifecycleActionsResponse>;
-    /**
-      * You can use one of the following methods to query lifecycle hooks:
-      * *   Specify a list of lifecycle hook IDs by using the LifecycleHookIds parameter. In this case, you do not need to specify the ScalingGroupId and LifecycleHookName parameters.
-      * *   Specify the scaling group ID by using the ScalingGroupId parameter.
-      * *   Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter at the same time.
-      *
-      * @param request DescribeLifecycleHooksRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeLifecycleHooksResponse
-     */
     describeLifecycleHooksWithOptions(request: DescribeLifecycleHooksRequest, runtime: $Util.RuntimeOptions): Promise<DescribeLifecycleHooksResponse>;
-    /**
-      * You can use one of the following methods to query lifecycle hooks:
-      * *   Specify a list of lifecycle hook IDs by using the LifecycleHookIds parameter. In this case, you do not need to specify the ScalingGroupId and LifecycleHookName parameters.
-      * *   Specify the scaling group ID by using the ScalingGroupId parameter.
-      * *   Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter at the same time.
-      *
-      * @param request DescribeLifecycleHooksRequest
-      * @return DescribeLifecycleHooksResponse
-     */
     describeLifecycleHooks(request: DescribeLifecycleHooksRequest): Promise<DescribeLifecycleHooksResponse>;
     describeLimitationWithOptions(request: DescribeLimitationRequest, runtime: $Util.RuntimeOptions): Promise<DescribeLimitationResponse>;
     describeLimitation(request: DescribeLimitationRequest): Promise<DescribeLimitationResponse>;
@@ -7207,23 +7160,10 @@ export default class Client extends OpenApi {
     describeScalingConfigurations(request: DescribeScalingConfigurationsRequest): Promise<DescribeScalingConfigurationsResponse>;
     describeScalingGroupsWithOptions(request: DescribeScalingGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DescribeScalingGroupsResponse>;
     describeScalingGroups(request: DescribeScalingGroupsRequest): Promise<DescribeScalingGroupsResponse>;
-    /**
-      * You can query ECS instances by scaling group ID, scaling configuration ID, health status, lifecycle status, and instance creation method.
-      *
-      * @param request DescribeScalingInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeScalingInstancesResponse
-     */
     describeScalingInstancesWithOptions(request: DescribeScalingInstancesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeScalingInstancesResponse>;
-    /**
-      * You can query ECS instances by scaling group ID, scaling configuration ID, health status, lifecycle status, and instance creation method.
-      *
-      * @param request DescribeScalingInstancesRequest
-      * @return DescribeScalingInstancesResponse
-     */
     describeScalingInstances(request: DescribeScalingInstancesRequest): Promise<DescribeScalingInstancesResponse>;
     /**
-      * Queries all scaling rules in a scaling group.
+      * You can specify a scaling group ID to query the information about all scaling rules in a scaling group. You can also specify the scaling rule ID, name, unique identifier, or type in the request parameters as filter conditions.
       *
       * @param request DescribeScalingRulesRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7231,90 +7171,38 @@ export default class Client extends OpenApi {
      */
     describeScalingRulesWithOptions(request: DescribeScalingRulesRequest, runtime: $Util.RuntimeOptions): Promise<DescribeScalingRulesResponse>;
     /**
-      * Queries all scaling rules in a scaling group.
+      * You can specify a scaling group ID to query the information about all scaling rules in a scaling group. You can also specify the scaling rule ID, name, unique identifier, or type in the request parameters as filter conditions.
       *
       * @param request DescribeScalingRulesRequest
       * @return DescribeScalingRulesResponse
      */
     describeScalingRules(request: DescribeScalingRulesRequest): Promise<DescribeScalingRulesResponse>;
-    /**
-      * You can query scheduled tasks by scaling rule, task ID, or task name.
-      *
-      * @param request DescribeScheduledTasksRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DescribeScheduledTasksResponse
-     */
     describeScheduledTasksWithOptions(request: DescribeScheduledTasksRequest, runtime: $Util.RuntimeOptions): Promise<DescribeScheduledTasksResponse>;
-    /**
-      * You can query scheduled tasks by scaling rule, task ID, or task name.
-      *
-      * @param request DescribeScheduledTasksRequest
-      * @return DescribeScheduledTasksResponse
-     */
     describeScheduledTasks(request: DescribeScheduledTasksRequest): Promise<DescribeScheduledTasksResponse>;
     detachAlbServerGroupsWithOptions(request: DetachAlbServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DetachAlbServerGroupsResponse>;
     detachAlbServerGroups(request: DetachAlbServerGroupsRequest): Promise<DetachAlbServerGroupsResponse>;
     detachDBInstancesWithOptions(request: DetachDBInstancesRequest, runtime: $Util.RuntimeOptions): Promise<DetachDBInstancesResponse>;
     detachDBInstances(request: DetachDBInstancesRequest): Promise<DetachDBInstancesResponse>;
-    /**
-      * Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
-      *
-      * @param request DetachInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DetachInstancesResponse
-     */
     detachInstancesWithOptions(request: DetachInstancesRequest, runtime: $Util.RuntimeOptions): Promise<DetachInstancesResponse>;
-    /**
-      * Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
-      *
-      * @param request DetachInstancesRequest
-      * @return DetachInstancesResponse
-     */
     detachInstances(request: DetachInstancesRequest): Promise<DetachInstancesResponse>;
     detachLoadBalancersWithOptions(request: DetachLoadBalancersRequest, runtime: $Util.RuntimeOptions): Promise<DetachLoadBalancersResponse>;
     detachLoadBalancers(request: DetachLoadBalancersRequest): Promise<DetachLoadBalancersResponse>;
     detachServerGroupsWithOptions(request: DetachServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DetachServerGroupsResponse>;
     detachServerGroups(request: DetachServerGroupsRequest): Promise<DetachServerGroupsResponse>;
-    /**
-      * Detaches one or more vServer groups of a Classic Load Balancer (CLB) instance from a scaling group.
-      *
-      * @param request DetachVServerGroupsRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DetachVServerGroupsResponse
-     */
     detachVServerGroupsWithOptions(request: DetachVServerGroupsRequest, runtime: $Util.RuntimeOptions): Promise<DetachVServerGroupsResponse>;
-    /**
-      * Detaches one or more vServer groups of a Classic Load Balancer (CLB) instance from a scaling group.
-      *
-      * @param request DetachVServerGroupsRequest
-      * @return DetachVServerGroupsResponse
-     */
     detachVServerGroups(request: DetachVServerGroupsRequest): Promise<DetachVServerGroupsResponse>;
     disableAlarmWithOptions(request: DisableAlarmRequest, runtime: $Util.RuntimeOptions): Promise<DisableAlarmResponse>;
     disableAlarm(request: DisableAlarmRequest): Promise<DisableAlarmResponse>;
-    /**
-      * Disables a scaling group.
-      *
-      * @param request DisableScalingGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return DisableScalingGroupResponse
-     */
     disableScalingGroupWithOptions(request: DisableScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<DisableScalingGroupResponse>;
-    /**
-      * Disables a scaling group.
-      *
-      * @param request DisableScalingGroupRequest
-      * @return DisableScalingGroupResponse
-     */
     disableScalingGroup(request: DisableScalingGroupRequest): Promise<DisableScalingGroupResponse>;
     enableAlarmWithOptions(request: EnableAlarmRequest, runtime: $Util.RuntimeOptions): Promise<EnableAlarmResponse>;
     enableAlarm(request: EnableAlarmRequest): Promise<EnableAlarmResponse>;
     /**
       * You can call this operation to enable a scaling group that is in the Inactive state and has an instance configuration source. The instance configuration source can be a scaling configuration, a launch template, or an Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If a scaling group is not in the Inactive state or does not have an active instance configuration source, you cannot call this operation to enable the scaling group.
       * > A scaling group can have only one active instance configuration source. When you call this operation to enable a scaling group, you can specify a scaling configuration or a launch template for the scaling group. If an instance configuration source has been configured for the scaling group before you call this operation, the scaling configuration or launch template that you specify in the request overwrites the original scaling configuration or launch template.
-      * If you specify a value for the InstanceId parameter when you call the operation, Auto Scaling checks whether the total number of ECS instances is within the range allowed in the scaling group after you call the operation.
-      * *   If the total number of ECS instances is less than the minimum number of instances allowed in the scaling group after you call the operation, Auto Scaling automatically creates the required number of pay-as-you-go ECS instances and adds the instances to the scaling group to reach the minimum number. For example, if the minimum number of instances allowed in your scaling group is five, and you specify the InstanceId parameter to add two created ECS instances to the scaling group, Auto Scaling automatically creates three instances in the scaling group after the two instances are added.
-      * *   If the value of the TotalCapactiy parameter is greater than the value of the MaxSize parameter, the call fails.
+      * If you specify a value for the InstanceIds parameter when you call the operation, Auto Scaling checks whether the total number of ECS instances is within the range allowed in the scaling group after you call the operation.
+      * *   If the total number of ECS instances is less than the minimum number of instances required in the scaling group after you call the operation, Auto Scaling automatically creates the required number of pay-as-you-go ECS instances and adds the instances to the scaling group to reach the minimum number. For example, if the minimum number of instances required in your scaling group is five, and you specify the InstanceIds parameter to add two ECS instances to the scaling group, Auto Scaling automatically creates three instances in the scaling group after the two instances are added.
+      * *   If the value of the TotalCapacity parameter is greater than the value of the MaxSize parameter, the call fails.
       *
       * @param request EnableScalingGroupRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7324,52 +7212,20 @@ export default class Client extends OpenApi {
     /**
       * You can call this operation to enable a scaling group that is in the Inactive state and has an instance configuration source. The instance configuration source can be a scaling configuration, a launch template, or an Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If a scaling group is not in the Inactive state or does not have an active instance configuration source, you cannot call this operation to enable the scaling group.
       * > A scaling group can have only one active instance configuration source. When you call this operation to enable a scaling group, you can specify a scaling configuration or a launch template for the scaling group. If an instance configuration source has been configured for the scaling group before you call this operation, the scaling configuration or launch template that you specify in the request overwrites the original scaling configuration or launch template.
-      * If you specify a value for the InstanceId parameter when you call the operation, Auto Scaling checks whether the total number of ECS instances is within the range allowed in the scaling group after you call the operation.
-      * *   If the total number of ECS instances is less than the minimum number of instances allowed in the scaling group after you call the operation, Auto Scaling automatically creates the required number of pay-as-you-go ECS instances and adds the instances to the scaling group to reach the minimum number. For example, if the minimum number of instances allowed in your scaling group is five, and you specify the InstanceId parameter to add two created ECS instances to the scaling group, Auto Scaling automatically creates three instances in the scaling group after the two instances are added.
-      * *   If the value of the TotalCapactiy parameter is greater than the value of the MaxSize parameter, the call fails.
+      * If you specify a value for the InstanceIds parameter when you call the operation, Auto Scaling checks whether the total number of ECS instances is within the range allowed in the scaling group after you call the operation.
+      * *   If the total number of ECS instances is less than the minimum number of instances required in the scaling group after you call the operation, Auto Scaling automatically creates the required number of pay-as-you-go ECS instances and adds the instances to the scaling group to reach the minimum number. For example, if the minimum number of instances required in your scaling group is five, and you specify the InstanceIds parameter to add two ECS instances to the scaling group, Auto Scaling automatically creates three instances in the scaling group after the two instances are added.
+      * *   If the value of the TotalCapacity parameter is greater than the value of the MaxSize parameter, the call fails.
       *
       * @param request EnableScalingGroupRequest
       * @return EnableScalingGroupResponse
      */
     enableScalingGroup(request: EnableScalingGroupRequest): Promise<EnableScalingGroupResponse>;
-    /**
-      * *   If you call the operation to set an Elastic Compute Service (ECS) instance in a scaling group that is associated with a Server Load Balancer (SLB) instance to the Standby state, the weight of the ECS instance as a backend server of the SLB instance is set to 0.
-      * *   You can remove an ECS instance that is in the Standby state from a scaling group and release the instance.
-      * *   When scale-in activities are triggered by changes in the number of scaling groups or by event-triggered tasks, the ECS instances that are in the Standby state are not removed from the scaling groups.
-      * *   If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, such as in the Stopping or Restarting state, Auto Scaling does not update the health check status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health check status of the ECS instance only when the ECS instance is no longer in the Standby state.
-      *
-      * @param request EnterStandbyRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return EnterStandbyResponse
-     */
     enterStandbyWithOptions(request: EnterStandbyRequest, runtime: $Util.RuntimeOptions): Promise<EnterStandbyResponse>;
-    /**
-      * *   If you call the operation to set an Elastic Compute Service (ECS) instance in a scaling group that is associated with a Server Load Balancer (SLB) instance to the Standby state, the weight of the ECS instance as a backend server of the SLB instance is set to 0.
-      * *   You can remove an ECS instance that is in the Standby state from a scaling group and release the instance.
-      * *   When scale-in activities are triggered by changes in the number of scaling groups or by event-triggered tasks, the ECS instances that are in the Standby state are not removed from the scaling groups.
-      * *   If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, such as in the Stopping or Restarting state, Auto Scaling does not update the health check status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health check status of the ECS instance only when the ECS instance is no longer in the Standby state.
-      *
-      * @param request EnterStandbyRequest
-      * @return EnterStandbyResponse
-     */
     enterStandby(request: EnterStandbyRequest): Promise<EnterStandbyResponse>;
-    /**
-      * Executes a scaling rule.
-      *
-      * @param request ExecuteScalingRuleRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ExecuteScalingRuleResponse
-     */
     executeScalingRuleWithOptions(request: ExecuteScalingRuleRequest, runtime: $Util.RuntimeOptions): Promise<ExecuteScalingRuleResponse>;
-    /**
-      * Executes a scaling rule.
-      *
-      * @param request ExecuteScalingRuleRequest
-      * @return ExecuteScalingRuleResponse
-     */
     executeScalingRule(request: ExecuteScalingRuleRequest): Promise<ExecuteScalingRuleResponse>;
     /**
-      * If the scaling group is associated with a load balancing instance, the ECS instance weight will be set to the weight value defined in the scaling configuration.
+      * The IDs of the ECS instances. The value of this parameter can be a JSON array that consists of up to 20 instance IDs. Separate multiple instance IDs with commas (,).
       *
       * @param request ExitStandbyRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7377,7 +7233,7 @@ export default class Client extends OpenApi {
      */
     exitStandbyWithOptions(request: ExitStandbyRequest, runtime: $Util.RuntimeOptions): Promise<ExitStandbyResponse>;
     /**
-      * If the scaling group is associated with a load balancing instance, the ECS instance weight will be set to the weight value defined in the scaling configuration.
+      * The IDs of the ECS instances. The value of this parameter can be a JSON array that consists of up to 20 instance IDs. Separate multiple instance IDs with commas (,).
       *
       * @param request ExitStandbyRequest
       * @return ExitStandbyResponse
@@ -7390,7 +7246,11 @@ export default class Client extends OpenApi {
     listTagValuesWithOptions(request: ListTagValuesRequest, runtime: $Util.RuntimeOptions): Promise<ListTagValuesResponse>;
     listTagValues(request: ListTagValuesRequest): Promise<ListTagValuesResponse>;
     /**
-      * Modifies an event-triggered task.
+      * *   If you set MetricType to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Custom monitoring event-triggered tasks](~~74861~~).
+      * *   When you create an event-triggered task, you must specify MetricName, DimensionKey, and DimensionValue to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances in a scaling group within an Alibaba Cloud account.
+      *     *   If you set MetricType to custom, the valid values are your custom metrics.
+      *     *   For information about the metrics that are supported if you set MetricType to system, see [Event-triggered task for system monitoring](~~74854~~).
+      * > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see `DimensionKey` and `DimensionValue` in the "Request parameters" section of this topic.
       *
       * @param request ModifyAlarmRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7398,7 +7258,11 @@ export default class Client extends OpenApi {
      */
     modifyAlarmWithOptions(request: ModifyAlarmRequest, runtime: $Util.RuntimeOptions): Promise<ModifyAlarmResponse>;
     /**
-      * Modifies an event-triggered task.
+      * *   If you set MetricType to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Custom monitoring event-triggered tasks](~~74861~~).
+      * *   When you create an event-triggered task, you must specify MetricName, DimensionKey, and DimensionValue to determine the range of statistics that you want to aggregate for the metrics of the scaling group. For example, you can specify the user_id and scaling_group dimensions for an event-triggered task to aggregate monitoring data of all Elastic Compute Service (ECS) instances in a scaling group within an Alibaba Cloud account.
+      *     *   If you set MetricType to custom, the valid values are your custom metrics.
+      *     *   For information about the metrics that are supported if you set MetricType to system, see [Event-triggered task for system monitoring](~~74854~~).
+      * > The user_id and scaling_group dimensions are automatically populated. You need to only specify the device and state dimensions. For more information, see `DimensionKey` and `DimensionValue` in the "Request parameters" section of this topic.
       *
       * @param request ModifyAlarmRequest
       * @return ModifyAlarmResponse
@@ -7420,7 +7284,9 @@ export default class Client extends OpenApi {
      */
     modifyEciScalingConfiguration(request: ModifyEciScalingConfigurationRequest): Promise<ModifyEciScalingConfigurationResponse>;
     /**
-      * Modifies a lifecycle hook.
+      * You can use one of the following methods to specify the lifecycle hook that you want to modify:
+      * *   Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
+      * *   Specify the scaling group ID by using the ScalingGroupId parameter and specify the lifecycle hook name by using the LifecycleHookName parameter.
       *
       * @param request ModifyLifecycleHookRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7428,7 +7294,9 @@ export default class Client extends OpenApi {
      */
     modifyLifecycleHookWithOptions(request: ModifyLifecycleHookRequest, runtime: $Util.RuntimeOptions): Promise<ModifyLifecycleHookResponse>;
     /**
-      * Modifies a lifecycle hook.
+      * You can use one of the following methods to specify the lifecycle hook that you want to modify:
+      * *   Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
+      * *   Specify the scaling group ID by using the ScalingGroupId parameter and specify the lifecycle hook name by using the LifecycleHookName parameter.
       *
       * @param request ModifyLifecycleHookRequest
       * @return ModifyLifecycleHookResponse
@@ -7437,7 +7305,7 @@ export default class Client extends OpenApi {
     modifyNotificationConfigurationWithOptions(request: ModifyNotificationConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<ModifyNotificationConfigurationResponse>;
     modifyNotificationConfiguration(request: ModifyNotificationConfigurationRequest): Promise<ModifyNotificationConfigurationResponse>;
     /**
-      * If you want to change the name of a scaling configuration in a scaling group, make sure that the new name is unique within the scaling group.
+      * You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
       *
       * @param tmpReq ModifyScalingConfigurationRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7445,114 +7313,28 @@ export default class Client extends OpenApi {
      */
     modifyScalingConfigurationWithOptions(tmpReq: ModifyScalingConfigurationRequest, runtime: $Util.RuntimeOptions): Promise<ModifyScalingConfigurationResponse>;
     /**
-      * If you want to change the name of a scaling configuration in a scaling group, make sure that the new name is unique within the scaling group.
+      * You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
       *
       * @param request ModifyScalingConfigurationRequest
       * @return ModifyScalingConfigurationResponse
      */
     modifyScalingConfiguration(request: ModifyScalingConfigurationRequest): Promise<ModifyScalingConfigurationResponse>;
-    /**
-      * Modifies a scaling group.
-      *
-      * @param request ModifyScalingGroupRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyScalingGroupResponse
-     */
     modifyScalingGroupWithOptions(request: ModifyScalingGroupRequest, runtime: $Util.RuntimeOptions): Promise<ModifyScalingGroupResponse>;
-    /**
-      * Modifies a scaling group.
-      *
-      * @param request ModifyScalingGroupRequest
-      * @return ModifyScalingGroupResponse
-     */
     modifyScalingGroup(request: ModifyScalingGroupRequest): Promise<ModifyScalingGroupResponse>;
     modifyScalingRuleWithOptions(request: ModifyScalingRuleRequest, runtime: $Util.RuntimeOptions): Promise<ModifyScalingRuleResponse>;
     modifyScalingRule(request: ModifyScalingRuleRequest): Promise<ModifyScalingRuleResponse>;
-    /**
-      * Modifies a scheduled task.
-      *
-      * @param request ModifyScheduledTaskRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return ModifyScheduledTaskResponse
-     */
     modifyScheduledTaskWithOptions(request: ModifyScheduledTaskRequest, runtime: $Util.RuntimeOptions): Promise<ModifyScheduledTaskResponse>;
-    /**
-      * Modifies a scheduled task.
-      *
-      * @param request ModifyScheduledTaskRequest
-      * @return ModifyScheduledTaskResponse
-     */
     modifyScheduledTask(request: ModifyScheduledTaskRequest): Promise<ModifyScheduledTaskResponse>;
-    /**
-      * Rebalances Elastic Compute Service (ECS) instances in a multi-zone scaling group across zones.
-      *
-      * @param request RebalanceInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return RebalanceInstancesResponse
-     */
     rebalanceInstancesWithOptions(request: RebalanceInstancesRequest, runtime: $Util.RuntimeOptions): Promise<RebalanceInstancesResponse>;
-    /**
-      * Rebalances Elastic Compute Service (ECS) instances in a multi-zone scaling group across zones.
-      *
-      * @param request RebalanceInstancesRequest
-      * @return RebalanceInstancesResponse
-     */
     rebalanceInstances(request: RebalanceInstancesRequest): Promise<RebalanceInstancesResponse>;
-    /**
-      * Prolongs a lifecycle hook for Elastic Compute Service (ECS) instances.
-      *
-      * @param request RecordLifecycleActionHeartbeatRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return RecordLifecycleActionHeartbeatResponse
-     */
     recordLifecycleActionHeartbeatWithOptions(request: RecordLifecycleActionHeartbeatRequest, runtime: $Util.RuntimeOptions): Promise<RecordLifecycleActionHeartbeatResponse>;
-    /**
-      * Prolongs a lifecycle hook for Elastic Compute Service (ECS) instances.
-      *
-      * @param request RecordLifecycleActionHeartbeatRequest
-      * @return RecordLifecycleActionHeartbeatResponse
-     */
     recordLifecycleActionHeartbeat(request: RecordLifecycleActionHeartbeatRequest): Promise<RecordLifecycleActionHeartbeatResponse>;
-    /**
-      * *   Before you call this operation, make sure that the following requirements are met:
-      *     *   The scaling group is in the Active state.
-      *     *   No scaling activity is in progress within the scaling group.
-      * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
-      * *   If an ECS instance is automatically created by Auto Scaling, or if an ECS instance is manually added to a scaling group and managed by the scaling group, the ECS instance is stopped in economical mode or is released after the instance is removed from the scaling group.
-      * *   If an ECS instance is manually added to a scaling group and is not managed by the scaling group, the ECS instance is not stopped or released after the instance is removed from the scaling group.
-      * *   If the difference between the number of existing ECS instances specified by the TotalCapacity parameter and the number of ECS instances that you call this operation to remove is less than the value of the MinSize parameter, the call fails.
-      * A successful call only means that Auto Scaling accepts the request. The scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
-      *
-      * @param request RemoveInstancesRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return RemoveInstancesResponse
-     */
     removeInstancesWithOptions(request: RemoveInstancesRequest, runtime: $Util.RuntimeOptions): Promise<RemoveInstancesResponse>;
-    /**
-      * *   Before you call this operation, make sure that the following requirements are met:
-      *     *   The scaling group is in the Active state.
-      *     *   No scaling activity is in progress within the scaling group.
-      * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
-      * *   If an ECS instance is automatically created by Auto Scaling, or if an ECS instance is manually added to a scaling group and managed by the scaling group, the ECS instance is stopped in economical mode or is released after the instance is removed from the scaling group.
-      * *   If an ECS instance is manually added to a scaling group and is not managed by the scaling group, the ECS instance is not stopped or released after the instance is removed from the scaling group.
-      * *   If the difference between the number of existing ECS instances specified by the TotalCapacity parameter and the number of ECS instances that you call this operation to remove is less than the value of the MinSize parameter, the call fails.
-      * A successful call only means that Auto Scaling accepts the request. The scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
-      *
-      * @param request RemoveInstancesRequest
-      * @return RemoveInstancesResponse
-     */
     removeInstances(request: RemoveInstancesRequest): Promise<RemoveInstancesResponse>;
     resumeProcessesWithOptions(request: ResumeProcessesRequest, runtime: $Util.RuntimeOptions): Promise<ResumeProcessesResponse>;
     resumeProcesses(request: ResumeProcessesRequest): Promise<ResumeProcessesResponse>;
     /**
-      * Compared with the ExecuteScalingRule operation, the ScaleWithAdjustment operation does not require a scaling rule to be created in advance. Before you call the ScaleWithAdjustment operation, take note of the following items:
-      * *   The following conditions must be met:
-      *     *   The scaling group is in the Active state.
-      *     *   No scaling activities in the scaling group are in progress.
-      * *   If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
-      * *   If the addition of a specified number of Elastic Compute Service (ECS) instances to a scaling group causes the total number of ECS instances in the scaling group to exceed the maximum number of instances allowed, Auto Scaling adds only a specific number of ECS instances to ensure that the total number of instances is equal to the maximum number of instances.
-      * *   If the removal of a specified number of ECS instances from a scaling group causes the total number of ECS instances in the scaling group to drop below the minimum number of instances allowed, Auto Scaling removes only a specific number of ECS instances to ensure that the total number of instances is equal to the minimum number of instances.
-      * A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the `ScalingActivityId` parameter in the response.
+      * The ID of the scaling activity.
       *
       * @param request ScaleWithAdjustmentRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -7560,14 +7342,7 @@ export default class Client extends OpenApi {
      */
     scaleWithAdjustmentWithOptions(request: ScaleWithAdjustmentRequest, runtime: $Util.RuntimeOptions): Promise<ScaleWithAdjustmentResponse>;
     /**
-      * Compared with the ExecuteScalingRule operation, the ScaleWithAdjustment operation does not require a scaling rule to be created in advance. Before you call the ScaleWithAdjustment operation, take note of the following items:
-      * *   The following conditions must be met:
-      *     *   The scaling group is in the Active state.
-      *     *   No scaling activities in the scaling group are in progress.
-      * *   If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
-      * *   If the addition of a specified number of Elastic Compute Service (ECS) instances to a scaling group causes the total number of ECS instances in the scaling group to exceed the maximum number of instances allowed, Auto Scaling adds only a specific number of ECS instances to ensure that the total number of instances is equal to the maximum number of instances.
-      * *   If the removal of a specified number of ECS instances from a scaling group causes the total number of ECS instances in the scaling group to drop below the minimum number of instances allowed, Auto Scaling removes only a specific number of ECS instances to ensure that the total number of instances is equal to the minimum number of instances.
-      * A successful call indicates that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity by using the value of the `ScalingActivityId` parameter in the response.
+      * The ID of the scaling activity.
       *
       * @param request ScaleWithAdjustmentRequest
       * @return ScaleWithAdjustmentResponse
@@ -7575,35 +7350,9 @@ export default class Client extends OpenApi {
     scaleWithAdjustment(request: ScaleWithAdjustmentRequest): Promise<ScaleWithAdjustmentResponse>;
     setGroupDeletionProtectionWithOptions(request: SetGroupDeletionProtectionRequest, runtime: $Util.RuntimeOptions): Promise<SetGroupDeletionProtectionResponse>;
     setGroupDeletionProtection(request: SetGroupDeletionProtectionRequest): Promise<SetGroupDeletionProtectionResponse>;
-    /**
-      * Configures the health check feature for Elastic Compute Service (ECS) instances.
-      *
-      * @param request SetInstanceHealthRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return SetInstanceHealthResponse
-     */
     setInstanceHealthWithOptions(request: SetInstanceHealthRequest, runtime: $Util.RuntimeOptions): Promise<SetInstanceHealthResponse>;
-    /**
-      * Configures the health check feature for Elastic Compute Service (ECS) instances.
-      *
-      * @param request SetInstanceHealthRequest
-      * @return SetInstanceHealthResponse
-     */
     setInstanceHealth(request: SetInstanceHealthRequest): Promise<SetInstanceHealthResponse>;
-    /**
-      * Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
-      *
-      * @param request SetInstancesProtectionRequest
-      * @param runtime runtime options for this request RuntimeOptions
-      * @return SetInstancesProtectionResponse
-     */
     setInstancesProtectionWithOptions(request: SetInstancesProtectionRequest, runtime: $Util.RuntimeOptions): Promise<SetInstancesProtectionResponse>;
-    /**
-      * Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
-      *
-      * @param request SetInstancesProtectionRequest
-      * @return SetInstancesProtectionResponse
-     */
     setInstancesProtection(request: SetInstancesProtectionRequest): Promise<SetInstancesProtectionResponse>;
     suspendProcessesWithOptions(request: SuspendProcessesRequest, runtime: $Util.RuntimeOptions): Promise<SuspendProcessesResponse>;
     suspendProcesses(request: SuspendProcessesRequest): Promise<SuspendProcessesResponse>;