60000..." /> 60000..." /> 60000..."/>

Best Practices for AWS Elastic Beanstalk Auto Scaling Trigger Settings for Web Application?

1.4k views Asked by At

By default when you create an elastic beanstalk application, the scaling is set to scale based on "Average network out", and add instance when > 6000000, and remove instance when < 2000000.

What's the best practice for setting trigger settings for these? These default settings are obviously terrible, as we just had a bunch of ELB errors because our servers couldn't handle the traffic, the CPU wasn't high either, this was on t2.micro servers.

Previously, I've always used the CPU trigger, but I understand a server can stop accepting request, even before the CPU is maxed out.

What are some of the general best practices you use when setting the auto scaling trigger?

I can't seem to find any really, it just leaves you to try and come up with them by yourself. This is just for a standard web application, and server size may change over time. So what's one setting I can just generally use for everything?

0

There are 0 answers