ECS vs EKS vs Fargate: Which Container Service Should You Choose?

Key Takeaway

ECS is AWS native, simple and cost-effective. EKS is for when you need the Kubernetes ecosystem. Fargate is for running containers without server management. Small teams/startups should choose ECS, large scale/multi-cloud should choose EKS.

Exam Tip

Exam Essential: "Run containers without server management?" → Fargate. "Kubernetes-based orchestration?" → EKS. "AWS integration important with simple container management?" → ECS.

1. Container Services Overview

Basic Concepts

┌─────────────────────────────────────────────────────────┐
│           AWS Container Service Architecture             │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  Orchestration Layer:                                   │
│  ┌────────────────┐    ┌────────────────┐              │
│  │     ECS        │    │     EKS        │              │
│  │ (AWS Native)   │    │ (Kubernetes)   │              │
│  └───────┬────────┘    └───────┬────────┘              │
│          │                      │                       │
│          └──────────┬───────────┘                       │
│                     │                                   │
│  Compute Layer:     ▼                                   │
│  ┌────────────────┐    ┌────────────────┐              │
│  │     EC2        │    │    Fargate     │              │
│  │ (Self-managed) │    │ (Serverless)   │              │
│  └────────────────┘    └────────────────┘              │
│                                                         │
│  Possible Combinations:                                 │
│  - ECS + EC2      - ECS + Fargate                      │
│  - EKS + EC2      - EKS + Fargate                      │
└─────────────────────────────────────────────────────────┘

Service Roles

Service	Role	Characteristics
ECS	Orchestration	AWS native, simple setup
EKS	Orchestration	Kubernetes-based, open source ecosystem
Fargate	Compute	Serverless, no instance management
EC2	Compute	Self-managed, fine-grained control

2. ECS (Elastic Container Service)

Features

ECS is a container orchestration service developed by AWS.

┌─────────────────────────────────────────────────────────┐
│                   ECS Key Features                       │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  ✅ Advantages                                          │
│  ├── No cluster management cost (EKS is $72/month)     │
│  ├── Deep integration with AWS services (ALB, CW, IAM) │
│  ├── Simple setup, fast deployment                     │
│  ├── Intuitive management in AWS console               │
│  └── Easy configuration with Task Definition           │
│                                                         │
│  ❌ Disadvantages                                       │
│  ├── AWS lock-in                                       │
│  ├── Cannot use Kubernetes ecosystem tools             │
│  └── Limited on-premises/multi-cloud support           │
└─────────────────────────────────────────────────────────┘

ECS Components

ECS Components:
├── Cluster: Logical container grouping
├── Task Definition: Container config (image, CPU, memory)
├── Task: Instance of Task Definition (running container)
├── Service: Configuration to maintain/manage Tasks
└── Container Instance: EC2 where Tasks run (not needed for Fargate)

ECS + EC2 vs ECS + Fargate

Feature	ECS + EC2	ECS + Fargate
Instance Management	Self-managed	AWS managed
Cost	Cheaper (at scale)	Simple but can be expensive
SSH Access	Possible	Not possible
GPU Support	Possible	Limited
Scaling	Requires Auto Scaling config	Automatic

3. EKS (Elastic Kubernetes Service)

Features

EKS is a managed Kubernetes service that leverages the open source ecosystem.

┌─────────────────────────────────────────────────────────┐
│                   EKS Key Features                       │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  ✅ Advantages                                          │
│  ├── Kubernetes standard (multi-cloud portability)     │
│  ├── Rich ecosystem (Helm, Istio, Prometheus, etc.)    │
│  ├── HA control plane (AWS managed)                    │
│  ├── Suitable for complex microservices                │
│  └── Consistency with on-premises Kubernetes           │
│                                                         │
│  ❌ Disadvantages                                       │
│  ├── Cluster management cost: $0.10/hour = $72/month   │
│  ├── Steep learning curve                              │
│  ├── Complex YAML configuration                        │
│  └── High operational overhead                         │
└─────────────────────────────────────────────────────────┘

When to Choose EKS

EKS Selection Criteria:
├── Already have Kubernetes experience/investment
├── Multi-cloud or hybrid cloud strategy
├── Need K8s tools like Istio, ArgoCD, Helm
├── Need consistency with on-premises Kubernetes
└── Large-scale microservices architecture

4. Fargate (Serverless Containers)

Features

Fargate is a compute layer for ECS/EKS that runs containers without server management.

┌─────────────────────────────────────────────────────────┐
│                  How Fargate Works                       │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  [EC2 Mode]                 [Fargate Mode]              │
│  ┌──────────────────┐      ┌──────────────────┐        │
│  │ EC2 Instance     │      │  Task 1  Task 2  │        │
│  │ ┌────┐ ┌────┐  │      │  ┌────┐ ┌────┐  │        │
│  │ │Task│ │Task│  │      │  │    │ │    │  │        │
│  │ │ 1  │ │ 2  │  │      │  │    │ │    │  │        │
│  │ └────┘ └────┘  │      │  └────┘ └────┘  │        │
│  │ OS, patching,  │      │  (All managed    │        │
│  │ capacity       │      │   by AWS)        │        │
│  │ self-managed   │      │                   │        │
│  └──────────────────┘      └──────────────────┘        │
│                                                         │
│  Fargate = Each Task runs in isolated environment       │
│            No instance management needed                │
└─────────────────────────────────────────────────────────┘

Fargate Limitations

Limitation	Description
SSH Access	Not possible (no host access)
Image Caching	Not possible (downloads every time)
GPU	Limited support
DaemonSets	Limited support in EKS only
Privileged Containers	Not possible

