Cloud concept · Updated

Usage-Based Pricing - Usage-based pricing charges for measured cloud resource consumption or provisioned capacity according to published rates and billing rules.

In short

Cloud costs are calculated from billable quantities such as instance runtime, stored data, requests, and data transfer rather than solely from an upfront infrastructure purchase. Understanding these meters helps engineers compare purchasing options, estimate total workload costs, and avoid paying for idle resources or unsuitable commitments.

Cloud Concepts Hub →

6 key aspects of Usage-Based Pricing

Effective usage-based pricing decisions combine accurate billing meters, suitable purchasing commitments, workload-aware storage choices, and continuous cost monitoring.

01
Explicit billing meters

Charges follow defined units such as compute time, requests, stored bytes, or provisioned throughput. Identify every meter in the workload and check its billing granularity and minimums.

02
Consumption and allocation both matter

Some resources charge for actual activity, while others charge for capacity kept available. Idle virtual machines, retained volumes, and unused capacity reservations can therefore remain billable.

03
Commitment-based rate reductions

Reserved Instances and Savings Plans exchange a term commitment for lower eligible compute rates. Size commitments around a dependable baseline because unused commitments can erase expected savings.

04
Price, availability, and tenancy are distinct

Spot discounts introduce interruption risk, capacity reservations address availability, and dedicated tenancy addresses isolation or licensing needs. Do not assume that a discount reserves capacity or that dedicated hardware reduces costs.

05
Storage cost depends on access patterns

Compare storage rates alongside request, retrieval, transition, and performance charges. Minimum storage durations and restore times can make a low-cost archive tier unsuitable for frequently accessed or short-lived data.

06
Estimation and ongoing cost control

Estimate with current regional pricing, then compare the assumptions with actual usage and billing data. Alerts, ownership tags, rightsizing, and cleanup processes help control a variable bill.

Cloud services for Usage-Based Pricing

A workload can combine EC2 for virtual machines, Lambda for event-driven processing, S3 for objects, and EBS for block storage, with each service contributing distinct billing meters. AWS Pricing Calculator models the expected combined cost before deployment, including the effects of selected configurations and purchasing options. After deployment, AWS Cost Explorer helps compare actual costs and usage with those assumptions. Engineers can then adjust compute commitments, remove unused volumes, tune function resources, and change storage classes while accounting for performance, availability, retrieval, and interruption requirements.

Amazon EC2Amazon EC2

EC2 illustrates how runtime, instance configuration, purchasing option, and tenancy affect compute charges. On-Demand Instances, Reserved Instances, Spot Instances, Savings Plans eligibility, Dedicated Hosts, Dedicated Instances, and Capacity Reservations address different cost and operational requirements.

Amazon S3Amazon S3

S3 charges can include storage volume, requests, retrievals, lifecycle transitions, and data transfer. Storage class selection should reflect access frequency, retention period, object sizes, and retrieval requirements.

AWS LambdaAWS Lambda

Lambda commonly meters requests and execution duration, with duration charges depending on allocated memory and processor architecture. Provisioned Concurrency and associated services can create additional charges beyond ordinary invocation costs.

AWS Pricing Calculator

AWS Pricing Calculator converts planned configurations and usage assumptions into estimates. It helps compare purchasing options and workload designs, but its results depend on the accuracy and completeness of the inputs.

AWS Cost ExplorerAWS Cost Explorer

Cost Explorer analyzes incurred costs and usage to reveal trends and cost drivers. It helps validate estimates and evaluate whether resource changes or purchasing commitments are producing the intended savings.

Usage-Based Pricing exam questions

Real practice exam questions on Usage-Based Pricing, with the correct answer and its explanation. Answer them with every option in the exam simulator.

AIF-C01

A company runs a generative AI application using Amazon Bedrock on-demand inference in two AWS Regions. Last month's charges increased unexpectedly. Before changing models or purchasing provisioned capacity, the finance team wants to identify which Region and billed usage categories contributed most to the increase compared with the previous month. Which approach best meets this requirement without adding application instrumentation?

Show answerCORRECT ANSWER

Use AWS Cost Explorer to filter costs to Amazon Bedrock, select both months, and group the costs by Region and usage type.

Cost Explorer analyzes historical AWS costs and usage. Filtering to Amazon Bedrock and grouping by Region and usage type helps identify where charges increased and which billed usage categories contributed to the increase.

MLA-C02 (beta)

A company hosts an open-weight foundation model on an Amazon SageMaker AI real-time endpoint for document extraction. The endpoint must run two instances continuously for availability. Each deployment configuration below has been tested with representative production prompts, output lengths, and peak traffic. Every configuration provides sufficient throughput with the same two-instance fleet.

The application requires an extraction accuracy of at least 96% and a p95 end-to-end response latency of no more than 3 seconds. The company can change model precision and serving configuration. The model has no licensing or per-token charges.

Tested configuration Price per instance-hour Extraction accuracy p95 response latency
FP16 model, standard batching $12 98% 2.1 seconds
INT8-quantized model, standard batching $7 97% 2.4 seconds
INT4-quantized model, standard batching $4 94% 2.0 seconds
INT8-quantized model, aggressive batching $6 97% 4.2 seconds

