Good day.
I want to share new acquired experience.
Our company needed its own AMIs with Windows XP, Windows 7, Windows 8 and Windows Server 2003 in AWS Amazon.
After a relatively short search, it was found that there is such a possibility, and it is called AWS VM Import / Export Tools (more
here ).
However, the possibilities of this service are still limited:
Q. What operating systems are supported?
VM Import / Export currently supports Windows Server 2003, Windows Server 2003 R2 and Windows Server 2008 (Datacenter, Enterprise, and Standard editions) VM images. For a full list of supported VM file formats, are you supported? ..
Frankly, not seeing in the list of supported OS Windows XP, sighed with relief.
So, to the point. For all the manipulations, we need the installed VirtualBox (I have version 4.2.4) and Amazon EC2 API Tools (you can download the latest version
here ).
The OS version selected for import is Windows Server 2003.
Let's create a new virtual machine in VirtualBox.

When creating the machine, specify the type of VMDK disk.

')
Further, the installation process is the most common and there is no sense in paying attention to it in addition.
The main thing - do not forget to add a user with administrator rights and allow him to connect via RDP.
After our virtual machine is installed, turn it off and go to the File - Export Configurations menu and select the required configuration.

In the export options, we put the mark “Save as OVF” and check that the extension in the name of the saved file is also ovf.

The result of the export will be two files. One with the extension ovf, the other - vmdk, and that is what we will continue to use.
When the export is complete, you can proceed to download. Open a command prompt or terminal (depending on your OS) and do the following:
Where:
- -f VMDK - downloadable file format,
- -b windows2003x86 — Bucket name in AWS S3
- -o XXXXXXXXXX - access_key_id
- -w XXXXXXXXXXXX - secret_access_key
- -t m1.small is an instance type that starts with your configuration
- -a i386 - OS Architecture

After our configuration has been loaded into S3, the process of converting it into an EBS instance will begin.
Conversion progress is checked with the command:
In the output, we are interested in two values:
- Status completed - this means the conversion is completed.
- InstanceID i-b8923ac8 - Instance ID with our configuration
Now we can remove the create AMI from this instance, either from the console or using the CLI.
CLI is closer to me.
That's it, now we can safely start new servers with our new AMI.
I hope the information will be useful.
PS If someone has found a way to make AMI from XP or knows another import method, please share your experience.