Which solution meets these requirements MOST cost-effectively?
Deploy an AWS Storage Gateway file gateway that is associated with an S3 bucket. Move the files from the on-premises file storage solution to the file gateway. Create an S3 Lifecycle rule to move the files to S3 Standard-Infrequent Access (S3 Standard-IA) after 5 days.
Deploy an AWS Storage Gateway volume gateway that is associated with an S3 bucket. Move the files from the on-premises file storage solution to the volume gateway. Create an S3 Lifecycle rule to move the files to S3 Glacier Deep Archive after 5 days.
Deploy an AWS Storage Gateway tape gateway that is associated with an S3 bucket. Move the files from the on-premises file storage solution to the tape gateway. Create an S3 Lifecycle rule to move the files to S3 Standard-Infrequent Access (S3 Standard-IA) after 5 days.
Deploy an AWS Storage Gateway file gateway that is associated with an S3 bucket. Move the files from the on-premises file storage solution to the file gateway. Create an S3 Lifecycle rule to move the files to S3 Glacier Deep Archive after 5 days.
Explanations:
While using a file gateway and transitioning files to S3 Standard-IA after 5 days is suitable for infrequent access, it does not meet the requirement of archiving files for disaster recovery, as S3 Standard-IA is still considered a standard storage class and is more expensive than archival options.
A volume gateway is not designed for file storage access but rather for block storage. This option does not support NFS directly as required. Additionally, moving files to S3 Glacier Deep Archive after 5 days may be overly complex for the use case.
A tape gateway is primarily designed for backup and archiving scenarios using virtual tapes. It does not directly support NFS, which is required for this solution. Also, moving files to S3 Standard-IA is not the most cost-effective archival solution.
A file gateway supports NFS, making it suitable for the company’s on-premises file storage solution. By moving files to S3 Glacier Deep Archive after 5 days, it provides a cost-effective archival solution suitable for disaster recovery, aligning with the company’s needs for retrieval timing and cost-efficiency.