@alicloud/ess20220222 1.0.3 → 1.0.4

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;
@@ -3129,6 +3135,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 +3195,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 +3351,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;
@@ -4060,6 +4069,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 +4207,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 +4264,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 +4295,7 @@ export declare class CreateEciScalingConfigurationRequestContainersSecurityConte
     });
 }
 export declare class CreateEciScalingConfigurationRequestContainersSecurityContext extends $tea.Model {
-    capability: CreateEciScalingConfigurationRequestContainersSecurityContextCapability;
+    capability?: CreateEciScalingConfigurationRequestContainersSecurityContextCapability;
     readOnlyRootFilesystem?: boolean;
     runAsUser?: number;
     static names(): {
@@ -4330,9 +4352,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 +4433,7 @@ export declare class CreateEciScalingConfigurationRequestInitContainersSecurityC
     });
 }
 export declare class CreateEciScalingConfigurationRequestInitContainersSecurityContext extends $tea.Model {
-    capability: CreateEciScalingConfigurationRequestInitContainersSecurityContextCapability;
+    capability?: CreateEciScalingConfigurationRequestInitContainersSecurityContextCapability;
     readOnlyRootFilesystem?: boolean;
     runAsUser?: number;
     static names(): {
@@ -4468,7 +4490,7 @@ export declare class CreateEciScalingConfigurationRequestInitContainersInitConta
     });
 }
 export declare class CreateEciScalingConfigurationRequestInitContainers extends $tea.Model {
-    securityContext: CreateEciScalingConfigurationRequestInitContainersSecurityContext;
+    securityContext?: CreateEciScalingConfigurationRequestInitContainersSecurityContext;
     args?: string[];
     commands?: string[];
     cpu?: number;
@@ -4599,11 +4621,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 +4640,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 +4756,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 +4917,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 +4985,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;
@@ -5532,7 +5604,7 @@ export declare class DescribeScalingConfigurationsResponseBodyScalingConfigurati
     });
 }
 export declare class DescribeScalingConfigurationsResponseBodyScalingConfigurations extends $tea.Model {
-    privatePoolOptions: DescribeScalingConfigurationsResponseBodyScalingConfigurationsPrivatePoolOptions;
+    privatePoolOptions?: DescribeScalingConfigurationsResponseBodyScalingConfigurationsPrivatePoolOptions;
     affinity?: string;
     cpu?: number;
     creationTime?: string;
@@ -5545,6 +5617,7 @@ export declare class DescribeScalingConfigurationsResponseBodyScalingConfigurati
     imageFamily?: string;
     imageId?: string;
     imageName?: string;
+    imageOptionsLoginAsNonRoot?: boolean;
     imageOwnerAlias?: string;
     instanceDescription?: string;
     instanceGeneration?: string;
@@ -5630,6 +5703,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;
@@ -5694,6 +5780,7 @@ export declare class DescribeScalingGroupsResponseBodyScalingGroups extends $tea
     launchTemplateOverrides?: DescribeScalingGroupsResponseBodyScalingGroupsLaunchTemplateOverrides[];
     launchTemplateVersion?: string;
     lifecycleState?: string;
+    loadBalancerConfigs?: DescribeScalingGroupsResponseBodyScalingGroupsLoadBalancerConfigs[];
     loadBalancerIds?: string[];
     maxInstanceLifetime?: number;
     maxSize?: number;
@@ -5766,6 +5853,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 +5916,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 +6152,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 +6209,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 +6240,7 @@ export declare class ModifyEciScalingConfigurationRequestContainersSecurityConte
     });
 }
 export declare class ModifyEciScalingConfigurationRequestContainersSecurityContext extends $tea.Model {
-    capability: ModifyEciScalingConfigurationRequestContainersSecurityContextCapability;
+    capability?: ModifyEciScalingConfigurationRequestContainersSecurityContextCapability;
     readOnlyRootFilesystem?: boolean;
     runAsUser?: number;
     static names(): {
@@ -6165,7 +6266,7 @@ export declare class ModifyEciScalingConfigurationRequestContainersEnvironmentVa
     });
 }
 export declare class ModifyEciScalingConfigurationRequestContainersEnvironmentVars extends $tea.Model {
-    fieldRef: ModifyEciScalingConfigurationRequestContainersEnvironmentVarsFieldRef;
+    fieldRef?: ModifyEciScalingConfigurationRequestContainersEnvironmentVarsFieldRef;
     key?: string;
     value?: string;
     static names(): {
@@ -6208,9 +6309,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 +6390,7 @@ export declare class ModifyEciScalingConfigurationRequestInitContainersSecurityC
     });
 }
 export declare class ModifyEciScalingConfigurationRequestInitContainersSecurityContext extends $tea.Model {
-    capability: ModifyEciScalingConfigurationRequestInitContainersSecurityContextCapability;
+    capability?: ModifyEciScalingConfigurationRequestInitContainersSecurityContextCapability;
     readOnlyRootFilesystem?: boolean;
     runAsUser?: number;
     static names(): {
@@ -6315,7 +6416,7 @@ export declare class ModifyEciScalingConfigurationRequestInitContainersInitConta
     });
 }
 export declare class ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVars extends $tea.Model {
-    fieldRef: ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVarsFieldRef;
+    fieldRef?: ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVarsFieldRef;
     key?: string;
     value?: string;
     static names(): {
@@ -6358,7 +6459,7 @@ export declare class ModifyEciScalingConfigurationRequestInitContainersInitConta
     });
 }
 export declare class ModifyEciScalingConfigurationRequestInitContainers extends $tea.Model {
-    securityContext: ModifyEciScalingConfigurationRequestInitContainersSecurityContext;
+    securityContext?: ModifyEciScalingConfigurationRequestInitContainersSecurityContext;
     args?: string[];
     commands?: string[];
     cpu?: number;
@@ -6489,11 +6590,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 +6609,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 +6725,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 +6855,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;
@@ -6856,7 +6994,7 @@ export default class Client extends OpenApi {
      */
     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,7 +7002,7 @@ 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
@@ -6911,10 +7049,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,10 +7060,10 @@ 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
@@ -6947,13 +7085,13 @@ export default class Client extends OpenApi {
      */
     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 lowest-priced instance type based on your configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode reduces the failures of scale-outs caused by insufficient inventory of instance types.
       * *   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 of the lowest-priced instance type. This mode is available only if the Scaling Policy parameter is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
+      * > You cannot specify InstanceType, InstanceTypes, InstanceTypeOverrides, and Cpu and Memory parameters at the same time. You can specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfo at the same time. If you specify the InstanceType and InstancePatternInfos parameters or specify the InstanceTypes and InstancePatternInfos parameters at the same time, Auto Scaling preferentially uses the instance types that are specified by the InstanceType or InstanceTypes parameter for scale-outs. If the instance types that are specified by the InstanceType or InstanceTypes parameter do not have sufficient inventory, Auto Scaling uses the instance types that are specified by the InstancePatternInfos parameter for scale-outs.
       *
       * @param tmpReq CreateScalingConfigurationRequest
       * @param runtime runtime options for this request RuntimeOptions
@@ -6961,13 +7099,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 lowest-priced instance type based on your configurations to create ECS instances. This mode is available only for scaling groups that reside in virtual private clouds (VPCs). This mode reduces the failures of scale-outs caused by insufficient inventory of instance types.
       * *   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 of the lowest-priced instance type. This mode is available only if the Scaling Policy parameter is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
+      * > You cannot specify InstanceType, InstanceTypes, InstanceTypeOverrides, and Cpu and Memory parameters at the same time. You can specify InstanceType and InstancePatternInfos or specify InstanceTypes and InstancePatternInfo at the same time. If you specify the InstanceType and InstancePatternInfos parameters or specify the InstanceTypes and InstancePatternInfos parameters at the same time, Auto Scaling preferentially uses the instance types that are specified by the InstanceType or InstanceTypes parameter for scale-outs. If the instance types that are specified by the InstanceType or InstanceTypes parameter do not have sufficient inventory, Auto Scaling uses the instance types that are specified by the InstancePatternInfos parameter for scale-outs.
       *
       * @param request CreateScalingConfigurationRequest
       * @return CreateScalingConfigurationResponse
@@ -6976,26 +7114,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,26 +7143,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
       * @return CreateScalingGroupResponse
@@ -7312,9 +7450,9 @@ 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
       * @param runtime runtime options for this request RuntimeOptions
@@ -7324,9 +7462,9 @@ 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
@@ -7420,7 +7558,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 +7568,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