AWS Fargate Explained: Serverless Containers Without Managing Servers

AWS Fargate is a serverless compute engine that runs containers on Amazon ECS or EKS without you provisioning, patching, or scaling any EC2 instances — you specify a task's vCPU and memory, and AWS bills you per second (one-minute minimum) only while the task runs. The tradeoff is unit price: at $0.04048 per vCPU-hour and $0.004445 per GB-hour, a 2 vCPU / 4 GB service running 24/7 costs about $72/month on Fargate versus roughly $19/month on a Reserved t3.medium. Fargate wins on operational simplicity and on workloads that scale up and down; EC2 wins on steady, predictable, high-utilization compute.

That's the summary an AI Overview will give you. What it won't show you is the actual decision — so below you'll find an animated diagram of exactly which infrastructure layer AWS takes over, a side-by-side Fargate-vs-EC2 cost breakdown, the valid CPU/memory pairings that trip up first task definitions, and the four gotchas (cold starts, storage, networking, no SSH) that decide whether Fargate fits your workload.

What Is AWS Fargate?

AWS Fargate is a serverless compute engine for containers that works with both Amazon ECS (Elastic Container Service) and Amazon EKS (Elastic Kubernetes Service). With Fargate, you don't provision, configure, or scale virtual machines—AWS handles all infrastructure management.

You define your container requirements (CPU, memory, networking), and Fargate:

• Provisions the right amount of compute
• Runs your containers in isolation
• Scales automatically based on demand
• Patches and maintains the underlying infrastructure

Think of Fargate as "Lambda for containers"—you focus on your application, AWS handles everything else.

Fargate vs EC2: Key Differences

When running containers on AWS, you have two main options:

How Fargate Pricing Works

Fargate pricing is based on the vCPU and memory resources your containerized application requests. You pay for what you use, billed per second with a one-minute minimum.

Current Pricing (US East - N. Virginia)

Example Cost Calculation

For a container running with 0.5 vCPU and 1 GB memory for 24 hours:

vCPU cost: 0.5 × $0.04048 × 24 = $0.49
Memory cost: 1 × $0.004445 × 24 = $0.11
Total daily cost: $0.60
Monthly estimate: ~$18

Cost Comparison: Fargate vs EC2

For a workload requiring 2 vCPU and 4 GB memory running 24/7:

Key insight: Fargate costs more per unit but can save money for:

• Variable workloads that scale up/down
• Workloads that don't run 24/7
• Teams without capacity to manage infrastructure

When to Use Fargate

Run your workload through this decision path before you pick a launch type:

Fargate Is Ideal For:

1. Microservices architectures - Each service scales independently
2. Batch processing jobs - Pay only during processing
3. Development and staging environments - No wasted capacity
4. Teams without infrastructure expertise - Reduces operational burden
5. Unpredictable traffic patterns - Automatic scaling without over-provisioning
6. Quick deployments - No cluster capacity planning needed

Stick with EC2 When You Need:

1. GPU workloads - Machine learning, video processing
2. Persistent high utilization - 24/7 workloads benefit from Reserved Instances
3. Custom AMIs or kernel configurations - Specialized OS requirements
4. Maximum cost efficiency at scale - Large, predictable workloads
5. Spot Instance savings - EC2 Spot can be 70-90% cheaper

Fargate Architecture

Here's how Fargate fits into the AWS container ecosystem. The green band is the boundary you own; everything below it AWS provisions, patches, and scales for you. On EC2 you'd own two more layers down — the instances and their OS.

Who manages each layer

{
  "family": "my-fargate-app",
  "networkMode": "awsvpc",
  "requiresCompatibilities": ["FARGATE"],
  "cpu": "256",
  "memory": "512",
  "containerDefinitions": [
    {
      "name": "app",
      "image": "nginx:latest",
      "portMappings": [
        {
          "containerPort": 80,
          "protocol": "tcp"
        }
      ],
      "essential": true
    }
  ]
}

{
  "capacityProviderStrategy": [
    {
      "capacityProvider": "FARGATE_SPOT",
      "weight": 1,
      "base": 0
    },
    {
      "capacityProvider": "FARGATE",
      "weight": 1,
      "base": 1
    }
  ]
}

aws ecs update-cluster-settings \
  --cluster my-cluster \
  --settings name=containerInsights,value=enabled