Prices are illustrative. All other costs are identical, and no purchasing discounts apply. Which deployment should an ML engineer recommend to minimize ongoing inference compute costs while meeting the application requirements?

Show answerCORRECT ANSWER

Use the INT8-quantized model with standard batching on two instances, for a total compute cost of $14 per hour.

Its 97% extraction accuracy exceeds the 96% minimum, and its 2.4-second p95 latency is within the 3-second limit. At two instances × $7 per instance-hour, it is the least expensive tested configuration that satisfies both requirements. These endpoint compute charges depend on provisioned instance runtime rather than token counts.

CLF-C02

A company uses AWS Pricing Calculator to estimate the monthly cost of a test environment. An Amazon EC2 On-Demand instance will remain running throughout a 30-day month, but employees will use it for only 2 hours each day. Its attached Amazon EBS volume will remain provisioned at 200 GB, with only 50 GB containing data. Considering only instance runtime and EBS storage capacity, which usage assumptions should the company enter?

Show answerCORRECT ANSWER

720 instance hours and 200 GB of EBS storage for the full month

The running instance incurs runtime charges for 24 hours × 30 days, or 720 hours. The EBS volume incurs storage charges for its full 200 GB of provisioned capacity throughout the month, regardless of how much contains data.

Practice Usage-Based Pricing in a full exam

Questions on Usage-Based Pricing in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Usage-Based Pricing

3 min read

Usage-based pricing connects a cloud bill to measurable quantities of resources or activity. A workload might incur charges for compute seconds, gigabyte-months of storage, API requests, database operations, and outbound data transfer. A useful starting estimate is billable quantity multiplied by the applicable rate, summed across all chargeable components. Actual calculations can also include pricing tiers, minimum charges, discounts, commitments, and free allowances.

The important distinction is that measured usage does not always mean useful application work. A running virtual machine typically incurs compute charges even when its CPU is idle. A provisioned disk usually incurs storage charges even when it contains little data. Billing granularity and minimum durations vary by service and configuration, so engineers should verify the relevant pricing rules rather than assume everything is billed per second.

Compute purchasing options change the rate, commitment, availability, and interruption characteristics of the same workload. AWS On-Demand Instances generally require no long-term commitment and suit short-lived or unpredictable workloads. Reserved Instances provide billing discounts for matching usage in exchange for a one- or three-year commitment, with payment options that can include no upfront, partial upfront, or all upfront payment. AWS Savings Plans instead commit to a consistent amount of eligible compute spending per hour for one or three years. Both approaches can reduce steady-state costs, but unused commitments still cost money.

Discounts and capacity guarantees are separate considerations. Regional EC2 Reserved Instances do not reserve capacity; zonal Reserved Instances include a capacity reservation in the selected Availability Zone. Savings Plans do not reserve capacity. EC2 On-Demand Capacity Reservations hold matching capacity in a particular Availability Zone, and unused reserved capacity is generally charged at the applicable On-Demand rate. Eligible discounts can apply to matching reservations, but a Capacity Reservation itself is not a discount mechanism.

Spot Instances use spare compute capacity at discounted rates and can be interrupted when the provider needs that capacity back. They suit fault-tolerant batch processing, distributed workers, and other workloads designed to recover from interruptions. Dedicated Instances run on hardware dedicated to one customer, while Dedicated Hosts allocate a physical server and provide host-level placement and licensing visibility. Dedicated tenancy is an isolation or licensing choice, not inherently a cheaper pricing option; host allocation and dedicated-tenancy charges must be evaluated separately.

Storage pricing requires comparing the entire access pattern, not just the advertised storage rate. Object storage classes can charge separately for stored bytes, requests, retrievals, lifecycle transitions, and data transfer. In Amazon S3, infrequent-access and archive classes can offer lower storage rates but introduce retrieval charges, minimum billable object sizes, minimum storage durations, or restore delays, depending on the class. Frequently accessed application assets and rarely restored compliance records therefore need different storage choices.

Block storage has different billing dimensions. Amazon EBS commonly charges for provisioned volume capacity, while some volume types also charge for provisioned performance beyond included levels. Snapshots introduce additional storage charges. Stopping an EC2 instance generally stops its instance compute charges, but retained EBS volumes and other associated resources can continue billing. Similarly, serverless execution can reduce idle compute spending without eliminating charges for requests, execution duration, logs, storage, or networking.

For example, an application could cover its predictable compute baseline with a commitment, serve temporary demand with On-Demand capacity, and run restartable overnight processing on Spot. Its recent files might remain in a frequently accessed storage class while older files transition to archival storage. This arrangement only saves money if commitments are used, interruptions are acceptable, and retrieval and transition costs do not outweigh storage savings.

Use official service pricing pages to check regional rates, billing units, operating system or licensing differences, and transfer charges. AWS Pricing Calculator estimates costs from workload assumptions; AWS Price List APIs provide programmatic pricing information for supported services. AWS Cost Explorer helps analyze actual spending and usage, while AWS Budgets can notify teams when configured thresholds are crossed. Estimates are not guaranteed bills, and budget alerts are not automatic spending caps. Reconcile estimates with observed usage and adjust resource sizes, schedules, storage classes, and commitments accordingly.

Learn Usage-Based Pricing in lessons

8 short lessons on Usage-Based Pricing in 4 certification courses.

and 2 more lessons

Open the lessons