Cooldown periods in AWS - Mini Project: Build & Apply

Cooldown Periods in AWS Auto Scaling

📖 Scenario: You manage a web application hosted on AWS. To handle traffic changes, you use an Auto Scaling group that adjusts the number of servers automatically. To avoid starting or stopping servers too quickly, you want to set a cooldown period.

🎯 Goal: Build an AWS Auto Scaling group configuration that includes a cooldown period to control scaling actions.

📋 What You'll Learn

Create an Auto Scaling group named MyAutoScalingGroup with a launch configuration named MyLaunchConfig.

Set the cooldown period to exactly 300 seconds (5 minutes).

Use the cooldown period setting in the Auto Scaling group configuration.

💡 Why This Matters

🌍 Real World

Cooldown periods help prevent your cloud servers from scaling up or down too quickly, which can save costs and improve stability.

💼 Career

Understanding cooldown periods is important for cloud engineers and DevOps professionals managing scalable applications on AWS.

1

Create the launch configuration

Create a launch configuration named MyLaunchConfig with the image ID ami-0abcdef1234567890 and instance type t2.micro.

AWS

# Your code here to create launch configuration MyLaunchConfig

Need a hint?

The launch configuration defines the server image and type for your Auto Scaling group.

2

Add the Auto Scaling group without cooldown

Create an Auto Scaling group named MyAutoScalingGroup using the launch configuration MyLaunchConfig. Set the minimum size to 1 and maximum size to 3. Do not add the cooldown period yet.

AWS

resource "aws_launch_configuration" "MyLaunchConfig" {
  name          = "MyLaunchConfig"
  image_id      = "ami-0abcdef1234567890"
  instance_type = "t2.micro"
}

# Your code here to create Auto Scaling group MyAutoScalingGroup without cooldown

Need a hint?

The Auto Scaling group manages the number of instances based on demand.

Use a placeholder subnet ID like subnet-12345678 for vpc_zone_identifier.

3

Add the cooldown period variable

Create a variable named cooldown_period with the default value 300 (seconds).

AWS

resource "aws_launch_configuration" "MyLaunchConfig" {
  name          = "MyLaunchConfig"
  image_id      = "ami-0abcdef1234567890"
  instance_type = "t2.micro"
}

resource "aws_autoscaling_group" "MyAutoScalingGroup" {
  name                      = "MyAutoScalingGroup"
  launch_configuration      = aws_launch_configuration.MyLaunchConfig.name
  min_size                  = 1
  max_size                  = 3
  vpc_zone_identifier       = ["subnet-12345678"]
}

# Your code here to create variable cooldown_period with default 300

Need a hint?

Variables help make your configuration flexible and reusable.

4

Set the cooldown period in the Auto Scaling group

Add the cooldown period to the Auto Scaling group MyAutoScalingGroup by setting the default_cooldown attribute to the variable cooldown_period.

AWS

variable "cooldown_period" {
  type    = number
  default = 300
}

resource "aws_launch_configuration" "MyLaunchConfig" {
  name          = "MyLaunchConfig"
  image_id      = "ami-0abcdef1234567890"
  instance_type = "t2.micro"
}

resource "aws_autoscaling_group" "MyAutoScalingGroup" {
  name                      = "MyAutoScalingGroup"
  launch_configuration      = aws_launch_configuration.MyLaunchConfig.name
  min_size                  = 1
  max_size                  = 3
  vpc_zone_identifier       = ["subnet-12345678"]

  # Your code here to set default_cooldown using cooldown_period variable
}

Need a hint?

The default_cooldown setting controls how long Auto Scaling waits between scaling actions.