I have 2 autoscaling policies in AWS one for CPU and one for memory restore when CPU goes high autoscaling adds one instance but as memory restored policy terminates that instance quickly
Asked
Active
Viewed 335 times
-1
-
1What exactly is the problem and the question you have? – stijndepestel Aug 16 '21 at 06:01
-
conflicting Autoscaling policies with each other – Sahil Dubey Aug 16 '21 at 09:02
-
please update your question to include a clear problem and a lot more context if you expect a response to help you out. Also include any related configuration of the services. Please refer to this for more information: https://stackoverflow.com/help/how-to-ask – stijndepestel Aug 16 '21 at 09:44
1 Answers
2
Do not use two different scaling policies on an Amazon EC2 Auto Scaling group.
They will not be aware of each other and will attempt to scale the group separately.
For example, if one metric is high and the other is low, Auto Scaling will trigger both scaling policies, which will cause instances to be added and terminated in a continuing cycle.

John Rotenstein
- 241,921
- 22
- 380
- 470
-
So you mean i need to create two groups one for memory and another for CPU right? – Sahil Dubey Sep 02 '21 at 11:03
-
No, I means that you should pick only one measurement (CPU _or_ RAM, but not both) and only scale on that single metric. – John Rotenstein Sep 02 '21 at 11:21