You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.

Class: Aws::ApplicationAutoScaling::Types::StepScalingPolicyConfiguration

Inherits:
Struct
  • Object
show all
Defined in:
(unknown)

Overview

Note:

When passing StepScalingPolicyConfiguration as input to an Aws::Client method, you can use a vanilla Hash:

{
  adjustment_type: "ChangeInCapacity", # accepts ChangeInCapacity, PercentChangeInCapacity, ExactCapacity
  step_adjustments: [
    {
      metric_interval_lower_bound: 1.0,
      metric_interval_upper_bound: 1.0,
      scaling_adjustment: 1, # required
    },
  ],
  min_adjustment_magnitude: 1,
  cooldown: 1,
  metric_aggregation_type: "Average", # accepts Average, Minimum, Maximum
}

Represents a step scaling policy configuration.

Returned by:

Instance Attribute Summary collapse

Instance Attribute Details

#adjustment_typeString

The adjustment type, which specifies how the ScalingAdjustment parameter in a StepAdjustment is interpreted.

Possible values:

  • ChangeInCapacity
  • PercentChangeInCapacity
  • ExactCapacity

Returns:

  • (String)

    The adjustment type, which specifies how the ScalingAdjustment parameter in a StepAdjustment is interpreted.

#cooldownInteger

The amount of time, in seconds, after a scaling activity completes where previous trigger-related scaling activities can influence future scaling events.

For scale out policies, while the cooldown period is in effect, the capacity that has been added by the previous scale out event that initiated the cooldown is calculated as part of the desired capacity for the next scale out. The intention is to continuously (but not excessively) scale out. For example, an alarm triggers a step scaling policy to scale out an Amazon ECS service by 2 tasks, the scaling activity completes successfully, and a cooldown period of 5 minutes starts. During the Cooldown period, if the alarm triggers the same policy again but at a more aggressive step adjustment to scale out the service by 3 tasks, the 2 tasks that were added in the previous scale out event are considered part of that capacity and only 1 additional task is added to the desired count.

For scale in policies, the cooldown period is used to block subsequent scale in requests until it has expired. The intention is to scale in conservatively to protect your application\'s availability. However, if another alarm triggers a scale out policy during the cooldown period after a scale-in, Application Auto Scaling scales out your scalable target immediately.

Returns:

  • (Integer)

    The amount of time, in seconds, after a scaling activity completes where previous trigger-related scaling activities can influence future scaling events.

#metric_aggregation_typeString

The aggregation type for the CloudWatch metrics. Valid values are Minimum, Maximum, and Average.

Possible values:

  • Average
  • Minimum
  • Maximum

Returns:

  • (String)

    The aggregation type for the CloudWatch metrics.

#min_adjustment_magnitudeInteger

The minimum number to adjust your scalable dimension as a result of a scaling activity. If the adjustment type is PercentChangeInCapacity, the scaling policy changes the scalable dimension of the scalable target by this amount.

Returns:

  • (Integer)

    The minimum number to adjust your scalable dimension as a result of a scaling activity.

#step_adjustmentsArray<Types::StepAdjustment>

A set of adjustments that enable you to scale based on the size of the alarm breach.

Returns:

  • (Array<Types::StepAdjustment>)

    A set of adjustments that enable you to scale based on the size of the alarm breach.