Skip to content
intermediate Phase 4 · Storage Services

EFS and FSx File Storage

Deploy elastic file systems for shared access across EC2 instances. Compare EFS, FSx for Windows, and FSx for Lustre use cases.

45m
0 problems
Topic Progress 0%

EFS Performance and Throughput Modes

Amazon EFS provides NFS file systems that can be mounted simultaneously by thousands of EC2 instances across multiple AZs. EFS is elastic—grows and shrinks automatically with usage.

Performance modes: General Purpose (default) for most workloads—low latency per operation. Max I/O for highly parallelized applications (big data, media processing) with higher throughput but slightly higher latency.

Throughput modes: Bursting scales with storage size—baseline 100 MB/s, bursting to 3 GB/s for large volumes. Provisioned for steady-state high throughput regardless of size—specify MB/s directly. Elastic automatically scales throughput with storage, ideal for workloads with changing patterns.

EFS supports up to 7,000 throughput operations per second. Monitor performance with CloudWatch metrics: BurstCreditBalance, PercentIOLimit, MeteredIOBytes.

Access Points, Mount Targets, and Encryption

Access Points simplify managing EFS for applications—create named entry points with POSIX user/group IDs and root directories. Different applications can use different access points with different permissions on the same file system.

Mount Targets are network interfaces in each AZ—EC2 instances connect through the mount target in their AZ. Create mount targets in each AZ for high availability. Mount targets use NFSv4.1—configure security groups to allow NFS traffic (port 2049).

Encryption at rest uses AWS KMS to encrypt data stored on EFS. Enable during file system creation—cannot be disabled after. Encryption in transit uses TLS for NFS connections—configure mount options with tls transport.

EFS Standard stores data across multiple AZs for high availability. EFS One Zone stores in a single AZ at lower cost—suitable for dev/test or non-critical data that can tolerate AZ failure.

FSx for Windows, Lustre, and NetApp ONTAP

FSx for Windows File Server provides fully managed SMB file shares—native Active Directory integration, DFS namespace support, and Windows ACLs. Ideal for lift-and-shift Windows workloads, .NET applications, and enterprise file shares.

FSx for Lustre is high-performance parallel file system for compute-intensive workloads—machine learning training, HPC, video rendering. Integrates with S3 as a data lake cache. Scales to hundreds of GB/s throughput and millions of IOPS.

FSx for NetApp ONTAP provides enterprise storage features—snapshots, cloning, replication, data tiering. Supports NFS, SMB, and iSCSI protocols. Good for databases, VMware migration, and applications needing enterprise storage features.

FSx for OpenZFS offers ZFS-compatible file systems with snapshots, compression, and data deduplication. Cost-effective for existing ZFS workloads moving to the cloud.

EFS Use Cases and Best Practices

Web serving and content management: EFS provides shared storage for web servers across multiple AZs—CMS files, WordPress content, media assets. Mount EFS on all web servers for consistent content.

Container storage: ECS and EKS use EFS for persistent container storage—shared configuration, logs, and application data. EFS CSI driver integrates with Kubernetes.

Development tools: Shared source code repositories, build artifacts, and IDE workspaces. Multiple developers access the same file system through different instances.

Best practices: Use access points for application isolation. Enable lifecycle policies to transition infrequently accessed files to EFS IA (60% cheaper). Monitor with StorageBytes and StorageBytesStandard metrics. Use VPC endpoints for private access without internet gateway.

Cost optimization: EFS IA automatically stores infrequently accessed files at lower cost. Configure lifecycle policies to move files after 30-90 days of inaccessibility.

Quiz

1. When should you use EFS Max I/O performance mode?

Question 1 options

2. What is the main advantage of FSx for Lustre over EFS?

Question 2 options

3. What is EFS One Zone?

Question 3 options

Flashcards

Question

What is Amazon EFS?

Answer

A fully managed NFS file system that can be mounted by thousands of EC2 instances across multiple AZs simultaneously.

Question

What is the difference between EFS Standard and One Zone?

Answer

Standard stores across multiple AZs for high availability. One Zone stores in a single AZ for lower cost—suitable for non-critical data.

Question

What is FSx for Lustre used for?

Answer

High-performance parallel file system for compute-intensive workloads like ML training, HPC, and video rendering. Integrates with S3.

Question

What is an EFS Access Point?

Answer

A named entry point with POSIX user/group IDs and root directory for application-specific access to an EFS file system.

Revision Notes

Key Takeaways

  • 1. EFS = NFS, elastic, multi-AZ file storage; use access points for application isolation
  • 2. Performance modes: General Purpose (low latency) vs Max I/O (high parallelism)
  • 3. Throughput: Bursting (scales with size), Provisioned (fixed), Elastic (auto-scale)
  • 4. FSx options: Windows (SMB), Lustre (HPC/ML), NetApp ONTAP (enterprise), OpenZFS

Interview Tips

  • Explain when to use EFS vs EBS vs S3 for different storage needs
  • Know the difference between performance modes and when to choose each
  • Discuss EFS lifecycle policies for cost optimization
  • Compare FSx offerings: Windows for SMB, Lustre for HPC, ONTAP for enterprise

Cheat Sheet

EFS: managed NFS, elastic, multi-AZ. Modes: General Purpose (low latency) vs Max I/O (parallel). Throughput: Bursting (size-based), Provisioned (fixed), Elastic (auto). Config: access points (app isolation), mount targets (AZ network). Encryption: KMS at rest, TLS in transit. EFS One Zone: single AZ, cheaper. FSx: Windows (SMB/AD), Lustre (HPC/ML, S3 integration), NetApp ONTAP (enterprise features), OpenZFS (ZFS compat).