April 7, 2026

Buckets, bunnies, and backlash

S3 Files and the changing face of S3

S3 gets a “folder” mode — but commenters smell EFS, old tricks, and a 60‑second lag

TLDR: Amazon’s “S3 Files” aims to make cloud storage feel like a regular folder, reportedly batching changes every minute and leaning on EFS under the hood. Commenters are split: some want the convenience, others call it old news (hello s3fs) and demand clear benefits for massive file counts and real‑world workloads

Amazon’s Andy Warfield just pitched “S3 Files” — the big idea: make the S3 cloud bucket feel like a normal computer folder. The origin story? Genomics labs, “burst” computing, and even a cheeky sunflower joke. But the crowd didn’t come for botany; they came for blood. The top reaction: it “uses EFS under the hood” — Amazon’s shared network drive — and that revelation lit the fuse. The quote about “locking senior engineers in a room” became an instant meme, while the detail that changes batch and sync back to S3 every ~60 seconds made skeptics raise eyebrows.

Fans liked the promise of fewer data copies and easier workflows. Skeptics fired back: this sounds like “eventual consistency” — your edits might take a moment to show up — and they pointed to s3fs, an open tool that’s been doing “mount S3 like a drive” for years. One pragmatist demanded a real pitch: “I’ve got 9 TB and 21 million files — what’s the benefit?” Translation for non‑nerds: S3 is Amazon’s giant online storage, EFS is a shared drive, and this new layer tries to make S3 behave like a familiar folder — with a caching delay and some gotchas. Drama score: high, with equal parts curiosity, side‑eye, and “show me the numbers”

Key Points

  • Andy Warfield introduces S3 Files as a solution to bridge Amazon S3 and filesystem-based workflows.
  • Genomics research at UBC exposed heavy data movement between S3 and local filesystems, causing inefficiency and inconsistency.
  • Workloads were characterized as “burst parallel,” benefiting from cloud elasticity and serverless execution.
  • JS Legare’s “bunnies” system packaged analyses in containers to run on S3, improving speed and repeatability.
  • Despite gains, tools expecting POSIX filesystems created persistent friction, motivating the development of S3 Files.

Hottest takes

"the 'under the hood uses EFS' part is the most interesting bit here" — goekjclo
"Zero mention of s3fs which already did this for decades" — mgaunard
"Sell the benefits… How does this change benefit me?" — CrzyLngPwd
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.