EFS - Elastic File System

Managed NFS (Network file System) that can be mounted on many EC2

 

• - EFS works with instances in mulit -AZ 
• - Highly available ,scalable
• - Expansive (3 * gp2 (EBS) ), pay per use

 

Use cases

• - Content management
• - web serving
• - data sharing
• - Wordpress

 

1. - Uses NFSv4.1 protocol
2. - Uses security group to control access to EFS
3. - Compatible with Linux based AMI (not Windows)
4. - Encryption at rest using KMS
5. - POSIX file system (~ Linux) that has a standard file API
6. - File system sacles automatically pay-per-use, no capacity planning!

 

Performace 

 

EFS Scale

• - 100s councurrent NFS clients, 10 GB+ /s throughput
• - Grow to Petabye-scale NFS automatically

Performace Mode (set at EFS creation time)

• - General Purpose (default) - latency - sensitive use cases ( web server, CMS, etc... )
• - Max I/O - higher latency, throughput, highly parellel ( big data, media processing )

Throughput Mode

• - bursting - 1TB = 50Mib/s + burst of up 100 Mib/s
• - provisioned - set your throughput regardless of storage size, ex 1GiB/s for 1 TB storage
• - Elatic - automatcally scales throughput up or down based on your workloads. (Up to 3Gib for read and 1Gib for write) - used for unpredictable workloads.

Storeage Classes

• - Storage Teirs ( lifecycle management feature - move file after N days ) 
  • standard : for frequently accessed files
  • Infrequent access (EFS-IA) : cost to retrieve files, lower price to store
  • Archive: rarely accessed data (few times each year), 50% cheaper
  • Implement lifecycle policies to move files between storage teirs
• - Availiability and durability
  • standard : Multi-AZ, great for prod
  • One Zone : One Az, great for dev, backup, enabled by default, compatible with IA (EFS One Zone-IA)
• - Over 90% in cost savings