Course contentsShow
← Cloud and Infrastructure
Lesson 292 of 2,9896. Auto ScalingFree lesson

Minimum, Maximum, and Desired Capacity

Configuring capacity constraints to control fleet size boundaries and initial desired state.

Minimum, Maximum, and Desired Capacity

You'll learn: How to set boundaries and starting points for your Auto Scaling group's fleet size.

The Control Knobs for Your Fleet

When you create an Auto Scaling group, you need to tell it three critical numbers that define how many instances it can manage:

Minimum Capacity – The absolute floor. Your Auto Scaling group will never scale below this number, even during periods of zero traffic. Think of this as your "always-on" baseline.

Maximum Capacity – The ceiling. Your Auto Scaling group will never scale above this number, no matter how high demand gets. This protects you from runaway costs or resource exhaustion.

Desired Capacity – Your starting point and target. This is how many instances you want running right now under normal conditions. Auto Scaling will work to maintain this number unless metrics trigger scaling actions.

A Restaurant Analogy

Imagine managing a restaurant's waitstaff:

  • Minimum = 2 waiters (you never operate with fewer, even on slow days)
  • Maximum = 10 waiters (your dining room physically can't accommodate more)
  • Desired = 5 waiters (your typical weeknight sweet spot)

During a dinner rush, Auto Scaling might add waiters up to 10. During a slow period, it might reduce to 2. But you start with 5 and adjust from there based on demand.

Configuration Example

When you set up Auto Scaling:

  • Minimum: 2
  • Maximum: 8
  • Desired: 4

Auto Scaling immediately launches 4 instances. As load increases, it can grow to 8. As load decreases, it can shrink to 2.

Key Takeaway: Minimum, maximum, and desired capacity define the boundaries and starting state of your Auto Scaling group—setting the floor, ceiling, and initial target for your fleet size.