AWS S3 vs EFS vs FSx – Storage Service Comparison

AWS S3 vs EFS vs FSx – Storage Service Comparison

📅 Published June 2026: Covers S3 Files (NFS mount for S3), S3 Access Points for FSx, FSx Intelligent-Tiering storage class, EFS Archive storage class, EFS performance enhancements (60 GiB/s, 2.5M IOPS), and updated exam guidance for SAA-C03, SAP-C02, and DEA-C01.

Overview

AWS offers multiple storage services designed for different workloads. Amazon S3 provides object storage accessed via API, Amazon EFS delivers managed NFS file storage, and the Amazon FSx family offers four purpose-built file systems (Lustre, Windows File Server, NetApp ONTAP, and OpenZFS). Choosing the right storage service depends on access patterns, performance requirements, protocol needs, and cost considerations.

Amazon S3 – Object Storage

  • Amazon S3 is a highly durable object storage service with a simple key-value design for storing any amount of data.
  • Accessed via REST API (PUT, GET, DELETE) — not a file system by default.
  • Provides 11 9’s (99.999999999%) durability by replicating data across at least 3 AZs.
  • Offers unlimited storage — stores over 500 trillion objects across hundreds of exabytes (as of 2026).
  • Supports multiple storage classes: Standard, Intelligent-Tiering, Standard-IA, One Zone-IA, Express One Zone, Glacier Instant Retrieval, Glacier Flexible Retrieval, and Glacier Deep Archive.
  • S3 Express One Zone provides single-digit millisecond latency with 10x faster access than S3 Standard.
  • 🆕 S3 Files (April 2026) — enables mounting S3 buckets as NFS v4.2 file systems on EC2, Lambda, EKS, and ECS with ~1ms latency and POSIX semantics.
  • 🆕 S3 Access Points for FSx — allows accessing FSx for NetApp ONTAP and FSx for OpenZFS data via the S3 API without copying data.
  • Best for: data lakes, backups, static website hosting, archive, big data analytics, content distribution.

Amazon EFS – Elastic File System

  • Amazon EFS is a fully managed, elastic NFS file system for Linux-based workloads.
  • Accessed via NFS v4.0/v4.1 protocol — mount as a standard file system on EC2, ECS, EKS, Lambda, and on-premises servers.
  • Provides Regional (Multi-AZ) durability by replicating data across multiple AZs, or One Zone for lower-cost single-AZ storage.
  • Elastic scaling — grows and shrinks automatically with no provisioning required. Pay only for storage used.
  • Supports up to 60 GiB/s read throughput, 2.5 million read IOPS, and 500,000 write IOPS (2024 enhancements).
  • Three storage classes: EFS Standard ($0.30/GB-month, sub-ms latency), EFS Infrequent Access ($0.016/GB-month), and EFS Archive ($0.008/GB-month — up to 97% lower than Standard).
  • Supports Lifecycle Management to automatically tier data between Standard, IA, and Archive based on access patterns.
  • Supports up to 10,000 access points per file system for multi-tenant and containerized applications.
  • Best for: shared home directories, CMS, development environments, containerized applications, machine learning training data.

Amazon FSx Family

FSx for Lustre

  • Fully managed high-performance parallel file system based on open-source Lustre.
  • Delivers sub-millisecond latency, up to 1,000 GB/s throughput, and millions of IOPS.
  • Uses a custom POSIX-compliant protocol optimized for performance (Linux clients only).
  • Native S3 integration via Data Repository Associations (DRA) — automatically imports/exports data between FSx and S3.
  • Deployment types: Persistent (long-term storage with data replicated within AZ) and Scratch (temporary high-burst workloads, no replication).
  • Storage options: SSD, HDD, and Intelligent-Tiering (elastic, starting at $0.004/GB-month for Archive tier).
  • Best for: HPC, machine learning training, financial modeling, genomics, video rendering, EDA.

