Comment 0 for bug 1122472

Latest/recent version of boto don't work with heat - looks like AWS changed their signature format to a new version which we don't yet support:

Investigation required to decide if we support the new signature format (will require the keystone ec2 api to support it), or figure out how to force boto to use the old format as an interim solution.

# heat-boto resource wordpress_ap3 WikiDatabase
send: 'GET /v1/?Action=DescribeStackResource&ContentType=JSON&LogicalResourceId=WikiDatabase&StackName=wordpress_ap3&Version=2010-05-15 HTTP/1.1\r\nHost: 127.0.0.1:8000\r\nAccept-Encoding: identity\r\nContent-Length: 0\r\nAuthorization: AWS4-HMAC-SHA256 Credential=27da451dba8148cbbde31641b32d17eb/20130211/0/127/aws4_request,SignedHeaders=host;x-amz-date,Signature=bb9578c10b212e774d4ff064188a912c5de87f1c33651fc0a16dd5468f0238ba\r\nX-Amz-Date: 20130211T221800Z\r\nUser-Agent: Boto/2.8.0-dev (linux2)\r\n\r\n'
reply: 'HTTP/1.1 400 IncompleteSignature\r\n'
header: Content-Type: application/xml; charset=UTF-8
header: Content-Length: 171
header: Date: Mon, 11 Feb 2013 22:18:00 GMT
ERROR:400 IncompleteSignature
ERROR:<ErrorResponse><Error><Message>The request signature does not conform to AWS standards</Message><Code>IncompleteSignature</Code><Type>Sender</Type></Error></ErrorResponse>
ERROR:Failed to resource. Got error:
ERROR:BotoServerError: 400 IncompleteSignature
ERROR:<ErrorResponse><Error><Message>The request signature does not conform to AWS standards</Message><Code>IncompleteSignature</Code><Type>Sender</Type></Error></ErrorResponse>