<p>First of all, the number of connections is not a common metric to use for autoscaling. Much more common is CPU utilization or possibly the amount of network traffic.</p>

<p>If you are happy with the performance of your application at a certain utilization level, you can modify the corresponding alarms configured in the auto-scaling group, so that autoscaling happens only at higher levels of your metric.</p>

<p>Secondly, you can limit auto-scaling to a certain number of instances. When this number is reached, no further scaling will occur.</p>

<p>Finally, if your traffic has a significant proportion of GET requests, it may be easiest to ensure caching headers are set appropriately and traffic is routed through a <a href="https://en.wikipedia.org/wiki/Amazon_CloudFront" rel="nofollow noreferrer">CloudFront</a> distribution before it reaches the load balancer. This will likely eliminate most of the GET requests from the load balancer altogether.</p>

CC BY-SA 4.0
2019-08-22T08:09:52.393Z
2019-08-22T22:23:55.493Z
2019-08-22T22:23:55.493Z
jdog
<p>If I set autoscaling for an EC2 instance in Amazon Web Services, how can I set optimized autoscaling for large numbers of connections in order to avoid unusual autoscaling?</p>

CC BY-SA 4.0
2019-08-22T12:15:02.377Z
What is *"AutoScalin"*? Do you mean *"autoscaling"*?
Peter Mortensen
<amazon-web-services><amazon-ec2>
How to avoid a high number of requests for avoiding Amazon AWS EC2 instance AutoScalin?
saddique
# How to avoid a high number of requests for avoiding Amazon AWS EC2 instance AutoScalin?

(Asked by: username_0 on 2019-08-19)

If I set autoscaling for an EC2 instance in Amazon Web Services, how can I set optimized autoscaling for large numbers of connections in order to avoid unusual autoscaling?

**Tags:** amazon-web-services, amazon-ec2

> **Comments:**
> **username_1**: What is *"AutoScalin"*? Do you mean *"autoscaling"*?  

---

## 1 answers

### Answer by username_2 on 2019-08-22. Score: 1 | Accepted answer

First of all, the number of connections is not a common metric to use for autoscaling. Much more common is CPU utilization or possibly the amount of network traffic.

If you are happy with the performance of your application at a certain utilization level, you can modify the corresponding alarms configured in the auto-scaling group, so that autoscaling happens only at higher levels of your metric.

Secondly, you can limit auto-scaling to a certain number of instances. When this number is reached, no further scaling will occur.

Finally, if your traffic has a significant proportion of GET requests, it may be easiest to ensure caching headers are set appropriately and traffic is routed through a [CloudFront](https://en.wikipedia.org/wiki/Amazon_CloudFront) distribution before it reaches the load balancer. This will likely eliminate most of the GET requests from the load balancer altogether.


---

