Auto Scaling：DescribeScalingGroups

The ID of the virtual private cloud (VPC) in which the scaling group resides.

The time when the scaling group was created.

The total number of ECS instances in the scaling group.

The name of the scaling group.

The number of instance types in the scaling group. Auto Scaling evenly creates preemptible instances of multiple instance types that are provided at the lowest price across the zones of the scaling group. Valid values: 0 to 10.

The number of instances that was stopped in Economical Mode in the scaling group.

The percentage of pay-as-you-go instances in excess when the minimum number of pay-as-you-go instances reaches the threshold. Valid values: 0 to 100.

The time when the scaling group was last modified.

The minimum number of ECS instances that must be contained in the scaling group.

The ID of the scaling group.

Indicates whether Auto Scaling can create pay-as-you-go instances to supplement preemptible instances if preemptible instances cannot be created due to price-related factors or insufficient inventory when MultiAZPolicy is set to COST_OPTIMIZED. Valid values:

• true
• false

The instance reclaim mode of the scaling group. Valid values:

• recycle: economical mode.
• release: release mode.
• forcerelease: forced release mode.

For more information, see RemoveInstances .

The number of ECS instances that are in the Pending Remove state in the scaling group.

The number of ECS instances that are in the In Service state in the scaling group.

The minimum number of pay-as-you-go instances that must be contained 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.

The number of ECS instances that are in the Protected state in the scaling group.

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

• NONE: Auto Scaling does not perform health checks.
• ECS: Auto Scaling checks the health status of ECS instances in the scaling group.
• LOAD_BALANCER: Auto Scaling checks the health status of instances in the scaling group based on the health check results of load balancers. The health check results of Classic Load Balancer (CLB, formerly known as Server Load Balancer or SLB) instances are not used as the basis to perform health checks on the instances in the scaling group.

The status of the scaling group. Valid values:

• Active: The scaling group is active. Active scaling groups can receive requests to execute scaling rules and trigger scaling activities.
• Inactive: The scaling group is in the Disabled state. Disabled scaling groups cannot receive requests to execute scaling rules.
• Deleting: The scaling group is being deleted. Scaling groups that are being deleted cannot receive requests to execute scaling rules, and the parameter settings of the scaling groups cannot be modified.

Indicates whether the Deletion Protection feature is enabled for the scaling group. Valid values:

• true: The Deletion Protection feature is enabled for the scaling group. The scaling group cannot be deleted.
• false: The Deletion Protection feature is disabled for the scaling group.

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

The type of instances that are managed by the scaling group.

The scaling policy of the ECS instances in the multi-zone scaling group. Valid values:

• PRIORITY: ECS instances are created based on the value of VSwitchIds. If Auto Scaling cannot create ECS instances in the zone where the vSwitch of the highest priority resides, Auto Scaling creates ECS instances in the zone where the vSwitch of the next highest priority resides.

• COST_OPTIMIZED: ECS instances are created based on the unit prices of their vCPUs. Auto Scaling preferentially creates ECS instances whose vCPUs are provided at the lowest price. If preemptible instance types are specified in the scaling configuration, Auto Scaling preferentially creates preemptible instances. You can also specify CompensateWithOnDemand to allow Auto Scaling to create pay-as-you-go instances if preemptible instances cannot be created due to limited stock.

  **

  Note The COST_OPTIMIZED setting takes effect only if your scaling configuration contains multiple instance types or contains preemptible instance types.

• BALANCE: ECS instances are evenly distributed across the zones that are specified for the scaling group. If ECS instances become unevenly distributed across the specified zones due to limited instance type availability, you can call the RebalanceInstance operation to balance the distribution of the ECS instances.

The number of ECS instances that are being removed from the scaling group.

The number of ECS instances that are in the Pending Add state in the scaling group.

The number of ECS instances that are in the Standby state in the scaling group.

The number of ECS instances that are being added to the scaling group and configured.

The ID of the launch template that is used by the scaling group.