FSx for Windows File Server

  • Fully managed Windows-native file system built on Windows Server with full SMB protocol support.
  • Accessed via SMB 2.0/2.1/3.0/3.1.1 protocol — supports Windows, Linux, and macOS clients.
  • Integrates with Microsoft Active Directory for authentication and Windows ACLs for access control.
  • Supports Multi-AZ deployment for 99.99% availability with automatic failover.
  • Up to 20 GB/s throughput and hundreds of thousands of IOPS per file system.
  • Maximum file system size: 64 TiB.
  • Supports DFS Namespaces, DFS Replication, shadow copies, user quotas, and data deduplication.
  • Best for: Windows application workloads, home directories, .NET applications, SQL Server, SharePoint, IIS.

FSx for NetApp ONTAP

  • Fully managed NetApp ONTAP file system providing enterprise-grade multi-protocol storage.
  • Supports NFS, SMB, and iSCSI protocols simultaneously — the only FSx option with block storage (iSCSI).
  • Up to 72-80 GB/s throughput and millions of IOPS with virtually unlimited storage (tens of PBs).
  • Automatic storage tiering moves cold data to lower-cost capacity pool storage.
  • Supports Multi-AZ deployment (99.99% SLA), snapshots, cloning, SnapMirror replication, and FlexCache.
  • Integrates with Active Directory for SMB access and supports NFS ACLs.
  • 🆕 S3 Access Points (2025) — access file data stored in ONTAP volumes via the S3 API for AI/analytics workloads without data movement.
  • Best for: enterprise NAS migration, multi-protocol workloads, Oracle/SAP, DevOps (cloning), hybrid cloud.

FSx for OpenZFS

  • Fully managed OpenZFS file system optimized for low-latency workloads.
  • Accessed via NFS v3/v4.0/v4.1/v4.2 — supports Linux, Windows, and macOS clients.
  • Delivers sub-0.5ms latency, up to 21 GB/s throughput (cached) / 10 GB/s (disk), and up to 2 million IOPS.
  • Maximum file system size: 512 TiB.
  • Supports instant snapshots, data cloning (space-efficient copies), and point-in-time recovery.
  • Supports Multi-AZ deployment (99.99% SLA) and Single-AZ (99.5% SLA).
  • 🆕 S3 Access Points (June 2025) — access OpenZFS file data via S3 API.
  • Best for: development/test (fast cloning), Linux workloads migrating from on-premises ZFS, databases, CI/CD pipelines.

Access Patterns Comparison

Service Access Method Protocol Client OS
S3 REST API (HTTP/HTTPS), S3 Files NFS mount HTTPS, NFS v4.2 (S3 Files) Any (API); Linux (NFS mount)
EFS Mount as file system NFS v4.0, v4.1 Linux, macOS
FSx for Lustre Mount as file system Lustre (POSIX-compliant custom) Linux only
FSx for Windows Map network drive / mount SMB 2.0/2.1/3.0/3.1.1 Windows, Linux, macOS
FSx for NetApp ONTAP Mount / map drive / iSCSI block NFS v3/v4.x, SMB, iSCSI, S3 API Windows, Linux, macOS
FSx for OpenZFS Mount as file system NFS v3/v4.0/v4.1/v4.2, S3 API Windows, Linux, macOS

Performance Tiers Comparison

Service Latency Max Throughput Max IOPS Max Storage
S3 Single-digit ms (Standard); <10ms (Express One Zone) Virtually unlimited (per-prefix: 5,500 GET/s) 3,500 PUT/s per prefix Unlimited
EFS Sub-millisecond (Standard) 60 GiB/s (read) 2.5 million (read), 500K (write) Unlimited (elastic)
FSx for Lustre Sub-millisecond 1,000 GB/s Millions Multiple PBs
FSx for Windows <1 ms 12-20 GB/s Hundreds of thousands 64 TiB
FSx for NetApp ONTAP <1 ms 72-80 GB/s Millions Virtually unlimited (tens of PBs)
FSx for OpenZFS <0.5 ms 10-21 GB/s 1-2 million 512 TiB

