search

dwilkie / carrierwave_direct

Process your uploads in the background by uploading directly to S3
MIT License
839 stars 181 forks source link

Unable to use AWS4-HMAC-SHA256 #217

Closed rmaspero closed 6 years ago

rmaspero commented 7 years ago

I believe I've followed all the instructions but seem to get the following error

<Error>
<Code>InvalidRequest</Code>
<Message>
The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
</Message>
<RequestId>77007434876C64A9</RequestId>
<HostId>
CABOhE9/c+mAMk75qDnm8/d/T2rjl4BLI4Qndre/HUZWJLjhjPitCvDqN79MOTiAHUI76V+b8Iw=
</HostId>
</Error>

Carrierwave works normally, but when I try and do Carrierwave_direct I get this message. My S3 bucket is in London, I don't know if this might affect it. I've been over everything again and again but can't seem to solve this?

rmaspero commented 7 years ago

I was able to solve the issue by changing my buckets location to an older location which supports the older signatures. Not really a fix, but now works.

alkami-io commented 6 years ago

Is there anymore info on this particular issue? I'm having the issue with a bucket on us-east-2 and have not come across any info on how to resolve it.

Thanks.

runephilosof commented 6 years ago

You have to use the master branch since the fix for this has not been released yet.

p8 commented 6 years ago

I've just released version 1.0.0.