The total weighted capacity of all ECS instances in the scaling group if Weighted is specified. In other cases, this parameter specifies the total number of ECS instances in the scaling group.

The expected number of ECS instances in the scaling group. Auto Scaling automatically maintains the expected number of ECS instances.

Indicates whether preemptible instances can be supplemented. If this parameter is set to true, Auto Scaling proactively creates instances to replace the preemptible instances for reclamation when Auto Scaling receives a system notification.

The version of the launch template that is used by the scaling group.

The region ID of the scaling group.

The vSwitch ID of the scaling group.

The maximum number of ECS instances that can be contained in the scaling group.

The cooldown period of the scaling group. During the cooldown period, Auto Scaling does not execute the scaling activities that are triggered by CloudMonitor event-triggered tasks.

The backend vServer groups.

The instance types that are extended in the launch template.

The Application Load Balancer (ALB) server groups.

The server groups.

The instance removal policies. Valid values:

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

The IDs of the ApsaraDB RDS instances that are attached to the scaling group.

The IDs of the load balancers that are attached to the scaling group.

The IDs of the vSwitches that are associated with the scaling group. If you specify VSwitchIds, VSwitchId is ignored.

The processes that are suspended. If no process is suspended, null is returned. Valid values:

• ScaleIn: scale-in processes.
• ScaleOut: scale-out processes.
• HealthCheck: health check processes.
• AlarmNotification: event-triggered task processes.
• ScheduledAction: scheduled task processes.

Indicates whether Auto Scaling stops executing scaling activities in the scaling group. Valid values:

• true: Auto Scaling stops executing scaling activities in the scaling group if the scaling activities failed for more than seven consecutive days in the scaling group. In this case, you must modify the scaling group or scaling configuration to resume the scaling activities.
• false: Auto Scaling does not stop executing scaling activities in the scaling group.

The ID of the CloudMonitor application group that is associated with the scaling group.

Indicates whether instances in the scaling group are evenly distributed across the specified zones. This parameter takes effect only if you set MultiAZPolicy to COMPOSABLE. Valid values:

• true
• false

The instance allocation policy. Auto Scaling selects instance types based on the allocation policy to create the required number of preemptible instances. The policy is suitable for pay-as-you-go instances and preemptible instances. This parameter takes effect only if you set MultiAZPolicy to COMPOSABLE. Valid values:

• priority: Auto Scaling adopts the predefined instance type sequence to create the required number of preemptible instances.
• lowestPrice: Auto Scaling selects instance types that have the most economical vCPU pricing to create the required number of instances.

The allocation policy of preemptible instances. This parameter indicates the manner in which Auto Scaling selects instance types to create the required number of preemptible instances. This parameter takes effect only if you set MultiAZPolicy to COMPOSABLE. Valid values:

• priority: Auto Scaling adopts the predefined instance type sequence to create the required number of preemptible instances.
• lowestPrice: Auto Scaling selects instance types that have the most economical vCPU pricing to create the required number of preemptible instances.

Default value: priority.

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

Valid values: 0 or [86400, Integer.maxValue]. A value of 0 for MaxInstanceLifetime indicates that a previously set limit has been removed. This effectively disables the maximum instance lifetime constraint.

Default value: null.

The Alibaba Cloud Resource Name (ARN) of the function that is specified in the custom scale-in policy. This parameter takes effect only if you set the first value of RemovalPolicies to CustomPolicy.

The number of instances that are initialized before they are added into the scaling group.

The ID of the resource group to which the scaling group belongs.

The load balancer configurations.

Indicates whether the Expected Number of Instances feature is enabled. Valid values:

• true
• false

The tags of the scaling group.

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

• NONE: Auto Scaling does not perform health checks.
• ECS: Auto Scaling checks the health status of ECS instances in the scaling group.
• LOAD_BALANCER: Auto Scaling checks the health status of instances in the scaling group based on the health check results of load balancers. The health check results of CLB instances are not used as the basis to perform health checks on the instances in the scaling group.

The databases that are attached to the scaling group.