Day 17: EFS – Elastic File System πŸŒπŸ“

Day 17: EFS – Elastic File System πŸŒπŸ“

Amazon EFS - A Glimpse into Elastic File Harmony πŸš€πŸ”

1. EFS Essentials πŸŒπŸ”„

  • NFS Marvel:

    • Managed NFS (Network File System) compatible with multiple EC2 instances.

    • Multitude of EC2 instances across multi-AZ for enhanced availability.

    • Offers high availability, scalability, with costs 3x that of gp2 (EBS).

2. Architectural View πŸ°πŸš€

  • Multi-AZ Ecosystem:

    • Presence across us-east-1a, us-east-1b, us-east-1c.

    • EC2 instances harmoniously interacting with EFS.

Navigating EFS Use Cases and Protocol πŸš€πŸŽ­

1. Versatility in Use Cases πŸŒπŸ’‘

  • Adaptable Scenarios:

    • Optimal for content management, web serving, data sharing, and WordPress.
  • Protocol Harmony:

    • Leveraging NFSv4.1 protocol.

    • Integration with security groups for EFS access control.

2. Key Features and Characteristics πŸŒŸπŸ”

  • Linux Compatibility:

    • Primarily compatible with Linux-based AMIs (Not Windows).

    • Data encryption at rest fortified by KMS.

    • Adheres to POSIX file system standards.

    • Dynamic scalability, pay-per-use, eliminating the need for capacity planning.

EFS Performance Unveiled πŸš€πŸ“ˆ

1. Performance Dynamics πŸ”„πŸš€

  • Scaling Horizons:

    • Accommodates thousands of concurrent NFS clients.

    • Achieves throughput exceeding 10 GB/s.

  • Performance Modes:

    • General Purpose:

      • Suited for latency-sensitive tasks like web servers and CMS.
    • Max I/O:

      • Catering to high-latency, high-throughput, and parallel workloads.
  • Throughput Modes:

    • Bursting:

      • 1 TB provides 50 MiB/s with bursts up to 100 MiB/s.
    • Provisioned:

      • Settable throughput, irrespective of storage size (e.g., 1 GiB/s for 1 TB).
    • Elastic:

      • Auto-scales throughput based on workload demands, reaching up to 3 GiB/s for reads and 1 GiB/s for writes.

EFS Storage Classes - Architecting Efficiency πŸš€πŸ—ƒοΈ

1. Storage Class Spectrum πŸŒˆπŸ—„οΈ

  • Lifecycles at Play:

    • Storage tiers governed by lifecycle management (file movement after N days).
  • Standard vs. Infrequent Access (IA):

    • Standard:

      • Tailored for frequently accessed files.
    • Infrequent Access (IA):

      • Cost-efficient for storing with lower retrieval costs.

      • Activate EFS-IA via Lifecycle Policy.

EFS vs. EBS - A Comparative Odyssey πŸ”„πŸ”

1. Elastic Block Storage (EBS) Insights πŸ“ŠπŸ’½

  • EBS Volumes:

    • Exclusive attachment to one instance (excluding multi-attach io1/io2).

    • Locked at the Availability Zone (AZ) level.

    • gp2: IO scales with disk size; gp3 & io1 can independently increase IO.

  • AZ Migration Tactics:

    • To migrate EBS across AZs: Snapshot creation followed by restoration.
  • EBS vs. EFS Dynamics:

    • EBS for single-instance scenarios; EFS for multi-instance ecosystems.

    • EFS tailored for Linux instances leveraging NFS.

    • EFS boasts higher pricing, alleviated by EFS-IA for cost efficiency.

πŸ“š Elevate your understanding: EFS vs. EBS vs. Instance Storeβ€”where each piece fits in the AWS puzzle. Explore the file system intricacies, and architect your storage strategy with wisdom. πŸš€πŸ”—

Did you find this article valuable?

Support Prasad Suman Mohan by becoming a sponsor. Any amount is appreciated!

Β