Check the ETag returned by the headObject call and compare it against an md5 hash of the file content in the stream. If the ETag matches the md5 hash then this file does not need to be uploaded to AWS and can be skipped which speeds up the overall time to upload files, especially on subsequent execution.
TMYK! I never did in-depth research pertaining to ETags, but that's good to know. I'll dig deeper into the AWS docs and add this change. I'll review and merge later this afternoon to add this to the next major version. I'll also close your issue ( #15 ).
Check the ETag returned by the
headObject
call and compare it against an md5 hash of the file content in the stream. If the ETag matches the md5 hash then this file does not need to be uploaded to AWS and can be skipped which speeds up the overall time to upload files, especially on subsequent execution.