AWS Fargate: Serverless Container Compute for ECS and EKS
What Fargate manages, how task-level isolation and resource sizing work, and when its operational simplicity outweighs reduced host control.
AWS Fargate is a compute engine for containers used by Amazon ECS and Amazon EKS. It is not a separate orchestrator: ECS services/tasks or Kubernetes pods still express desired work, while Fargate supplies isolated compute without exposing an EC2 fleet for the customer to patch or scale.
The unit of capacity changes
With EC2-backed containers, teams buy instances and then pack workloads onto them. With Fargate, they request supported CPU, memory, ephemeral storage, platform, and architecture combinations per task or pod. This removes host bin-packing and idle-node management, but poor requests can still waste money or cause throttling and out-of-memory failures. Measure real workload demand before standardizing sizes.
Security and networking
Fargate tasks use awsvpc networking and receive their own network identity. Security groups, private subnets, VPC endpoints, and least-privilege task roles remain customer responsibilities. The isolation boundary is stronger than placing unrelated containers on one customer-managed host, yet application vulnerabilities, permissive IAM, exposed listeners, and compromised images remain fully relevant.
Operations and observability
There is no host to SSH into. Diagnostics therefore depend on container logs, ECS or Kubernetes events, metrics, distributed traces, and optional runtime debugging mechanisms. Images must start cleanly, handle termination signals, expose meaningful health checks, and externalize persistent state. Platform-version changes and supported feature matrices should be reviewed before relying on a kernel capability or storage behavior.
When to choose it
Fargate works well for variable services, scheduled tasks, and teams that do not need privileged containers, host networking, custom kernel modules, or specialized instance tuning. Stable, large fleets can be cheaper or more flexible on carefully managed EC2 capacity, especially with reservations or Spot. Compare the complete operating cost and risk, not only compute price.
Sources: AWS Fargate for Amazon ECS, Amazon ECS Fargate getting started