I was working through creating a bunch of Amazon Machine Instances for internal use. And here is the kicker: they all descend from a single Debian 6 image with some custom Java and build tools support.
I proceeded to get the error reading certificate file amitools/cert-ec2.pem error, as posted by traxonius, when trying to create new descendant images.
I also had the pleasure of getting keyring errors because all of the Debian apt-get keyring files get dumped by the AMI bundle rules.
my original API/AMI setup
I set up my tools in
/opt/ec2 based on the following commands from the
CreateEC2Image article on the Debian project wiki.
wget http://s3.amazonaws.com/ec2-downloads/ec2-api-tools.zip wget http://s3.amazonaws.com/ec2-downloads/ec2-ami-tools.zip unzip ec2-api-tools.zip unzip ec2-ami-tools.zip mkdir /opt/ec2 rsync -ar ec2-api-tools-*/* /opt/ec2 rsync -ar ec2-ami-tools-*/* /opt/ec2 rm -rf ec2-api-tools* rm -rf ec2-ami-tools*
EC2_HOME by adding
export EC2_HOME=/opt/ec2 to
EC2_HOME/bin to your
PATH by updating
export PATH to look like
chmod -R 755 /opt for good measure.
the hackish fix
If you are only using these images for intra-company use, then you might be able
to take advantage of the slightly hackish solution I used. I removed
the excerpted lines from the
'"*.pem"', '"*.priv"', '"*.gpg"', '"*.jks"',
223 words. Post tags: AWS, AMI, certificate, and bundle.