Pricing Model Comparison

Service Pricing Model Storage Cost (US East) Additional Charges
S3 Standard Pay per GB stored + requests + data transfer $0.023/GB-month GET: $0.0004/1K req; PUT: $0.005/1K req; data out
S3 Glacier Deep Archive Pay per GB stored + requests + retrieval $0.00099/GB-month Retrieval fees; 12-48 hour restore time
EFS Standard Pay per GB stored (elastic); optional throughput provisioning $0.30/GB-month IA reads: $0.03/GB; Provisioned throughput extra
EFS Archive Pay per GB stored + access fees $0.008/GB-month Access charges for reads/writes
FSx for Lustre (SSD) Pay per GB provisioned $0.140/GB-month (scratch); $0.145/GB-month (persistent) Metadata IOPS; backups: $0.05/GB-month
FSx for Lustre (Intelligent-Tiering) Pay per GB consumed + throughput + requests $0.023 (Frequent); $0.0125 (IA); $0.004 (Archive)/GB-month Throughput: $0.52/MBps-month; read/write request fees
FSx for Windows Pay per GB provisioned + throughput SSD: $0.13/GB-month; HDD: $0.013/GB-month Throughput capacity; backups; data dedup savings
FSx for NetApp ONTAP Pay per GB provisioned (SSD) + capacity pool + throughput SSD: $0.125/GB-month; Capacity pool: $0.0125/GB-month Throughput capacity; IOPS; backup storage
FSx for OpenZFS Pay per GB provisioned + throughput + IOPS SSD: $0.09/GB-month Throughput; additional IOPS; backup storage

Key Pricing Insights:

  • S3 is the cheapest for raw storage ($0.023/GB) but charges per API request — ideal for infrequent access or bulk data.
  • EFS is the most expensive per GB ($0.30) but offers elastic scaling with no provisioning — use Lifecycle policies to move data to IA/Archive for savings.
  • FSx for Lustre Intelligent-Tiering starts at $0.004/GB-month for archive data — lowest-cost managed Lustre option.
  • FSx for NetApp ONTAP automatic tiering to capacity pool ($0.0125/GB) provides significant savings for mixed workloads.
  • FSx for Windows HDD at $0.013/GB-month is cost-effective for large Windows file shares with infrequent access.

Durability and Availability

Service Durability Availability SLA Deployment Options
S3 Standard 99.999999999% (11 9’s) 99.99% Multi-AZ (automatic); One Zone-IA for single AZ
EFS Regional 99.999999999% (11 9’s) 99.99% Regional (Multi-AZ) or One Zone
FSx for Lustre Persistent: data replicated within AZ; Scratch: no replication 99.5% (Single-AZ) Single-AZ only (Persistent or Scratch)
FSx for Windows Data replicated within AZ (Single-AZ) or across AZs (Multi-AZ) Multi-AZ: 99.99%; Single-AZ: 99.5% Single-AZ or Multi-AZ
FSx for NetApp ONTAP Data replicated within/across AZs; SnapMirror for cross-region Multi-AZ: 99.99%; Single-AZ: 99.9% Single-AZ or Multi-AZ
FSx for OpenZFS Data replicated within/across AZs based on deployment Multi-AZ: 99.99%; Single-AZ: 99.5% Single-AZ or Multi-AZ

Encryption

