Which solution will meet these requirements with the LEAST operational overhead?
Create Amazon Elastic Block Store (Amazon EBS) volumes in the same Availability Zones where EKS worker nodes are placed. Register the volumes in a StorageClass object on an EKS cluster. Use EBS Multi-Attach to share the data between containers.
Create an Amazon Elastic File System (Amazon EFS) file system. Register the file system in a StorageClass object on an EKS cluster. Use the same file system for all containers.
Create an Amazon Elastic Block Store (Amazon EBS) volume. Register the volume in a StorageClass object on an EKS cluster. Use the same volume for all containers.
Create Amazon Elastic File System (Amazon EFS) file systems in the same Availability Zones where EKS worker nodes are placed. Register the file systems in a StorageClass object on an EKS cluster. Create an AWS Lambda function to synchronize the data between file systems.
Explanations:
Amazon EBS volumes cannot be shared among multiple containers unless using EBS Multi-Attach, which is limited to specific workloads. It also adds complexity for managing multiple volumes and does not inherently provide fault tolerance across Availability Zones.
Amazon EFS provides a fully managed, scalable file storage solution that is accessible from multiple containers simultaneously. It is designed for high availability and fault tolerance, making it ideal for shared storage needs in an EKS cluster with minimal operational overhead.
A single Amazon EBS volume cannot be shared across multiple containers. EBS is designed for single-instance attachment, which limits its use for applications requiring shared access. Additionally, EBS does not provide inherent fault tolerance across Availability Zones.
Creating multiple EFS file systems does not simplify management or reduce operational overhead. Synchronizing data between file systems using an AWS Lambda function introduces additional complexity and potential points of failure, while EFS alone provides the necessary sharing and fault tolerance without needing separate file systems.
I measure that the answer is:
Create an Amazon Elastic File System (Amazon EFS) file system. Register the file system in a StorageClass object on an EKS cluster. Use the same file system for all containers.