Exam AWS Certified Developer Associate topic 1 question 12 discussion

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/docker.html#single-container-docker.deploy-remote Deploy a remote Docker image to Elastic Beanstalk After testing your container locally, deploy it to an Elastic Beanstalk environment. Elastic Beanstalk uses the docker-compose.yml file to pull and run your image if you are using Docker Compose. Otherwise, Elastic Beanstalk uses the Dockerrun.aws.json instead. Use the EB CLI to create an environment and deploy your image. ~/remote-docker$ eb create environment-name

A) Eliminated - This option is not efficient because the Docker image is already pre-built and available in a public registry. Elastic Beanstalk does not need to rebuild the image; it can pull the image directly.

This case we need to zip image and upload it to aws beanstalk

answer B.Docker environment with Docker Compose This section describes how to prepare your Docker image and container for deployment to Elastic Beanstalk. Any web application that you deploy to Elastic Beanstalk in a Docker environment must include a docker-compose.yml file if you also use the Docker Compose tool. You can deploy your web application as a containerized service to Elastic Beanstalk by doing one of the following actions: Create a docker-compose.yml file to deploy a Docker image from a hosted repository to Elastic Beanstalk.

I think option A is correct.My reason - .yml is added for confusion. Because in cicd the prosses follows - CodeCommit then code build and then code deploy by elasticbeanstalk.Elastic Beanstalk supports the deployment of web applications from Docker containers

Elastic Beanstalk supports deploying Docker containers directly. You should create a Dockerfile that defines the application's container, and then Elastic Beanstalk will use this Dockerfile to build the Docker image and deploy it to the environment. Option B mentions using docker-compose.yml, but Elastic Beanstalk typically deploys single Docker containers, so docker-compose is not necessary in this context.

I think so A ,Elastic Beanstalk supports deploying Docker containers directly. You should create a Dockerfile that defines the application's container, and then Elastic Beanstalk will use this Dockerfile to build the Docker image and deploy it to the environment. Option B mentions using docker-compose.yml, but Elastic Beanstalk typically deploys single Docker containers, so docker-compose is not necessary in this context.

B, chatGTP 4 said it is B. and it says that docker-compose.yml can be used to define and run multi-container Docker applications, but it can also be used for single-container applications.

The question explicitly states that the Docker image is already built before you get your hands on it. You only need to configure EB to load and deploy the existing image.

As the question clearly states, though CI/CD build is completed and image is pushed to artifactory. SO if image already available, then we can just refer the image in docker-compose.yaml and deploy via EB CLI.

ChatGPT says its A

I have a doubt but I would say B (I didn't put the voting comment because I am not sure about that)

A. Create a Dockerfile. Configure Elastic Beanstalk to build the application as a Docker image. Option B is incorrect because using docker-compose.yml file is not recommended for Elastic Beanstalk deployments. Elastic Beanstalk supports Dockerfiles to define the application's dependencies and configuration.

AWS Elastic Beanstalk can launch Docker environments by building an image described in a Dockerfile or pulling a remote Docker image. If you're deploying a remote Docker image, you don't need to include a Dockerfile. Instead, if you are also using Docker Compose, use a docker-compose.yml file, which specifies an image to use and additional configuration options. If you are not using Docker Compose with your Docker environments, use a Dockerrun.aws.json file instead.

The question did not specify whether Docker Compose is being used, so both A and B could be correct depending on whether Docker Compose is being used or not. If Docker Compose is used, then answer option B is the correct approach for deploying a single Docker image to Elastic Beanstalk.

I vote for B from this document, https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/GettingStarted.DeployApp.html " If you're deploying a remote Docker image, you don't need to include a Dockerfile. Instead, if you are also using Docker Compose, use a docker-compose.yml file, which specifies an image to use and additional configuration options. If you are not using Docker Compose with your Docker environments, use a Dockerrun.aws.json file instead. " The image is on the remote registry, does not make sense to build again locally using dockerfile.

It's A Stephane Maarek lectures: Elastic Beanstalk – Single Docker • Run your application as a single docker container • Either provide: • Dockerfile: Elastic Beanstalk will build and run the Docker container • Dockerrun.aws.json (v1): Describe where *already built* Docker image is • Image • Ports • Volumes • Logging • Etc... • Beanstalk in Single Docker Container does not use ECS