AWS Fargate Cost Calculator

Estimate Fargate-style compute cost from average running tasks, vCPU per task, memory per task, and days per month. Compare baseline vs peak usage with your region pricing.

Inputs

Running tasks (average)
Avg $18.01 per task-month.
vCPU per task
Memory (GB) per task
Hours/day
Days/month
Use 30.4 for an average month.
Monthly hours: 730
Price ($ / vCPU-hour)
Price ($ / GB-hour)
Scenario presets
Tip: for autoscaling services, use average running tasks over the month (not peak).

Results

Estimated monthly Fargate compute total
$54.03
vCPU-hours
1,094
GB-hours
2,189
vCPU cost
$44.30
Memory cost
$9.73
Cost per task
$18.01

How to get your inputs

  • Tasks: use average running tasks from ECS metrics, not peak or desired count.
  • Task size: pull vCPU and memory from the task definition (GB, not MB).
  • Pricing: use region-specific vCPU-hour and GB-hour rates.
  • Schedule: hours/day and days/month should reflect real uptime windows.

Result interpretation

  • If memory cost dominates, right-size memory per task or adjust task count.
  • If vCPU cost dominates, check CPU utilization and consider lower vCPU per task.

Common mistakes

  • Using peak task count as the average baseline.
  • Mixing MB and GB for memory inputs.
  • Assuming data transfer or logs are included in compute.

Advanced inputs to capture

  • vCPU and memory per task times running hours is the baseline.
  • Separate always-on services from batch or cron workloads.
  • Include ephemeral storage or platform add-ons if used.
  • Add data transfer and logs as separate line items.

Scenario planning

Scenario Tasks vCPU Memory
Baseline Average Configured Configured
Peak High Configured Configured

Validate after changes

  • Compare vCPU-hours and GB-hours in billing to your estimate.
  • Check ECS service metrics for average running tasks.

Next steps

Guides All calculators Guide: Fargate pricing (what to include) Guide: Lambda vs Fargate cost Guide: Fargate vs EKS cost Lambda vs Fargate cost (compare)
Advertisement

Example scenario

  • 3 tasks running 24h/day for 30.4 days at 0.5 vCPU and 1 GB each - estimate vCPU-hours + GB-hours charges.
  • For autoscaling services, use average running tasks, not peak.
  • Peak 220% scenario models scaling bursts during launches.

Included

  • vCPU-hour and memory GB-hour compute charges (modeled with your $/unit inputs).
  • A simple steady-state model for average running tasks over a month.
  • Baseline vs peak scenario table for autoscaling spikes.

Not included

  • Load balancers, data transfer/egress, NAT, and private link costs (model separately).
  • Logs/metrics ingestion and retention costs (model separately).
  • Tiering, discounts, and rounding rules unless you reflect them in inputs.

How we calculate

  • vCPU-hours = tasks x vCPU per task x (hours/day x days/month).
  • GB-hours = tasks x memory (GB) per task x (hours/day x days/month).
  • Hours/month = hours/day x days/month.
  • Total = (vCPU-hours x $/vCPU-hour) + (GB-hours x $/GB-hour).

FAQ

What should I use for days per month?
A common planning value is 30.4 days/month for 24/7 services. If you need a specific billing month, use the actual days.
How do I model autoscaling?
Use average running tasks over the month. If you only know peak tasks, estimate an average (for example, peak x 0.3 to 0.7 depending on traffic shape).
Does this include data transfer and logs?
No. Fargate compute is only part of the bill. For many services, transfer (egress/NAT) and logging can be significant separate line items.

Related tools

Guide: Fargate pricing (what to include) Guide: Lambda vs Fargate cost Guide: Fargate vs EKS cost Lambda vs Fargate cost (compare) Guide: Fargate vs EC2 cost Fargate vs EC2 cost (compare) Lambda cost calculator EKS cost calculator Load balancer cost Data egress cost Log cost

Related guides

S3 pricing: a practical model for storage, requests, egress, and replication
A practical S3 pricing guide: what to include (GB-month, requests, egress, replication) and how to estimate the key inputs without copying price tables.
CDN cost comparison: how to compare pricing across providers
A practical framework to compare CDN pricing across providers: normalize bandwidth, requests, regions, cache fill, and contract terms before choosing the lowest total cost.
Cloud cost estimation checklist: build a model Google (and finance) will trust
A practical checklist to estimate cloud cost without missing major line items: requests, compute, storage, logs/metrics, and network transfer. Includes a worksheet template, validation steps, and the most common double-counting traps.
Copy storage pricing: what you pay for when data moves
A practical guide to pricing storage copy operations (cross-region copy, replication, backups) across S3-like object storage: transfer, requests, and extra storage.
Google Kubernetes Engine (GKE) pricing: nodes, networking, storage, and observability
GKE cost is not just nodes: include node pools, autoscaling, requests/limits (bin packing), load balancing/egress, storage, and logs/metrics. Includes a worked estimate template, pitfalls, and validation steps to keep clusters right-sized.
S3 CRR vs SRR cost: what changes (transfer, storage, requests)
A practical cost comparison of S3 cross-region replication (CRR) vs same-region replication (SRR). Compare transfer/feature fees, extra replica storage, and request costs - with calculators.
Advertisement

Disclaimer

Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.

Last updated: 2026-02-07