Service Encryption at Rest Encryption in Transit Key Management
S3 Yes — SSE-S3 (default), SSE-KMS, SSE-C, DSSE-KMS Yes — TLS/HTTPS (enforced by default on new buckets) AWS KMS, S3-managed keys, customer-provided keys
EFS Yes — AWS KMS (enabled at creation) Yes — TLS 1.2 via EFS mount helper AWS KMS (aws/elasticfilesystem or custom CMK)
FSx for Lustre Yes — AWS KMS Yes — encryption in transit supported AWS KMS (AWS managed or customer managed)
FSx for Windows Yes — AWS KMS Yes — SMB Kerberos encryption AWS KMS (AWS managed or customer managed)
FSx for NetApp ONTAP Yes — AWS KMS Yes — SMB encryption, NFS Kerberos (krb5p) AWS KMS (AWS managed or customer managed)
FSx for OpenZFS Yes — AWS KMS Yes — encryption in transit supported AWS KMS (AWS managed or customer managed)

Access Control

Service Access Control Mechanisms
S3 IAM policies, bucket policies, S3 Access Points, VPC endpoints, Block Public Access, Object Ownership, ACLs (legacy)
EFS IAM resource policies, VPC security groups, POSIX user/group permissions, Access Points with root directory and UID/GID enforcement
FSx for Lustre VPC security groups, POSIX permissions, IAM for API operations
FSx for Windows Active Directory authentication, Windows NTFS ACLs, IAM for API operations, file access auditing
FSx for NetApp ONTAP Active Directory (SMB), NFS export policies, NTFS/UNIX ACLs, IAM for API operations, anti-virus integration, file access auditing
FSx for OpenZFS VPC security groups, NFS export policies, POSIX permissions, IAM for API operations

Use Cases – When to Use Which

Use Case Recommended Service Why
Data lake / analytics S3 Unlimited scale, lowest cost, native integration with Athena/EMR/Glue/Redshift Spectrum
Shared Linux home directories EFS NFS mount, elastic scaling, POSIX permissions, multi-AZ access
HPC / ML training FSx for Lustre Highest throughput (1,000 GB/s), millions of IOPS, S3 integration for data staging
Windows workloads / .NET apps FSx for Windows Native SMB, Active Directory, NTFS, DFS, Windows-native features
Enterprise NAS migration (multi-protocol) FSx for NetApp ONTAP NFS + SMB + iSCSI simultaneously, auto-tiering, SnapMirror, FlexCache
Dev/test with instant cloning FSx for OpenZFS Instant snapshots, space-efficient clones, lowest latency (<0.5ms)
Backup and archive S3 Glacier Cheapest storage ($0.00099/GB), 11 9’s durability, compliance retention
Container shared storage (EKS/ECS) EFS or FSx for Lustre EFS for general shared; FSx for Lustre for high-throughput ML training
Oracle/SAP databases FSx for NetApp ONTAP iSCSI block storage, snapshots, cloning for test/dev, enterprise features
Static website hosting / CDN origin S3 Native static hosting, CloudFront integration, low cost
Financial modeling / EDA FSx for Lustre Ultra-low latency, parallel I/O, compute-intensive workloads
AI/ML analytics on existing file data FSx for NetApp ONTAP / OpenZFS (with S3 Access Points) Access file data via S3 API for Bedrock, SageMaker, Athena without data movement

EFS vs EBS Multi-Attach

Both EFS and EBS Multi-Attach provide shared storage across multiple EC2 instances, but they are fundamentally different:

Feature Amazon EFS EBS Multi-Attach
Storage Type File storage (NFS) Block storage (raw disk)
Protocol NFS v4.0/v4.1 Block-level (no file system protocol — application must manage)
Max Instances Thousands (concurrent) Up to 16 Nitro-based instances
AZ Scope Multi-AZ (Regional) or One Zone Single AZ only
Volume Types N/A (elastic) io1 and io2 Provisioned IOPS only
Storage Capacity Virtually unlimited (auto-scales to petabytes) Up to 64 TiB per volume (io2 Block Express)
File System Managed (NFS — no setup needed) Requires cluster-aware file system (GFS2, OCFS2) or application-level I/O fencing
Concurrent Read/Write Full POSIX — safe concurrent reads and writes Requires I/O fencing — application must coordinate writes (NVMe Reservations on io2)
Performance Up to 60 GiB/s read, 2.5M IOPS Up to 256K IOPS, sub-ms latency (io2 Block Express)
Typical Use Cases Shared file storage, CMS, home dirs, containers Clustered databases, Oracle RAC, failover clusters requiring lowest latency

