I guess it must upload as one step internally, then try to adjust ACL as another step which is the part that fails. But it does still error out which is not good for an Ansible task. Anyone get Ansible working with Backblaze before? Thanks!Įdit: Oh, the upload actually worked (it takes a while before it shows up in the UI). So, I am surprised it doesnt work, and not sure how to work around it.

The application key I am using does have 'writeFiles' permission (confirmed in UI) which should have access to 'Put Object ACL' as per the same Backblaze documentation page. but my bucket is marked as private so that should already be okay. Backblaze, however, was significantly faster at restoring files. Meaning that the object permission ('private') needs to match the bucket permission. IDrive managed to transfer the folder in just 1 hour and 32 minutes, while Backblaze took 2 hours and 42 minutes. The call will succeed only when specified ACL matches the ACL of the bucket. The Put Object ACL call only supports the same canned ACL values mentioned previously. Which is odd because according to BackBlaze documentation: My task definition is: - name: Install required dependencies I am trying to use Ansible's community S3 task to upload a file to S3 compatible Backblaze but alas no success. Backblaze gets high marks from a security perspective: not only can you enable two-step authentication on your account, but you can also rely on AES 128-bit encryption and an SSL connection to.

Backblaze vs amazon