This topic describes how to resume a suspended scaling process. This allows the scaling group to continue the specified process based on its functional logic.

Background information

After a scaling process is resumed, the process takes into account the changes made during the suspension. For example, after the scale-out process is resumed, Auto Scaling performs a check on the expected number of ECS instances to add instances, and the expected number of instances changes accordingly.
Scaling process Effect of resumed process
Scale-out The scaling group resumes scale-out events, such as manually adding instances as well as checking the expected number of instances and the minimum number of instances.

If the Expected Instances feature is enabled and the expected number of instances increases during a suspension, Auto Scaling performs a check on the expected number of instances to add ECS instances.

Scale-in The scaling group resumes scale-in events, such as manually removing instances as well as checking the expected number of instances and the maximum number of instances.

If the Expected Instances feature is enabled and the expected number of instances decreases during a suspension, Auto Scaling performs a check on the expected number of instances to remove ECS instances.

Health check The scaling group resumes the health check and automatically removes unhealthy ECS instances.
Scheduled task If a scheduled task is not due or is being retried, the scaling rules that are associated with the task are triggered.
Event-triggered task If an event-triggered task enters the alert state, the scaling rules that are associated with the task are triggered.

Procedure

  1. Log on to the Auto Scaling console.
  2. In the left-side navigation pane, click Scaling Groups.
  3. In the top navigation bar, select a region.
  4. Find the target scaling group and click Edit in the Actions column.
  5. In Suspended Processes, remove the process that you want to resume.
  6. Click OK.