The request signature does not match about aws-elixir

[tomazbracic]

Hi @philss

Awesome!!! It works now. Thank you so much!

[philss]

Hi @tomazbracic 👋

I'm not sure what is happening, but I found this mention in the docs:

The service endpoints that expose this API are listed in Amazon Web Services IoT Core Endpoints and Quotas. You must
use the endpoint for the region that has the resources you want to access.

Maybe you need to specify a custom endpoint for that. Can you give it a try? To change the endpoint you can use AWS.Client.put_endpoint/2.

[tomazbracic]

Doesn't help. I used endpoint listed there, called AWS.Client.put_endpoint/2 function. It did set it... but calling AWS.IoT.describe_thing/2 doesn't work. The same error.

body: "{\"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.\"}",```

[philss]

OK, thanks. I wanna try to compare this with what the Ruby SDK is doing. I'm almost sure that is a requirement for this endpoint that we are missing. By the way, have you tried with a SDK in another language?

[tomazbracic]

Ok, I tried to use Go's v2 SDK and I get Things listed just fine. Without any real specifics. I am using pretty much the same credentials for retrieving S3 buckets as for listing and reaching out to IoT service.

[philss]

Oh, interesting. Thanks for the testing! I'm going to research more about that. It's probably a bug on our side... maybe a header missing or a signature bug.

[tomazbracic]

Can you say at this moment... when you will have more info on this? Do you think this is something that might be fixed soon? or... you don't see it like that?

[philss]

@tomazbracic sorry for the delay. I think I found the issue and fixed it here: ce47b9f

Can you confirm that the version from the master branch fixes the problem? I'm going to release a version after this.

[philss]

@tomazbracic the fix was released in v0.9.1 :)