• Amazon EFS is a simple, serverless, elastic, set-and-forget file system that automatically grows and shrinks as you add and removes files without needing management or provisioning.
• You can use Amazon EFS with Amazon EC2, AWS Lambda, Amazon ECS, Amazon EKS, and other AWS compute instances or with on-premises servers.

• Amazon Elastic File System (Amazon EFS) provides serverless, fully elastic file storage to share files without provisioning or managing storage capacity and performance.
• Amazon EFS is built to scale on demand to petabytes without disrupting applications, growing and shrinking automatically as you add and remove files.
• Because Amazon EFS has a simple web services interface, you can create and configure file systems quickly and easily.
• The service manages all the file storage infrastructure for you, meaning that you can avoid the complexity of deploying, patching, and maintaining complex file system configurations.
• Amazon EFS supports the Network File System version 4 (NFSv4.1 and NFSv4.0) protocol, so the applications and tools you use today work seamlessly with Amazon EFS.
• Multiple compute instances, including Amazon EC2, Amazon ECS, and AWS Lambda, can access an Amazon EFS file system at the same time.
• Therefore, an EFS file system can provide a shared data source for workloads and applications running on multiple compute instances or servers.
• With Amazon EFS, you pay only for the storage used by your file system, and there is no minimum fee or setup cost. Amazon EFS offers the following storage class options for different use cases:
  • Standard storage classes (Recommended): EFS Standard and EFS Standard–Infrequent Access (Standard–IA) offer Multi-AZ resilience and the highest levels of durability and availability.
  • One Zone storage classes: EFS One Zone and EFS One Zone–Infrequent Access (EFS One Zone–IA), which offer you the choice of additional savings by choosing to save your data in a single Availability Zone.
• Amazon EFS provides the throughput, IOPS, and low latency needed for a broad range of workloads.
  • We recommend using the default performance and throughput file system settings for most workloads.
• The default General Purpose performance mode is ideal for latency-sensitive applications, like web-serving environments, content management systems, home directories, and general file serving.
• The default Elastic Throughput mode is designed to automatically scale throughput performance up or down to meet the needs of your workload activity.
• Alternatively, if you know the specific access patterns for your workloads (including throughput, latency, and storage needs), you can choose different performance and throughput modes.
• The Max I/O performance mode can scale to higher aggregate throughput and operations per second. However, these file systems have higher latencies for file system operations.
• With Provisioned Throughput mode, you specify a level of throughput that the file system can drive independent of the file system's size or burst credit balance.
• The Bursting Throughput mode provides throughput that scales with the amount of storage in your file system and supports bursting to higher levels for up to 12 hours per day.
• The service is designed to be highly scalable, highly available, and highly durable.
  • Amazon EFS file systems using Standard storage classes store data and metadata across multiple Availability Zones in an AWS Region.
  • EFS file systems can grow to petabyte scale, drive high throughput levels, and allow massively parallel access from compute instances to your data.