How AWS Fargate Is Redefining Cloud‑Native Container Deployment

Changing the calculus of containers in the cloud

Two years ago the author wrote about the inner workings of Amazon ECS; at the recent re:Invent conference AWS launched Fargate, a service that fundamentally changes the container landscape.

Innovation often comes from combining existing concepts with new approaches. The rapid adoption of containers over the past four years is the result of blending the old technology of containers with the new Docker toolchain and the cloud.

Containers solve code‑portability problems and enable immutable deployment units, but they also add an extra layer between code and runtime. Managing large clusters, scheduling, and state stores feels at odds with the cloud’s pay‑as‑you‑go premise.

AWS Fargate’s vision is to let developers write code and run it without configuring complex management tools. With Fargate you do not stand up a control plane, choose instance types, or configure networking, scaling, service discovery, load balancing, security groups, permissions, or secrets. You simply build a container image, define how and where it runs, and pay only for the resources you consume.

Fargate integrates natively with Amazon VPC, Auto Scaling, Elastic Load Balancing, IAM roles, and Secrets Management. AWS has made it production‑ready with a 99.99 % SLA and compliance with PCI, SOC, ISO and HIPAA.

Resource provisioning is fine‑grained: you select exactly the CPU and memory your code needs, and you are billed per container. Although the per‑MiB price may appear higher than traditional VMs, the total cost of running an application is often lower because you only pay for what you use, and developers save significant time on operational tasks.

The emergence of container‑orchestration ecosystems was driven by the lack of a native way to run containers in the cloud. With Fargate, orchestration becomes unnecessary; the only thing you manage is the application itself, making containers truly cloud‑native.

The next wave of innovation will focus on application and service management: inter‑connecting independent services, ensuring visibility, handling traffic patterns, securing multi‑service deployments, service discovery, and defining access to shared data stores. The author looks forward to the evolution of the container ecosystem that gives developers more control with less effort.

AWS Fargate integrates seamlessly with Amazon ECS; you define your application as you would for ECS, package it into task definitions, specify CPU, memory, networking, and IAM policies, and Fargate launches and manages the containers. Support for Amazon EKS (Elastic Kubernetes Service) is slated for later in 2018.