liveBook · Manning

EFS storage

As explained in Effective Platform Engineering

Amazon EFS is a managed, elastic file storage service that provides shared, scalable file systems for compute workloads.

EFS storage provides a managed, operationally resilient file system for Kubernetes workloads. Unlike EBS volumes, it is less directly tied to node groups, supports writes from multiple pods, and provides automated backups. section 7.4.6

Validate an EFS storage class by:

  • Checking that each pod can read data written by the other, then deleting test resources. section 7.4.6

Shared-write health test

Run app1 and app2 against the same EFS claim. Each app appends UTC timestamps to a different file; Bats then verifies that app1 reads app2's file and app2 reads app1's file.

How Effective Platform Engineering covers it

How deep it goes
Explains operational differences and exercises provisioning, mounting, cross-pod writes, and cleanup without detailing EFS internals.
Examples
Uses a ReadWriteMany claim, two BusyBox pods, shared files, UTC timestamps, and Bats assertions for cross-pod access.
What it assumes
Assumes familiarity with EKS, Kubernetes pods, PersistentVolumeClaims, PersistentVolumes, StorageClasses, and Bats tests.
What you can do after
Diagnose storage-class health by verifying shared mounts and cross-pod read/write behavior in an EKS cluster.
How it connects
Connects EFS storage with EBS volumes, Kubernetes PersistentVolumeClaims, StorageClasses, pods, node groups, and the EFS CSI driver.

Also explained in

Compare how 2 books explain EFS storage →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.