Microsoft Azure → Amazon Web Services
AWS equivalent of Azure Data Lake Storage (hierarchical namespace)
The closest AWS equivalent of Azure Data Lake Storage (hierarchical namespace) is Amazon S3.
About Azure Data Lake Storage (hierarchical namespace)
| Provider | Microsoft Azure |
|---|---|
| Status | Generally available |
| What it is | Not a separate service. It's Blob Storage with the hierarchical namespace turned on, adding real directories, atomic renames, POSIX-style ACLs, and the Hadoop ABFS driver. It's also required for SFTP and NFS 3.0 on Blob. |
| Documentation | learn.microsoft.com |
| Pricing | Official pricing page |
AWS mappings (1)
| Capability | AWS equivalent | Match |
|---|---|---|
| Data lake storage with real directories | Amazon S3 | Partial match |
Object access, file access & analytics(1)
Data lake storage with real directories Partial match
On AWS, data lakes are built directly on S3 general purpose buckets. On Azure, you turn on the hierarchical namespace for a storage account to get Azure Data Lake Storage, which adds real directories, atomic renames, and POSIX-style ACLs.
- Namespace. S3 general purpose buckets are flat, and folders are key prefixes, so "renaming" a folder copies every object. ADLS directories are real, with atomic rename and delete. (S3 directory buckets do have a hierarchical namespace, but only for Express One Zone.)
- Permissions. ADLS supports POSIX-like ACLs on directories and files as well as RBAC. On AWS, fine-grained data lake permissions usually come from Lake Formation or S3 Access Grants.
- Feature trade-offs. The hierarchical namespace is required for SFTP and NFS 3.0 on Blob, but some Blob features have limits on ADLS accounts. Check the feature support matrix before enabling it.