Fargate Is Not Firecracker (2024)
During my time working on the EKS team at AWS, I witnessed one of the most persistent misunderstandings surrounding AWS Fargate. Customers frequently asked about Fargate's underlying technology, often citing Firecracker's role in its operation. However, the reality was far from the marketing claims.
Fargate does not utilize Firecracker to create "microVMs" for containers. While the documentation and blog posts frequently state that Firecracker was developed to enhance user experiences for services like AWS Lambda and Fargate, the truth is that Fargate has moved away from Docker and now employs containerd. Despite this shift, Fargate can still leverage a VM-based runtime for containers by simply switching containerd's runtime plugin to firecracker-containerd instead of runC.
The truth, however, is that switching to Firecracker is anything but simple at Amazon's scale. The operational burden is merely shifted to other areas, such as handling EBS volumes or GPUs and integrating with sidecars. Customers often believe that Fargate is a magical solution, but in reality, AWS builds on AWS with only rare instances of behind-the-scenes special sauce. It's essential to be aware of the true nature of Fargate and the heavy lifting that still falls on users.
Written by urgent.news from Lobsters's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.