An ecommerce company is looking for ways to deploy an application on AWS that satisfies the following requirements:
• Has a simple and automated application deployment process.
• Has minimal deployment costs while ensuring that at least half of the instances are available to receive end-user requests.
• If the application fails, an automated healing mechanism will replace the affected instances.
Which deployment strategy will meet these requirements?
Using AWS CodeDeploy with Auto Scaling and an Elastic Load Balancer meets the requirements for a simple and automated application deployment process. The CodeDeployDefault.HalfAtAtime deployment strategy ensures that at least half of the instances are available to receive end-user requests during deployment. Additionally, enabling an Elastic Load Balancing health check and setting the Auto Scaling health check to ELB ensures that there is an automated healing mechanism to replace affected instances if the application fails.
The keyword is "Has a simple and automated application deployment process." You can't find anything simpler than Beanstalk. Answer: A
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.deploy-existing-version.html#deployments-scenarios how to auto healing ?
A is missing an important aspect of Automatic Healing. Rolling deployments in Elastic Beanstalk if failed are not rollback automatically. hence the answer is C
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rolling-version-deploy.html#environments-cfg-rollingdeployments-method
Correct answer is A.
Should be A, Beanstalk will help to replace failed instance: "If an instance in your environment fails an Amazon EC2 status check, Auto Scaling takes it down and replaces it." https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environmentconfig-autoscaling-healthchecktype.html
It's C: Regarding A - Beanstalk: "Amazon EC2 status checks only cover an instance's health, not the health of your application, server, or any Docker containers running on the instance. If your application crashes, but the instance that it runs on is still healthy, it may be kicked out of the load balancer, but Auto Scaling won't replace it automatically. "
A - Incorrect. EB rolling deployments don't auto rollback C - CodeDeploy deployment configuration can be set to auto rollback
Why not B? https://docs.aws.amazon.com/opsworks/latest/userguide/workinginstances-autohealing.html
This is C
1.)AWS CodeDeploy with Auto Scaling and an Elastic Load Balancer provides a simple and automated application deployment process. 2.)The CodeDeployDefault.HalfAtAtime deployment strategy ensures minimal deployment costs while ensuring that at least half of the instances are available to receive end-user requests. 3.)AWS CodeDeploy provides an automated healing mechanism that can replace the affected instances if the application fails.
It is possible to configure Beanstalk ASG health check for using ELB Elastic Load Balancing health check and monitor the application. From: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environmentconfig-autoscaling-healthchecktype.html "If you want Auto Scaling to replace instances whose application has stopped responding, you can use a configuration file to configure the Auto Scaling group to use Elastic Load Balancing health checks. The following example sets the group to use the load balancer's health checks, in addition to the Amazon EC2 status check, to determine an instance's health"
It'c C. C is not correct: In Beanstalk, in case application is not healthy - instance can still stay: "Amazon EC2 status checks only cover an instance's health, not the health of your application, server, or any Docker containers running on the instance. If your application crashes, but the instance that it runs on is still healthy, it may be kicked out of the load balancer, but Auto Scaling won't replace it automatically. "
Elastic Beanstalk doesn’t have an automated healing mechanism to replace the affected instances. Thus: C.
Considering rolling back i.e healing process .Its C
It's C not A. A. Creating an AWS Elastic Beanstalk environment with Auto Scaling and an Elastic Load Balancer and using rolling deployments with a batch size of 50% does not guarantee that at least half of the instances will be available to receive end-user requests. It is possible that during the deployment process, the application could become partially or completely unavailable.
A is more suitable
Agree with SmileyCloud
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rolling-version-deploy.html#environments-cfg-rollingdeployments-method
Beanstalk fulfills all condition