Skip to content

Scaling Policies

Links: 101 AWS SAA Index


Dynamic Scaling Policies

  • It is of 3 types: target tracking, step and simple
If you have multiple scaling policies and multiple of them are met at the same time then

Amazon EC2 Auto Scaling chooses the policy that provides the largest capacity.

Target Tracking

  • It increases or decreases the current capacity of the group based on a target value for a specific metric.
  • It is similar to the way that your thermostat maintains the temperature of your home – you select a temperature and the thermostat does the rest.
I want the average ASG CPU to stay at around 40%
  • If you are scaling based on a utilisation metric that increases or decreases proportionally to the number of instances in an Auto Scaling group, then it is recommended that you use target tracking scaling policies. Otherwise, it is better to use step scaling policies instead.

Step Scaling

  • It increases or decreases the current capacity of the group based on a set of scaling adjustments, known as step adjustments, that vary based on the size of the alarm breach.
  • We have instance warmup time in step scaling.
Here the important term is set. This is what separates it from simple scaling policy.
  • You will have to setup how many units you want to add or remove.
    • attachments/Pasted image 20220420195330.jpg

Simple Scaling

  • It increases or decreases the current capacity of the group based on a single scaling adjustment.
  • You will have to setup how many units you want to add or remove.

Scheduled Scaling

  • Anticipate a scaling a based on known usage patterns. Example: increase the min capacity to 10 at 5 pm on Fridays.
  • A scheduled action sets the minimum, maximum, and desired sizes at the time of creating a scheduled action.
We use min and max value when we want to specify a range. If you know the number of instances that will be required then go with the desired sized option.

Forecasted Scaling

  • ML Driven
  • Predictive scaling to continuously forecast load and schedule scaling ahead.

Scaling Cooldowns

  • There is a default scaling cool down (300s) after every scaling event in order to stabilise the metrics.
  • No new instances are launched or terminated in the cool down period.
Use a ready-to-use AMI to reduce configuration time in order to be serving request fasters and reduce the cooldown period.

Last updated: 2022-05-05