scaling policy
A rule that changes a group’s desired capacity based on a metric, such as average processor use or requests per instance.
In more detail
Choose a signal that follows the work users wait for: request count or queue depth often tracks demand better than processor use. A policy needs a target or steps, a cooldown or warm-up, and a maximum.
Related terms
- Auto Scaling group — An EC2 feature that keeps a desired number of identical instances running, replacing failed ones and adding or removing them as load changes.
- cooldown — A waiting period after a scaling action during which further scaling is held back, so the system can settle.
- metric — A number measured over time, such as requests per second or error count, that shows how a system behaves in aggregate.
- oscillation — When an automatic control keeps overshooting, such as scaling out, then in, then out again, instead of settling.
Taught in
- Scaling Patterns: When Capacity Arrives Too Late — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- The Full Mock And Your Review Plan — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Decoupling: SQS, SNS, EventBridge And Step Functions — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Load Balancers And Auto Scaling: Capacity That Arrives On Time — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Long-Stem Clinic: The Phrase That Decides — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- Elasticity and Scale — Cloud Infrastructure & Hyperscaler Architecture
- Auto Scaling Groups — Cloud Infrastructure & Hyperscaler Architecture
- NoSQL and DynamoDB — Cloud Infrastructure & Hyperscaler Architecture