@alicloud/ess20220222 1.3.2 → 1.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/client.js CHANGED
@@ -28,14 +28,14 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
28
28
  Object.defineProperty(exports, "__esModule", { value: true });
29
29
  exports.CreateScalingRuleRequest = exports.CreateScalingGroupResponse = exports.CreateScalingGroupResponseBody = exports.CreateScalingGroupRequest = exports.CreateScalingConfigurationResponse = exports.CreateScalingConfigurationResponseBody = exports.CreateScalingConfigurationShrinkRequest = exports.CreateScalingConfigurationRequest = exports.CreateNotificationConfigurationResponse = exports.CreateNotificationConfigurationResponseBody = exports.CreateNotificationConfigurationRequest = exports.CreateLifecycleHookResponse = exports.CreateLifecycleHookResponseBody = exports.CreateLifecycleHookRequest = exports.CreateEciScalingConfigurationResponse = exports.CreateEciScalingConfigurationResponseBody = exports.CreateEciScalingConfigurationRequest = exports.CreateAlarmResponse = exports.CreateAlarmResponseBody = exports.CreateAlarmRequest = exports.CompleteLifecycleActionResponse = exports.CompleteLifecycleActionResponseBody = exports.CompleteLifecycleActionRequest = exports.ChangeResourceGroupResponse = exports.ChangeResourceGroupResponseBody = exports.ChangeResourceGroupRequest = exports.AttachVServerGroupsResponse = exports.AttachVServerGroupsResponseBody = exports.AttachVServerGroupsRequest = exports.AttachServerGroupsResponse = exports.AttachServerGroupsResponseBody = exports.AttachServerGroupsRequest = exports.AttachLoadBalancersResponse = exports.AttachLoadBalancersResponseBody = exports.AttachLoadBalancersRequest = exports.AttachInstancesResponse = exports.AttachInstancesResponseBody = exports.AttachInstancesRequest = exports.AttachDBInstancesResponse = exports.AttachDBInstancesResponseBody = exports.AttachDBInstancesRequest = exports.AttachAlbServerGroupsResponse = exports.AttachAlbServerGroupsResponseBody = exports.AttachAlbServerGroupsRequest = exports.ApplyScalingGroupResponse = exports.ApplyScalingGroupResponseBody = exports.ApplyScalingGroupRequest = exports.ApplyEciScalingConfigurationResponse = exports.ApplyEciScalingConfigurationResponseBody = exports.ApplyEciScalingConfigurationRequest = void 0;
30
30
  exports.DescribeLimitationResponse = exports.DescribeLimitationResponseBody = exports.DescribeLimitationRequest = exports.DescribeLifecycleHooksResponse = exports.DescribeLifecycleHooksResponseBody = exports.DescribeLifecycleHooksRequest = exports.DescribeLifecycleActionsResponse = exports.DescribeLifecycleActionsResponseBody = exports.DescribeLifecycleActionsRequest = exports.DescribeEciScalingConfigurationsResponse = exports.DescribeEciScalingConfigurationsResponseBody = exports.DescribeEciScalingConfigurationsRequest = exports.DescribeEciScalingConfigurationDetailResponse = exports.DescribeEciScalingConfigurationDetailResponseBody = exports.DescribeEciScalingConfigurationDetailRequest = exports.DescribeAlarmsResponse = exports.DescribeAlarmsResponseBody = exports.DescribeAlarmsRequest = exports.DeleteScheduledTaskResponse = exports.DeleteScheduledTaskResponseBody = exports.DeleteScheduledTaskRequest = exports.DeleteScalingRuleResponse = exports.DeleteScalingRuleResponseBody = exports.DeleteScalingRuleRequest = exports.DeleteScalingGroupResponse = exports.DeleteScalingGroupResponseBody = exports.DeleteScalingGroupRequest = exports.DeleteScalingConfigurationResponse = exports.DeleteScalingConfigurationResponseBody = exports.DeleteScalingConfigurationRequest = exports.DeleteNotificationConfigurationResponse = exports.DeleteNotificationConfigurationResponseBody = exports.DeleteNotificationConfigurationRequest = exports.DeleteLifecycleHookResponse = exports.DeleteLifecycleHookResponseBody = exports.DeleteLifecycleHookRequest = exports.DeleteEciScalingConfigurationResponse = exports.DeleteEciScalingConfigurationResponseBody = exports.DeleteEciScalingConfigurationRequest = exports.DeleteAlarmResponse = exports.DeleteAlarmResponseBody = exports.DeleteAlarmRequest = exports.DeactivateScalingConfigurationResponse = exports.DeactivateScalingConfigurationResponseBody = exports.DeactivateScalingConfigurationRequest = exports.CreateScheduledTaskResponse = exports.CreateScheduledTaskResponseBody = exports.CreateScheduledTaskRequest = exports.CreateScalingRuleResponse = exports.CreateScalingRuleResponseBody = void 0;
31
- exports.DetachVServerGroupsResponseBody = exports.DetachVServerGroupsRequest = exports.DetachServerGroupsResponse = exports.DetachServerGroupsResponseBody = exports.DetachServerGroupsRequest = exports.DetachLoadBalancersResponse = exports.DetachLoadBalancersResponseBody = exports.DetachLoadBalancersRequest = exports.DetachInstancesResponse = exports.DetachInstancesResponseBody = exports.DetachInstancesRequest = exports.DetachDBInstancesResponse = exports.DetachDBInstancesResponseBody = exports.DetachDBInstancesRequest = exports.DetachAlbServerGroupsResponse = exports.DetachAlbServerGroupsResponseBody = exports.DetachAlbServerGroupsRequest = exports.DescribeScheduledTasksResponse = exports.DescribeScheduledTasksResponseBody = exports.DescribeScheduledTasksRequest = exports.DescribeScalingRulesResponse = exports.DescribeScalingRulesResponseBody = exports.DescribeScalingRulesRequest = exports.DescribeScalingInstancesResponse = exports.DescribeScalingInstancesResponseBody = exports.DescribeScalingInstancesRequest = exports.DescribeScalingGroupsResponse = exports.DescribeScalingGroupsResponseBody = exports.DescribeScalingGroupsRequest = exports.DescribeScalingGroupDetailResponse = exports.DescribeScalingGroupDetailResponseBody = exports.DescribeScalingGroupDetailRequest = exports.DescribeScalingConfigurationsResponse = exports.DescribeScalingConfigurationsResponseBody = exports.DescribeScalingConfigurationsRequest = exports.DescribeScalingActivityDetailResponse = exports.DescribeScalingActivityDetailResponseBody = exports.DescribeScalingActivityDetailRequest = exports.DescribeScalingActivitiesResponse = exports.DescribeScalingActivitiesResponseBody = exports.DescribeScalingActivitiesRequest = exports.DescribeRegionsResponse = exports.DescribeRegionsResponseBody = exports.DescribeRegionsRequest = exports.DescribeNotificationTypesResponse = exports.DescribeNotificationTypesResponseBody = exports.DescribeNotificationTypesRequest = exports.DescribeNotificationConfigurationsResponse = exports.DescribeNotificationConfigurationsResponseBody = exports.DescribeNotificationConfigurationsRequest = void 0;
32
- exports.ModifyScalingConfigurationResponse = exports.ModifyScalingConfigurationResponseBody = exports.ModifyScalingConfigurationShrinkRequest = exports.ModifyScalingConfigurationRequest = exports.ModifyNotificationConfigurationResponse = exports.ModifyNotificationConfigurationResponseBody = exports.ModifyNotificationConfigurationRequest = exports.ModifyLifecycleHookResponse = exports.ModifyLifecycleHookResponseBody = exports.ModifyLifecycleHookRequest = exports.ModifyInstanceAttributeResponse = exports.ModifyInstanceAttributeResponseBody = exports.ModifyInstanceAttributeRequest = exports.ModifyEciScalingConfigurationResponse = exports.ModifyEciScalingConfigurationResponseBody = exports.ModifyEciScalingConfigurationRequest = exports.ModifyAlarmResponse = exports.ModifyAlarmResponseBody = exports.ModifyAlarmRequest = exports.ListTagValuesResponse = exports.ListTagValuesResponseBody = exports.ListTagValuesRequest = exports.ListTagResourcesResponse = exports.ListTagResourcesResponseBody = exports.ListTagResourcesRequest = exports.ListTagKeysResponse = exports.ListTagKeysResponseBody = exports.ListTagKeysRequest = exports.ExitStandbyResponse = exports.ExitStandbyResponseBody = exports.ExitStandbyRequest = exports.ExecuteScalingRuleResponse = exports.ExecuteScalingRuleResponseBody = exports.ExecuteScalingRuleRequest = exports.EnterStandbyResponse = exports.EnterStandbyResponseBody = exports.EnterStandbyRequest = exports.EnableScalingGroupResponse = exports.EnableScalingGroupResponseBody = exports.EnableScalingGroupRequest = exports.EnableAlarmResponse = exports.EnableAlarmResponseBody = exports.EnableAlarmRequest = exports.DisableScalingGroupResponse = exports.DisableScalingGroupResponseBody = exports.DisableScalingGroupRequest = exports.DisableAlarmResponse = exports.DisableAlarmResponseBody = exports.DisableAlarmRequest = exports.DetachVServerGroupsResponse = void 0;
33
- exports.AttachAlbServerGroupsRequestAlbServerGroups = exports.VerifyUserResponse = exports.VerifyUserResponseBody = exports.VerifyUserRequest = exports.VerifyAuthenticationResponse = exports.VerifyAuthenticationResponseBody = exports.VerifyAuthenticationRequest = exports.UntagResourcesResponse = exports.UntagResourcesResponseBody = exports.UntagResourcesRequest = exports.TagResourcesResponse = exports.TagResourcesResponseBody = exports.TagResourcesRequest = exports.SuspendProcessesResponse = exports.SuspendProcessesResponseBody = exports.SuspendProcessesRequest = exports.SetInstancesProtectionResponse = exports.SetInstancesProtectionResponseBody = exports.SetInstancesProtectionRequest = exports.SetInstanceHealthResponse = exports.SetInstanceHealthResponseBody = exports.SetInstanceHealthRequest = exports.SetGroupDeletionProtectionResponse = exports.SetGroupDeletionProtectionResponseBody = exports.SetGroupDeletionProtectionRequest = exports.ScaleWithAdjustmentResponse = exports.ScaleWithAdjustmentResponseBody = exports.ScaleWithAdjustmentShrinkRequest = exports.ScaleWithAdjustmentRequest = exports.ResumeProcessesResponse = exports.ResumeProcessesResponseBody = exports.ResumeProcessesRequest = exports.RemoveInstancesResponse = exports.RemoveInstancesResponseBody = exports.RemoveInstancesRequest = exports.RecordLifecycleActionHeartbeatResponse = exports.RecordLifecycleActionHeartbeatResponseBody = exports.RecordLifecycleActionHeartbeatRequest = exports.RebalanceInstancesResponse = exports.RebalanceInstancesResponseBody = exports.RebalanceInstancesRequest = exports.ModifyScheduledTaskResponse = exports.ModifyScheduledTaskResponseBody = exports.ModifyScheduledTaskRequest = exports.ModifyScalingRuleResponse = exports.ModifyScalingRuleResponseBody = exports.ModifyScalingRuleRequest = exports.ModifyScalingGroupResponse = exports.ModifyScalingGroupResponseBody = exports.ModifyScalingGroupRequest = void 0;
34
- exports.CreateScalingConfigurationShrinkRequestPrivatePoolOptions = exports.CreateScalingConfigurationShrinkRequestImageOptions = exports.CreateScalingConfigurationRequestSpotPriceLimits = exports.CreateScalingConfigurationRequestNetworkInterfaces = exports.CreateScalingConfigurationRequestInstanceTypeOverrides = exports.CreateScalingConfigurationRequestInstancePatternInfos = exports.CreateScalingConfigurationRequestDataDisks = exports.CreateScalingConfigurationRequestCustomPriorities = exports.CreateScalingConfigurationRequestSystemDisk = exports.CreateScalingConfigurationRequestPrivatePoolOptions = exports.CreateScalingConfigurationRequestImageOptions = exports.CreateEciScalingConfigurationRequestVolumes = exports.CreateEciScalingConfigurationRequestVolumesConfigFileVolumeConfigFileToPaths = exports.CreateEciScalingConfigurationRequestVolumesNFSVolume = exports.CreateEciScalingConfigurationRequestVolumesHostPathVolume = exports.CreateEciScalingConfigurationRequestVolumesFlexVolume = exports.CreateEciScalingConfigurationRequestVolumesEmptyDirVolume = exports.CreateEciScalingConfigurationRequestVolumesDiskVolume = exports.CreateEciScalingConfigurationRequestTags = exports.CreateEciScalingConfigurationRequestSecurityContextSysctls = exports.CreateEciScalingConfigurationRequestInitContainers = exports.CreateEciScalingConfigurationRequestInitContainersInitContainerVolumeMounts = exports.CreateEciScalingConfigurationRequestInitContainersInitContainerPorts = exports.CreateEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVars = exports.CreateEciScalingConfigurationRequestInitContainersSecurityContext = exports.CreateEciScalingConfigurationRequestInitContainersSecurityContextCapability = exports.CreateEciScalingConfigurationRequestImageRegistryCredentials = exports.CreateEciScalingConfigurationRequestHostAliases = exports.CreateEciScalingConfigurationRequestDnsConfigOptions = exports.CreateEciScalingConfigurationRequestContainers = exports.CreateEciScalingConfigurationRequestContainersVolumeMounts = exports.CreateEciScalingConfigurationRequestContainersPorts = exports.CreateEciScalingConfigurationRequestContainersEnvironmentVars = exports.CreateEciScalingConfigurationRequestContainersSecurityContext = exports.CreateEciScalingConfigurationRequestContainersSecurityContextCapability = exports.CreateEciScalingConfigurationRequestContainersReadinessProbe = exports.CreateEciScalingConfigurationRequestContainersReadinessProbeTcpSocket = exports.CreateEciScalingConfigurationRequestContainersReadinessProbeHttpGet = exports.CreateEciScalingConfigurationRequestContainersReadinessProbeExec = exports.CreateEciScalingConfigurationRequestContainersLivenessProbe = exports.CreateEciScalingConfigurationRequestContainersLivenessProbeTcpSocket = exports.CreateEciScalingConfigurationRequestContainersLivenessProbeHttpGet = exports.CreateEciScalingConfigurationRequestContainersLivenessProbeExec = exports.CreateEciScalingConfigurationRequestAcrRegistryInfos = exports.CreateAlarmRequestExpressions = exports.CreateAlarmRequestDimensions = exports.AttachVServerGroupsRequestVServerGroups = exports.AttachVServerGroupsRequestVServerGroupsVServerGroupAttributes = exports.AttachServerGroupsRequestServerGroups = exports.AttachLoadBalancersRequestLoadBalancerConfigs = void 0;
35
- exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainers = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainersInitContainerVolumeMounts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainersInitContainerPorts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainersInitContainerEnvironmentVars = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsImageRegistryCredentials = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsHostAliases = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsDnsConfigOptions = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainers = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainersVolumeMounts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainersPorts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainersEnvironmentVars = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsAcrRegistryInfos = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfiguration = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationVolumes = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationVolumesConfigFileVolumeConfigFileToPaths = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationTags = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationSecurityContextSysCtls = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainers = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainersInitContainerVolumeMounts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainersInitContainerPorts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainersInitContainerEnvironmentVars = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationImageRegistryCredentials = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationHostAliases = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationDnsConfigOptions = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainers = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainersVolumeMounts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainersPorts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainersEnvironmentVars = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationAcrRegistryInfos = exports.DescribeAlarmsResponseBodyAlarmList = exports.DescribeAlarmsResponseBodyAlarmListExpressions = exports.DescribeAlarmsResponseBodyAlarmListDimensions = exports.CreateScalingRuleRequestStepAdjustments = exports.CreateScalingRuleRequestAlarmDimensions = exports.CreateScalingGroupRequestVServerGroups = exports.CreateScalingGroupRequestVServerGroupsVServerGroupAttributes = exports.CreateScalingGroupRequestTags = exports.CreateScalingGroupRequestServerGroups = exports.CreateScalingGroupRequestLoadBalancerConfigs = exports.CreateScalingGroupRequestLifecycleHooks = exports.CreateScalingGroupRequestLaunchTemplateOverrides = exports.CreateScalingGroupRequestDBInstances = exports.CreateScalingGroupRequestAlbServerGroups = exports.CreateScalingConfigurationShrinkRequestSpotPriceLimits = exports.CreateScalingConfigurationShrinkRequestNetworkInterfaces = exports.CreateScalingConfigurationShrinkRequestInstanceTypeOverrides = exports.CreateScalingConfigurationShrinkRequestInstancePatternInfos = exports.CreateScalingConfigurationShrinkRequestDataDisks = exports.CreateScalingConfigurationShrinkRequestCustomPriorities = exports.CreateScalingConfigurationShrinkRequestSystemDisk = void 0;
36
- exports.ListTagResourcesRequestTags = exports.EnableScalingGroupRequestLaunchTemplateOverrides = exports.DetachVServerGroupsRequestVServerGroups = exports.DetachVServerGroupsRequestVServerGroupsVServerGroupAttributes = exports.DetachServerGroupsRequestServerGroups = exports.DetachAlbServerGroupsRequestAlbServerGroups = exports.DescribeScheduledTasksResponseBodyScheduledTasks = exports.DescribeScalingRulesResponseBodyScalingRules = exports.DescribeScalingRulesResponseBodyScalingRulesStepAdjustments = exports.DescribeScalingRulesResponseBodyScalingRulesAlarms = exports.DescribeScalingRulesResponseBodyScalingRulesAlarmsDimensions = exports.DescribeScalingRulesResponseBodyScalingRulesAlarmDimensions = exports.DescribeScalingInstancesResponseBodyScalingInstances = exports.DescribeScalingGroupsResponseBodyScalingGroups = exports.DescribeScalingGroupsResponseBodyScalingGroupsVServerGroups = exports.DescribeScalingGroupsResponseBodyScalingGroupsVServerGroupsVServerGroupAttributes = exports.DescribeScalingGroupsResponseBodyScalingGroupsTags = exports.DescribeScalingGroupsResponseBodyScalingGroupsServerGroups = exports.DescribeScalingGroupsResponseBodyScalingGroupsLoadBalancerConfigs = exports.DescribeScalingGroupsResponseBodyScalingGroupsLaunchTemplateOverrides = exports.DescribeScalingGroupsResponseBodyScalingGroupsDBInstances = exports.DescribeScalingGroupsResponseBodyScalingGroupsAlbServerGroups = exports.DescribeScalingGroupsRequestTags = exports.DescribeScalingGroupDetailResponseBodyScalingGroup = exports.DescribeScalingGroupDetailResponseBodyScalingGroupVServerGroups = exports.DescribeScalingGroupDetailResponseBodyScalingGroupVServerGroupsVServerGroupAttributes = exports.DescribeScalingGroupDetailResponseBodyScalingGroupTags = exports.DescribeScalingGroupDetailResponseBodyScalingGroupServerGroups = exports.DescribeScalingGroupDetailResponseBodyScalingGroupLoadBalancerConfigs = exports.DescribeScalingGroupDetailResponseBodyScalingGroupLaunchTemplateOverrides = exports.DescribeScalingGroupDetailResponseBodyScalingGroupAlbServerGroups = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurations = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsTags = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsSpotPriceLimits = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsSchedulerOptions = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsNetworkInterfaces = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsInstancePatternInfos = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsDataDisks = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsCustomPriorities = exports.DescribeScalingActivitiesResponseBodyScalingActivities = exports.DescribeScalingActivitiesResponseBodyScalingActivitiesLifecycleHookContext = exports.DescribeRegionsResponseBodyRegions = exports.DescribeNotificationConfigurationsResponseBodyNotificationConfigurationModels = exports.DescribeLifecycleHooksResponseBodyLifecycleHooks = exports.DescribeLifecycleActionsResponseBodyLifecycleActions = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurations = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsVolumes = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsVolumesConfigFileVolumeConfigFileToPaths = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsTags = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsSecurityContextSysCtls = void 0;
37
- exports.ModifyScalingConfigurationShrinkRequestSystemDisk = exports.ModifyScalingConfigurationShrinkRequestPrivatePoolOptions = exports.ModifyScalingConfigurationShrinkRequestImageOptions = exports.ModifyScalingConfigurationRequestSpotPriceLimits = exports.ModifyScalingConfigurationRequestNetworkInterfaces = exports.ModifyScalingConfigurationRequestInstanceTypeOverrides = exports.ModifyScalingConfigurationRequestInstancePatternInfos = exports.ModifyScalingConfigurationRequestDataDisks = exports.ModifyScalingConfigurationRequestCustomPriorities = exports.ModifyScalingConfigurationRequestSystemDisk = exports.ModifyScalingConfigurationRequestPrivatePoolOptions = exports.ModifyScalingConfigurationRequestImageOptions = exports.ModifyEciScalingConfigurationRequestVolumes = exports.ModifyEciScalingConfigurationRequestVolumesConfigFileVolumeConfigFileToPath = exports.ModifyEciScalingConfigurationRequestVolumesNFSVolume = exports.ModifyEciScalingConfigurationRequestVolumesHostPathVolume = exports.ModifyEciScalingConfigurationRequestVolumesFlexVolume = exports.ModifyEciScalingConfigurationRequestVolumesEmptyDirVolume = exports.ModifyEciScalingConfigurationRequestVolumesDiskVolume = exports.ModifyEciScalingConfigurationRequestTags = exports.ModifyEciScalingConfigurationRequestSecurityContextSysCtls = exports.ModifyEciScalingConfigurationRequestInitContainers = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerVolumeMounts = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerPorts = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVars = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVarsFieldRef = exports.ModifyEciScalingConfigurationRequestInitContainersSecurityContext = exports.ModifyEciScalingConfigurationRequestInitContainersSecurityContextCapability = exports.ModifyEciScalingConfigurationRequestImageRegistryCredentials = exports.ModifyEciScalingConfigurationRequestHostAliases = exports.ModifyEciScalingConfigurationRequestDnsConfigOptions = exports.ModifyEciScalingConfigurationRequestContainers = exports.ModifyEciScalingConfigurationRequestContainersVolumeMounts = exports.ModifyEciScalingConfigurationRequestContainersPorts = exports.ModifyEciScalingConfigurationRequestContainersEnvironmentVars = exports.ModifyEciScalingConfigurationRequestContainersEnvironmentVarsFieldRef = exports.ModifyEciScalingConfigurationRequestContainersSecurityContext = exports.ModifyEciScalingConfigurationRequestContainersSecurityContextCapability = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbe = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbeTcpSocket = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbeHttpGet = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbeExec = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbe = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbeTcpSocket = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbeHttpGet = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbeExec = exports.ModifyEciScalingConfigurationRequestAcrRegistryInfos = exports.ModifyAlarmRequestExpressions = exports.ModifyAlarmRequestDimensions = exports.ListTagResourcesResponseBodyTagResources = void 0;
38
- exports.TagResourcesRequestTags = exports.ScaleWithAdjustmentRequestOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverridesEnvironmentVars = exports.ScaleWithAdjustmentRequestLifecycleHookContext = exports.ModifyScalingRuleRequestStepAdjustments = exports.ModifyScalingRuleRequestAlarmDimensions = exports.ModifyScalingGroupRequestLaunchTemplateOverrides = exports.ModifyScalingConfigurationShrinkRequestSpotPriceLimits = exports.ModifyScalingConfigurationShrinkRequestNetworkInterfaces = exports.ModifyScalingConfigurationShrinkRequestInstanceTypeOverrides = exports.ModifyScalingConfigurationShrinkRequestInstancePatternInfos = exports.ModifyScalingConfigurationShrinkRequestDataDisks = exports.ModifyScalingConfigurationShrinkRequestCustomPriorities = void 0;
31
+ exports.DetachServerGroupsResponseBody = exports.DetachServerGroupsRequest = exports.DetachLoadBalancersResponse = exports.DetachLoadBalancersResponseBody = exports.DetachLoadBalancersRequest = exports.DetachInstancesResponse = exports.DetachInstancesResponseBody = exports.DetachInstancesRequest = exports.DetachDBInstancesResponse = exports.DetachDBInstancesResponseBody = exports.DetachDBInstancesRequest = exports.DetachAlbServerGroupsResponse = exports.DetachAlbServerGroupsResponseBody = exports.DetachAlbServerGroupsRequest = exports.DescribeScheduledTasksResponse = exports.DescribeScheduledTasksResponseBody = exports.DescribeScheduledTasksRequest = exports.DescribeScalingRulesResponse = exports.DescribeScalingRulesResponseBody = exports.DescribeScalingRulesRequest = exports.DescribeScalingInstancesResponse = exports.DescribeScalingInstancesResponseBody = exports.DescribeScalingInstancesRequest = exports.DescribeScalingGroupsResponse = exports.DescribeScalingGroupsResponseBody = exports.DescribeScalingGroupsRequest = exports.DescribeScalingGroupDetailResponse = exports.DescribeScalingGroupDetailResponseBody = exports.DescribeScalingGroupDetailRequest = exports.DescribeScalingConfigurationsResponse = exports.DescribeScalingConfigurationsResponseBody = exports.DescribeScalingConfigurationsRequest = exports.DescribeScalingActivityDetailResponse = exports.DescribeScalingActivityDetailResponseBody = exports.DescribeScalingActivityDetailRequest = exports.DescribeScalingActivitiesResponse = exports.DescribeScalingActivitiesResponseBody = exports.DescribeScalingActivitiesRequest = exports.DescribeRegionsResponse = exports.DescribeRegionsResponseBody = exports.DescribeRegionsRequest = exports.DescribePatternTypesResponse = exports.DescribePatternTypesResponseBody = exports.DescribePatternTypesRequest = exports.DescribeNotificationTypesResponse = exports.DescribeNotificationTypesResponseBody = exports.DescribeNotificationTypesRequest = exports.DescribeNotificationConfigurationsResponse = exports.DescribeNotificationConfigurationsResponseBody = exports.DescribeNotificationConfigurationsRequest = void 0;
32
+ exports.ModifyScalingConfigurationRequest = exports.ModifyNotificationConfigurationResponse = exports.ModifyNotificationConfigurationResponseBody = exports.ModifyNotificationConfigurationRequest = exports.ModifyLifecycleHookResponse = exports.ModifyLifecycleHookResponseBody = exports.ModifyLifecycleHookRequest = exports.ModifyInstanceAttributeResponse = exports.ModifyInstanceAttributeResponseBody = exports.ModifyInstanceAttributeRequest = exports.ModifyEciScalingConfigurationResponse = exports.ModifyEciScalingConfigurationResponseBody = exports.ModifyEciScalingConfigurationRequest = exports.ModifyAlarmResponse = exports.ModifyAlarmResponseBody = exports.ModifyAlarmRequest = exports.ListTagValuesResponse = exports.ListTagValuesResponseBody = exports.ListTagValuesRequest = exports.ListTagResourcesResponse = exports.ListTagResourcesResponseBody = exports.ListTagResourcesRequest = exports.ListTagKeysResponse = exports.ListTagKeysResponseBody = exports.ListTagKeysRequest = exports.ExitStandbyResponse = exports.ExitStandbyResponseBody = exports.ExitStandbyRequest = exports.ExecuteScalingRuleResponse = exports.ExecuteScalingRuleResponseBody = exports.ExecuteScalingRuleRequest = exports.EnterStandbyResponse = exports.EnterStandbyResponseBody = exports.EnterStandbyRequest = exports.EnableScalingGroupResponse = exports.EnableScalingGroupResponseBody = exports.EnableScalingGroupRequest = exports.EnableAlarmResponse = exports.EnableAlarmResponseBody = exports.EnableAlarmRequest = exports.DisableScalingGroupResponse = exports.DisableScalingGroupResponseBody = exports.DisableScalingGroupRequest = exports.DisableAlarmResponse = exports.DisableAlarmResponseBody = exports.DisableAlarmRequest = exports.DetachVServerGroupsResponse = exports.DetachVServerGroupsResponseBody = exports.DetachVServerGroupsRequest = exports.DetachServerGroupsResponse = void 0;
33
+ exports.VerifyUserRequest = exports.VerifyAuthenticationResponse = exports.VerifyAuthenticationResponseBody = exports.VerifyAuthenticationRequest = exports.UntagResourcesResponse = exports.UntagResourcesResponseBody = exports.UntagResourcesRequest = exports.TagResourcesResponse = exports.TagResourcesResponseBody = exports.TagResourcesRequest = exports.SuspendProcessesResponse = exports.SuspendProcessesResponseBody = exports.SuspendProcessesRequest = exports.SetInstancesProtectionResponse = exports.SetInstancesProtectionResponseBody = exports.SetInstancesProtectionRequest = exports.SetInstanceHealthResponse = exports.SetInstanceHealthResponseBody = exports.SetInstanceHealthRequest = exports.SetGroupDeletionProtectionResponse = exports.SetGroupDeletionProtectionResponseBody = exports.SetGroupDeletionProtectionRequest = exports.ScaleWithAdjustmentResponse = exports.ScaleWithAdjustmentResponseBody = exports.ScaleWithAdjustmentShrinkRequest = exports.ScaleWithAdjustmentRequest = exports.ResumeProcessesResponse = exports.ResumeProcessesResponseBody = exports.ResumeProcessesRequest = exports.RemoveInstancesResponse = exports.RemoveInstancesResponseBody = exports.RemoveInstancesRequest = exports.RecordLifecycleActionHeartbeatResponse = exports.RecordLifecycleActionHeartbeatResponseBody = exports.RecordLifecycleActionHeartbeatRequest = exports.RebalanceInstancesResponse = exports.RebalanceInstancesResponseBody = exports.RebalanceInstancesRequest = exports.ModifyScheduledTaskResponse = exports.ModifyScheduledTaskResponseBody = exports.ModifyScheduledTaskRequest = exports.ModifyScalingRuleResponse = exports.ModifyScalingRuleResponseBody = exports.ModifyScalingRuleRequest = exports.ModifyScalingGroupResponse = exports.ModifyScalingGroupResponseBody = exports.ModifyScalingGroupRequest = exports.ModifyScalingConfigurationResponse = exports.ModifyScalingConfigurationResponseBody = exports.ModifyScalingConfigurationShrinkRequest = void 0;
34
+ exports.CreateScalingConfigurationRequestNetworkInterfaces = exports.CreateScalingConfigurationRequestInstanceTypeOverrides = exports.CreateScalingConfigurationRequestInstancePatternInfos = exports.CreateScalingConfigurationRequestDataDisks = exports.CreateScalingConfigurationRequestCustomPriorities = exports.CreateScalingConfigurationRequestSystemDisk = exports.CreateScalingConfigurationRequestPrivatePoolOptions = exports.CreateScalingConfigurationRequestImageOptions = exports.CreateEciScalingConfigurationRequestVolumes = exports.CreateEciScalingConfigurationRequestVolumesConfigFileVolumeConfigFileToPaths = exports.CreateEciScalingConfigurationRequestVolumesNFSVolume = exports.CreateEciScalingConfigurationRequestVolumesHostPathVolume = exports.CreateEciScalingConfigurationRequestVolumesFlexVolume = exports.CreateEciScalingConfigurationRequestVolumesEmptyDirVolume = exports.CreateEciScalingConfigurationRequestVolumesDiskVolume = exports.CreateEciScalingConfigurationRequestTags = exports.CreateEciScalingConfigurationRequestSecurityContextSysctls = exports.CreateEciScalingConfigurationRequestInitContainers = exports.CreateEciScalingConfigurationRequestInitContainersInitContainerVolumeMounts = exports.CreateEciScalingConfigurationRequestInitContainersInitContainerPorts = exports.CreateEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVars = exports.CreateEciScalingConfigurationRequestInitContainersSecurityContext = exports.CreateEciScalingConfigurationRequestInitContainersSecurityContextCapability = exports.CreateEciScalingConfigurationRequestImageRegistryCredentials = exports.CreateEciScalingConfigurationRequestHostAliases = exports.CreateEciScalingConfigurationRequestDnsConfigOptions = exports.CreateEciScalingConfigurationRequestContainers = exports.CreateEciScalingConfigurationRequestContainersVolumeMounts = exports.CreateEciScalingConfigurationRequestContainersPorts = exports.CreateEciScalingConfigurationRequestContainersEnvironmentVars = exports.CreateEciScalingConfigurationRequestContainersSecurityContext = exports.CreateEciScalingConfigurationRequestContainersSecurityContextCapability = exports.CreateEciScalingConfigurationRequestContainersReadinessProbe = exports.CreateEciScalingConfigurationRequestContainersReadinessProbeTcpSocket = exports.CreateEciScalingConfigurationRequestContainersReadinessProbeHttpGet = exports.CreateEciScalingConfigurationRequestContainersReadinessProbeExec = exports.CreateEciScalingConfigurationRequestContainersLivenessProbe = exports.CreateEciScalingConfigurationRequestContainersLivenessProbeTcpSocket = exports.CreateEciScalingConfigurationRequestContainersLivenessProbeHttpGet = exports.CreateEciScalingConfigurationRequestContainersLivenessProbeExec = exports.CreateEciScalingConfigurationRequestAcrRegistryInfos = exports.CreateAlarmRequestExpressions = exports.CreateAlarmRequestDimensions = exports.AttachVServerGroupsRequestVServerGroups = exports.AttachVServerGroupsRequestVServerGroupsVServerGroupAttributes = exports.AttachServerGroupsRequestServerGroups = exports.AttachLoadBalancersRequestLoadBalancerConfigs = exports.AttachAlbServerGroupsRequestAlbServerGroups = exports.VerifyUserResponse = exports.VerifyUserResponseBody = void 0;
35
+ exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainersInitContainerEnvironmentVars = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsImageRegistryCredentials = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsHostAliases = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsDnsConfigOptions = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainers = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainersVolumeMounts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainersPorts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsContainersEnvironmentVars = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsAcrRegistryInfos = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfiguration = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationVolumes = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationVolumesConfigFileVolumeConfigFileToPaths = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationTags = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationSecurityContextSysCtls = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainers = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainersInitContainerVolumeMounts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainersInitContainerPorts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationInitContainersInitContainerEnvironmentVars = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationImageRegistryCredentials = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationHostAliases = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationDnsConfigOptions = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainers = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainersVolumeMounts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainersPorts = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationContainersEnvironmentVars = exports.DescribeEciScalingConfigurationDetailResponseBodyScalingConfigurationAcrRegistryInfos = exports.DescribeAlarmsResponseBodyAlarmList = exports.DescribeAlarmsResponseBodyAlarmListExpressions = exports.DescribeAlarmsResponseBodyAlarmListDimensions = exports.CreateScalingRuleRequestStepAdjustments = exports.CreateScalingRuleRequestAlarmDimensions = exports.CreateScalingGroupRequestVServerGroups = exports.CreateScalingGroupRequestVServerGroupsVServerGroupAttributes = exports.CreateScalingGroupRequestTags = exports.CreateScalingGroupRequestServerGroups = exports.CreateScalingGroupRequestLoadBalancerConfigs = exports.CreateScalingGroupRequestLifecycleHooks = exports.CreateScalingGroupRequestLaunchTemplateOverrides = exports.CreateScalingGroupRequestDBInstances = exports.CreateScalingGroupRequestAlbServerGroups = exports.CreateScalingConfigurationShrinkRequestSpotPriceLimits = exports.CreateScalingConfigurationShrinkRequestNetworkInterfaces = exports.CreateScalingConfigurationShrinkRequestInstanceTypeOverrides = exports.CreateScalingConfigurationShrinkRequestInstancePatternInfos = exports.CreateScalingConfigurationShrinkRequestDataDisks = exports.CreateScalingConfigurationShrinkRequestCustomPriorities = exports.CreateScalingConfigurationShrinkRequestSystemDisk = exports.CreateScalingConfigurationShrinkRequestPrivatePoolOptions = exports.CreateScalingConfigurationShrinkRequestImageOptions = exports.CreateScalingConfigurationRequestSpotPriceLimits = void 0;
36
+ exports.DetachServerGroupsRequestServerGroups = exports.DetachAlbServerGroupsRequestAlbServerGroups = exports.DescribeScheduledTasksResponseBodyScheduledTasks = exports.DescribeScalingRulesResponseBodyScalingRules = exports.DescribeScalingRulesResponseBodyScalingRulesStepAdjustments = exports.DescribeScalingRulesResponseBodyScalingRulesAlarms = exports.DescribeScalingRulesResponseBodyScalingRulesAlarmsDimensions = exports.DescribeScalingRulesResponseBodyScalingRulesAlarmDimensions = exports.DescribeScalingInstancesResponseBodyScalingInstances = exports.DescribeScalingGroupsResponseBodyScalingGroups = exports.DescribeScalingGroupsResponseBodyScalingGroupsVServerGroups = exports.DescribeScalingGroupsResponseBodyScalingGroupsVServerGroupsVServerGroupAttributes = exports.DescribeScalingGroupsResponseBodyScalingGroupsTags = exports.DescribeScalingGroupsResponseBodyScalingGroupsServerGroups = exports.DescribeScalingGroupsResponseBodyScalingGroupsLoadBalancerConfigs = exports.DescribeScalingGroupsResponseBodyScalingGroupsLaunchTemplateOverrides = exports.DescribeScalingGroupsResponseBodyScalingGroupsDBInstances = exports.DescribeScalingGroupsResponseBodyScalingGroupsAlbServerGroups = exports.DescribeScalingGroupsRequestTags = exports.DescribeScalingGroupDetailResponseBodyScalingGroup = exports.DescribeScalingGroupDetailResponseBodyScalingGroupVServerGroups = exports.DescribeScalingGroupDetailResponseBodyScalingGroupVServerGroupsVServerGroupAttributes = exports.DescribeScalingGroupDetailResponseBodyScalingGroupTags = exports.DescribeScalingGroupDetailResponseBodyScalingGroupServerGroups = exports.DescribeScalingGroupDetailResponseBodyScalingGroupLoadBalancerConfigs = exports.DescribeScalingGroupDetailResponseBodyScalingGroupLaunchTemplateOverrides = exports.DescribeScalingGroupDetailResponseBodyScalingGroupAlbServerGroups = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurations = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsTags = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsSpotPriceLimits = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsSchedulerOptions = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsNetworkInterfaces = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsInstancePatternInfos = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsDataDisks = exports.DescribeScalingConfigurationsResponseBodyScalingConfigurationsCustomPriorities = exports.DescribeScalingActivitiesResponseBodyScalingActivities = exports.DescribeScalingActivitiesResponseBodyScalingActivitiesLifecycleHookContext = exports.DescribeRegionsResponseBodyRegions = exports.DescribePatternTypesResponseBodyPatternTypes = exports.DescribeNotificationConfigurationsResponseBodyNotificationConfigurationModels = exports.DescribeLifecycleHooksResponseBodyLifecycleHooks = exports.DescribeLifecycleActionsResponseBodyLifecycleActions = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurations = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsVolumes = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsVolumesConfigFileVolumeConfigFileToPaths = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsTags = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsSecurityContextSysCtls = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainers = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainersInitContainerVolumeMounts = exports.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsInitContainersInitContainerPorts = void 0;
37
+ exports.ModifyScalingConfigurationRequestNetworkInterfaces = exports.ModifyScalingConfigurationRequestInstanceTypeOverrides = exports.ModifyScalingConfigurationRequestInstancePatternInfos = exports.ModifyScalingConfigurationRequestDataDisks = exports.ModifyScalingConfigurationRequestCustomPriorities = exports.ModifyScalingConfigurationRequestSystemDisk = exports.ModifyScalingConfigurationRequestPrivatePoolOptions = exports.ModifyScalingConfigurationRequestImageOptions = exports.ModifyEciScalingConfigurationRequestVolumes = exports.ModifyEciScalingConfigurationRequestVolumesConfigFileVolumeConfigFileToPath = exports.ModifyEciScalingConfigurationRequestVolumesNFSVolume = exports.ModifyEciScalingConfigurationRequestVolumesHostPathVolume = exports.ModifyEciScalingConfigurationRequestVolumesFlexVolume = exports.ModifyEciScalingConfigurationRequestVolumesEmptyDirVolume = exports.ModifyEciScalingConfigurationRequestVolumesDiskVolume = exports.ModifyEciScalingConfigurationRequestTags = exports.ModifyEciScalingConfigurationRequestSecurityContextSysCtls = exports.ModifyEciScalingConfigurationRequestInitContainers = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerVolumeMounts = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerPorts = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVars = exports.ModifyEciScalingConfigurationRequestInitContainersInitContainerEnvironmentVarsFieldRef = exports.ModifyEciScalingConfigurationRequestInitContainersSecurityContext = exports.ModifyEciScalingConfigurationRequestInitContainersSecurityContextCapability = exports.ModifyEciScalingConfigurationRequestImageRegistryCredentials = exports.ModifyEciScalingConfigurationRequestHostAliases = exports.ModifyEciScalingConfigurationRequestDnsConfigOptions = exports.ModifyEciScalingConfigurationRequestContainers = exports.ModifyEciScalingConfigurationRequestContainersVolumeMounts = exports.ModifyEciScalingConfigurationRequestContainersPorts = exports.ModifyEciScalingConfigurationRequestContainersEnvironmentVars = exports.ModifyEciScalingConfigurationRequestContainersEnvironmentVarsFieldRef = exports.ModifyEciScalingConfigurationRequestContainersSecurityContext = exports.ModifyEciScalingConfigurationRequestContainersSecurityContextCapability = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbe = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbeTcpSocket = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbeHttpGet = exports.ModifyEciScalingConfigurationRequestContainersReadinessProbeExec = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbe = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbeTcpSocket = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbeHttpGet = exports.ModifyEciScalingConfigurationRequestContainersLivenessProbeExec = exports.ModifyEciScalingConfigurationRequestAcrRegistryInfos = exports.ModifyAlarmRequestExpressions = exports.ModifyAlarmRequestDimensions = exports.ListTagResourcesResponseBodyTagResources = exports.ListTagResourcesRequestTags = exports.EnableScalingGroupRequestLaunchTemplateOverrides = exports.DetachVServerGroupsRequestVServerGroups = exports.DetachVServerGroupsRequestVServerGroupsVServerGroupAttributes = void 0;
38
+ exports.TagResourcesRequestTags = exports.ScaleWithAdjustmentRequestOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverrides = exports.ScaleWithAdjustmentRequestOverridesContainerOverridesEnvironmentVars = exports.ScaleWithAdjustmentRequestLifecycleHookContext = exports.ModifyScalingRuleRequestStepAdjustments = exports.ModifyScalingRuleRequestAlarmDimensions = exports.ModifyScalingGroupRequestLaunchTemplateOverrides = exports.ModifyScalingConfigurationShrinkRequestSpotPriceLimits = exports.ModifyScalingConfigurationShrinkRequestNetworkInterfaces = exports.ModifyScalingConfigurationShrinkRequestInstanceTypeOverrides = exports.ModifyScalingConfigurationShrinkRequestInstancePatternInfos = exports.ModifyScalingConfigurationShrinkRequestDataDisks = exports.ModifyScalingConfigurationShrinkRequestCustomPriorities = exports.ModifyScalingConfigurationShrinkRequestSystemDisk = exports.ModifyScalingConfigurationShrinkRequestPrivatePoolOptions = exports.ModifyScalingConfigurationShrinkRequestImageOptions = exports.ModifyScalingConfigurationRequestSpotPriceLimits = void 0;
39
39
  // This file is auto-generated, don't edit it
