euca2ools

[Garrett Holmstrom]

On 11/11/2010 1:50, Jan Pazdziora wrote:
> On Wed, Nov 03, 2010 at 10:36:19AM -0500, Garrett Holmstrom wrote:
>>
>> euca2ools aims to be an open source drop-in replacement for most of
>> ec2-*-tools.  While you folks are working with your images, please try
>> installing the euca2ools package and running euca-attach-volume instead
>> of ec2-attach-volume, euca-run-instances instead of ec2-run-instances,
>> and so forth so we can get things working without needing to install
>> proprietary bits from Amazon.
>
> Thank you for pointing this out. I've tried
>
> 	$ euca-describe-instances
> 	EC2_ACCESS_KEY environment variable must be set.
> 	Connection failed
>
> while having EC2_CERT and EC2_PRIVATE_KEY setup and in shell where
> ec2-describe-instances works. The man euca-describe-instances(1) says
> that
>
>         Euca2ools  will  use the environment variables EC2_URL, EC2_ACCESS_KEY,
>         EC2_SECRET_KEY, EC2_CERT, EC2_PRIVATE_KEY, S3_URL,  EUCALYPTUS_CERT  by
>         default.
>
> Is there anything else I need to have setup beyond EC2_CERT and
> EC2_PRIVATE_KEY?

Euca2ools programs don't hard-code things like URIs, so you typically 
need to specify more in the environment to get them to work with AWS.

I recommend setting everything of importance up in your shell's rc file. 
  For instance, my .zshrc file contains something similar to this:

export S3_URL=https://s3.amazonaws.com:443
export EC2_URL=https://ec2.amazonaws.com:443
export EC2_PRIVATE_KEY=~/ec2/euca2-gholms-00000000-pk.pem
export EC2_CERT=~/ec2/euca2-gholms-00000000-cert.pem
export EC2_ACCESS_KEY='00000000000000000000'
export EC2_SECRET_KEY='0000000000000000000000000000000000000000'

...where the '0's are replaced with account-specific numbers and things.

At the moment you need all six of these variables, though the *_KEY 
variables may not be necessary in future releases.