Elastic File Systems with Laravel Vapor

Is there any downside to attaching an Elastic File System to my Vapor app - other than cost?

The reason I'm considering doing this is speed. Especially when it comes to mutating files that were just uploaded and forced to be stored in an S3 bucket.

The server can't manipulate those files from their buckets, so it has to re-download them into memory to manipulate them, even though they were just uploaded. I think the Elastic File System could fix that - does that make sense?