AWS calculators

Practical calculators for common AWS cost line items. Use your own pricing assumptions.

CloudFront cost
Bandwidth + requests model with your pricing assumptions.
EKS cost
Node sizing from requests, then apply per-node pricing.
EC2 cost
Instance count x $/hour x uptime.
S3 cost
Storage + requests + optional egress + replication.
S3 request cost
GET/PUT request fees using your per-1k assumptions.
S3 replication cost
Replicated GB/month x $/GB.
VPC data transfer cost
Estimate GB/month transfer spend from $/GB.
CloudWatch Logs cost
Ingestion + retention storage baseline estimate.
CloudWatch Logs Insights cost
Estimate query scan costs from GB scanned.
CloudWatch Metrics cost
Custom metrics + alarms + dashboards + API requests.
CloudWatch Alarms cost
Alarm-month estimate from standard/high-res/composite counts.
Lambda cost
Requests + GB-seconds compute estimate with your pricing inputs.
Fargate cost
vCPU-hours + memory GB-hours estimate from average running tasks.
Lambda vs Fargate (cost compare)
Side-by-side compute-only comparison from consistent inputs.
Fargate vs EC2 (cost compare)
Compare vCPU/GB-hours vs instance-hours with shared assumptions.
ECS on EC2 vs Fargate (cost compare)
Compute-only comparison for ECS launch types (EC2 vs Fargate).
ECS task sizing
Estimate required task count from vCPU/memory demand and utilization.
RDS cost
Compute + storage + backups + I/O requests estimate.
DynamoDB cost
Reads + writes + storage estimate using your pricing inputs.
EBS cost
Storage + optional IOPS/throughput performance charges.
EBS snapshot cost
Estimate snapshot storage from churn and retention.
SQS cost
Estimate SQS request cost from messages and retries.
NAT gateway cost
Hourly gateway fees + per-GB processed charges.
VPC interface endpoint cost
Endpoint-hours + per-GB processing (PrivateLink).
Load balancer cost (ALB/NLB)
Fixed hourly + LCU/NLCU usage estimate.
ALB LCU / NLB NLCU estimator
Estimate capacity units/hour from metrics and drivers.
API Gateway cost
Request fees + response transfer estimate.
API Gateway access log cost
Estimate log ingestion + retention from requests and log size.
CloudTrail cost
Event-based cost estimate with your per-100k pricing inputs.
WAF cost
ACLs + rules + request charges estimate.
ECR cost
Container registry storage + egress estimate.
Route 53 cost
Hosted zones + DNS queries + health checks.
S3 Glacier / Deep Archive cost
Storage (GB-month) + retrieval (GB and requests).
SNS cost
Publish + delivery + optional payload transfer.
SES cost
Email sending estimate from volume + payload.
KMS cost
Key-months + request charges estimate.
SSM Parameter Store cost
Advanced parameters + API call charges estimate.
Secrets Manager cost
Secret-months + API call charges estimate.

How to get your inputs

  • Requests: API Gateway/ALB metrics or application dashboards (RPS and total requests).
  • Transfer: VPC Flow Logs, CloudFront logs, or Cost Explorer usage types (GB).
  • Storage: S3 storage metrics and EBS volume size/IOPS from CloudWatch.
  • Compute: instance-hours from billing exports and uptime schedules.

Result interpretation (AWS)

  • Use a baseline month and a peak month; most AWS bills swing with traffic and retries.
  • If transfer dominates, split internet egress, inter-AZ, and inter-region before tuning rates.
  • If requests dominate, validate request counts, retries, and per-request unit size.
  • For compute, check uptime hours and average utilization assumptions before changing instance types.
  • For logs/metrics, retention days and query scan volume usually matter more than storage size.
  • When the estimate is off, adjust the driver inputs, not the math.

Scenario planning (AWS)

  • Baseline: average traffic, stable cache hit rate, and normal retry levels.
  • Peak: 2x-4x requests and egress for launches or incidents.
  • Region mix: split rates if traffic or storage spans multiple regions.
  • Commitments: compare on-demand vs Savings Plans with realistic utilization.
  • Logging burst: double ingestion for incident months and check retention impact.

Validate after changes (AWS)

  • Compare estimated drivers to Cost Explorer usage types (requests, GB, hours).
  • Verify region and AZ assumptions after routing, caching, or replication changes.
  • Check that log retention and query volume match your new policy.
  • Review top line items for a week to confirm the model still fits.

Related guides

For step-by-step estimation guidance and pitfalls, browse AWS cost guides.