backblaze S3 storage - access and secret key length

After some research, it appears that the key length is actually variable: docs.aws.amazon.com/.../API_AccessKey.html

Did you ever figure out how to add the credentials? My Backblaze Access Key and Secret Key are not the same length as AWS values and I cannot add my Backblaze storage.

Quest told me they had no plans on making the field length compatible in the software and that I should contact backblaze to ask them if they can make a compatible length string. Backblaze said they couldn't do that so it looks like Backblaze can't be used. I started research Wasabi storage at that time but didn't have an opportunity to test it out yet.

I'm not sure why they need to bother to validate the length of either string. I'm sure there are more S3 compatible services out there and they may not all be exactly the same string length. Just doing an eval now...so good to find this out before spending too much time on Rapid Recovery. Thanks for your quick response!

I'm not sure why they need to bother to validate the length of either string. I'm sure there are more S3 compatible services out there and they may not all be exactly the same string length. Just doing an eval now...so good to find this out before spending too much time on Rapid Recovery. Thanks for your quick response!