Amazon EC2 Auto Scaling

It doesn't require any monitoring or manual changes.

It automatically scale up the infrastructure whenever required.

It put the extra instances on sleep in case of the reduced load to save money and electricity.

It replaces the instances automatically in case of bad health conditions.

Support of AWS is good but they take so much time to respond.

You require an experienced technical team to setup AWS EC2 Auto Scaling.

Dynamic scaling can be configured to respond to a wide variety of metrics and alerts

Predictive scaling allows one to get ahead of high traffic events rather than simply reacting to them

Health checks are configurable based on the needs of your application and architecture

It can be confusing if you have multiple scaling policies in effect for an autoscaling group and they conflict. In that case, conflict resolution is handled by whichever policy has the greater impact. It would be more ideal if there was intelligence preventing these kinds of conflicting policies

It can be confusing if you have conflicting and concurrent scale out and scale in policies in effect. In this case, the scale out action will take place, in order to ensure availability. It would be more ideal if there was intelligence preventing these kinds of conflicting policies

IAM is always a bit confusing and the appropriate service roles are required to configure autoscaling correctly

Recovery time is surprisingly fast.

It is always used as a preference in conversations with other engineers.

Compared to other IaaS, the scale is different.

For newcomers, it might be a little confusing.

The setup procedure's content still needs a knowledge of AWS.

Self-learning can be beneficial, however, I found it really beneficial to share my expertise and common processes with my colleagues.

Divide Load of the site on multi-server

It help is improving bill with high performance

It helps for high availability and site speed

It enable to sleep the resources which are not in use

It should be a more User friendly UI to set up

Automatic scaling in AWS saves credit and can be configured to respond to various metrics and alerts.

It is possible to anticipate high traffic events rather than simply reacting to them with predictive scaling.

Resource allocation is flexible. On-demand access to resources with high capacity is possible.

Auto-scaling servers for load sharing and failover works well when configured correctly.

It's expensive to run multiple health checks simultaneously, so make it easier for people to understand.

Auto-tuning and auto-suggestive tuning for ASGs can be automated using machine learning or other advanced techniques, or both.

Pricing is plus point as compare to other products

Less instructions needed to scale the load up and down

Sometime it takes time to give response when load is heavy

Lots of options which creates confusion for new users

Very cost effective.

Easy to set up and use.

Auto-scaling feature.

It can be rigid with the time periods for reserved instances.

Having multiple instances at the same time can be really expensive.

Sometimes there are issues that prevent you from accessing an instance.

It is so easy to configure and everything can be done through console as well.

CFT also supports Auto scaling which is very good thing when you keep your Infrastructure as a code.

It is one of the best tool if you need to control your EC2 instances.

Best thing is its totally free, we only pay for the EC2 resources which we use

Sometimes, Auto scaling takes time to spin up your instances if your traffic is so high in short span of time.

And, Auto scaling can be more efficient if we have only Load balancer in our architecture.

It has some limitations on setting up the Auto scaling infra.

Set some rules and auto delete instances

Auto assign resources based on our needs, which is perfect to stop the constant monitoring

EC2 more than Auto scaling, they could provide a graphic interface that helps the setup

Functions well when configured correctly

Price is reasonable

Would be better if it can support more types of rules

Sometimes will over-provision which results in a waste of resources.

Disaster recovery.

Ensures repeatability.

Handling expansion and growth.

Make it easier to understand health checks.

Use machine learning or other advanced techniques to auto-tune or auto-suggest tuning improvements to ASGs.

Automate the creation of them through a service broker on EKS.

AWS Autoscaling is a beneficial feature , saves a lot of credit

Resources can be provisioned as need be. High capacity resources can be allocated when required.

Auto spinning of servers for load sharing and failover

Autoscaling helps replicating the OS VM, however , he application software configuration is a missing part. Manual Intervention is required to set up the configuration for the new spun EC2 instances to be productive.

Launch configuration allows contol of each instance.

Launch groups are easy to configure

Very Stable in Production

Integration with CloudWatch to monitor the Group

AMI dropdown in Launch configuration is not user friendly. The list is long

There is a learning curve to understand AWS terminology

Automation.

Increase/decrease capacity on demand based on rules.

Very flexible, but technical tool.

See server logs seamless[ly] while increasing/decreasing capacity.

Be much easier to manage and configure [for] a non-technical person

Might need other tools to make admins tasks easier.

Automatic capacity increases based on rules.

No user intervention.

Very flexible tool.

Sometimes decrease rules may not work.

New scaling policy creation is a bit confusing and do[es] no[t] have help.

Previous scaling policy screen no longer exists, so you need to understand what new interface actually does.