Hi everyone!
I’m sharing what many of my clients ask me every day regarding the S3 protocol, and why it’s the best choice for a backup repository.
From a security standpoint, S3 features native immutability rather than an artificially added layer. Unlike applying immutability to file or block storage—where an extra layer is imposed that can degrade performance and increase the likelihood of security vulnerabilities (most notably via administrator access).
S3 provides it natively at its core.
The S3 (Simple Storage Service) API has become the industry's de facto standard for cloud object storage, thanks to its unmatched scalability, stateless HTTP-based flexibility, and broad ecosystem support.
Instead of rigid file structures, S3 flattens data into easily manageable objects inside buckets.
While Block, File, and S3 are general-purpose storage protocols used across various use cases, S3 is the only protocol with a native mode designed specifically for the absolute immutable backup storage use case: S3 Object Lock in COMPLIANCE mode.
Exclusive Object Lock in Compliance Mode
S3 Object Lock guarantees that written object versions cannot be modified or deleted during the established retention period.
Governance Mode (where users with elevated privileges can bypass the lock) and Compliance Mode (where no one can delete them).
Let’s think about the Flat and Efficient Data Structure:
Traditional Storage (File / Block)
-
Relies on rigid and complex hierarchical structures.
-
Requires continuous metadata search operations and directory traversal.
-
Creates severe bottlenecks when scaling to billions of files.
S3 Protocol (Object-Based)
-
Flattens the data structure by storing objects inside global buckets.
-
Eliminates complex directory trees, enabling management of massive data volumes.
-
No performance degradation.
Native Immutability Without Artificial Layers
Unlike traditional file or block systems where immutability is enforced by adding extra software layers, S3 integrates it directly into the protocol's core.
Extra artificial layers degrade overall performance and create critical security vulnerabilities (such as admin access bypasses).
In S3, protection occurs natively at the storage level.
No permanent session structures: Unlike Block/File protocols (SMB/NFS), S3 does not require maintaining continuous open and close file states.
Direct access to objects: Specific blocks are accessed directly via pure HTTP/REST calls (GET, PUT).
Lower cache memory usage: Drastically reduces server overhead by not requiring persistent state tables.
Unlimited linear scalability: Facilitates massive concurrent processing for demanding backup environments.
