Pricing and Billing

AWS Pricing and Billing

AWS pricing varies by service, Region, consumption dimension, commitment, data movement, and support plan. Cost management begins with architecture and ownership: a technically idle resource can still incur storage, address, log, snapshot, or reservation charges.

Core ideas

• On-demand pricing offers flexibility, while Savings Plans and reservations exchange commitment for eligible discounts.
• Cost Explorer analyzes historical and forecasted cost and usage.
• AWS Budgets tracks thresholds but is not a guaranteed hard spending cap.
• Tags, linked accounts, and cost categories allocate spend to teams, products, and environments.

Design and operating model

Estimate with the AWS Pricing Calculator, deploy a small measured environment, compare actual billing dimensions, then refine the model. Create owner and environment tags, budget alerts, anomaly detection, and recurring reviews. Optimize waste first, then size, schedule, select pricing models, and redesign expensive transfer paths.

Example

aws ce get-cost-and-usage \
  --time-period Start=2026-07-01,End=2026-08-01 \
  --granularity MONTHLY \
  --metrics UnblendedCost \
  --group-by Type=DIMENSION,Key=SERVICE

Run examples in a disposable training account and replace Regions, identifiers, policies, resource sizes, and names with reviewed values. Verify commands with the current AWS CLI and service documentation before production use.

Production guidance

• Review data transfer, NAT processing, logs, snapshots, idle addresses, and provisioned database capacity.
• Do not purchase commitments before usage is stable, attributable, and understood.
• Balance cost against availability, security, performance, delivery speed, and recovery objectives.

The chapter quiz follows the lesson and checks both service vocabulary and architecture decisions.