4 Pricing, Billing, and Support
Learn how AWS usage-based pricing works, how to monitor and allocate costs, what support plans provide, and how to optimize spending without compromising workload requirements.
How AWS pricing works
AWS pricing is generally usage-based: charges depend on the resources and services consumed and on the pricing rules for each service. Services can measure usage by compute time, storage capacity, requests, or data transferred. The billing unit depends on the service and sometimes the AWS Region, so check service pricing before deployment. A resource's direct operating cost may not include associated storage, requests, or data-transfer charges.
Common pricing approaches
: Pay for usage without a long-term commitment. This is flexible for variable workloads or when trying a service.
: Receive discounts on eligible compute usage in exchange for a consistent hourly spend commitment, generally for one or three years. Compute apply across eligible EC2, Fargate, and Lambda usage; other plan types have different eligibility.
: Receive discounted pricing for qualifying usage by committing to specific usage attributes for a term. Some options also reserve capacity, depending on the service and option selected.
: Use spare EC2 capacity at a discount. Because Spot capacity can be interrupted, it is suited to workloads that tolerate interruption, such as flexible batch jobs.
: Try eligible services within specified usage limits or time periods. Exceeding those limits can incur charges, so review the terms and monitor usage.
A company could use capacity for unpredictable traffic, a Savings Plan for steady baseline compute, and for interruptible data-processing jobs. Commitments can lower the price, but may cost more than if usage falls below the committed level.
The estimates planned costs before deployment. Estimates depend on the supplied inputs and assumptions, and Free Tier usage is not automatically included in calculator estimates.
Billing and cost-management tools
The Billing and Cost Management console is the central place to review charges, invoices, payment settings, and cost-management features. Actual charges can change as usage occurs, so an estimate is not a guaranteed final bill.
Tools for understanding and monitoring costs
visualizes, filters, and groups historical cost and usage. It can create reports and forecast costs.
sets cost, usage, or other supported budgets and sends alerts when actual or forecast amounts reach thresholds. Budgets alert you; they do not automatically stop all spending.
identifies unusual spending patterns and sends alerts for investigation.
Cost and Usage Reports / Data Exports provide detailed cost and usage data for deeper analysis or integration with other tools.
and Cost Categories organize costs by projects, teams, or environments for reporting and allocation. Resource tags must be activated for cost allocation, and not every resource or charge can necessarily be tagged.
For example, a team can tag resources with Project and Environment, activate those tags for cost allocation, and use Cost Explorer to compare development and production spending. can alert the team if monthly cost crosses a chosen threshold. Billing data and budget alerts are not necessarily instantaneous, so budgets should complement—not replace—regular cost review.
Invoices across organization accounts
With , a management account receives and pays the consolidated bill for its member accounts. This makes organization-wide charges easier to view and can combine eligible usage for volume pricing and applicable Reserved Instance or benefits. Each account remains distinct: consolidated billing does not by itself merge accounts' resources or permissions.
AWS Support plans
Support plans determine what help and guidance are available. Support charges, when applicable, are separate from service usage charges. is included for all AWS customers and provides resources such as documentation, community access, account and billing assistance, and core health information. Paid plans add technical support and operational guidance.
As of 2026, AWS lists Business Support+, Enterprise Support, and Unified Operations as its enhanced support plans. They differ in technical support access, response targets, and proactive or expert guidance; higher tiers are designed for increasingly critical workloads. Features and pricing can change, so consult AWS's current comparison before selecting a plan.
Older study materials may refer to Developer, Business, Enterprise On-Ramp, or Enterprise plans. AWS says it is transitioning existing customers from those older plans, which are scheduled to shut down on January 1, 2027.
A practical cost-optimization cycle
Cost optimization means meeting workload requirements without paying for unnecessary resources; it does not mean simply selecting the lowest-priced option. A practical cost-management cycle is to measure, allocate, optimize, commit carefully, and monitor.
Measure: Estimate costs before deployment and inspect actual usage regularly.
Allocate: Use consistent tags, accounts, and cost categories to identify which teams or workloads create charges.
Optimize: Right-size resources, shut down idle nonproduction resources, remove unused storage or other resources, and choose a suitable pricing model for stable versus flexible workloads.
Commit carefully: Consider or only after reviewing sustained usage and understanding the term and covered usage.
Monitor: Use budgets and anomaly alerts, then investigate unexpected changes rather than assuming an alert automatically prevents charges.
Turning off a development instance outside working hours can reduce compute charges for the hours it is stopped. Reviewing storage and data-transfer costs can also help identify potential savings. Together, regular measurement, clear cost allocation, waste removal, and commitments based on dependable usage support more predictable spending.