{"id":23357,"date":"2015-08-01T17:21:06","date_gmt":"2015-08-01T11:51:06","guid":{"rendered":"https:\/\/2thenew.online\/blog\/?p=23357"},"modified":"2015-08-03T11:19:42","modified_gmt":"2015-08-03T05:49:42","slug":"aws-step-auto-scaling-policies","status":"publish","type":"post","link":"https:\/\/2thenew.online\/blog\/aws-step-auto-scaling-policies\/","title":{"rendered":"AWS Step Auto Scaling Policies"},"content":{"rendered":"

Amazon Web Services<\/strong> has introduced Step Autoscaling Policies<\/strong> for the autoscaling of EC2 instances<\/a>. These policies are much different from the Simple Autoscaling Policies which are being used till the date. The cooldown periods are not supported in the Step Scaling Policies. It let you define lower bound , upper bound for metric values and the amount by which to scale in or scale out the instances.<\/p>\n

In Simple Autoscaling Policy, you define the threshold value and upper bound. The alarm monitors the metric values. When the metric value breaches the threshold, the scaling policy acts. The instances are added or removed as per the policy. The Amazon Web Services has modified the Autoscaling Policies and new features have been introduced. It now lets you scale in and scale out your instances in percentage terms of the running instances. You can now define multiple scaling policies in a single AutoScaling Policy based on your metric values.<\/p>\n

\"AWS<\/p>\n

In this figure, you can see there are multiple actions in the AutoScaling Policy. \u00a0For example, it has been defined to add 1 instance when CPU Utilization is between 40%-50%. It will add 2,3,4 instances to 50%-70%,70%-90%,90%-infinity CPU utilization respectively. You can also define to increase or decrease instances in percentage of the number of instances. Thus, this new policy lets us define different metric value comparisons in contrast to the previous Simple AutoScaling Policy.<\/p>\n

In the same way we can define the Scale down policies for AutoScaling groups. We can also define the duration which the new instances will need to warm up. Thus, the new policy will act only after the previous policy passes down the warmup period of the instances.<\/p>\n

We had a use case few days ago and the same time Amazon introduced this new Step Scaling Policy. We usually had one AutoScaling Policy in which we scaled out and scaled in instances using only a particular condition. The main drawback was that our traffic was unpredictable and it used to change in few seconds from very high to low or vice-versa.\u00a0The step scaling policy is very helpful in this case.<\/p>\n

 <\/p>\n

HOW TO CREATE AWS STEP AUTO SCALING POLICY:<\/strong><\/h3>\n