Which set of actions should a solutions architect take to support these needs?
Store the data in an Amazon Elastic Block Store (Amazon EBS) volume. Mount the EBS volume on the application instances.
Store the data in an Amazon Elastic File System (Amazon EFS) file system. Mount the file system on the application instances.
Store the data in Amazon S3 Glacier. Update the S3 Glacier vault policy to allow access to the application instances.
Store the data in an Amazon Elastic Block Store (Amazon EBS) Provisioned IOPS volume shared between the application instances.
Explanations:
Amazon EBS volumes are not designed to be shared between multiple EC2 instances simultaneously. They can only be attached to one instance at a time, making this option unsuitable for the requirement of multiple instances modifying data concurrently.
Amazon EFS provides a scalable, shared file system that can be mounted on multiple EC2 instances across different Availability Zones. It supports concurrent access and is designed for growing storage needs, making it the best fit for this scenario.
Amazon S3 Glacier is primarily used for long-term archival storage and is not suitable for data that requires frequent access and modification. It has retrieval delays and higher costs for access, which does not align with the hourly analysis and modification requirement.
Similar to option A, Amazon EBS volumes cannot be shared across multiple instances. Even with Provisioned IOPS, they are still limited to one instance at a time, which does not meet the need for concurrent data modifications by several instances.
I rank that the answer is:
Store the data in an Amazon Elastic File System (Amazon EFS) file system. Mount the file system on the application instances.