5. ECS vs EKS vs Fargate Comparison

Core Comparison Table

Feature	ECS	EKS	Fargate
Type	Orchestration	Orchestration	Compute
Foundation	AWS Native	Kubernetes	Serverless
Cluster Cost	None	$72/month	N/A
Learning Curve	Low	High	Low
AWS Integration	Excellent	Good	Good
Portability	AWS only	High	AWS only
Ecosystem	AWS tools	K8s ecosystem	N/A

Selection Criteria Flowchart

Start
  │
  ├── Do you have Kubernetes experience/requirements?
  │     ├── Yes → EKS
  │     └── No → Next question
  │
  ├── Multi-cloud/hybrid strategy?
  │     ├── Yes → EKS
  │     └── No → Next question
  │
  ├── Don't want to manage servers?
  │     ├── Yes → ECS + Fargate
  │     └── No → Next question
  │
  ├── Is cost the top priority?
  │     ├── Yes → ECS + EC2
  │     └── No → Next question
  │
  └── Small team/startup?
        ├── Yes → ECS + Fargate
        └── No → ECS + EC2 or EKS

Recommended Use Cases by Combination

Combination	Recommended Use Cases
ECS + Fargate	Small scale, startups, quick start, simple workloads
ECS + EC2	Cost-sensitive, large scale, stateful workloads
EKS + Fargate	Need K8s + reduce server management burden
EKS + EC2	Large scale, complex microservices, GPU needed

6. Cost Comparison

Fixed Costs

Item	ECS	EKS
Cluster Management	Free	$0.10/hour = $72/month

Compute Cost Example

Example: 2 vCPU, 4GB memory, 24 hours, Seoul region

EC2 (t3.medium):
= $0.052/hour × 24 hours × 30 days = $37.44/month

Fargate:
= (2 vCPU × $0.04048 + 4GB × $0.004445) × 24 × 30
= ~$70/month

Conclusion: Fargate costs ~1.5-2x more than EC2
However, consider management cost savings

Cost Optimization Strategies

┌─────────────────────────────────────────────────────────┐
│              Container Cost Optimization                 │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  EC2 Mode:                                              │
│  ├── Use Spot Instances (up to 90% savings)            │
│  ├── Reserved Instances / Savings Plans                │
│  └── Maintain optimal capacity with Auto Scaling       │
│                                                         │
│  Fargate Mode:                                          │
│  ├── Fargate Spot (up to 70% savings, interruptible)   │
│  ├── Right-size Task definitions                       │
│  └── Clean up unnecessary Tasks                        │
│                                                         │
│  Common:                                                │
│  ├── Use Graviton2 (ARM) processors                    │
│  └── Optimize container images (minimize size)         │
└─────────────────────────────────────────────────────────┘

7. Practical Perspective

Recommended for Startups/Small Teams

Recommended: ECS + Fargate

Reasons:
- No cluster management cost
- No server management needed
- Quick start, low learning curve
- Intuitive management in AWS console

When scaling:
- Switch Fargate → EC2 (cost savings)
- Or switch ECS → EKS (if needed)

Recommended for Enterprise/Large Scale

Recommended: EKS + EC2 (or hybrid)

Reasons:
- Leverage Kubernetes standard tools
- Prepare for multi-cloud/hybrid
- Manage large-scale microservices
- Fine-grained resource control

Cost optimization:
- Mix Spot Instances + On-Demand
- Auto-scale with Karpenter

Exam Focus Points

Common Question Types

Service Selection
- "Run containers without server management?" → Fargate
- "Kubernetes-based orchestration?" → EKS
- "AWS integration important, simple containers?" → ECS
Cost Related
- "EKS vs ECS cluster management cost?" → Only EKS has $72/month
- "Fargate vs EC2 cost?" → Fargate more expensive but no management burden
Limitations
- "SSH to host in Fargate possible?" → No
- "GPU in Fargate?" → Limited

Exam Tip

Key Memorization:

ECS = AWS native, no cluster management cost
EKS = Kubernetes, cluster $72/month
Fargate = Serverless, no host access
Small scale → ECS + Fargate, Large scale/K8s → EKS

FAQ

Q1: I'm already using Docker Compose, which service is best?

ECS is recommended. AWS Copilot CLI can easily convert Docker Compose files to ECS. If you don't have Kubernetes experience, ECS has a lower learning curve.

Q2: Fargate is more expensive than EC2, why use it?

Consider Total Cost of Ownership (TCO). Fargate saves management costs for server patching, scaling, and monitoring. For small teams, engineer time savings can outweigh infrastructure costs.

Q3: Is migrating from ECS to EKS difficult?

Yes, it's difficult. ECS Task Definitions and Kubernetes Deployments are completely different formats. Container images can be reused, but orchestration configurations must be rewritten.

Q4: When should I use Fargate Spot?

Suitable for interruptible workloads: batch processing, CI/CD builds, data analytics, etc. Not suitable for services that must always run like web servers.

Q5: Can I install Kubernetes directly without EKS?

Possible but not recommended. Control plane management, upgrades, and security patching create significant operational burden. Managed service EKS is more operationally efficient.

Summary

Container service selection summary:

Situation	Recommended Combination
Small scale, quick start	ECS + Fargate
Cost-sensitive, large scale	ECS + EC2
Need Kubernetes	EKS
Serverless + K8s	EKS + Fargate

For exams, remember: "serverless container" → Fargate, "Kubernetes" → EKS, "simple container + AWS integration" → ECS.