1 Answer
- Newest
- Most votes
- Most comments
0
The Fast Launch feature itself launches temporary instances, which are used to do the prep steps which happen on the first Windows boot. See the steps at the top of this doc for more details: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/win-ami-config-fast-launch.html
If you're using an ASG, then you could instead use a Warm Pool, which accomplishes a similar goal. It allows you to pre-provision instances, take care of the delays from the first Windows boot, as well as run any user-data you might want to get your application setup. After that's all done, you would complete the Lifecycle Hook on the ASG (as the last step in the userdata script), which tells the ASG to Stop that instance until its needed for a scale-out action
Relevant content
- asked 8 months ago
- asked a year ago
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Can you check the Tags on one of the new instances to confirm its being launched by the AutoScaling Group? If yes, can you check the "Activity" tab of the Group and see what reason it gives for launching the new instances?
It's not started by the ASG. It seems it might be part of the provisioning of the Fast Launch that it starts EC2 instances. But the Fast Launch enabling always fails with the reasoning: Unable to stop instance (ID=i-xx) for snapshot creation.