Inquiry Regarding Amazon FSx Cost Optimization and S3 Object Exclusion

Hello,

Thanks for reaching out to us.

So, on a general note, S3 offers various storage classes. You can set lifecycle rule to transition the objects to Glacier Deep Archive or Glacier Flexible retrieval storage class after 180 days. No operation can be performed on the objects stored in Glacier storage classes. Therefore, these objects will not be accessible when you run any sort of sync operation on these objects. However, keep in mind that these objects won’t be readily accessible until you manually restore them.

[] Comparing the Amazon S3 storage classes - https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html#sc-compare

Additionally, I am not sure about the mechanism you’re using to sync FSx with S3 in your case. Hence, to gain a better understanding of your architecture and delve into it to provide best cost optimisation, I would request you to open a case with AWS team. Our team will be more than happy to provide you with more details once we have a deeper understanding of your architecture.

In my opinion, I would suggest doing:

1. Tag the S3 objects that you want to exclude from the sync process. For example, you could add a tag like ExcludeFromSync: true to these objects.
2. FSx supports filtering based on object tags when syncing with S3. You can modify the FSx sync options to exclude objects with specific tags.
3. If you want to further optimize costs in S3, you can use S3 Lifecycle policies to transition infrequently accessed objects to cheaper storage classes (e.g., S3 Glacier). This can help reduce storage costs without deleting the objects.