# AWS sync errors **URL:** \ **Category:** Support\ **Created:** [September 12, 2022, 3:43am UTC](https://forum.duplicati.com/t/aws-sync-errors/14963 "2022-09-12T03:43:04Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\ **Post date:** [September 22, 2022, 5:45pm UTC](https://forum.duplicati.com/t/aws-sync-errors/14963/8 "2022-09-22T17:45:16Z")
> [@gpatel-fr](#): > > when the backend decides by itself to delete old files Hopefully that means delete based on a config. It looks like S3 lifecycle rules are able. Don’t tell it to. 😉 I’m not sure how it connects to the object lock question, but I agree we need to live with what we have. > [@LoganKreft](#): > > On a side note we have object lock enabled on the bucket (immutability) [Bucket configuration](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-overview.html#object-lock-bucket-config) makes me ask – what mode and period? Governance mode seems a little looser. Setting period near Duplicati retention period might create some benefits, but I don’t know if it’s enough. Any backup will upload a dlist file and some dblock files with changed data, and dindex files for dblocks. Duplicati retention directly affects deletion of dlist files corresponding to backup versions, and indirectly affects deletion of dblock and dindex because their blocks are still in use as long as dlist file uses them. > [@Cost optimisation on wasabi](https://forum.duplicati.com/t/cost-optimisation-on-wasabi/11803/11): > > TL;DR Setting backup retention to match Wasabi 90-day retention can help keep storage charge “active”. was trying to avoid an extra fee from early deletion. With object lock, you’re avoiding early delete failures. This is far from a solid path, and you can expect some bumps. Ideally set up an AWS escape hatch too. --- _[View the full topic](https://forum.duplicati.com/t/aws-sync-errors/14963)._