CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2amazon-elastic-beanstalkautoscaling
Si-N
Si-N

Reputation: 1495

Elastic Beanstalk NetworkOut auto scaling

I have an Elastic Beanstalk app running on t2.medium with autoscaling enabled. EB automatically sets a default autoscale trigger of 6,000,000 bytes over a 5 minute period on NetworkOut. We have a meeting app, so many people load the page at the same time, this causes a spike of NetworkOut data for probably a 10 minute period.

The only place I can get info on what the bandwidth of a t2.medium instance is here:

EC2 instance types's exact network performance?

This says 250-300 MBit/s, which over 5 minutes is a much larger amount of data (~9Gb, unless my calculations are wrong).

I possibly incorrectly assumed EB would set a sensible figure for autoscaling but this seems miles out. Do you think it's safe to increase the autoscaling trigger to something closer to the available bandwidth?

Upvotes: 11

Views: 6297

Answers (1)

Brian
Brian

Reputation: 5491

The default NetworkOut alarms are kind of silly - the <2,000,000 one in particular, since it often leads to frequent termination/rebuild of low-use instances.

I believe, however, what the >6,000,000 alarm is alerting on is that outgoing bandwidth from your instance(s) has exceeded 6Mbit/min for five consecutive minutes. That's still well below the maximum bandwidth in the SO post you linked, but not quite as egregious as 6MBit total for five minutes.

Regardless, there's no right or wrong answer - every application is going to have different alarm criteria. I would suggest that you gradually increase the alarm threshold while monitoring your instance's performance until you find an appropriate level that provides a good user experience with over-alerting.

Upvotes: 12

Related Questions