40
40
  /**
41
41
  *
@@ -2805,6 +2805,84 @@ class DescribeNotificationTypesResponse extends $tea.Model {
2805
2805
  }
2806
2806
  }
2807
2807
  exports.DescribeNotificationTypesResponse = DescribeNotificationTypesResponse;
2808
+ class DescribePatternTypesRequest extends $tea.Model {
2809
+ static names() {
2810
+ return {
2811
+ architecture: 'Architecture',
2812
+ burstablePerformance: 'BurstablePerformance',
2813
+ channelId: 'ChannelId',
2814
+ cores: 'Cores',
2815
+ coresList: 'CoresList',
2816
+ excludedInstanceType: 'ExcludedInstanceType',
2817
+ instanceFamilyLevel: 'InstanceFamilyLevel',
2818
+ maxPrice: 'MaxPrice',
2819
+ memory: 'Memory',
2820
+ memoryList: 'MemoryList',
2821
+ regionId: 'RegionId',
2822
+ spotStrategy: 'SpotStrategy',
2823
+ vSwitchId: 'VSwitchId',
2824
+ };
2825
+ }
2826
+ static types() {
2827
+ return {
2828
+ architecture: { 'type': 'array', 'itemType': 'string' },
2829
+ burstablePerformance: 'string',
2830
+ channelId: 'number',
2831
+ cores: 'number',
2832
+ coresList: { 'type': 'array', 'itemType': 'number' },
2833
+ excludedInstanceType: { 'type': 'array', 'itemType': 'string' },
2834
+ instanceFamilyLevel: 'string',
2835
+ maxPrice: 'number',
2836
+ memory: 'number',
2837
+ memoryList: { 'type': 'array', 'itemType': 'number' },
2838
+ regionId: 'string',
2839
+ spotStrategy: 'string',
2840
+ vSwitchId: { 'type': 'array', 'itemType': 'string' },
2841
+ };
2842
+ }
2843
+ constructor(map) {
2844
+ super(map);
2845
+ }
2846
+ }
2847
+ exports.DescribePatternTypesRequest = DescribePatternTypesRequest;
2848
+ class DescribePatternTypesResponseBody extends $tea.Model {
2849
+ static names() {
2850
+ return {
2851
+ patternTypes: 'PatternTypes',
2852
+ requestId: 'RequestId',
2853
+ };
2854
+ }
2855
+ static types() {
2856
+ return {
2857
+ patternTypes: { 'type': 'array', 'itemType': DescribePatternTypesResponseBodyPatternTypes },
2858
+ requestId: 'string',
2859
+ };
2860
+ }
2861
+ constructor(map) {
2862
+ super(map);
2863
+ }
2864
+ }
2865
+ exports.DescribePatternTypesResponseBody = DescribePatternTypesResponseBody;
2866
+ class DescribePatternTypesResponse extends $tea.Model {
2867
+ static names() {
2868
+ return {
2869
+ headers: 'headers',
2870
+ statusCode: 'statusCode',
2871
+ body: 'body',
2872
+ };
2873
+ }
2874
+ static types() {
2875
+ return {
2876
+ headers: { 'type': 'map', 'keyType': 'string', 'valueType': 'string' },
2877
+ statusCode: 'number',
2878
+ body: DescribePatternTypesResponseBody,
2879
+ };
2880
+ }
2881
+ constructor(map) {
2882
+ super(map);
2883
+ }
2884
+ }
2885
+ exports.DescribePatternTypesResponse = DescribePatternTypesResponse;
2808
2886
  class DescribeRegionsRequest extends $tea.Model {
2809
2887
  static names() {
2810
2888
  return {
@@ -9291,6 +9369,30 @@ class DescribeNotificationConfigurationsResponseBodyNotificationConfigurationMod
9291
9369
  }
9292
9370
  }
9293
9371
  exports.DescribeNotificationConfigurationsResponseBodyNotificationConfigurationModels = DescribeNotificationConfigurationsResponseBodyNotificationConfigurationModels;
9372
+ class DescribePatternTypesResponseBodyPatternTypes extends $tea.Model {
9373
+ static names() {
9374
+ return {
9375
+ cores: 'Cores',
9376
+ instanceFamilyLevel: 'InstanceFamilyLevel',
9377
+ instanceType: 'InstanceType',
9378
+ instanceTypeFamily: 'InstanceTypeFamily',
9379
+ memory: 'Memory',
9380
+ };
9381
+ }
9382
+ static types() {
9383
+ return {
9384
+ cores: 'number',
9385
+ instanceFamilyLevel: 'string',
9386
+ instanceType: 'string',
9387
+ instanceTypeFamily: 'string',
9388
+ memory: 'number',
9389
+ };
9390
+ }
9391
+ constructor(map) {
9392
+ super(map);
9393
+ }
9394
+ }
9395
+ exports.DescribePatternTypesResponseBodyPatternTypes = DescribePatternTypesResponseBodyPatternTypes;
9294
9396
  class DescribeRegionsResponseBodyRegions extends $tea.Model {
9295
9397
  static names() {
9296
9398
  return {
@@ -12143,6 +12245,16 @@ class Client extends openapi_client_1.default {
12143
12245
  }
12144
12246
  return endpoint_util_1.default.getEndpointRules(productId, regionId, endpointRule, network, suffix);
12145
12247
  }
12248
+ /**
12249
+ * @summary Manages scaling configurations of the Elastic Container Instance type. If you want to efficiently create or update a scaling configuration of the Elastic Container Instance type by using a configuration file, you can call the ApplyEciScalingConfiguration operation.
12250
+ *
12251
+ * @description You can manage scaling configurations of the Elastic Container Instance type by using a YAML configuration file based on the following logic:
12252
+ * If you specify the ID of a scaling configuration, you can update the scaling configuration by using the YAML configuration file. If you do not specify the ID of a scaling configuration, you can create a scaling configuration by using the YAML configuration file.
12253
+ *
12254
+ * @param request ApplyEciScalingConfigurationRequest
12255
+ * @param runtime runtime options for this request RuntimeOptions
12256
+ * @return ApplyEciScalingConfigurationResponse
12257
+ */
12146
12258
  async applyEciScalingConfigurationWithOptions(request, runtime) {
12147
12259
  tea_util_1.default.validateModel(request);
12148
12260
  let query = {};
@@ -12177,10 +12289,60 @@ class Client extends openapi_client_1.default {
12177
12289
  });
12178
12290
  return $tea.cast(await this.callApi(params, req, runtime), new ApplyEciScalingConfigurationResponse({}));
12179
12291
  }
12292
+ /**
12293
+ * @summary Manages scaling configurations of the Elastic Container Instance type. If you want to efficiently create or update a scaling configuration of the Elastic Container Instance type by using a configuration file, you can call the ApplyEciScalingConfiguration operation.
12294
+ *
12295
+ * @description You can manage scaling configurations of the Elastic Container Instance type by using a YAML configuration file based on the following logic:
12296
+ * If you specify the ID of a scaling configuration, you can update the scaling configuration by using the YAML configuration file. If you do not specify the ID of a scaling configuration, you can create a scaling configuration by using the YAML configuration file.
12297
+ *
12298
+ * @param request ApplyEciScalingConfigurationRequest
12299
+ * @return ApplyEciScalingConfigurationResponse
12300
+ */
12180
12301
  async applyEciScalingConfiguration(request) {
12181
12302
  let runtime = new $Util.RuntimeOptions({});
12182
12303
  return await this.applyEciScalingConfigurationWithOptions(request, runtime);
12183
12304
  }
12305
+ /**
12306
+ * @summary 基于yaml配置进行弹性伸缩管理
12307
+ *
12308
+ * @description You can call the ApplyScalingGroup operation to create scaling groups of the Elastic Container Instance type with ease. The resources of the scaling groups are defined in Kubernetes Deployment YAML files. You can also call this operation to extend annotations for elastic container instances in Kubernetes Deployment YAML files. For more information, see "Supported annotations" in this topic.
12309
+ * Mapping between YAML files and scaling groups: You can map the triplet of namespace, kind, and name in a YAML file to a scaling group name. A YAML file and a scaling group have a one-to-one mapping relationship in a region. For example, if you use the Kubernetes Deployment YAML file whose name is NGINX in the default namespace to create a scaling group in a region, the unique name of the mapped scaling group is k8s_default_Deployment_nginx.
12310
+ * You can use a Kubernetes Deployment YAML file to manage a scaling group based on the following logic:
12311
+ * * If an existing scaling group has a mapping relationship with your Kubernetes Deployment YAML file, you can update the scaling group by using the YAML file.
12312
+ * * If no scaling group that has a mapping relationship with your Kubernetes Deployment YAML file exists, you can create a scaling group with ease by using the YAML file.
12313
+ * ### Precautions
12314
+ * 1. If you do not specify a virtual private cloud (VPC), vSwitch, security group, or annotation in your Kubernetes Deployment YAML file, the system creates a default VPC that has default vSwitches and uses the default security group ess-default-sg of Auto Scaling. By default, the security group rule allows traffic on Transmission Control Protocol (TCP)-based port 22 and port 3389 and enables Internet Control Message Protocol (ICMP) for IPv4 addresses. If you want to enable other ports or protocols, you can create custom security group rules.
12315
+ * 2. If you want to use a public image, you must enable the Internet access feature and configure the k8s.aliyun.com/eci-with-eip pod annotation to enable the elastic IP address (EIP) feature.
12316
+ * 3. After you call the ApplyScalingGroup operation to apply a Kubernetes Deployment YAML file, the scaling group immediately enters the Enabled state and the scaling configuration immediately enters the Active state. If the number of replicas that you specified in the YAML file is grater than 0, elastic container instances are automatically created.
12317
+ * ### Supported annotations
12318
+ * For more information about annotations, see [ECI Pod Annotation](https://help.aliyun.com/document_detail/186939.html).
12319
+ * |Annotation|Example|Description|
12320
+ * |---|---|---|
12321
+ * |k8s.aliyun.com/ess-scaling-group-min-size|1|The minimum size of the scaling group that you want to create. Default value: 0.|
12322
+ * |k8s.aliyun.com/ess-scaling-group-max-size|20|The maximum size of the scaling group that you want to create. Default value: maximum number of replicas or 30, whichever is greater.|
12323
+ * |k8s.aliyun.com/eci-ntp-server|100.100.*.*|The IP address of the Network Time Protocol (NTP) server.|
12324
+ * |k8s.aliyun.com/eci-use-specs|2-4Gi|The specifications of 2 vCPUs and 4 GB memory. For more information, see [Create pods by specifying multiple specifications](https://help.aliyun.com/document_detail/451267.html).|
12325
+ * |k8s.aliyun.com/eci-vswitch|vsw-bp1xpiowfm5vo8o3c\\*\\*\\*\\*|The ID of the vSwitch. You can specify multiple vSwitches to specify multiple zones.|
12326
+ * |k8s.aliyun.com/eci-security-group|sg-bp1dktddjsg5nktv\\*\\*\\*\\*|The ID of the security group. Before you configure this annotation, take note of the following requirements:<ul data-sourcepos="26:74-26:168"><li data-sourcepos="26:78-26:114">You can specify one or more security groups. You can specify up to five security groups for each scaling group.</li><li data-sourcepos="26:114-26:140">If you specify multiple security groups, the security groups must belong to the same VPC.</li><li data-sourcepos="26:140-26:163">If you specify multiple security groups, the security groups must be of the same type.</li></ul>|
12327
+ * |k8s.aliyun.com/eci-sls-enable|"false"|If you set the value to false, the log collection feature is disabled.
12328
+ * If you do not want to use Custom Resource Definition (CRD) for Simple Log Service to collect logs of specific pods, you can configure this annotation for the pods and set the value to false. This prevents resource wastes caused by Logtails created by the system.|
12329
+ * |k8s.aliyun.com/eci-spot-strategy|SpotAsPriceGo|The bidding policy for the preemptible instance. Valid values:<ul data-sourcepos="28:69-28:204"><li data-sourcepos="28:73-28:158">SpotWithPriceLimit: The instance is created as a preemptible instance for which you specify the maximum hourly price If you set the value to SpotWithPriceLimit, you must configure the k8s.aliyun.com/eci-spot-price-limit annotation.</li><li data-sourcepos="28:158-28:199">SpotAsPriceGo: The instance is a preemptible instance for which the market price at the time of purchase is used as the bid price.</li></ul>|
12330
+ * |k8s.aliyun.com/eci-spot-price-limit|"0.5"|The maximum hourly price of the preemptible instance. This value can be accurate to up to three decimal places.
12331
+ * This annotation takes effect only when you set the k8s.aliyun.com/eci-spot-strategy annotation to SpotWithPriceLimit.|
12332
+ * |k8s.aliyun.com/eci-with-eip|"true"|If you set the value to true, an EIP is automatically created and bound to each elastic container instance.|
12333
+ * |k8s.aliyun.com/eci-data-cache-bucket|default|The bucket of the specified DataCache. If you want to use a DataCache to create a pod, you must configure this annotation.|
12334
+ * |k8s.aliyun.com/eci-data-cache-pl|PL1|The performance level (PL) of the cloud disk that you want to create by using the specified DataCache.
12335
+ * By default, enhanced SSDs (ESSDs) are created. Default value: PL1.|
12336
+ * |k8s.aliyun.com/eci-data-cache-provisionedIops|"40000"|The provisioned read/write IOPS of the ESSD AutoPL disk. Valid values: 0 to min{50000, 1000 × Capacity - Baseline IOPS}. Baseline IOPS = min{1,800 + 50 × Capacity, 50,000}. For more information, see [ESSD AutoPL](https://help.aliyun.com/document_detail/368372.html).
12337
+ * If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
12338
+ * |k8s.aliyun.com/eci-data-cache-burstingEnabled|"true"|Specifies whether the Burst feature is enabled for the ESSD AutoPL disk. For more information, see [ESSD AutoPL](https://help.aliyun.com/document_detail/368372.html).
12339
+ * If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
12340
+ * |k8s.aliyun.com/eci-custom-tags|"env:test,name:alice"|The tags that you want to add to each elastic container instance. You can add up to three tags for each elastic container instance. Separate a tag key and a tag value with a colon (:). Separate multiple tags with commas (,).|
12341
+ *
12342
+ * @param request ApplyScalingGroupRequest
12343
+ * @param runtime runtime options for this request RuntimeOptions
12344
+ * @return ApplyScalingGroupResponse
12345
+ */
12184
12346
  async applyScalingGroupWithOptions(request, runtime) {
12185
12347
  tea_util_1.default.validateModel(request);
12186
12348
  let query = {};
@@ -12209,19 +12371,61 @@ class Client extends openapi_client_1.default {
12209
12371
  });
12210
12372
  return $tea.cast(await this.callApi(params, req, runtime), new ApplyScalingGroupResponse({}));
12211
12373
  }
