Microsoft Azure → Amazon Web Services
AWS equivalent of NFS 3.0 protocol support for Blob Storage
The closest AWS equivalents of NFS 3.0 protocol support for Blob Storage are Amazon S3 Files and Mountpoint for Amazon S3.
About NFS 3.0 protocol support for Blob Storage
| Provider | Microsoft Azure |
|---|---|
| Status | Generally available |
| What it is | Mount a Blob container over NFS 3.0 from Linux clients in Azure or on premises (over a private network). Requires the hierarchical namespace and suits large, sequential, read-heavy workloads. |
| Documentation | learn.microsoft.com |
| Pricing | Official pricing page |
AWS mappings (1)
| Capability | AWS equivalent | Match |
|---|---|---|
| Mount object storage as a file system | Amazon S3 Files, Mountpoint for Amazon S3 | Partial match |
Object access, file access & analytics(1)
Mount object storage as a file system Partial match
Amazon S3 Files (a managed shared file system over a bucket) and Mountpoint for Amazon S3 map to NFS 3.0 support for Blob Storage and BlobFuse2. Azure has no managed file-system layer over Blob comparable to S3 Files.
- Semantics. S3 Files provides full file-system semantics with a managed high-performance layer and two-way sync to the bucket. Mountpoint, BlobFuse2, and NFS 3.0 on Blob are thinner layers that aren't fully POSIX (for example, renames aren't atomic in BlobFuse2).
- Where it mounts. S3 Files mounts on EC2, Lambda, EKS, and ECS. NFS 3.0 on Blob mounts from Linux clients in Azure or on premises over a private network. BlobFuse2 and Mountpoint are client-side FUSE drivers on Linux.
- Prerequisites. NFS 3.0 on Blob needs the hierarchical namespace. BlobFuse2 works with flat or hierarchical accounts.