Mucking about with virtual disks, I wanted to install qemu on a AWS EC2 instance in order to use qemu-img. Not finding it in a yum repo, I built it from scratch: $ uname -a Linux ip-10-0-1-238 4.4.41-36.55.amzn1.x86_64 #1 SMP Wed Jan 18 01:03:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Steps: sudo yum install -y ghc-glib-devel ghc-glib autoconf autogen intltool libtool wget http://download.qemu-project.org/qemu-2.8.0.tar.xz tar xvJf qemu-2.8.0.tar.xz cd qemu-2.8.0 ./configure make sudo make install I hit a few errors, recorded here for passing Googlers:

So you’ve got a Linux VM that you want to access the contents of in EC2 - how do you do it? Let’s see how. First up, convert the VMDK to raw image file. If you’ve got a ova/ovf then just untar it first (tar -xvf my_vm.ova), from which you should get the VMDK. With that, convert it using qemu-img: $ time qemu-img convert -f vmdk -O raw SampleAppv607p-appliance-disk1.vmdk SampleAppv607p-appliance-disk1.raw real 16m36.

Presented without comment, warranty, or context - other than these might help a wandering code hacker. When using SigV4, you must specify a ‘host’ parameter boto.s3.connection.HostRequiredError: BotoClientError: When using SigV4, you must specify a 'host' parameter. To fix, switch conn_s3 = boto.connect_s3() for conn_s3 = boto.connect_s3(host='s3.amazonaws.com') You can see a list of endpoints here. boto.exception.S3ResponseError: S3ResponseError: 400 Bad Request Make sure you’re specifying the correct hostname (see above) for the bucket’s region.