Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. Amazon Web Services
  3. s3fs-fuse

s3fs-fuse

GPL-2.0C++v1.97

A FUSE-based file system that allows Linux, macOS, and FreeBSD to mount an S3 bucket as a local file system.

GitHubGitHub
9.8k stars1.1k forks0 contributors

What is s3fs-fuse?

s3fs-fuse is a FUSE (Filesystem in Userspace) implementation that allows operating systems like Linux, macOS, and FreeBSD to mount an Amazon S3 bucket as a local file system. It preserves the native object format for files, enabling seamless interoperability with other tools like the AWS CLI, and makes cloud storage accessible through standard file operations. This bridges cloud object storage with traditional file system interfaces, addressing the need for familiar file management in S3 environments.

Target Audience

System administrators, DevOps engineers, and developers who need to interact with S3 or S3-compatible object storage as if it were a local file system, particularly for tasks like file backups, data migration, or integrating cloud storage into legacy applications. It is also suitable for users on non-AWS platforms who require compatibility with various S3-based object stores.

Value Proposition

Developers choose s3fs-fuse for its POSIX compatibility, which supports a large subset of operations including reading/writing files, directories, and symlinks, making it feel like a native file system. Its unique selling point is the ability to mount S3 buckets directly, enabling use of standard file operations and tools without modifying applications, while offering features like multi-part uploads for large files, server-side encryption, and support for multiple authentication methods.

Overview

FUSE-based file system backed by Amazon S3

Use Cases

Best For

  • Mounting Amazon S3 buckets as local directories for seamless file access and management on Linux, macOS, or FreeBSD systems.
  • Integrating S3 storage with legacy applications that rely on standard file system APIs without code changes.
  • Performing data backups or migrations to/from S3 using familiar command-line tools like cp, rsync, or tar.
  • Accessing S3-compatible object stores from other providers (e.g., Backblaze B2, Microsoft Azure) through a unified file system interface.
  • Enabling random writes, appends, and renames to files in S3 via server-side copy and multi-part upload optimizations.
  • Setting up cloud storage for development or testing environments where local file system semantics are required for compatibility.

Not Ideal For

  • High-performance applications requiring low-latency file access, due to network overhead and poor metadata operation performance.
  • Multi-client environments needing coordinated, concurrent access to the same bucket, as s3fs lacks built-in locking or consistency mechanisms.
  • Use cases demanding atomic file operations like renames, which are not supported and can lead to data inconsistency.
  • Real-time data synchronization where external changes must be immediately detected, since inotify only covers local modifications.

Pros & Cons

Pros

Broad POSIX Compatibility

Supports a large subset of POSIX operations including reading/writing files, directories, symlinks, and extended attributes, making S3 buckets feel like native file systems without modifying applications.

Cross-Provider Flexibility

Compatible not only with Amazon S3 but also with various S3-based object stores from other providers, as noted in the wiki, allowing seamless use with platforms like Backblaze B2 or Microsoft Azure.

Advanced S3 Feature Support

Enables random writes, appends, and renames via server-side copy with multi-part upload for large files, leveraging S3's capabilities while maintaining file system semantics.

Performance Optimizations

Includes in-memory metadata caching and local disk data caching, which help mitigate network latency and improve efficiency for repeated file accesses, as highlighted in the features.

Cons

Metadata Performance Bottleneck

Directory listings and other metadata operations have poor performance due to network latency, a limitation explicitly admitted in the README, making it sluggish for frequent file system scans.

Consistency and Coordination Issues

No support for atomic renames or coordination between multiple clients mounting the same bucket, and non-AWS providers may have eventual consistency, leading to potential stale data reads.

Limited Real-Time Updates

Inotify only detects local modifications, not external changes by other clients or tools like AWS CLI, making it unsuitable for scenarios requiring immediate synchronization across systems.

Frequently Asked Questions

Quick Stats

Stars9,818
Forks1,075
Contributors0
Open Issues300
Last commit5 days ago
CreatedSince 2013

Tags

#filesystem#amazon-s3#object-storage#posix#cloud-storage#fuse-filesystem#s3#aws-s3#linux#file-system#fuse#macos#freebsd

Built With

F
FUSE
C
C++

Included in

Amazon Web Services14.0k
Auto-fetched 1 day ago

Related Projects

miniominio

MinIO is a high-performance, S3 compatible object store, open sourced under GNU AGPLv3 license.

Stars60,772
Forks7,406
Last commit2 months ago
rclonerclone

"rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files

Stars56,802
Forks5,054
Last commit2 days ago
filestashfilestash

:file_folder: File Management Platform / Universal Data Access Layer (without FUSE)

Stars14,093
Forks976
Last commit2 days ago
goofysgoofys

a high-performance, POSIX-ish Amazon S3 file system written in Go

Stars5,533
Forks531
Last commit1 year ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub