Windows Image Optimization State is enabling-failed

Question

Hello!

We've read about the new Launch Speed Optimizations for Windows Server (https://aws.amazon.com/about-aws/whats-new/2022/01/aws-speed-optimizations-windows-instances-ec2/ ) and wanted to try it out, as it really fits our use-case.

However, on every Image we enable the optimizations spins up several t3 instances for like half an hour and then ends up in an **enabling-failed** state. Our image is Windows Server based and usually runs on g5.

Greetings
Dominique

Answer

Hi! I figured out the problem with AWS Support - the instance's boot volume did not have enough free space to complete the sysprep procedure. Apparently one needs to make sure that at least 2 * the user profile fits.

(answering from my IAM account)

Answer

Is your Windows AMI created using sysprep? Does your AMI support user data execution on launch? The Fast launch feature launches t3 based instances when enabled to create fast-launch snapshots. Once these snapshots are created, the t3 instances are terminated. The fast-launch snapshots are eventually used to speed up your instances launched from the enabled AMI. The feature may go to enabling-failed if the instance does not support user data execution. Happy to work with you to debug further.

Windows Image Optimization State is enabling-failed

関連するコンテンツ