Windows – How to get an EC2 Windows machine’s instance-id into a batch variable

The EC2Config is configured by default to rename the host on first startup. Renaming the host on windows requires a reboot and therefore every instance reboots once after first startup. You can disable the renaming of the host if you do not use the internal DNS for the instance. More details here:

Windows Configuration Service: http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/appendix-windows-config.html

The EC2Config service also has its own log file within the instance:

C:\Program Files\Amazon\Ec2ConfigService\Logs\Ec2ConfigLog.txt

And this file should have the EC2Config service relevant details that your are seeing on the Amazon Console Output. Here's a snippet from one of my instances:

=====Starting Ec2RebootInstance in a new thread=======
Ec2InitializeDrives: Found Disk : \.\PHYSICALDRIVE0
Checking current volumes for any device name change
C: is mounted with Volume Name
Opening COM port handle to write to the console
Ec2RebootInstance:Waiting for all threads to finish
Ec2InitializeDrives: Initialization finished. Plugin exiting...
Ec2RebootInstance:Checking if any thread requested a reboot
Ec2RebootInstance:Windows is Ready to use
Sending event windows is ready to use to everyone
Ec2RebootInstance:Monitoring for reboot requests.

Background

Launching an Instance from a Snapshot is not available for Windows AMIs (as you have meanwhile discovered yourself):

Important

Registering a snapshot works only for Linux/UNIX AMIs; although you can register a snapshot to create a Windows AMI, the AMI isn't launchable. [emphasis mine]

Alternative

While not specified, one should be aware of the possibility to simply clone an Amazon EBS-Backed Instance as outlined in Creating an Image from a Running Instance - when doing this via the AWS Management Console like so, EC2 attempts to cleanly shut down the instance before image creation and reboots the instance afterwards. This is obviously generally preferable, however, it can be avoided via the command line, if so desired:

If you prefer the instance not be rebooted, you can use the Amazon EC2 command line tools to create the image [...]. The ec2-create-image command has a --no-reboot option.

Solution

The alternative approach mentioned above obviously won't help to create a new EC2 instance from one of these snapshots as specified - a solution useful to be aware of anyway is outlined in section Moving to a New Instance of Eric Hammond's article Move a Running EBS Boot Instance to New Hardware on Amazon EC2 (which has a different use case, but applies regardless) and boils down to these steps in your case:

1. Create a new instance with the same startup parameters as the original one.
2. Wait until the new instance is running and then stop (not terminate) it.
3. Detach the EBS boot volume from the new instance and delete this detached volume, as it is not required anymore.
4. Create a new volume from the snapshot and attach it to the new instance.
5. Restart the new instance which is now going to boot with the volume created from your snapshot.

This technique has been used by Colin Percival to enable running FreeBSD on EC2 via defenestration as well btw. (which includes some hints towards the virtualization issues):

EC2 Windows instances, on the other hand, are launched in HVM (Hardware Virtual Machine) mode — which FreeBSD supports very well. If we can somehow trick EC2 into launching FreeBSD the same way as it launches Windows, we can run FreeBSD on a wide range of instance types. How can we trick EC2? Take advantage of the fact that Elastic Block Store disks can be detached from EC2 instances and reattached to different instances, and replace the boot disk of a "Windows" instance with a disk containing FreeBSD.