Workers in multiple Availability Zones use an EFS file system.
Meet the required throughput as well as the capacity requirement.
Which consideration is most appropriate?
Choose EFS performance and throughput modes based on the workload's access pattern, latency, and throughput requirements.
Detailed explanation
EFS exposes throughput and performance modes that tune access characteristics separately from capacity.
EFS exposes throughput and performance modes that tune access characteristics separately from capacity.
DNS record count is unrelated to EFS performance settings.
DNS record count is unrelated to EFS performance settings.
SQS is a message queue and cannot provide shared file storage.
SQS is a message queue and cannot provide shared file storage.
File count does not by itself select or guarantee an EFS throughput mode.
File count does not by itself select or guarantee an EFS throughput mode.
Check official documentation
Compare the following points with the official documentation.
Amazon EFS performance modeとthroughput modeの公式説明を確認する。
What to confirm
共有ファイルの容量・レイテンシー・スループットを分けて設計できる。
Key points
- EFS Throughput Mode
- EFS Performance Mode
- Throughput
Notes
- Environment: AWS公式EFSドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Independent dimensions
A file system can have enough capacity while still needing a different performance or throughput mode.
Access pattern
Concurrency, file size, and read or write behavior influence the appropriate mode.