"The core product is solid. I threw ten deliberate conflicts at it - writing to the same key from the NFS mount and the S3 API simultaneously - and S3 won every single one, converging in under two seconds with zero split-brain states."
"It's built on EFS infrastructure, charges the same rates ($0.30/GB storage, $0.03/GB reads, $0.06/GB writes), and the pricing match is deliberate. The trick is that you only pay those rates on the small, hot fraction of data that actually lands on the filesystem."
"The team spent months trying to make the boundary between files and objects invisible before realizing the boundary itself was the right design. Filesystem clients mutating objects every 10 milliseconds? That's normal."
AWS launched S3 Files, enabling users to mount S3 buckets as NFS shares. The product demonstrated strong performance, resolving conflicts quickly and effectively. It operates on EFS infrastructure with competitive pricing, charging for only the actively used data while keeping the rest in S3 at a lower rate. The engineering team focused on maintaining a clear boundary between files and objects, ultimately leading to a more effective design that avoids the pitfalls of previous community drivers.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]