Auto Scaling:ModifyScalingGroup

The operation that you want to perform. Set the value to ModifyScalingGroup.

The ID of the scaling group that you want to modify.

The name of the scaling group. The name of each scaling group must be unique in a region. The name must be 2 to 64 characters in length, and can contain letters, digits, underscores (_), hyphens (-), and periods (.). The name must start with a letter or a digit.

The minimum number of ECS instances in the scaling group. When the number of ECS instances in the scaling group is less than the value of the MinSize parameter, Auto Scaling automatically adds ECS instances until the number of instances is equal to the value of the MinSize parameter.

The maximum number of ECS instances in the scaling group. When the number of ECS instances in the scaling group is greater than the value of the MaxSize parameter, Auto Scaling automatically removes ECS instances from the scaling group until the number of instances is equal to the value of the MaxSize parameter.

The value range of the MaxSize parameter varies based on the instance quota. You can go to Quota Center to check the quota of instances that can be added to a scaling group.

For example, if the quota of instances that can be added to a scaling group is 2,000, the valid values of the MaxSize parameter range from 0 to 2000.

The cooldown time of the scaling group after a scaling activity is triggered. Valid values: 0 to 86400. Unit: seconds.

During the cooldown time, Auto Scaling executes only scaling activities that are triggered by event-triggered tasks monitored by CloudMonitor.

The first step to remove ECS instances from the scaling group. Valid values:

• OldestInstance: removes ECS instances that are added at the earliest point in time to the scaling group.
• NewestInstance: removes ECS instances that are most recently added to the scaling group.
• OldestScalingConfiguration: removes ECS instances that are created based on the earliest scaling configuration.
• CustomPolicy: removes ECS instances based on the custom scale-in policy (Function).

The second step to remove ECS instances from the scaling group. Valid values:

• OldestInstance: removes ECS instances that are added at the earliest point in time to the scaling group.
• NewestInstance: removes ECS instances that are most recently added to the scaling group.
• OldestScalingConfiguration: removes ECS instances that are created based on the earliest scaling configuration.

  Note The scaling configuration source specified by OldestScalingConfiguration can be a scaling configuration or a launch template.

The third step to remove ECS instances from the scaling group. Valid values:

• OldestInstance: removes ECS instances that are added at the earliest point in time to the scaling group.
• NewestInstance: removes ECS instances that are most recently added to the scaling group.
• OldestScalingConfiguration: removes ECS instances that are created based on the earliest scaling configuration.

The ID of the active scaling configuration in the scaling group.

The health check mode of the scaling group. Valid values:

• NONE: Auto Scaling does not perform health checks on instances in the scaling group.
• ECS: Auto Scaling performs health checks on ECS instances in the scaling group.

The ID of the launch template that is used by Auto Scaling to create instances.

The version number of the launch template. Valid values:

• A fixed template version number.
• Default: the default template version.
• Latest: the latest template version.

The minimum number of pay-as-you-go instances required in the scaling group. Valid values: 0 to 1000. If the number of pay-as-you-go instances is less than the value of this parameter, Auto Scaling preferentially creates pay-as-you-go instances.

If the MultiAZPolicy parameter is set to COMPOSABLE Policy, the default value is 0.

The percentage of pay-as-you-go instances among the excess instances when the requirement on the minimum number of pay-as-you-go instances is met. Valid values: 0 to 100.

If the MultiAZPolicy parameter is set to COMPOSABLE Policy, the default value is 100.

Specifies whether to supplement preemptible instances. If you set this parameter to true, Auto Scaling creates an instance to replace a preemptible instance when Auto Scaling receives a system message that indicates the preemptible instance is to be reclaimed.

Specifies whether to automatically create pay-as-you-go instances to meet the requirement on the number of ECS instances in the scaling group when the number of preemptible instances cannot be reached due to reasons such as costs and insufficient resources. This parameter takes effect only if you set the MultiAZPolicy parameter in the CreateScalingGroup operation to COST_OPTIMIZED. Valid values:

• true
• false

The number of instance types that you specify. Auto Scaling creates preemptible instances of multiple instance types that are provided at the lowest price. Valid values: 0 to 10.

If the MultiAZPolicy parameter is set to COMPOSABLE Policy, the default value is 2.

The expected number of ECS instances in the scaling group. Auto Scaling automatically maintains the expected number of ECS instances that you specify. The expected number cannot be greater than the value of the MaxSize parameter and cannot be less than the value of the MinSize parameter.

Specifies whether to enable deletion protection for the scaling group. Valid values:

• true: enables deletion protection for the scaling group. This way, the scaling group cannot be deleted.
• false: disables deletion protection for the scaling group.

The scaling policy for the multi-zone scaling group that contains ECS instances. Valid values:

