[StarCluster] ERROR - Invalid AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY combination

[Justin Riley]

What version of boto are you using? Also You can determine this using:

$ python -c 'import boto; print boto.Version'

Also this is using StarCluster 0.91.2 correct?

~Justin

On 12/20/10 8:36 PM, Stuart Young wrote:
> Hi Justin,
>
> ElasticFox works fine with all three sets of credentials. I'm still 
> looking into boto's error. Will update you if I find anything.
>
> Cheers,
>
> Stuart
>
>
> On 12/20/2010 4:21 PM, Stuart Young wrote:
>> Hi Justin,
>>
>> Thanks for the debugging methods information - I actually got it 
>> working by trial and error using a permuation of method 2 but method 
>> 1 is so much more straightforward! (As you'll guess, I'm a noob to 
>> python.) I tracked the error down to boto's connect.py and 
>> ec2/connect.py modules:
>>
>>     awsutils.conn   self.conn()
>>     awsutils.conn   self.aws_access_key: **AAAAA<no-weird-symbols>HHHHQ**
>>     awsutils.conn   self.aws_secret_access_key:
>>     **4+0Ma<no-weird-symbols-except'+'>DrschU6**
>>     awsutils.py:57 - DEBUG - creating self._conn w/
>>     connection_authenticator kwargs = {'path': '/', 'region': None,
>>     'port': None, 'is_secure': True}
>>     awsutils.conn    Doing self._conn = self.connection_authenticator()
>>     awsutils.conn    self.connection_authenticator: <function
>>     connect_ec2 at 0x9c5cf8>
>>     boto.__init__.connect_ec2   
>>     boto.__init__.connect_ec2(aws_access_key_id,
>>     aws_secret_access_key, kwargs)
>>     boto.__init__.connect_ec2    aws_access_key_id: 
>>     AAAAA<no-weird-symbols>HHHHQ
>>     boto.__init__.connect_ec2   
>>     aws_secret_boto.__init__.connect_ec2access_key: 
>>     4+0Ma<no-weird-symbols-except'+'>DrschU6
>>     boto.connection.AWSQueryConnection.__init__   
>>     boto.connection.AWSQueryConnection.__init__(self, host,
>>     aws_access_key_id, aws_secret_access_key, etc)
>>     boto.connection.AWSQueryConnection.__init__   
>>     aws_access_key_id:  AAAAA<no-weird-symbols>HHHHQ
>>     boto.connection.AWSQueryConnection.__init__   
>>     aws_secret_access_key:  4+0Ma<no-weird-symbols-except'+'>DrschU6
>>     awsutils.conn    Returning...
>>     awsutils.is_valid_conn    boto.exception.EC2REsponseError RAISED!!!
>>     awsutils.is_valid_conn    e:  EC2ResponseError: 403 Forbidden
>>     <?xml version="1.0" encoding="UTF-8"?>
>>     <Response><Errors><Error><Code>SignatureDoesNotMatch</Code><Message>The
>>     request signature we calculated does not match the signature you
>>     provided. Check your AWS Secret Access Key and signing method.
>>     Consult the service documentation for
>>     details.</Message></Error></Errors><RequestID>deb3819a-d8d1-457a-a432-b6f35675be14</RequestID></Response>
>>     cluster._validate_credentials    ERROR OCCURRED in
>>     self.ec2.is_valid_conn
>>     cluster.py:770 - ERROR - Invalid
>>     AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY combination.
>>     cli.py:253 - ERROR - settings for cluster template "smallcluster"
>>     are not valid
>>
>>
>> I was able to connect and launch instances with my existing 
>> AWS_ACCESS_KEY and AWS_SECRET_ACCESS_KEY via the perl module 
>> Net::Amazon::EC2 so I'm perplexed as to why I'm getting the error 
>> using boto. I will try elasticfox as you suggested and update you later.
>>
>> Cheers,
>>
>> Stuart.
>>
>>
>>
>>
>>
>> On 12/20/2010 4:04 PM, Justin Riley wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 12/20/2010 11:19 AM, Stuart Young wrote:
>>>>      cli.py:1083 - ERROR - SignatureDoesNotMatch: The request signature
>>>>      we calculated does not match the signature you provided. Check your
>>>>      AWS Secret Access Key and signing method. Consult the service
>>>>      documentation for details.
>>> Hmmm this is an error reported directly from Amazon; this shouldn't be
>>> caused
>>> by boto and definitely not paramiko. I can reproduce this message if I
>>> remove a character from my AWS_SECRET_ACCESS_KEY so it seems either
>>> something's wrong with the keys in your config or wrong on Amazon's side.
>>> In the past when I've seen this message it's always due to using quotes
>>> or a stray
>>> character some where...
>>>
>>> Are these recently created accounts?
>>>
>>>> I got the same error when I tried with two other AWS accounts. Is this
>>>> maybe something to do with boto or paramiko?
>>> Would you mind installing elasticfox (firefox plugin) and see if it has
>>> issues with your access keys as well?
>>>
>>>> I was also wondering if it's possible to to run a local, unzipped copy of the StarCluster egg for
>>>> debugging purposes?
>>> Yes it is and there are two ways:
>>>
>>> 1. First uninstall starcluster (remove the egg from your site-packages).
>>> Download the 0.91.2 release, unpack it somewhere, and run python
>>> setup.py develop. This will 'link' the unzipped source to your python
>>> install. This means if you make changes to the source code, you will be
>>> able to import and see/use those changes without having to reinstall.
>>> This is currently how I'm developing the code.
>>>
>>> OR
>>>
>>> 2. Simply unzip the egg in your Python's site-packages directory and
>>> edit the source within your site-packages directory. You'll likely want
>>> to move the egg outside of your site-packages directory after you unzip
>>> it to make sure you import the unzipped code and not the egg.
>>>
>>> Does that make sense?
>>>
>>> ~Justin
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v2.0.16 (GNU/Linux)
>>> Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/
>>>
>>> iEYEARECAAYFAk0PxMwACgkQ4llAkMfDcrkylwCfQpHxxNaZsbXX3xBNe9hbRfgE
>>> QAkAnR2YlcUQTH4cQTEg4M8V8Cg8MQIc
>>> =1Rcm
>>> -----END PGP SIGNATURE-----
>>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/starcluster/attachments/20101220/5e54d971/attachment.htm