We currently don't have a way to remove the bucket name completely and unfortunately don't have full CNAME support.

Cloudflare Workers would be able to do it on a small scale, but they cost $0.50 per million requests, which is prohibitively expensive for any high-traffic website. You need to put some kind of URL rewriting service of your own in the workflow. As of, they do not have a way to accomplish this using just Cloudflare DNS + B2, even using the S3-like CNAME here. Is there any way to ditch the /file/ in URLs if you are using Backblaze B2 and Cloudflare together? Cloudflare workers might work, but they are very expensive to use to re-write every image request we receive.Įdit: Backblaze support responded. Also also this prevents you from using b2 to host any sort of static website.) (That pattern leaks the name of the bucket you are using to everyone. It would probably be a huge blocker if we had to change the public structure of our file URLs just to use Backblaze. I can see that our test files are available without that part of the path using the file's 'S3 URL' on Backblaze, but that particular sub-sub-subdomain doesn't seem to work as a CNAME target on Cloudflare. However, after I set up a trial bucket and a subdomain on Cloudflare, I can't seem to figure out how to ditch the the /file/ portion of the URL.

We are considering migrating our S3 buckets to Backblaze to take advantage of the Cloudflare Bandwidth Alliance and save a bunch of money.

Backblaze cloudflare