12374
+ /**
12375
+ * @summary 基于yaml配置进行弹性伸缩管理
12376
+ *
12377
+ * @description You can call the ApplyScalingGroup operation to create scaling groups of the Elastic Container Instance type with ease. The resources of the scaling groups are defined in Kubernetes Deployment YAML files. You can also call this operation to extend annotations for elastic container instances in Kubernetes Deployment YAML files. For more information, see "Supported annotations" in this topic.
12378
+ * Mapping between YAML files and scaling groups: You can map the triplet of namespace, kind, and name in a YAML file to a scaling group name. A YAML file and a scaling group have a one-to-one mapping relationship in a region. For example, if you use the Kubernetes Deployment YAML file whose name is NGINX in the default namespace to create a scaling group in a region, the unique name of the mapped scaling group is k8s_default_Deployment_nginx.
12379
+ * You can use a Kubernetes Deployment YAML file to manage a scaling group based on the following logic:
12380
+ * * If an existing scaling group has a mapping relationship with your Kubernetes Deployment YAML file, you can update the scaling group by using the YAML file.
12381
+ * * If no scaling group that has a mapping relationship with your Kubernetes Deployment YAML file exists, you can create a scaling group with ease by using the YAML file.
12382
+ * ### Precautions
12383
+ * 1. If you do not specify a virtual private cloud (VPC), vSwitch, security group, or annotation in your Kubernetes Deployment YAML file, the system creates a default VPC that has default vSwitches and uses the default security group ess-default-sg of Auto Scaling. By default, the security group rule allows traffic on Transmission Control Protocol (TCP)-based port 22 and port 3389 and enables Internet Control Message Protocol (ICMP) for IPv4 addresses. If you want to enable other ports or protocols, you can create custom security group rules.
12384
+ * 2. If you want to use a public image, you must enable the Internet access feature and configure the k8s.aliyun.com/eci-with-eip pod annotation to enable the elastic IP address (EIP) feature.
12385
+ * 3. After you call the ApplyScalingGroup operation to apply a Kubernetes Deployment YAML file, the scaling group immediately enters the Enabled state and the scaling configuration immediately enters the Active state. If the number of replicas that you specified in the YAML file is grater than 0, elastic container instances are automatically created.
12386
+ * ### Supported annotations
12387
+ * For more information about annotations, see [ECI Pod Annotation](https://help.aliyun.com/document_detail/186939.html).
12388
+ * |Annotation|Example|Description|
12389
+ * |---|---|---|
12390
+ * |k8s.aliyun.com/ess-scaling-group-min-size|1|The minimum size of the scaling group that you want to create. Default value: 0.|
12391
+ * |k8s.aliyun.com/ess-scaling-group-max-size|20|The maximum size of the scaling group that you want to create. Default value: maximum number of replicas or 30, whichever is greater.|
12392
+ * |k8s.aliyun.com/eci-ntp-server|100.100.*.*|The IP address of the Network Time Protocol (NTP) server.|
12393
+ * |k8s.aliyun.com/eci-use-specs|2-4Gi|The specifications of 2 vCPUs and 4 GB memory. For more information, see [Create pods by specifying multiple specifications](https://help.aliyun.com/document_detail/451267.html).|
12394
+ * |k8s.aliyun.com/eci-vswitch|vsw-bp1xpiowfm5vo8o3c\\*\\*\\*\\*|The ID of the vSwitch. You can specify multiple vSwitches to specify multiple zones.|
12395
+ * |k8s.aliyun.com/eci-security-group|sg-bp1dktddjsg5nktv\\*\\*\\*\\*|The ID of the security group. Before you configure this annotation, take note of the following requirements:<ul data-sourcepos="26:74-26:168"><li data-sourcepos="26:78-26:114">You can specify one or more security groups. You can specify up to five security groups for each scaling group.</li><li data-sourcepos="26:114-26:140">If you specify multiple security groups, the security groups must belong to the same VPC.</li><li data-sourcepos="26:140-26:163">If you specify multiple security groups, the security groups must be of the same type.</li></ul>|
12396
+ * |k8s.aliyun.com/eci-sls-enable|"false"|If you set the value to false, the log collection feature is disabled.
12397
+ * If you do not want to use Custom Resource Definition (CRD) for Simple Log Service to collect logs of specific pods, you can configure this annotation for the pods and set the value to false. This prevents resource wastes caused by Logtails created by the system.|
12398
+ * |k8s.aliyun.com/eci-spot-strategy|SpotAsPriceGo|The bidding policy for the preemptible instance. Valid values:<ul data-sourcepos="28:69-28:204"><li data-sourcepos="28:73-28:158">SpotWithPriceLimit: The instance is created as a preemptible instance for which you specify the maximum hourly price If you set the value to SpotWithPriceLimit, you must configure the k8s.aliyun.com/eci-spot-price-limit annotation.</li><li data-sourcepos="28:158-28:199">SpotAsPriceGo: The instance is a preemptible instance for which the market price at the time of purchase is used as the bid price.</li></ul>|
12399
+ * |k8s.aliyun.com/eci-spot-price-limit|"0.5"|The maximum hourly price of the preemptible instance. This value can be accurate to up to three decimal places.
12400
+ * This annotation takes effect only when you set the k8s.aliyun.com/eci-spot-strategy annotation to SpotWithPriceLimit.|
12401
+ * |k8s.aliyun.com/eci-with-eip|"true"|If you set the value to true, an EIP is automatically created and bound to each elastic container instance.|
12402
+ * |k8s.aliyun.com/eci-data-cache-bucket|default|The bucket of the specified DataCache. If you want to use a DataCache to create a pod, you must configure this annotation.|
12403
+ * |k8s.aliyun.com/eci-data-cache-pl|PL1|The performance level (PL) of the cloud disk that you want to create by using the specified DataCache.
12404
+ * By default, enhanced SSDs (ESSDs) are created. Default value: PL1.|
12405
+ * |k8s.aliyun.com/eci-data-cache-provisionedIops|"40000"|The provisioned read/write IOPS of the ESSD AutoPL disk. Valid values: 0 to min{50000, 1000 × Capacity - Baseline IOPS}. Baseline IOPS = min{1,800 + 50 × Capacity, 50,000}. For more information, see [ESSD AutoPL](https://help.aliyun.com/document_detail/368372.html).
12406
+ * If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
12407
+ * |k8s.aliyun.com/eci-data-cache-burstingEnabled|"true"|Specifies whether the Burst feature is enabled for the ESSD AutoPL disk. For more information, see [ESSD AutoPL](https://help.aliyun.com/document_detail/368372.html).
12408
+ * If you configure this annotation, the cloud disk that is created by using the specified DataCache is of the ESSD AutoPL type.|
12409
+ * |k8s.aliyun.com/eci-custom-tags|"env:test,name:alice"|The tags that you want to add to each elastic container instance. You can add up to three tags for each elastic container instance. Separate a tag key and a tag value with a colon (:). Separate multiple tags with commas (,).|
12410
+ *
12411
+ * @param request ApplyScalingGroupRequest
12412
+ * @return ApplyScalingGroupResponse
12413
+ */
12212
12414
  async applyScalingGroup(request) {
12213
12415
  let runtime = new $Util.RuntimeOptions({});
12214
12416
  return await this.applyScalingGroupWithOptions(request, runtime);
12215
12417
  }
12216
12418
  /**
12217
- * Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
12218
- * * The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
12219
- * * The ALB server group is in the Available state.
12220
- * * You can associate only a limited number of ALB server groups with a scaling group. To view the quota or manually request a quota increase, go to [Quota Center](https://quotas.console.aliyun.com/products/ess/quotas).
12221
- *
12222
- * @param request AttachAlbServerGroupsRequest
12223
- * @param runtime runtime options for this request RuntimeOptions
12224
- * @return AttachAlbServerGroupsResponse
12419
+ * @summary Associates Application Load Balancer (ALB) server groups with a scaling group.
12420
+ *
12421
+ * @description Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
12422
+ * * The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
12423
+ * * The ALB server group is in the Available state.
12424
+ * * You can associate only a limited number of ALB server groups with a scaling group. To view the quota or manually request a quota increase, go to [Quota Center](https://quotas.console.aliyun.com/products/ess/quotas).
12425
+ *
12426
+ * @param request AttachAlbServerGroupsRequest
12427
+ * @param runtime runtime options for this request RuntimeOptions
12428
+ * @return AttachAlbServerGroupsResponse
12225
12429
  */
