Originally published on DevToolHub.
ECS vs EKS comparisons usually stop at "ECS is simpler, EKS is more portable." That's true, but it skips the number that actually shows up on your AWS bill. ECS charges nothing to run the control plane. EKS charges $0.10 per cluster-hour for the first 14 months a Kubernetes version is supported, then $0.60 per cluster-hour once that version moves into extended support — a jump from roughly $73 a month to about $438 a month for a single cluster.
The Control Plane Price Everyone Skips
ECS has no separate control-plane charge. AWS runs the scheduler, API, and task placement logic for free — you only pay for the EC2 or Fargate compute actually running your containers.
EKS is different. Per AWS's own EKS pricing page, every cluster costs $0.10 per hour for standard support, covering a Kubernetes version for 14 months after release. Miss that window, and the same cluster jumps to $0.60 per hour under extended support for up to 12 more months. $0.10/hour is about $73/month. $0.60/hour is about $438/month — a 6x jump for leaving a cluster on an older version.
| ECS | EKS | |
|---|---|---|
| Control plane | Free | $0.10/hour (standard support) |
| After 14 months, unpatched | N/A | $0.60/hour (extended support) |
| Approx. monthly control-plane cost | $0 | $73 → $438 |
| Compute | EC2 or Fargate, billed normally | EC2 or Fargate, billed normally |
Why the Extended Support Jump Catches Teams Off Guard
It's not hidden — it's right on AWS's pricing page. What catches teams off guard is that it's a per-cluster charge tied to the Kubernetes version, not your application code. A cluster that sits forgotten for a year and a half is exactly the kind of cost that shows up as a surprise line item in a FinOps review.
Where ECS's Simplicity Argument Actually Holds
ECS wins on cost and simplicity when your workload doesn't need Kubernetes-specific tooling. No control plane fee, no version-lifecycle clock, and task definitions are a smaller surface than Kubernetes manifests and CRDs.
That has a limit. ECS's model is AWS-specific. Need to run the same workload elsewhere, or through Helm charts and ArgoCD? None of that transfers.
Where EKS's Cost Actually Pays for Itself
EKS's fee buys the entire Kubernetes ecosystem — the same manifests, Helm charts, and GitOps tooling that work on GKE, AKS, or bare metal. If your team already runs Kubernetes anywhere else, that portability is worth more than $73 a month.
EKS also supports Fargate, same as ECS, so "EKS forces node management" doesn't hold up anymore.
The Actual Decision Criteria
Pick ECS if you're AWS-only with no existing Kubernetes investment. Pick EKS if you need multi-cloud portability, or your team's tooling is already built around Kubernetes primitives.
If you pick EKS, put the version upgrade on a real calendar — cheap to handle on schedule, expensive to ignore.
Quick Summary:
- ECS has no control-plane fee; EKS charges $0.10/cluster-hour standard, $0.60/cluster-hour extended support
- The extended-support jump (~$73/mo → ~$438/mo) hits clusters running Kubernetes versions older than 14 months
- ECS wins on simplicity and cost for AWS-only workloads
- EKS's fee buys real portability across any Kubernetes environment
- Both support Fargate — "EKS means managing nodes" isn't a real argument anymore
Top comments (0)