Thankfully, this can be done using a small ruby script. First, install the needed ruby gems:

>sudo gem install right_aws

Then, paste this into your text editor, and edit before you run:

 
#!/usr/bin/env ruby -w
 
require 'rubygems'
require 'right_aws'
 
s3 = RightAws::S3.new(aws_access_key='your-access-key-here', aws_secret_access_key='your-secret-access-key-here')
 
s3.buckets.each do |bucket|
 
  keys = bucket.keys('max-keys'=>1000 )
 
  while keys.length > 0 do
    keys.each do |key|
      puts key.full_name
      key.delete
    end
    keys = bucket.keys('max-keys'=>1000 )
  end
 
  bucket.delete
 
end
 

Note that I only get a 1000 keys at a time. Having a lot of files in a bucket will break most GUI tools, because they try to do to much - like listing all of my files...

Happy deleting!

Tip: Run this for an instance on Amazon, not from your own computer. Running inside Amazon is much faster.

First step is to boot an instance. You need the command line tools for this, as neither the AWS Management Web Console nor ElasticFox currently supports this right now (note to developers - please add!).

ec2-run-instances --region eu-west-1 \
     -K pk-YOURKEYHERE.pem \
     -C cert-YOURCERTHERE.pem \
     -b '/dev/sda1=:100' \
     ami-d7a78ca3 \
     -g my-security-group -g common-security-group \
     -t m1.large \
     -k thekeyhere \
     --disable-api-termination \
     --instance-initiated-shutdown-behavior stop \
     -z eu-west-1a

• The command is ec2-run-instances with an 's' in the end. There is another command in the API without the s, which doesn't work.
• -b is the most important flag here. It says to make the boot disk (/dev/sda is Linux speek for C:) 100 GB, despite what the AMI manifest says (which is 30 GB).
• ami-d7a78ca3 is the Windows image, in this case a 64bit Windows 2008.
• -g security-group you should add as many as you like. Remember to think these through, since you cannot change which groups an instance belongs to.
• The flags --disable-api-termination --instance-initiated-shutdown-behavior stop are really nice, because that make sure you cannot accidentally terminate the instance, making the harddrive disappear.
• Note that I'm running in the EU region here.

Ok, so now you have a running Windows server. Once it has booted, you log on using remote desktop (well, as soon as you have the generated password, which takes 15 min). PLease note that the C: drive will show up as 30 GB at this point. The partition is still only 30 GB, even if the virtual harddrive is 100 GB.

1. Go into the windows management console. Go to disk management.
2. Right-click on the C: drive. Choose Extend volume from the context menu.
3. In the wizard that pops up, just accept the defaults, and click finish.

Done! The change is instant (no reboot or anything), and your system drive C: is now 100 GB.