S3 Files: The Missing Piece We All Pretended Wasn’t Missing
AWS just launched S3 Files, a new service that lets you mount an S3 bucket as a real file system across EC2, ECS, EKS, and even Lambda. It’s one of those announcements that lands with a quiet sense of inevitability. Of course S3 should behave like this. Of course teams want direct, file‑system‑style access to the data they already keep in S3. It’s surprising how long we all worked around the gap.
For years, we’ve lived with an awkward divide. Object storage was durable, cheap, and the natural home for almost all data. File systems were interactive, hierarchical, and mutable, but expensive and operationally heavy. Any workload that needed “S3 data, but as files” ended up with a patchwork of solutions that always felt slightly off. Sync jobs, FUSE layers, EFS pipelines, custom wrappers — all workable, none satisfying.
S3 Files finally closes that gap in a way that feels native instead of bolted on.
What AWS Actually Shipped
From the announcement, S3 Files provides:
A proper NFSv4.1+ file system interface backed by S3
Low‑latency access for active data using a high‑performance layer
Direct reads from S3 for large sequential access patterns
Byte‑range reads so you only fetch what you need
Automatic sync back to S3 with versioning semantics
Concurrent access across compute without duplication
IAM and POSIX permissions, CloudWatch metrics, CloudTrail logging
It’s a clean mental model: S3 stays the source of truth, and you get a file‑system view when you need one.
Why This Matters
Every alternative we’ve had until now was always missing something.
EFS gave us a managed file system, but not a native view of S3 data.
FSx gave us specialised file systems, but not the universality of S3.
DIY sync jobs gave us control, but also drift and operational overhead.
FUSE‑based S3 mounts gave us hope, then reminded us why abstraction layers are hard.
S3 Files is the first option that doesn’t feel like a compromise. It’s S3, presented in a way that aligns with how teams actually work.
🔥 Sponsored by QuickTable
QuickTable is the refreshingly simple way for restaurants to take online bookings. No clunky dashboards, no endless setup — just clean, intuitive design that works. It’s built with the same technical principles we celebrate in The Serverless Mindset: simplicity, resilience, and focus on what really matters.
And here’s the best part: friends of this newsletter get a full year free. That’s right,twelve months of effortless booking, on the house. Don’t miss it, use this signup link.
Pricing: Surprisingly Reasonable
The pricing model is straightforward. Reads served directly from S3 don’t incur additional S3 Files charges, which is exactly the behaviour you’d hope for. You pay for:
Data stored in the high‑performance layer
Small file reads and all writes
S3 requests generated during sync
There are caveats, so the pricing page is worth a proper read, but the overall shape feels fair. For many workloads, this will be cheaper and cleaner than maintaining a separate file system layer or duplicating data across services.
The Bigger Picture
This launch removes a friction we’ve all worked around for years.
It tidies up pipelines, reduces the amount of glue code teams end up maintaining, and lets S3 sit more naturally at the centre of both batch and interactive workloads.
It’s the kind of feature that feels obvious once you see it, yet still manages to open up new architectural paths. S3 Files fits neatly into the way people already think about building on AWS, and that’s exactly why it’s going to matter.