Which solution will meet these requirements with the LEAST operational overhead?
Use AWS App2Container to containerize the application. Use an AWS CloudFormation template to deploy the application to Amazon Elastic Container Service (Amazon ECS) on AWS Fargate.
Use AWS App2Container to containerize the application. Use an AWS CloudFormation template to deploy the application to Amazon Elastic Container Service (Amazon ECS) on Amazon EC2 instances.
Use AWS App Runner to containerize the application. Use App Runner to deploy the application to Amazon Elastic Container Service (Amazon ECS) on AWS Fargate.
Use AWS App Runner to containerize the application. Use App Runner to deploy the application to Amazon Elastic Kubernetes Service (Amazon EKS) on Amazon EC2 instances.
Explanations:
AWS App2Container helps containerize the application with minimal effort. ECS with AWS Fargate eliminates the need to manage EC2 instances, providing the least operational overhead. CloudWatch metrics allow scaling the containers efficiently based on resource usage, meeting the requirements for scalability and reduced operational maintenance.
Although AWS App2Container and ECS with EC2 instances can work, managing EC2 instances requires more operational overhead compared to Fargate, as the company would need to handle infrastructure management, scaling, and maintenance.
AWS App Runner is a fully managed service, but it does not support the containerization of existing applications through AWS App2Container. App Runner is designed to deploy applications directly from source code or container images without the need for ECS or Kubernetes.
AWS App Runner is not designed to integrate with EKS (Elastic Kubernetes Service). App Runner is meant to deploy applications in a simplified, fully managed environment without the complexity of Kubernetes. It cannot directly deploy to EKS on EC2 instances.