TechPrufer
Get started
Backblaze
Backblaze logoBackblaze · Feature trail

Default Server-Side Encryption for B2

2 posts · Aug 2026 – Sep 2026

What this trail covers

Backblaze B2 Cloud Storage now enforces Server-Side Encryption with Backblaze-managed keys (SSE-B2) using AES-256 as the default for all new uploads and destination copies. This change is applied automatically without requiring application modifications, additional costs, or performance impacts. Existing objects retain their original encryption state. Server-Side Encryption with Customer-Managed Keys (SSE-C) remains available for users who need to provide their own encryption keys.

All Backblaze trails
  1. TAMS and Backblaze B2: Cloud-Native Media ProductionThis post introduces the integration of Backblaze B2 with the Time Addressable Media Store (TAMS) standard, enabling cloud-native media production workflows. It details how TAMS organizes media by time into timestamped segments stored in object storage, allowing interoperable tools to access content via an open API. The post highlights the roles of ecosystem partners LiveWyer (TAMOSS for API layer), CuttingRoom (browser-based editor), and Drastic Technologies (NetX for ingest/read/write) in building these workflows on Backblaze B2. It emphasizes the benefits of TAMS for live video production, including real-time editing of live feeds, efficient media reuse, and scalable cloud storage for large media datasets at a cost-effective price point.
  2. Backblaze B2 Adds Default Encryption for New UploadsThis post announces the enforcement of SSE-B2 as the default for all new uploads and destination copies in Backblaze B2 Cloud Storage, starting September 14, 2026. This change is automatic, requires no application modifications, and has no additional cost or performance impact. Existing objects retain their prior encryption state. SSE-C remains available for users who need to provide their own keys. The post provides examples of how this default applies to S3-Compatible API and B2 Native API usage, highlighting that explicit encryption flags are no longer necessary for new data.