What should a solutions architect do to meet these requirements?
Deploy AWS Storage Gateway for the application data, and use the file gateway to store the data in Amazon S3. Connect the on-premises application servers to the file gateway using NFS.
Attach an Amazon Elastic File System (Amazon EFS) file system to the NFS server, and copy the application data to the EFS file system. Then connect the on-premises application to Amazon EFS.
Configure AWS Storage Gateway as a volume gateway. Make the application data available to the on-premises application from the NFS server and with Amazon Elastic Block Store (Amazon EBS) snapshots.
Create an AWS DataSync agent with the NFS server as the source location and an Amazon Elastic File System (Amazon EFS) file system as the destination for application data transfer. Connect the on-premises application to the EFS file system.
Explanations:
Deploying AWS Storage Gateway with the file gateway allows the on-premises application to access data stored in Amazon S3 via NFS, providing a seamless integration with existing workflows and low-latency access due to the Direct Connect connection.
Amazon EFS does provide NFS access, but attaching it directly to the on-premises NFS server is not supported. The on-premises application cannot directly connect to EFS without a proper integration layer, making this option unviable.
While configuring a volume gateway can provide on-premises access to cloud storage, it requires additional management of block-level snapshots, which complicates the architecture and does not leverage low-latency NFS access directly from the application.
AWS DataSync is used for transferring data efficiently but does not provide continuous low-latency access from the on-premises application to the EFS file system, as it is primarily for batch data transfer rather than real-time access.