I have observed it takes 15 data points in 15 minutes to trigger an alarm and start scale in and I could not find an option to change or adjust this behavior.
Can we change this behavior or we will have to define another scaling policy to scale in?
It seems like its the default settings for Target Tracking scaling policy for cpu utilization that
- CPUUtilization > 50 for 3 datapoints within 3 minutes [will trigger high alarm]
- CPUUtilization < 35 for 15 datapoints within 15 minutes [will trigger low alarm]
Is this true?