Which solution will meet these requirements MOST cost-effectively?
Set up an AWS Storage Gateway Volume Gateway. Use an Amazon S3 Lifecycle policy to transition the data to the appropriate storage class.
Set up an AWS Storage Gateway Amazon S3 File Gateway. Use an Amazon S3 Lifecycle policy to transition the data to the appropriate storage class.
Use the Amazon Elastic File System (Amazon EFS) Standard-Infrequent Access (Standard-IA) storage class. Activate the infrequent access lifecycle policy.
Use the Amazon Elastic File System (Amazon EFS) One Zone-Infrequent Access (One Zone-IA) storage class. Activate the infrequent access lifecycle policy.
Explanations:
AWS Storage Gateway Volume Gateway is primarily for block storage use cases and doesn’t directly provide NFS access or integration with S3 for data lifecycle management. This option would not be optimal for a scenario needing scalable NFS-like access.
The AWS Storage Gateway Amazon S3 File Gateway provides a way to access Amazon S3 objects as files via NFS, making it suitable for workloads that require NFS compatibility. This option also allows using S3 lifecycle policies to transition data to lower-cost storage classes, providing a cost-effective solution.
While Amazon EFS offers scalability, the Standard-Infrequent Access (Standard-IA) storage class is not applicable since EFS does not have a “Standard-IA” class. Additionally, EFS is generally more expensive than S3, making it less cost-effective for large-scale data storage.
Similar to option C, Amazon EFS One Zone-Infrequent Access (One Zone-IA) does not exist as a recognized class. Furthermore, EFS would not be as cost-effective as using S3 for large-scale, infrequently accessed data storage.
I judge that the answer is:
Set up an AWS Storage Gateway Amazon S3 File Gateway. Use an Amazon S3 Lifecycle policy to transition the data to the appropriate storage class.