Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

On-demand vs provisioned

This revision card explains On-demand vs provisioned. It starts from the need that wrong mode surprises either the bill or the throttle graph. It describes on-demand = pay per request; provisioned = set RCU/WCU (+ auto scaling). The how-to section notes spiky/unknown , then on-demand; steady , then provisioned + AS; reserved if committed. An example on the card is rohan Deshmukh starts labs on-demand and revisits after a week of metrics.

On-demand vs provisioned Wrong mode surprises either the bill or the throttle graph. On-demand = pay per request; provisioned = set RCU/WCU (+ auto scaling). Spiky/unknown → on-demand; steady → provisioned + AS; reserved if committed. Rohan Deshmukh starts labs on-demand and revisits after a week of metrics.
On-demand vs provisioned · Download PNG
Read card text

What this card says

Why do we need it?

Wrong mode surprises either the bill or the throttle graph.

What is it?

On-demand = pay per request; provisioned = set RCU/WCU (+ auto scaling).

on-demand

How to do it

Spiky/unknown → on-demand; steady → provisioned + AS; reserved if committed.

Example

Rohan Deshmukh starts labs on-demand and revisits after a week of metrics.

See all AWS revision cards