Cooldown periods in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a cooldown period of 300 seconds for an Auto Scaling group.

AWS

AutoScalingGroup:
  Type: AWS::AutoScaling::AutoScalingGroup
  Properties:
    Cooldown: [1]

Drag options to blanks, or click blank then click option'

A300

B0

C30

D600

Attempts:

3 left

💡 Hint

Common Mistakes

Using too short cooldown like 30 seconds may cause rapid scaling.

Setting cooldown to 0 disables cooldown, which is usually not recommended.

The cooldown period is set in seconds. Setting it to 300 means the group waits 5 minutes before another scaling activity.

2fill in blank

medium

Complete the code to add a cooldown period to a scaling policy in AWS CloudFormation.

AWS

MyScalingPolicy:
  Type: AWS::AutoScaling::ScalingPolicy
  Properties:
    Cooldown: [1]

Drag options to blanks, or click blank then click option'

A60

B0

C10

D300

Attempts:

3 left

💡 Hint

Common Mistakes

Setting cooldown too low can cause scaling thrashing.

Setting cooldown to zero disables cooldown, which can cause issues.

The Cooldown property defines the wait time after a scaling activity. 300 seconds is a typical cooldown period.

3fill in blank

hard

Fix the error in the cooldown period value to ensure it is valid for an Auto Scaling group.

AWS

AutoScalingGroup:
  Type: AWS::AutoScaling::AutoScalingGroup
  Properties:
    Cooldown: [1]

Drag options to blanks, or click blank then click option'

A300

B-100

Cfive minutes

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using negative numbers for cooldown.

Using text strings instead of numbers.

Cooldown must be a non-negative integer in seconds. '300' is valid, negative or string values are invalid.

4fill in blank

hard

Fill both blanks to correctly configure cooldown and min adjustment step in a scaling policy.

AWS

ScalingPolicy:
  Type: AWS::AutoScaling::ScalingPolicy
  Properties:
    Cooldown: [1]
    MinAdjustmentStep: [2]

Drag options to blanks, or click blank then click option'

A300

B1

C5

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Setting MinAdjustmentStep to zero disables scaling steps.

Setting cooldown too low causes rapid scaling.

Cooldown is set to 300 seconds to allow stabilization. MinAdjustmentStep of 5 means scaling changes happen in steps of 5 units.

5fill in blank

hard

Fill all three blanks to configure a scaling policy with cooldown, adjustment type, and scaling adjustment.

AWS

ScalingPolicy:
  Type: AWS::AutoScaling::ScalingPolicy
  Properties:
    Cooldown: [1]
    AdjustmentType: [2]
    ScalingAdjustment: [3]

Drag options to blanks, or click blank then click option'

A200

BChangeInCapacity

C3

DPercentChangeInCapacity

Attempts:

3 left

💡 Hint

Common Mistakes

Using PercentChangeInCapacity with a small integer scaling adjustment.

Setting cooldown too low or too high.

Cooldown is 200 seconds to wait between scaling actions. AdjustmentType 'ChangeInCapacity' means the scaling adjustment is an absolute number. ScalingAdjustment of 3 means add or remove 3 instances.