12226
12430
  async attachAlbServerGroupsWithOptions(request, runtime) {
12227
12431
  tea_util_1.default.validateModel(request);
@@ -12264,28 +12468,32 @@ class Client extends openapi_client_1.default {
12264
12468
  return $tea.cast(await this.callApi(params, req, runtime), new AttachAlbServerGroupsResponse({}));
12265
12469
  }
12266
12470
  /**
12267
- * Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
12268
- * * The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
12269
- * * The ALB server group is in the Available state.
12270
- * * You can associate only a limited number of ALB server groups with a scaling group. To view the quota or manually request a quota increase, go to [Quota Center](https://quotas.console.aliyun.com/products/ess/quotas).
12271
- *
12272
- * @param request AttachAlbServerGroupsRequest
12273
- * @return AttachAlbServerGroupsResponse
12471
+ * @summary Associates Application Load Balancer (ALB) server groups with a scaling group.
12472
+ *
12473
+ * @description Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
12474
+ * * The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
12475
+ * * The ALB server group is in the Available state.
12476
+ * * You can associate only a limited number of ALB server groups with a scaling group. To view the quota or manually request a quota increase, go to [Quota Center](https://quotas.console.aliyun.com/products/ess/quotas).
12477
+ *
12478
+ * @param request AttachAlbServerGroupsRequest
12479
+ * @return AttachAlbServerGroupsResponse
12274
12480
  */
12275
12481
  async attachAlbServerGroups(request) {
12276
12482
  let runtime = new $Util.RuntimeOptions({});
12277
12483
  return await this.attachAlbServerGroupsWithOptions(request, runtime);
12278
12484
  }
12279
12485
  /**
12280
- * Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
12281
- * * The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
12282
- * * The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](~~41872~~).
12283
- * * The ApsaraDB RDS instance must be in the Running state.
12284
- * After an ApsaraDB RDS instance is associated with the scaling group, the default IP address whitelist of the ApsaraDB RDS instance can contain no more than 1,000 IP addresses. For more information, see [Set the whitelist](~~43185~~).
12285
- *
12286
- * @param request AttachDBInstancesRequest
12287
- * @param runtime runtime options for this request RuntimeOptions
12288
- * @return AttachDBInstancesResponse
12486
+ * @summary Associates one or more ApsaraDB RDS instances with a scaling group.
12487
+ *
12488
+ * @description Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
12489
+ * * The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
12490
+ * * The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](https://help.aliyun.com/document_detail/41872.html).
12491
+ * * The ApsaraDB RDS instance must be in the Running state.
12492
+ * After an ApsaraDB RDS instance is associated with the scaling group, the default IP address whitelist of the ApsaraDB RDS instance can contain no more than 1,000 IP addresses. For more information, see [Set the whitelist](https://help.aliyun.com/document_detail/43185.html).
12493
+ *
12494
+ * @param request AttachDBInstancesRequest
12495
+ * @param runtime runtime options for this request RuntimeOptions
12496
+ * @return AttachDBInstancesResponse
12289
12497
  */
12290
12498
  async attachDBInstancesWithOptions(request, runtime) {
12291
12499
  tea_util_1.default.validateModel(request);
@@ -12334,38 +12542,42 @@ class Client extends openapi_client_1.default {
12334
12542
  return $tea.cast(await this.callApi(params, req, runtime), new AttachDBInstancesResponse({}));
12335
12543
  }
12336
12544
  /**
12337
- * Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
12338
- * * The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
12339
- * * The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](~~41872~~).
12340
- * * The ApsaraDB RDS instance must be in the Running state.
12341
- * After an ApsaraDB RDS instance is associated with the scaling group, the default IP address whitelist of the ApsaraDB RDS instance can contain no more than 1,000 IP addresses. For more information, see [Set the whitelist](~~43185~~).
12342
- *
12343
- * @param request AttachDBInstancesRequest
12344
- * @return AttachDBInstancesResponse
12545
+ * @summary Associates one or more ApsaraDB RDS instances with a scaling group.
12546
+ *
12547
+ * @description Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
12548
+ * * The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
12549
+ * * The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](https://help.aliyun.com/document_detail/41872.html).
12550
+ * * The ApsaraDB RDS instance must be in the Running state.
12551
+ * After an ApsaraDB RDS instance is associated with the scaling group, the default IP address whitelist of the ApsaraDB RDS instance can contain no more than 1,000 IP addresses. For more information, see [Set the whitelist](https://help.aliyun.com/document_detail/43185.html).
12552
+ *
12553
+ * @param request AttachDBInstancesRequest
12554
+ * @return AttachDBInstancesResponse
12345
12555
  */
12346
12556
  async attachDBInstances(request) {
12347
12557
  let runtime = new $Util.RuntimeOptions({});
12348
12558
  return await this.attachDBInstancesWithOptions(request, runtime);
12349
12559
  }
12350
12560
  /**
12351
- * Before you call this operation, take note of the following items:
12352
- * * The scaling group is in the Active state.
12353
- * * No scaling activities in the scaling group are in progress.
12354
- * The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
12355
- * * The instances reside in the same region as the scaling group.
12356
- * * The instances must be in the Running state.
12357
- * * The instances are not added to other scaling groups.
12358
- * * The instances use the subscription or pay-as-you-go billing method, or are preemptible instances.
12359
- * * If the VswitchID parameter is specified for a scaling group, the instances that are in the classic network or those that are not in the same virtual private cloud (VPC) as the specified vSwitch cannot be added to the scaling group.
12360
- * * If the VswitchID parameter is not specified for a scaling group, the instances that are in VPCs cannot be added to the scaling group.
12361
- * If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
12362
- * 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.
12363
- * If the sum of the number of instances that you want to add and the number of existing instances in the scaling group is greater than the value of the MaxSize parameter, the call fails.
12364
- * Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
12365
- *
12366
- * @param request AttachInstancesRequest
12367
- * @param runtime runtime options for this request RuntimeOptions
12368
- * @return AttachInstancesResponse
12561
+ * @summary Adds instances to a scaling group. You can call the AttachInstances operation to add independent Elastic Compute Service (ECS) instances, elastic container instances, or non-Alibaba Cloud instances to your scaling group to provide services. You can also call this operation to change the state of ECS instances in your scaling group from Economical Mode to In Service.
12562
+ *
12563
+ * @description Before you call this operation, take note of the following items:
12564
+ * * The scaling group is in the Active state.
12565
+ * * No scaling activities in the scaling group are in progress.
12566
+ * The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
12567
+ * * The instances reside in the same region as the scaling group.
12568
+ * * The instances must be in the Running state.
12569
+ * * The instances are not added to other scaling groups.
12570
+ * * The instances use the subscription or pay-as-you-go billing method, or are preemptible instances.
12571
+ * * If the VswitchID parameter is specified for a scaling group, the instances that are in the classic network or those that are not in the same virtual private cloud (VPC) as the specified vSwitch cannot be added to the scaling group.
12572
+ * * If the VswitchID parameter is not specified for a scaling group, the instances that are in VPCs cannot be added to the scaling group.
12573
+ * If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
12574
+ * 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.
12575
+ * If the sum of the number of instances that you want to add and the number of existing instances in the scaling group is greater than the value of the MaxSize parameter, the call fails.
12576
+ * Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
12577
+ *
12578
+ * @param request AttachInstancesRequest
12579
+ * @param runtime runtime options for this request RuntimeOptions
12580
+ * @return AttachInstancesResponse
12369
12581
  */
12370
12582
  async attachInstancesWithOptions(request, runtime) {
12371
12583
  tea_util_1.default.validateModel(request);
@@ -12420,41 +12632,44 @@ class Client extends openapi_client_1.default {
12420
12632
  return $tea.cast(await this.callApi(params, req, runtime), new AttachInstancesResponse({}));
12421
12633
  }
12422
12634
  /**
12423
- * Before you call this operation, take note of the following items:
12424
- * * The scaling group is in the Active state.
12425
- * * No scaling activities in the scaling group are in progress.
12426
- * The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
12427
- * * The instances reside in the same region as the scaling group.
12428
- * * The instances must be in the Running state.
12429
- * * The instances are not added to other scaling groups.
12430
- * * The instances use the subscription or pay-as-you-go billing method, or are preemptible instances.
12431
- * * If the VswitchID parameter is specified for a scaling group, the instances that are in the classic network or those that are not in the same virtual private cloud (VPC) as the specified vSwitch cannot be added to the scaling group.
12432
- * * If the VswitchID parameter is not specified for a scaling group, the instances that are in VPCs cannot be added to the scaling group.
12433
- * If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
12434
- * 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.
12435
- * If the sum of the number of instances that you want to add and the number of existing instances in the scaling group is greater than the value of the MaxSize parameter, the call fails.
12436
- * Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
12437
- *
12438
- * @param request AttachInstancesRequest
12439
- * @return AttachInstancesResponse
12635
+ * @summary Adds instances to a scaling group. You can call the AttachInstances operation to add independent Elastic Compute Service (ECS) instances, elastic container instances, or non-Alibaba Cloud instances to your scaling group to provide services. You can also call this operation to change the state of ECS instances in your scaling group from Economical Mode to In Service.
12636
+ *
12637
+ * @description Before you call this operation, take note of the following items:
12638
+ * * The scaling group is in the Active state.
12639
+ * * No scaling activities in the scaling group are in progress.
12640
+ * The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
12641
+ * * The instances reside in the same region as the scaling group.
12642
+ * * The instances must be in the Running state.
12643
+ * * The instances are not added to other scaling groups.
12644
+ * * The instances use the subscription or pay-as-you-go billing method, or are preemptible instances.
12645
+ * * If the VswitchID parameter is specified for a scaling group, the instances that are in the classic network or those that are not in the same virtual private cloud (VPC) as the specified vSwitch cannot be added to the scaling group.
12646
+ * * If the VswitchID parameter is not specified for a scaling group, the instances that are in VPCs cannot be added to the scaling group.
12647
+ * If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
12648
+ * 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.
12649
+ * If the sum of the number of instances that you want to add and the number of existing instances in the scaling group is greater than the value of the MaxSize parameter, the call fails.
12650
+ * Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
12651
+ *
12652
+ * @param request AttachInstancesRequest
12653
+ * @return AttachInstancesResponse
12440
12654
  */
12441
12655
  async attachInstances(request) {
12442
12656
  let runtime = new $Util.RuntimeOptions({});
12443
12657
  return await this.attachInstancesWithOptions(request, runtime);
12444
12658
  }
12445
12659
  /**
12446
- * Before you call this operation to attach a CLB instance to your scaling group, take note of the following items:
12447
- * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12448
- * * The CLB instance and the scaling group must reside in the same region.
12449
- * * The CLB instance must be in the Running state.
12450
- * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12451
- * * The CLB instance and the scaling group must be in the same virtual private cloud (VPC) if their network type is VPC.
12452
- * * If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the CLB backend server groups contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
12453
- * * You can attach only a limited number of CLB instances to a scaling group. Fore more information, see [Limits](~~25863~~).
12454
- *
12455
- * @param request AttachLoadBalancersRequest
12456
- * @param runtime runtime options for this request RuntimeOptions
12457
- * @return AttachLoadBalancersResponse
12660
+ * @summary Attaches load balancers to a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups. Load balancers help distribute the access traffic to the instances in scaling groups, which effectively improves the service performance of the scaling groups. You can call the AttachLoadBalancers operation to attach one or more load balancers to your scaling group.
12661
+ *
12662
+ * @description Before you call this operation, make sure that the following requirements are met:
12663
+ * * The load balancer and the scaling group belong to the same Alibaba Cloud account and region.
12664
+ * * The load balancer is in the `Running` state.
12665
+ * * At least one listener is configured for the load balancer, and the health check feature is enabled for the load balancer.
12666
+ * * If the network type of the load balancer and the scaling group is virtual private cloud (VPC), they use the same VPC.
12667
+ * * If the network type of the scaling group is VPC, and that of the load balancer is classic network and a backend server of the load balancer uses a VPC, the scaling group and the backend server use the same VPC.
12668
+ * * The attachment of load balancers ensures that the cumulative number of load balancers attached to the scaling group stays within the predefined maximum limit. For information about the load balancer quota, see [Limits](https://help.aliyun.com/document_detail/25863.html).
12669
+ *
12670
+ * @param request AttachLoadBalancersRequest
12671
+ * @param runtime runtime options for this request RuntimeOptions
12672
+ * @return AttachLoadBalancersResponse
12458
12673
  */
12459
12674
  async attachLoadBalancersWithOptions(request, runtime) {
12460
12675
  tea_util_1.default.validateModel(request);
@@ -12500,22 +12715,30 @@ class Client extends openapi_client_1.default {
12500
12715
  return $tea.cast(await this.callApi(params, req, runtime), new AttachLoadBalancersResponse({}));
12501
12716
  }
12502
12717
  /**
12503
- * Before you call this operation to attach a CLB instance to your scaling group, take note of the following items:
12504
- * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12505
- * * The CLB instance and the scaling group must reside in the same region.
12506
- * * The CLB instance must be in the Running state.
12507
- * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12508
- * * The CLB instance and the scaling group must be in the same virtual private cloud (VPC) if their network type is VPC.
12509
- * * If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the CLB backend server groups contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
12510
- * * You can attach only a limited number of CLB instances to a scaling group. Fore more information, see [Limits](~~25863~~).
12511
- *
12512
- * @param request AttachLoadBalancersRequest
12513
- * @return AttachLoadBalancersResponse
12718
+ * @summary Attaches load balancers to a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups. Load balancers help distribute the access traffic to the instances in scaling groups, which effectively improves the service performance of the scaling groups. You can call the AttachLoadBalancers operation to attach one or more load balancers to your scaling group.
12719
+ *
12720
+ * @description Before you call this operation, make sure that the following requirements are met:
12721
+ * * The load balancer and the scaling group belong to the same Alibaba Cloud account and region.
12722
+ * * The load balancer is in the `Running` state.
12723
+ * * At least one listener is configured for the load balancer, and the health check feature is enabled for the load balancer.
12724
+ * * If the network type of the load balancer and the scaling group is virtual private cloud (VPC), they use the same VPC.
12725
+ * * If the network type of the scaling group is VPC, and that of the load balancer is classic network and a backend server of the load balancer uses a VPC, the scaling group and the backend server use the same VPC.
12726
+ * * The attachment of load balancers ensures that the cumulative number of load balancers attached to the scaling group stays within the predefined maximum limit. For information about the load balancer quota, see [Limits](https://help.aliyun.com/document_detail/25863.html).
12727
+ *
12728
+ * @param request AttachLoadBalancersRequest
12729
+ * @return AttachLoadBalancersResponse
12514
12730
  */
12515
12731
  async attachLoadBalancers(request) {
12516
12732
  let runtime = new $Util.RuntimeOptions({});
12517
12733
  return await this.attachLoadBalancersWithOptions(request, runtime);
12518
12734
  }
12735
+ /**
12736
+ * @summary Attaches one or more server groups to a scaling group. You can attach the following server groups to a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
12737
+ *
12738
+ * @param request AttachServerGroupsRequest
12739
+ * @param runtime runtime options for this request RuntimeOptions
12740
+ * @return AttachServerGroupsResponse
12741
+ */
12519
12742
  async attachServerGroupsWithOptions(request, runtime) {
12520
12743
  tea_util_1.default.validateModel(request);
12521
12744
  let query = {};
@@ -12556,29 +12779,37 @@ class Client extends openapi_client_1.default {
12556
12779
  });
12557
12780
  return $tea.cast(await this.callApi(params, req, runtime), new AttachServerGroupsResponse({}));
12558
12781
  }
12782
+ /**
12783
+ * @summary Attaches one or more server groups to a scaling group. You can attach the following server groups to a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
12784
+ *
12785
+ * @param request AttachServerGroupsRequest
12786
+ * @return AttachServerGroupsResponse
12787
+ */
12559
12788
  async attachServerGroups(request) {
12560
12789
  let runtime = new $Util.RuntimeOptions({});
12561
12790
  return await this.attachServerGroupsWithOptions(request, runtime);
12562
12791
  }
12563
12792
  /**
12564
- * Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
12565
- * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12566
- * * The CLB instance and the scaling group must reside in the same region.
12567
- * * The CLB instance must be in the Running state.
12568
- * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12569
- * * The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
12570
- * * If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the vServer groups of the CLB instance contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
12571
- * * The vServer group that you want to attach to your scaling group must belong to the CLB instance.
12572
- * * You can attach only a limited number of vServer groups to a scaling group. For information about the quota on vServer groups, see [Limits](~~25863~~).
12573
- * When you call this operation, you must specify the following parameters:
12574
- * * LoadBalancerId: the ID of the CLB instance.
12575
- * * VServerGroupId: the ID of the vServer group.
12576
- * * Port: the port number of the vServer group.
12577
- * If a vServer group is attached to a scaling group by using different ports, Auto Scaling considers that more than one vServer group is attached to the scaling group. If multiple vServer groups with the same group ID and port number are specified in the request parameters, only the first vServer group is used. The other vServer groups are ignored.
12578
- *
12579
- * @param request AttachVServerGroupsRequest
12580
- * @param runtime runtime options for this request RuntimeOptions
12581
- * @return AttachVServerGroupsResponse
12793
+ * @summary Associates Sever Load Balancer (SLB) vServer groups with a scaling group.
12794
+ *
12795
+ * @description Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
12796
+ * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12797
+ * * The CLB instance and the scaling group must reside in the same region.
12798
+ * * The CLB instance must be in the Running state.
12799
+ * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12800
+ * * The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
12801
+ * * If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the vServer groups of the CLB instance contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
12802
+ * * The vServer group that you want to attach to your scaling group must belong to the CLB instance.
12803
+ * * You can attach only a limited number of vServer groups to a scaling group. For information about the quota on vServer groups, see [Limits](https://help.aliyun.com/document_detail/25863.html).
12804
+ * When you call this operation, you must specify the following parameters:
12805
+ * * LoadBalancerId: the ID of the CLB instance.
12806
+ * * VServerGroupId: the ID of the vServer group.
12807
+ * * Port: the port number of the vServer group.
12808
+ * If a vServer group is attached to a scaling group by using different ports, Auto Scaling considers that more than one vServer group is attached to the scaling group. If multiple vServer groups with the same group ID and port number are specified in the request parameters, only the first vServer group is used. The other vServer groups are ignored.
12809
+ *
12810
+ * @param request AttachVServerGroupsRequest
12811
+ * @param runtime runtime options for this request RuntimeOptions
12812
+ * @return AttachVServerGroupsResponse
12582
12813
  */
12583
12814
  async attachVServerGroupsWithOptions(request, runtime) {
12584
12815
  tea_util_1.default.validateModel(request);
@@ -12621,28 +12852,37 @@ class Client extends openapi_client_1.default {
12621
12852
  return $tea.cast(await this.callApi(params, req, runtime), new AttachVServerGroupsResponse({}));
12622
12853
  }
12623
12854
  /**
12624
- * Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
12625
- * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12626
- * * The CLB instance and the scaling group must reside in the same region.
12627
- * * The CLB instance must be in the Running state.
12628
- * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12629
- * * The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
12630
- * * If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the vServer groups of the CLB instance contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
12631
- * * The vServer group that you want to attach to your scaling group must belong to the CLB instance.
12632
- * * You can attach only a limited number of vServer groups to a scaling group. For information about the quota on vServer groups, see [Limits](~~25863~~).
12633
- * When you call this operation, you must specify the following parameters:
12634
- * * LoadBalancerId: the ID of the CLB instance.
12635
- * * VServerGroupId: the ID of the vServer group.
12636
- * * Port: the port number of the vServer group.
12637
- * If a vServer group is attached to a scaling group by using different ports, Auto Scaling considers that more than one vServer group is attached to the scaling group. If multiple vServer groups with the same group ID and port number are specified in the request parameters, only the first vServer group is used. The other vServer groups are ignored.
12638
- *
12639
- * @param request AttachVServerGroupsRequest
12640
- * @return AttachVServerGroupsResponse
12855
+ * @summary Associates Sever Load Balancer (SLB) vServer groups with a scaling group.
12856
+ *
12857
+ * @description Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
12858
+ * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12859
+ * * The CLB instance and the scaling group must reside in the same region.
12860
+ * * The CLB instance must be in the Running state.
12861
+ * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12862
+ * * The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
12863
+ * * If the network type of the scaling group is VPC, the network type of the CLB instance is classic network, and the vServer groups of the CLB instance contain instances of the VPC network type, the instances and the scaling group must be in the same VPC.
12864
+ * * The vServer group that you want to attach to your scaling group must belong to the CLB instance.
12865
+ * * You can attach only a limited number of vServer groups to a scaling group. For information about the quota on vServer groups, see [Limits](https://help.aliyun.com/document_detail/25863.html).
12866
+ * When you call this operation, you must specify the following parameters:
12867
+ * * LoadBalancerId: the ID of the CLB instance.
12868
+ * * VServerGroupId: the ID of the vServer group.
12869
+ * * Port: the port number of the vServer group.
12870
+ * If a vServer group is attached to a scaling group by using different ports, Auto Scaling considers that more than one vServer group is attached to the scaling group. If multiple vServer groups with the same group ID and port number are specified in the request parameters, only the first vServer group is used. The other vServer groups are ignored.
12871
+ *
12872
+ * @param request AttachVServerGroupsRequest
12873
+ * @return AttachVServerGroupsResponse
12641
12874
  */
12642
12875
  async attachVServerGroups(request) {
12643
12876
  let runtime = new $Util.RuntimeOptions({});
12644
12877
  return await this.attachVServerGroupsWithOptions(request, runtime);
12645
12878
  }
12879
+ /**
12880
+ * @summary Adds a scaling group to a resource group.
12881
+ *
12882
+ * @param request ChangeResourceGroupRequest
12883
+ * @param runtime runtime options for this request RuntimeOptions
12884
+ * @return ChangeResourceGroupResponse
12885
+ */
12646
12886
  async changeResourceGroupWithOptions(request, runtime) {
12647
12887
  tea_util_1.default.validateModel(request);
12648
12888
  let query = {};
@@ -12680,16 +12920,24 @@ class Client extends openapi_client_1.default {
12680
12920
  });
12681
12921
  return $tea.cast(await this.callApi(params, req, runtime), new ChangeResourceGroupResponse({}));
12682
12922
  }
12923
+ /**
12924
+ * @summary Adds a scaling group to a resource group.
12925
+ *
12926
+ * @param request ChangeResourceGroupRequest
12927
+ * @return ChangeResourceGroupResponse
12928
+ */
12683
12929
  async changeResourceGroup(request) {
12684
12930
  let runtime = new $Util.RuntimeOptions({});
12685
12931
  return await this.changeResourceGroupWithOptions(request, runtime);
12686
12932
  }
12687
12933
  /**
12688
- * 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.
12689
- *
12690
- * @param request CompleteLifecycleActionRequest
12691
- * @param runtime runtime options for this request RuntimeOptions
12692
- * @return CompleteLifecycleActionResponse
12934
+ * @summary Ends the timeout period of a lifecycle hook ahead of schedule. If you have created a lifecycle hook for your scaling group, you can call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule based on your business requirements.
12935
+ *
12936
+ * @description When you manually cut short the timeout period of a lifecycle hook, Auto Scaling proceeds with one of the following actions based on the predefined settings: responding to the scaling request, aborting the scaling request, and initiating a rollback process.
12937
+ *
12938
+ * @param request CompleteLifecycleActionRequest
12939
+ * @param runtime runtime options for this request RuntimeOptions
12940
+ * @return CompleteLifecycleActionResponse
12693
12941
  */
12694
12942
  async completeLifecycleActionWithOptions(request, runtime) {
12695
12943
  tea_util_1.default.validateModel(request);
@@ -12735,15 +12983,30 @@ class Client extends openapi_client_1.default {
12735
12983
  return $tea.cast(await this.callApi(params, req, runtime), new CompleteLifecycleActionResponse({}));
12736
12984
  }
12737
12985
  /**
12738
- * 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.
12739
- *
12740
- * @param request CompleteLifecycleActionRequest
12741
- * @return CompleteLifecycleActionResponse
12986
+ * @summary Ends the timeout period of a lifecycle hook ahead of schedule. If you have created a lifecycle hook for your scaling group, you can call the CompleteLifecycleAction operation to end the timeout period of the lifecycle hook ahead of schedule based on your business requirements.
12987
+ *
12988
+ * @description When you manually cut short the timeout period of a lifecycle hook, Auto Scaling proceeds with one of the following actions based on the predefined settings: responding to the scaling request, aborting the scaling request, and initiating a rollback process.
12989
+ *
12990
+ * @param request CompleteLifecycleActionRequest
12991
+ * @return CompleteLifecycleActionResponse
12742
12992
  */
12743
12993
  async completeLifecycleAction(request) {
12744
12994
  let runtime = new $Util.RuntimeOptions({});
12745
12995
  return await this.completeLifecycleActionWithOptions(request, runtime);
12746
12996
  }
12997
+ /**
12998
+ * @summary Creates an event-triggered task.
12999
+ *
13000
+ * @description * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
13001
+ * * 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.
13002
+ * * If you set the MetricType parameter to custom, the valid values are your custom metrics.
13003
+ * * For information about the supported metrics when you set the MetricType parameter to system, see [Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
13004
+ * > 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.
13005
+ *
13006
+ * @param request CreateAlarmRequest
13007
+ * @param runtime runtime options for this request RuntimeOptions
13008
+ * @return CreateAlarmResponse
13009
+ */
12747
13010
  async createAlarmWithOptions(request, runtime) {
12748
13011
  tea_util_1.default.validateModel(request);
12749
13012
  let query = {};
@@ -12820,17 +13083,31 @@ class Client extends openapi_client_1.default {
12820
13083
  });
12821
13084
  return $tea.cast(await this.callApi(params, req, runtime), new CreateAlarmResponse({}));
12822
13085
  }
13086
+ /**
13087
+ * @summary Creates an event-triggered task.
13088
+ *
13089
+ * @description * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
13090
+ * * 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.
13091
+ * * If you set the MetricType parameter to custom, the valid values are your custom metrics.
13092
+ * * For information about the supported metrics when you set the MetricType parameter to system, see [Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
13093
+ * > 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.
13094
+ *
13095
+ * @param request CreateAlarmRequest
13096
+ * @return CreateAlarmResponse
13097
+ */
12823
13098
  async createAlarm(request) {
12824
13099
  let runtime = new $Util.RuntimeOptions({});
12825
13100
  return await this.createAlarmWithOptions(request, runtime);
12826
13101
  }
12827
13102
  /**
12828
- * A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
12829
- * You can specify the Cpu and Memory parameters to determine the range of instance types. If you specify the parameters, Auto Scaling determines the available instance types based on factors such as I/O optimization requirements and zones. Auto Scaling preferentially creates elastic container instances of the instance type that is provided at the lowest price. This scaling mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
12830
- *
12831
- * @param request CreateEciScalingConfigurationRequest
12832
- * @param runtime runtime options for this request RuntimeOptions
12833
- * @return CreateEciScalingConfigurationResponse
13103
+ * @summary Creates a scaling configuration of the Elastic Container Instance type. Auto Scaling uses the scaling configuration as a template to create elastic container instances to meet your business requirements during scale-outs.
13104
+ *
13105
+ * @description A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
13106
+ * You can specify the Cpu and Memory parameters to determine the range of instance types. If you specify the parameters, Auto Scaling determines the available instance types based on factors such as I/O optimization requirements and zones. Auto Scaling preferentially creates elastic container instances of the instance type that is provided at the lowest price. This scaling mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
13107
+ *
13108
+ * @param request CreateEciScalingConfigurationRequest
13109
+ * @param runtime runtime options for this request RuntimeOptions
13110
+ * @return CreateEciScalingConfigurationResponse
12834
13111
  */
12835
13112
  async createEciScalingConfigurationWithOptions(request, runtime) {
12836
13113
  tea_util_1.default.validateModel(request);
@@ -12999,25 +13276,29 @@ class Client extends openapi_client_1.default {
12999
13276
  return $tea.cast(await this.callApi(params, req, runtime), new CreateEciScalingConfigurationResponse({}));
13000
13277
  }
13001
13278
  /**
13002
- * A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
13003
- * You can specify the Cpu and Memory parameters to determine the range of instance types. If you specify the parameters, Auto Scaling determines the available instance types based on factors such as I/O optimization requirements and zones. Auto Scaling preferentially creates elastic container instances of the instance type that is provided at the lowest price. This scaling mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
13004
- *
13005
- * @param request CreateEciScalingConfigurationRequest
13006
- * @return CreateEciScalingConfigurationResponse
13279
+ * @summary Creates a scaling configuration of the Elastic Container Instance type. Auto Scaling uses the scaling configuration as a template to create elastic container instances to meet your business requirements during scale-outs.
13280
+ *
13281
+ * @description A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
13282
+ * You can specify the Cpu and Memory parameters to determine the range of instance types. If you specify the parameters, Auto Scaling determines the available instance types based on factors such as I/O optimization requirements and zones. Auto Scaling preferentially creates elastic container instances of the instance type that is provided at the lowest price. This scaling mode is available only if Scaling Policy is set to Cost Optimization Policy and no instance type is specified in the scaling configuration.
13283
+ *
13284
+ * @param request CreateEciScalingConfigurationRequest
13285
+ * @return CreateEciScalingConfigurationResponse
13007
13286
  */
13008
13287
  async createEciScalingConfiguration(request) {
13009
13288
  let runtime = new $Util.RuntimeOptions({});
13010
13289
  return await this.createEciScalingConfigurationWithOptions(request, runtime);
13011
13290
  }
13012
13291
  /**
13013
- * 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.
13014
- * 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.
13015
- * 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~~).
13016
- * > 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.
13017
- *
13018
- * @param request CreateLifecycleHookRequest
13019
- * @param runtime runtime options for this request RuntimeOptions
13020
- * @return CreateLifecycleHookResponse
13292
+ * @summary Creates one or more lifecycle hooks.
13293
+ *
13294
+ * @description You can create up to six lifecycle hooks for each scaling group. After a lifecycle hook is created for a scaling group, Elastic Compute Service (ECS) instances in the scaling group waits to be added to or removed from the scaling group during scaling activities. You can use the HeartbeatTimeout parameter to specify the timeout period of the lifecycle hook. During the timeout period of a lifecycle hook, you can perform custom operations such as initialize ECS instance configurations and download ECS instance data on the ECS instances for which the lifecycle hook is applied.
13295
+ * 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.
13296
+ * You can configure a notification method for a lifecycle hook. When the lifecycle hook is triggered, a notification can be sent to the specified Message Service (MNS) topic or queue, or an operation can be performed based on the specified Operation Orchestration Service (OOS) template. If you want to configure an OOS template, you must create a Resource Access Management (RAM) role for OOS. For more information, see [Grant RAM permissions to OOS](https://help.aliyun.com/document_detail/120810.html).
13297
+ * > 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.
13298
+ *
13299
+ * @param request CreateLifecycleHookRequest
13300
+ * @param runtime runtime options for this request RuntimeOptions
13301
+ * @return CreateLifecycleHookResponse
13021
13302
  */
13022
13303
  async createLifecycleHookWithOptions(request, runtime) {
13023
13304
  tea_util_1.default.validateModel(request);
@@ -13069,25 +13350,29 @@ class Client extends openapi_client_1.default {
13069
13350
  return $tea.cast(await this.callApi(params, req, runtime), new CreateLifecycleHookResponse({}));
13070
13351
  }
13071
13352
  /**
13072
- * 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.
13073
- * 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.
13074
- * 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~~).
13075
- * > 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.
13076
- *
13077
- * @param request CreateLifecycleHookRequest
13078
- * @return CreateLifecycleHookResponse
13353
+ * @summary Creates one or more lifecycle hooks.
13354
+ *
13355
+ * @description You can create up to six lifecycle hooks for each scaling group. After a lifecycle hook is created for a scaling group, Elastic Compute Service (ECS) instances in the scaling group waits to be added to or removed from the scaling group during scaling activities. You can use the HeartbeatTimeout parameter to specify the timeout period of the lifecycle hook. During the timeout period of a lifecycle hook, you can perform custom operations such as initialize ECS instance configurations and download ECS instance data on the ECS instances for which the lifecycle hook is applied.
13356
+ * 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.
13357
+ * You can configure a notification method for a lifecycle hook. When the lifecycle hook is triggered, a notification can be sent to the specified Message Service (MNS) topic or queue, or an operation can be performed based on the specified Operation Orchestration Service (OOS) template. If you want to configure an OOS template, you must create a Resource Access Management (RAM) role for OOS. For more information, see [Grant RAM permissions to OOS](https://help.aliyun.com/document_detail/120810.html).
13358
+ * > 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.
13359
+ *
13360
+ * @param request CreateLifecycleHookRequest
13361
+ * @return CreateLifecycleHookResponse
13079
13362
  */
13080
13363
  async createLifecycleHook(request) {
13081
13364
  let runtime = new $Util.RuntimeOptions({});
13082
13365
  return await this.createLifecycleHookWithOptions(request, runtime);
13083
13366
  }
13084
13367
  /**
13085
- * ## Description
13086
- * You can configure CloudMonitor system events, Message Service (MNS) queues, or MNS topics to receive notifications. When a specified type of scaling activity or resource change occurs in a scaling group, Auto Scaling sends notifications by using CloudMonitor or MNS.
13087
- *
13088
- * @param request CreateNotificationConfigurationRequest
13089
- * @param runtime runtime options for this request RuntimeOptions
13090
- * @return CreateNotificationConfigurationResponse
13368
+ * @summary Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
13369
+ *
13370
+ * @description ## Description
13371
+ * You can configure CloudMonitor system events, Message Service (MNS) queues, or MNS topics to receive notifications. When a specified type of scaling activity or resource change occurs in a scaling group, Auto Scaling sends notifications by using CloudMonitor or MNS.
13372
+ *
13373
+ * @param request CreateNotificationConfigurationRequest
13374
+ * @param runtime runtime options for this request RuntimeOptions
13375
+ * @return CreateNotificationConfigurationResponse
13091
13376
  */
13092
13377
  async createNotificationConfigurationWithOptions(request, runtime) {
13093
13378
  tea_util_1.default.validateModel(request);
@@ -13127,28 +13412,32 @@ class Client extends openapi_client_1.default {
13127
13412
  return $tea.cast(await this.callApi(params, req, runtime), new CreateNotificationConfigurationResponse({}));
13128
13413
  }
13129
13414
  /**
13130
- * ## Description
13131
- * You can configure CloudMonitor system events, Message Service (MNS) queues, or MNS topics to receive notifications. When a specified type of scaling activity or resource change occurs in a scaling group, Auto Scaling sends notifications by using CloudMonitor or MNS.
13132
- *
13133
- * @param request CreateNotificationConfigurationRequest
13134
- * @return CreateNotificationConfigurationResponse
13415
+ * @summary Creates a notification rule. You can call the CreateNotificationConfiguration operation to create a notification rule to stay informed about scaling events or resource changes. This helps you learn about the dynamic status of your scaling group in real time and further automates the management of scaling events.
13416
+ *
13417
+ * @description ## Description
13418
+ * You can configure CloudMonitor system events, Message Service (MNS) queues, or MNS topics to receive notifications. When a specified type of scaling activity or resource change occurs in a scaling group, Auto Scaling sends notifications by using CloudMonitor or MNS.
13419
+ *
13420
+ * @param request CreateNotificationConfigurationRequest
13421
+ * @return CreateNotificationConfigurationResponse
13135
13422
  */
13136
13423
  async createNotificationConfiguration(request) {
13137
13424
  let runtime = new $Util.RuntimeOptions({});
13138
13425
  return await this.createNotificationConfigurationWithOptions(request, runtime);
13139
13426
  }
13140
13427
  /**
13141
- * Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
13142
- * * 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.
13143
- * * InstanceType: In this mode, you must specify one instance type.
13144
- * * InstanceTypes: In this mode, you can specify more than one instance type.
13145
- * * InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
13146
- * * 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.
13147
- * > 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.
13148
- *
13149
- * @param tmpReq CreateScalingConfigurationRequest
13150
- * @param runtime runtime options for this request RuntimeOptions
13151
- * @return CreateScalingConfigurationResponse
13428
+ * @summary Creates a scaling configuration.
13429
+ *
13430
+ * @description Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
13431
+ * * 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.
13432
+ * * InstanceType: In this mode, you must specify one instance type.
13433
+ * * InstanceTypes: In this mode, you can specify more than one instance type.
13434
+ * * InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
13435
+ * * 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.
13436
+ * > 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.
13437
+ *
13438
+ * @param tmpReq CreateScalingConfigurationRequest
13439
+ * @param runtime runtime options for this request RuntimeOptions
13440
+ * @return CreateScalingConfigurationResponse
13152
13441
  */
13153
13442
  async createScalingConfigurationWithOptions(tmpReq, runtime) {
13154
13443
  tea_util_1.default.validateModel(tmpReq);
@@ -13346,48 +13635,52 @@ class Client extends openapi_client_1.default {
13346
13635
  return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingConfigurationResponse({}));
13347
13636
  }
13348
13637
  /**
13349
- * Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
13350
- * * 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.
13351
- * * InstanceType: In this mode, you must specify one instance type.
13352
- * * InstanceTypes: In this mode, you can specify more than one instance type.
13353
- * * InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
13354
- * * 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.
13355
- * > 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.
13356
- *
13357
- * @param request CreateScalingConfigurationRequest
13358
- * @return CreateScalingConfigurationResponse
13638
+ * @summary Creates a scaling configuration.
13639
+ *
13640
+ * @description Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
13641
+ * * 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.
13642
+ * * InstanceType: In this mode, you must specify one instance type.
13643
+ * * InstanceTypes: In this mode, you can specify more than one instance type.
13644
+ * * InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
13645
+ * * 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.
13646
+ * > 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.
13647
+ *
13648
+ * @param request CreateScalingConfigurationRequest
13649
+ * @return CreateScalingConfigurationResponse
13359
13650
  */
13360
13651
  async createScalingConfiguration(request) {
13361
13652
  let runtime = new $Util.RuntimeOptions({});
13362
13653
  return await this.createScalingConfigurationWithOptions(request, runtime);
13363
13654
  }
13364
13655
  /**
13365
- * A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
13366
- * 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.
13367
- * 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.
13368
- * 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](~~40654~~) topic.
13369
- * 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:
13370
- * * 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.
13371
- * * 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.
13372
- * > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
13373
- * 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:
13374
- * * The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
13375
- * * 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.
13376
- * 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.
13377
- * 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:
13378
- * * 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.
13379
- * * 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.
13380
- * If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
13381
- * * 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.
13382
- * * 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.
13383
- * If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules apply:
13384
- * * 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.
13385
- * * 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.
13386
- * * 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.
13387
- *
13388
- * @param request CreateScalingGroupRequest
13389
- * @param runtime runtime options for this request RuntimeOptions
13390
- * @return CreateScalingGroupResponse
13656
+ * @summary Creates a scaling group.
13657
+ *
13658
+ * @description A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
13659
+ * 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.
13660
+ * 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.
13661
+ * 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](https://help.aliyun.com/document_detail/40654.html) topic.
13662
+ * 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:
13663
+ * * 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.
13664
+ * * 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.
13665
+ * > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
13666
+ * 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:
13667
+ * * The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
13668
+ * * 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.
13669
+ * 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.
13670
+ * 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:
13671
+ * * 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.
13672
+ * * 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.
13673
+ * If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
13674
+ * * 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.
13675
+ * * 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.
13676
+ * If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules apply:
13677
+ * * 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.
13678
+ * * 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.
13679
+ * * 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.
13680
+ *
13681
+ * @param request CreateScalingGroupRequest
13682
+ * @param runtime runtime options for this request RuntimeOptions
13683
+ * @return CreateScalingGroupResponse
13391
13684
  */
13392
13685
  async createScalingGroupWithOptions(request, runtime) {
13393
13686
  tea_util_1.default.validateModel(request);
@@ -13544,54 +13837,58 @@ class Client extends openapi_client_1.default {
13544
13837
  return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingGroupResponse({}));
13545
13838
  }
13546
13839
  /**
13547
- * A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
13548
- * 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.
13549
- * 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.
13550
- * 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](~~40654~~) topic.
13551
- * 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:
13552
- * * 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.
13553
- * * 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.
13554
- * > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
13555
- * 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:
13556
- * * The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
13557
- * * 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.
13558
- * 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.
13559
- * 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:
13560
- * * 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.
13561
- * * 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.
13562
- * If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
13563
- * * 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.
13564
- * * 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.
13565
- * If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules apply:
13566
- * * 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.
13567
- * * 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.
13568
- * * 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.
13569
- *
13570
- * @param request CreateScalingGroupRequest
13571
- * @return CreateScalingGroupResponse
13840
+ * @summary Creates a scaling group.
13841
+ *
13842
+ * @description A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
13843
+ * 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.
13844
+ * 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.
13845
+ * 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](https://help.aliyun.com/document_detail/40654.html) topic.
13846
+ * 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:
13847
+ * * 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.
13848
+ * * 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.
13849
+ * > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
13850
+ * 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:
13851
+ * * The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
13852
+ * * 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.
13853
+ * 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.
13854
+ * 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:
13855
+ * * 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.
13856
+ * * 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.
13857
+ * If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
13858
+ * * 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.
13859
+ * * 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.
13860
+ * If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules apply:
13861
+ * * 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.
13862
+ * * 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.
13863
+ * * 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.
13864
+ *
13865
+ * @param request CreateScalingGroupRequest
13866
+ * @return CreateScalingGroupResponse
13572
13867
  */
13573
13868
  async createScalingGroup(request) {
13574
13869
  let runtime = new $Util.RuntimeOptions({});
13575
13870
  return await this.createScalingGroupWithOptions(request, runtime);
13576
13871
  }
13577
13872
  /**
13578
- * ## Description
13579
- * 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 adjusts the number of ECS instances that you want to add or remove. This way, the number of ECS instances can be maintained within the valid range after the scaling rule is executed. The number of ECS instances that is specified in the scaling rule remains unchanged. Example:
13580
- * * 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. The number of ECS instances that is specified in the scaling rule remains unchanged.
13581
- * * 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. The number of ECS instances that is specified in the scaling rule remains unchanged.
13582
- * Before you call this operation, take note of the following items:
13583
- * * If you set the AdjustmentType parameter to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of the AdjustmentValue parameter must be greater than or equal to 0.
13584
- * * If you set the AdjustmentType parameter to QuantityChangeInCapacity or PercentChangeInCapacity, 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.
13585
- * * If you set the AdjustmentType parameter 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.
13586
- * * If the cooldown time is specified in a scaling rule, the specified time applies to the scaling group after the rule is executed. Otherwise, the value of the DefaultCooldown parameter of the scaling group applies to the scaling group.
13587
- * * You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
13588
- * * The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
13589
- * * ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule by setting the ScalingRuleAri parameter to the unique identifier of the scaling rule.
13590
- * * CreateScheduledTask: You can call this operation to create a scheduled task for a specific scaling rule by setting the ScheduledAction parameter to the unique identifier of the scaling rule.
13591
- *
13592
- * @param request CreateScalingRuleRequest
13593
- * @param runtime runtime options for this request RuntimeOptions
13594
- * @return CreateScalingRuleResponse
13873
+ * @summary Creates a scaling rule.
13874
+ *
13875
+ * @description ## Description
13876
+ * 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 adjusts the number of ECS instances that you want to add or remove. This way, the number of ECS instances can be maintained within the valid range after the scaling rule is executed. The number of ECS instances that is specified in the scaling rule remains unchanged. Example:
13877
+ * * 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. The number of ECS instances that is specified in the scaling rule remains unchanged.
13878
+ * * 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. The number of ECS instances that is specified in the scaling rule remains unchanged.
13879
+ * Before you call this operation, take note of the following items:
13880
+ * * If you set the AdjustmentType parameter to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of the AdjustmentValue parameter must be greater than or equal to 0.
13881
+ * * If you set the AdjustmentType parameter to QuantityChangeInCapacity or PercentChangeInCapacity, 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.
13882
+ * * If you set the AdjustmentType parameter 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.
13883
+ * * If the cooldown time is specified in a scaling rule, the specified time applies to the scaling group after the rule is executed. Otherwise, the value of the DefaultCooldown parameter of the scaling group applies to the scaling group.
13884
+ * * You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
13885
+ * * The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
13886
+ * * ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule by setting the ScalingRuleAri parameter to the unique identifier of the scaling rule.
13887
+ * * CreateScheduledTask: You can call this operation to create a scheduled task for a specific scaling rule by setting the ScheduledAction parameter to the unique identifier of the scaling rule.
13888
+ *
13889
+ * @param request CreateScalingRuleRequest
13890
+ * @param runtime runtime options for this request RuntimeOptions
13891
+ * @return CreateScalingRuleResponse
13595
13892
  */
13596
13893
  async createScalingRuleWithOptions(request, runtime) {
13597
13894
  tea_util_1.default.validateModel(request);
@@ -13685,38 +13982,42 @@ class Client extends openapi_client_1.default {
13685
13982
  return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingRuleResponse({}));
13686
13983
  }
13687
13984
  /**
13688
- * ## Description
13689
- * 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 adjusts the number of ECS instances that you want to add or remove. This way, the number of ECS instances can be maintained within the valid range after the scaling rule is executed. The number of ECS instances that is specified in the scaling rule remains unchanged. Example:
13690
- * * 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. The number of ECS instances that is specified in the scaling rule remains unchanged.
13691
- * * 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. The number of ECS instances that is specified in the scaling rule remains unchanged.
13692
- * Before you call this operation, take note of the following items:
13693
- * * If you set the AdjustmentType parameter to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of the AdjustmentValue parameter must be greater than or equal to 0.
13694
- * * If you set the AdjustmentType parameter to QuantityChangeInCapacity or PercentChangeInCapacity, 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.
13695
- * * If you set the AdjustmentType parameter 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.
13696
- * * If the cooldown time is specified in a scaling rule, the specified time applies to the scaling group after the rule is executed. Otherwise, the value of the DefaultCooldown parameter of the scaling group applies to the scaling group.
13697
- * * You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
13698
- * * The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
13699
- * * ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule by setting the ScalingRuleAri parameter to the unique identifier of the scaling rule.
13700
- * * CreateScheduledTask: You can call this operation to create a scheduled task for a specific scaling rule by setting the ScheduledAction parameter to the unique identifier of the scaling rule.
13701
- *
13702
- * @param request CreateScalingRuleRequest
13703
- * @return CreateScalingRuleResponse
13985
+ * @summary Creates a scaling rule.
13986
+ *
13987
+ * @description ## Description
13988
+ * 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 adjusts the number of ECS instances that you want to add or remove. This way, the number of ECS instances can be maintained within the valid range after the scaling rule is executed. The number of ECS instances that is specified in the scaling rule remains unchanged. Example:
13989
+ * * 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. The number of ECS instances that is specified in the scaling rule remains unchanged.
13990
+ * * 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. The number of ECS instances that is specified in the scaling rule remains unchanged.
13991
+ * Before you call this operation, take note of the following items:
13992
+ * * If you set the AdjustmentType parameter to TotalCapacity, the number of ECS instances in the scaling group is adjusted to the specified value. The value of the AdjustmentValue parameter must be greater than or equal to 0.
13993
+ * * If you set the AdjustmentType parameter to QuantityChangeInCapacity or PercentChangeInCapacity, 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.
13994
+ * * If you set the AdjustmentType parameter 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.
13995
+ * * If the cooldown time is specified in a scaling rule, the specified time applies to the scaling group after the rule is executed. Otherwise, the value of the DefaultCooldown parameter of the scaling group applies to the scaling group.
13996
+ * * You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
13997
+ * * The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
13998
+ * * ExecuteScalingRule: You can call this operation to manually execute a specific scaling rule by setting the ScalingRuleAri parameter to the unique identifier of the scaling rule.
13999
+ * * CreateScheduledTask: You can call this operation to create a scheduled task for a specific scaling rule by setting the ScheduledAction parameter to the unique identifier of the scaling rule.
14000
+ *
14001
+ * @param request CreateScalingRuleRequest
14002
+ * @return CreateScalingRuleResponse
13704
14003
  */
13705
14004
  async createScalingRule(request) {
13706
14005
  let runtime = new $Util.RuntimeOptions({});
13707
14006
  return await this.createScalingRuleWithOptions(request, runtime);
13708
14007
  }
13709
14008
  /**
13710
- * * If a scheduled task fails to trigger a scaling activity due to an ongoing scaling activity in a scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the period that is specified by the LaunchExpirationTime parameter. If the scheduled task still fails to trigger a scaling activity after the period ends, the task is automatically skipped.
13711
- * * If multiple tasks are scheduled at similar points in time to trigger scaling activities in the same scaling group, the earliest task triggers the scaling activity first. Other tasks trigger scaling activities within their launch expiration time. Only one scaling activity can be triggered in a scaling group at a time.`` If the previous scaling activity is complete and another scheduled task attempts to trigger a scaling activity, Auto Scaling executes the scaling rule that is specified in the scheduled task and then triggers a scaling activity.``
13712
- * * A scheduled task supports the following scaling methods:
13713
- * * `ScheduledAction`: Specify an existing scaling rule that you want Auto Scaling to execute when the scheduled task is triggered.
13714
- * * `ScalingGroupId`: Specify the minimum number, maximum number, or expected number of instances for the scaling group for which you created the scheduled task.
13715
- * > You cannot specify the `ScheduledAction` and ScalingGroupId parameters at the same time.
13716
- *
13717
- * @param request CreateScheduledTaskRequest
13718
- * @param runtime runtime options for this request RuntimeOptions
13719
- * @return CreateScheduledTaskResponse
14009
+ * @summary Creates a scheduled task. A scheduled task is a type of scaling task that enables automatic execution of a specific scaling rule at a specified point in time. You can call the CreateScheduledTask operation to create a scheduled task to implement automatic scaling of computing resources. This ensures your business continuity and minimizes resource costs.
14010
+ *
14011
+ * @description * If a scheduled task fails to trigger a scaling activity due to an ongoing scaling activity in a scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the period that is specified by the LaunchExpirationTime parameter. If the scheduled task still fails to trigger a scaling activity after the period ends, the task is automatically skipped.
14012
+ * * If multiple tasks are scheduled at similar points in time to trigger scaling activities in the same scaling group, the earliest task triggers the scaling activity first. Other tasks trigger scaling activities within their launch expiration time. Only one scaling activity can be triggered in a scaling group at a time.`` If the previous scaling activity is complete and another scheduled task attempts to trigger a scaling activity, Auto Scaling executes the scaling rule that is specified in the scheduled task and then triggers a scaling activity.``
14013
+ * * A scheduled task supports the following scaling methods:
14014
+ * * `ScheduledAction`: Specify an existing scaling rule that you want Auto Scaling to execute when the scheduled task is triggered.
14015
+ * * `ScalingGroupId`: Specify the minimum number, maximum number, or expected number of instances for the scaling group for which you created the scheduled task.
14016
+ * > You cannot specify the `ScheduledAction` and ScalingGroupId parameters at the same time.
14017
+ *
14018
+ * @param request CreateScheduledTaskRequest
14019
+ * @param runtime runtime options for this request RuntimeOptions
14020
+ * @return CreateScheduledTaskResponse
13720
14021
  */
13721
14022
  async createScheduledTaskWithOptions(request, runtime) {
13722
14023
  tea_util_1.default.validateModel(request);
@@ -13789,20 +14090,31 @@ class Client extends openapi_client_1.default {
13789
14090
  return $tea.cast(await this.callApi(params, req, runtime), new CreateScheduledTaskResponse({}));
13790
14091
  }
13791
14092
  /**
13792
- * * If a scheduled task fails to trigger a scaling activity due to an ongoing scaling activity in a scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the period that is specified by the LaunchExpirationTime parameter. If the scheduled task still fails to trigger a scaling activity after the period ends, the task is automatically skipped.
13793
- * * If multiple tasks are scheduled at similar points in time to trigger scaling activities in the same scaling group, the earliest task triggers the scaling activity first. Other tasks trigger scaling activities within their launch expiration time. Only one scaling activity can be triggered in a scaling group at a time.`` If the previous scaling activity is complete and another scheduled task attempts to trigger a scaling activity, Auto Scaling executes the scaling rule that is specified in the scheduled task and then triggers a scaling activity.``
13794
- * * A scheduled task supports the following scaling methods:
13795
- * * `ScheduledAction`: Specify an existing scaling rule that you want Auto Scaling to execute when the scheduled task is triggered.
13796
- * * `ScalingGroupId`: Specify the minimum number, maximum number, or expected number of instances for the scaling group for which you created the scheduled task.
13797
- * > You cannot specify the `ScheduledAction` and ScalingGroupId parameters at the same time.
13798
- *
13799
- * @param request CreateScheduledTaskRequest
13800
- * @return CreateScheduledTaskResponse
14093
+ * @summary Creates a scheduled task. A scheduled task is a type of scaling task that enables automatic execution of a specific scaling rule at a specified point in time. You can call the CreateScheduledTask operation to create a scheduled task to implement automatic scaling of computing resources. This ensures your business continuity and minimizes resource costs.
14094
+ *
14095
+ * @description * If a scheduled task fails to trigger a scaling activity due to an ongoing scaling activity in a scaling group or because the scaling group is disabled, the scheduled task is automatically retried during the period that is specified by the LaunchExpirationTime parameter. If the scheduled task still fails to trigger a scaling activity after the period ends, the task is automatically skipped.
14096
+ * * If multiple tasks are scheduled at similar points in time to trigger scaling activities in the same scaling group, the earliest task triggers the scaling activity first. Other tasks trigger scaling activities within their launch expiration time. Only one scaling activity can be triggered in a scaling group at a time.`` If the previous scaling activity is complete and another scheduled task attempts to trigger a scaling activity, Auto Scaling executes the scaling rule that is specified in the scheduled task and then triggers a scaling activity.``
14097
+ * * A scheduled task supports the following scaling methods:
14098
+ * * `ScheduledAction`: Specify an existing scaling rule that you want Auto Scaling to execute when the scheduled task is triggered.
14099
+ * * `ScalingGroupId`: Specify the minimum number, maximum number, or expected number of instances for the scaling group for which you created the scheduled task.
14100
+ * > You cannot specify the `ScheduledAction` and ScalingGroupId parameters at the same time.
14101
+ *
14102
+ * @param request CreateScheduledTaskRequest
14103
+ * @return CreateScheduledTaskResponse
13801
14104
  */
13802
14105
  async createScheduledTask(request) {
13803
14106
  let runtime = new $Util.RuntimeOptions({});
13804
14107
  return await this.createScheduledTaskWithOptions(request, runtime);
13805
14108
  }
14109
+ /**
14110
+ * @summary Deactivates a scaling configuration.
14111
+ *
14112
+ * @description * You can call this operation to deactivate a scaling configuration only in a disabled scaling group.
14113
+ *
14114
+ * @param request DeactivateScalingConfigurationRequest
14115
+ * @param runtime runtime options for this request RuntimeOptions
14116
+ * @return DeactivateScalingConfigurationResponse
14117
+ */
13806
14118
  async deactivateScalingConfigurationWithOptions(request, runtime) {
13807
14119
  tea_util_1.default.validateModel(request);
13808
14120
  let query = {};
@@ -13834,10 +14146,25 @@ class Client extends openapi_client_1.default {
13834
14146
  });
13835
14147
  return $tea.cast(await this.callApi(params, req, runtime), new DeactivateScalingConfigurationResponse({}));
13836
14148
  }
14149
+ /**
14150
+ * @summary Deactivates a scaling configuration.
14151
+ *
14152
+ * @description * You can call this operation to deactivate a scaling configuration only in a disabled scaling group.
14153
+ *
14154
+ * @param request DeactivateScalingConfigurationRequest
14155
+ * @return DeactivateScalingConfigurationResponse
14156
+ */
13837
14157
  async deactivateScalingConfiguration(request) {
13838
14158
  let runtime = new $Util.RuntimeOptions({});
13839
14159
  return await this.deactivateScalingConfigurationWithOptions(request, runtime);
13840
14160
  }
14161
+ /**
14162
+ * @summary Deletes an event-triggered task.
14163
+ *
14164
+ * @param request DeleteAlarmRequest
14165
+ * @param runtime runtime options for this request RuntimeOptions
14166
+ * @return DeleteAlarmResponse
14167
+ */
13841
14168
  async deleteAlarmWithOptions(request, runtime) {
13842
14169
  tea_util_1.default.validateModel(request);
13843
14170
  let query = {};
@@ -13869,18 +14196,26 @@ class Client extends openapi_client_1.default {
13869
14196
  });
13870
14197
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteAlarmResponse({}));
13871
14198
  }
14199
+ /**
14200
+ * @summary Deletes an event-triggered task.
14201
+ *
14202
+ * @param request DeleteAlarmRequest
14203
+ * @return DeleteAlarmResponse
14204
+ */
13872
14205
  async deleteAlarm(request) {
13873
14206
  let runtime = new $Util.RuntimeOptions({});
13874
14207
  return await this.deleteAlarmWithOptions(request, runtime);
13875
14208
  }
13876
14209
  /**
13877
- * You cannot delete a scaling configuration that is used to create elastic container instances in the following scenarios:
13878
- * * The scaling configuration is in the Active state.
13879
- * * The scaling group contains elastic container instances that are created based on the scaling configuration.
13880
- *
13881
- * @param request DeleteEciScalingConfigurationRequest
13882
- * @param runtime runtime options for this request RuntimeOptions
13883
- * @return DeleteEciScalingConfigurationResponse
14210
+ * @summary Deletes a scaling configuration that is used to create elastic container instances.
14211
+ *
14212
+ * @description You cannot delete a scaling configuration that is used to create elastic container instances in the following scenarios:
14213
+ * * The scaling configuration is in the Active state.
14214
+ * * The scaling group contains elastic container instances that are created based on the scaling configuration.
14215
+ *
14216
+ * @param request DeleteEciScalingConfigurationRequest
14217
+ * @param runtime runtime options for this request RuntimeOptions
14218
+ * @return DeleteEciScalingConfigurationResponse
13884
14219
  */
13885
14220
  async deleteEciScalingConfigurationWithOptions(request, runtime) {
13886
14221
  tea_util_1.default.validateModel(request);
@@ -13917,17 +14252,30 @@ class Client extends openapi_client_1.default {
13917
14252
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteEciScalingConfigurationResponse({}));
13918
14253
  }
13919
14254
  /**
13920
- * You cannot delete a scaling configuration that is used to create elastic container instances in the following scenarios:
13921
- * * The scaling configuration is in the Active state.
13922
- * * The scaling group contains elastic container instances that are created based on the scaling configuration.
13923
- *
13924
- * @param request DeleteEciScalingConfigurationRequest
13925
- * @return DeleteEciScalingConfigurationResponse
14255
+ * @summary Deletes a scaling configuration that is used to create elastic container instances.
14256
+ *
14257
+ * @description You cannot delete a scaling configuration that is used to create elastic container instances in the following scenarios:
14258
+ * * The scaling configuration is in the Active state.
14259
+ * * The scaling group contains elastic container instances that are created based on the scaling configuration.
14260
+ *
14261
+ * @param request DeleteEciScalingConfigurationRequest
14262
+ * @return DeleteEciScalingConfigurationResponse
13926
14263
  */
13927
14264
  async deleteEciScalingConfiguration(request) {
13928
14265
  let runtime = new $Util.RuntimeOptions({});
13929
14266
  return await this.deleteEciScalingConfigurationWithOptions(request, runtime);
13930
14267
  }
14268
+ /**
14269
+ * @summary Deletes a lifecycle hook.
14270
+ *
14271
+ * @description 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:
14272
+ * * 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.
14273
+ * * Specify the lifecycle hook ID by using the LifecycleHookId parameter. In this case, the ScalingGroupId parameter and the LifecycleHookName parameter are ignored.
14274
+ *
14275
+ * @param request DeleteLifecycleHookRequest
14276
+ * @param runtime runtime options for this request RuntimeOptions
14277
+ * @return DeleteLifecycleHookResponse
14278
+ */
13931
14279
  async deleteLifecycleHookWithOptions(request, runtime) {
13932
14280
  tea_util_1.default.validateModel(request);
13933
14281
  let query = {};
@@ -13968,10 +14316,27 @@ class Client extends openapi_client_1.default {
13968
14316
  });
13969
14317
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteLifecycleHookResponse({}));
13970
14318
  }
14319
+ /**
14320
+ * @summary Deletes a lifecycle hook.
14321
+ *
14322
+ * @description 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:
14323
+ * * 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.
14324
+ * * Specify the lifecycle hook ID by using the LifecycleHookId parameter. In this case, the ScalingGroupId parameter and the LifecycleHookName parameter are ignored.
14325
+ *
14326
+ * @param request DeleteLifecycleHookRequest
14327
+ * @return DeleteLifecycleHookResponse
14328
+ */
13971
14329
  async deleteLifecycleHook(request) {
13972
14330
  let runtime = new $Util.RuntimeOptions({});
13973
14331
  return await this.deleteLifecycleHookWithOptions(request, runtime);
13974
14332
  }
14333
+ /**
14334
+ * @summary Deletes a notification.
14335
+ *
14336
+ * @param request DeleteNotificationConfigurationRequest
14337
+ * @param runtime runtime options for this request RuntimeOptions
14338
+ * @return DeleteNotificationConfigurationResponse
14339
+ */
13975
14340
  async deleteNotificationConfigurationWithOptions(request, runtime) {
13976
14341
  tea_util_1.default.validateModel(request);
13977
14342
  let query = {};
@@ -14006,18 +14371,26 @@ class Client extends openapi_client_1.default {
14006
14371
  });
14007
14372
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteNotificationConfigurationResponse({}));
14008
14373
  }
