S3 Authorization mechanism issue

It's an issue I just had, but I found the solution. Posting here in case someone else encounters the same problem.

I had a bucket in the eu-central-1 (Frankfurt), and upload wasn't working. I was just receiving an error: true. With some debugging I found that the authorization mechanism was the problem, as explained here:

http://stackoverflow.com/questions/26533245/the-authorization-mechanism-you-have-provided-is-not-supported-please-use-aws4

Looks like new regions are using a new way of securing datas: "AWS4-HMAC-SHA256, also known as "V4," is one of two authentication schemes in S3.". The temporary solution was to change region for eu-west-1 (Ireland), but I guess that the new mechanism will soon be the standard, so... any plan to support it in this package?

Thanks.

Jun 23 '16 08:06 nicooprat

I'm definitely updating the package to V4

Jun 23 '16 14:06 Lepozepo

Great! Hope you'll keep the way it works for now. Your package is the only one using local collections to store objects, and it's really handy for treating multiple images uploads at once and managing disconnected state.

Jun 23 '16 14:06 nicooprat

No more auth issues since 46998ed01dd9d0b9166a4e520b69f4f257015d86, but can't delete files. API returns true as if no error happened, but the file is not deleted on S3... Deleting files works fine with the previous bucket (eu-west-1). Policies and CORS are the same. The only difference is the owner of the bucket – no idea why I'm not the owner of the new bucket (different behaviours per region?) – but I guess this is not related to the issue...

Jun 27 '16 13:06 nicooprat