EC2 workers in multiple Availability Zones mount the same POSIX file system. Data volume and I/O vary substantially by day, and future capacity and throughput cannot be forecast in advance.
The design must preserve file-sharing semantics while avoiding payment for unused capacity or provisioned throughput.
Which storage configuration is most appropriate?
Use a Regional Amazon EFS file system with Elastic throughput when multiple Availability Zones need shared files and both capacity and I/O are difficult to predict.
Detailed explanation
EFS provides shared NFS access without pre-provisioning capacity. Elastic throughput adjusts performance to unpredictable I/O so a fixed amount of unused capacity or performance is not reserved.
EFS provides shared NFS access without pre-provisioning capacity. Elastic throughput adjusts performance to unpredictable I/O so a fixed amount of unused capacity or performance is not reserved.
EBS is instance-oriented block storage, not shared file storage. The application would have to implement synchronization and conflict handling while paying for duplicated fixed capacity.
EBS is instance-oriented block storage, not shared file storage. The application would have to implement synchronization and conflict handling while paying for duplicated fixed capacity.
S3 is object storage and does not provide POSIX mounts or file locking as-is. Requiring an application access-model rewrite does not satisfy the shared-file requirement.
S3 is object storage and does not provide POSIX mounts or file locking as-is. Requiring an application access-model rewrite does not satisfy the shared-file requirement.
FSx can be appropriate for specific file-system features, but fixed capacity and throughput can leave unused provisioned resources when both workload dimensions are unpredictable.
FSx can be appropriate for specific file-system features, but fixed capacity and throughput can leave unused provisioned resources when both workload dimensions are unpredictable.
Check official documentation
Compare the following points with the official documentation.
Amazon EFSの容量の自動伸縮とElastic throughputの公式説明を確認する。
Official references
What to confirm
ファイルシステムは保存データに応じて拡張・縮小し、I/Oが変動してもスループットを事前に固定せずに共有アクセスを継続する。
Key points
- Amazon EFS
- Regional file system
- Elastic throughput
- NFS
Notes
- Environment:
- Confirm the current file-system types, capacity behavior, and throughput modes in the official EFS documentation.
Foundation review
Capacity and throughput
Stored data growth and I/O demand are separate dimensions. EFS can combine elastic file-system capacity with Elastic throughput when both are hard to forecast.
Access-model compatibility
EBS is block storage, S3 is object storage, and EFS is NFS file storage. Select from the existing application's access semantics and Availability Zone requirements.