• PRIORITY: The first vSwitch specified by using the VSwitchIds.N parameter has the highest priority. Auto Scaling scales instances in the zone where the vSwitch that has the highest priority resides. If the scaling fails, Auto Scaling scales instances in the zone where the vSwitch that has the next highest priority resides.
• COST_OPTIMIZED: Auto Scaling creates ECS instances whose vCPUs are provided at the lowest price during scale-out activities and removes ECS instances whose vCPUs are provided at the highest price during scale-in activities. If preemptible instance types are specified in the active scaling configuration, Auto Scaling preferentially creates preemptible instances. You can use the CompensateWithOnDemand parameter to specify whether to automatically create pay-as-you-go instances when Auto Scaling fails to create preemptible instances.

  Note The COST_OPTIMIZED setting takes effect only when you specify multiple instance types or when you specify at least one preemptible instance type.
• BALANCE: Auto Scaling evenly distributes ECS instances across zones that are specified for the scaling group. If ECS instances are unevenly distributed across zones due to insufficient resources, you can call the RebalanceInstance operation to evenly distribute the instances across the zones.
• COMPOSABLE: You can flexibly combine the preceding policies based on your business requirements.

The ID of vSwitch N. Valid values of N: 1 to 5.

This parameter is available only if the network type of the scaling group is virtual private cloud (VPC). The specified vSwitches and the scaling group must reside in the same VPC.

The vSwitches can reside in different zones. The vSwitches are sorted in ascending order based on the value of N. 1 specifies the highest priority. A greater value of N specifies a lower priority. If Auto Scaling fails to create ECS instances in the zone where the vSwitch that has the highest priority resides, Auto Scaling creates ECS instances in the zone where the vSwitch that has the next highest priority resides.

Instance type N. The instance type that is specified by using this parameter overrides the instance type that is specified in the launch template. If you want to scale instances in the scaling group based on the weighted capacity of instances, you must specify the LaunchTemplateOverride.N.InstanceType and LaunchTemplateOverride.N.WeightedCapacity parameters at the same time.

You can specify N instance types by using the Extended Configurations feature of the launch template. Valid values of N: 1 to 10.

For information about the valid values of InstanceType in InstanceTypeOverride.N.InstanceType, see Overview of instance families.

The weight of instance type N. The weight of an instance type specifies the capacity of a single instance of the instance type in the scaling group. If you want to scale instances in the scaling group based on the weighted capacity of instances, you must specify the LaunchTemplateOverride.N.WeightedCapacity parameter after you specify the LaunchTemplateOverride.N.InstanceType parameter. The values of N in the two parameters must be the same.

A higher weight specifies that a smaller number of instances of the specified instance type are required to meet the expected capacity requirement.

Performance metrics, such as the number of vCPUs and the memory size of each instance type, may vary. You can specify different weights for different instance types based on your business requirements.

Example:

• Current capacity: 0
• Expected capacity: 6
• Capacity of ecs.c5.xlarge: 4

To meet the expected capacity requirement, Auto Scaling must create two ecs.c5.xlarge instances.

Valid values of WeightedCapacity in the InstanceTypeOverride.N.WeightedCapacity parameter: 1 to 500.

The maximum bid price of instance type N that is specified by the LaunchTemplateOverride.N.InstanceType parameter. You can specify N instance types by using the Extended Configurations feature of the launch template. Valid values of N: 1 to 10.

Specifies whether to evenly distribute instances in the scaling group across multiple zones. This parameter is available only if you set the MultiAZPolicy parameter to COMPOSABLE. Valid values:

• true
• false

Default value: false.

The allocation policy of instances. Auto Scaling selects instance types based on the allocation policy to create instances. The policy can be applied to pay-as-you-go instances and preemptible instances. This parameter is available only if you set the MultiAZPolicy parameter to COMPOSABLE. Valid values:

• priority: Auto Scaling selects instance types based on the specified orders of the instance types to create instances.
• lowestPrice: Auto Scaling selects instance types that have the lowest unit price of vCPU to create instances.

Default value: priority.

The allocation policy of preemptible instances. You can use this parameter to individually specify the allocation policy of preemptible instances. This parameter is available only if you set the MultiAZPolicy parameter to COMPOSABLE. Valid values:

• priority: Auto Scaling selects instance types based on the specified orders of the instance types to create preemptible instances.
• lowestPrice: Auto Scaling selects instance types that have the lowest unit price of vCPU to create preemptible instances.

Default value: priority.

The maximum life span of the instance in the scaling group. Unit: seconds.

Valid values: 86400 to Integer.maxValue. You can also set this parameter to 0. If you set this parameter to 0, the instance has an unlimited life span.

Default value: null.

The Alibaba Cloud Resource Name (ARN) of the custom scale-in policy (Function). This parameter is available only if you specify CustomPolicy as the first step of the instance removal policy.

The ID of the request.