Amazon ECS & AWS Fargate

What are Amazon ECS and AWS Fargate?

Amazon ECS (Elastic Container Service) is AWS’s in-house container orchestration service. It reliably launches containerised applications, distributes them across multiple servers, restarts them in the event of failures and scales them as required. Unlike Kubernetes, ECS is deliberately kept lean and is deeply integrated into AWS – this significantly reduces the learning curve.

AWS Fargate is not a standalone orchestration service, but a computing option for ECS (and EKS). With Fargate, there is no need to manage EC2 servers at all: you simply define how much CPU and memory a container requires, and AWS provides the appropriate capacity. You no longer run worker nodes, do not need to patch operating systems, and only pay for the resources you actually use.

How ECS works

ECS operates on a few clear concepts:

• Task Definition: A description of which container images are to be run with which resources and environment variables.
• Task: A running instance of a task definition.
• Service: Keeps a desired number of tasks running continuously, restarts failed tasks and binds them to a load balancer.
• Cluster: The logical grouping in which tasks and services are executed.

ECS with Fargate or EC2

ECS can source computing capacity in two ways. With the EC2 option, you manage a fleet of servers yourself – this gives you full control and allows for cost-effective Spot Instances. With the Fargate option, AWS takes care of the entire infrastructure. For most medium-sized applications, Fargate is the pragmatic way to get started, as it minimises operational overhead.

Benefits for SMEs

• Low barrier to entry: Significantly fewer concepts than Kubernetes – teams can become productive quickly.
• No server management with Fargate: No operating system updates, no capacity planning at node level.
• Seamless AWS integration: IAM, Load Balancer, CloudWatch and Secrets work together seamlessly without any extra effort.
• Predictable costs: Billed per second of CPU and storage used.

ECS or EKS – which is right for you?

ECS is the right choice if you want to run containerised applications without having to learn Kubernetes, and remain entirely within the AWS ecosystem. EKS is worth considering if you need standards-compliant Kubernetes, a broad ecosystem of tools, or a more vendor-neutral platform. An architecture consultation can clarify this decision early on – switching later involves significant effort.