Amazon EBS CSI Driver Architecture

Amazon EBS CSI Driver Architecture An architecture diagram generated by Archify. Pod 1 · Node 1 · Amazon EKS cluster Pod 1 Node 1 EBS CSI driver · Node 1 DaemonSet · Amazon EKS cluster EBS CSI driver Node 1 DaemonSet EBS volume 1 · gp3 · single AZ · Architecture component EBS volume 1 gp3 · single AZ Pod 2 · Node 2 · Amazon EKS cluster Pod 2 Node 2 EBS CSI driver · Node 2 DaemonSet · Amazon EKS cluster EBS CSI driver Node 2 DaemonSet EBS volume 2 · gp3 · single AZ · Architecture component EBS volume 2 gp3 · single AZ Mounts volume AttachVolume Mounts volume AttachVolume Amazon EKS cluster Legend Frontend Backend Database

Volume types

  • • gp3 starts at 3,000 IOPS and 125 MiB/s, tunable regardless of size
  • • io1 and io2 target transactional workloads needing hundreds of thousands of IOPS
  • • st1 and sc1 are low-cost HDD options for sequential throughput

StorageClass configuration

  • • Default to provisioner: ebs.csi.aws.com, type: gp3, encrypted: "true"
  • • volumeBindingMode: WaitForFirstConsumer creates the volume in the AZ where the pod lands
  • • Setting allowVolumeExpansion: true keeps online expansion available later

Best practices

  • • An EBS volume is a single-AZ resource, so a pod moved to another AZ cannot mount it
  • • Give the driver a least-privilege IAM role through IRSA or Pod Identity
  • • Back up with snapshots and rehearse recovery through CSI VolumeSnapshot