A game studio must replace Auto Scaling instances with a new launch template version without dropping below the healthy capacity the team requires. Deleting the group and creating it again was proposed. What should perform the replacement?
Select an answer to reveal the explanation.
Short Explanation
You repave one lane while the other lanes stay open. An instance refresh replaces launch template instances gradually and holds the minimum healthy percentage, instead of deleting the whole group. The trap is a big-bang terminate that drops everyone at once.
Full Explanation
An instance refresh replaces Auto Scaling instances with instances launched from the current launch template. The minimum healthy percentage tells the refresh how much of the group's desired capacity must stay healthy while replacements proceed, so the group is not taken down at once. Deleting the group removes the service before any replacement group exists. Terminating every instance at once ignores that percentage and lets healthy capacity fall as far as the replacements lag. Raising desired capacity for good adds instances and cost and does not retire members that still run the old template. The percentage is the team's availability choice on that refresh, and a value that leaves no room under the group's maximum size can stall the refresh because replacements cannot launch before old instances are removed. Start the refresh, watch the healthy count stay within the limit the team set, and confirm the new instances show the new launch template version. Instance refresh follows the group's current launch template, so set that template version before starting the refresh or the new instances will keep the old one.