Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 112 discussion

Less operational overhead means A: Fargate (no EC2), move the containers on ECS, autoscaling for growth and ALB to balance consumption. B - requires configure EC2 C - requires add code (developpers) D - seems like the most complex approach, like re-architecting the app to take advantage of an HPC platform.

And A - its containers so use FarGate, add some auto-scaling...

A makes sense

key = LEAST operational overhead Fargate a serverless service fully managed by aws https://docs.aws.amazon.com/AmazonECS/latest/userguide/what-is-fargate.html#:~:text=AWS%20Fargate%20is,optimize%20cluster%20packing.

Less operational overhead means A: Fargate (no EC2), move the containers on ECS, autoscaling for growth and ALB to balance consumption.

LEAST operational overhead = AWS Fargate

A is the best solution to meet the requirements with the least operational overhead. The key reasons are: AWS Fargate removes the need to provision and manage servers. Fargate will automatically scale the application based on demand. This removes a significant operational burden. Using ECS along with Fargate provides a managed orchestration layer to easily run and scale the containerized application. The Application Load Balancer handles distribution of traffic without additional effort. No code changes are required to move the application to Fargate. The containers can run as-is.

A is the correct answer. AWS Fargate removes the need to provision and manage servers, allowing you to focus on deploying and running applications. Fargate will scale compute capacity up and down automatically based on application load. This removes the operational overhead of managing servers.

Existing: "containerized web-app", "minimum code changes + minimum development effort" --> AWS Fargate + Amazon Elastic Container Services (ECS). Easy question.

A Fargate, ECS, ASG, ALB….What else one will need for a nice sleep?

Option A (AWS Fargate on Amazon ECS with Service Auto Scaling) is the best choice as it provides a serverless and managed environment for your containerized web application. It requires minimal code changes, offers automatic scaling, and utilizes an Application Load Balancer for request distribution. Option B (Amazon EC2 instances with an Application Load Balancer) requires manual management of EC2 instances, resulting in more operational overhead compared to option A. Option C (AWS Lambda with API Gateway) may require significant code changes and restructuring, introducing complexity and potentially increasing development effort. Option D (AWS ParallelCluster) is not suitable for a containerized web application and involves significant setup and configuration overhead.

AWS Fargate is a technology that you can use with Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances. With Fargate, you no longer have to provision, configure, or scale clusters of virtual machines to run containers. This removes the need to choose server types, decide when to scale your clusters, or optimize cluster packing.

Least Operational Overhead = Serverless

AWS Fargate is a technology that you can use with Amazon ECS to run containers without having to manage servers on clusters of Amazon EC2 instances. With Fargate, you no longer have to provision, configure, or scale of virtual machines to run containers. https://docs.aws.amazon.com/AmazonECS/latest/userguide/what-is-fargate.html

A is correct

The best solution to meet the requirements with the least operational overhead is Option A: Use AWS Fargate on Amazon Elastic Container Service (Amazon ECS) to run the containerized web application with Service Auto Scaling. Use an Application Load Balancer to distribute the incoming requests.

Option A has minimum operational overhead and almost no application code changes.