A company is designing a new microservices architecture on AWS. Each service must be independently deployable and scale based on demand. The company wants to minimize operational overhead for container orchestration. Which AWS service should the company use?
ECS with Fargate is serverless and reduces operational overhead for container orchestration.
Why this answer
Amazon ECS with AWS Fargate is the correct choice because it provides a fully managed container orchestration service that eliminates the need to provision, configure, or scale underlying EC2 instances. Fargate runs each container in its own isolated compute environment, allowing each microservice to scale independently based on demand while minimizing operational overhead for cluster management.
Exam trap
The trap here is that candidates often choose Amazon EKS assuming Kubernetes is the only modern orchestration tool, but the question specifically asks for minimal operational overhead, and Fargate's serverless model removes the need to manage any cluster infrastructure, which EKS does not fully eliminate even with managed node groups.
How to eliminate wrong answers
Option A is wrong because Amazon EKS requires you to manage the Kubernetes control plane (or pay for it) and typically involves managing worker nodes or using managed node groups, which adds operational overhead compared to Fargate's serverless model. Option B is wrong because Amazon EC2 with Auto Scaling requires you to manage the underlying instances, including patching, scaling policies, and container orchestration software, which contradicts the goal of minimizing operational overhead. Option D is wrong because AWS Lambda is designed for short-running, event-driven functions with a maximum execution timeout of 15 minutes and limited runtime environments, making it unsuitable for long-running microservices that require container-level isolation and persistent connections.