S3 Is Not a Filesystem (But Now There’s One In Front of It)

Key Takeaways

• Mount S3 buckets as NFS 4.1/4.2 on multiple AWS compute services
• Hot data stored on high‑performance tier; cold data remains standard S3
• Charges apply per‑GB‑month plus 32 KB‑minimum read/write metering
• First small‑file read incurs $0.06/GB import write cost
• Best for metadata‑heavy, small‑file workloads like ML checkpoints

Pulse Analysis

The introduction of S3 Files marks a strategic shift for AWS, turning the object store into a dual‑purpose data substrate. By leveraging an EFS‑backed layer, the service offers true POSIX semantics while preserving S3’s durability and lifecycle policies. This architecture eliminates the need for third‑party FUSE solutions that suffered from latency and consistency issues, allowing developers to mount buckets with a single command and let the system handle syncs behind the scenes. The result is a seamless bridge between object‑oriented APIs and traditional file‑based applications.

From a cost perspective, S3 Files adopts the same pricing structure as EFS performance‑optimized storage, charging $0.30 per GB‑month for the fast tier and per‑GB access fees for reads and writes. Crucially, only the portion of data that crosses the 128 KB threshold or is actively accessed incurs these charges; the bulk of the bucket remains at standard S3 rates ($0.023 per GB‑month). However, the 32 KB minimum metering and the $0.06/GB import write on first reads of small files can add up for metadata‑intensive workloads, so careful modeling is essential before deployment.

The service’s sweet spot lies in AI/ML pipelines, agentic workloads, and legacy applications that expect a shared POSIX filesystem. Teams can now keep S3 as the source of truth while providing developers with a familiar file‑system interface, reducing the operational overhead of managing separate storage solutions. For workloads dominated by large files, S3 Files offers free reads directly from S3, delivering significant savings over traditional EFS. In short, S3 Files expands the versatility of Amazon S3, making it a practical choice for both object‑centric and file‑centric use cases.