# AWS Fargate pricing calculator

Free, in your browser · Prices checked 17 November 2026, us-east-1

## Fargate pricing calculator

### Show the formula

```
Per task-hour = vCPU × price per vCPU-hour + GB × price per GB-hour
              (+ vCPU × Windows licence fee) (+ storage GB above 20 × storage price)
Monthly cost  = task-hours × per task-hour
```

Prices checked 17 November 2026, us-east-1, on-demand, in US dollars. Other regions differ. Always on means 730 hours a month, as in the AWS Pricing Calculator. Everything is calculated in your browser.

Screenshot: Cost by resource: estimated monthly total and resources ranked by cost

In the CloudConsole app

## Run this on your own account

For services already running, the app’s monthly cost card on an ECS service on Fargate multiplies its task size by the tasks running now, at your region’s price, and Cost by resource ranks it with your instances, databases and NAT gateways.

[How Cost by resource works →](https://cloudconsole.dev/app-tools/aws-cost-per-resource)

[Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710) · [Get it on Google Play](https://play.google.com/store/apps/details?id=com.cloudconsole.app)

**Short answer**

Fargate bills the vCPU and memory a task requests, per second with a 1-minute minimum: $0.04048 per vCPU-hour and $0.004445 per GB-hour for Linux/x86 in us-east-1, about 20% less on Arm. A task with 1 vCPU and 2 GB costs $0.04937 an hour, or about $36.04 a month if it runs all the time. Windows adds a licence fee and has a 5-minute minimum; ephemeral storage above 20 GB costs extra.

## How AWS Fargate pricing works

Fargate charges for what each ECS task (or EKS Pod) *requests*, not what it uses: the task’s vCPU and memory, its operating system and CPU architecture, and any ephemeral storage above the 20 GB every task gets. Billing runs from when the task starts pulling its container image until it stops, rounded up to the nearest second.

```
cost per task-hour = vCPU × price per vCPU-hour
                   + memory (GB) × price per GB-hour
                   + vCPU × Windows licence fee        (Windows only)
                   + (ephemeral storage GB − 20) × $0.000111
monthly cost       = cost per task-hour × task-hours a month
```

A task that runs for less than the minimum is billed for the minimum: **1 minute on Linux, 5 minutes on Windows**. That matters for short scheduled jobs. A Linux job that runs for 20 seconds every minute is billed as if it ran all the time, and a 2-minute Windows job costs as much as a 5-minute one.

Because the bill follows the task size, the cheapest setting is the smallest size your containers fit in. CloudWatch’s CPUUtilization and MemoryUtilization show how much of each task is used; a service that sits at 10% CPU on 4 vCPU pays for more than 3 vCPU it doesn’t use.

## Fargate prices in us-east-1

Prices checked 17 November 2026 for US East (N. Virginia), on-demand, from the AWS Price List and the Fargate pricing page. AWS counts a GB as 1024³ bytes.

| Charge | Linux/x86 | Linux/Arm | Windows/x86 |
|---|---|---|---|
| Per vCPU-hour | $0.04048 | $0.03238 | $0.046552 |
| Per GB-hour of memory | $0.004445 | $0.00356 | $0.00511175 |
| Windows OS licence, per vCPU-hour | — | — | $0.046 |
| Ephemeral storage above 20 GB, per GB-hour | $0.000111 | $0.000111 | $0.000111 |
| Minimum charge per task | 1 minute | 1 minute | 5 minutes |

### Monthly cost of common task sizes

One task running all month (730 hours), with the included 20 GB of storage:

| Task size | Linux/x86 | Linux/Arm | Windows/x86 |
|---|---|---|---|
| 0.25 vCPU, 0.5 GB | $9.01 | $7.21 | — |
| 0.25 vCPU, 1 GB | $10.63 | $8.51 | — |
| 0.5 vCPU, 1 GB | $18.02 | $14.42 | — |
| 1 vCPU, 2 GB | $36.04 | $28.84 | $75.03 |
| 1 vCPU, 4 GB | $42.53 | $34.03 | $82.49 |
| 2 vCPU, 4 GB | $72.08 | $57.67 | $150.05 |
| 2 vCPU, 8 GB | $85.06 | $68.07 | $164.98 |
| 4 vCPU, 8 GB | $144.16 | $115.34 | $300.10 |
| 4 vCPU, 16 GB | $170.12 | $136.13 | $329.96 |
| 8 vCPU, 16 GB | $288.32 | $230.68 | — |
| 16 vCPU, 32 GB | $576.64 | $461.36 | — |

## Valid Fargate CPU and memory combinations

Fargate only runs the task sizes below. The calculator snaps to them: pick a vCPU value and the memory list shows what that size allows. CPU is also written in CPU units in task definitions (1 vCPU = 1024).

| vCPU (CPU units) | Memory | Operating systems |
|---|---|---|
| 0.25 vCPU (256) | 0.5, 1 or 2 GB | Linux |
| 0.5 vCPU (512) | 1, 2, 3 or 4 GB | Linux |
| 1 vCPU (1024) | 2–8 GB in 1 GB steps | Linux, Windows |
| 2 vCPU (2048) | 4–16 GB in 1 GB steps | Linux, Windows |
| 4 vCPU (4096) | 8–30 GB in 1 GB steps | Linux, Windows |
| 8 vCPU (8192) | 16–60 GB in 4 GB steps | Linux |
| 16 vCPU (16384) | 32–120 GB in 8 GB steps | Linux |
| 32 vCPU (32768) | 60, 120 or 244 GB | Linux |

8, 16 and 32 vCPU need Linux platform version 1.4.0 or later. Windows tasks need at least 1 vCPU and run on x86 only. Ephemeral storage can be raised from the default 20 GB to 200 GB per task.

## ECS or EKS, Arm, Spot and Savings Plans

- **EKS on Fargate.** AWS’s Fargate pricing page prices EKS Pods with the same vCPU and memory rates as ECS tasks. Each Pod is rounded up to the nearest size in the table above after adding 256 MB for Kubernetes components, so a Pod that requests 1 vCPU and 8 GB runs, and is billed, as 2 vCPU and 9 GB. Windows and Arm are only available on ECS.
- **Arm (Graviton).** About 20% cheaper than x86 for both vCPU and memory. Images need an arm64 (or multi-arch) build.
- **Fargate Spot.** Interruptible capacity for ECS tasks on Linux at up to 70% off. Its price moves with supply and demand and isn’t in the AWS Price List file, so the calculator doesn’t include it.
- **Compute Savings Plans.** Up to 50% off Fargate in exchange for a one- or three-year spend commitment. Not modelled here.

## What else a Fargate workload costs

The calculator covers Fargate’s own charges. A real bill for a container service usually has more lines:

- **Load balancers.** An Application Load Balancer in front of a service bills per hour and per LCU.
- **NAT gateways and data transfer.** Tasks in private subnets pull images and call the internet through a NAT gateway, billed per hour and per GB, unless VPC endpoints are used. Traffic out to the internet costs extra.
- **Public IPv4 addresses.** Tasks with a public IP address pay the VPC public IPv4 charge.
- **CloudWatch Logs.** Everything containers write to the awslogs driver is ingested and stored.
- **Amazon ECR.** Image storage, and data transfer for pulls from outside the region.

To see what you actually spend, group Cost Explorer by service and then by usage type; the [AWS cost breakdown guide](https://cloudconsole.dev/how-to/see-aws-cost-breakdown) shows how, and the [AWS guides](https://cloudconsole.dev/guides/) cover the rest of the bill.

**Fargate or Lambda?** There’s no like-for-like figure here: Lambda bills per request and per GB-second of each invocation, with CPU tied to memory, so the same work costs depend on traffic, not on a task size. Use the [Lambda cost calculator](https://cloudconsole.dev/tools/lambda-cost-calculator) with your request rate and duration to compare.

## Questions

### How is AWS Fargate priced?

Fargate charges for the vCPU and memory a task requests, per second, from the moment it starts pulling the container image until the task stops, with a 1-minute minimum on Linux. In us-east-1 Linux/x86 costs $0.04048 per vCPU-hour and $0.004445 per GB-hour. Windows adds an OS licence fee per vCPU-hour and has a 5-minute minimum.

### How much does a Fargate task cost per month?

A task with 1 vCPU and 2 GB running all month (730 hours) costs about $36.04 on Linux/x86, $28.84 on Linux/Arm and $75.03 on Windows in us-east-1. The smallest task, 0.25 vCPU and 0.5 GB, costs about $9.01 a month on Linux/x86.

### Is Fargate cheaper on Arm (Graviton)?

Yes, by about 20%: Linux/Arm is $0.03238 per vCPU-hour and $0.00356 per GB-hour in us-east-1, against $0.04048 and $0.004445 on Linux/x86. Your container images need an arm64 build, and Windows tasks can only use x86.

### Does EKS on Fargate cost the same as ECS on Fargate?

AWS’s Fargate pricing page uses the same vCPU and memory prices for EKS Pods as for ECS tasks, and its EKS example uses the Linux/x86 rates. On EKS each Pod is rounded up to the nearest Fargate size, with 256 MB added for Kubernetes components, and Windows and Arm are only available on ECS.

### What about Fargate Spot?

Fargate Spot runs interruptible ECS tasks on Linux at up to 70% off, but its price changes over time and isn’t in the AWS Price List file this calculator uses, so it isn’t modelled. Check the current Spot price on the AWS Fargate pricing page.

### What does the Fargate pricing calculator leave out?

Data transfer, load balancers, NAT gateways, public IPv4 addresses, CloudWatch Logs, Amazon ECR image storage, Fargate Spot and Compute Savings Plans. It prices only Fargate’s own vCPU, memory, Windows licence and ephemeral storage charges.

**See what your containers cost**

CloudConsole shows your spend by service, with usage types and regions, next to your ECS clusters, services and tasks, so a service that suddenly costs more stands out. On iPhone and Android.

[About the app →](https://cloudconsole.dev/aws-console-app)

## Sources

- [AWS Fargate pricing](https://aws.amazon.com/fargate/pricing/)
- [AWS Price List: Amazon ECS (Fargate), us-east-1](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonECS/current/us-east-1/index.json)
- [Amazon ECS task definition differences for Fargate (task CPU and memory)](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-tasks-services.html)
- [Fargate task ephemeral storage for Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-task-storage.html)
- [Understand Fargate Pod configuration details (EKS)](https://docs.aws.amazon.com/eks/latest/userguide/fargate-pod-configuration.html)
- [Amazon ECS clusters for Fargate (Fargate Spot)](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-capacity-providers.html)

## Related

- [AWS Lambda cost calculator](https://cloudconsole.dev/tools/lambda-cost-calculator) – Free tools
- [How to scale an ECS service](https://cloudconsole.dev/how-to/scale-ecs-service) – How-to guides
- [OutOfMemoryError: Container killed due to memory usage](https://cloudconsole.dev/errors/ecs-outofmemoryerror) – AWS error fixes
- [CloudWatch alarm for Amazon ECS service CPUUtilization](https://cloudconsole.dev/alarms/ecs-cpuutilization) – CloudWatch alarms
- [Why is my AWS bill so high?](https://cloudconsole.dev/how-to/why-is-my-aws-bill-so-high) – How-to guides
- [How to see an AWS cost breakdown](https://cloudconsole.dev/how-to/see-aws-cost-breakdown) – How-to guides

---

Source: https://cloudconsole.dev/tools/fargate-pricing-calculator

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
