Debugging AWS Autoscaling Group Issues

Correct Answer: C.

The AWS Documentation mentions the following.

You can suspend and then resume one or more of the scaling processes for your Auto Scaling group.

This can be useful when you want to investigate a configuration problem or other issue with your web application and then make changes to your application without invoking the scaling processes.

Amazon EC2 Auto Scaling can suspend processes for Auto Scaling groups that repeatedly fail to launch instances.

This is known as an administrative suspension, and most commonly applies to Auto Scaling groups trying to launch instances for over 24 hours but have not succeeded in launching any instances.

You can resume processes suspended for administrative reasons.

Options A and B are incorrect since you should not delete either the Autoscaling Group or the Launch Configuration.

This will disrupt the architecture of the application.

Option D is incorrect since this is not possible with the AWS Config service.

For more information on suspending and resuming autoscaling processes, please visit the following URL-

https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html

The best answer to this question would be C. Suspend the scaling process so that you can investigate the underlying Instances.

The reason why this is the best answer is that suspending the scaling process allows the team to investigate the underlying instances while still keeping them running. Deleting the Autoscaling Group or Launch Configuration would result in terminating the instances, which would not allow the team to debug the problem.

Suspending the scaling process can be achieved by adjusting the desired capacity of the Autoscaling Group to the current number of instances. This will prevent the Autoscaling Group from launching or terminating instances automatically while allowing the current instances to continue running.

Using AWS Config to take a configuration snapshot of the instances and then investigating them is not a recommended solution for this issue, as it is not directly related to Autoscaling. AWS Config can be used to evaluate the configuration of AWS resources over time, and it is more suitable for compliance and auditing purposes. It could be helpful to use AWS Config to check if the instances comply with the application's configuration requirements.

In summary, suspending the scaling process would be the best solution as it would allow the team to investigate the underlying instances while still keeping them running.