Review Fargate CPU and memory allocations
On this page
Review each ECS Fargate task’s requested vCPU, memory, operating system, architecture, configured ephemeral storage, and duration against AWS pricing inputs. Do not treat this review as an observed-utilization analysis.
Why this is worth a look
AWS says Fargate pricing is based on requested vCPU, memory, operating system, CPU architecture, and storage for the task, with duration running from container-image download until termination. AWS also lists supported CPU and memory combinations and says 20 GB of ephemeral storage is available by default, with additional configured ephemeral storage charged separately. These inputs explain core Fargate compute pricing, but a full bill review may also need Region-specific rates, purchase model, duration, and separate charges such as CloudWatch, public IPv4, or data transfer.
Run this check
CHECKLISTManually review one ECS Fargate task or a defined task set in one Region using AWS pricing dimensions, supported configurations, duration rules, and ephemeral-storage treatment.
Scope: one ECS Fargate task or a defined task set in one Region.
Time window: record the task run or review period being assessed; use seconds for duration.
Permissions: no command is required. Use an approved read-only inventory or task record.
[ ] Record requested vCPU and memory.
[ ] Record operating system, CPU architecture, and configured ephemeral storage.
[ ] Confirm the vCPU and memory pair appears in AWS Supported Configurations.
[ ] If configured ephemeral storage exceeds 20 GB, record only the additional configured ephemeral-storage amount as chargeable.
[ ] Record image-download start and task-termination times. Check the one-minute minimum and nearest-second rounding; use the five-minute minimum for Windows containers.
[ ] Record Region and whether Fargate Spot or a Savings Plan applies before comparing with rates.
[ ] Keep CloudWatch, public IPv4, other AWS services, and data transfer as separate possible charges.How to confirm it
- 01
Set the review scope
Choose one ECS Fargate task or a defined task set, one AWS Region, and a stated task-run or billing review period. Record the period in seconds when assessing duration. This checklist does not retrieve account data.
- 02
Record requested inputs
From an approved read-only task record or inventory, write down requested vCPU, memory, operating system, CPU architecture, and configured ephemeral storage. AWS identifies these as Fargate pricing dimensions. If other storage is reviewed, list and price it separately under its applicable AWS service.
- 03
Validate size and ephemeral storage
Compare the vCPU and memory pair with AWS Supported Configurations. Use 20 GB as the included ephemeral-storage amount shown on the AWS page. If configured ephemeral storage is higher than 20 GB, treat only the additional configured ephemeral-storage amount as chargeable.
- 04
Review duration rules
Record when container-image download starts and when the task terminates. Apply per-second pricing rounded up to the nearest second, with a one-minute minimum, or a five-minute minimum for Windows containers.
- 05
Separate other pricing inputs
Before comparing with rates, record the Region and whether Fargate Spot or a Savings Plan applies. Keep CloudWatch, public IPv4, other AWS services, and data transfer separate from the core Fargate resource review.
Before making changes
This is a manual, read-only checklist. It assumes an ECS Fargate task, a defined AWS Region, an approved read-only source for task and run records, and a stated review period. The supplied AWS page supports the pricing dimensions, supported combinations, duration rules, 20 GB ephemeral-storage wording, purchase-model context, and additional-charge examples, but does not define task-record field paths or provide utilization metrics or account cost data. GB follows the page’s wording, which defines GB as 1024^3 bytes.