14374
+ /**
14375
+ * @summary Deletes a notification.
14376
+ *
14377
+ * @param request DeleteNotificationConfigurationRequest
14378
+ * @return DeleteNotificationConfigurationResponse
14379
+ */
14009
14380
  async deleteNotificationConfiguration(request) {
14010
14381
  let runtime = new $Util.RuntimeOptions({});
14011
14382
  return await this.deleteNotificationConfigurationWithOptions(request, runtime);
14012
14383
  }
14013
14384
  /**
14014
- * You cannot delete a scaling configuration in one of the following scenarios:
14015
- * * The scaling configuration in your scaling group is in the Active state.
14016
- * * The scaling group contains ECS instances that were created based on the scaling configuration.
14017
- *
14018
- * @param request DeleteScalingConfigurationRequest
14019
- * @param runtime runtime options for this request RuntimeOptions
14020
- * @return DeleteScalingConfigurationResponse
14385
+ * @summary Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
14386
+ *
14387
+ * @description You cannot delete a scaling configuration in one of the following scenarios:
14388
+ * * The scaling configuration in your scaling group is in the Active state.
14389
+ * * The scaling group contains ECS instances that were created based on the scaling configuration.
14390
+ *
14391
+ * @param request DeleteScalingConfigurationRequest
14392
+ * @param runtime runtime options for this request RuntimeOptions
14393
+ * @return DeleteScalingConfigurationResponse
14021
14394
  */
14022
14395
  async deleteScalingConfigurationWithOptions(request, runtime) {
14023
14396
  tea_util_1.default.validateModel(request);
@@ -14051,17 +14424,30 @@ class Client extends openapi_client_1.default {
14051
14424
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingConfigurationResponse({}));
14052
14425
  }
14053
14426
  /**
14054
- * You cannot delete a scaling configuration in one of the following scenarios:
14055
- * * The scaling configuration in your scaling group is in the Active state.
14056
- * * The scaling group contains ECS instances that were created based on the scaling configuration.
14057
- *
14058
- * @param request DeleteScalingConfigurationRequest
14059
- * @return DeleteScalingConfigurationResponse
14427
+ * @summary Deletes a scaling configuration that is used to create Elastic Compute Service (ECS) instances.
14428
+ *
14429
+ * @description You cannot delete a scaling configuration in one of the following scenarios:
14430
+ * * The scaling configuration in your scaling group is in the Active state.
14431
+ * * The scaling group contains ECS instances that were created based on the scaling configuration.
14432
+ *
14433
+ * @param request DeleteScalingConfigurationRequest
14434
+ * @return DeleteScalingConfigurationResponse
14060
14435
  */
14061
14436
  async deleteScalingConfiguration(request) {
14062
14437
  let runtime = new $Util.RuntimeOptions({});
14063
14438
  return await this.deleteScalingConfigurationWithOptions(request, runtime);
14064
14439
  }
14440
+ /**
14441
+ * @summary Deletes a scaling group.
14442
+ *
14443
+ * @description Before you delete a scaling group, take note of the following items:
14444
+ * * After you delete a scaling group, the scaling configuration, scaling rules, scaling activities, and scaling requests related to the scaling group are also deleted.
14445
+ * * After you delete a scaling group, the scheduled tasks and event-triggered tasks of the scaling group are not deleted. The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances with which the scaling group is associated are also not deleted.
14446
+ *
14447
+ * @param request DeleteScalingGroupRequest
14448
+ * @param runtime runtime options for this request RuntimeOptions
14449
+ * @return DeleteScalingGroupResponse
14450
+ */
14065
14451
  async deleteScalingGroupWithOptions(request, runtime) {
14066
14452
  tea_util_1.default.validateModel(request);
14067
14453
  let query = {};
@@ -14099,10 +14485,27 @@ class Client extends openapi_client_1.default {
14099
14485
  });
14100
14486
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingGroupResponse({}));
14101
14487
  }
14488
+ /**
14489
+ * @summary Deletes a scaling group.
14490
+ *
14491
+ * @description Before you delete a scaling group, take note of the following items:
14492
+ * * After you delete a scaling group, the scaling configuration, scaling rules, scaling activities, and scaling requests related to the scaling group are also deleted.
14493
+ * * After you delete a scaling group, the scheduled tasks and event-triggered tasks of the scaling group are not deleted. The Classic Load Balancer (CLB) instances and ApsaraDB RDS instances with which the scaling group is associated are also not deleted.
14494
+ *
14495
+ * @param request DeleteScalingGroupRequest
14496
+ * @return DeleteScalingGroupResponse
14497
+ */
14102
14498
  async deleteScalingGroup(request) {
14103
14499
  let runtime = new $Util.RuntimeOptions({});
14104
14500
  return await this.deleteScalingGroupWithOptions(request, runtime);
14105
14501
  }
14502
+ /**
14503
+ * @summary Deletes a scaling rule.
14504
+ *
14505
+ * @param request DeleteScalingRuleRequest
14506
+ * @param runtime runtime options for this request RuntimeOptions
14507
+ * @return DeleteScalingRuleResponse
14508
+ */
14106
14509
  async deleteScalingRuleWithOptions(request, runtime) {
14107
14510
  tea_util_1.default.validateModel(request);
14108
14511
  let query = {};
@@ -14137,10 +14540,23 @@ class Client extends openapi_client_1.default {
14137
14540
  });
14138
14541
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingRuleResponse({}));
14139
14542
  }
14543
+ /**
14544
+ * @summary Deletes a scaling rule.
14545
+ *
14546
+ * @param request DeleteScalingRuleRequest
14547
+ * @return DeleteScalingRuleResponse
14548
+ */
14140
14549
  async deleteScalingRule(request) {
14141
14550
  let runtime = new $Util.RuntimeOptions({});
14142
14551
  return await this.deleteScalingRuleWithOptions(request, runtime);
14143
14552
  }
14553
+ /**
14554
+ * @summary Deletes a scheduled task.
14555
+ *
14556
+ * @param request DeleteScheduledTaskRequest
14557
+ * @param runtime runtime options for this request RuntimeOptions
14558
+ * @return DeleteScheduledTaskResponse
14559
+ */
14144
14560
  async deleteScheduledTaskWithOptions(request, runtime) {
14145
14561
  tea_util_1.default.validateModel(request);
14146
14562
  let query = {};
@@ -14175,10 +14591,23 @@ class Client extends openapi_client_1.default {
14175
14591
  });
14176
14592
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteScheduledTaskResponse({}));
14177
14593
  }
14594
+ /**
14595
+ * @summary Deletes a scheduled task.
14596
+ *
14597
+ * @param request DeleteScheduledTaskRequest
14598
+ * @return DeleteScheduledTaskResponse
14599
+ */
14178
14600
  async deleteScheduledTask(request) {
14179
14601
  let runtime = new $Util.RuntimeOptions({});
14180
14602
  return await this.deleteScheduledTaskWithOptions(request, runtime);
14181
14603
  }
14604
+ /**
14605
+ * @summary Queries event-triggered tasks.
14606
+ *
14607
+ * @param request DescribeAlarmsRequest
14608
+ * @param runtime runtime options for this request RuntimeOptions
14609
+ * @return DescribeAlarmsResponse
14610
+ */
14182
14611
  async describeAlarmsWithOptions(request, runtime) {
14183
14612
  tea_util_1.default.validateModel(request);
14184
14613
  let query = {};
@@ -14231,10 +14660,23 @@ class Client extends openapi_client_1.default {
14231
14660
  });
14232
14661
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeAlarmsResponse({}));
14233
14662
  }
14663
+ /**
14664
+ * @summary Queries event-triggered tasks.
14665
+ *
14666
+ * @param request DescribeAlarmsRequest
14667
+ * @return DescribeAlarmsResponse
14668
+ */
14234
14669
  async describeAlarms(request) {
14235
14670
  let runtime = new $Util.RuntimeOptions({});
14236
14671
  return await this.describeAlarmsWithOptions(request, runtime);
14237
14672
  }
14673
+ /**
14674
+ * @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances. If you set OutputFormat to yaml, the output is a Kubernetes Deployment file in the YAML format.
14675
+ *
14676
+ * @param request DescribeEciScalingConfigurationDetailRequest
14677
+ * @param runtime runtime options for this request RuntimeOptions
14678
+ * @return DescribeEciScalingConfigurationDetailResponse
14679
+ */
14238
14680
  async describeEciScalingConfigurationDetailWithOptions(request, runtime) {
14239
14681
  tea_util_1.default.validateModel(request);
14240
14682
  let query = {};
@@ -14266,10 +14708,23 @@ class Client extends openapi_client_1.default {
14266
14708
  });
14267
14709
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationDetailResponse({}));
14268
14710
  }
14711
+ /**
14712
+ * @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances. If you set OutputFormat to yaml, the output is a Kubernetes Deployment file in the YAML format.
14713
+ *
14714
+ * @param request DescribeEciScalingConfigurationDetailRequest
14715
+ * @return DescribeEciScalingConfigurationDetailResponse
14716
+ */
14269
14717
  async describeEciScalingConfigurationDetail(request) {
14270
14718
  let runtime = new $Util.RuntimeOptions({});
14271
14719
  return await this.describeEciScalingConfigurationDetailWithOptions(request, runtime);
14272
14720
  }
14721
+ /**
14722
+ * @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances.
14723
+ *
14724
+ * @param request DescribeEciScalingConfigurationsRequest
14725
+ * @param runtime runtime options for this request RuntimeOptions
14726
+ * @return DescribeEciScalingConfigurationsResponse
14727
+ */
14273
14728
  async describeEciScalingConfigurationsWithOptions(request, runtime) {
14274
14729
  tea_util_1.default.validateModel(request);
14275
14730
  let query = {};
@@ -14319,20 +14774,28 @@ class Client extends openapi_client_1.default {
14319
14774
  });
14320
14775
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationsResponse({}));
14321
14776
  }
14777
+ /**
14778
+ * @summary Queries scaling configurations of the Elastic Container Instance type to learn the scaling configuration details. This allows you to select an appropriate template when you create elastic container instances.
14779
+ *
14780
+ * @param request DescribeEciScalingConfigurationsRequest
14781
+ * @return DescribeEciScalingConfigurationsResponse
14782
+ */
14322
14783
  async describeEciScalingConfigurations(request) {
14323
14784
  let runtime = new $Util.RuntimeOptions({});
14324
14785
  return await this.describeEciScalingConfigurationsWithOptions(request, runtime);
14325
14786
  }
14326
14787
  /**
14327
- * If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
14328
- * * If a lifecycle action is in the Pending state, Elastic Compute Service (ECS) instances are waiting to be added to a scaling group or waiting to be removed from a scaling group.
14329
- * * If a lifecycle action is in the Timeout state, the lifecycle hook that triggers the lifecycle action expires and ECS instances are added to or removed from a scaling group.
14330
- * * If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
14331
- * If you do not specify the action to perform, such as execute a specific OOS template, after a lifecycle hook ends, you can call this operation to obtain the token of the lifecycle action that corresponds to the lifecycle hook. Then, you can specify a custom action to perform after the lifecycle hook ends.
14332
- *
14333
- * @param request DescribeLifecycleActionsRequest
14334
- * @param runtime runtime options for this request RuntimeOptions
14335
- * @return DescribeLifecycleActionsResponse
14788
+ * @summary Queries lifecycle actions.
14789
+ *
14790
+ * @description If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
14791
+ * * If a lifecycle action is in the Pending state, Elastic Compute Service (ECS) instances are waiting to be added to a scaling group or waiting to be removed from a scaling group.
14792
+ * * If a lifecycle action is in the Timeout state, the lifecycle hook that triggers the lifecycle action expires and ECS instances are added to or removed from a scaling group.
14793
+ * * If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
14794
+ * If you do not specify the action to perform, such as execute a specific OOS template, after a lifecycle hook ends, you can call this operation to obtain the token of the lifecycle action that corresponds to the lifecycle hook. Then, you can specify a custom action to perform after the lifecycle hook ends.
14795
+ *
14796
+ * @param request DescribeLifecycleActionsRequest
14797
+ * @param runtime runtime options for this request RuntimeOptions
14798
+ * @return DescribeLifecycleActionsResponse
14336
14799
  */
14337
14800
  async describeLifecycleActionsWithOptions(request, runtime) {
14338
14801
  tea_util_1.default.validateModel(request);
@@ -14375,19 +14838,33 @@ class Client extends openapi_client_1.default {
14375
14838
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleActionsResponse({}));
14376
14839
  }
14377
14840
  /**
14378
- * If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
14379
- * * If a lifecycle action is in the Pending state, Elastic Compute Service (ECS) instances are waiting to be added to a scaling group or waiting to be removed from a scaling group.
14380
- * * If a lifecycle action is in the Timeout state, the lifecycle hook that triggers the lifecycle action expires and ECS instances are added to or removed from a scaling group.
14381
- * * If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
14382
- * If you do not specify the action to perform, such as execute a specific OOS template, after a lifecycle hook ends, you can call this operation to obtain the token of the lifecycle action that corresponds to the lifecycle hook. Then, you can specify a custom action to perform after the lifecycle hook ends.
14383
- *
14384
- * @param request DescribeLifecycleActionsRequest
14385
- * @return DescribeLifecycleActionsResponse
14841
+ * @summary Queries lifecycle actions.
14842
+ *
14843
+ * @description If a scaling activity is executed and a lifecycle hook is created for the scaling activity, the lifecycle hook triggers a lifecycle action. A lifecycle action can be in one of the following states:
14844
+ * * If a lifecycle action is in the Pending state, Elastic Compute Service (ECS) instances are waiting to be added to a scaling group or waiting to be removed from a scaling group.
14845
+ * * If a lifecycle action is in the Timeout state, the lifecycle hook that triggers the lifecycle action expires and ECS instances are added to or removed from a scaling group.
14846
+ * * If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
14847
+ * If you do not specify the action to perform, such as execute a specific OOS template, after a lifecycle hook ends, you can call this operation to obtain the token of the lifecycle action that corresponds to the lifecycle hook. Then, you can specify a custom action to perform after the lifecycle hook ends.
14848
+ *
14849
+ * @param request DescribeLifecycleActionsRequest
14850
+ * @return DescribeLifecycleActionsResponse
14386
14851
  */
14387
14852
  async describeLifecycleActions(request) {
14388
14853
  let runtime = new $Util.RuntimeOptions({});
14389
14854
  return await this.describeLifecycleActionsWithOptions(request, runtime);
14390
14855
  }
14856
+ /**
14857
+ * @summary Queries lifecycle hooks.
14858
+ *
14859
+ * @description You can use one of the following methods to query lifecycle hooks:
14860
+ * * 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.
14861
+ * * Specify the scaling group ID by using the ScalingGroupId parameter.
14862
+ * * Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter at the same time.
14863
+ *
14864
+ * @param request DescribeLifecycleHooksRequest
14865
+ * @param runtime runtime options for this request RuntimeOptions
14866
+ * @return DescribeLifecycleHooksResponse
14867
+ */
14391
14868
  async describeLifecycleHooksWithOptions(request, runtime) {
14392
14869
  tea_util_1.default.validateModel(request);
14393
14870
  let query = {};
@@ -14434,10 +14911,28 @@ class Client extends openapi_client_1.default {
14434
14911
  });
14435
14912
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleHooksResponse({}));
14436
14913
  }
14914
+ /**
14915
+ * @summary Queries lifecycle hooks.
14916
+ *
14917
+ * @description You can use one of the following methods to query lifecycle hooks:
14918
+ * * 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.
14919
+ * * Specify the scaling group ID by using the ScalingGroupId parameter.
14920
+ * * Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter at the same time.
14921
+ *
14922
+ * @param request DescribeLifecycleHooksRequest
14923
+ * @return DescribeLifecycleHooksResponse
14924
+ */
14437
14925
  async describeLifecycleHooks(request) {
14438
14926
  let runtime = new $Util.RuntimeOptions({});
14439
14927
  return await this.describeLifecycleHooksWithOptions(request, runtime);
14440
14928
  }
14929
+ /**
14930
+ * @summary Queries resource quotas. You can call the DescribeLimitation operation to query the upper limits on resources such as scheduled tasks that can be created in a scaling group, load balancers that can be attached to a scaling group, instances that can be contained in a scaling group, and scaling configurations that can be created in a scaling group.
14931
+ *
14932
+ * @param request DescribeLimitationRequest
14933
+ * @param runtime runtime options for this request RuntimeOptions
14934
+ * @return DescribeLimitationResponse
14935
+ */
14441
14936
  async describeLimitationWithOptions(request, runtime) {
14442
14937
  tea_util_1.default.validateModel(request);
14443
14938
  let query = {};
@@ -14463,10 +14958,23 @@ class Client extends openapi_client_1.default {
14463
14958
  });
14464
14959
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeLimitationResponse({}));
14465
14960
  }
14961
+ /**
14962
+ * @summary Queries resource quotas. You can call the DescribeLimitation operation to query the upper limits on resources such as scheduled tasks that can be created in a scaling group, load balancers that can be attached to a scaling group, instances that can be contained in a scaling group, and scaling configurations that can be created in a scaling group.
14963
+ *
14964
+ * @param request DescribeLimitationRequest
14965
+ * @return DescribeLimitationResponse
14966
+ */
14466
14967
  async describeLimitation(request) {
14467
14968
  let runtime = new $Util.RuntimeOptions({});
14468
14969
  return await this.describeLimitationWithOptions(request, runtime);
14469
14970
  }
14971
+ /**
14972
+ * @summary Queries event notifications.
14973
+ *
14974
+ * @param request DescribeNotificationConfigurationsRequest
14975
+ * @param runtime runtime options for this request RuntimeOptions
14976
+ * @return DescribeNotificationConfigurationsResponse
14977
+ */
14470
14978
  async describeNotificationConfigurationsWithOptions(request, runtime) {
14471
14979
  tea_util_1.default.validateModel(request);
14472
14980
  let query = {};
@@ -14498,10 +15006,23 @@ class Client extends openapi_client_1.default {
14498
15006
  });
14499
15007
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationConfigurationsResponse({}));
14500
15008
  }
15009
+ /**
15010
+ * @summary Queries event notifications.
15011
+ *
15012
+ * @param request DescribeNotificationConfigurationsRequest
15013
+ * @return DescribeNotificationConfigurationsResponse
15014
+ */
14501
15015
  async describeNotificationConfigurations(request) {
14502
15016
  let runtime = new $Util.RuntimeOptions({});
14503
15017
  return await this.describeNotificationConfigurationsWithOptions(request, runtime);
14504
15018
  }
15019
+ /**
15020
+ * @summary Queries notification types.
15021
+ *
15022
+ * @param request DescribeNotificationTypesRequest
15023
+ * @param runtime runtime options for this request RuntimeOptions
15024
+ * @return DescribeNotificationTypesResponse
15025
+ */
14505
15026
  async describeNotificationTypesWithOptions(request, runtime) {
14506
15027
  tea_util_1.default.validateModel(request);
14507
15028
  let query = {};
@@ -14527,10 +15048,59 @@ class Client extends openapi_client_1.default {
14527
15048
  });
14528
15049
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationTypesResponse({}));
14529
15050
  }
15051
+ /**
15052
+ * @summary Queries notification types.
15053
+ *
15054
+ * @param request DescribeNotificationTypesRequest
15055
+ * @return DescribeNotificationTypesResponse
15056
+ */
14530
15057
  async describeNotificationTypes(request) {
14531
15058
  let runtime = new $Util.RuntimeOptions({});
14532
15059
  return await this.describeNotificationTypesWithOptions(request, runtime);
14533
15060
  }