Exam Tip: Choose EFS when you need a simple shared file system across multiple instances and AZs. Choose EBS Multi-Attach only for specialized clustered applications (Oracle RAC, clustered databases) that require block-level access with application-managed I/O coordination within a single AZ.

FSx for Lustre with S3 Integration

FSx for Lustre provides native, bi-directional integration with Amazon S3 through Data Repository Associations (DRA):

  • Automatic Import: When a client accesses a file, FSx for Lustre automatically imports the file metadata (and optionally data) from the linked S3 bucket. New/changed objects in S3 are automatically reflected in the file system.
  • Automatic Export: New or modified files in the FSx file system are automatically exported back to the linked S3 bucket, keeping S3 as the durable long-term store.
  • Lazy Loading: Only metadata is loaded initially; actual file data is fetched from S3 on first access (lazy load) or can be preloaded using hsm_restore.
  • Data Tiering: With Intelligent-Tiering storage class, infrequently accessed data is automatically tiered to S3 (IA and Archive tiers) while maintaining file system visibility.
  • Multiple DRAs: A single file system can be linked to multiple S3 buckets/prefixes, enabling consolidated access to distributed datasets.
  • Cross-Account Access: FSx for Lustre can be linked to S3 buckets in different AWS accounts for shared data access.

Architecture Pattern — HPC/ML with S3 Data Lake:

  • Store raw data durably in S3 (lowest cost, 11 9’s durability).
  • Create a FSx for Lustre file system linked to the S3 bucket via DRA.
  • Compute instances mount FSx for Lustre and process data at hundreds of GB/s throughput.
  • Results are automatically exported back to S3.
  • Delete the FSx file system after processing to save costs (scratch deployments).

Exam Tip: When a question mentions HPC or ML workloads that need to process data stored in S3 with high throughput and POSIX file system access, FSx for Lustre with DRA is the answer. FSx for Lustre acts as a high-speed processing layer on top of S3.

Detailed Comparison Table – All Storage Types

Feature S3 EFS FSx for Lustre FSx for Windows FSx for NetApp ONTAP FSx for OpenZFS
Storage Type Object File (NFS) File (Lustre) File (SMB) File + Block (NFS/SMB/iSCSI) File (NFS)
Protocol HTTPS/REST, NFS v4.2 (S3 Files) NFS v4.0/v4.1 Lustre (POSIX) SMB 2.x/3.x NFS, SMB, iSCSI, S3 API NFS v3/v4.x, S3 API
Client OS Any (API); Linux (NFS) Linux, macOS Linux only Windows, Linux, macOS Windows, Linux, macOS Windows, Linux, macOS
Max Throughput Unlimited (parallel) 60 GiB/s 1,000 GB/s 12-20 GB/s 72-80 GB/s 10-21 GB/s
Latency Single-digit ms Sub-ms Sub-ms <1 ms <1 ms <0.5 ms
Max Storage Unlimited Unlimited (elastic) Multiple PBs 64 TiB Tens of PBs 512 TiB
Scaling Automatic (unlimited) Automatic (elastic) Provisioned (IT: elastic) Provisioned; can increase Provisioned + auto-tier Provisioned; can increase
Multi-AZ Yes (default) Yes (Regional) No (Single-AZ only) Yes (option) Yes (option) Yes (option)
Durability 11 9’s 11 9’s (Regional) Replicated within AZ (Persistent) Replicated within/across AZ Replicated within/across AZ Replicated within/across AZ
Availability SLA 99.99% 99.99% 99.5% 99.99% (Multi-AZ) 99.99% (Multi-AZ) 99.99% (Multi-AZ)
S3 Integration Native No (use DataSync) Native DRA (auto import/export) No S3 Access Points (2025) S3 Access Points (2025)
Active Directory No No No Yes (required) Yes (for SMB) No
Snapshots/Cloning Versioning (object-level) No native snapshots Backups only Shadow copies, backups Instant snapshots + cloning Instant snapshots + cloning
Data Deduplication No No No Yes Yes No
Data Compression No (client-side) No Yes (LZ4) Yes Yes Yes (LZ4, ZSTD)
Pricing Model GB stored + requests GB stored (elastic) GB provisioned or consumed GB provisioned + throughput GB provisioned + capacity pool + throughput GB provisioned + throughput + IOPS
Lowest Storage Cost $0.00099/GB (Deep Archive) $0.008/GB (Archive) $0.004/GB (IT Archive) $0.013/GB (HDD) $0.0125/GB (capacity pool) $0.09/GB (SSD)
On-Premises Access Yes (Internet/Direct Connect) Yes (VPN/Direct Connect) Yes (VPN/Direct Connect) Yes (VPN/Direct Connect) Yes (VPN/DX + FlexCache/Global File Cache) Yes (VPN/Direct Connect)

