Architecture Layers That S3 Files Eliminates — and Creates

On April 7, 2026, AWS made Amazon S3 Files generally available. It lets you mount S3 buckets as NFS v4.1/v4.2 file systems from EC2, EKS, ECS, and Lambda. Launching S3 Files, making S3 buckets accessible as file systems | AWS News Blog aws.amazon.com There are already plenty of setup guides and first-look posts. This article focuses on something different: what becomes unnecessary and what becomes possible in your architecture. If you use S3 regularly and are wondering "this sounds big, but how does it actually affect my architecture?" — this is for you. The Problem S3 Files Is Solving Let's start with a shared understanding. Say an ML team needs to preprocess training data. The raw data is in S3. They want to use pandas. While pd.read_csv("s3://my-bucket/data.csv") works, under the hood boto3 issues GET requests and loads data into memory. Writing results back requires PUT. This is fundamentally different from open("./data.csv") . At scale, this becomes an architectural problem. Many