Amazon S3 Files: making S3 buckets accessible as file systems
AWS just launched S3 Files, a feature that turns S3 buckets into fully accessible file systems for compute resources. If you’ve ever dealt with the friction of copying data between S3 and file-based applications, this is the kind of update that changes your workflow fundamentally. S3 Files delivers a shared file system interface on top of S3, combining the scalability, durability, and cost-effectiveness of object storage with the semantics applications expect from a traditional file system.
The technical approach is straightforward but powerful. S3 Files lets thousands of AWS compute instances connect simultaneously to the same S3 bucket through standard file system operations—reads, writes, directory listings—without requiring any data migration or duplication. The system uses intelligent caching to deliver multiple terabytes per second of aggregate read throughput with low-latency file operations. Your existing S3 data becomes immediately accessible through file system protocols, and new data written through the file interface lands directly in S3. No ETL pipelines, no sync jobs, no copies sitting in EBS volumes eating into your budget.
Where this gets interesting is for workloads that have traditionally required both object storage and file storage. Think machine learning training pipelines that need to read massive datasets, media processing workflows that operate on files but store results in S3, or analytics platforms where multiple compute nodes need shared access to the same data. Previously, you’d either use EFS (more expensive per GB), FSx (additional infrastructure to manage), or build custom sync logic between S3 and local storage. S3 Files eliminates that tradeoff entirely—you get file system access at S3 economics.
The feature is currently available across 34 AWS regions, which means broad coverage for most production workloads. If you’re running compute-intensive applications that interact with large S3 datasets, this is worth evaluating immediately. The pricing model follows S3 conventions, so there’s no separate file system infrastructure cost to worry about. For teams already deep in the S3 ecosystem, this feels less like a new service and more like S3 finally becoming the universal storage layer AWS has been building toward.