AWS Certification Exam Relevance

  • SAA-C03 (Solutions Architect Associate): Frequently tests storage service selection based on access patterns, performance needs, cost optimization, and durability requirements. Know when to choose S3 vs EFS vs FSx.
  • SAP-C02 (Solutions Architect Professional): Tests complex architectures combining S3 data lakes with FSx for Lustre processing, hybrid storage with ONTAP, and multi-protocol requirements.
  • DEA-C01 (Data Engineer Associate): Tests FSx for Lustre with S3 integration for ETL pipelines, data lake architectures, and high-performance analytics.
  • Key Exam Themes:
    • S3 = object storage, unlimited, cheapest, API access, data lake.
    • EFS = shared NFS file system, elastic, Linux, multi-AZ, POSIX.
    • FSx for Lustre = HPC, ML, highest throughput, S3 integration, Linux only.
    • FSx for Windows = Windows workloads, SMB, Active Directory, NTFS ACLs.
    • FSx for NetApp ONTAP = multi-protocol (NFS+SMB+iSCSI), enterprise NAS, auto-tiering.
    • FSx for OpenZFS = lowest latency, instant clones, dev/test, Linux NFS migration.
    • EBS Multi-Attach ≠ EFS — block vs file, single-AZ vs multi-AZ, requires cluster-aware FS.

