A company is running an application on Amazon EC2 instances behind an ELB Application Load Balancer. The instances run in an EC2 Auto Scaling group across multiple Availability Zones.
After a recent application update, users are getting HTTP 502 Bad Gateway errors from the application URL. The DevOps Engineer cannot analyze the problem because Auto Scaling is terminating all EC2 instances shortly after launch for being unhealthy.
What steps will allow the DevOps Engineer access to one of the unhealthy instances to troubleshoot the deployed application?
A. Create an image from the terminated instance and create a new instance from that image. The Application team can then log into the new instance.
B. As soon as a new instance is created by AutoScaling, put the instance into a Standbystate as this will prevent the instance from being terminated.
C. Add a lifecycle hook to your Auto Scaling group to move instances in the Terminatingstate to the Terminating:Waitstate.
D. Edit the Auto Scaling group to enable termination protection as this will protect unhealthy instances from being terminated.
After a recent application update, users are getting HTTP 502 Bad Gateway errors from the application URL. The DevOps Engineer cannot analyze the problem because Auto Scaling is terminating all EC2 instances shortly after launch for being unhealthy.
What steps will allow the DevOps Engineer access to one of the unhealthy instances to troubleshoot the deployed application?
A. Create an image from the terminated instance and create a new instance from that image. The Application team can then log into the new instance.
B. As soon as a new instance is created by AutoScaling, put the instance into a Standbystate as this will prevent the instance from being terminated.
C. Add a lifecycle hook to your Auto Scaling group to move instances in the Terminatingstate to the Terminating:Waitstate.
D. Edit the Auto Scaling group to enable termination protection as this will protect unhealthy instances from being terminated.