-----BEGIN PGP SIGNED MESSAGE-----
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
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.
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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
Received on Mon Dec 20 2010 - 16:04:19 EST