Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« AWS Marketplace - New Management Portal for ISVs & VARs | Main | Background Task Handling for AWS Elastic Beanstalk »


Feed You can follow this conversation by subscribing to the comment feed for this post.


Wow that's great. Three questions:
1, How can we make git deployment for this kind of "dynamic" network? I currently have two Ec2 node loadbalanced and it is quite straightforward, but I can't imagine how can I do with multiple/variable instances?

2, How can we use SSL certs in this case?

3, How can we attach this to Route53?


Nick Lamming

Fantastic addition to the console and I'm sure it's been eagerly awaited by a number of users.

A question concerning other scaling methods. Are there any plans for incorporating pro-active scaling into this added feature? We have managed to create our own in-house process but it would be great to be able to use similar processes to those you have incorporated into the auto-scaling method within the console.



I have removed default VPC from one of my accounts. When creating "launch configuration" and getting to the last step, it fails to create one with error "Failed to create launch configuration. No default VPC for this user".


This is an amazing addition to AWS and is really bringing forward an amazing service for mass consumption.

One thing missing though... would be great if this interface allowed for the configuration of Instance Tags within the Auto Scale Group Configuration. The setup I work with requires my newly started EC2 Instances to have specific instance tags to work within my setup.

Keep up the great work... AWS is on fire lately!

Juan David Gutierrez

Now it will be easier to work with autoscaling, for those who still have problems with the CLI

John Tobin

Great work! It's great to see this feature in the console at last. Just a couple of observations:

- Tagging isn't supported yet, a pretty important feature for managing a lot of instances (unless I missed it?)
- My existing launch configuration and scaling groups didn't appear in the list until I created a new launch config in the console.



Thanks a lot! Been waiting for this for a while now!

Arindam Majumder

It's really great. It's working fine for me.

Have few questions.

1. Can we add an existing EC2 instance into newly created Auto Scaling Group? I saw it's not happening. That mean's we need to first decide on Auto Scaling feature.

2. When created Auto Scaling with Min 1 and Max 2. First time I saw two Ec2 instances got created in the Instance section. Didn't understand why?

3. Once we create Auto Scaling group, can we able to edit scaling policy?

Best Regards

So this is super fantastic and I'm really excited to see you guys finally launch this, but I have to agree with others here in the fact that it's missing a few critical pieces.

1. Tagging....really??? It can't be that hard to have added this feature...SUPER important.
2. Scheduled Scaling. It would be great if there was a way to do scheduled scaling. For instance, I have very predictable traffic patterns for one of our products. I can scale it down to ~3 instances at night, and depending on request counts go up to approx 16 instances during peak traffic. This interface doesn't allow me to easily do this yet. Perhaps with a large amount of custom application of cloudwatch metrics/alarms, etc... but that's more work than it should be. Just look at Asgard and you'll see how simple it can be, and you could add more features.
3. Option to perform some other options against instances. For instance:
3.1 DON'T terminate (sometimes we need this)
3.2 Configure scale-in to remove from ELB, give the instance(s) a cooldown period of X minutes before shutting off
3.3 Be able to perform actions such as snapshot ebs, remote push out an action (ie. userdata/scripts/etc...anything).
4. Ability to reuse instances. A good example is when utilizing Windows based images, these are often significantly slower to startup than a linux image. If we could have a contingent of "stopped" instances that are brought up and down as needed, this would be great.

All in all, it's pretty fantastic, and I'm loving it, but until some of these other features have been implemented, I'm going to have to use Asgard or CLI to configure still.

Jeff Barr

@Arindam, here are some answers for you:

1. Adding an existing EC2 instance to a new group is not currently supported.
2. Min and Max determine the upper and lower boundaries for the size of your group. On the preceding screen, you specify the initial number of instances to launch. If you want to start with just one instance, you can set that value to “1”.
3. Yes, you can edit a scaling policy by selecting your group from the list in the Auto Scaling Groups screen, clicking the “Scaling Policies” tab in the lower panel, and then clicking “Edit”.

The comments to this entry are closed.

Featured Events

The AWS Report

Brought to You By

Jeff Barr (@jeffbarr):

Jinesh Varia (@jinman):

Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30