15061
+ /**
15062
+ * @summary DescribePatternTypes
15063
+ *
15064
+ * @param request DescribePatternTypesRequest
15065
+ * @param runtime runtime options for this request RuntimeOptions
15066
+ * @return DescribePatternTypesResponse
15067
+ */
15068
+ async describePatternTypesWithOptions(request, runtime) {
15069
+ tea_util_1.default.validateModel(request);
15070
+ let query = openapi_util_1.default.query(tea_util_1.default.toMap(request));
15071
+ let req = new $OpenApi.OpenApiRequest({
15072
+ query: openapi_util_1.default.query(query),
15073
+ });
15074
+ let params = new $OpenApi.Params({
15075
+ action: "DescribePatternTypes",
15076
+ version: "2022-02-22",
15077
+ protocol: "HTTPS",
15078
+ pathname: "/",
15079
+ method: "GET",
15080
+ authType: "AK",
15081
+ style: "RPC",
15082
+ reqBodyType: "formData",
15083
+ bodyType: "json",
15084
+ });
15085
+ return $tea.cast(await this.callApi(params, req, runtime), new DescribePatternTypesResponse({}));
15086
+ }
15087
+ /**
15088
+ * @summary DescribePatternTypes
15089
+ *
15090
+ * @param request DescribePatternTypesRequest
15091
+ * @return DescribePatternTypesResponse
15092
+ */
15093
+ async describePatternTypes(request) {
15094
+ let runtime = new $Util.RuntimeOptions({});
15095
+ return await this.describePatternTypesWithOptions(request, runtime);
15096
+ }
15097
+ /**
15098
+ * @summary Queries the regions in which Auto Scaling is available.
15099
+ *
15100
+ * @param request DescribeRegionsRequest
15101
+ * @param runtime runtime options for this request RuntimeOptions
15102
+ * @return DescribeRegionsResponse
15103
+ */
14534
15104
  async describeRegionsWithOptions(request, runtime) {
14535
15105
  tea_util_1.default.validateModel(request);
14536
15106
  let query = {};
@@ -14562,18 +15132,26 @@ class Client extends openapi_client_1.default {
14562
15132
  });
14563
15133
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeRegionsResponse({}));
14564
15134
  }
15135
+ /**
15136
+ * @summary Queries the regions in which Auto Scaling is available.
15137
+ *
15138
+ * @param request DescribeRegionsRequest
15139
+ * @return DescribeRegionsResponse
15140
+ */
14565
15141
  async describeRegions(request) {
14566
15142
  let runtime = new $Util.RuntimeOptions({});
14567
15143
  return await this.describeRegionsWithOptions(request, runtime);
14568
15144
  }
14569
15145
  /**
14570
- * You can specify a scaling group ID to query all scaling activities in the scaling group.
14571
- * You can filter query results based on the status of scaling activities.
14572
- * You can query scaling activities that are executed in the previous 30 days.
14573
- *
14574
- * @param request DescribeScalingActivitiesRequest
14575
- * @param runtime runtime options for this request RuntimeOptions
14576
- * @return DescribeScalingActivitiesResponse
15146
+ * @summary Queries scaling activities.
15147
+ *
15148
+ * @description You can specify a scaling group ID to query all scaling activities in the scaling group.
15149
+ * You can filter query results based on the status of scaling activities.
15150
+ * You can query scaling activities that are executed in the previous 30 days.
15151
+ *
15152
+ * @param request DescribeScalingActivitiesRequest
15153
+ * @param runtime runtime options for this request RuntimeOptions
15154
+ * @return DescribeScalingActivitiesResponse
14577
15155
  */
14578
15156
  async describeScalingActivitiesWithOptions(request, runtime) {
14579
15157
  tea_util_1.default.validateModel(request);
@@ -14625,17 +15203,26 @@ class Client extends openapi_client_1.default {
14625
15203
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivitiesResponse({}));
14626
15204
  }
14627
15205
  /**
14628
- * You can specify a scaling group ID to query all scaling activities in the scaling group.
14629
- * You can filter query results based on the status of scaling activities.
14630
- * You can query scaling activities that are executed in the previous 30 days.
14631
- *
14632
- * @param request DescribeScalingActivitiesRequest
14633
- * @return DescribeScalingActivitiesResponse
15206
+ * @summary Queries scaling activities.
15207
+ *
15208
+ * @description You can specify a scaling group ID to query all scaling activities in the scaling group.
15209
+ * You can filter query results based on the status of scaling activities.
15210
+ * You can query scaling activities that are executed in the previous 30 days.
15211
+ *
15212
+ * @param request DescribeScalingActivitiesRequest
15213
+ * @return DescribeScalingActivitiesResponse
14634
15214
  */
14635
15215
  async describeScalingActivities(request) {
14636
15216
  let runtime = new $Util.RuntimeOptions({});
14637
15217
  return await this.describeScalingActivitiesWithOptions(request, runtime);
14638
15218
  }
15219
+ /**
15220
+ * @summary Queries the details about a scaling activity.
15221
+ *
15222
+ * @param request DescribeScalingActivityDetailRequest
15223
+ * @param runtime runtime options for this request RuntimeOptions
15224
+ * @return DescribeScalingActivityDetailResponse
15225
+ */
14639
15226
  async describeScalingActivityDetailWithOptions(request, runtime) {
14640
15227
  tea_util_1.default.validateModel(request);
14641
15228
  let query = {};
@@ -14667,10 +15254,23 @@ class Client extends openapi_client_1.default {
14667
15254
  });
14668
15255
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivityDetailResponse({}));
14669
15256
  }
15257
+ /**
15258
+ * @summary Queries the details about a scaling activity.
15259
+ *
15260
+ * @param request DescribeScalingActivityDetailRequest
15261
+ * @return DescribeScalingActivityDetailResponse
15262
+ */
14670
15263
  async describeScalingActivityDetail(request) {
14671
15264
  let runtime = new $Util.RuntimeOptions({});
14672
15265
  return await this.describeScalingActivityDetailWithOptions(request, runtime);
14673
15266
  }
15267
+ /**
15268
+ * @summary Queries scaling configurations.
15269
+ *
15270
+ * @param request DescribeScalingConfigurationsRequest
15271
+ * @param runtime runtime options for this request RuntimeOptions
15272
+ * @return DescribeScalingConfigurationsResponse
15273
+ */
14674
15274
  async describeScalingConfigurationsWithOptions(request, runtime) {
14675
15275
  tea_util_1.default.validateModel(request);
14676
15276
  let query = {};
@@ -14720,10 +15320,23 @@ class Client extends openapi_client_1.default {
14720
15320
  });
14721
15321
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingConfigurationsResponse({}));
14722
15322
  }
15323
+ /**
15324
+ * @summary Queries scaling configurations.
15325
+ *
15326
+ * @param request DescribeScalingConfigurationsRequest
15327
+ * @return DescribeScalingConfigurationsResponse
15328
+ */
14723
15329
  async describeScalingConfigurations(request) {
14724
15330
  let runtime = new $Util.RuntimeOptions({});
14725
15331
  return await this.describeScalingConfigurationsWithOptions(request, runtime);
14726
15332
  }
15333
+ /**
15334
+ * @summary Queries a scaling group. You can call the DescribeScalingGroupDetail operation to query the basic information, instances, and scaling configurations of a scaling group. If you set OutputFormat to yaml, a Kubernetes Deployment file that is in the YAML format is returned.
15335
+ *
15336
+ * @param request DescribeScalingGroupDetailRequest
15337
+ * @param runtime runtime options for this request RuntimeOptions
15338
+ * @return DescribeScalingGroupDetailResponse
15339
+ */
14727
15340
  async describeScalingGroupDetailWithOptions(request, runtime) {
14728
15341
  tea_util_1.default.validateModel(request);
14729
15342
  let query = {};
@@ -14755,10 +15368,23 @@ class Client extends openapi_client_1.default {
14755
15368
  });
14756
15369
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupDetailResponse({}));
14757
15370
  }
15371
+ /**
15372
+ * @summary Queries a scaling group. You can call the DescribeScalingGroupDetail operation to query the basic information, instances, and scaling configurations of a scaling group. If you set OutputFormat to yaml, a Kubernetes Deployment file that is in the YAML format is returned.
15373
+ *
15374
+ * @param request DescribeScalingGroupDetailRequest
15375
+ * @return DescribeScalingGroupDetailResponse
15376
+ */
14758
15377
  async describeScalingGroupDetail(request) {
14759
15378
  let runtime = new $Util.RuntimeOptions({});
14760
15379
  return await this.describeScalingGroupDetailWithOptions(request, runtime);
14761
15380
  }
15381
+ /**
15382
+ * @summary Queries scaling groups. If you want to query the basic information, instances, and scaling configurations of a scaling group, you can call the DescribeScalingGroups operation.
15383
+ *
15384
+ * @param request DescribeScalingGroupsRequest
15385
+ * @param runtime runtime options for this request RuntimeOptions
15386
+ * @return DescribeScalingGroupsResponse
15387
+ */
14762
15388
  async describeScalingGroupsWithOptions(request, runtime) {
14763
15389
  tea_util_1.default.validateModel(request);
14764
15390
  let query = {};
@@ -14817,10 +15443,23 @@ class Client extends openapi_client_1.default {
14817
15443
  });
14818
15444
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupsResponse({}));
14819
15445
  }
15446
+ /**
15447
+ * @summary Queries scaling groups. If you want to query the basic information, instances, and scaling configurations of a scaling group, you can call the DescribeScalingGroups operation.
15448
+ *
15449
+ * @param request DescribeScalingGroupsRequest
15450
+ * @return DescribeScalingGroupsResponse
15451
+ */
14820
15452
  async describeScalingGroups(request) {
14821
15453
  let runtime = new $Util.RuntimeOptions({});
14822
15454
  return await this.describeScalingGroupsWithOptions(request, runtime);
14823
15455
  }
15456
+ /**
15457
+ * @summary Queries the Elastic Compute Service (ECS) instances in a scaling group
15458
+ *
15459
+ * @param request DescribeScalingInstancesRequest
15460
+ * @param runtime runtime options for this request RuntimeOptions
15461
+ * @return DescribeScalingInstancesResponse
15462
+ */
14824
15463
  async describeScalingInstancesWithOptions(request, runtime) {
14825
15464
  tea_util_1.default.validateModel(request);
14826
15465
  let query = {};
@@ -14888,16 +15527,24 @@ class Client extends openapi_client_1.default {
14888
15527
  });
14889
15528
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingInstancesResponse({}));
14890
15529
  }
15530
+ /**
15531
+ * @summary Queries the Elastic Compute Service (ECS) instances in a scaling group
15532
+ *
15533
+ * @param request DescribeScalingInstancesRequest
15534
+ * @return DescribeScalingInstancesResponse
15535
+ */
14891
15536
  async describeScalingInstances(request) {
14892
15537
  let runtime = new $Util.RuntimeOptions({});
14893
15538
  return await this.describeScalingInstancesWithOptions(request, runtime);
14894
15539
  }
14895
15540
  /**
14896
- * You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
14897
- *
14898
- * @param request DescribeScalingRulesRequest
14899
- * @param runtime runtime options for this request RuntimeOptions
14900
- * @return DescribeScalingRulesResponse
15541
+ * @summary Queries all scaling rules in a scaling group.
15542
+ *
15543
+ * @description You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
15544
+ *
15545
+ * @param request DescribeScalingRulesRequest
15546
+ * @param runtime runtime options for this request RuntimeOptions
15547
+ * @return DescribeScalingRulesResponse
14901
15548
  */
14902
15549
  async describeScalingRulesWithOptions(request, runtime) {
14903
15550
  tea_util_1.default.validateModel(request);
@@ -14958,15 +15605,26 @@ class Client extends openapi_client_1.default {
14958
15605
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingRulesResponse({}));
14959
15606
  }
14960
15607
  /**
14961
- * You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
14962
- *
14963
- * @param request DescribeScalingRulesRequest
14964
- * @return DescribeScalingRulesResponse
15608
+ * @summary Queries all scaling rules in a scaling group.
15609
+ *
15610
+ * @description You can specify a scaling group ID to query all scaling rules in the scaling group. You can also specify the scaling rule ID, name, unique identifier, and type in the request parameters as filter conditions.
15611
+ *
15612
+ * @param request DescribeScalingRulesRequest
15613
+ * @return DescribeScalingRulesResponse
14965
15614
  */
14966
15615
  async describeScalingRules(request) {
14967
15616
  let runtime = new $Util.RuntimeOptions({});
14968
15617
  return await this.describeScalingRulesWithOptions(request, runtime);
14969
15618
  }
15619
+ /**
15620
+ * @summary Queries scheduled tasks.
15621
+ *
15622
+ * @description You can query scheduled tasks by scaling rule, task ID, or task name.
15623
+ *
15624
+ * @param request DescribeScheduledTasksRequest
15625
+ * @param runtime runtime options for this request RuntimeOptions
15626
+ * @return DescribeScheduledTasksResponse
15627
+ */
14970
15628
  async describeScheduledTasksWithOptions(request, runtime) {
14971
15629
  tea_util_1.default.validateModel(request);
14972
15630
  let query = {};
@@ -15019,10 +15677,25 @@ class Client extends openapi_client_1.default {
15019
15677
  });
15020
15678
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScheduledTasksResponse({}));
15021
15679
  }
15680
+ /**
15681
+ * @summary Queries scheduled tasks.
15682
+ *
15683
+ * @description You can query scheduled tasks by scaling rule, task ID, or task name.
15684
+ *
15685
+ * @param request DescribeScheduledTasksRequest
15686
+ * @return DescribeScheduledTasksResponse
15687
+ */
15022
15688
  async describeScheduledTasks(request) {
15023
15689
  let runtime = new $Util.RuntimeOptions({});
15024
15690
  return await this.describeScheduledTasksWithOptions(request, runtime);
15025
15691
  }
15692
+ /**
15693
+ * @summary Disassociates one or more Application Load Balancer (ALB) server groups from a scaling group.
15694
+ *
15695
+ * @param request DetachAlbServerGroupsRequest
15696
+ * @param runtime runtime options for this request RuntimeOptions
15697
+ * @return DetachAlbServerGroupsResponse
15698
+ */
15026
15699
  async detachAlbServerGroupsWithOptions(request, runtime) {
15027
15700
  tea_util_1.default.validateModel(request);
15028
15701
  let query = {};
@@ -15063,10 +15736,23 @@ class Client extends openapi_client_1.default {
15063
15736
  });
15064
15737
  return $tea.cast(await this.callApi(params, req, runtime), new DetachAlbServerGroupsResponse({}));
15065
15738
  }
15739
+ /**
15740
+ * @summary Disassociates one or more Application Load Balancer (ALB) server groups from a scaling group.
15741
+ *
15742
+ * @param request DetachAlbServerGroupsRequest
15743
+ * @return DetachAlbServerGroupsResponse
15744
+ */
15066
15745
  async detachAlbServerGroups(request) {
15067
15746
  let runtime = new $Util.RuntimeOptions({});
15068
15747
  return await this.detachAlbServerGroupsWithOptions(request, runtime);
15069
15748
  }
15749
+ /**
15750
+ * @summary Disassociates one or more ApsaraDB RDS instances from a scaling group.
15751
+ *
15752
+ * @param request DetachDBInstancesRequest
15753
+ * @param runtime runtime options for this request RuntimeOptions
15754
+ * @return DetachDBInstancesResponse
15755
+ */
15070
15756
  async detachDBInstancesWithOptions(request, runtime) {
15071
15757
  tea_util_1.default.validateModel(request);
15072
15758
  let query = {};
@@ -15110,23 +15796,31 @@ class Client extends openapi_client_1.default {
15110
15796
  });
15111
15797
  return $tea.cast(await this.callApi(params, req, runtime), new DetachDBInstancesResponse({}));
15112
15798
  }
15799
+ /**
15800
+ * @summary Disassociates one or more ApsaraDB RDS instances from a scaling group.
15801
+ *
15802
+ * @param request DetachDBInstancesRequest
15803
+ * @return DetachDBInstancesResponse
15804
+ */
15113
15805
  async detachDBInstances(request) {
15114
15806
  let runtime = new $Util.RuntimeOptions({});
15115
15807
  return await this.detachDBInstancesWithOptions(request, runtime);
15116
15808
  }
15117
15809
  /**
15118
- * After ECS instances or elastic container instances are removed from a scaling group, you can call the AttachInstances operation to add the ECS instances or elastic container instances that are removed from the scaling group to other scaling groups.
15119
- * After you remove an ECS instance or elastic container instance by calling the DetachInstances operation, the instance is not stopped or released.
15120
- * Before you call this operation, make sure that the following conditions are met:
15121
- * * The specified scaling group is enabled.
15122
- * * No scaling activities in the specified scaling group are in progress.
15123
- * > If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15124
- * A successful call indicates only that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
15125
- * The number of ECS instances or elastic container instances in a scaling group after you remove a specific number of instances from the scaling group must be equal to or greater than the value of the MinSize parameter. Otherwise, an error is reported when you call the DetachInstances operation.
15126
- *
15127
- * @param request DetachInstancesRequest
15128
- * @param runtime runtime options for this request RuntimeOptions
15129
- * @return DetachInstancesResponse
15810
+ * @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
15811
+ *
15812
+ * @description After ECS instances or elastic container instances are removed from a scaling group, you can call the AttachInstances operation to add the ECS instances or elastic container instances that are removed from the scaling group to other scaling groups.
15813
+ * After you remove an ECS instance or elastic container instance by calling the DetachInstances operation, the instance is not stopped or released.
15814
+ * Before you call this operation, make sure that the following conditions are met:
15815
+ * * The specified scaling group is enabled.
15816
+ * * No scaling activities in the specified scaling group are in progress.
15817
+ * > If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15818
+ * A successful call indicates only that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
15819
+ * The number of ECS instances or elastic container instances in a scaling group after you remove a specific number of instances from the scaling group must be equal to or greater than the value of the MinSize parameter. Otherwise, an error is reported when you call the DetachInstances operation.
15820
+ *
15821
+ * @param request DetachInstancesRequest
15822
+ * @param runtime runtime options for this request RuntimeOptions
15823
+ * @return DetachInstancesResponse
15130
15824
  */
15131
15825
  async detachInstancesWithOptions(request, runtime) {
15132
15826
  tea_util_1.default.validateModel(request);
@@ -15178,22 +15872,31 @@ class Client extends openapi_client_1.default {
15178
15872
  return $tea.cast(await this.callApi(params, req, runtime), new DetachInstancesResponse({}));
15179
15873
  }
15180
15874
  /**
15181
- * After ECS instances or elastic container instances are removed from a scaling group, you can call the AttachInstances operation to add the ECS instances or elastic container instances that are removed from the scaling group to other scaling groups.
15182
- * After you remove an ECS instance or elastic container instance by calling the DetachInstances operation, the instance is not stopped or released.
15183
- * Before you call this operation, make sure that the following conditions are met:
15184
- * * The specified scaling group is enabled.
15185
- * * No scaling activities in the specified scaling group are in progress.
15186
- * > If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15187
- * A successful call indicates only that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
15188
- * The number of ECS instances or elastic container instances in a scaling group after you remove a specific number of instances from the scaling group must be equal to or greater than the value of the MinSize parameter. Otherwise, an error is reported when you call the DetachInstances operation.
15189
- *
15190
- * @param request DetachInstancesRequest
15191
- * @return DetachInstancesResponse
15875
+ * @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
15876
+ *
15877
+ * @description After ECS instances or elastic container instances are removed from a scaling group, you can call the AttachInstances operation to add the ECS instances or elastic container instances that are removed from the scaling group to other scaling groups.
15878
+ * After you remove an ECS instance or elastic container instance by calling the DetachInstances operation, the instance is not stopped or released.
15879
+ * Before you call this operation, make sure that the following conditions are met:
15880
+ * * The specified scaling group is enabled.
15881
+ * * No scaling activities in the specified scaling group are in progress.
15882
+ * > If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15883
+ * A successful call indicates only that Auto Scaling accepts the request. However, the scaling activity may still fail. You can obtain the status of a scaling activity based on the value of the ScalingActivityId parameter in the response.
15884
+ * The number of ECS instances or elastic container instances in a scaling group after you remove a specific number of instances from the scaling group must be equal to or greater than the value of the MinSize parameter. Otherwise, an error is reported when you call the DetachInstances operation.
15885
+ *
15886
+ * @param request DetachInstancesRequest
15887
+ * @return DetachInstancesResponse
15192
15888
  */
15193
15889
  async detachInstances(request) {
15194
15890
  let runtime = new $Util.RuntimeOptions({});
15195
15891
  return await this.detachInstancesWithOptions(request, runtime);
15196
15892
  }
15893
+ /**
15894
+ * @summary Detaches one or more Classic Load Balancer (CLB) instances from a scaling group.
15895
+ *
15896
+ * @param request DetachLoadBalancersRequest
15897
+ * @param runtime runtime options for this request RuntimeOptions
15898
+ * @return DetachLoadBalancersResponse
15899
+ */
15197
15900
  async detachLoadBalancersWithOptions(request, runtime) {
15198
15901
  tea_util_1.default.validateModel(request);
15199
15902
  let query = {};
@@ -15237,10 +15940,23 @@ class Client extends openapi_client_1.default {
15237
15940
  });
15238
15941
  return $tea.cast(await this.callApi(params, req, runtime), new DetachLoadBalancersResponse({}));
15239
15942
  }
15943
+ /**
15944
+ * @summary Detaches one or more Classic Load Balancer (CLB) instances from a scaling group.
15945
+ *
15946
+ * @param request DetachLoadBalancersRequest
15947
+ * @return DetachLoadBalancersResponse
15948
+ */
15240
15949
  async detachLoadBalancers(request) {
15241
15950
  let runtime = new $Util.RuntimeOptions({});
15242
15951
  return await this.detachLoadBalancersWithOptions(request, runtime);
15243
15952
  }
15953
+ /**
15954
+ * @summary Detaches one or more server groups from a scaling group. You can attach and detach the following server groups from a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
15955
+ *
15956
+ * @param request DetachServerGroupsRequest
15957
+ * @param runtime runtime options for this request RuntimeOptions
15958
+ * @return DetachServerGroupsResponse
15959
+ */
15244
15960
  async detachServerGroupsWithOptions(request, runtime) {
15245
15961
  tea_util_1.default.validateModel(request);
15246
15962
  let query = {};
@@ -15281,20 +15997,29 @@ class Client extends openapi_client_1.default {
15281
15997
  });
15282
15998
  return $tea.cast(await this.callApi(params, req, runtime), new DetachServerGroupsResponse({}));
15283
15999
  }
16000
+ /**
16001
+ * @summary Detaches one or more server groups from a scaling group. You can attach and detach the following server groups from a scaling group: Application Load Balancer (ALB) and Network Load Balancer (NLB) server groups.
16002
+ *
16003
+ * @param request DetachServerGroupsRequest
16004
+ * @return DetachServerGroupsResponse
16005
+ */
15284
16006
  async detachServerGroups(request) {
15285
16007
  let runtime = new $Util.RuntimeOptions({});
15286
16008
  return await this.detachServerGroupsWithOptions(request, runtime);
15287
16009
  }
15288
16010
  /**
15289
- * You can use the following parameters to specify the vServer groups that you want to detach from your scaling group.
15290
- * * LoadBalancerId: the ID of the Classic Load Balancer (CLB) instance.
15291
- * * VServerGroupId: the ID of the vServer group.
15292
- * * Port: the port number of the vServer group.
15293
- * If the vServer group that is specified in this call matches the vServer group associated with your scaling group, the vServer group can be detached. Otherwise, the request for detaching the vServer group is ignored, and no error is reported.
15294
- *
15295
- * @param request DetachVServerGroupsRequest
15296
- * @param runtime runtime options for this request RuntimeOptions
15297
- * @return DetachVServerGroupsResponse
16011
+ * @summary Detaches vServer groups from a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups to improve service performance. If the load balancer currently attached to your scaling group is no longer needed to distribute the access traffic to the instances in your scaling group, you can call the DetachVServerGroups operation to detach one or more vServer groups of this load balancer from the scaling group.
16012
+ *
16013
+ * @description * When you call the DetachVServerGroups operation, you must use the following parameters to specify the vServer groups that you want to detach from your scaling group:
16014
+ * * LoadBalancerId: the ID of the load balancer
16015
+ * * VServerGroupId: the ID of the vServer group
16016
+ * * Port: the port number of the vServer group
16017
+ * * When the vServer group specified by the request parameters matches that attached to your scaling group, this operation yields a favorable result. Otherwise, the request is ignored and no error is reported.
16018
+ * * Before you call this operation, you must make sure that the load balancer has ceased routing the access traffic to the instances in the scaling group. Failure to do so may lead to service requests being dropped or lost during the detachment process.
16019
+ *
16020
+ * @param request DetachVServerGroupsRequest
16021
+ * @param runtime runtime options for this request RuntimeOptions
16022
+ * @return DetachVServerGroupsResponse
15298
16023
  */
15299
16024
  async detachVServerGroupsWithOptions(request, runtime) {
15300
16025
  tea_util_1.default.validateModel(request);
@@ -15337,19 +16062,29 @@ class Client extends openapi_client_1.default {
15337
16062
  return $tea.cast(await this.callApi(params, req, runtime), new DetachVServerGroupsResponse({}));
15338
16063
  }
15339
16064
  /**
15340
- * You can use the following parameters to specify the vServer groups that you want to detach from your scaling group.
15341
- * * LoadBalancerId: the ID of the Classic Load Balancer (CLB) instance.
15342
- * * VServerGroupId: the ID of the vServer group.
15343
- * * Port: the port number of the vServer group.
15344
- * If the vServer group that is specified in this call matches the vServer group associated with your scaling group, the vServer group can be detached. Otherwise, the request for detaching the vServer group is ignored, and no error is reported.
15345
- *
15346
- * @param request DetachVServerGroupsRequest
15347
- * @return DetachVServerGroupsResponse
16065
+ * @summary Detaches vServer groups from a scaling group. Auto Scaling supports the attachment of load balancers to scaling groups to improve service performance. If the load balancer currently attached to your scaling group is no longer needed to distribute the access traffic to the instances in your scaling group, you can call the DetachVServerGroups operation to detach one or more vServer groups of this load balancer from the scaling group.
16066
+ *
16067
+ * @description * When you call the DetachVServerGroups operation, you must use the following parameters to specify the vServer groups that you want to detach from your scaling group:
16068
+ * * LoadBalancerId: the ID of the load balancer
16069
+ * * VServerGroupId: the ID of the vServer group
16070
+ * * Port: the port number of the vServer group
16071
+ * * When the vServer group specified by the request parameters matches that attached to your scaling group, this operation yields a favorable result. Otherwise, the request is ignored and no error is reported.
16072
+ * * Before you call this operation, you must make sure that the load balancer has ceased routing the access traffic to the instances in the scaling group. Failure to do so may lead to service requests being dropped or lost during the detachment process.
16073
+ *
16074
+ * @param request DetachVServerGroupsRequest
16075
+ * @return DetachVServerGroupsResponse
15348
16076
  */
15349
16077
  async detachVServerGroups(request) {
15350
16078
  let runtime = new $Util.RuntimeOptions({});
15351
16079
  return await this.detachVServerGroupsWithOptions(request, runtime);
15352
16080
  }
16081
+ /**
16082
+ * @summary Disables an event-triggered task.
16083
+ *
16084
+ * @param request DisableAlarmRequest
16085
+ * @param runtime runtime options for this request RuntimeOptions
16086
+ * @return DisableAlarmResponse
16087
+ */
15353
16088
  async disableAlarmWithOptions(request, runtime) {
15354
16089
  tea_util_1.default.validateModel(request);
15355
16090
  let query = {};
@@ -15381,10 +16116,27 @@ class Client extends openapi_client_1.default {
15381
16116
  });
15382
16117
  return $tea.cast(await this.callApi(params, req, runtime), new DisableAlarmResponse({}));
15383
16118
  }
16119
+ /**
16120
+ * @summary Disables an event-triggered task.
16121
+ *
16122
+ * @param request DisableAlarmRequest
16123
+ * @return DisableAlarmResponse
16124
+ */
15384
16125
  async disableAlarm(request) {
15385
16126
  let runtime = new $Util.RuntimeOptions({});
15386
16127
  return await this.disableAlarmWithOptions(request, runtime);
15387
16128
  }
16129
+ /**
16130
+ * @summary Disables a scaling group.
16131
+ *
16132
+ * @description Before you call this operation to disable a scaling group, take note of the following items:
16133
+ * * When you call this operation, ongoing scaling activities will continue until they are complete, but new activities will be rejected.
16134
+ * * You can disable only scaling groups that are in the Active state.
16135
+ *
16136
+ * @param request DisableScalingGroupRequest
16137
+ * @param runtime runtime options for this request RuntimeOptions
16138
+ * @return DisableScalingGroupResponse
16139
+ */
15388
16140
  async disableScalingGroupWithOptions(request, runtime) {
15389
16141
  tea_util_1.default.validateModel(request);
15390
16142
  let query = {};
@@ -15419,10 +16171,27 @@ class Client extends openapi_client_1.default {
15419
16171
  });
15420
16172
  return $tea.cast(await this.callApi(params, req, runtime), new DisableScalingGroupResponse({}));
15421
16173
  }
16174
+ /**
16175
+ * @summary Disables a scaling group.
16176
+ *
16177
+ * @description Before you call this operation to disable a scaling group, take note of the following items:
16178
+ * * When you call this operation, ongoing scaling activities will continue until they are complete, but new activities will be rejected.
16179
+ * * You can disable only scaling groups that are in the Active state.
16180
+ *
16181
+ * @param request DisableScalingGroupRequest
16182
+ * @return DisableScalingGroupResponse
16183
+ */
15422
16184
  async disableScalingGroup(request) {
15423
16185
  let runtime = new $Util.RuntimeOptions({});
15424
16186
  return await this.disableScalingGroupWithOptions(request, runtime);
15425
16187
  }
16188
+ /**
16189
+ * @summary Enables an event-triggered task.
16190
+ *
16191
+ * @param request EnableAlarmRequest
16192
+ * @param runtime runtime options for this request RuntimeOptions
16193
+ * @return EnableAlarmResponse
16194
+ */
15426
16195
  async enableAlarmWithOptions(request, runtime) {
15427
16196
  tea_util_1.default.validateModel(request);
15428
16197
  let query = {};
@@ -15454,20 +16223,28 @@ class Client extends openapi_client_1.default {
15454
16223
  });
15455
16224
  return $tea.cast(await this.callApi(params, req, runtime), new EnableAlarmResponse({}));
15456
16225
  }
