AWS Pricing Calculator - AWS Pricing Calculator is a cost-estimation tool for modeling the expected charges of proposed AWS workloads and changes to existing environments.

Combine supported AWS services into one estimate to model an application rather than a single resource. Include supporting components such as storage and databases instead of treating compute as the entire workload cost.

Select the deployment Region for supported service configurations. Compare equivalent designs across Regions while accounting separately for latency, data residency, and transfer requirements.

Enter the pricing dimensions relevant to each supported service, such as runtime, storage, requests, and provisioned performance. Use measured workload characteristics or explicit assumptions rather than leaving important inputs at defaults.

Organize services into groups representing application tiers, environments, or cost ownership boundaries. This makes it easier to review which components contribute to the total.

Compare supported purchase options, including On-Demand and applicable commitment-based pricing. Check term length, payment assumptions, and expected utilization before interpreting a lower estimated rate as a realizable saving.

Save and share public estimates using generated links, and export estimate details for planning documents. Avoid sensitive information in estimate metadata because a shared link is not an account-level access-control mechanism.

Use the console experience to model proposed workloads within an AWS account context. Available pricing and discount preferences depend on the workflow and account permissions.

Use supported console workflows to evaluate changes against an existing billing baseline. This is useful when existing usage and commitments make incremental cost different from a standalone public estimate.

Estimate the expected cost of compute, databases, storage, and supporting infrastructure before approving a design. Document operating hours, request volume, and retention assumptions so reviewers can reproduce the result.

Model a proposed AWS deployment for an existing application and compare alternative resource configurations. Keep migration expenses, licensing obligations, and operational labor separate unless explicitly included in the analysis.

Compare Single-AZ, Multi-AZ, and multi-Region designs using the same demand assumptions. Include replicated storage, additional capacity, and relevant transfer charges rather than comparing only primary resources.

Compare supported commitment-based prices with an On-Demand baseline for stable workloads. Validate anticipated utilization and existing commitment coverage before purchasing Savings Plans or Reserved Instances.

Create scenarios for changes in users, request rates, data retention, and runtime. Use the results to identify whether storage, requests, compute, or networking becomes the dominant cost driver.

Use an account-aware bill scenario to assess a proposed workload change against existing spending. Compare the scenario with actual billing data after implementation to refine future assumptions.

Creating workload estimates in the authenticated AWS Pricing Calculator console experience is free. Deploying the resources described by an estimate incurs the applicable service charges.

The public AWS Pricing Calculator is free to use. The infrastructure charges displayed in an estimate are projected AWS service costs, not fees for creating the estimate.

The console bill-estimation workflow includes five free bill estimates per month, followed by a charge of $2 for each additional bill estimate generated. These estimation fees are separate from the projected infrastructure charges shown in the result.

AWS Cost Explorer

Cost Explorer complements calculator estimates by exposing historical cost and usage for validating assumptions; it does not automatically synchronize public estimates. For example, inspect recent EC2 runtime and S3 usage before preparing a revised estimate, then compare actual charges with the estimate after deployment. Authenticated bill-estimation workflows provide a separate account-aware approach to modeling changes against existing usage.

Amazon EC2

The calculator models supported EC2 configurations using inputs such as Region, instance type, operating system, runtime, and purchase option. For example, estimate a fleet of Linux application servers running continuously and compare it with a schedule that stops development servers outside working hours. This is a pricing relationship, not a mechanism for launching instances.

Amazon RDS

Estimate supported RDS configurations using database engine, instance capacity, deployment option, storage, and other applicable dimensions. For example, compare a Single-AZ development database with a Multi-AZ production deployment while keeping data volume and workload assumptions consistent. Include applicable backup, I/O, and licensing considerations.

AWS Lambda

Model Lambda charges using supported inputs such as request count, execution duration, memory allocation, and architecture. For example, estimate a function handling several million monthly events using measured average duration from a representative test. Add related API, logging, queue, and storage costs as separate services when the application uses them.

Amazon S3

Use supported S3 pricing inputs to estimate storage, requests, retrieval, and transfer for an object-storage workload. For example, model an application that stores uploaded files in S3 Standard and moves older objects to an archival class. Include lifecycle transition requests and expected retrieval activity rather than comparing storage rates alone.