@alicloud/ess20220222 1.3.1 → 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.DescribeEciScalingConfigurationsResponseBodyScalingConfigurationsSecurityContextSysCtls = 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.CreateScalingGroupRequestAlbServerGroups = exports.CreateScalingConfigurationShrinkRequestSpotPriceLimits = exports.CreateScalingConfigurationShrinkRequestNetworkInterfaces = exports.CreateScalingConfigurationShrinkRequestInstanceTypeOverrides = exports.CreateScalingConfigurationShrinkRequestInstancePatternInfos = exports.CreateScalingConfigurationShrinkRequestDataDisks = exports.CreateScalingConfigurationShrinkRequestCustomPriorities = exports.CreateScalingConfigurationShrinkRequestSystemDisk = void 0;
36
- exports.ModifyAlarmRequestDimensions = exports.ListTagResourcesResponseBodyTagResources = 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.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 = void 0;
37
- exports.ModifyScalingConfigurationShrinkRequestDataDisks = exports.ModifyScalingConfigurationShrinkRequestCustomPriorities = 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 = 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 = 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
  *
@@ -234,6 +234,7 @@ exports.AttachAlbServerGroupsResponse = AttachAlbServerGroupsResponse;
234
234
  class AttachDBInstancesRequest extends $tea.Model {
235
235
  static names() {
236
236
  return {
237
+ attachMode: 'AttachMode',
237
238
  clientToken: 'ClientToken',
238
239
  DBInstances: 'DBInstances',
239
240
  forceAttach: 'ForceAttach',
@@ -241,10 +242,12 @@ class AttachDBInstancesRequest extends $tea.Model {
241
242
  regionId: 'RegionId',
242
243
  resourceOwnerAccount: 'ResourceOwnerAccount',
243
244
  scalingGroupId: 'ScalingGroupId',
245
+ type: 'Type',
244
246
  };
245
247
  }
246
248
  static types() {
247
249
  return {
250
+ attachMode: 'string',
248
251
  clientToken: 'string',
249
252
  DBInstances: { 'type': 'array', 'itemType': 'string' },
250
253
  forceAttach: 'boolean',
@@ -252,6 +255,7 @@ class AttachDBInstancesRequest extends $tea.Model {
252
255
  regionId: 'string',
253
256
  resourceOwnerAccount: 'string',
254
257
  scalingGroupId: 'string',
258
+ type: 'string',
255
259
  };
256
260
  }
257
261
  constructor(map) {
@@ -1081,6 +1085,7 @@ class CreateScalingConfigurationRequest extends $tea.Model {
1081
1085
  creditSpecification: 'CreditSpecification',
1082
1086
  customPriorities: 'CustomPriorities',
1083
1087
  dataDisks: 'DataDisks',
1088
+ dedicatedHostClusterId: 'DedicatedHostClusterId',
1084
1089
  dedicatedHostId: 'DedicatedHostId',
1085
1090
  deletionProtection: 'DeletionProtection',
1086
1091
  deploymentSetId: 'DeploymentSetId',
@@ -1141,6 +1146,7 @@ class CreateScalingConfigurationRequest extends $tea.Model {
1141
1146
  creditSpecification: 'string',
1142
1147
  customPriorities: { 'type': 'array', 'itemType': CreateScalingConfigurationRequestCustomPriorities },
1143
1148
  dataDisks: { 'type': 'array', 'itemType': CreateScalingConfigurationRequestDataDisks },
1149
+ dedicatedHostClusterId: 'string',
1144
1150
  dedicatedHostId: 'string',
1145
1151
  deletionProtection: 'boolean',
1146
1152
  deploymentSetId: 'string',
@@ -1207,6 +1213,7 @@ class CreateScalingConfigurationShrinkRequest extends $tea.Model {
1207
1213
  creditSpecification: 'CreditSpecification',
1208
1214
  customPriorities: 'CustomPriorities',
1209
1215
  dataDisks: 'DataDisks',
1216
+ dedicatedHostClusterId: 'DedicatedHostClusterId',
1210
1217
  dedicatedHostId: 'DedicatedHostId',
1211
1218
  deletionProtection: 'DeletionProtection',
1212
1219
  deploymentSetId: 'DeploymentSetId',
@@ -1267,6 +1274,7 @@ class CreateScalingConfigurationShrinkRequest extends $tea.Model {
1267
1274
  creditSpecification: 'string',
1268
1275
  customPriorities: { 'type': 'array', 'itemType': CreateScalingConfigurationShrinkRequestCustomPriorities },
1269
1276
  dataDisks: { 'type': 'array', 'itemType': CreateScalingConfigurationShrinkRequestDataDisks },
1277
+ dedicatedHostClusterId: 'string',
1270
1278
  dedicatedHostId: 'string',
1271
1279
  deletionProtection: 'boolean',
1272
1280
  deploymentSetId: 'string',
@@ -1370,6 +1378,7 @@ class CreateScalingGroupRequest extends $tea.Model {
1370
1378
  containerGroupId: 'ContainerGroupId',
1371
1379
  customPolicyARN: 'CustomPolicyARN',
1372
1380
  DBInstanceIds: 'DBInstanceIds',
1381
+ DBInstances: 'DBInstances',
1373
1382
  defaultCooldown: 'DefaultCooldown',
1374
1383
  desiredCapacity: 'DesiredCapacity',
1375
1384
  groupDeletionProtection: 'GroupDeletionProtection',
@@ -1418,6 +1427,7 @@ class CreateScalingGroupRequest extends $tea.Model {
1418
1427
  containerGroupId: 'string',
1419
1428
  customPolicyARN: 'string',
1420
1429
  DBInstanceIds: 'string',
1430
+ DBInstances: { 'type': 'array', 'itemType': CreateScalingGroupRequestDBInstances },
1421
1431
  defaultCooldown: 'number',
1422
1432
  desiredCapacity: 'number',
1423
1433
  groupDeletionProtection: 'boolean',
@@ -2795,6 +2805,84 @@ class DescribeNotificationTypesResponse extends $tea.Model {
2795
2805
  }
2796
2806
  }
2797
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;
2798
2886
  class DescribeRegionsRequest extends $tea.Model {
2799
2887
  static names() {
2800
2888
  return {
@@ -3549,6 +3637,7 @@ class DetachDBInstancesRequest extends $tea.Model {
3549
3637
  forceDetach: 'ForceDetach',
3550
3638
  ownerId: 'OwnerId',
3551
3639
  regionId: 'RegionId',
3640
+ removeSecurityGroup: 'RemoveSecurityGroup',
3552
3641
  resourceOwnerAccount: 'ResourceOwnerAccount',
3553
3642
  scalingGroupId: 'ScalingGroupId',
3554
3643
  };
@@ -3560,6 +3649,7 @@ class DetachDBInstancesRequest extends $tea.Model {
3560
3649
  forceDetach: 'boolean',
3561
3650
  ownerId: 'number',
3562
3651
  regionId: 'string',
3652
+ removeSecurityGroup: 'boolean',
3563
3653
  resourceOwnerAccount: 'string',
3564
3654
  scalingGroupId: 'string',
3565
3655
  };
@@ -4982,6 +5072,7 @@ class ModifyScalingConfigurationRequest extends $tea.Model {
4982
5072
  creditSpecification: 'CreditSpecification',
4983
5073
  customPriorities: 'CustomPriorities',
4984
5074
  dataDisks: 'DataDisks',
5075
+ dedicatedHostClusterId: 'DedicatedHostClusterId',
4985
5076
  dedicatedHostId: 'DedicatedHostId',
4986
5077
  deletionProtection: 'DeletionProtection',
4987
5078
  deploymentSetId: 'DeploymentSetId',
@@ -5038,6 +5129,7 @@ class ModifyScalingConfigurationRequest extends $tea.Model {
5038
5129
  creditSpecification: 'string',
5039
5130
  customPriorities: { 'type': 'array', 'itemType': ModifyScalingConfigurationRequestCustomPriorities },
5040
5131
  dataDisks: { 'type': 'array', 'itemType': ModifyScalingConfigurationRequestDataDisks },
5132
+ dedicatedHostClusterId: 'string',
5041
5133
  dedicatedHostId: 'string',
5042
5134
  deletionProtection: 'boolean',
5043
5135
  deploymentSetId: 'string',
@@ -5100,6 +5192,7 @@ class ModifyScalingConfigurationShrinkRequest extends $tea.Model {
5100
5192
  creditSpecification: 'CreditSpecification',
5101
5193
  customPriorities: 'CustomPriorities',
5102
5194
  dataDisks: 'DataDisks',
5195
+ dedicatedHostClusterId: 'DedicatedHostClusterId',
5103
5196
  dedicatedHostId: 'DedicatedHostId',
5104
5197
  deletionProtection: 'DeletionProtection',
5105
5198
  deploymentSetId: 'DeploymentSetId',
@@ -5156,6 +5249,7 @@ class ModifyScalingConfigurationShrinkRequest extends $tea.Model {
5156
5249
  creditSpecification: 'string',
5157
5250
  customPriorities: { 'type': 'array', 'itemType': ModifyScalingConfigurationShrinkRequestCustomPriorities },
5158
5251
  dataDisks: { 'type': 'array', 'itemType': ModifyScalingConfigurationShrinkRequestDataDisks },
5252
+ dedicatedHostClusterId: 'string',
5159
5253
  dedicatedHostId: 'string',
5160
5254
  deletionProtection: 'boolean',
5161
5255
  deploymentSetId: 'string',
@@ -7729,6 +7823,26 @@ class CreateScalingGroupRequestAlbServerGroups extends $tea.Model {
7729
7823
  }
7730
7824
  }
7731
7825
  exports.CreateScalingGroupRequestAlbServerGroups = CreateScalingGroupRequestAlbServerGroups;
7826
+ class CreateScalingGroupRequestDBInstances extends $tea.Model {
7827
+ static names() {
7828
+ return {
7829
+ attachMode: 'AttachMode',
7830
+ DBInstanceId: 'DBInstanceId',
7831
+ type: 'Type',
7832
+ };
7833
+ }
7834
+ static types() {
7835
+ return {
7836
+ attachMode: 'string',
7837
+ DBInstanceId: 'string',
7838
+ type: 'string',
7839
+ };
7840
+ }
7841
+ constructor(map) {
7842
+ super(map);
7843
+ }
7844
+ }
7845
+ exports.CreateScalingGroupRequestDBInstances = CreateScalingGroupRequestDBInstances;
7732
7846
  class CreateScalingGroupRequestLaunchTemplateOverrides extends $tea.Model {
7733
7847
  static names() {
7734
7848
  return {
@@ -9255,6 +9369,30 @@ class DescribeNotificationConfigurationsResponseBodyNotificationConfigurationMod
9255
9369
  }
9256
9370
  }
9257
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;
9258
9396
  class DescribeRegionsResponseBodyRegions extends $tea.Model {
9259
9397
  static names() {
9260
9398
  return {
@@ -9538,6 +9676,7 @@ class DescribeScalingConfigurationsResponseBodyScalingConfigurations extends $te
9538
9676
  creditSpecification: 'CreditSpecification',
9539
9677
  customPriorities: 'CustomPriorities',
9540
9678
  dataDisks: 'DataDisks',
9679
+ dedicatedHostClusterId: 'DedicatedHostClusterId',
9541
9680
  dedicatedHostId: 'DedicatedHostId',
9542
9681
  deletionProtection: 'DeletionProtection',
9543
9682
  deploymentSetId: 'DeploymentSetId',
@@ -9609,6 +9748,7 @@ class DescribeScalingConfigurationsResponseBodyScalingConfigurations extends $te
9609
9748
  creditSpecification: 'string',
9610
9749
  customPriorities: { 'type': 'array', 'itemType': DescribeScalingConfigurationsResponseBodyScalingConfigurationsCustomPriorities },
9611
9750
  dataDisks: { 'type': 'array', 'itemType': DescribeScalingConfigurationsResponseBodyScalingConfigurationsDataDisks },
9751
+ dedicatedHostClusterId: 'string',
9612
9752
  dedicatedHostId: 'string',
9613
9753
  deletionProtection: 'boolean',
9614
9754
  deploymentSetId: 'string',
@@ -9985,6 +10125,26 @@ class DescribeScalingGroupsResponseBodyScalingGroupsAlbServerGroups extends $tea
9985
10125
  }
9986
10126
  }
9987
10127
  exports.DescribeScalingGroupsResponseBodyScalingGroupsAlbServerGroups = DescribeScalingGroupsResponseBodyScalingGroupsAlbServerGroups;
10128
+ class DescribeScalingGroupsResponseBodyScalingGroupsDBInstances extends $tea.Model {
10129
+ static names() {
10130
+ return {
10131
+ DBInstanceId: 'DBInstanceId',
10132
+ securityGroupIds: 'SecurityGroupIds',
10133
+ type: 'Type',
10134
+ };
10135
+ }
10136
+ static types() {
10137
+ return {
10138
+ DBInstanceId: 'string',
10139
+ securityGroupIds: { 'type': 'array', 'itemType': 'string' },
10140
+ type: 'string',
10141
+ };
10142
+ }
10143
+ constructor(map) {
10144
+ super(map);
10145
+ }
10146
+ }
10147
+ exports.DescribeScalingGroupsResponseBodyScalingGroupsDBInstances = DescribeScalingGroupsResponseBodyScalingGroupsDBInstances;
9988
10148
  class DescribeScalingGroupsResponseBodyScalingGroupsLaunchTemplateOverrides extends $tea.Model {
9989
10149
  static names() {
9990
10150
  return {
@@ -10116,6 +10276,7 @@ class DescribeScalingGroupsResponseBodyScalingGroups extends $tea.Model {
10116
10276
  currentHostName: 'CurrentHostName',
10117
10277
  customPolicyARN: 'CustomPolicyARN',
10118
10278
  DBInstanceIds: 'DBInstanceIds',
10279
+ DBInstances: 'DBInstances',
10119
10280
  defaultCooldown: 'DefaultCooldown',
10120
10281
  desiredCapacity: 'DesiredCapacity',
10121
10282
  enableDesiredCapacity: 'EnableDesiredCapacity',
@@ -10179,6 +10340,7 @@ class DescribeScalingGroupsResponseBodyScalingGroups extends $tea.Model {
10179
10340
  currentHostName: 'string',
10180
10341
  customPolicyARN: 'string',
10181
10342
  DBInstanceIds: { 'type': 'array', 'itemType': 'string' },
10343
+ DBInstances: { 'type': 'array', 'itemType': DescribeScalingGroupsResponseBodyScalingGroupsDBInstances },
10182
10344
  defaultCooldown: 'number',
10183
10345
  desiredCapacity: 'number',
10184
10346
  enableDesiredCapacity: 'boolean',
@@ -12083,6 +12245,16 @@ class Client extends openapi_client_1.default {
12083
12245
  }
12084
12246
  return endpoint_util_1.default.getEndpointRules(productId, regionId, endpointRule, network, suffix);
12085
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
+ */
12086
12258
  async applyEciScalingConfigurationWithOptions(request, runtime) {
12087
12259
  tea_util_1.default.validateModel(request);
12088
12260
  let query = {};
@@ -12117,10 +12289,60 @@ class Client extends openapi_client_1.default {
12117
12289
  });
12118
12290
  return $tea.cast(await this.callApi(params, req, runtime), new ApplyEciScalingConfigurationResponse({}));
12119
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
+ */
12120
12301
  async applyEciScalingConfiguration(request) {
12121
12302
  let runtime = new $Util.RuntimeOptions({});
12122
12303
  return await this.applyEciScalingConfigurationWithOptions(request, runtime);
12123
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
+ */
12124
12346
  async applyScalingGroupWithOptions(request, runtime) {
12125
12347
  tea_util_1.default.validateModel(request);
12126
12348
  let query = {};
@@ -12149,19 +12371,61 @@ class Client extends openapi_client_1.default {
12149
12371
  });
12150
12372
  return $tea.cast(await this.callApi(params, req, runtime), new ApplyScalingGroupResponse({}));
12151
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
+ */
12152
12414
  async applyScalingGroup(request) {
12153
12415
  let runtime = new $Util.RuntimeOptions({});
12154
12416
  return await this.applyScalingGroupWithOptions(request, runtime);
12155
12417
  }
12156
12418
  /**
12157
- * Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
12158
- * * The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
12159
- * * The ALB server group is in the Available state.
12160
- * * 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).
12161
- *
12162
- * @param request AttachAlbServerGroupsRequest
12163
- * @param runtime runtime options for this request RuntimeOptions
12164
- * @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
12165
12429
  */
12166
12430
  async attachAlbServerGroupsWithOptions(request, runtime) {
12167
12431
  tea_util_1.default.validateModel(request);
@@ -12204,32 +12468,39 @@ class Client extends openapi_client_1.default {
12204
12468
  return $tea.cast(await this.callApi(params, req, runtime), new AttachAlbServerGroupsResponse({}));
12205
12469
  }
12206
12470
  /**
12207
- * Before you associate an ALB server group with a scaling group, make sure that the following requirements are met:
12208
- * * The scaling group resides in a virtual private cloud (VPC). The scaling group and the ALB server group must reside in the same VPC.
12209
- * * The ALB server group is in the Available state.
12210
- * * 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).
12211
- *
12212
- * @param request AttachAlbServerGroupsRequest
12213
- * @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
12214
12480
  */
12215
12481
  async attachAlbServerGroups(request) {
12216
12482
  let runtime = new $Util.RuntimeOptions({});
12217
12483
  return await this.attachAlbServerGroupsWithOptions(request, runtime);
12218
12484
  }
12219
12485
  /**
12220
- * Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
12221
- * * The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
12222
- * * The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](~~41872~~).
12223
- * * The ApsaraDB RDS instance must be in the Running state.
12224
- * 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~~).
12225
- *
12226
- * @param request AttachDBInstancesRequest
12227
- * @param runtime runtime options for this request RuntimeOptions
12228
- * @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
12229
12497
  */
12230
12498
  async attachDBInstancesWithOptions(request, runtime) {
12231
12499
  tea_util_1.default.validateModel(request);
12232
12500
  let query = {};
12501
+ if (!tea_util_1.default.isUnset(request.attachMode)) {
12502
+ query["AttachMode"] = request.attachMode;
12503
+ }
12233
12504
  if (!tea_util_1.default.isUnset(request.clientToken)) {
12234
12505
  query["ClientToken"] = request.clientToken;
12235
12506
  }
@@ -12251,6 +12522,9 @@ class Client extends openapi_client_1.default {
12251
12522
  if (!tea_util_1.default.isUnset(request.scalingGroupId)) {
12252
12523
  query["ScalingGroupId"] = request.scalingGroupId;
12253
12524
  }
12525
+ if (!tea_util_1.default.isUnset(request.type)) {
12526
+ query["Type"] = request.type;
12527
+ }
12254
12528
  let req = new $OpenApi.OpenApiRequest({
12255
12529
  query: openapi_util_1.default.query(query),
12256
12530
  });
@@ -12268,38 +12542,42 @@ class Client extends openapi_client_1.default {
12268
12542
  return $tea.cast(await this.callApi(params, req, runtime), new AttachDBInstancesResponse({}));
12269
12543
  }
12270
12544
  /**
12271
- * Before you associate an ApsaraDB RDS instance with a scaling group, make sure that the ApsaraDB RDS instance meets the following requirements:
12272
- * * The ApsaraDB RDS instance and the scaling group must belong to the same Alibaba Cloud account.
12273
- * * The ApsaraDB RDS instance must be unlocked. For more information about the lock policy, see [ApsaraDB RDS usage notes](~~41872~~).
12274
- * * The ApsaraDB RDS instance must be in the Running state.
12275
- * 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~~).
12276
- *
12277
- * @param request AttachDBInstancesRequest
12278
- * @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
12279
12555
  */
12280
12556
  async attachDBInstances(request) {
12281
12557
  let runtime = new $Util.RuntimeOptions({});
12282
12558
  return await this.attachDBInstancesWithOptions(request, runtime);
12283
12559
  }
12284
12560
  /**
12285
- * Before you call this operation, take note of the following items:
12286
- * * The scaling group is in the Active state.
12287
- * * No scaling activities in the scaling group are in progress.
12288
- * The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
12289
- * * The instances reside in the same region as the scaling group.
12290
- * * The instances must be in the Running state.
12291
- * * The instances are not added to other scaling groups.
12292
- * * The instances use the subscription or pay-as-you-go billing method, or are preemptible instances.
12293
- * * 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.
12294
- * * If the VswitchID parameter is not specified for a scaling group, the instances that are in VPCs cannot be added to the scaling group.
12295
- * If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
12296
- * 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.
12297
- * 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.
12298
- * Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
12299
- *
12300
- * @param request AttachInstancesRequest
12301
- * @param runtime runtime options for this request RuntimeOptions
12302
- * @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
12303
12581
  */
12304
12582
  async attachInstancesWithOptions(request, runtime) {
12305
12583
  tea_util_1.default.validateModel(request);
@@ -12354,41 +12632,44 @@ class Client extends openapi_client_1.default {
12354
12632
  return $tea.cast(await this.callApi(params, req, runtime), new AttachInstancesResponse({}));
12355
12633
  }
12356
12634
  /**
12357
- * Before you call this operation, take note of the following items:
12358
- * * The scaling group is in the Active state.
12359
- * * No scaling activities in the scaling group are in progress.
12360
- * The ECS instances or the elastic container instances that you want to add to a scaling group must meet the following requirements:
12361
- * * The instances reside in the same region as the scaling group.
12362
- * * The instances must be in the Running state.
12363
- * * The instances are not added to other scaling groups.
12364
- * * The instances use the subscription or pay-as-you-go billing method, or are preemptible instances.
12365
- * * 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.
12366
- * * If the VswitchID parameter is not specified for a scaling group, the instances that are in VPCs cannot be added to the scaling group.
12367
- * If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
12368
- * 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.
12369
- * 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.
12370
- * Instances that are manually added by calling the AttachInstances operation are not associated with the active scaling configuration of the scaling group.
12371
- *
12372
- * @param request AttachInstancesRequest
12373
- * @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
12374
12654
  */
12375
12655
  async attachInstances(request) {
12376
12656
  let runtime = new $Util.RuntimeOptions({});
12377
12657
  return await this.attachInstancesWithOptions(request, runtime);
12378
12658
  }
12379
12659
  /**
12380
- * Before you call this operation to attach a CLB instance to your scaling group, take note of the following items:
12381
- * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12382
- * * The CLB instance and the scaling group must reside in the same region.
12383
- * * The CLB instance must be in the Running state.
12384
- * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12385
- * * The CLB instance and the scaling group must be in the same virtual private cloud (VPC) if their network type is VPC.
12386
- * * 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.
12387
- * * You can attach only a limited number of CLB instances to a scaling group. Fore more information, see [Limits](~~25863~~).
12388
- *
12389
- * @param request AttachLoadBalancersRequest
12390
- * @param runtime runtime options for this request RuntimeOptions
12391
- * @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
12392
12673
  */
12393
12674
  async attachLoadBalancersWithOptions(request, runtime) {
12394
12675
  tea_util_1.default.validateModel(request);
@@ -12434,22 +12715,30 @@ class Client extends openapi_client_1.default {
12434
12715
  return $tea.cast(await this.callApi(params, req, runtime), new AttachLoadBalancersResponse({}));
12435
12716
  }
12436
12717
  /**
12437
- * Before you call this operation to attach a CLB instance to your scaling group, take note of the following items:
12438
- * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12439
- * * The CLB instance and the scaling group must reside in the same region.
12440
- * * The CLB instance must be in the Running state.
12441
- * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12442
- * * The CLB instance and the scaling group must be in the same virtual private cloud (VPC) if their network type is VPC.
12443
- * * 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.
12444
- * * You can attach only a limited number of CLB instances to a scaling group. Fore more information, see [Limits](~~25863~~).
12445
- *
12446
- * @param request AttachLoadBalancersRequest
12447
- * @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
12448
12730
  */
12449
12731
  async attachLoadBalancers(request) {
12450
12732
  let runtime = new $Util.RuntimeOptions({});
12451
12733
  return await this.attachLoadBalancersWithOptions(request, runtime);
12452
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
+ */
12453
12742
  async attachServerGroupsWithOptions(request, runtime) {
12454
12743
  tea_util_1.default.validateModel(request);
12455
12744
  let query = {};
@@ -12490,29 +12779,37 @@ class Client extends openapi_client_1.default {
12490
12779
  });
12491
12780
  return $tea.cast(await this.callApi(params, req, runtime), new AttachServerGroupsResponse({}));
12492
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
+ */
12493
12788
  async attachServerGroups(request) {
12494
12789
  let runtime = new $Util.RuntimeOptions({});
12495
12790
  return await this.attachServerGroupsWithOptions(request, runtime);
12496
12791
  }
12497
12792
  /**
12498
- * Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
12499
- * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12500
- * * The CLB instance and the scaling group must reside in the same region.
12501
- * * The CLB instance must be in the Running state.
12502
- * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12503
- * * The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
12504
- * * 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.
12505
- * * The vServer group that you want to attach to your scaling group must belong to the CLB instance.
12506
- * * 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~~).
12507
- * When you call this operation, you must specify the following parameters:
12508
- * * LoadBalancerId: the ID of the CLB instance.
12509
- * * VServerGroupId: the ID of the vServer group.
12510
- * * Port: the port number of the vServer group.
12511
- * 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.
12512
- *
12513
- * @param request AttachVServerGroupsRequest
12514
- * @param runtime runtime options for this request RuntimeOptions
12515
- * @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
12516
12813
  */
12517
12814
  async attachVServerGroupsWithOptions(request, runtime) {
12518
12815
  tea_util_1.default.validateModel(request);
@@ -12555,28 +12852,37 @@ class Client extends openapi_client_1.default {
12555
12852
  return $tea.cast(await this.callApi(params, req, runtime), new AttachVServerGroupsResponse({}));
12556
12853
  }
12557
12854
  /**
12558
- * Before you call this operation to attach a vServer group to your scaling group, take note of the following items:
12559
- * * The CLB instance and the scaling group must belong to the same Alibaba Cloud account.
12560
- * * The CLB instance and the scaling group must reside in the same region.
12561
- * * The CLB instance must be in the Running state.
12562
- * * The CLB instance must be configured with at least one listener. Health check is enabled for the CLB instance.
12563
- * * The CLB instance and the scaling group must be in the same VPC if their network type is VPC.
12564
- * * 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.
12565
- * * The vServer group that you want to attach to your scaling group must belong to the CLB instance.
12566
- * * 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~~).
12567
- * When you call this operation, you must specify the following parameters:
12568
- * * LoadBalancerId: the ID of the CLB instance.
12569
- * * VServerGroupId: the ID of the vServer group.
12570
- * * Port: the port number of the vServer group.
12571
- * 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.
12572
- *
12573
- * @param request AttachVServerGroupsRequest
12574
- * @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
12575
12874
  */
12576
12875
  async attachVServerGroups(request) {
12577
12876
  let runtime = new $Util.RuntimeOptions({});
12578
12877
  return await this.attachVServerGroupsWithOptions(request, runtime);
12579
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
+ */
12580
12886
  async changeResourceGroupWithOptions(request, runtime) {
12581
12887
  tea_util_1.default.validateModel(request);
12582
12888
  let query = {};
@@ -12614,16 +12920,24 @@ class Client extends openapi_client_1.default {
12614
12920
  });
12615
12921
  return $tea.cast(await this.callApi(params, req, runtime), new ChangeResourceGroupResponse({}));
12616
12922
  }
12923
+ /**
12924
+ * @summary Adds a scaling group to a resource group.
12925
+ *
12926
+ * @param request ChangeResourceGroupRequest
12927
+ * @return ChangeResourceGroupResponse
12928
+ */
12617
12929
  async changeResourceGroup(request) {
12618
12930
  let runtime = new $Util.RuntimeOptions({});
12619
12931
  return await this.changeResourceGroupWithOptions(request, runtime);
12620
12932
  }
12621
12933
  /**
12622
- * 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.
12623
- *
12624
- * @param request CompleteLifecycleActionRequest
12625
- * @param runtime runtime options for this request RuntimeOptions
12626
- * @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
12627
12941
  */
12628
12942
  async completeLifecycleActionWithOptions(request, runtime) {
12629
12943
  tea_util_1.default.validateModel(request);
@@ -12669,15 +12983,30 @@ class Client extends openapi_client_1.default {
12669
12983
  return $tea.cast(await this.callApi(params, req, runtime), new CompleteLifecycleActionResponse({}));
12670
12984
  }
12671
12985
  /**
12672
- * 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.
12673
- *
12674
- * @param request CompleteLifecycleActionRequest
12675
- * @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
12676
12992
  */
12677
12993
  async completeLifecycleAction(request) {
12678
12994
  let runtime = new $Util.RuntimeOptions({});
12679
12995
  return await this.completeLifecycleActionWithOptions(request, runtime);
12680
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
+ */
12681
13010
  async createAlarmWithOptions(request, runtime) {
12682
13011
  tea_util_1.default.validateModel(request);
12683
13012
  let query = {};
@@ -12754,17 +13083,31 @@ class Client extends openapi_client_1.default {
12754
13083
  });
12755
13084
  return $tea.cast(await this.callApi(params, req, runtime), new CreateAlarmResponse({}));
12756
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
+ */
12757
13098
  async createAlarm(request) {
12758
13099
  let runtime = new $Util.RuntimeOptions({});
12759
13100
  return await this.createAlarmWithOptions(request, runtime);
12760
13101
  }
12761
13102
  /**
12762
- * A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
12763
- * 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.
12764
- *
12765
- * @param request CreateEciScalingConfigurationRequest
12766
- * @param runtime runtime options for this request RuntimeOptions
12767
- * @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
12768
13111
  */
12769
13112
  async createEciScalingConfigurationWithOptions(request, runtime) {
12770
13113
  tea_util_1.default.validateModel(request);
@@ -12933,25 +13276,29 @@ class Client extends openapi_client_1.default {
12933
13276
  return $tea.cast(await this.callApi(params, req, runtime), new CreateEciScalingConfigurationResponse({}));
12934
13277
  }
12935
13278
  /**
12936
- * A scaling configuration is a template that is used to create elastic container instances during scale-out activities.
12937
- * 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.
12938
- *
12939
- * @param request CreateEciScalingConfigurationRequest
12940
- * @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
12941
13286
  */
12942
13287
  async createEciScalingConfiguration(request) {
12943
13288
  let runtime = new $Util.RuntimeOptions({});
12944
13289
  return await this.createEciScalingConfigurationWithOptions(request, runtime);
12945
13290
  }
12946
13291
  /**
12947
- * 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.
12948
- * 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.
12949
- * 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~~).
12950
- * > 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.
12951
- *
12952
- * @param request CreateLifecycleHookRequest
12953
- * @param runtime runtime options for this request RuntimeOptions
12954
- * @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
12955
13302
  */
12956
13303
  async createLifecycleHookWithOptions(request, runtime) {
12957
13304
  tea_util_1.default.validateModel(request);
@@ -13003,25 +13350,29 @@ class Client extends openapi_client_1.default {
13003
13350
  return $tea.cast(await this.callApi(params, req, runtime), new CreateLifecycleHookResponse({}));
13004
13351
  }
13005
13352
  /**
13006
- * 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.
13007
- * 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.
13008
- * 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~~).
13009
- * > 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.
13010
- *
13011
- * @param request CreateLifecycleHookRequest
13012
- * @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
13013
13362
  */
13014
13363
  async createLifecycleHook(request) {
13015
13364
  let runtime = new $Util.RuntimeOptions({});
13016
13365
  return await this.createLifecycleHookWithOptions(request, runtime);
13017
13366
  }
13018
13367
  /**
13019
- * ## Description
13020
- * 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.
13021
- *
13022
- * @param request CreateNotificationConfigurationRequest
13023
- * @param runtime runtime options for this request RuntimeOptions
13024
- * @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
13025
13376
  */
13026
13377
  async createNotificationConfigurationWithOptions(request, runtime) {
13027
13378
  tea_util_1.default.validateModel(request);
@@ -13061,28 +13412,32 @@ class Client extends openapi_client_1.default {
13061
13412
  return $tea.cast(await this.callApi(params, req, runtime), new CreateNotificationConfigurationResponse({}));
13062
13413
  }
13063
13414
  /**
13064
- * ## Description
13065
- * 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.
13066
- *
13067
- * @param request CreateNotificationConfigurationRequest
13068
- * @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
13069
13422
  */
13070
13423
  async createNotificationConfiguration(request) {
13071
13424
  let runtime = new $Util.RuntimeOptions({});
13072
13425
  return await this.createNotificationConfigurationWithOptions(request, runtime);
13073
13426
  }
13074
13427
  /**
13075
- * Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
13076
- * * 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.
13077
- * * InstanceType: In this mode, you must specify one instance type.
13078
- * * InstanceTypes: In this mode, you can specify more than one instance type.
13079
- * * InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
13080
- * * 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.
13081
- * > 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.
13082
- *
13083
- * @param tmpReq CreateScalingConfigurationRequest
13084
- * @param runtime runtime options for this request RuntimeOptions
13085
- * @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
13086
13441
  */
13087
13442
  async createScalingConfigurationWithOptions(tmpReq, runtime) {
13088
13443
  tea_util_1.default.validateModel(tmpReq);
@@ -13110,6 +13465,9 @@ class Client extends openapi_client_1.default {
13110
13465
  if (!tea_util_1.default.isUnset(request.dataDisks)) {
13111
13466
  query["DataDisks"] = request.dataDisks;
13112
13467
  }
13468
+ if (!tea_util_1.default.isUnset(request.dedicatedHostClusterId)) {
13469
+ query["DedicatedHostClusterId"] = request.dedicatedHostClusterId;
13470
+ }
13113
13471
  if (!tea_util_1.default.isUnset(request.dedicatedHostId)) {
13114
13472
  query["DedicatedHostId"] = request.dedicatedHostId;
13115
13473
  }
@@ -13277,48 +13635,52 @@ class Client extends openapi_client_1.default {
13277
13635
  return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingConfigurationResponse({}));
13278
13636
  }
13279
13637
  /**
13280
- * Auto Scaling automatically creates Elastic Compute Service (ECS) instances based on the specified scaling configuration. ECS instances can be created in the following modes:
13281
- * * 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.
13282
- * * InstanceType: In this mode, you must specify one instance type.
13283
- * * InstanceTypes: In this mode, you can specify more than one instance type.
13284
- * * InstanceTypeOverrides: In this mode, you can specify multiple instance types and weights for the instance types.
13285
- * * 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.
13286
- * > 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.
13287
- *
13288
- * @param request CreateScalingConfigurationRequest
13289
- * @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
13290
13650
  */
13291
13651
  async createScalingConfiguration(request) {
13292
13652
  let runtime = new $Util.RuntimeOptions({});
13293
13653
  return await this.createScalingConfigurationWithOptions(request, runtime);
13294
13654
  }
13295
13655
  /**
13296
- * A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
13297
- * 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.
13298
- * 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.
13299
- * 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.
13300
- * 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:
13301
- * * 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.
13302
- * * 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.
13303
- * > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
13304
- * 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:
13305
- * * The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
13306
- * * 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.
13307
- * 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.
13308
- * 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:
13309
- * * 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.
13310
- * * 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.
13311
- * If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
13312
- * * 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.
13313
- * * 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.
13314
- * If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules apply:
13315
- * * 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.
13316
- * * 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.
13317
- * * 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.
13318
- *
13319
- * @param request CreateScalingGroupRequest
13320
- * @param runtime runtime options for this request RuntimeOptions
13321
- * @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
13322
13684
  */
13323
13685
  async createScalingGroupWithOptions(request, runtime) {
13324
13686
  tea_util_1.default.validateModel(request);
@@ -13347,6 +13709,9 @@ class Client extends openapi_client_1.default {
13347
13709
  if (!tea_util_1.default.isUnset(request.DBInstanceIds)) {
13348
13710
  query["DBInstanceIds"] = request.DBInstanceIds;
13349
13711
  }
13712
+ if (!tea_util_1.default.isUnset(request.DBInstances)) {
13713
+ query["DBInstances"] = request.DBInstances;
13714
+ }
13350
13715
  if (!tea_util_1.default.isUnset(request.defaultCooldown)) {
13351
13716
  query["DefaultCooldown"] = request.defaultCooldown;
13352
13717
  }
@@ -13472,54 +13837,58 @@ class Client extends openapi_client_1.default {
13472
13837
  return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingGroupResponse({}));
13473
13838
  }
13474
13839
  /**
13475
- * A scaling group is a group of Elastic Compute Service (ECS) instances that can be used in similar business scenarios.
13476
- * 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.
13477
- * 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.
13478
- * 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.
13479
- * 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:
13480
- * * 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.
13481
- * * 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.
13482
- * > If you specify the default server group and multiple vServer groups at the same time, ECS instances are added to all specified server groups.
13483
- * 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:
13484
- * * The CLB instance must be in the Active state. You can call the DescribeLoadBalancers operation to query the state of the CLB instance.
13485
- * * 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.
13486
- * 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.
13487
- * 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:
13488
- * * 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.
13489
- * * 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.
13490
- * If you set the MultiAZPolicy parameter of the scaling group to COST_OPTIMIZED, take note of the following items:
13491
- * * 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.
13492
- * * 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.
13493
- * If you set the `Tags.Propagate` parameter of the scaling group to true, the following rules apply:
13494
- * * 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.
13495
- * * 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.
13496
- * * 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.
13497
- *
13498
- * @param request CreateScalingGroupRequest
13499
- * @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
13500
13867
  */
13501
13868
  async createScalingGroup(request) {
13502
13869
  let runtime = new $Util.RuntimeOptions({});
13503
13870
  return await this.createScalingGroupWithOptions(request, runtime);
13504
13871
  }
13505
13872
  /**
13506
- * ## Description
13507
- * 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:
13508
- * * 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.
13509
- * * 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.
13510
- * Before you call this operation, take note of the following items:
13511
- * * 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.
13512
- * * 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.
13513
- * * 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.
13514
- * * 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.
13515
- * * You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
13516
- * * The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
13517
- * * 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.
13518
- * * 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.
13519
- *
13520
- * @param request CreateScalingRuleRequest
13521
- * @param runtime runtime options for this request RuntimeOptions
13522
- * @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
13523
13892
  */
13524
13893
  async createScalingRuleWithOptions(request, runtime) {
13525
13894
  tea_util_1.default.validateModel(request);
@@ -13613,38 +13982,42 @@ class Client extends openapi_client_1.default {
13613
13982
  return $tea.cast(await this.callApi(params, req, runtime), new CreateScalingRuleResponse({}));
13614
13983
  }
13615
13984
  /**
13616
- * ## Description
13617
- * 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:
13618
- * * 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.
13619
- * * 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.
13620
- * Before you call this operation, take note of the following items:
13621
- * * 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.
13622
- * * 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.
13623
- * * 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.
13624
- * * 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.
13625
- * * You can create only a limited number of scaling rules for a scaling group. For more information, see the "Limits" topic.
13626
- * * The unique identifier (ScalingRuleAri) of a scaling rule can be used by the following operations:
13627
- * * 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.
13628
- * * 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.
13629
- *
13630
- * @param request CreateScalingRuleRequest
13631
- * @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
13632
14003
  */
13633
14004
  async createScalingRule(request) {
13634
14005
  let runtime = new $Util.RuntimeOptions({});
13635
14006
  return await this.createScalingRuleWithOptions(request, runtime);
13636
14007
  }
13637
14008
  /**
13638
- * * 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.
13639
- * * 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.``
13640
- * * A scheduled task supports the following scaling methods:
13641
- * * `ScheduledAction`: Specify an existing scaling rule that you want Auto Scaling to execute when the scheduled task is triggered.
13642
- * * `ScalingGroupId`: Specify the minimum number, maximum number, or expected number of instances for the scaling group for which you created the scheduled task.
13643
- * > You cannot specify the `ScheduledAction` and ScalingGroupId parameters at the same time.
13644
- *
13645
- * @param request CreateScheduledTaskRequest
13646
- * @param runtime runtime options for this request RuntimeOptions
13647
- * @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
13648
14021
  */
13649
14022
  async createScheduledTaskWithOptions(request, runtime) {
13650
14023
  tea_util_1.default.validateModel(request);
@@ -13717,20 +14090,31 @@ class Client extends openapi_client_1.default {
13717
14090
  return $tea.cast(await this.callApi(params, req, runtime), new CreateScheduledTaskResponse({}));
13718
14091
  }
13719
14092
  /**
13720
- * * 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.
13721
- * * 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.``
13722
- * * A scheduled task supports the following scaling methods:
13723
- * * `ScheduledAction`: Specify an existing scaling rule that you want Auto Scaling to execute when the scheduled task is triggered.
13724
- * * `ScalingGroupId`: Specify the minimum number, maximum number, or expected number of instances for the scaling group for which you created the scheduled task.
13725
- * > You cannot specify the `ScheduledAction` and ScalingGroupId parameters at the same time.
13726
- *
13727
- * @param request CreateScheduledTaskRequest
13728
- * @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
13729
14104
  */
13730
14105
  async createScheduledTask(request) {
13731
14106
  let runtime = new $Util.RuntimeOptions({});
13732
14107
  return await this.createScheduledTaskWithOptions(request, runtime);
13733
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
+ */
13734
14118
  async deactivateScalingConfigurationWithOptions(request, runtime) {
13735
14119
  tea_util_1.default.validateModel(request);
13736
14120
  let query = {};
@@ -13762,10 +14146,25 @@ class Client extends openapi_client_1.default {
13762
14146
  });
13763
14147
  return $tea.cast(await this.callApi(params, req, runtime), new DeactivateScalingConfigurationResponse({}));
13764
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
+ */
13765
14157
  async deactivateScalingConfiguration(request) {
13766
14158
  let runtime = new $Util.RuntimeOptions({});
13767
14159
  return await this.deactivateScalingConfigurationWithOptions(request, runtime);
13768
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
+ */
13769
14168
  async deleteAlarmWithOptions(request, runtime) {
13770
14169
  tea_util_1.default.validateModel(request);
13771
14170
  let query = {};
@@ -13797,18 +14196,26 @@ class Client extends openapi_client_1.default {
13797
14196
  });
13798
14197
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteAlarmResponse({}));
13799
14198
  }
14199
+ /**
14200
+ * @summary Deletes an event-triggered task.
14201
+ *
14202
+ * @param request DeleteAlarmRequest
14203
+ * @return DeleteAlarmResponse
14204
+ */
13800
14205
  async deleteAlarm(request) {
13801
14206
  let runtime = new $Util.RuntimeOptions({});
13802
14207
  return await this.deleteAlarmWithOptions(request, runtime);
13803
14208
  }
13804
14209
  /**
13805
- * You cannot delete a scaling configuration that is used to create elastic container instances in the following scenarios:
13806
- * * The scaling configuration is in the Active state.
13807
- * * The scaling group contains elastic container instances that are created based on the scaling configuration.
13808
- *
13809
- * @param request DeleteEciScalingConfigurationRequest
13810
- * @param runtime runtime options for this request RuntimeOptions
13811
- * @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
13812
14219
  */
13813
14220
  async deleteEciScalingConfigurationWithOptions(request, runtime) {
13814
14221
  tea_util_1.default.validateModel(request);
@@ -13845,17 +14252,30 @@ class Client extends openapi_client_1.default {
13845
14252
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteEciScalingConfigurationResponse({}));
13846
14253
  }
13847
14254
  /**
13848
- * You cannot delete a scaling configuration that is used to create elastic container instances in the following scenarios:
13849
- * * The scaling configuration is in the Active state.
13850
- * * The scaling group contains elastic container instances that are created based on the scaling configuration.
13851
- *
13852
- * @param request DeleteEciScalingConfigurationRequest
13853
- * @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
13854
14263
  */
13855
14264
  async deleteEciScalingConfiguration(request) {
13856
14265
  let runtime = new $Util.RuntimeOptions({});
13857
14266
  return await this.deleteEciScalingConfigurationWithOptions(request, runtime);
13858
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
+ */
13859
14279
  async deleteLifecycleHookWithOptions(request, runtime) {
13860
14280
  tea_util_1.default.validateModel(request);
13861
14281
  let query = {};
@@ -13896,10 +14316,27 @@ class Client extends openapi_client_1.default {
13896
14316
  });
13897
14317
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteLifecycleHookResponse({}));
13898
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
+ */
13899
14329
  async deleteLifecycleHook(request) {
13900
14330
  let runtime = new $Util.RuntimeOptions({});
13901
14331
  return await this.deleteLifecycleHookWithOptions(request, runtime);
13902
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
+ */
13903
14340
  async deleteNotificationConfigurationWithOptions(request, runtime) {
13904
14341
  tea_util_1.default.validateModel(request);
13905
14342
  let query = {};
@@ -13934,18 +14371,26 @@ class Client extends openapi_client_1.default {
13934
14371
  });
13935
14372
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteNotificationConfigurationResponse({}));
13936
14373
  }
14374
+ /**
14375
+ * @summary Deletes a notification.
14376
+ *
14377
+ * @param request DeleteNotificationConfigurationRequest
14378
+ * @return DeleteNotificationConfigurationResponse
14379
+ */
13937
14380
  async deleteNotificationConfiguration(request) {
13938
14381
  let runtime = new $Util.RuntimeOptions({});
13939
14382
  return await this.deleteNotificationConfigurationWithOptions(request, runtime);
13940
14383
  }
13941
14384
  /**
13942
- * You cannot delete a scaling configuration in one of the following scenarios:
13943
- * * The scaling configuration in your scaling group is in the Active state.
13944
- * * The scaling group contains ECS instances that were created based on the scaling configuration.
13945
- *
13946
- * @param request DeleteScalingConfigurationRequest
13947
- * @param runtime runtime options for this request RuntimeOptions
13948
- * @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
13949
14394
  */
13950
14395
  async deleteScalingConfigurationWithOptions(request, runtime) {
13951
14396
  tea_util_1.default.validateModel(request);
@@ -13979,17 +14424,30 @@ class Client extends openapi_client_1.default {
13979
14424
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingConfigurationResponse({}));
13980
14425
  }
13981
14426
  /**
13982
- * You cannot delete a scaling configuration in one of the following scenarios:
13983
- * * The scaling configuration in your scaling group is in the Active state.
13984
- * * The scaling group contains ECS instances that were created based on the scaling configuration.
13985
- *
13986
- * @param request DeleteScalingConfigurationRequest
13987
- * @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
13988
14435
  */
13989
14436
  async deleteScalingConfiguration(request) {
13990
14437
  let runtime = new $Util.RuntimeOptions({});
13991
14438
  return await this.deleteScalingConfigurationWithOptions(request, runtime);
13992
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
+ */
13993
14451
  async deleteScalingGroupWithOptions(request, runtime) {
13994
14452
  tea_util_1.default.validateModel(request);
13995
14453
  let query = {};
@@ -14027,10 +14485,27 @@ class Client extends openapi_client_1.default {
14027
14485
  });
14028
14486
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingGroupResponse({}));
14029
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
+ */
14030
14498
  async deleteScalingGroup(request) {
14031
14499
  let runtime = new $Util.RuntimeOptions({});
14032
14500
  return await this.deleteScalingGroupWithOptions(request, runtime);
14033
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
+ */
14034
14509
  async deleteScalingRuleWithOptions(request, runtime) {
14035
14510
  tea_util_1.default.validateModel(request);
14036
14511
  let query = {};
@@ -14065,10 +14540,23 @@ class Client extends openapi_client_1.default {
14065
14540
  });
14066
14541
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteScalingRuleResponse({}));
14067
14542
  }
14543
+ /**
14544
+ * @summary Deletes a scaling rule.
14545
+ *
14546
+ * @param request DeleteScalingRuleRequest
14547
+ * @return DeleteScalingRuleResponse
14548
+ */
14068
14549
  async deleteScalingRule(request) {
14069
14550
  let runtime = new $Util.RuntimeOptions({});
14070
14551
  return await this.deleteScalingRuleWithOptions(request, runtime);
14071
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
+ */
14072
14560
  async deleteScheduledTaskWithOptions(request, runtime) {
14073
14561
  tea_util_1.default.validateModel(request);
14074
14562
  let query = {};
@@ -14103,10 +14591,23 @@ class Client extends openapi_client_1.default {
14103
14591
  });
14104
14592
  return $tea.cast(await this.callApi(params, req, runtime), new DeleteScheduledTaskResponse({}));
14105
14593
  }
14594
+ /**
14595
+ * @summary Deletes a scheduled task.
14596
+ *
14597
+ * @param request DeleteScheduledTaskRequest
14598
+ * @return DeleteScheduledTaskResponse
14599
+ */
14106
14600
  async deleteScheduledTask(request) {
14107
14601
  let runtime = new $Util.RuntimeOptions({});
14108
14602
  return await this.deleteScheduledTaskWithOptions(request, runtime);
14109
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
+ */
14110
14611
  async describeAlarmsWithOptions(request, runtime) {
14111
14612
  tea_util_1.default.validateModel(request);
14112
14613
  let query = {};
@@ -14159,10 +14660,23 @@ class Client extends openapi_client_1.default {
14159
14660
  });
14160
14661
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeAlarmsResponse({}));
14161
14662
  }
14663
+ /**
14664
+ * @summary Queries event-triggered tasks.
14665
+ *
14666
+ * @param request DescribeAlarmsRequest
14667
+ * @return DescribeAlarmsResponse
14668
+ */
14162
14669
  async describeAlarms(request) {
14163
14670
  let runtime = new $Util.RuntimeOptions({});
14164
14671
  return await this.describeAlarmsWithOptions(request, runtime);
14165
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
+ */
14166
14680
  async describeEciScalingConfigurationDetailWithOptions(request, runtime) {
14167
14681
  tea_util_1.default.validateModel(request);
14168
14682
  let query = {};
@@ -14194,10 +14708,23 @@ class Client extends openapi_client_1.default {
14194
14708
  });
14195
14709
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationDetailResponse({}));
14196
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
+ */
14197
14717
  async describeEciScalingConfigurationDetail(request) {
14198
14718
  let runtime = new $Util.RuntimeOptions({});
14199
14719
  return await this.describeEciScalingConfigurationDetailWithOptions(request, runtime);
14200
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
+ */
14201
14728
  async describeEciScalingConfigurationsWithOptions(request, runtime) {
14202
14729
  tea_util_1.default.validateModel(request);
14203
14730
  let query = {};
@@ -14247,20 +14774,28 @@ class Client extends openapi_client_1.default {
14247
14774
  });
14248
14775
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeEciScalingConfigurationsResponse({}));
14249
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
+ */
14250
14783
  async describeEciScalingConfigurations(request) {
14251
14784
  let runtime = new $Util.RuntimeOptions({});
14252
14785
  return await this.describeEciScalingConfigurationsWithOptions(request, runtime);
14253
14786
  }
14254
14787
  /**
14255
- * 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:
14256
- * * 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.
14257
- * * 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.
14258
- * * If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
14259
- * 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.
14260
- *
14261
- * @param request DescribeLifecycleActionsRequest
14262
- * @param runtime runtime options for this request RuntimeOptions
14263
- * @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
14264
14799
  */
14265
14800
  async describeLifecycleActionsWithOptions(request, runtime) {
14266
14801
  tea_util_1.default.validateModel(request);
@@ -14303,19 +14838,33 @@ class Client extends openapi_client_1.default {
14303
14838
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleActionsResponse({}));
14304
14839
  }
14305
14840
  /**
14306
- * 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:
14307
- * * 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.
14308
- * * 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.
14309
- * * If a lifecycle action is in the Completed state, you manually end the lifecycle hook that triggers the lifecycle action ahead of schedule.
14310
- * 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.
14311
- *
14312
- * @param request DescribeLifecycleActionsRequest
14313
- * @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
14314
14851
  */
14315
14852
  async describeLifecycleActions(request) {
14316
14853
  let runtime = new $Util.RuntimeOptions({});
14317
14854
  return await this.describeLifecycleActionsWithOptions(request, runtime);
14318
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
+ */
14319
14868
  async describeLifecycleHooksWithOptions(request, runtime) {
14320
14869
  tea_util_1.default.validateModel(request);
14321
14870
  let query = {};
@@ -14362,10 +14911,28 @@ class Client extends openapi_client_1.default {
14362
14911
  });
14363
14912
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeLifecycleHooksResponse({}));
14364
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
+ */
14365
14925
  async describeLifecycleHooks(request) {
14366
14926
  let runtime = new $Util.RuntimeOptions({});
14367
14927
  return await this.describeLifecycleHooksWithOptions(request, runtime);
14368
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
+ */
14369
14936
  async describeLimitationWithOptions(request, runtime) {
14370
14937
  tea_util_1.default.validateModel(request);
14371
14938
  let query = {};
@@ -14391,10 +14958,23 @@ class Client extends openapi_client_1.default {
14391
14958
  });
14392
14959
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeLimitationResponse({}));
14393
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
+ */
14394
14967
  async describeLimitation(request) {
14395
14968
  let runtime = new $Util.RuntimeOptions({});
14396
14969
  return await this.describeLimitationWithOptions(request, runtime);
14397
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
+ */
14398
14978
  async describeNotificationConfigurationsWithOptions(request, runtime) {
14399
14979
  tea_util_1.default.validateModel(request);
14400
14980
  let query = {};
@@ -14426,10 +15006,23 @@ class Client extends openapi_client_1.default {
14426
15006
  });
14427
15007
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationConfigurationsResponse({}));
14428
15008
  }
15009
+ /**
15010
+ * @summary Queries event notifications.
15011
+ *
15012
+ * @param request DescribeNotificationConfigurationsRequest
15013
+ * @return DescribeNotificationConfigurationsResponse
15014
+ */
14429
15015
  async describeNotificationConfigurations(request) {
14430
15016
  let runtime = new $Util.RuntimeOptions({});
14431
15017
  return await this.describeNotificationConfigurationsWithOptions(request, runtime);
14432
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
+ */
14433
15026
  async describeNotificationTypesWithOptions(request, runtime) {
14434
15027
  tea_util_1.default.validateModel(request);
14435
15028
  let query = {};
@@ -14455,10 +15048,59 @@ class Client extends openapi_client_1.default {
14455
15048
  });
14456
15049
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeNotificationTypesResponse({}));
14457
15050
  }
15051
+ /**
15052
+ * @summary Queries notification types.
15053
+ *
15054
+ * @param request DescribeNotificationTypesRequest
15055
+ * @return DescribeNotificationTypesResponse
15056
+ */
14458
15057
  async describeNotificationTypes(request) {
14459
15058
  let runtime = new $Util.RuntimeOptions({});
14460
15059
  return await this.describeNotificationTypesWithOptions(request, runtime);
14461
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
+ */
14462
15104
  async describeRegionsWithOptions(request, runtime) {
14463
15105
  tea_util_1.default.validateModel(request);
14464
15106
  let query = {};
@@ -14490,18 +15132,26 @@ class Client extends openapi_client_1.default {
14490
15132
  });
14491
15133
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeRegionsResponse({}));
14492
15134
  }
15135
+ /**
15136
+ * @summary Queries the regions in which Auto Scaling is available.
15137
+ *
15138
+ * @param request DescribeRegionsRequest
15139
+ * @return DescribeRegionsResponse
15140
+ */
14493
15141
  async describeRegions(request) {
14494
15142
  let runtime = new $Util.RuntimeOptions({});
14495
15143
  return await this.describeRegionsWithOptions(request, runtime);
14496
15144
  }
14497
15145
  /**
14498
- * You can specify a scaling group ID to query all scaling activities in the scaling group.
14499
- * You can filter query results based on the status of scaling activities.
14500
- * You can query scaling activities that are executed in the previous 30 days.
14501
- *
14502
- * @param request DescribeScalingActivitiesRequest
14503
- * @param runtime runtime options for this request RuntimeOptions
14504
- * @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
14505
15155
  */
14506
15156
  async describeScalingActivitiesWithOptions(request, runtime) {
14507
15157
  tea_util_1.default.validateModel(request);
@@ -14553,17 +15203,26 @@ class Client extends openapi_client_1.default {
14553
15203
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivitiesResponse({}));
14554
15204
  }
14555
15205
  /**
14556
- * You can specify a scaling group ID to query all scaling activities in the scaling group.
14557
- * You can filter query results based on the status of scaling activities.
14558
- * You can query scaling activities that are executed in the previous 30 days.
14559
- *
14560
- * @param request DescribeScalingActivitiesRequest
14561
- * @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
14562
15214
  */
14563
15215
  async describeScalingActivities(request) {
14564
15216
  let runtime = new $Util.RuntimeOptions({});
14565
15217
  return await this.describeScalingActivitiesWithOptions(request, runtime);
14566
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
+ */
14567
15226
  async describeScalingActivityDetailWithOptions(request, runtime) {
14568
15227
  tea_util_1.default.validateModel(request);
14569
15228
  let query = {};
@@ -14595,10 +15254,23 @@ class Client extends openapi_client_1.default {
14595
15254
  });
14596
15255
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingActivityDetailResponse({}));
14597
15256
  }
15257
+ /**
15258
+ * @summary Queries the details about a scaling activity.
15259
+ *
15260
+ * @param request DescribeScalingActivityDetailRequest
15261
+ * @return DescribeScalingActivityDetailResponse
15262
+ */
14598
15263
  async describeScalingActivityDetail(request) {
14599
15264
  let runtime = new $Util.RuntimeOptions({});
14600
15265
  return await this.describeScalingActivityDetailWithOptions(request, runtime);
14601
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
+ */
14602
15274
  async describeScalingConfigurationsWithOptions(request, runtime) {
14603
15275
  tea_util_1.default.validateModel(request);
14604
15276
  let query = {};
@@ -14648,10 +15320,23 @@ class Client extends openapi_client_1.default {
14648
15320
  });
14649
15321
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingConfigurationsResponse({}));
14650
15322
  }
15323
+ /**
15324
+ * @summary Queries scaling configurations.
15325
+ *
15326
+ * @param request DescribeScalingConfigurationsRequest
15327
+ * @return DescribeScalingConfigurationsResponse
15328
+ */
14651
15329
  async describeScalingConfigurations(request) {
14652
15330
  let runtime = new $Util.RuntimeOptions({});
14653
15331
  return await this.describeScalingConfigurationsWithOptions(request, runtime);
14654
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
+ */
14655
15340
  async describeScalingGroupDetailWithOptions(request, runtime) {
14656
15341
  tea_util_1.default.validateModel(request);
14657
15342
  let query = {};
@@ -14683,10 +15368,23 @@ class Client extends openapi_client_1.default {
14683
15368
  });
14684
15369
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupDetailResponse({}));
14685
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
+ */
14686
15377
  async describeScalingGroupDetail(request) {
14687
15378
  let runtime = new $Util.RuntimeOptions({});
14688
15379
  return await this.describeScalingGroupDetailWithOptions(request, runtime);
14689
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
+ */
14690
15388
  async describeScalingGroupsWithOptions(request, runtime) {
14691
15389
  tea_util_1.default.validateModel(request);
14692
15390
  let query = {};
@@ -14745,10 +15443,23 @@ class Client extends openapi_client_1.default {
14745
15443
  });
14746
15444
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingGroupsResponse({}));
14747
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
+ */
14748
15452
  async describeScalingGroups(request) {
14749
15453
  let runtime = new $Util.RuntimeOptions({});
14750
15454
  return await this.describeScalingGroupsWithOptions(request, runtime);
14751
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
+ */
14752
15463
  async describeScalingInstancesWithOptions(request, runtime) {
14753
15464
  tea_util_1.default.validateModel(request);
14754
15465
  let query = {};
@@ -14816,16 +15527,24 @@ class Client extends openapi_client_1.default {
14816
15527
  });
14817
15528
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingInstancesResponse({}));
14818
15529
  }
15530
+ /**
15531
+ * @summary Queries the Elastic Compute Service (ECS) instances in a scaling group
15532
+ *
15533
+ * @param request DescribeScalingInstancesRequest
15534
+ * @return DescribeScalingInstancesResponse
15535
+ */
14819
15536
  async describeScalingInstances(request) {
14820
15537
  let runtime = new $Util.RuntimeOptions({});
14821
15538
  return await this.describeScalingInstancesWithOptions(request, runtime);
14822
15539
  }
14823
15540
  /**
14824
- * 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.
14825
- *
14826
- * @param request DescribeScalingRulesRequest
14827
- * @param runtime runtime options for this request RuntimeOptions
14828
- * @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
14829
15548
  */
14830
15549
  async describeScalingRulesWithOptions(request, runtime) {
14831
15550
  tea_util_1.default.validateModel(request);
@@ -14886,15 +15605,26 @@ class Client extends openapi_client_1.default {
14886
15605
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScalingRulesResponse({}));
14887
15606
  }
14888
15607
  /**
14889
- * 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.
14890
- *
14891
- * @param request DescribeScalingRulesRequest
14892
- * @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
14893
15614
  */
14894
15615
  async describeScalingRules(request) {
14895
15616
  let runtime = new $Util.RuntimeOptions({});
14896
15617
  return await this.describeScalingRulesWithOptions(request, runtime);
14897
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
+ */
14898
15628
  async describeScheduledTasksWithOptions(request, runtime) {
14899
15629
  tea_util_1.default.validateModel(request);
14900
15630
  let query = {};
@@ -14947,10 +15677,25 @@ class Client extends openapi_client_1.default {
14947
15677
  });
14948
15678
  return $tea.cast(await this.callApi(params, req, runtime), new DescribeScheduledTasksResponse({}));
14949
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
+ */
14950
15688
  async describeScheduledTasks(request) {
14951
15689
  let runtime = new $Util.RuntimeOptions({});
14952
15690
  return await this.describeScheduledTasksWithOptions(request, runtime);
14953
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
+ */
14954
15699
  async detachAlbServerGroupsWithOptions(request, runtime) {
14955
15700
  tea_util_1.default.validateModel(request);
14956
15701
  let query = {};
@@ -14991,10 +15736,23 @@ class Client extends openapi_client_1.default {
14991
15736
  });
14992
15737
  return $tea.cast(await this.callApi(params, req, runtime), new DetachAlbServerGroupsResponse({}));
14993
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
+ */
14994
15745
  async detachAlbServerGroups(request) {
14995
15746
  let runtime = new $Util.RuntimeOptions({});
14996
15747
  return await this.detachAlbServerGroupsWithOptions(request, runtime);
14997
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
+ */
14998
15756
  async detachDBInstancesWithOptions(request, runtime) {
14999
15757
  tea_util_1.default.validateModel(request);
15000
15758
  let query = {};
@@ -15013,6 +15771,9 @@ class Client extends openapi_client_1.default {
15013
15771
  if (!tea_util_1.default.isUnset(request.regionId)) {
15014
15772
  query["RegionId"] = request.regionId;
15015
15773
  }
15774
+ if (!tea_util_1.default.isUnset(request.removeSecurityGroup)) {
15775
+ query["RemoveSecurityGroup"] = request.removeSecurityGroup;
15776
+ }
15016
15777
  if (!tea_util_1.default.isUnset(request.resourceOwnerAccount)) {
15017
15778
  query["ResourceOwnerAccount"] = request.resourceOwnerAccount;
15018
15779
  }
@@ -15035,23 +15796,31 @@ class Client extends openapi_client_1.default {
15035
15796
  });
15036
15797
  return $tea.cast(await this.callApi(params, req, runtime), new DetachDBInstancesResponse({}));
15037
15798
  }
15799
+ /**
15800
+ * @summary Disassociates one or more ApsaraDB RDS instances from a scaling group.
15801
+ *
15802
+ * @param request DetachDBInstancesRequest
15803
+ * @return DetachDBInstancesResponse
15804
+ */
15038
15805
  async detachDBInstances(request) {
15039
15806
  let runtime = new $Util.RuntimeOptions({});
15040
15807
  return await this.detachDBInstancesWithOptions(request, runtime);
15041
15808
  }
15042
15809
  /**
15043
- * 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.
15044
- * After you remove an ECS instance or elastic container instance by calling the DetachInstances operation, the instance is not stopped or released.
15045
- * Before you call this operation, make sure that the following conditions are met:
15046
- * * The specified scaling group is enabled.
15047
- * * No scaling activities in the specified scaling group are in progress.
15048
- * > If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15049
- * 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.
15050
- * 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.
15051
- *
15052
- * @param request DetachInstancesRequest
15053
- * @param runtime runtime options for this request RuntimeOptions
15054
- * @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
15055
15824
  */
15056
15825
  async detachInstancesWithOptions(request, runtime) {
15057
15826
  tea_util_1.default.validateModel(request);
@@ -15103,22 +15872,31 @@ class Client extends openapi_client_1.default {
15103
15872
  return $tea.cast(await this.callApi(params, req, runtime), new DetachInstancesResponse({}));
15104
15873
  }
15105
15874
  /**
15106
- * 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.
15107
- * After you remove an ECS instance or elastic container instance by calling the DetachInstances operation, the instance is not stopped or released.
15108
- * Before you call this operation, make sure that the following conditions are met:
15109
- * * The specified scaling group is enabled.
15110
- * * No scaling activities in the specified scaling group are in progress.
15111
- * > If no scaling activities in the specified scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15112
- * 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.
15113
- * 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.
15114
- *
15115
- * @param request DetachInstancesRequest
15116
- * @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
15117
15888
  */
15118
15889
  async detachInstances(request) {
15119
15890
  let runtime = new $Util.RuntimeOptions({});
15120
15891
  return await this.detachInstancesWithOptions(request, runtime);
15121
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
+ */
15122
15900
  async detachLoadBalancersWithOptions(request, runtime) {
15123
15901
  tea_util_1.default.validateModel(request);
15124
15902
  let query = {};
@@ -15162,10 +15940,23 @@ class Client extends openapi_client_1.default {
15162
15940
  });
15163
15941
  return $tea.cast(await this.callApi(params, req, runtime), new DetachLoadBalancersResponse({}));
15164
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
+ */
15165
15949
  async detachLoadBalancers(request) {
15166
15950
  let runtime = new $Util.RuntimeOptions({});
15167
15951
  return await this.detachLoadBalancersWithOptions(request, runtime);
15168
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
+ */
15169
15960
  async detachServerGroupsWithOptions(request, runtime) {
15170
15961
  tea_util_1.default.validateModel(request);
15171
15962
  let query = {};
@@ -15206,20 +15997,29 @@ class Client extends openapi_client_1.default {
15206
15997
  });
15207
15998
  return $tea.cast(await this.callApi(params, req, runtime), new DetachServerGroupsResponse({}));
15208
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
+ */
15209
16006
  async detachServerGroups(request) {
15210
16007
  let runtime = new $Util.RuntimeOptions({});
15211
16008
  return await this.detachServerGroupsWithOptions(request, runtime);
15212
16009
  }
15213
16010
  /**
15214
- * You can use the following parameters to specify the vServer groups that you want to detach from your scaling group.
15215
- * * LoadBalancerId: the ID of the Classic Load Balancer (CLB) instance.
15216
- * * VServerGroupId: the ID of the vServer group.
15217
- * * Port: the port number of the vServer group.
15218
- * 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.
15219
- *
15220
- * @param request DetachVServerGroupsRequest
15221
- * @param runtime runtime options for this request RuntimeOptions
15222
- * @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
15223
16023
  */
15224
16024
  async detachVServerGroupsWithOptions(request, runtime) {
15225
16025
  tea_util_1.default.validateModel(request);
@@ -15262,19 +16062,29 @@ class Client extends openapi_client_1.default {
15262
16062
  return $tea.cast(await this.callApi(params, req, runtime), new DetachVServerGroupsResponse({}));
15263
16063
  }
15264
16064
  /**
15265
- * You can use the following parameters to specify the vServer groups that you want to detach from your scaling group.
15266
- * * LoadBalancerId: the ID of the Classic Load Balancer (CLB) instance.
15267
- * * VServerGroupId: the ID of the vServer group.
15268
- * * Port: the port number of the vServer group.
15269
- * 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.
15270
- *
15271
- * @param request DetachVServerGroupsRequest
15272
- * @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
15273
16076
  */
15274
16077
  async detachVServerGroups(request) {
15275
16078
  let runtime = new $Util.RuntimeOptions({});
15276
16079
  return await this.detachVServerGroupsWithOptions(request, runtime);
15277
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
+ */
15278
16088
  async disableAlarmWithOptions(request, runtime) {
15279
16089
  tea_util_1.default.validateModel(request);
15280
16090
  let query = {};
@@ -15306,10 +16116,27 @@ class Client extends openapi_client_1.default {
15306
16116
  });
15307
16117
  return $tea.cast(await this.callApi(params, req, runtime), new DisableAlarmResponse({}));
15308
16118
  }
16119
+ /**
16120
+ * @summary Disables an event-triggered task.
16121
+ *
16122
+ * @param request DisableAlarmRequest
16123
+ * @return DisableAlarmResponse
16124
+ */
15309
16125
  async disableAlarm(request) {
15310
16126
  let runtime = new $Util.RuntimeOptions({});
15311
16127
  return await this.disableAlarmWithOptions(request, runtime);
15312
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
+ */
15313
16140
  async disableScalingGroupWithOptions(request, runtime) {
15314
16141
  tea_util_1.default.validateModel(request);
15315
16142
  let query = {};
@@ -15344,10 +16171,27 @@ class Client extends openapi_client_1.default {
15344
16171
  });
15345
16172
  return $tea.cast(await this.callApi(params, req, runtime), new DisableScalingGroupResponse({}));
15346
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
+ */
15347
16184
  async disableScalingGroup(request) {
15348
16185
  let runtime = new $Util.RuntimeOptions({});
15349
16186
  return await this.disableScalingGroupWithOptions(request, runtime);
15350
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
+ */
15351
16195
  async enableAlarmWithOptions(request, runtime) {
15352
16196
  tea_util_1.default.validateModel(request);
15353
16197
  let query = {};
@@ -15379,20 +16223,28 @@ class Client extends openapi_client_1.default {
15379
16223
  });
15380
16224
  return $tea.cast(await this.callApi(params, req, runtime), new EnableAlarmResponse({}));
15381
16225
  }
16226
+ /**
16227
+ * @summary Enables an event-triggered task.
16228
+ *
16229
+ * @param request EnableAlarmRequest
16230
+ * @return EnableAlarmResponse
16231
+ */
15382
16232
  async enableAlarm(request) {
15383
16233
  let runtime = new $Util.RuntimeOptions({});
15384
16234
  return await this.enableAlarmWithOptions(request, runtime);
15385
16235
  }
15386
16236
  /**
15387
- * 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.
15388
- * > 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.
15389
- * 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.
15390
- * * 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.
15391
- * * If the value of the TotalCapacity parameter is greater than the value of the MaxSize parameter, the call fails.
15392
- *
15393
- * @param request EnableScalingGroupRequest
15394
- * @param runtime runtime options for this request RuntimeOptions
15395
- * @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
15396
16248
  */
15397
16249
  async enableScalingGroupWithOptions(request, runtime) {
15398
16250
  tea_util_1.default.validateModel(request);
@@ -15450,19 +16302,34 @@ class Client extends openapi_client_1.default {
15450
16302
  return $tea.cast(await this.callApi(params, req, runtime), new EnableScalingGroupResponse({}));
15451
16303
  }
15452
16304
  /**
15453
- * 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.
15454
- * > 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.
15455
- * 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.
15456
- * * 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.
15457
- * * If the value of the TotalCapacity parameter is greater than the value of the MaxSize parameter, the call fails.
15458
- *
15459
- * @param request EnableScalingGroupRequest
15460
- * @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
15461
16315
  */
15462
16316
  async enableScalingGroup(request) {
15463
16317
  let runtime = new $Util.RuntimeOptions({});
15464
16318
  return await this.enableScalingGroupWithOptions(request, runtime);
15465
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
+ */
15466
16333
  async enterStandbyWithOptions(request, runtime) {
15467
16334
  tea_util_1.default.validateModel(request);
15468
16335
  let query = {};
@@ -15500,23 +16367,37 @@ class Client extends openapi_client_1.default {
15500
16367
  });
15501
16368
  return $tea.cast(await this.callApi(params, req, runtime), new EnterStandbyResponse({}));
15502
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
+ */
15503
16382
  async enterStandby(request) {
15504
16383
  let runtime = new $Util.RuntimeOptions({});
15505
16384
  return await this.enterStandbyWithOptions(request, runtime);
15506
16385
  }
15507
16386
  /**
15508
- * Before you call this operation, take note of the following items:
15509
- * * The scaling group is in the Active state.
15510
- * * No scaling activities in the scaling group are in progress.
15511
- * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15512
- * 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.
15513
- * 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.
15514
- * 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.
15515
- * 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.
15516
- *
15517
- * @param request ExecuteScalingRuleRequest
15518
- * @param runtime runtime options for this request RuntimeOptions
15519
- * @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
15520
16401
  */
15521
16402
  async executeScalingRuleWithOptions(request, runtime) {
15522
16403
  tea_util_1.default.validateModel(request);
@@ -15565,22 +16446,34 @@ class Client extends openapi_client_1.default {
15565
16446
  return $tea.cast(await this.callApi(params, req, runtime), new ExecuteScalingRuleResponse({}));
15566
16447
  }
15567
16448
  /**
15568
- * Before you call this operation, take note of the following items:
15569
- * * The scaling group is in the Active state.
15570
- * * No scaling activities in the scaling group are in progress.
15571
- * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
15572
- * 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.
15573
- * 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.
15574
- * 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.
15575
- * 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.
15576
- *
15577
- * @param request ExecuteScalingRuleRequest
15578
- * @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
15579
16462
  */
15580
16463
  async executeScalingRule(request) {
15581
16464
  let runtime = new $Util.RuntimeOptions({});
15582
16465
  return await this.executeScalingRuleWithOptions(request, runtime);
15583
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
+ */
15584
16477
  async exitStandbyWithOptions(request, runtime) {
15585
16478
  tea_util_1.default.validateModel(request);
15586
16479
  let query = {};
@@ -15621,10 +16514,26 @@ class Client extends openapi_client_1.default {
15621
16514
  });
15622
16515
  return $tea.cast(await this.callApi(params, req, runtime), new ExitStandbyResponse({}));
15623
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
+ */
15624
16526
  async exitStandby(request) {
15625
16527
  let runtime = new $Util.RuntimeOptions({});
15626
16528
  return await this.exitStandbyWithOptions(request, runtime);
15627
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
+ */
15628
16537
  async listTagKeysWithOptions(request, runtime) {
15629
16538
  tea_util_1.default.validateModel(request);
15630
16539
  let query = {};
@@ -15662,10 +16571,23 @@ class Client extends openapi_client_1.default {
15662
16571
  });
15663
16572
  return $tea.cast(await this.callApi(params, req, runtime), new ListTagKeysResponse({}));
15664
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
+ */
15665
16580
  async listTagKeys(request) {
15666
16581
  let runtime = new $Util.RuntimeOptions({});
15667
16582
  return await this.listTagKeysWithOptions(request, runtime);
15668
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
+ */
15669
16591
  async listTagResourcesWithOptions(request, runtime) {
15670
16592
  tea_util_1.default.validateModel(request);
15671
16593
  let query = {};
@@ -15706,10 +16628,23 @@ class Client extends openapi_client_1.default {
15706
16628
  });
15707
16629
  return $tea.cast(await this.callApi(params, req, runtime), new ListTagResourcesResponse({}));
15708
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
+ */
15709
16637
  async listTagResources(request) {
15710
16638
  let runtime = new $Util.RuntimeOptions({});
15711
16639
  return await this.listTagResourcesWithOptions(request, runtime);
15712
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
+ */
15713
16648
  async listTagValuesWithOptions(request, runtime) {
15714
16649
  tea_util_1.default.validateModel(request);
15715
16650
  let query = {};
@@ -15750,20 +16685,28 @@ class Client extends openapi_client_1.default {
15750
16685
  });
15751
16686
  return $tea.cast(await this.callApi(params, req, runtime), new ListTagValuesResponse({}));
15752
16687
  }
16688
+ /**
16689
+ * @summary Queries tag values.
16690
+ *
16691
+ * @param request ListTagValuesRequest
16692
+ * @return ListTagValuesResponse
16693
+ */
15753
16694
  async listTagValues(request) {
15754
16695
  let runtime = new $Util.RuntimeOptions({});
15755
16696
  return await this.listTagValuesWithOptions(request, runtime);
15756
16697
  }
15757
16698
  /**
15758
- * * 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~~).
15759
- * * 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.
15760
- * * If you set the MetricType parameter to custom, the valid values are your custom metrics.
15761
- * * For information about the metrics that are supported if you set the MetricType parameter to system, see[ Event-triggered task for system monitoring](~~74854~~).
15762
- * > 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.
15763
- *
15764
- * @param request ModifyAlarmRequest
15765
- * @param runtime runtime options for this request RuntimeOptions
15766
- * @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
15767
16710
  */
15768
16711
  async modifyAlarmWithOptions(request, runtime) {
15769
16712
  tea_util_1.default.validateModel(request);
@@ -15842,25 +16785,29 @@ class Client extends openapi_client_1.default {
15842
16785
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyAlarmResponse({}));
15843
16786
  }
15844
16787
  /**
15845
- * * 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~~).
15846
- * * 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.
15847
- * * If you set the MetricType parameter to custom, the valid values are your custom metrics.
15848
- * * For information about the metrics that are supported if you set the MetricType parameter to system, see[ Event-triggered task for system monitoring](~~74854~~).
15849
- * > 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.
15850
- *
15851
- * @param request ModifyAlarmRequest
15852
- * @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
15853
16798
  */
15854
16799
  async modifyAlarm(request) {
15855
16800
  let runtime = new $Util.RuntimeOptions({});
15856
16801
  return await this.modifyAlarmWithOptions(request, runtime);
15857
16802
  }
15858
16803
  /**
15859
- * 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.
15860
- *
15861
- * @param request ModifyEciScalingConfigurationRequest
15862
- * @param runtime runtime options for this request RuntimeOptions
15863
- * @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
15864
16811
  */
15865
16812
  async modifyEciScalingConfigurationWithOptions(request, runtime) {
15866
16813
  tea_util_1.default.validateModel(request);
@@ -16032,15 +16979,24 @@ class Client extends openapi_client_1.default {
16032
16979
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyEciScalingConfigurationResponse({}));
16033
16980
  }
16034
16981
  /**
16035
- * 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.
16036
- *
16037
- * @param request ModifyEciScalingConfigurationRequest
16038
- * @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
16039
16988
  */
16040
16989
  async modifyEciScalingConfiguration(request) {
16041
16990
  let runtime = new $Util.RuntimeOptions({});
16042
16991
  return await this.modifyEciScalingConfigurationWithOptions(request, runtime);
16043
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
+ */
16044
17000
  async modifyInstanceAttributeWithOptions(request, runtime) {
16045
17001
  tea_util_1.default.validateModel(request);
16046
17002
  let query = {};
@@ -16078,18 +17034,26 @@ class Client extends openapi_client_1.default {
16078
17034
  });
16079
17035
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyInstanceAttributeResponse({}));
16080
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
+ */
16081
17043
  async modifyInstanceAttribute(request) {
16082
17044
  let runtime = new $Util.RuntimeOptions({});
16083
17045
  return await this.modifyInstanceAttributeWithOptions(request, runtime);
16084
17046
  }
16085
17047
  /**
16086
- * You can use one of the following methods to specify the lifecycle hook that you want to modify:
16087
- * * Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
16088
- * * Specify the scaling group ID by using the ScalingGroupId parameter and specify the lifecycle hook name by using the LifecycleHookName parameter.
16089
- *
16090
- * @param request ModifyLifecycleHookRequest
16091
- * @param runtime runtime options for this request RuntimeOptions
16092
- * @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
16093
17057
  */
16094
17058
  async modifyLifecycleHookWithOptions(request, runtime) {
16095
17059
  tea_util_1.default.validateModel(request);
@@ -16150,17 +17114,26 @@ class Client extends openapi_client_1.default {
16150
17114
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyLifecycleHookResponse({}));
16151
17115
  }
16152
17116
  /**
16153
- * You can use one of the following methods to specify the lifecycle hook that you want to modify:
16154
- * * Specify the lifecycle hook ID by using the LifecycleHookId parameter. When you use this method, the ScalingGroupId and LifecycleHookName parameters are ignored.
16155
- * * Specify the scaling group ID by using the ScalingGroupId parameter and specify the lifecycle hook name by using the LifecycleHookName parameter.
16156
- *
16157
- * @param request ModifyLifecycleHookRequest
16158
- * @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
16159
17125
  */
16160
17126
  async modifyLifecycleHook(request) {
16161
17127
  let runtime = new $Util.RuntimeOptions({});
16162
17128
  return await this.modifyLifecycleHookWithOptions(request, runtime);
16163
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
+ */
16164
17137
  async modifyNotificationConfigurationWithOptions(request, runtime) {
16165
17138
  tea_util_1.default.validateModel(request);
16166
17139
  let query = {};
@@ -16198,16 +17171,24 @@ class Client extends openapi_client_1.default {
16198
17171
  });
16199
17172
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyNotificationConfigurationResponse({}));
16200
17173
  }
17174
+ /**
17175
+ * @summary Modifies a notification.
17176
+ *
17177
+ * @param request ModifyNotificationConfigurationRequest
17178
+ * @return ModifyNotificationConfigurationResponse
17179
+ */
16201
17180
  async modifyNotificationConfiguration(request) {
16202
17181
  let runtime = new $Util.RuntimeOptions({});
16203
17182
  return await this.modifyNotificationConfigurationWithOptions(request, runtime);
16204
17183
  }
16205
17184
  /**
16206
- * You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
16207
- *
16208
- * @param tmpReq ModifyScalingConfigurationRequest
16209
- * @param runtime runtime options for this request RuntimeOptions
16210
- * @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
16211
17192
  */
16212
17193
  async modifyScalingConfigurationWithOptions(tmpReq, runtime) {
16213
17194
  tea_util_1.default.validateModel(tmpReq);
@@ -16232,6 +17213,9 @@ class Client extends openapi_client_1.default {
16232
17213
  if (!tea_util_1.default.isUnset(request.dataDisks)) {
16233
17214
  query["DataDisks"] = request.dataDisks;
16234
17215
  }
17216
+ if (!tea_util_1.default.isUnset(request.dedicatedHostClusterId)) {
17217
+ query["DedicatedHostClusterId"] = request.dedicatedHostClusterId;
17218
+ }
16235
17219
  if (!tea_util_1.default.isUnset(request.dedicatedHostId)) {
16236
17220
  query["DedicatedHostId"] = request.dedicatedHostId;
16237
17221
  }
@@ -16390,31 +17374,35 @@ class Client extends openapi_client_1.default {
16390
17374
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingConfigurationResponse({}));
16391
17375
  }
16392
17376
  /**
16393
- * You can change the name of a scaling configuration in a scaling group. The name must be unique within the scaling group.
16394
- *
16395
- * @param request ModifyScalingConfigurationRequest
16396
- * @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
16397
17383
  */
16398
17384
  async modifyScalingConfiguration(request) {
16399
17385
  let runtime = new $Util.RuntimeOptions({});
16400
17386
  return await this.modifyScalingConfigurationWithOptions(request, runtime);
16401
17387
  }
16402
17388
  /**
16403
- * * You cannot call this operation to modify the settings of the following parameters:
16404
- * * RegionId
16405
- * * LoadBalancerId
16406
- * > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
16407
- * * DBInstanceId
16408
- * > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
16409
- * * You can modify only scaling groups that are in the Active or Inactive state.
16410
- * * 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.
16411
- * * 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.
16412
- * * 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.
16413
- * * 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.
16414
- *
16415
- * @param request ModifyScalingGroupRequest
16416
- * @param runtime runtime options for this request RuntimeOptions
16417
- * @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
16418
17406
  */
16419
17407
  async modifyScalingGroupWithOptions(request, runtime) {
16420
17408
  tea_util_1.default.validateModel(request);
@@ -16532,25 +17520,34 @@ class Client extends openapi_client_1.default {
16532
17520
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingGroupResponse({}));
16533
17521
  }
16534
17522
  /**
16535
- * * You cannot call this operation to modify the settings of the following parameters:
16536
- * * RegionId
16537
- * * LoadBalancerId
16538
- * > If you want to change the CLB instances that are associated with your scaling group, call the AttachLoadBalancers and DetachLoadBalancers operations.
16539
- * * DBInstanceId
16540
- * > If you want to change the ApsaraDB RDS instances that are associated with your scaling group, call the AttachDBInstances and DetachDBInstances operations.
16541
- * * You can modify only scaling groups that are in the Active or Inactive state.
16542
- * * 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.
16543
- * * 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.
16544
- * * 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.
16545
- * * 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.
16546
- *
16547
- * @param request ModifyScalingGroupRequest
16548
- * @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
16549
17539
  */
16550
17540
  async modifyScalingGroup(request) {
16551
17541
  let runtime = new $Util.RuntimeOptions({});
16552
17542
  return await this.modifyScalingGroupWithOptions(request, runtime);
16553
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
+ */
16554
17551
  async modifyScalingRuleWithOptions(request, runtime) {
16555
17552
  tea_util_1.default.validateModel(request);
16556
17553
  let query = {};
@@ -16639,19 +17636,27 @@ class Client extends openapi_client_1.default {
16639
17636
  });
16640
17637
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyScalingRuleResponse({}));
16641
17638
  }
17639
+ /**
17640
+ * @summary Modifies a scaling rule.
17641
+ *
17642
+ * @param request ModifyScalingRuleRequest
17643
+ * @return ModifyScalingRuleResponse
17644
+ */
16642
17645
  async modifyScalingRule(request) {
16643
17646
  let runtime = new $Util.RuntimeOptions({});
16644
17647
  return await this.modifyScalingRuleWithOptions(request, runtime);
16645
17648
  }
16646
17649
  /**
16647
- * You can use the following parameters to specify the scaling method of a scheduled task:
16648
- * * If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
16649
- * * If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
16650
- * > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
16651
- *
16652
- * @param request ModifyScheduledTaskRequest
16653
- * @param runtime runtime options for this request RuntimeOptions
16654
- * @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
16655
17660
  */
16656
17661
  async modifyScheduledTaskWithOptions(request, runtime) {
16657
17662
  tea_util_1.default.validateModel(request);
@@ -16727,18 +17732,35 @@ class Client extends openapi_client_1.default {
16727
17732
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyScheduledTaskResponse({}));
16728
17733
  }
16729
17734
  /**
16730
- * You can use the following parameters to specify the scaling method of a scheduled task:
16731
- * * If you use the `ScheduledAction` parameter, you must select an existing scaling rule for the scheduled task.
16732
- * * If you use the `ScalingGroupId` parameter, you must specify the minimum number, maximum number, or expected number of instances in the scheduled task.
16733
- * > You cannot specify the `ScheduledAction` and `ScalingGroupId` parameters at the same time.
16734
- *
16735
- * @param request ModifyScheduledTaskRequest
16736
- * @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
16737
17744
  */
16738
17745
  async modifyScheduledTask(request) {
16739
17746
  let runtime = new $Util.RuntimeOptions({});
16740
17747
  return await this.modifyScheduledTaskWithOptions(request, runtime);
16741
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
+ */
16742
17764
  async rebalanceInstancesWithOptions(request, runtime) {
16743
17765
  tea_util_1.default.validateModel(request);
16744
17766
  let query = {};
@@ -16776,16 +17798,32 @@ class Client extends openapi_client_1.default {
16776
17798
  });
16777
17799
  return $tea.cast(await this.callApi(params, req, runtime), new RebalanceInstancesResponse({}));
16778
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
+ */
16779
17815
  async rebalanceInstances(request) {
16780
17816
  let runtime = new $Util.RuntimeOptions({});
16781
17817
  return await this.rebalanceInstancesWithOptions(request, runtime);
16782
17818
  }
16783
17819
  /**
16784
- * 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.
16785
- *
16786
- * @param request RecordLifecycleActionHeartbeatRequest
16787
- * @param runtime runtime options for this request RuntimeOptions
16788
- * @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
16789
17827
  */
16790
17828
  async recordLifecycleActionHeartbeatWithOptions(request, runtime) {
16791
17829
  tea_util_1.default.validateModel(request);
@@ -16828,28 +17866,32 @@ class Client extends openapi_client_1.default {
16828
17866
  return $tea.cast(await this.callApi(params, req, runtime), new RecordLifecycleActionHeartbeatResponse({}));
16829
17867
  }
16830
17868
  /**
16831
- * 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.
16832
- *
16833
- * @param request RecordLifecycleActionHeartbeatRequest
16834
- * @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
16835
17875
  */
16836
17876
  async recordLifecycleActionHeartbeat(request) {
16837
17877
  let runtime = new $Util.RuntimeOptions({});
16838
17878
  return await this.recordLifecycleActionHeartbeatWithOptions(request, runtime);
16839
17879
  }
16840
17880
  /**
16841
- * * Before you call this operation, make sure that the following requirements are met:
16842
- * * The scaling group is in the Active state.
16843
- * * No scaling activity is in progress within the scaling group.
16844
- * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
16845
- * * 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.
16846
- * * 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.
16847
- * * 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.
16848
- * 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.
16849
- *
16850
- * @param request RemoveInstancesRequest
16851
- * @param runtime runtime options for this request RuntimeOptions
16852
- * @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
16853
17895
  */
16854
17896
  async removeInstancesWithOptions(request, runtime) {
16855
17897
  tea_util_1.default.validateModel(request);
@@ -16901,22 +17943,31 @@ class Client extends openapi_client_1.default {
16901
17943
  return $tea.cast(await this.callApi(params, req, runtime), new RemoveInstancesResponse({}));
16902
17944
  }
16903
17945
  /**
16904
- * * Before you call this operation, make sure that the following requirements are met:
16905
- * * The scaling group is in the Active state.
16906
- * * No scaling activity is in progress within the scaling group.
16907
- * > If no scaling activity is in progress within the scaling group, you can call the operation even within the cooldown period.
16908
- * * 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.
16909
- * * 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.
16910
- * * 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.
16911
- * 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.
16912
- *
16913
- * @param request RemoveInstancesRequest
16914
- * @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
16915
17959
  */
16916
17960
  async removeInstances(request) {
16917
17961
  let runtime = new $Util.RuntimeOptions({});
16918
17962
  return await this.removeInstancesWithOptions(request, runtime);
16919
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
+ */
16920
17971
  async resumeProcessesWithOptions(request, runtime) {
16921
17972
  tea_util_1.default.validateModel(request);
16922
17973
  let query = {};
@@ -16954,23 +18005,31 @@ class Client extends openapi_client_1.default {
16954
18005
  });
16955
18006
  return $tea.cast(await this.callApi(params, req, runtime), new ResumeProcessesResponse({}));
16956
18007
  }
18008
+ /**
18009
+ * @summary Resumes suspended processes in a scaling group.
18010
+ *
18011
+ * @param request ResumeProcessesRequest
18012
+ * @return ResumeProcessesResponse
18013
+ */
16957
18014
  async resumeProcesses(request) {
16958
18015
  let runtime = new $Util.RuntimeOptions({});
16959
18016
  return await this.resumeProcessesWithOptions(request, runtime);
16960
18017
  }
16961
18018
  /**
16962
- * 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:
16963
- * * The following conditions must be met:
16964
- * * The scaling group is in the Active state.
16965
- * * No scaling activities in the scaling group are in progress.
16966
- * * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
16967
- * * 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.
16968
- * * 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.
16969
- * 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.
16970
- *
16971
- * @param tmpReq ScaleWithAdjustmentRequest
16972
- * @param runtime runtime options for this request RuntimeOptions
16973
- * @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
16974
18033
  */
16975
18034
  async scaleWithAdjustmentWithOptions(tmpReq, runtime) {
16976
18035
  tea_util_1.default.validateModel(tmpReq);
@@ -17033,22 +18092,31 @@ class Client extends openapi_client_1.default {
17033
18092
  return $tea.cast(await this.callApi(params, req, runtime), new ScaleWithAdjustmentResponse({}));
17034
18093
  }
17035
18094
  /**
17036
- * 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:
17037
- * * The following conditions must be met:
17038
- * * The scaling group is in the Active state.
17039
- * * No scaling activities in the scaling group are in progress.
17040
- * * If no scaling activities in the scaling group are in progress, the operation can trigger scaling activities even before the cooldown time expires.
17041
- * * 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.
17042
- * * 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.
17043
- * 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.
17044
- *
17045
- * @param request ScaleWithAdjustmentRequest
17046
- * @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
17047
18108
  */
17048
18109
  async scaleWithAdjustment(request) {
17049
18110
  let runtime = new $Util.RuntimeOptions({});
17050
18111
  return await this.scaleWithAdjustmentWithOptions(request, runtime);
17051
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
+ */
17052
18120
  async setGroupDeletionProtectionWithOptions(request, runtime) {
17053
18121
  tea_util_1.default.validateModel(request);
17054
18122
  let query = {};
@@ -17083,16 +18151,24 @@ class Client extends openapi_client_1.default {
17083
18151
  });
17084
18152
  return $tea.cast(await this.callApi(params, req, runtime), new SetGroupDeletionProtectionResponse({}));
17085
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
+ */
17086
18160
  async setGroupDeletionProtection(request) {
17087
18161
  let runtime = new $Util.RuntimeOptions({});
17088
18162
  return await this.setGroupDeletionProtectionWithOptions(request, runtime);
17089
18163
  }
17090
18164
  /**
17091
- * Configures the health check feature for Elastic Compute Service (ECS) instances.
17092
- *
17093
- * @param request SetInstanceHealthRequest
17094
- * @param runtime runtime options for this request RuntimeOptions
17095
- * @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
17096
18172
  */
17097
18173
  async setInstanceHealthWithOptions(request, runtime) {
17098
18174
  tea_util_1.default.validateModel(request);
@@ -17126,21 +18202,29 @@ class Client extends openapi_client_1.default {
17126
18202
  return $tea.cast(await this.callApi(params, req, runtime), new SetInstanceHealthResponse({}));
17127
18203
  }
17128
18204
  /**
17129
- * Configures the health check feature for Elastic Compute Service (ECS) instances.
17130
- *
17131
- * @param request SetInstanceHealthRequest
17132
- * @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
17133
18211
  */
17134
18212
  async setInstanceHealth(request) {
17135
18213
  let runtime = new $Util.RuntimeOptions({});
17136
18214
  return await this.setInstanceHealthWithOptions(request, runtime);
17137
18215
  }
17138
18216
  /**
17139
- * Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
17140
- *
17141
- * @param request SetInstancesProtectionRequest
17142
- * @param runtime runtime options for this request RuntimeOptions
17143
- * @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
17144
18228
  */
17145
18229
  async setInstancesProtectionWithOptions(request, runtime) {
17146
18230
  tea_util_1.default.validateModel(request);
@@ -17177,15 +18261,28 @@ class Client extends openapi_client_1.default {
17177
18261
  return $tea.cast(await this.callApi(params, req, runtime), new SetInstancesProtectionResponse({}));
17178
18262
  }
17179
18263
  /**
17180
- * Puts one or more Elastic Compute Service (ECS) instances into the Protected state.
17181
- *
17182
- * @param request SetInstancesProtectionRequest
17183
- * @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
17184
18274
  */
17185
18275
  async setInstancesProtection(request) {
17186
18276
  let runtime = new $Util.RuntimeOptions({});
17187
18277
  return await this.setInstancesProtectionWithOptions(request, runtime);
17188
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
+ */
17189
18286
  async suspendProcessesWithOptions(request, runtime) {
17190
18287
  tea_util_1.default.validateModel(request);
17191
18288
  let query = {};
@@ -17223,10 +18320,23 @@ class Client extends openapi_client_1.default {
17223
18320
  });
17224
18321
  return $tea.cast(await this.callApi(params, req, runtime), new SuspendProcessesResponse({}));
17225
18322
  }
18323
+ /**
18324
+ * @summary Suspends processes in a scaling group.
18325
+ *
18326
+ * @param request SuspendProcessesRequest
18327
+ * @return SuspendProcessesResponse
18328
+ */
17226
18329
  async suspendProcesses(request) {
17227
18330
  let runtime = new $Util.RuntimeOptions({});
17228
18331
  return await this.suspendProcessesWithOptions(request, runtime);
17229
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
+ */
17230
18340
  async tagResourcesWithOptions(request, runtime) {
17231
18341
  tea_util_1.default.validateModel(request);
17232
18342
  let query = {};
@@ -17264,10 +18374,23 @@ class Client extends openapi_client_1.default {
17264
18374
  });
17265
18375
  return $tea.cast(await this.callApi(params, req, runtime), new TagResourcesResponse({}));
17266
18376
  }
18377
+ /**
18378
+ * @summary Adds tags to specified Auto Scaling resources.
18379
+ *
18380
+ * @param request TagResourcesRequest
18381
+ * @return TagResourcesResponse
18382
+ */
17267
18383
  async tagResources(request) {
17268
18384
  let runtime = new $Util.RuntimeOptions({});
17269
18385
  return await this.tagResourcesWithOptions(request, runtime);
17270
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
+ */
17271
18394
  async untagResourcesWithOptions(request, runtime) {
17272
18395
  tea_util_1.default.validateModel(request);
17273
18396
  let query = {};
@@ -17308,10 +18431,23 @@ class Client extends openapi_client_1.default {
17308
18431
  });
17309
18432
  return $tea.cast(await this.callApi(params, req, runtime), new UntagResourcesResponse({}));
17310
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
+ */
17311
18440
  async untagResources(request) {
17312
18441
  let runtime = new $Util.RuntimeOptions({});
17313
18442
  return await this.untagResourcesWithOptions(request, runtime);
17314
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
+ */
17315
18451
  async verifyAuthenticationWithOptions(request, runtime) {
17316
18452
  tea_util_1.default.validateModel(request);
17317
18453
  let query = {};
@@ -17346,10 +18482,23 @@ class Client extends openapi_client_1.default {
17346
18482
  });
17347
18483
  return $tea.cast(await this.callApi(params, req, runtime), new VerifyAuthenticationResponse({}));
17348
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
+ */
17349
18491
  async verifyAuthentication(request) {
17350
18492
  let runtime = new $Util.RuntimeOptions({});
17351
18493
  return await this.verifyAuthenticationWithOptions(request, runtime);
17352
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
+ */
17353
18502
  async verifyUserWithOptions(request, runtime) {
17354
18503
  tea_util_1.default.validateModel(request);
17355
18504
  let query = {};
@@ -17381,6 +18530,12 @@ class Client extends openapi_client_1.default {
17381
18530
  });
17382
18531
  return $tea.cast(await this.callApi(params, req, runtime), new VerifyUserResponse({}));
17383
18532
  }
18533
+ /**
18534
+ * @summary Checks whether Auto Scaling is activated.
18535
+ *
18536
+ * @param request VerifyUserRequest
18537
+ * @return VerifyUserResponse
18538
+ */
17384
18539
  async verifyUser(request) {
17385
18540
  let runtime = new $Util.RuntimeOptions({});
17386
18541
  return await this.verifyUserWithOptions(request, runtime);