For small games like Valheim or Minecraft (~4GB I think?), this means nothing. However if you look at something like Plex, this can explode.
Describe the solution you'd like
S3 has a problem with random read-writes that you get from Games. However EFS (even single zone) is much more expensive than S3. Maybe have an option in the config, on which paths should be backed by S3, and which by EFS. Only use S3 for large-data folders like a Plex media directory (but not it's metadata directory).
Stretch goal if this works out: Only create the EFS object itself if they have a mount type for it. Same for the S3 bucket.
Describe alternatives you've considered
Just leave as is, and either don't support Plex-like stuff, or be okay with the cost. This isn't a blocker if it doesn't work out, just a nice-to-have.
Additional context
We DON'T want to use DataSync. That will duplicate the data to both s3 and efs, then you're paying for both at once.
Is your feature request related to a problem? Please describe.
$0.16/GB /Month
=>$163.84/TB /Month
$0.023/GB /Month
=>$23.55/TB /Month
For small games like Valheim or Minecraft (~
4GB
I think?), this means nothing. However if you look at something like Plex, this can explode.Describe the solution you'd like S3 has a problem with random read-writes that you get from Games. However EFS (even single zone) is much more expensive than S3. Maybe have an option in the config, on which paths should be backed by S3, and which by EFS. Only use S3 for large-data folders like a Plex media directory (but not it's metadata directory).
EFS
object itself if they have a mount type for it. Same for theS3
bucket.Describe alternatives you've considered Just leave as is, and either don't support Plex-like stuff, or be okay with the cost. This isn't a blocker if it doesn't work out, just a nice-to-have.
Additional context We DON'T want to use DataSync. That will duplicate the data to both s3 and efs, then you're paying for both at once.
Docs/Guides on this: