BackBlaze B2

Starting September 14, new B2 buckets will automatically use Server-Side Encryption with Backblaze-managed keys (SSE-B2) by default. Existing buckets will receive the new default gradually.

Once enabled for a bucket, new uploads and destination copies that do not explicitly request SSE-C will automatically use SSE-B2 with AES-256 encryption at rest. You cannot disable server-side encryption for new uploads or destination copies after this change takes effect for a bucket.

No action is required. You do not need to update your application, add an encryption header, or enable a bucket setting.

A few things to keep in mind:

Existing objects will retain their current encryption state and will not be rewritten.
Valid SSE-C requests will continue to use your customer-provided encryption key.
Buckets already configured for SSE-B2 are unaffected.
There is no additional charge for SSE-B2 and no impact on upload or download performance. Normal B2 storage and API charges still apply.
If you want an older unencrypted object to use SSE-B2, upload it again or create a new destination copy.
 
Back