14

AWS Autoscaling has 2 concepts:

  • Cooldown period: From AWS documentation: the cooldown period helps to ensure that your Auto Scaling group doesn't launch or terminate additional instances before the previous scaling activity takes effect. You can configure the length of time based on your instance warmup period or other application needs. Details are here.
  • Health check grace period: From AWS documentation: frequently, an Auto Scaling instance that has just come into service needs to warm up before it can pass the health check. Amazon EC2 Auto Scaling waits until the health check grace period ends before checking the health status of the instance. Details are here.

But I can't figure out the difference between them. Can somebody help?

Thanks in advance.

BinaryButterfly
  • 18,137
  • 13
  • 50
  • 91
krishna_mee2004
  • 6,556
  • 2
  • 35
  • 45

1 Answers1

16

A few differences to consider:

The cooldown period is scoped to an auto-scaling action; if that action launches 3 instances, the cooldown period starts when the last instance is ready. Health check grace periods are scoped to an individual instance.

Auto-scaling cooldowns can be applied to many different auto-scaling policies, such as policies for when things scale in. You can delay the termination of additional instances for a set period time. Health check grace periods are only for scaling out.

Cooldowns will be ignored if a health check fails and causes another auto-scaling event. Grace periods will always be in place for the defined amount of time.

bwest
  • 9,182
  • 3
  • 28
  • 58
  • Got it. Thank you! – krishna_mee2004 Apr 01 '19 at 11:52
  • 4
    Its imported to add that cooldown can be used only [`when using simple scaling policies, but not when using other scaling policies`](https://docs.aws.amazon.com/autoscaling/ec2/userguide/Cooldown.html) – Marcin Dec 05 '19 at 00:34
  • I believe a cooldown period can be created for any Auto-scaling policy. In good common sense practice, cooldown periods are best suited for simple scaling policies; enough whereby, they are defaulted when the policy is created. – Roger England Dec 14 '21 at 19:39