A file system is shared by clients in several AZs, but old files are rarely read.
Keep the files in the same file system and retrieve them when needed.
Which design is most appropriate?
Use EFS Lifecycle Management to move files that meet the access policy into the EFS Infrequent Access storage class.
Detailed explanation
SQS is a message queue and cannot replace a shared file system.
SQS is a message queue and cannot replace a shared file system.
Instance Store is temporary and does not provide durable shared storage.
Instance Store is temporary and does not provide durable shared storage.
EFS can transition files based on access behavior while preserving the shared file-system interface.
EFS can transition files based on access behavior while preserving the shared file-system interface.
DNS TTL does not affect EFS storage pricing or file lifecycle.
DNS TTL does not affect EFS storage pricing or file lifecycle.
Check official documentation
Compare the following points with the official documentation.
Amazon EFS Infrequent AccessとLifecycle Managementの公式説明を確認する。
What to confirm
共有ファイルのアクセス頻度に応じたEFS階層化を設計できる。
Key points
- EFS Infrequent Access
- Lifecycle Management
- Shared file system
Notes
- Environment: AWS公式EFSドキュメントの確認
- Confirm current AWS pricing and service behavior in the official documentation.
Foundation review
Interface continuity
Lifecycle moves files inside EFS, so clients continue using the same shared file system.
Durability
Instance Store cannot replace a durable shared file system because it is tied to an instance and is temporary.