The amount of time (in minutes) after a scaling event occurs that AWS
OpsWorks should ignore metrics and suppress additional scaling events.
For example, AWS OpsWorks adds new instances following an upscaling
event but the instances won't start reducing the load until they have
been booted and configured. There is no point in raising additional
scaling events during that operation, which typically takes several
minutes. IgnoreMetricsTime allows you to direct AWS
OpsWorks to suppress scaling events long enough to get the new
instances online.

Custom Cloudwatch auto scaling alarms, to be used as thresholds. This
parameter takes a list of up to five alarm names, which are case
sensitive and must be in the same region as the stack. <note>To use
custom alarms, you must update your service role to allow
cloudwatch:DescribeAlarms. You can either have AWS
OpsWorks update the role for you when you first use this feature or
you can edit the role manually. For more information, see Allowing
AWS OpsWorks to Act on Your Behalf.</note>

The amount of time (in minutes) after a scaling event occurs that AWS
OpsWorks should ignore metrics and suppress additional scaling events.
For example, AWS OpsWorks adds new instances following an upscaling
event but the instances won't start reducing the load until they have
been booted and configured. There is no point in raising additional
scaling events during that operation, which typically takes several
minutes. IgnoreMetricsTime allows you to direct AWS
OpsWorks to suppress scaling events long enough to get the new
instances online.

Constraints:Range: 1 - 100

Returns:

The amount of time (in minutes) after a scaling event occurs that AWS
OpsWorks should ignore metrics and suppress additional scaling events.
For example, AWS OpsWorks adds new instances following an upscaling
event but the instances won't start reducing the load until they have
been booted and configured. There is no point in raising additional
scaling events during that operation, which typically takes several
minutes. IgnoreMetricsTime allows you to direct AWS
OpsWorks to suppress scaling events long enough to get the new
instances online.

The amount of time (in minutes) after a scaling event occurs that AWS
OpsWorks should ignore metrics and suppress additional scaling events.
For example, AWS OpsWorks adds new instances following an upscaling
event but the instances won't start reducing the load until they have
been booted and configured. There is no point in raising additional
scaling events during that operation, which typically takes several
minutes. IgnoreMetricsTime allows you to direct AWS
OpsWorks to suppress scaling events long enough to get the new
instances online.

Constraints:Range: 1 - 100

Parameters:

ignoreMetricsTime The amount of time (in minutes) after a scaling event occurs that AWS
OpsWorks should ignore metrics and suppress additional scaling events.
For example, AWS OpsWorks adds new instances following an upscaling
event but the instances won't start reducing the load until they have
been booted and configured. There is no point in raising additional
scaling events during that operation, which typically takes several
minutes. IgnoreMetricsTime allows you to direct AWS
OpsWorks to suppress scaling events long enough to get the new
instances online.

The amount of time (in minutes) after a scaling event occurs that AWS
OpsWorks should ignore metrics and suppress additional scaling events.
For example, AWS OpsWorks adds new instances following an upscaling
event but the instances won't start reducing the load until they have
been booted and configured. There is no point in raising additional
scaling events during that operation, which typically takes several
minutes. IgnoreMetricsTime allows you to direct AWS
OpsWorks to suppress scaling events long enough to get the new
instances online.

Returns a reference to this object so that method calls can be chained together.

Constraints:Range: 1 - 100

Parameters:

ignoreMetricsTime The amount of time (in minutes) after a scaling event occurs that AWS
OpsWorks should ignore metrics and suppress additional scaling events.
For example, AWS OpsWorks adds new instances following an upscaling
event but the instances won't start reducing the load until they have
been booted and configured. There is no point in raising additional
scaling events during that operation, which typically takes several
minutes. IgnoreMetricsTime allows you to direct AWS
OpsWorks to suppress scaling events long enough to get the new
instances online.

Returns:

A reference to this updated object so that method calls can be chained
together.

Custom Cloudwatch auto scaling alarms, to be used as thresholds. This
parameter takes a list of up to five alarm names, which are case
sensitive and must be in the same region as the stack. <note>To use
custom alarms, you must update your service role to allow
cloudwatch:DescribeAlarms. You can either have AWS
OpsWorks update the role for you when you first use this feature or
you can edit the role manually. For more information, see Allowing
AWS OpsWorks to Act on Your Behalf.</note>

Returns:

Custom Cloudwatch auto scaling alarms, to be used as thresholds. This
parameter takes a list of up to five alarm names, which are case
sensitive and must be in the same region as the stack. <note>To use
custom alarms, you must update your service role to allow
cloudwatch:DescribeAlarms. You can either have AWS
OpsWorks update the role for you when you first use this feature or
you can edit the role manually. For more information, see Allowing
AWS OpsWorks to Act on Your Behalf.</note>

Custom Cloudwatch auto scaling alarms, to be used as thresholds. This
parameter takes a list of up to five alarm names, which are case
sensitive and must be in the same region as the stack. <note>To use
custom alarms, you must update your service role to allow
cloudwatch:DescribeAlarms. You can either have AWS
OpsWorks update the role for you when you first use this feature or
you can edit the role manually. For more information, see Allowing
AWS OpsWorks to Act on Your Behalf.</note>

Parameters:

alarms Custom Cloudwatch auto scaling alarms, to be used as thresholds. This
parameter takes a list of up to five alarm names, which are case
sensitive and must be in the same region as the stack. <note>To use
custom alarms, you must update your service role to allow
cloudwatch:DescribeAlarms. You can either have AWS
OpsWorks update the role for you when you first use this feature or
you can edit the role manually. For more information, see Allowing
AWS OpsWorks to Act on Your Behalf.</note>

Custom Cloudwatch auto scaling alarms, to be used as thresholds. This
parameter takes a list of up to five alarm names, which are case
sensitive and must be in the same region as the stack. <note>To use
custom alarms, you must update your service role to allow
cloudwatch:DescribeAlarms. You can either have AWS
OpsWorks update the role for you when you first use this feature or
you can edit the role manually. For more information, see Allowing
AWS OpsWorks to Act on Your Behalf.</note>

Returns a reference to this object so that method calls can be chained together.

Parameters:

alarms Custom Cloudwatch auto scaling alarms, to be used as thresholds. This
parameter takes a list of up to five alarm names, which are case
sensitive and must be in the same region as the stack. <note>To use
custom alarms, you must update your service role to allow
cloudwatch:DescribeAlarms. You can either have AWS
OpsWorks update the role for you when you first use this feature or
you can edit the role manually. For more information, see Allowing
AWS OpsWorks to Act on Your Behalf.</note>

Returns:

A reference to this updated object so that method calls can be chained
together.

Custom Cloudwatch auto scaling alarms, to be used as thresholds. This
parameter takes a list of up to five alarm names, which are case
sensitive and must be in the same region as the stack. <note>To use
custom alarms, you must update your service role to allow
cloudwatch:DescribeAlarms. You can either have AWS
OpsWorks update the role for you when you first use this feature or
you can edit the role manually. For more information, see Allowing
AWS OpsWorks to Act on Your Behalf.</note>

Returns a reference to this object so that method calls can be chained together.

Parameters:

alarms Custom Cloudwatch auto scaling alarms, to be used as thresholds. This
parameter takes a list of up to five alarm names, which are case
sensitive and must be in the same region as the stack. <note>To use
custom alarms, you must update your service role to allow
cloudwatch:DescribeAlarms. You can either have AWS
OpsWorks update the role for you when you first use this feature or
you can edit the role manually. For more information, see Allowing
AWS OpsWorks to Act on Your Behalf.</note>

Returns:

A reference to this updated object so that method calls can be chained
together.