Exam AWS Certified Solutions Architect - Professional topic 1 question 61 discussion

D. - Docker with awslogs E. VM Import/Export + CW logs

D. Create a Dockerfile for the application. Create an AWS Elastic Beanstalk application using the Docker platform and the Dockerfile. Enable logging the Docker configuration to automatically publish the application logs. Enable log file rotation to Amazon S3. E. Use VM import/Export to import a virtual machine image of the server into AWS as an AMI. Create an Amazon Elastic Compute Cloud (EC2) instance from AMI, and install and configure the Amazon CloudWatch Logs agent. Create a new AMI from the instance. Create an AWS Elastic Beanstalk application using the AMI platform and the new AMI.

The correct options are A and D. Option A allows you to create an AWS Elastic Beanstalk application using the custom web server platform. This is a good option if you want to migrate the application without making any changes to the code. You can also enable log file rotation to Amazon S3, which will ensure that the logs are stored in a durable location. Option D allows you to create a Dockerfile for the application and then create an AWS Elastic Beanstalk application using the Docker platform and the Dockerfile. This is a good option if you want to containerize the application. You can also enable logging the Docker configuration to automatically publish the application logs. This will ensure that the logs are published to Amazon S3, which is a durable location.

now , beanstalk does not work with AMI as Custom Platform.. the Useless discussion..

D & E I believe. I rule out A because you dont have a custom web server platform with Beanstalk. You can use an EC2 for the custom web platform however.

DE. A falls of because there’s a custom platform for AWS Elastic Beanstalk but it works based on an AMI and not on an executable. This is what you do in E.

Docker with awslogs to S3 . Since ELB Cloudwatch agents doesnt send logs directly to S3, it is not A but E

BE A. It sounds substantially wrong. There's no "custom web server platform" only "custom platform". And if that's the case the one doesn't have to specify a web server executable anywhere. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/custom-platforms.html B. That's completely feasible. https://aws.amazon.com/blogs/devops/running-docker-on-aws-opsworks/ C. Wrong. There's no such thing as "Docker layer". A custom layer is required. https://docs.aws.amazon.com/opsworks/latest/userguide/workinglayers.html D. Wrong. The one is only able to request logs from EB instances. On an instance the logs appear via docker volumes. There are no mentions of any sctipts for sending logs anywhere which has to be embedded into custom ami for EB env. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker.container.console.html#docker-env-cfg.dc-customized-logging E. That's ancually feasible. A custom image is fairly common pattern. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.customenv.html

B & D is best

There is nothing here that indicates that we need to containerize this application. It is BeSpoke so it is customized. so E for sure and A. I am opting for A and E

B & E https://aws.amazon.com/blogs/devops/running-docker-on-aws-opsworks/ https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.customenv.html

D. Create a Dockerfile for the application. Create an AWS Elastic Beanstalk application using the Docker platform and the Dockerfile. Enable logging the Docker configuration to automatically publish the application logs. Enable log file rotation to Amazon S3. E. Use VM import/Export to import a virtual machine image of the server into AWS as an AMI. Create an Amazon Elastic Compute Cloud (EC2) instance from AMI, and install and configure the Amazon CloudWatch Logs agent. Create a new AMI from the instance. Create an AWS Elastic Beanstalk application using the AMI platform and the new AMI.

A, D. A : The question mentions it uses a specific webserver of bespoke, and A mentions creating the customized platform. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/custom-platforms.html Why E is incorrect : Because `Elastic Beanstalk installs a CloudWatch log agent with the default configuration settings on each instance it creates` : https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/AWSHowTo.cloudwatchlogs.html Cloudwatch logs agent is already there, you don't need to do that complex steps to install it.

BE D - Wrong, logs are not in S3

A, D and E are correct. A & E - https://aws.amazon.com/about-aws/whats-new/2017/02/aws-elastic-beanstalk-supports-custom-platforms/ D- Docker platform runs natively on Linux. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/docker-basics.html https://acloud.guru/forums/aws-certified-solutions-architect-professional/discussion/-KHL5b624o_6PR_KAW30/sample-question- CloudWatch Logs will store your log data indefinitely. S3 is equally durable. Going with A & E since they allow "custom platform" comparing to D which offers "Docker platform".

DE Correct

A and D because S3 is the durable location that the question hints.