AWS Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. A genomics research company stores 500 TB of sequencing data in Amazon S3. Their HPC cluster needs to process this data with sub-millisecond latency and hundreds of GB/s throughput using a POSIX-compliant file system. The processed results must be stored back in S3 for long-term retention. Which solution meets these requirements with MINIMUM operational overhead?
    1. Copy data from S3 to Amazon EFS, process on EC2, copy results back to S3
    2. Create an FSx for Lustre file system with a Data Repository Association linked to the S3 bucket
    3. Mount S3 using S3 Files on the HPC cluster instances
    4. Use AWS DataSync to copy data from S3 to FSx for OpenZFS

    Answer: b. FSx for Lustre provides native S3 integration via Data Repository Associations, delivering sub-ms latency and up to 1,000 GB/s throughput. Data is automatically imported from and exported back to S3 without manual copy operations.

  2. A company is migrating an on-premises Windows file server to AWS. The application requires SMB protocol access, Active Directory authentication, Windows ACLs, DFS Namespaces, and shadow copies for end-user file restore. Which AWS storage service should they use?
    1. Amazon EFS with Windows clients
    2. Amazon S3 with AWS Transfer Family
    3. Amazon FSx for Windows File Server
    4. Amazon FSx for NetApp ONTAP with SMB

    Answer: c. FSx for Windows File Server is purpose-built for Windows workloads with native SMB support, Active Directory integration, NTFS ACLs, DFS Namespaces, DFS Replication, and shadow copies. While FSx for NetApp ONTAP also supports SMB, it doesn’t provide native DFS Namespaces or Windows shadow copies.

  3. A media company needs shared file storage accessible from both Linux-based video rendering instances (using NFS) and Windows-based editing workstations (using SMB) simultaneously. They also need automatic tiering of cold data to lower-cost storage. Which solution provides this capability with a SINGLE file system?
    1. Amazon EFS with SMB gateway
    2. Amazon FSx for Windows File Server with NFS
    3. Amazon S3 with Transfer Family for NFS and SMB
    4. Amazon FSx for NetApp ONTAP

    Answer: d. FSx for NetApp ONTAP is the only AWS file service that supports NFS, SMB, and iSCSI simultaneously on the same file system, with automatic storage tiering that moves cold data to a lower-cost capacity pool.

  4. A development team wants to create multiple test environments by cloning a 10 TB production database file system. They need the clones to be created instantly without consuming additional storage for unchanged data. The file system uses NFS protocol on Linux. Which AWS service provides this capability MOST cost-effectively?
    1. Amazon EFS with AWS Backup restore
    2. Amazon FSx for Lustre with multiple file systems
    3. Amazon FSx for OpenZFS with instant cloning
    4. Amazon EBS snapshots with volume restore

    Answer: c. FSx for OpenZFS supports instant, space-efficient cloning using copy-on-write. Clones are created instantly regardless of data size and consume no additional storage for unchanged data. This is ideal for development/test environments.

  5. A solutions architect needs to choose a storage solution for a containerized application running on Amazon EKS. The application requires shared persistent storage across multiple pods in different Availability Zones, POSIX file permissions, and automatic scaling without capacity planning. Which storage service is MOST appropriate?
    1. Amazon EBS with CSI driver
    2. Amazon S3 with CSI driver
    3. Amazon EFS with EFS CSI driver
    4. Amazon FSx for Lustre with CSI driver

    Answer: c. Amazon EFS provides multi-AZ shared file storage with POSIX permissions and elastic scaling (no capacity planning needed). The EFS CSI driver enables EKS pods to mount EFS as persistent volumes. EBS is single-AZ and cannot be shared across AZs; S3 is not a file system; FSx for Lustre requires capacity provisioning.

  6. A company has a data pipeline where raw data lands in S3, needs high-performance file processing, and the results are used by AI services through the S3 API. They currently copy data between S3 and their file system, creating data duplication. Which AWS feature eliminates this data movement while allowing both file and S3 API access to the SAME data? (Select TWO)
    1. S3 Object Lambda
    2. FSx for Lustre Data Repository Association
    3. AWS DataSync with S3 as destination
    4. S3 Access Points for FSx for NetApp ONTAP
    5. S3 Transfer Acceleration

    Answer: b, d. FSx for Lustre DRA provides automatic bi-directional sync between the file system and S3. S3 Access Points for FSx for NetApp ONTAP allow accessing file data stored in ONTAP volumes directly via the S3 API without copying data, enabling AI/analytics services to work with file data natively.

  7. An organization needs to store compliance data for 7 years with the lowest possible storage cost. The data is written once and rarely accessed (less than once per year). Retrieval time of 12 hours is acceptable. Which storage option provides the LOWEST cost?
    1. Amazon EFS Archive storage class
    2. Amazon S3 Glacier Flexible Retrieval
    3. Amazon S3 Glacier Deep Archive
    4. Amazon FSx for Lustre Intelligent-Tiering Archive tier

    Answer: c. S3 Glacier Deep Archive is the lowest-cost storage in AWS at $0.00099/GB-month (~$1/TB/month) with 12-48 hour retrieval time, specifically designed for data retained 7+ years with rare access. EFS Archive ($0.008/GB) is 8x more expensive.

Related Posts

References

Posted in AWS

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.