Depending on your data needs, you have two options that I can think of:
Mapping S3 Bucket as Local Disk
You can split the S3 bucket and restrict access to any number of instances. We are using a drive mapping solution on Windows that will mount the S3 bucket as a local drive. Similar drivers exist for Linux . Thus, each instance receives the same mapped drive and transfers this persistent data. Data is read / written, so if we scale or exit, each instance has access to S3 data in a consistent format.
Mount the volume from the snapshot
If you think this is readable data that you need access to, you can use Userdata scripts to mount the volume from the snapshot at startup. You just need a script and an IAM account / role to run the appropriate commands at startup
source share