-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define Automatic scaling policy #24
Comments
"What are the conditions that should be met for us to turn this on?" |
Determining the proper thresholds will require data from monitoring to determine how the machines handle load. Helpful documentation for how to set up scaling policies: https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html |
I think the scaling policy that we need will look at the number of messages in the various sqs queues, and use that to determine how much to scale. Unfortunately, this will require spinning up a new service that just reads and reports that data to Cloudwatch. That is what I will now be working on. |
After further discussions, it doesn't look I'll have time to implement this design. It would effectively require spinning up a new service (per-enviroment) that just watches the SQS queues (probably just HIGH_PRIORITY and VIDEO) and triggers a Cloudwatch alarm when the queue lengths get too long. The scaling group will then spin up new instances accordingly. |
No description provided.
The text was updated successfully, but these errors were encountered: