- Más nuevo
- Más votos
- Más comentarios
Hi bimargulies,
When PreserveDeletedFiles is set to REMOVE [1], the deletion of files on the destination that do not exist on the source is prevented if an affected file or object cannot be read during the transfer phase. This occurs when an object is inventoried when listing the source, but becomes unreadable during the transfer phase.
This behavior is intentionally designed to prevent accidental deletions when files that were expected to be transferred can no longer be read. Such situations may arise due to:
- Failure to connect to the source
- Changes in permissions
- Timeouts during read operations
DataSync Enhanced logs will show:
"ErrorDetail": "DataSync was unable to read the file or folder from the source: Access Denied"
for "Action": "DELETE"
Thanks
The problem here was objectTags. I turned on object tag copying without realizing that this required more permission to the source than I had. That resulted in errors all around, on both deletes and additions. It became obvious when the first new document appeared at the source, producing an error message that did not seem to be self-contradicting.
In AWS DataSync's Enhanced mode logs, the "DELETE" action in your log message indicates that DataSync was attempting to delete a file at the destination location that doesn't exist in the source location.
When DataSync performs a DELETE action, it first needs to read the source location to confirm that the file is indeed missing from the source before deleting it from the destination. The error "UnableToReadSource" with detail "DataSync was unable to read the file or folder from the source: Access Denied" suggests that DataSync couldn't access the source location to verify whether the file exists there.
This typically happens when:
- The DataSync task is configured to delete files in the destination that don't exist in the source
- DataSync needs to check if the file exists in the source before deleting it from the destination
- There's a permissions issue preventing DataSync from reading the source location
The Enhanced mode logs provide structured JSON data that makes it easier to understand what's happening during the task execution. In this case, you can see:
- The specific file path being processed
- The source and destination location IDs
- The exact error code and description
- Timestamp of when this occurred
To resolve this issue, you would need to check the permissions for the DataSync task at the source location to ensure it has proper read access to verify file existence.
Sources
Monitoring data transfers with Amazon CloudWatch Logs - AWS DataSync
Troubleshooting data verification issues - AWS DataSync
Monitoring your data transfers with task reports - AWS DataSync
This appears to be LLM slop. To trigger a DELETE at all, DataSync has to have read the source bucket to get a list of its contents to compare with the target bucket. So the text in here makes no sense at all.
Contenido relevante
- preguntada hace 17 días
- preguntada hace 4 meses
- preguntada hace 13 días

Please see my answer, which I guess is consistent with yours.