zoom_in Click to enlarge

AWS Fargate

▲ ▼

language

description AWS Fargate Overview

Fargate removes the need to provision, configure, or manage EC2 worker nodes for your containers on AWS. You simply define the CPU and memory requirements, and AWS handles the underlying infrastructure provisioning and scaling. It significantly reduces operational complexity compared to managing node groups in EKS, making it a strong choice for teams wanting K8s power without node management headaches.

help AWS Fargate FAQ

Does AWS Fargate replace ECS or EKS?

No. Amazon ECS and Amazon EKS orchestrate containers, while Fargate supplies managed compute on which ECS tasks or EKS pods run.

How is AWS Fargate billed?

AWS bills Fargate according to requested vCPU, memory, operating system, CPU architecture, and additional ephemeral storage. Metering starts while the container image is downloaded and continues until the ECS task or EKS pod terminates, with usage rounded to the nearest second.

Can Fargate containers use persistent storage?

Yes. ECS tasks on Fargate can mount Amazon EFS for persistent shared files, while the task's local ephemeral storage disappears when the task ends.

When is ECS on EC2 a better choice than Fargate?

EC2 can be preferable when workloads need specialized instances, host-level control, predictable high utilization, or aggressive bin-packing to reduce cost. Fargate is strongest when avoiding worker-node management matters more than controlling the underlying machines.

swap_horiz

Looking for AWS Fargate alternatives? Compare top competitors ranked & scored

arrow_forward