• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Subscribers 29 subscribers
  • Views 3239 views
  • Users 0 members are here
Options
Related

backblaze S3 storage - access and secret key length

mbeccaria
over 3 years ago

We are running Rapid Recovery 6.4. I am trying to utilize Backblaze S3 compatible storage (https://www.backblaze.com/blog/backblaze-b2-s3-compatible-api/) and am running into an issue. When I create an app key in backblaze it gives me a string for the "Access Key" that is longer than 20 characters and a "Secret Key" that is less than 40 characters. RR will not let me save the credentials as a new cloud account because of this. Is there a reason that those string limits are in there? If BackBlaze is not being compliant I am happy to contact them, but at this point I'm not sure if this is an S3 compatible requirement. Anyone know how best to proceed?

Mike

Parents Reply Children
  • 0 over 3 years ago in reply to ransaldo

    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.

  • 0 over 3 years ago in reply to mbeccaria

    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!