Release: Auto Scaling on 2011-07-25

Release Notes>Amazon EC2>Release: Auto Scaling on 2011 07 25
This release of Auto Scaling includes support for Amazon SNS notifications, the ability to set up recurring scaling activities, and more.


Submitted By: Francis@AWS
Release Date: July 25, 2011 7:00 AM GMT
Latest Version: 2011-01-01
Latest WSDL:
Created On: July 25, 2011 11:11 PM GMT
Last Updated: July 25, 2011 11:11 PM GMT

New Features

Amazon SNS Notifications in Auto Scaling

Auto Scaling now supports Amazon Simple Notification Service (Amazon SNS) so you can use it to receive notifications whenever Auto Scaling launches or terminates Amazon EC2 instances. For more information, see Auto Scaling With Email Notifications.


You now have the ability to set up recurring scaling activities using cron syntax. For more information, see the PutScheduledUpdateGroupAction API command.

AddToLoadBalancer Process Type You can now use the new configuration setting that allows you to scale up without adding the launched instance to the LoadBalancer. For more information, see the ProcessType API datatype.
ForceDelete Flag By using the new ForceDelete flag in the DeleteAutoScalingGroup command, you tell the service to delete the Auto Scaling group with the instances associated to it. You don't have to wait for the instances to be terminated first. For more information, see the DeleteAutoScalingGroup API command.

Known Issues

We no longer allow the ":" character in the name of any object.

You can no longer use the ":" (colon) character in the name of any object. This includes Launch Configurations, Auto Scaling groups, Policies, and any other named object.

The "Cooldown" parameter is now called "DefaultCooldown."

The "Cooldown" parameter for the CreateAutoScalingGroup and UpdateAutoScalingGroup actions is now named "DefaultCooldown."

IMPORTANT: If you are upgrading from a previous version, please be sure to update any calls that involve this parameter. Although the CLI and the SOAP protocol will return an error if you do not rename this parameter, the Query protocol will silently ignore the misnamed parameter.

Trigger functionality has been redesigned to work closely with CloudWatch alarms.

You no longer create triggers with a single call to CreateOrUpdateTrigger. Instead, you create a trigger by combining two AWS features: a CloudWatch alarm (configured to watch a specified CloudWatch metric) and an Auto Scaling policy that describes what should happen if the alarm threshold is crossed. In most cases, you will need two triggers—one trigger for scaling up and another for scaling down.

Migrating legacy triggers.

Auto Scaling does not permit using both a legacy trigger and the new alarms-based scaling system on an Auto Scaling group. To use the new scaling system you will have to migrate any legacy triggers to the new system. For detailed instructions on how to migrate legacy triggers, go to the following thread in the Amazon Web Services Discussion Forums: Migrating legacy Auto Scaling Triggers to the new, CloudWatch Alarm based scaling system.

Administrative suspensions. Auto Scaling might, at times, suspend processes for Auto Scaling groups that repeatedly fail to launch instances. This is known as an "administrative suspension," and most commonly applies to Auto Scaling groups that have zero running instances, have been trying to launch instances for more than 24 hours, and have not succeeded in that time in launching any instances. To resume processes, whether the suspension was manual (using SuspendProcesses) or administrative, use either the ResumeProcesses API action or the as-resume-processes CLI command.
©2017, Amazon Web Services, Inc. or its affiliates. All rights reserved.