It is best to use when we need to scale our resources help to manage the health of instances replace unhealthy instances with e2 instance it make and manage the performance perfectly it also scale up ec2 capacity according to the values or condition we define. It help to monitor the application more accurately through autoscaling we can get notifications as well Review collected by and hosted on G2.com.

After implementation of autoscaling of any kind can make updates deployments or changes more complex and challenging. we need extra services to change code or update or synchronize the projects separately it requires much time to setup and increase complexity Review collected by and hosted on G2.com.

Low maintenance - write once, fire and forget. Review collected by and hosted on G2.com.

Occasionally debugging runaway costs, usually caused by the developers in config. Review collected by and hosted on G2.com.

Once you have an application that is working, a few more clicks can allow you to scale up and down according to load, optimizing your costs and providing a great user experience. The easiest way is creating an AMI off the existing instance that provides your service and then configure the corresponding AutoScaling Group to use it to launch new instances when specific metrics are reached or remove instance when they drop below specific thresholds. And that is just the beginning, you can continue to optimize for both performance and costs the more you learn about this service. Review collected by and hosted on G2.com.

If you are just starting, there are a lot of caveats as to how to best implement proper autoscaling with what you already have. You need to be very careful with stateful services/requests and your architecture needs to allow for servers to appear and disappear. You will also need to review your deployment processes to make sure that all your instances are running the same code or instrument more complex workflows to update AMIs or configure instance as they are created (using Puppet/Chef/Ansible) Review collected by and hosted on G2.com.

Load balancer auto registration for new instances from auto scaling group.

Easy replace Review collected by and hosted on G2.com.

Not very easy to setup when you are not using Terraform / Packer. Review collected by and hosted on G2.com.

The ability to keep balance, monitor, and replace instances and it ensures that it always has the most computing power distributed to the closest availability zones. Review collected by and hosted on G2.com.

The learning curve, it is probably best to get AWS certified even at the minimum available certificate. There are tons of resources, but to really maximize the usability of EC2 Auto Scaling you really have to be familiar and "get your bearings" around AWS as a whole. Review collected by and hosted on G2.com.

Auto Scaling for EC2 instances saves our company lots of time. You can just simply configure a template and then set up auto scaling group with the configuration. You don't have to worry about the rest of it. It will automatically scale up EC2 instances if workload get heavier and scale down if workload get lighter. You can set up the metrics for scaling up and down. Such as setting CPU utilization to greater than 80 percent or lower than 10 percent. It saves money and time and trouble. If you need lots of computing power and it goes up and down, you should consider auto scaling group. Review collected by and hosted on G2.com.

I have not found anything I don't like yet. Review collected by and hosted on G2.com.

The autoscaling system is easy to use and is integrated into everything. Review collected by and hosted on G2.com.

To use the autoscaling system pretty much everything you do has to be implemented in AWS. Review collected by and hosted on G2.com.

Works great and seamlessly for horizontal scaling (increasing number of VMs based on metrics like CPU, memory, etc.) Review collected by and hosted on G2.com.

Lack of support for vertical scaling (increase CPU and memory for same VM) for stateful application.

Scaling down with horizontal scaling is unpredicatable. AWS EC2 autoscaling does offer some termination policies like oldest instance, newest instance, etc. but this still does not guarantee that the instance being terminated is not doing some task. There should be a feedback capability provided between instances and AWS EC2 autoscaling (similar to what kubernetes provides). Review collected by and hosted on G2.com.

The simplicity of interface, which nonetheless allows to setup everything you need to autoscale. It is fast enough and reliable Review collected by and hosted on G2.com.

It would be better to have a metric like an app performance as New Relic has, so you could scale based on that metric. It is not fully related to that product, but the absence of that metric its the only thing I don't like about it. Review collected by and hosted on G2.com.

Like it's automatically scalling up compute instances and scalling down as I was using AWS HPC. Its gonna be very costly without Auto-Scalling. Review collected by and hosted on G2.com.

It took some time around 1-2 minute to scale up from 0 instance. Review collected by and hosted on G2.com.