I've got a particular use case where a microservice (dockerized python) running in an EKS pod will write some images and plaintext logfiles to its container disk during the course of its business. The need has arisen to access these assets and logfiles on a persistent basis, so they're not lost when the container restarts.
For various reasons, it's not feasible to modify the application logic itself to upload to S3 vs. dumping to disk. I can change the path where they're written, though.
Is there a recommended approach for a) having these filesystem writes persist to somewhere permanent in AWS, and b) conveniently accessing them later (i.e. mounting that drive as read-only would be great)?
Thanks in advance!