-
Hi Joseph,
Thanks for sharing your question. We’ve already provided an exhaustive write-up as to why S3 is not suitable for this scenario. The cost is just one of the things that you have to consider.
In this scenario, the keywords are “rapidly changing data” and “over a thousand Linux servers”.
Amazon EFS is a file storage service for use with Amazon EC2. Amazon EFS provides a file system interface, file system access semantics (such as strong consistency and file locking), and concurrently-accessible storage for up to thousands of Amazon EC2 instances. EFS provides the same level of high availability and high scalability like S3 however, this service is more suitable for scenarios where it is required to have a POSIX-compatible file system or if you are storing rapidly changing data.
Although S3 provides the same level of high availability and high scalability like EFS, this service is not suitable for storing data which are rapidly changing, just as mentioned in the above explanation. It is still more effective to use EFS as it offers strong consistency and file locking which the S3 service lacks. In addition, the AWS Systems Manager Patch Manager is primarily used to automate the process of patching managed instances with security-related updates. Hence, using the AWS Systems Manager State Manager is a better choice.
Moreover, you can also use Amazon EFS Infrequent Access (EFS IA) to further lower-down your operating cost of storage. I understand the S3 is cheaper than EFS, but once again, the cost is just one of the things you have to consider here.
Regards,
Jon Bonso
