Yes, if you are creating your own private AMIs you have to change the S3_BUCKET setting in hbase-ec2-env.sh to a bucket that you own. The HBase public AMI bucket is read only. :-) If the bucket name you specify does not exist it will be created by ec2-upload-bundle. You may want to try that route if there is some ACL issue on an existing bucket.
I remember some problem with the ant copy task in the build not maintaining permissions on the helper scripts. Perhaps if you use the latest scripts from 0.20 branch in SVN this is no longer an issue? Either way, chmod 755 bin/* bin/image/* locally before doing anything will clear up any potential problem with missing +x. Meantime, I am finally getting around to building HBase AMIs in all EC2 regions. Sorry for the trouble. - Andy > From: Tim Robertson <timrobertson...@gmail.com> > Subject: Re: EC2 scripts > To: hbase-user@hadoop.apache.org, apurt...@apache.org > Date: Saturday, March 27, 2010, 11:39 AM > Hi Andy, > > Thanks - appreciate that. I haven't used EC2 in a > while and it was always US-East last time despite me being > in Europe, but I'll dig into it. > > Actually I started creating my own hbase AMI today using > your scripts but it failed on > > /mnt/create-hbase-image-remote > > with privileges error. I SSH'ed onto the machine and > (ahem) ran chmod 777 and was able to get it into my own > S3 bucket, but then I could not get an ec2-register to > work at all with an ACL issue.
