Configuring Windows Components (Like IIS) on Amazon EC2

After getting my Amazon EC2 imaged created, I quickly discovered that the default image is as bare-as-bare-as-can-be.  They had other default images with SQL Server 2005 Express on it, but I prefered to use a clean Windows customized by yours truely.

Optional Windows Server operating system components are typically added or configured using installation media. This tutorial describes how to add or configure optional Windows components within the Amazon EC2 environment.

Windows Server operating systems include many optional components. Installing all components on each Amazon EC2 Windows AMI is not practical. Instead, you can access the necessary files to configure or install components using Elastic Block Storage (EBS) Snapshots.

The following is a list of available snapshots:

  • Windows 2003 R2 Enterprise 32-bit: snap-bb10f6d2
  • Windows 2003 R2 Datacenter 32-bit: snap-8010f6e9
  • Windows 2003 R2 Enterprise 64-bit: snap-d010f6b9
  • Windows 2003 R2 Datacenter 64-bit: snap-a310f6ca

Simply add the volume with a size of 2GB – using whatever tool or command line you prefer – to set it up and attach it to the instance you want to configure.  It might take a few moments for the instance to detect the volume, but after that, you will then be able to configure the Windows Components Wizard to point to the new volume.

4 thoughts on “Configuring Windows Components (Like IIS) on Amazon EC2

Leave a Reply to RajDeep Singh Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.