Thanks, Matt.
I looked around for the algorithm in the src, but couldn't discern how things
worked myself. Thank you for the explanation and reasoning behind how it's done.
The aws s3 sync algorithm states it operate like so
A local file will require uploading if the size of the local file
I've struggled with some huge object count transfers and went back and forth
between aws s3 cli and s3cmd.
aws s3 cli seems to edge s3cmd out on speed and RAM consumption when doing huge
object count transfers. However, aws s3 cli seems to choke on large object
counts and s3cmd offers so much
aws-cli (after a quick perusal of their source code) uses the LastModified
value (set by S3 to be the time the upload of the object occurred) on
objects in S3, which is obtainable from the ListBucket XML, without doing
a HEAD call. They then go on to calculate the difference between
LastModified
