An enterprise is migrating a legacy document management system to AWS. The application runs on Amazon EC2 instances distributed across three Availability Zones. The instances require concurrent read and write access to a shared directory that supports standard file system operations (POSIX compliance). A large portion of the files consists of compliance reports that are rarely accessed after 30 days but must remain online and accessible with low latency when requested. Which AWS storage solution meets these requirements with the lowest operational overhead?
- AAmazon Simple Storage Service (Amazon S3) using Mountpoint for Amazon S3 to attach the bucket to the EC2 instances, utilizing S3 Lifecycle policies to transition reports to S3 Glacier Flexible Retrieval.
- Amazon Elastic File System (Amazon EFS) with an EFS Lifecycle Management policy configured to transition files to EFS Infrequent Access (IA) after 30 days of inactivity.Answer
- CAmazon Elastic Block Store (Amazon EBS) with Multi-Attach enabled on Provisioned IOPS volumes, configuring an automated backup policy to Amazon S3 Glacier.
- DAmazon Elastic File System (Amazon EFS) mounted on a single primary EC2 instance, using an AWS Storage Gateway (Volume Gateway) to replicate files to other instances in different Availability Zones.
Answer
Amazon Elastic File System (Amazon EFS) with an EFS Lifecycle Management policy configured to transition files to EFS Infrequent Access (IA) after 30 days of inactivity.
Amazon Elastic File System (Amazon EFS) is a serverless, fully managed network file system that supports POSIX compliance, allowing multiple Amazon EC2 instances across multiple Availability Zones to concurrently read and write to the same directory. Furthermore, EFS Lifecycle Management automatically transitions files that have not been accessed for 30 days to the EFS Infrequent Access (IA) storage class, reducing storage costs by up to 92% while keeping the files online and immediately accessible with low latency.
Step-by-Step Solution
Key Concept
Selecting the appropriate AWS storage service (block, file, or object) based on access patterns, multi-AZ support, POSIX compliance, and lifecycle cost optimization.