Which solution should the solutions architect recommend?
Deploy AWS DataSync on-premises. Configure DataSync to continuously replicate the .csv files between the company’s on-premises storage and the company’s S3 bucket.
Deploy an on-premises file gateway. Configure data sources to write the .csv files to the file gateway. Point the legacy analytics application to the file gateway. The file gateway should replicate the .csv files to Amazon S3.
Deploy an on-premises volume gateway. Configure data sources to write the .csv files to the volume gateway. Point the legacy analytics application to the volume gateway. The volume gateway should replicate data to Amazon S3.
Deploy AWS DataSync on-premises. Configure DataSync to continuously replicate the .csv files between on-premises and Amazon Elastic File System (Amazon EFS). Enable replication from Amazon Elastic File System (Amazon EFS) to the company’s S3 bucket.
Explanations:
AWS DataSync is ideal for synchronizing data between on-premises storage and Amazon S3, enabling continuous and efficient replication of .csv files, which addresses the company’s needs to support the legacy application and maintain copies in Amazon S3.
An on-premises file gateway replicates data to Amazon S3 but requires modification of data source paths to the file gateway. This might not be feasible, and the file gateway mainly serves files via NFS/SMB, which does not align with the current .csv file structure requirements.
An on-premises volume gateway is designed for block storage and not file-based systems. Since the data involves .csv files (file storage), a volume gateway would be inappropriate and inefficient for file handling and would complicate integration with Amazon S3.
DataSync can sync files with Amazon EFS, but this introduces unnecessary complexity, as direct synchronization from on-premises storage to Amazon S3 is more efficient. Additionally, EFS is primarily for Linux-based shared files, which may not align with the legacy application’s format.