AWS S3 Files: Why It's a Bigger Deal Than People Think
Summary
AWS just shipped S3 Files — and most people are sleeping on it. The short version: you can now mount any S3 bucket like a regular file system. ~1ms latency on cached data, the same bucket reachable through both the S3 API and POSIX, already live in 34 regions.
About this video
AWS just shipped S3 Files — and most people are sleeping on it. The short version: you can now mount any S3 bucket like a regular file system. ~1ms latency on cached data, the same bucket reachable through both the S3 API and POSIX, already live in 34 regions. Why does it matter? Most tooling — data science notebooks, build systems, log processors, even the bash scripts you wrote five years ago — expects a normal file system. Until now you'd copy data out of S3 onto EFS or a local disk, run your job, and copy it back. S3 Files just deletes that step. One nice side effect: agents get easier. A coding agent already knows ls, cat, and grep — point it at a mount path and it just works. The bigger thing is the pattern. Object storage stays the source of truth, a faster layer sits on top as cache. We use the same shape at Mixpeek for vectors — S3 Vectors underneath, Qdrant on top, retrieval pipeline above that. mixpeek.com #AWS #S3 #CloudComputing #AIInfrastructure #DataEngineering #ObjectStorage #Mixpeek