How should the solutions architect gain access to an EC2 instance to troubleshoot the issue?
Suspend the Auto Scaling group’s HealthCheck scaling process. Use Session Manager to log in to an instance that is marked as unhealthy.
Enable EC2 instance termination protection. Use Session Manager to log in to an instance that is marked as unhealthy.
Set the termination policy to OldestInstance on the Auto Scaling group. Use Session Manager to log in to an instance that is marked an unhealthy.
Suspend the Auto Scaling group’s Terminate process. Use Session Manager to log in to an instance that is marked as unhealthy.
Explanations:
Suspending the HealthCheck scaling process would prevent the Auto Scaling group from detecting unhealthy instances, but it does not directly address the need to troubleshoot the unhealthy instance. Session Manager can still be used to access the instance, but suspending health checks may lead to further issues.
Enabling termination protection prevents an instance from being terminated, but it does not help in accessing or troubleshooting the instance. Additionally, it does not address the issue of unhealthy instances being terminated.
Changing the termination policy to OldestInstance does not affect the access to the unhealthy instance, nor does it help with troubleshooting. It only determines which instances get terminated, but it doesn’t provide a means to log in to the instance.
Suspending the Terminate process allows the instance to remain operational while the solutions architect logs in via Session Manager. This provides the opportunity to troubleshoot the instance without it being au
I estimate that the answer is:
Suspend the Auto Scaling group’s Terminate process. Use Session Manager to log in to an instance that is marked as unhealthy.
I plot that the answer is:
Suspend the Auto Scaling group’s Terminate process. Use Session Manager to log in to an instance that is marked as unhealthy.