16226
+ /**
16227
+ * @summary Enables an event-triggered task.
16228
+ *
16229
+ * @param request EnableAlarmRequest
16230
+ * @return EnableAlarmResponse
16231
+ */
15457
16232
  async enableAlarm(request) {
15458
16233
  let runtime = new $Util.RuntimeOptions({});
15459
16234
  return await this.enableAlarmWithOptions(request, runtime);
15460
16235
  }
15461
16236
  /**
15462
- * 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.
15463
- * > 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.
15464
- * 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.
15465
- * * 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.
15466
- * * If the value of the TotalCapacity parameter is greater than the value of the MaxSize parameter, the call fails.
15467
- *
15468
- * @param request EnableScalingGroupRequest
15469
- * @param runtime runtime options for this request RuntimeOptions
15470
- * @return EnableScalingGroupResponse
16237
+ * @summary Enables a scaling group.
16238
+ *
16239
+ * @description You can call this operation to enable a scaling group that is in the Inactive state and has an instance configuration source. The instance configuration source can be a scaling configuration, a launch template, or an Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If a scaling group is not in the Inactive state or does not have an active instance configuration source, you cannot call this operation to enable the scaling group.
16240
+ * > 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.
16241
+ * 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.
16242
+ * * 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.
16243
+ * * If the value of the TotalCapactiy parameter is greater than the value of the MaxSize parameter, the call fails.
16244
+ *
16245
+ * @param request EnableScalingGroupRequest
16246
+ * @param runtime runtime options for this request RuntimeOptions
16247
+ * @return EnableScalingGroupResponse
15471
16248
  */
15472
16249
  async enableScalingGroupWithOptions(request, runtime) {
15473
16250
  tea_util_1.default.validateModel(request);
@@ -15525,19 +16302,34 @@ class Client extends openapi_client_1.default {
15525
16302
  return $tea.cast(await this.callApi(params, req, runtime), new EnableScalingGroupResponse({}));
15526
16303
  }
15527
16304
  /**
15528
- * 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.
15529
- * > 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.
15530
- * 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.
15531
- * * 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.
15532
- * * If the value of the TotalCapacity parameter is greater than the value of the MaxSize parameter, the call fails.
15533
- *
15534
- * @param request EnableScalingGroupRequest
15535
- * @return EnableScalingGroupResponse
16305
+ * @summary Enables a scaling group.
16306
+ *
16307
+ * @description You can call this operation to enable a scaling group that is in the Inactive state and has an instance configuration source. The instance configuration source can be a scaling configuration, a launch template, or an Elastic Compute Service (ECS) instance that you specified when you created the scaling group. If a scaling group is not in the Inactive state or does not have an active instance configuration source, you cannot call this operation to enable the scaling group.
16308
+ * > 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.
16309
+ * 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.
16310
+ * * 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.
16311
+ * * If the value of the TotalCapactiy parameter is greater than the value of the MaxSize parameter, the call fails.
16312
+ *
16313
+ * @param request EnableScalingGroupRequest
16314
+ * @return EnableScalingGroupResponse
15536
16315
  */
15537
16316
  async enableScalingGroup(request) {
15538
16317
  let runtime = new $Util.RuntimeOptions({});
15539
16318
  return await this.enableScalingGroupWithOptions(request, runtime);
15540
16319
  }
16320
+ /**
16321
+ * @summary Puts an Elastic Compute Service (ECS) instance into the Standby state.
16322
+ *
16323
+ * @description ## Description
16324
+ * * If you call the operation to put an ECS instance in a scaling group that is associated with a Classic Load Balancer (CLB) instance into the Standby state, the weight of the ECS instance as a backend server of the CLB instance is set to 0.
16325
+ * * You can remove an instance that is in the Standby state from a scaling group, and then release the instance.
16326
+ * * ECS instances that are in the Standby state are not removed from the scaling group during scale-in activities triggered by event-triggered tasks.
16327
+ * * If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, for example, the ECS instance is being stopped or being restarted, Auto Scaling does not update the health status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health status of the ECS instance only when the ECS instance is no longer in the Standby state.
16328
+ *
16329
+ * @param request EnterStandbyRequest
16330
+ * @param runtime runtime options for this request RuntimeOptions
16331
+ * @return EnterStandbyResponse
16332
+ */
15541
16333
  async enterStandbyWithOptions(request, runtime) {
15542
16334
  tea_util_1.default.validateModel(request);
15543
16335
  let query = {};
@@ -15575,23 +16367,37 @@ class Client extends openapi_client_1.default {
15575
16367
  });
15576
16368
  return $tea.cast(await this.callApi(params, req, runtime), new EnterStandbyResponse({}));
15577
16369
  }
16370
+ /**
16371
+ * @summary Puts an Elastic Compute Service (ECS) instance into the Standby state.
16372
+ *
16373
+ * @description ## Description
16374
+ * * If you call the operation to put an ECS instance in a scaling group that is associated with a Classic Load Balancer (CLB) instance into the Standby state, the weight of the ECS instance as a backend server of the CLB instance is set to 0.
16375
+ * * You can remove an instance that is in the Standby state from a scaling group, and then release the instance.
16376
+ * * ECS instances that are in the Standby state are not removed from the scaling group during scale-in activities triggered by event-triggered tasks.
16377
+ * * If Auto Scaling considers an ECS instance that is in the Standby state unhealthy, for example, the ECS instance is being stopped or being restarted, Auto Scaling does not update the health status of the ECS instance or trigger scale-in activities to remove the ECS instance from the scaling group. Auto Scaling updates the health status of the ECS instance only when the ECS instance is no longer in the Standby state.
16378
+ *
16379
+ * @param request EnterStandbyRequest
16380
+ * @return EnterStandbyResponse
16381
+ */
15578
16382
  async enterStandby(request) {
15579
16383
  let runtime = new $Util.RuntimeOptions({});
15580
16384
  return await this.enterStandbyWithOptions(request, runtime);
15581
16385
  }
15582
16386
  /**
15583
- * Before you call this operation, take note of the following items:
15584
- * * The scaling group is in the Active state.
15585
- * * No scaling activities in the scaling group are in progress.
15586
- * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15587
- * 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.
15588
- * 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.
15589
- * 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.
15590
- * You can specify only a limited number of ECS instances in each adjustment. For more information, see the description of the AdjustmentValue parameter in the CreateScalingRule topic.
15591
- *
15592
- * @param request ExecuteScalingRuleRequest
15593
- * @param runtime runtime options for this request RuntimeOptions
15594
- * @return ExecuteScalingRuleResponse
16387
+ * @summary Executes a scaling rule.
16388
+ *
16389
+ * @description Before you call this operation, take note of the following items:
16390
+ * * The scaling group is in the Active state.
16391
+ * * No scaling activities in the scaling group are in progress.
16392
+ * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
16393
+ * 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.
16394
+ * 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.
16395
+ * 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.
16396
+ * You can specify only a limited number of ECS instances in each adjustment. For more information, see the description of the AdjustmentValue parameter in the CreateScalingRule topic.
16397
+ *
16398
+ * @param request ExecuteScalingRuleRequest
16399
+ * @param runtime runtime options for this request RuntimeOptions
16400
+ * @return ExecuteScalingRuleResponse
15595
16401
  */
15596
16402
  async executeScalingRuleWithOptions(request, runtime) {
15597
16403
  tea_util_1.default.validateModel(request);
@@ -15640,22 +16446,34 @@ class Client extends openapi_client_1.default {
15640
16446
  return $tea.cast(await this.callApi(params, req, runtime), new ExecuteScalingRuleResponse({}));
15641
16447
  }
15642
16448
  /**
15643
- * Before you call this operation, take note of the following items:
15644
- * * The scaling group is in the Active state.
15645
- * * No scaling activities in the scaling group are in progress.
15646
- * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15647
- * 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.
15648
- * 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.
15649
- * 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.
15650
- * You can specify only a limited number of ECS instances in each adjustment. For more information, see the description of the AdjustmentValue parameter in the CreateScalingRule topic.
15651
- *
15652
- * @param request ExecuteScalingRuleRequest
15653
- * @return ExecuteScalingRuleResponse
16449
+ * @summary Executes a scaling rule.
16450
+ *
16451
+ * @description Before you call this operation, take note of the following items:
16452
+ * * The scaling group is in the Active state.
16453
+ * * No scaling activities in the scaling group are in progress.
16454
+ * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
16455
+ * 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.
16456
+ * 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.
16457
+ * 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.
16458
+ * You can specify only a limited number of ECS instances in each adjustment. For more information, see the description of the AdjustmentValue parameter in the CreateScalingRule topic.
16459
+ *
16460
+ * @param request ExecuteScalingRuleRequest
16461
+ * @return ExecuteScalingRuleResponse
15654
16462
  */
15655
16463
  async executeScalingRule(request) {
15656
16464
  let runtime = new $Util.RuntimeOptions({});
15657
16465
  return await this.executeScalingRuleWithOptions(request, runtime);
15658
16466
  }
16467
+ /**
16468
+ * @summary Moves an Elastic Compute Service (ECS) instance out of the Standby state.
16469
+ *
16470
+ * @description ## Description
16471
+ * If your scaling group is associated with a Classic Load Balancer (CLB) instance and you move an ECS instance in your scaling group out of the Standby state, the weight of the ECS instance is reset to the value that is specified in the scaling configuration of your scaling group.
16472
+ *
16473
+ * @param request ExitStandbyRequest
16474
+ * @param runtime runtime options for this request RuntimeOptions
16475
+ * @return ExitStandbyResponse
16476
+ */
15659
16477
  async exitStandbyWithOptions(request, runtime) {
15660
16478
  tea_util_1.default.validateModel(request);
15661
16479
  let query = {};
@@ -15696,10 +16514,26 @@ class Client extends openapi_client_1.default {
15696
16514
  });
15697
16515
  return $tea.cast(await this.callApi(params, req, runtime), new ExitStandbyResponse({}));
15698
16516
  }
16517
+ /**
16518
+ * @summary Moves an Elastic Compute Service (ECS) instance out of the Standby state.
16519
+ *
16520
+ * @description ## Description
16521
+ * If your scaling group is associated with a Classic Load Balancer (CLB) instance and you move an ECS instance in your scaling group out of the Standby state, the weight of the ECS instance is reset to the value that is specified in the scaling configuration of your scaling group.
16522
+ *
16523
+ * @param request ExitStandbyRequest
16524
+ * @return ExitStandbyResponse
16525
+ */
15699
16526
  async exitStandby(request) {
15700
16527
  let runtime = new $Util.RuntimeOptions({});
15701
16528
  return await this.exitStandbyWithOptions(request, runtime);
15702
16529
  }
16530
+ /**
16531
+ * @summary Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.
16532
+ *
16533
+ * @param request ListTagKeysRequest
16534
+ * @param runtime runtime options for this request RuntimeOptions
16535
+ * @return ListTagKeysResponse
16536
+ */
15703
16537
  async listTagKeysWithOptions(request, runtime) {
15704
16538
  tea_util_1.default.validateModel(request);
15705
16539
  let query = {};
@@ -15737,10 +16571,23 @@ class Client extends openapi_client_1.default {
15737
16571
  });
15738
16572
  return $tea.cast(await this.callApi(params, req, runtime), new ListTagKeysResponse({}));
15739
16573
  }
16574
+ /**
16575
+ * @summary Queries the tag keys added to Auto Scaling resources. Querying tag keys facilitates easier classification, identification, and monitoring of your Auto Scaling resources, thereby enhancing the flexibility and convenience of your resource management processes.
16576
+ *
16577
+ * @param request ListTagKeysRequest
16578
+ * @return ListTagKeysResponse
16579
+ */
15740
16580
  async listTagKeys(request) {
15741
16581
  let runtime = new $Util.RuntimeOptions({});
15742
16582
  return await this.listTagKeysWithOptions(request, runtime);
15743
16583
  }
16584
+ /**
16585
+ * @summary Queries tags that are added to one or more Auto Scaling resources.
16586
+ *
16587
+ * @param request ListTagResourcesRequest
16588
+ * @param runtime runtime options for this request RuntimeOptions
16589
+ * @return ListTagResourcesResponse
16590
+ */
15744
16591
  async listTagResourcesWithOptions(request, runtime) {
15745
16592
  tea_util_1.default.validateModel(request);
15746
16593
  let query = {};
@@ -15781,10 +16628,23 @@ class Client extends openapi_client_1.default {
15781
16628
  });
15782
16629
  return $tea.cast(await this.callApi(params, req, runtime), new ListTagResourcesResponse({}));
15783
16630
  }
16631
+ /**
16632
+ * @summary Queries tags that are added to one or more Auto Scaling resources.
16633
+ *
16634
+ * @param request ListTagResourcesRequest
16635
+ * @return ListTagResourcesResponse
16636
+ */
15784
16637
  async listTagResources(request) {
15785
16638
  let runtime = new $Util.RuntimeOptions({});
15786
16639
  return await this.listTagResourcesWithOptions(request, runtime);
15787
16640
  }
16641
+ /**
16642
+ * @summary Queries tag values.
16643
+ *
16644
+ * @param request ListTagValuesRequest
16645
+ * @param runtime runtime options for this request RuntimeOptions
16646
+ * @return ListTagValuesResponse
16647
+ */
15788
16648
  async listTagValuesWithOptions(request, runtime) {
15789
16649
  tea_util_1.default.validateModel(request);
15790
16650
  let query = {};
@@ -15825,20 +16685,28 @@ class Client extends openapi_client_1.default {
15825
16685
  });
15826
16686
  return $tea.cast(await this.callApi(params, req, runtime), new ListTagValuesResponse({}));
15827
16687
  }
16688
+ /**
16689
+ * @summary Queries tag values.
16690
+ *
16691
+ * @param request ListTagValuesRequest
16692
+ * @return ListTagValuesResponse
16693
+ */
15828
16694
  async listTagValues(request) {
15829
16695
  let runtime = new $Util.RuntimeOptions({});
15830
16696
  return await this.listTagValuesWithOptions(request, runtime);
15831
16697
  }
15832
16698
  /**
15833
- * * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Custom monitoring event-triggered tasks](~~74861~~).
15834
- * * 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.
15835
- * * If you set the MetricType parameter to custom, the valid values are your custom metrics.
15836
- * * For information about the metrics that are supported if you set the MetricType parameter to system, see[ Event-triggered task for system monitoring](~~74854~~).
15837
- * > 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.
15838
- *
15839
- * @param request ModifyAlarmRequest
15840
- * @param runtime runtime options for this request RuntimeOptions
15841
- * @return ModifyAlarmResponse
16699
+ * @summary Modifies an event-triggered task.
16700
+ *
16701
+ * @description * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
16702
+ * * 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.
16703
+ * * If you set the MetricType parameter to custom, the valid values are your custom metrics.
16704
+ * * For information about the metrics that are supported if you set the MetricType parameter to system, see[ Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
16705
+ * > 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.
16706
+ *
16707
+ * @param request ModifyAlarmRequest
16708
+ * @param runtime runtime options for this request RuntimeOptions
16709
+ * @return ModifyAlarmResponse
15842
16710
  */
15843
16711
  async modifyAlarmWithOptions(request, runtime) {
15844
16712
  tea_util_1.default.validateModel(request);
@@ -15917,25 +16785,29 @@ class Client extends openapi_client_1.default {
15917
16785
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyAlarmResponse({}));
15918
16786
  }
15919
16787
  /**
15920
- * * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Custom monitoring event-triggered tasks](~~74861~~).
15921
- * * 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.
15922
- * * If you set the MetricType parameter to custom, the valid values are your custom metrics.
15923
- * * For information about the metrics that are supported if you set the MetricType parameter to system, see[ Event-triggered task for system monitoring](~~74854~~).
15924
- * > 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.
15925
- *
15926
- * @param request ModifyAlarmRequest
15927
- * @return ModifyAlarmResponse
16788
+ * @summary Modifies an event-triggered task.
16789
+ *
16790
+ * @description * If you set the MetricType parameter to custom, you must report your custom metrics to CloudMonitor before you can create event-triggered tasks by using the custom metrics. For more information, see [Custom monitoring event-triggered tasks](https://help.aliyun.com/document_detail/74861.html).
16791
+ * * 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.
16792
+ * * If you set the MetricType parameter to custom, the valid values are your custom metrics.
16793
+ * * For information about the metrics that are supported if you set the MetricType parameter to system, see[ Event-triggered task for system monitoring](https://help.aliyun.com/document_detail/74854.html).
16794
+ * > 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.
16795
+ *
16796
+ * @param request ModifyAlarmRequest
16797
+ * @return ModifyAlarmResponse
15928
16798
  */
15929
16799
  async modifyAlarm(request) {
15930
16800
  let runtime = new $Util.RuntimeOptions({});
15931
16801
  return await this.modifyAlarmWithOptions(request, runtime);
15932
16802
  }
15933
16803
  /**
15934
- * 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.
15935
- *
15936
- * @param request ModifyEciScalingConfigurationRequest
15937
- * @param runtime runtime options for this request RuntimeOptions
15938
- * @return ModifyEciScalingConfigurationResponse
16804
+ * @summary Modifies a scaling configuration for a scaling group that contains elastic container instances.
16805
+ *
16806
+ * @description If you want to change the name of a scaling configuration in a scaling group, make sure that the new name is unique within the scaling group.
16807
+ *
16808
+ * @param request ModifyEciScalingConfigurationRequest
16809
+ * @param runtime runtime options for this request RuntimeOptions
16810
+ * @return ModifyEciScalingConfigurationResponse
15939
16811
  */
15940
16812
  async modifyEciScalingConfigurationWithOptions(request, runtime) {
15941
16813
  tea_util_1.default.validateModel(request);
@@ -16107,15 +16979,24 @@ class Client extends openapi_client_1.default {
16107
16979
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyEciScalingConfigurationResponse({}));
16108
16980
  }
16109
16981
  /**
16110
- * 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.
16111
- *
16112
- * @param request ModifyEciScalingConfigurationRequest
16113
- * @return ModifyEciScalingConfigurationResponse
16982
+ * @summary Modifies a scaling configuration for a scaling group that contains elastic container instances.
16983
+ *
16984
+ * @description If you want to change the name of a scaling configuration in a scaling group, make sure that the new name is unique within the scaling group.
16985
+ *
16986
+ * @param request ModifyEciScalingConfigurationRequest
16987
+ * @return ModifyEciScalingConfigurationResponse
16114
16988
  */
16115
16989
  async modifyEciScalingConfiguration(request) {
16116
16990
  let runtime = new $Util.RuntimeOptions({});
16117
16991
  return await this.modifyEciScalingConfigurationWithOptions(request, runtime);
16118
16992
  }
16993
+ /**
16994
+ * @summary Modifies the attributes of an Elastic Compute Service (ECS) instance in a scaling group. You can call the ModifyInstanceAttribute operation to modify the lifecycle management attribute of a manually added ECS instance in a scaling group.
16995
+ *
16996
+ * @param request ModifyInstanceAttributeRequest
16997
+ * @param runtime runtime options for this request RuntimeOptions
16998
+ * @return ModifyInstanceAttributeResponse
16999
+ */
16119
17000
  async modifyInstanceAttributeWithOptions(request, runtime) {
16120
17001
  tea_util_1.default.validateModel(request);
16121
17002
  let query = {};
@@ -16153,18 +17034,26 @@ class Client extends openapi_client_1.default {
16153
17034
  });
16154
17035
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyInstanceAttributeResponse({}));
16155
17036
  }
17037
+ /**
17038
+ * @summary Modifies the attributes of an Elastic Compute Service (ECS) instance in a scaling group. You can call the ModifyInstanceAttribute operation to modify the lifecycle management attribute of a manually added ECS instance in a scaling group.
17039
+ *
17040
+ * @param request ModifyInstanceAttributeRequest
17041
+ * @return ModifyInstanceAttributeResponse
17042
+ */
16156
17043
  async modifyInstanceAttribute(request) {
16157
17044
  let runtime = new $Util.RuntimeOptions({});
16158
17045
  return await this.modifyInstanceAttributeWithOptions(request, runtime);
16159
17046
  }
16160
17047
  /**
16161
- * You can use one of the following methods to specify the lifecycle hook that you want to modify:
16162
- * * Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
16163
- * * Specify the scaling group ID by using the ScalingGroupId parameter and specify the lifecycle hook name by using the LifecycleHookName parameter.
16164
- *
16165
- * @param request ModifyLifecycleHookRequest
16166
- * @param runtime runtime options for this request RuntimeOptions
16167
- * @return ModifyLifecycleHookResponse
17048
+ * @summary Modifies a lifecycle hook.
17049
+ *
17050
+ * @description You can use one of the following methods to specify the lifecycle hook that you want to modify:
17051
+ * * Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
17052
+ * * Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
17053
+ *
17054
+ * @param request ModifyLifecycleHookRequest
17055
+ * @param runtime runtime options for this request RuntimeOptions
17056
+ * @return ModifyLifecycleHookResponse
16168
17057
  */
16169
17058
  async modifyLifecycleHookWithOptions(request, runtime) {
16170
17059
  tea_util_1.default.validateModel(request);
@@ -16225,17 +17114,26 @@ class Client extends openapi_client_1.default {
16225
17114
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyLifecycleHookResponse({}));
16226
17115
  }
16227
17116
  /**
16228
- * You can use one of the following methods to specify the lifecycle hook that you want to modify:
16229
- * * Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
16230
- * * Specify the scaling group ID by using the ScalingGroupId parameter and specify the lifecycle hook name by using the LifecycleHookName parameter.
16231
- *
16232
- * @param request ModifyLifecycleHookRequest
16233
- * @return ModifyLifecycleHookResponse
17117
+ * @summary Modifies a lifecycle hook.
17118
+ *
17119
+ * @description You can use one of the following methods to specify the lifecycle hook that you want to modify:
17120
+ * * Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
17121
+ * * Specify the scaling group ID by using the ScalingGroupId parameter and the lifecycle hook name by using the LifecycleHookName parameter.
17122
+ *
17123
+ * @param request ModifyLifecycleHookRequest
17124
+ * @return ModifyLifecycleHookResponse
16234
17125
  */
16235
17126
  async modifyLifecycleHook(request) {
16236
17127
  let runtime = new $Util.RuntimeOptions({});
16237
17128
  return await this.modifyLifecycleHookWithOptions(request, runtime);
16238
17129
  }
17130
+ /**
17131
+ * @summary Modifies a notification.
17132
+ *
17133
+ * @param request ModifyNotificationConfigurationRequest
17134
+ * @param runtime runtime options for this request RuntimeOptions
17135
+ * @return ModifyNotificationConfigurationResponse
17136
+ */
16239
17137
  async modifyNotificationConfigurationWithOptions(request, runtime) {
16240
17138
  tea_util_1.default.validateModel(request);
16241
17139
  let query = {};
@@ -16273,16 +17171,24 @@ class Client extends openapi_client_1.default {
16273
17171
  });
16274
17172
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyNotificationConfigurationResponse({}));
16275
17173
  }
17174
+ /**
17175
+ * @summary Modifies a notification.
17176
+ *
17177
+ * @param request ModifyNotificationConfigurationRequest
17178
+ * @return ModifyNotificationConfigurationResponse
17179
+ */
16276
17180
  async modifyNotificationConfiguration(request) {
16277
17181
  let runtime = new $Util.RuntimeOptions({});
16278
17182
  return await this.modifyNotificationConfigurationWithOptions(request, runtime);
16279
17183
  }
16280
17184
  /**
16281
- * You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
16282
- *
16283
- * @param tmpReq ModifyScalingConfigurationRequest
16284
- * @param runtime runtime options for this request RuntimeOptions
16285
- * @return ModifyScalingConfigurationResponse
17185
+ * @summary Modifies a scaling configuration.
17186
+ *
17187
+ * @description You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
17188
+ *
17189
+ * @param tmpReq ModifyScalingConfigurationRequest
17190
+ * @param runtime runtime options for this request RuntimeOptions
17191
+ * @return ModifyScalingConfigurationResponse
16286
17192
  */
16287
17193
  async modifyScalingConfigurationWithOptions(tmpReq, runtime) {
16288
17194
  tea_util_1.default.validateModel(tmpReq);
@@ -16468,31 +17374,35 @@ class Client extends openapi_client_1.default {
16468
17374
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingConfigurationResponse({}));
16469
17375
  }
16470
17376
  /**
16471
- * You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
16472
- *
16473
- * @param request ModifyScalingConfigurationRequest
16474
- * @return ModifyScalingConfigurationResponse
17377
+ * @summary Modifies a scaling configuration.
17378
+ *
17379
+ * @description You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
17380
+ *
17381
+ * @param request ModifyScalingConfigurationRequest
17382
+ * @return ModifyScalingConfigurationResponse
16475
17383
  */
16476
17384
  async modifyScalingConfiguration(request) {
16477
17385
  let runtime = new $Util.RuntimeOptions({});
16478
17386
  return await this.modifyScalingConfigurationWithOptions(request, runtime);
16479
17387
  }
16480
17388
  /**
16481
- * * You cannot call this operation to modify the settings of the following parameters:
16482
- * * RegionId
16483
- * * LoadBalancerId
16484
- * > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
16485
- * * DBInstanceId
16486
- * > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
16487
- * * You can modify only scaling groups that are in the Active or Inactive state.
16488
- * * If you enable a new scaling configuration, Elastic Compute Service (ECS) instances that are created based on the previous scaling configuration still run as expected in the scaling group.
16489
- * * If the total number of instances in the scaling group is greater than the allowed maximum number after you change the value of the MaxSize parameter, Auto Scaling automatically removes instances from the scaling group to ensure that the number of instances is within the new range.
16490
- * * If the total number of instances in the scaling group is less than the allowed minimum number after you change the value of the MinSize parameter, Auto Scaling automatically adds instances to the scaling group to ensure that the number of instances is within the new range.
16491
- * * If the total number of instances in the scaling group does not match the expected number of instances after you change the value of the DesiredCapacity parameter, Auto Scaling automatically adds instances to or removes instances from the scaling group to ensure that the number of instances matches the value of the DesiredCapacity parameter.
16492
- *
16493
- * @param request ModifyScalingGroupRequest
16494
- * @param runtime runtime options for this request RuntimeOptions
16495
- * @return ModifyScalingGroupResponse
17389
+ * @summary Modifies a scaling group.
17390
+ *
17391
+ * @description * You cannot call this operation to modify the settings of the following parameters:
17392
+ * * RegionId
17393
+ * * LoadBalancerId
17394
+ * > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
17395
+ * * DBInstanceId
17396
+ * > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
17397
+ * * You can modify only scaling groups that are in the Active or Inactive state.
17398
+ * * If you enable a new scaling configuration, Elastic Compute Service (ECS) instances that are created based on the previous scaling configuration still run as expected in the scaling group.
17399
+ * * If the total number of instances in the scaling group is greater than the allowed maximum number after you change the value of the MaxSize parameter, Auto Scaling automatically removes instances from the scaling group to ensure that the number of instances is within the new range.
17400
+ * * If the total number of instances in the scaling group is less than the allowed minimum number after you change the value of the MinSize parameter, Auto Scaling automatically adds instances to the scaling group to ensure that the number of instances is within the new range.
17401
+ * * If the total number of instances in the scaling group does not match the expected number of instances after you change the value of the DesiredCapacity parameter, Auto Scaling automatically adds instances to or removes instances from the scaling group to ensure that the number of instances matches the value of the DesiredCapacity parameter.
17402
+ *
17403
+ * @param request ModifyScalingGroupRequest
17404
+ * @param runtime runtime options for this request RuntimeOptions
17405
+ * @return ModifyScalingGroupResponse
16496
17406
  */
16497
17407
  async modifyScalingGroupWithOptions(request, runtime) {
16498
17408
  tea_util_1.default.validateModel(request);
@@ -16610,25 +17520,34 @@ class Client extends openapi_client_1.default {
16610
17520
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingGroupResponse({}));
16611
17521
  }
16612
17522
  /**
16613
- * * You cannot call this operation to modify the settings of the following parameters:
16614
- * * RegionId
16615
- * * LoadBalancerId
16616
- * > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
16617
- * * DBInstanceId
16618
- * > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
16619
- * * You can modify only scaling groups that are in the Active or Inactive state.
16620
- * * If you enable a new scaling configuration, Elastic Compute Service (ECS) instances that are created based on the previous scaling configuration still run as expected in the scaling group.
16621
- * * If the total number of instances in the scaling group is greater than the allowed maximum number after you change the value of the MaxSize parameter, Auto Scaling automatically removes instances from the scaling group to ensure that the number of instances is within the new range.
16622
- * * If the total number of instances in the scaling group is less than the allowed minimum number after you change the value of the MinSize parameter, Auto Scaling automatically adds instances to the scaling group to ensure that the number of instances is within the new range.
16623
- * * If the total number of instances in the scaling group does not match the expected number of instances after you change the value of the DesiredCapacity parameter, Auto Scaling automatically adds instances to or removes instances from the scaling group to ensure that the number of instances matches the value of the DesiredCapacity parameter.
16624
- *
16625
- * @param request ModifyScalingGroupRequest
16626
- * @return ModifyScalingGroupResponse
17523
+ * @summary Modifies a scaling group.
17524
+ *
17525
+ * @description * You cannot call this operation to modify the settings of the following parameters:
17526
+ * * RegionId
17527
+ * * LoadBalancerId
17528
+ * > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
17529
+ * * DBInstanceId
17530
+ * > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
17531
+ * * You can modify only scaling groups that are in the Active or Inactive state.
17532
+ * * If you enable a new scaling configuration, Elastic Compute Service (ECS) instances that are created based on the previous scaling configuration still run as expected in the scaling group.
17533
+ * * If the total number of instances in the scaling group is greater than the allowed maximum number after you change the value of the MaxSize parameter, Auto Scaling automatically removes instances from the scaling group to ensure that the number of instances is within the new range.
17534
+ * * If the total number of instances in the scaling group is less than the allowed minimum number after you change the value of the MinSize parameter, Auto Scaling automatically adds instances to the scaling group to ensure that the number of instances is within the new range.
17535
+ * * If the total number of instances in the scaling group does not match the expected number of instances after you change the value of the DesiredCapacity parameter, Auto Scaling automatically adds instances to or removes instances from the scaling group to ensure that the number of instances matches the value of the DesiredCapacity parameter.
17536
+ *
17537
+ * @param request ModifyScalingGroupRequest
17538
+ * @return ModifyScalingGroupResponse
16627
17539
  */
