Closed nicklaw5 closed 1 year ago
Same problem when using the latest awscli v1.27.127 with elasticmq
e.g. creating a new SQS Queue results in:
An error occurred (400) when calling the CreateQueue operation: <ErrorResponse xmlns="http://queue.amazonaws.com/doc/2012-11-05/">
<Error>
<Type>Sender</Type>
<Code>MissingAction</Code>
<Message>MissingAction; see the SQS docs.</Message>
<Detail/>
</Error>
<RequestId>00000000-0000-0000-0000-000000000000</RequestId>
</ErrorResponse>
The fix is to downgrade the awscli to v1.27.126:
pip install awscli==1.27.126
Same problem as well
botocore
1.29.127
introduced this breaking change, it has been reverted in 1.29.128
see: https://github.com/boto/botocore/pull/2931
elasticmq
works fine with 1.29.128
👍
Hey, thanks for reporting the issue. The change would be quite big, so it will take some time to implement.
The json support has been implemented in 1.4.0
thanks to the amazing job by @katlasik and @flsh86
If you find any issue, please report.
AWS SDK JS v3.327.0 has changed the way SQS API calls are serialized. It appears they're now using AWS JSON-1.0 protocol. This is causing my requests to ElasticMQ to fail with errors like:
Here's a dump of the returned error response:
Once I bumped the AWS SDK JS back to v3.326.0 all worked fine again.