---
title: Amazon Fargate & ECS Task Pricing: vCPU-Seconds, Ephemeral Storage, and Fargate vs EC2 Launch Type (2026)
description: Fargate bills per vCPU-second and GB-second — not per task hour. A 0.25 vCPU / 0.5 GB task running 24/7 costs ~$9/mo in us-east-1; a 4 vCPU / 16 GB task costs ~$145/mo. ECS on EC2 adds cluster overhead but wins at sustained utilization above ~55%.
url: https://www.factualminds.com/blog/amazon-fargate-ecs-task-pricing-2026/
datePublished: 2026-06-17T00:00:00.000Z
dateModified: 2026-06-17T00:00:00.000Z
author: palaniappan-p
category: Cost Optimization & FinOps
tags: aws-fargate, aws-ecs, container-pricing, cost-optimization, finops
---

# Amazon Fargate & ECS Task Pricing: vCPU-Seconds, Ephemeral Storage, and Fargate vs EC2 Launch Type (2026)

> Fargate bills per vCPU-second and GB-second — not per task hour. A 0.25 vCPU / 0.5 GB task running 24/7 costs ~$9/mo in us-east-1; a 4 vCPU / 16 GB task costs ~$145/mo. ECS on EC2 adds cluster overhead but wins at sustained utilization above ~55%.

import PricingHeroStats from '~/components/blog/PricingHeroStats.astro';
import PricingCalculatorCta from '~/components/blog/PricingCalculatorCta.astro';

As of **June 2026**, Fargate prices Linux x86 at **$0.04048/vCPU-hour** and **$0.004445/GB-hour** in us-east-1; Graviton (arm64) runs ~20% lower. ECS itself has no per-task control-plane fee on EC2 launch type — you pay EC2 (or Fargate) plus optional Service Connect, CloudWatch, and data transfer.

<PricingHeroStats
  stats={[
    { value: '$0.04048', label: 'vCPU-hour', note: 'Fargate Linux x86 us-east-1' },
    { value: '$0.004445', label: 'GB-hour', note: 'Task memory' },
    { value: '~55%', label: 'Utilization crossover', note: 'ECS EC2 vs Fargate (typical)' },
    { value: '20 GB', label: 'Free ephemeral', note: 'Per task; then per-GB-hour' },
  ]}
/>

<PricingCalculatorCta blogSlug="amazon-fargate-ecs-task-pricing-2026" />

## Quantified pattern

A **B2B API platform** (~$22k/mo containers, 40 Fargate services) averaged **38% CPU utilization** on rightsized tasks. Moving steady-state services to ECS on EC2 with Spot capacity providers cut container compute **$6,800/mo** (~31%) with two weeks of platform engineering. Bursty webhook workers stayed on Fargate.

## Fargate vs ECS on EC2

| Factor | Fargate | ECS on EC2 |
| ------ | ------- | ------------ |
| Ops burden | Lowest | AMI, patching, scaling |
| Billing unit | vCPU + GB seconds | EC2 instance hours |
| Best fit | Spiky / small teams | Sustained utilization |
| Spot | Fargate Spot (interruptions) | EC2 Spot via capacity providers |

Model all three paths: [Fargate calculator](/tools/aws-fargate-pricing-calculator/), [ECS on EC2 calculator](/tools/aws-ecs-pricing-calculator/), [Fargate vs EC2 calculator](/tools/aws-fargate-vs-ec2-pricing-calculator/).

## If you only do one thing this week

Pull **ECS CPUUtilization** and **MemoryUtilization** for your top five services by cost. Any service under **30% average CPU and memory** for 14 days is a Fargate rightsizing candidate — drop one vCPU or 1 GB and re-measure before changing launch type.

## FAQ

### How is Fargate priced?
Per vCPU-hour and per GB-hour of task memory, billed per second with a 1-minute minimum. Ephemeral storage above 20 GB is charged per GB-hour. OS choice (Linux vs Windows) and architecture (x86 vs arm64/Graviton) change the rate. Regional multipliers apply.

### When is ECS on EC2 cheaper than Fargate?
When average cluster CPU utilization exceeds roughly 50–60% over a month and you can tolerate EC2 operations (AMI patching, capacity providers, Spot blending). Fargate wins for spiky, low-utilization, or ops-light workloads where engineer time to run EC2 exceeds the compute premium.

---

*Source: https://www.factualminds.com/blog/amazon-fargate-ecs-task-pricing-2026/*