An existing application accesses an on-premises file share over NFS and SMB.
Keep frequently used files available with low latency through an on-premises cache while storing the source of record in AWS.
Which architecture is most appropriate?
Use File Gateway to retain NFS/SMB access and local caching while storing the data in Amazon S3.
Detailed explanation
File Gateway provides NFS/SMB file interfaces and a local cache while using S3 as the cloud storage target.
File Gateway provides NFS/SMB file interfaces and a local cache while using S3 as the cloud storage target.
EFS is a VPC-based regional file system and does not provide the local cache and S3-backed file gateway behavior required here.
EFS is a VPC-based regional file system and does not provide the local cache and S3-backed file gateway behavior required here.
FSx is a managed file system, but it does not directly satisfy the S3-backed File Gateway cache requirement.
FSx is a managed file system, but it does not directly satisfy the S3-backed File Gateway cache requirement.
Transfer Acceleration speeds object transfers but does not provide an SMB or NFS file-share interface.
Transfer Acceleration speeds object transfers but does not provide an SMB or NFS file-share interface.
Check official documentation
Compare the following points with the official documentation.
AWS Storage Gateway File Gatewayのファイル共有とキャッシュの公式説明を確認する。
Official references
What to confirm
ファイルプロトコルの互換性、ローカルキャッシュ、クラウド側の保存先を分けて設計できる。
Key points
- AWS Storage Gateway
- File Gateway
- Local cache
Notes
- Environment:
- Confirm current behavior in the official SAA-C03 guide and AWS service documentation.
Foundation review
Protocol compatibility
First verify that the existing NFS or SMB access pattern can remain unchanged.
Cache and source of record
Design local responsiveness and cloud persistence as separate responsibilities.