WireByte

Home / Technology

Photo of robotics warehouse, network, office team
Image: Wikipedia
Technology

Amazon S3 Files and ZeroFS Expose POSIX Filesystems Backed by Object Storage

WireByte Staff · July 11, 2026

Amazon S3 Files and ZeroFS offer POSIX filesystems backed by object storage, but with different approaches. S3 Files preserves file identity, while ZeroFS trades direct access for packing, compression, and encryption. This choice affects storage layout and performance. The move highlights the evolving landscape of cloud storage solutions.

Key points

  • Amazon S3 Files and ZeroFS expose POSIX filesystems backed by object storage, offering alternative approaches to traditional storage solutions.
  • S3 Files preserves file identity, maintaining a one-to-one correspondence between files and objects in the bucket.
  • ZeroFS, on the other hand, trades direct S3 access for packing, compression, and client-side encryption, resulting in an opaque internal layout.
  • The choice between S3 Files and ZeroFS depends on the role of the bucket: S3 Files is suitable for preserving file identity, while ZeroFS is ideal for internal persistence layers.
  • The introduction of these solutions highlights the growing importance of object storage and the need for flexible, scalable storage options in the cloud.

Amazon S3 Files and ZeroFS Expose POSIX Filesystems Backed by Object Storage

Amazon Web Services (AWS) has introduced two new solutions, S3 Files and ZeroFS, which expose POSIX filesystems backed by object storage. While both solutions offer a shared interface, they differ in their approach to storage layout and performance.

S3 Files: Preserving File Identity

S3 Files is built using Amazon Elastic File System (EFS) and maintains a one-to-one correspondence between files and objects in the bucket. This means that if a file is modified, the corresponding object in the bucket will be updated accordingly. S3 Files is suitable for use cases where file identity needs to be preserved, such as in traditional file systems.

ZeroFS: Trading Direct Access for Packing and Encryption

ZeroFS, on the other hand, trades direct S3 access for packing, compression, and client-side encryption. This results in an opaque internal layout, where the client sees an S3 object but not the underlying file system. ZeroFS is ideal for use cases where the bucket can be used as an internal persistence layer, such as in distributed systems.

Choosing Between S3 Files and ZeroFS

The choice between S3 Files and ZeroFS depends on the specific use case and requirements. S3 Files is suitable for preserving file identity, while ZeroFS is ideal for internal persistence layers. The introduction of these solutions highlights the growing importance of object storage and the need for flexible, scalable storage options in the cloud.

What's Next?

As the landscape of cloud storage solutions continues to evolve, it will be interesting to see how S3 Files and ZeroFS are adopted and integrated into existing systems. The flexibility and scalability offered by these solutions make them attractive options for developers and organizations looking to build and deploy cloud-native applications.

Sources

WireByte Staff — Editorial Team

The WireByte editorial team synthesises technology news from multiple primary sources, verifies the facts, and links every source. Articles are produced with AI assistance and reviewed under our editorial policy.