# Fargate Resource Rounding and Per-Pod Overhead Driving Step-Up Costs

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/fargate-resource-rounding-and-per-pod-overhead-driving-step-up-costs

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Fargate Resource Rounding and Per-Pod Overhead Driving Step-Up Costs

## Explanation

This inefficiency occurs when pod resource requests-often inflated by sidecar containers-push total memory or CPU just over a Fargate sizing boundary. Because Fargate adds mandatory system overhead and only supports fixed resource combinations, small incremental increases can force a pod into a much larger billing tier. This results in materially higher cost for marginal additional resource needs, especially in workloads that run continuously or at scale.

## Relevant Billing Model

Fargate charges per vCPU-second and GB-second based on the provisioned pod size. EKS on Fargate adds a fixed 256 MB memory overhead per pod and rounds resource requests up to the nearest supported compute configuration.

## Detection

- Review pods whose requested resources sit near known Fargate sizing thresholds

- Assess whether sidecar containers materially increase total requested CPU or memory

- Identify workloads where provisioned capacity significantly exceeds observed workload needs

## Remediation

- Right-size pod resource requests with explicit awareness of Fargate overhead and rounding behavior

- Tune or consolidate sidecar resource requests to avoid unnecessary tier step-ups

- Consider managed node groups for workloads where bin-packing efficiency outweighs Fargate simplicity

## Relevant Documentation

- [https://docs.aws.amazon.com/eks/latest/userguide/fargate-pod-configuration.html](https://docs.aws.amazon.com/eks/latest/userguide/fargate-pod-configuration.html)

- [https://aws.amazon.com/fargate/pricing/](https://aws.amazon.com/fargate/pricing/)

[Submit Feedback](https://hub.pointfive.co/inefficiencies/fargate-resource-rounding-and-per-pod-overhead-driving-step-up-costs)

## At a glance

Reference

CER-0280

Cloud provider

AWS

Service

AWS EKS

Category

[Compute](https://www.pointfive.co/efficiency-hub/service-category/compute)

Inefficiency type

Suboptimal resource sizing

## Contributed by

- Tai Nguyen 

### Tai Nguyen

Senior Site Reliability Engineer @ Spartan

[LinkedIn](https://www.linkedin.com/in/taind772/)

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.