Amazon EC2 Auto Scaling Reviews

[Amazon EC2 Auto Scaling] is simple to set up and pretty self-explanatory. Never had issues around scaling up or down. [Now] we won't need to guess the capacity for our apps or services. The both scaling, up and down is simply perfect, you can actually stop checking every time for resources because this tool takes care of everything

It is great if you
want something less sophisticated than Kubernetes. There is less complexity in scalling and there is freedom in configuring how you want to scale. Downside is that you can scale one particular micro service, maybe its not the best fit for a micro service based application.

Amazon EC2 AUTO SCALING is quite useful where a dynamic and predictive scaling is required. One has to predefine the conditions and the scaling function automatically adds or reduces the instances. The scaling is faster in comparison to other scaling applications. Multiple resource scaling can also be setup in minutes.

Best suitable cases would be, the capacity the spin up and spin down the EC2 instances and the way it works with AWS resources is way to good. And the best part is the interconnection between these resources are totally taken care by AWS internally.

The place where AWS can improve is the timing it takes to spin up the instances in short span of time.

If you have a website or application with large number of users, then Amazon EC2 Auto Scaling can help you a lot.
If you are not sure when and how many users can access resources same time, then you can start with basic configuration with auto scaling.
Your AWS server will manage server load automatically when user increases, same as it will reduce newly created server when less users.

Its a beneficial feature provided by AWS. Users should make use of this feature in the work systems to have full benefit of the cloud EC2 instance.

When you have a simple auto scaling use case and it does not require complex rules.

EC2 Auto Scaling is a foundational component of high availability architectures in AWS. It allows one to dynamically scale in response to key metrics - such as CPU utilization on the web nodes - or schedule scaling based on anticipated events - such as a flash sale for an e-commerce site. By scaling horizontally, one saves money by not having to scale up to peak traffic. By maintaining manageable traffic loads on each of the nodes in the autoscaling group, one minimizes the incidence of nodes in the autoscaling group failing, which translates to higher availability of the application served by the instances. This is not to mention the possibility of hardware failure on the AWS side, a low likelihood but totally possible event. High availability is not purely a frontend or backend concern. Anything you can do with EC2s that benefits from high availability benefits from autoscaling.

We used autoscaling to be able to take more traffic demand, we noticed our software would crash out at 1000 users and we wanted to be able to push that to 10x that amount, using autoscaling with the cloudwatch events and a load balancer we have managed to go up to 10000 users and beyond

I cannot think of any reason to NOT use EC2 auto-scaling except if you're just quickly testing something on a single instance and plan to terminate it after.

EC2 Autoscaling is a excellent solution for situations where you have a highly variable load, especially a load that requires large compute time per instance. Specifically, the startup time associated with starting a full VM in order to process requests makes this best suited to long running tasks such as jenkins test or compile jobs, or to situations where webserver load scales over large periods of time, like a site that's busy during the workday but not at night. Both these situations make excellent use of EC2 Autoscaling to control overall costs.

Auto manage and maintain instances when demand is spiking. But when instance limit is reached, quota needs to be reapply.

It is well suited for hosting files, websites, and applications on the internet rather than using multiple third parties.

Well suited when you really meet their requirement to handle increase/decrease resources based on demand. Without it, the process should be done manually and can be error-prone due to human intervention on repetitive tasks. Automation is the key word here. The problem would be the complexity or technicality it might add but with clear dev-ops team or documentation or a manual of how to use it might be fine.

For basic and non-complex set ups there [are] a lot of tutorials and information out there on the internet. You can solve pretty much any problem you are dealing with. AWS also provides different support plans. In our case, since we have a dev-ops team we do not need any support plan yet, but we can reconsider it in the future since we are growing.

Despite the problems with the lack of information (and help) on the new user interface, Amazon EC2 Auto Scaling is a terrific tool that show[s] us easily the power of "the cloud". Only a few years ago, increasing server capacity involved weeks or months of planning, and a hefty budget in some cases. Now, with the Auto Scaling capacity, you can increase and decrease capacity with a rule, and without a long commitment and investment on hardware.

The platform works as is. The help and tutorials on the help page can help you to setup the entire platform without problems, and also provides help on a huge variety of problems.

Amazon also provides support plans. We have the basic support plan, but Amazon offers three support tiers, and we know that it works perfect.