16628
17540
  async modifyScalingGroup(request) {
16629
17541
  let runtime = new $Util.RuntimeOptions({});
16630
17542
  return await this.modifyScalingGroupWithOptions(request, runtime);
16631
17543
  }
17544
+ /**
17545
+ * @summary Modifies a scaling rule.
17546
+ *
17547
+ * @param request ModifyScalingRuleRequest
17548
+ * @param runtime runtime options for this request RuntimeOptions
17549
+ * @return ModifyScalingRuleResponse
17550
+ */
16632
17551
  async modifyScalingRuleWithOptions(request, runtime) {
16633
17552
  tea_util_1.default.validateModel(request);
16634
17553
  let query = {};
@@ -16717,19 +17636,27 @@ class Client extends openapi_client_1.default {
16717
17636
  });
16718
17637
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingRuleResponse({}));
16719
17638
  }
17639
+ /**
17640
+ * @summary Modifies a scaling rule.
17641
+ *
17642
+ * @param request ModifyScalingRuleRequest
17643
+ * @return ModifyScalingRuleResponse
17644
+ */
16720
17645
  async modifyScalingRule(request) {
16721
17646
  let runtime = new $Util.RuntimeOptions({});
16722
17647
  return await this.modifyScalingRuleWithOptions(request, runtime);
16723
17648
  }
16724
17649
  /**
16725
- * You can use the following parameters to specify the scaling method of a scheduled task:
16726
- * * If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
16727
- * * If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
16728
- * > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
16729
- *
16730
- * @param request ModifyScheduledTaskRequest
16731
- * @param runtime runtime options for this request RuntimeOptions
16732
- * @return ModifyScheduledTaskResponse
17650
+ * @summary Modifies a scheduled task.
17651
+ *
17652
+ * @description You can use the following parameters to specify the scaling method of a scheduled task:
17653
+ * * If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
17654
+ * * If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
17655
+ * > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
17656
+ *
17657
+ * @param request ModifyScheduledTaskRequest
17658
+ * @param runtime runtime options for this request RuntimeOptions
17659
+ * @return ModifyScheduledTaskResponse
16733
17660
  */
16734
17661
  async modifyScheduledTaskWithOptions(request, runtime) {
16735
17662
  tea_util_1.default.validateModel(request);
@@ -16805,18 +17732,35 @@ class Client extends openapi_client_1.default {
16805
17732
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyScheduledTaskResponse({}));
16806
17733
  }
16807
17734
  /**
16808
- * You can use the following parameters to specify the scaling method of a scheduled task:
16809
- * * If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
16810
- * * If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
16811
- * > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
16812
- *
16813
- * @param request ModifyScheduledTaskRequest
16814
- * @return ModifyScheduledTaskResponse
17735
+ * @summary Modifies a scheduled task.
17736
+ *
17737
+ * @description You can use the following parameters to specify the scaling method of a scheduled task:
17738
+ * * If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
17739
+ * * If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
17740
+ * > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
17741
+ *
17742
+ * @param request ModifyScheduledTaskRequest
17743
+ * @return ModifyScheduledTaskResponse
16815
17744
  */
16816
17745
  async modifyScheduledTask(request) {
16817
17746
  let runtime = new $Util.RuntimeOptions({});
16818
17747
  return await this.modifyScheduledTaskWithOptions(request, runtime);
16819
17748
  }
17749
+ /**
17750
+ * @summary Rebalances the distribution of Elastic Compute Service (ECS) instances across zones. If ECS instances are unevenly distributed across multiple zones, you can call the RebalanceInstances operation to rebalance the distribution of the ECS instances across the zones.
17751
+ *
17752
+ * @description ## [](#)Usage notes
17753
+ * Auto Scaling creates new ECS instances to replace the existing ECS instances to fulfill the rebalancing purpose. Auto Scaling starts the new ECS instances before stopping the existing ECS instances. The rebalancing operation does not affect the performance or service availability of your application.
17754
+ * * This operation is supported by only multi-zone scaling groups whose `MultiAZPolicy` is set to `BALANCE`.
17755
+ * * A rebalancing operation is required only when the distribution of the instances of a multi-zone scaling group is significantly unbalanced. In a rebalancing activity, Auto Scaling replaces up to 20 ECS instances to rectify the unbalanced distribution.
17756
+ * * During the execution of a rebalancing operation, if the number of instances in the scaling group approaches or hits the value of MaxSize but the rebalancing operation needs to continue, Auto Scaling allows the total number of ECS instances to momentarily exceed the value of MaxSize by 10%. This temporary surplus condition persists for a duration until equilibrium in the distribution of ECS instances is achieved. Typically, it takes 1 to 6 minutes.
17757
+ * **
17758
+ * **Note** If the 10% increment of the maximum number of instances in a scaling group yield a non-integer value, the decimal portion is always rounded up to ensure an additional instance is accounted for. For example, you have a scaling group that holds a maximum of 15 ECS instances. During a rebalancing operation, Auto Scaling would permit the total number of instances to momentarily surpass this limit by 2, instead of the calculated 10% (which is 1.5).
17759
+ *
17760
+ * @param request RebalanceInstancesRequest
17761
+ * @param runtime runtime options for this request RuntimeOptions
17762
+ * @return RebalanceInstancesResponse
17763
+ */
16820
17764
  async rebalanceInstancesWithOptions(request, runtime) {
16821
17765
  tea_util_1.default.validateModel(request);
16822
17766
  let query = {};
@@ -16854,16 +17798,32 @@ class Client extends openapi_client_1.default {
16854
17798
  });
16855
17799
  return $tea.cast(await this.callApi(params, req, runtime), new RebalanceInstancesResponse({}));
16856
17800
  }
17801
+ /**
17802
+ * @summary Rebalances the distribution of Elastic Compute Service (ECS) instances across zones. If ECS instances are unevenly distributed across multiple zones, you can call the RebalanceInstances operation to rebalance the distribution of the ECS instances across the zones.
17803
+ *
17804
+ * @description ## [](#)Usage notes
17805
+ * Auto Scaling creates new ECS instances to replace the existing ECS instances to fulfill the rebalancing purpose. Auto Scaling starts the new ECS instances before stopping the existing ECS instances. The rebalancing operation does not affect the performance or service availability of your application.
17806
+ * * This operation is supported by only multi-zone scaling groups whose `MultiAZPolicy` is set to `BALANCE`.
17807
+ * * A rebalancing operation is required only when the distribution of the instances of a multi-zone scaling group is significantly unbalanced. In a rebalancing activity, Auto Scaling replaces up to 20 ECS instances to rectify the unbalanced distribution.
17808
+ * * During the execution of a rebalancing operation, if the number of instances in the scaling group approaches or hits the value of MaxSize but the rebalancing operation needs to continue, Auto Scaling allows the total number of ECS instances to momentarily exceed the value of MaxSize by 10%. This temporary surplus condition persists for a duration until equilibrium in the distribution of ECS instances is achieved. Typically, it takes 1 to 6 minutes.
17809
+ * **
17810
+ * **Note** If the 10% increment of the maximum number of instances in a scaling group yield a non-integer value, the decimal portion is always rounded up to ensure an additional instance is accounted for. For example, you have a scaling group that holds a maximum of 15 ECS instances. During a rebalancing operation, Auto Scaling would permit the total number of instances to momentarily surpass this limit by 2, instead of the calculated 10% (which is 1.5).
17811
+ *
17812
+ * @param request RebalanceInstancesRequest
17813
+ * @return RebalanceInstancesResponse
17814
+ */
16857
17815
  async rebalanceInstances(request) {
16858
17816
  let runtime = new $Util.RuntimeOptions({});
16859
17817
  return await this.rebalanceInstancesWithOptions(request, runtime);
16860
17818
  }
16861
17819
  /**
16862
- * You can call this operation to prolong the length of a lifecycle hook up to 20 times. Take note that the total length of a lifecycle hook cannot exceed 6 hours.
16863
- *
16864
- * @param request RecordLifecycleActionHeartbeatRequest
16865
- * @param runtime runtime options for this request RuntimeOptions
16866
- * @return RecordLifecycleActionHeartbeatResponse
17820
+ * @summary Prolongs a lifecycle hook for Elastic Compute Service (ECS) instances.
17821
+ *
17822
+ * @description You can call this operation to prolong the length of a lifecycle hook up to 20 times. Take note that the total length of a lifecycle hook cannot exceed 6 hours.
17823
+ *
17824
+ * @param request RecordLifecycleActionHeartbeatRequest
17825
+ * @param runtime runtime options for this request RuntimeOptions
17826
+ * @return RecordLifecycleActionHeartbeatResponse
16867
17827
  */
16868
17828
  async recordLifecycleActionHeartbeatWithOptions(request, runtime) {
16869
17829
  tea_util_1.default.validateModel(request);
@@ -16906,28 +17866,32 @@ class Client extends openapi_client_1.default {
16906
17866
  return $tea.cast(await this.callApi(params, req, runtime), new RecordLifecycleActionHeartbeatResponse({}));
16907
17867
  }
16908
17868
  /**
16909
- * You can call this operation to prolong the length of a lifecycle hook up to 20 times. Take note that the total length of a lifecycle hook cannot exceed 6 hours.
16910
- *
16911
- * @param request RecordLifecycleActionHeartbeatRequest
16912
- * @return RecordLifecycleActionHeartbeatResponse
17869
+ * @summary Prolongs a lifecycle hook for Elastic Compute Service (ECS) instances.
17870
+ *
17871
+ * @description You can call this operation to prolong the length of a lifecycle hook up to 20 times. Take note that the total length of a lifecycle hook cannot exceed 6 hours.
17872
+ *
17873
+ * @param request RecordLifecycleActionHeartbeatRequest
17874
+ * @return RecordLifecycleActionHeartbeatResponse
16913
17875
  */
16914
17876
  async recordLifecycleActionHeartbeat(request) {
16915
17877
  let runtime = new $Util.RuntimeOptions({});
16916
17878
  return await this.recordLifecycleActionHeartbeatWithOptions(request, runtime);
16917
17879
  }
16918
17880
  /**
16919
- * * Before you call this operation, make sure that the following requirements are met:
16920
- * * The scaling group is in the Active state.
16921
- * * No scaling activity is in progress within the scaling group.
16922
- * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
16923
- * * 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.
16924
- * * 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.
16925
- * * 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.
16926
- * 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.
16927
- *
16928
- * @param request RemoveInstancesRequest
16929
- * @param runtime runtime options for this request RuntimeOptions
16930
- * @return RemoveInstancesResponse
17881
+ * @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
17882
+ *
17883
+ * @description * Before you call this operation, make sure that the following requirements are met:
17884
+ * * The scaling group is in the Active state.
17885
+ * * No scaling activity is in progress within the scaling group.
17886
+ * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
17887
+ * * 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.
17888
+ * * 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.
17889
+ * * 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.
17890
+ * 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.
17891
+ *
17892
+ * @param request RemoveInstancesRequest
17893
+ * @param runtime runtime options for this request RuntimeOptions
17894
+ * @return RemoveInstancesResponse
16931
17895
  */
16932
17896
  async removeInstancesWithOptions(request, runtime) {
16933
17897
  tea_util_1.default.validateModel(request);
@@ -16979,22 +17943,31 @@ class Client extends openapi_client_1.default {
16979
17943
  return $tea.cast(await this.callApi(params, req, runtime), new RemoveInstancesResponse({}));
16980
17944
  }
16981
17945
  /**
16982
- * * Before you call this operation, make sure that the following requirements are met:
16983
- * * The scaling group is in the Active state.
16984
- * * No scaling activity is in progress within the scaling group.
16985
- * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
16986
- * * 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.
16987
- * * 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.
16988
- * * 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.
16989
- * 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.
16990
- *
16991
- * @param request RemoveInstancesRequest
16992
- * @return RemoveInstancesResponse
17946
+ * @summary Removes one or more Elastic Compute Service (ECS) instances or elastic container instances from a scaling group.
17947
+ *
17948
+ * @description * Before you call this operation, make sure that the following requirements are met:
17949
+ * * The scaling group is in the Active state.
17950
+ * * No scaling activity is in progress within the scaling group.
17951
+ * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
17952
+ * * 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.
17953
+ * * 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.
17954
+ * * 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.
17955
+ * 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.
17956
+ *
17957
+ * @param request RemoveInstancesRequest
17958
+ * @return RemoveInstancesResponse
16993
17959
  */
16994
17960
  async removeInstances(request) {
16995
17961
  let runtime = new $Util.RuntimeOptions({});
16996
17962
  return await this.removeInstancesWithOptions(request, runtime);
16997
17963
  }
17964
+ /**
17965
+ * @summary Resumes suspended processes in a scaling group.
17966
+ *
17967
+ * @param request ResumeProcessesRequest
17968
+ * @param runtime runtime options for this request RuntimeOptions
17969
+ * @return ResumeProcessesResponse
17970
+ */
16998
17971
  async resumeProcessesWithOptions(request, runtime) {
16999
17972
  tea_util_1.default.validateModel(request);
17000
17973
  let query = {};
@@ -17032,23 +18005,31 @@ class Client extends openapi_client_1.default {
17032
18005
  });
17033
18006
  return $tea.cast(await this.callApi(params, req, runtime), new ResumeProcessesResponse({}));
17034
18007
  }
18008
+ /**
18009
+ * @summary Resumes suspended processes in a scaling group.
18010
+ *
18011
+ * @param request ResumeProcessesRequest
18012
+ * @return ResumeProcessesResponse
18013
+ */
17035
18014
  async resumeProcesses(request) {
17036
18015
  let runtime = new $Util.RuntimeOptions({});
17037
18016
  return await this.resumeProcessesWithOptions(request, runtime);
17038
18017
  }
17039
18018
  /**
17040
- * 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:
17041
- * * The following conditions must be met:
17042
- * * The scaling group is in the Active state.
17043
- * * No scaling activities in the scaling group are in progress.
17044
- * * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
17045
- * * 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.
17046
- * * 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.
17047
- * 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.
17048
- *
17049
- * @param tmpReq ScaleWithAdjustmentRequest
17050
- * @param runtime runtime options for this request RuntimeOptions
17051
- * @return ScaleWithAdjustmentResponse
18019
+ * @summary Scales instances in a scaling group based on the specified scaling policy.
18020
+ *
18021
+ * @description Compared with the ExecuteScalingRule operation, the ScaleWithAdjustment operation does not require a scaling rule to be created in advance. Before you call the ScaleWithAdjustment operation, take note of the following items:
18022
+ * * The following conditions must be met:
18023
+ * * The scaling group is in the Active state.
18024
+ * * No scaling activities in the scaling group are in progress.
18025
+ * * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
18026
+ * * 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.
18027
+ * * 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.
18028
+ * 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.
18029
+ *
18030
+ * @param tmpReq ScaleWithAdjustmentRequest
18031
+ * @param runtime runtime options for this request RuntimeOptions
18032
+ * @return ScaleWithAdjustmentResponse
17052
18033
  */
17053
18034
  async scaleWithAdjustmentWithOptions(tmpReq, runtime) {
17054
18035
  tea_util_1.default.validateModel(tmpReq);
@@ -17111,22 +18092,31 @@ class Client extends openapi_client_1.default {
17111
18092
  return $tea.cast(await this.callApi(params, req, runtime), new ScaleWithAdjustmentResponse({}));
17112
18093
  }
17113
18094
  /**
17114
- * 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:
17115
- * * The following conditions must be met:
17116
- * * The scaling group is in the Active state.
17117
- * * No scaling activities in the scaling group are in progress.
17118
- * * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
17119
- * * 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.
17120
- * * 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.
17121
- * 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.
17122
- *
17123
- * @param request ScaleWithAdjustmentRequest
17124
- * @return ScaleWithAdjustmentResponse
18095
+ * @summary Scales instances in a scaling group based on the specified scaling policy.
18096
+ *
18097
+ * @description Compared with the ExecuteScalingRule operation, the ScaleWithAdjustment operation does not require a scaling rule to be created in advance. Before you call the ScaleWithAdjustment operation, take note of the following items:
18098
+ * * The following conditions must be met:
18099
+ * * The scaling group is in the Active state.
18100
+ * * No scaling activities in the scaling group are in progress.
18101
+ * * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
18102
+ * * 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.
18103
+ * * 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.
18104
+ * 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.
18105
+ *
18106
+ * @param request ScaleWithAdjustmentRequest
18107
+ * @return ScaleWithAdjustmentResponse
17125
18108
  */
17126
18109
  async scaleWithAdjustment(request) {
17127
18110
  let runtime = new $Util.RuntimeOptions({});
17128
18111
  return await this.scaleWithAdjustmentWithOptions(request, runtime);
17129
18112
  }
18113
+ /**
18114
+ * @summary Sets deletion protection for a scaling group. If you enable deletion protection for a scaling group, you cannot delete the scaling group. If you disable deletion protection for a scaling group, you can directly delete the scaling group. You can call the SetGroupDeletionProtection operation to enable or disable deletion protection.
18115
+ *
18116
+ * @param request SetGroupDeletionProtectionRequest
18117
+ * @param runtime runtime options for this request RuntimeOptions
18118
+ * @return SetGroupDeletionProtectionResponse
18119
+ */
17130
18120
  async setGroupDeletionProtectionWithOptions(request, runtime) {
17131
18121
  tea_util_1.default.validateModel(request);
17132
18122
  let query = {};
@@ -17161,16 +18151,24 @@ class Client extends openapi_client_1.default {
17161
18151
  });
17162
18152
  return $tea.cast(await this.callApi(params, req, runtime), new SetGroupDeletionProtectionResponse({}));
17163
18153
  }
18154
+ /**
18155
+ * @summary Sets deletion protection for a scaling group. If you enable deletion protection for a scaling group, you cannot delete the scaling group. If you disable deletion protection for a scaling group, you can directly delete the scaling group. You can call the SetGroupDeletionProtection operation to enable or disable deletion protection.
18156
+ *
18157
+ * @param request SetGroupDeletionProtectionRequest
18158
+ * @return SetGroupDeletionProtectionResponse
18159
+ */
17164
18160
  async setGroupDeletionProtection(request) {
17165
18161
  let runtime = new $Util.RuntimeOptions({});
17166
18162
  return await this.setGroupDeletionProtectionWithOptions(request, runtime);
17167
18163
  }
17168
18164
  /**
17169
- * Configures the health check feature for Elastic Compute Service (ECS) instances.
17170
- *
17171
- * @param request SetInstanceHealthRequest
17172
- * @param runtime runtime options for this request RuntimeOptions
17173
- * @return SetInstanceHealthResponse
18165
+ * @summary Sets instance health. At times, the automatic health check system might not sufficiently determine the precise health status of your Elastic Compute Service (ECS) instances or elastic container instances. To overcome this, you can call the SetInstanceHealth operation to swiftly pinpoint problematic instances and resolve issues. This operation is designed to more precisely align with real-world business requirements and tackle O\\&M hurdles efficiently.
18166
+ *
18167
+ * @description Auto Scaling detects and removes unhealthy ECS instances or elastic container instances from the corresponding scaling groups. If you want to retain a specific instance in the corresponding scaling group, you can put the instance into the Standby or Protected state. For more information, see [EnterStandby](~~EnterStandby~~) and [SetInstancesProtection](~~SetInstancesProtection~~).
18168
+ *
18169
+ * @param request SetInstanceHealthRequest
18170
+ * @param runtime runtime options for this request RuntimeOptions
18171
+ * @return SetInstanceHealthResponse
17174
18172
  */
17175
18173
  async setInstanceHealthWithOptions(request, runtime) {
17176
18174
  tea_util_1.default.validateModel(request);
@@ -17204,21 +18202,29 @@ class Client extends openapi_client_1.default {
17204
18202
  return $tea.cast(await this.callApi(params, req, runtime), new SetInstanceHealthResponse({}));
17205
18203
  }
17206
18204
  /**
17207
- * Configures the health check feature for Elastic Compute Service (ECS) instances.
17208
- *
17209
- * @param request SetInstanceHealthRequest
17210
- * @return SetInstanceHealthResponse
18205
+ * @summary Sets instance health. At times, the automatic health check system might not sufficiently determine the precise health status of your Elastic Compute Service (ECS) instances or elastic container instances. To overcome this, you can call the SetInstanceHealth operation to swiftly pinpoint problematic instances and resolve issues. This operation is designed to more precisely align with real-world business requirements and tackle O\\&M hurdles efficiently.
18206
+ *
18207
+ * @description Auto Scaling detects and removes unhealthy ECS instances or elastic container instances from the corresponding scaling groups. If you want to retain a specific instance in the corresponding scaling group, you can put the instance into the Standby or Protected state. For more information, see [EnterStandby](~~EnterStandby~~) and [SetInstancesProtection](~~SetInstancesProtection~~).
18208
+ *
18209
+ * @param request SetInstanceHealthRequest
18210
+ * @return SetInstanceHealthResponse
17211
18211
  */
17212
18212
  async setInstanceHealth(request) {
17213
18213
  let runtime = new $Util.RuntimeOptions({});
17214
18214
  return await this.setInstanceHealthWithOptions(request, runtime);
17215
18215
  }
17216
18216
  /**
17217
- * Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
17218
- *
17219
- * @param request SetInstancesProtectionRequest
17220
- * @param runtime runtime options for this request RuntimeOptions
17221
- * @return SetInstancesProtectionResponse
18217
+ * @summary Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
18218
+ *
18219
+ * @description ## Description
18220
+ * Before you call this operation, take note of the following items:
18221
+ * * After you put an ECS instance into the Protected state, the ECS instance remains in the Protected state until you manually move the ECS instance out of the Protected state.
18222
+ * * After you put an ECS instance into the Protected state, Auto Scaling does not remove the ECS instance even if a scale-in activity caused by changes in instance quantity or event-triggered tasks occurs. In this case, you must manually move the ECS instance out of the Protected state and then release the ECS instance. For more information, see the "RemoveInstances" topic.
18223
+ * * After you put an ECS instance into the Protected state, Auto Scaling does not update the health status of the instance when the instance is stopped or restarted.
18224
+ *
18225
+ * @param request SetInstancesProtectionRequest
18226
+ * @param runtime runtime options for this request RuntimeOptions
18227
+ * @return SetInstancesProtectionResponse
17222
18228
  */
17223
18229
  async setInstancesProtectionWithOptions(request, runtime) {
17224
18230
  tea_util_1.default.validateModel(request);
@@ -17255,15 +18261,28 @@ class Client extends openapi_client_1.default {
17255
18261
  return $tea.cast(await this.callApi(params, req, runtime), new SetInstancesProtectionResponse({}));
17256
18262
  }
17257
18263
  /**
17258
- * Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
17259
- *
17260
- * @param request SetInstancesProtectionRequest
17261
- * @return SetInstancesProtectionResponse
18264
+ * @summary Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
18265
+ *
18266
+ * @description ## Description
18267
+ * Before you call this operation, take note of the following items:
18268
+ * * After you put an ECS instance into the Protected state, the ECS instance remains in the Protected state until you manually move the ECS instance out of the Protected state.
18269
+ * * After you put an ECS instance into the Protected state, Auto Scaling does not remove the ECS instance even if a scale-in activity caused by changes in instance quantity or event-triggered tasks occurs. In this case, you must manually move the ECS instance out of the Protected state and then release the ECS instance. For more information, see the "RemoveInstances" topic.
18270
+ * * After you put an ECS instance into the Protected state, Auto Scaling does not update the health status of the instance when the instance is stopped or restarted.
18271
+ *
18272
+ * @param request SetInstancesProtectionRequest
18273
+ * @return SetInstancesProtectionResponse
17262
18274
  */
17263
18275
  async setInstancesProtection(request) {
17264
18276
  let runtime = new $Util.RuntimeOptions({});
17265
18277
  return await this.setInstancesProtectionWithOptions(request, runtime);
17266
18278
  }
18279
+ /**
18280
+ * @summary Suspends processes in a scaling group.
18281
+ *
18282
+ * @param request SuspendProcessesRequest
18283
+ * @param runtime runtime options for this request RuntimeOptions
18284
+ * @return SuspendProcessesResponse
18285
+ */
17267
18286
  async suspendProcessesWithOptions(request, runtime) {
17268
18287
  tea_util_1.default.validateModel(request);
17269
18288
  let query = {};
@@ -17301,10 +18320,23 @@ class Client extends openapi_client_1.default {
17301
18320
  });
17302
18321
  return $tea.cast(await this.callApi(params, req, runtime), new SuspendProcessesResponse({}));
17303
18322
  }
18323
+ /**
18324
+ * @summary Suspends processes in a scaling group.
18325
+ *
18326
+ * @param request SuspendProcessesRequest
18327
+ * @return SuspendProcessesResponse
18328
+ */
17304
18329
  async suspendProcesses(request) {
17305
18330
  let runtime = new $Util.RuntimeOptions({});
17306
18331
  return await this.suspendProcessesWithOptions(request, runtime);
17307
18332
  }
18333
+ /**
18334
+ * @summary Adds tags to specified Auto Scaling resources.
18335
+ *
18336
+ * @param request TagResourcesRequest
18337
+ * @param runtime runtime options for this request RuntimeOptions
18338
+ * @return TagResourcesResponse
18339
+ */
17308
18340
  async tagResourcesWithOptions(request, runtime) {
17309
18341
  tea_util_1.default.validateModel(request);
17310
18342
  let query = {};
@@ -17342,10 +18374,23 @@ class Client extends openapi_client_1.default {
17342
18374
  });
17343
18375
  return $tea.cast(await this.callApi(params, req, runtime), new TagResourcesResponse({}));
17344
18376
  }
18377
+ /**
18378
+ * @summary Adds tags to specified Auto Scaling resources.
18379
+ *
18380
+ * @param request TagResourcesRequest
18381
+ * @return TagResourcesResponse
18382
+ */
17345
18383
  async tagResources(request) {
17346
18384
  let runtime = new $Util.RuntimeOptions({});
17347
18385
  return await this.tagResourcesWithOptions(request, runtime);
17348
18386
  }
18387
+ /**
18388
+ * @summary Removes tags from the specified Auto Scaling resources. If you remove a tag and the tag is not added to other resources, the tag is automatically deleted.
18389
+ *
18390
+ * @param request UntagResourcesRequest
18391
+ * @param runtime runtime options for this request RuntimeOptions
18392
+ * @return UntagResourcesResponse
18393
+ */
17349
18394
  async untagResourcesWithOptions(request, runtime) {
17350
18395
  tea_util_1.default.validateModel(request);
17351
18396
  let query = {};
@@ -17386,10 +18431,23 @@ class Client extends openapi_client_1.default {
17386
18431
  });
17387
18432
  return $tea.cast(await this.callApi(params, req, runtime), new UntagResourcesResponse({}));
17388
18433
  }
18434
+ /**
18435
+ * @summary Removes tags from the specified Auto Scaling resources. If you remove a tag and the tag is not added to other resources, the tag is automatically deleted.
18436
+ *
18437
+ * @param request UntagResourcesRequest
18438
+ * @return UntagResourcesResponse
18439
+ */
17389
18440
  async untagResources(request) {
17390
18441
  let runtime = new $Util.RuntimeOptions({});
17391
18442
  return await this.untagResourcesWithOptions(request, runtime);
17392
18443
  }
18444
+ /**
18445
+ * @summary Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
18446
+ *
18447
+ * @param request VerifyAuthenticationRequest
18448
+ * @param runtime runtime options for this request RuntimeOptions
18449
+ * @return VerifyAuthenticationResponse
18450
+ */
17393
18451
  async verifyAuthenticationWithOptions(request, runtime) {
17394
18452
  tea_util_1.default.validateModel(request);
17395
18453
  let query = {};
@@ -17424,10 +18482,23 @@ class Client extends openapi_client_1.default {
17424
18482
  });
17425
18483
  return $tea.cast(await this.callApi(params, req, runtime), new VerifyAuthenticationResponse({}));
17426
18484
  }
18485
+ /**
18486
+ * @summary Checks whether Auto Scaling is authorized to access Elastic Compute Service (ECS) and Elastic Container Instance resources.
18487
+ *
18488
+ * @param request VerifyAuthenticationRequest
18489
+ * @return VerifyAuthenticationResponse
18490
+ */
17427
18491
  async verifyAuthentication(request) {
17428
18492
  let runtime = new $Util.RuntimeOptions({});
17429
18493
  return await this.verifyAuthenticationWithOptions(request, runtime);
17430
18494
  }
18495
+ /**
18496
+ * @summary Checks whether Auto Scaling is activated.
18497
+ *
18498
+ * @param request VerifyUserRequest
18499
+ * @param runtime runtime options for this request RuntimeOptions
18500
+ * @return VerifyUserResponse
18501
+ */
17431
18502
  async verifyUserWithOptions(request, runtime) {
17432
18503
  tea_util_1.default.validateModel(request);
17433
18504
  let query = {};
@@ -17459,6 +18530,12 @@ class Client extends openapi_client_1.default {
17459
18530
  });
17460
18531
  return $tea.cast(await this.callApi(params, req, runtime), new VerifyUserResponse({}));
17461
18532
  }
18533
+ /**
18534
+ * @summary Checks whether Auto Scaling is activated.
18535
+ *
18536
+ * @param request VerifyUserRequest
18537
+ * @return VerifyUserResponse
18538
+ */
17462
18539
  async verifyUser(request) {
17463
18540
  let runtime = new $Util.RuntimeOptions({});
17464
18541
  return await this.verifyUserWithOptions(request, runtime);