AWS DevOps Engineer Professional Practice Test

When changing the instance type of an Auto Scaling Group, what are the required steps?

1. Modify the existing launch configuration directly

2. Copy the existing launch configuration, modify the instance type, and attach the new launch configuration to the existing ASG

3. Terminate the existing instances and launch new ones

4. Change the configuration in the AWS Console

The correct answer is: Copy the existing launch configuration, modify the instance type, and attach the new launch configuration to the existing ASG

The correct answer indicates the necessity of creating a new launch configuration to change the instance type of an Auto Scaling Group (ASG). When you modify an Auto Scaling Group, you cannot directly alter the instance type in an existing launch configuration. Instead, the typical and recommended procedure involves copying the existing launch configuration, altering the instance type as needed, and then attaching this newly created configuration to the ASG. This approach ensures that all instances launched as part of the ASG will now utilize the updated configuration, while preserving the original settings and instances until they are replaced. Once the new launch configuration is in place, you can trigger scaling actions or update the group settings to begin using the new instance type. This method also allows for a smooth transition without any unintentional downtime since instances can be replaced gradually. Maintaining the integrity of the existing instances and configuration helps minimize disruptions in service continuity. It is essential to follow this structured process to align with AWS best practices for managing Auto Scaling Groups effectively.