Description of problem:
In the older boxgrinder release, we were using ec2-ami-tools to do the bundling and uploading of ec2 images to S3.  When those tools were in use, they would automatically create appropriate buckets in S3 if they did not exist.

Because of licensing concerns, newer boxgrinder has moved to euca2ools to do the bundling and uploading of ec2 images.  This tool does *not* create appropriate buckets, so if the bucket we expect is not there, the upload portion will fail.

In the conductor we should manually create the bucket that we need when the user first registers with us.  That will ensure that the appropriate bucket always exists.