Which combination of steps should the developer take to deploy the containerized proof-of-concept application with the LEAST operational effort?
(Choose two.)
Package the application into a .zip file by using a command line tool. Upload the package to Amazon S3.
Package the application into a container image by using the Docker CLI. Upload the image to Amazon Elastic Container Registry (Amazon ECR).
Deploy the application to an Amazon EC2 instance by using AWS CodeDeploy.
Deploy the application to Amazon Elastic Kubernetes Service (Amazon EKS) on AWS Fargate.
Deploy the application to Amazon Elastic Container Service (Amazon ECS) on AWS Fargate.
Explanations:
Packaging the application into a .zip file is not suitable for a containerized application, as it does not leverage the benefits of containerization. Container images should be used instead.
Packaging the application into a container image using Docker CLI and uploading it to Amazon ECR is an essential step for deploying containerized applications on AWS. This allows the application to be stored and versioned properly for deployment.
Deploying the application to an EC2 instance using AWS CodeDeploy involves managing the underlying infrastructure, which increases operational effort. The goal is to minimize operational tasks.
While deploying to Amazon EKS on AWS Fargate is a viable option, it typically requires more management and setup compared to ECS on Fargate, which is more straightforward for a proof-of-concept.
Deploying the application to Amazon ECS on AWS Fargate allows for serverless container deployment, minimizing the need to manage infrastructure and reducing operational effort.