1 Answer
- Newest
- Most votes
- Most comments
1
aws s3 sync by default will ignore files of same size and same timestamps if the object exists on both source and destination.
Sync will copy files from source to destination if:
- if the size of the local file is different than the size of the s3 object
- the last modified time of the local file is newer than the last modified time of the s3 object
- the local file does not exist under the specified bucket and prefix.
Is it possible that the objects you are expecting to sync are same size/timestamp and therefore being skipped by s3 sync?
Flags of interest to help with modifying aws s3 sync behavior
--size-only (boolean) Makes the size of each key the only criteria used to decide whether to sync from source to destination.
--exact-timestamps (boolean) When syncing from S3 to local, same-sized items will be ignored only when the timestamps match exactly. The default behavior is to ignore same-sized items unless the local version is newer than the S3 version.
See also https://docs.aws.amazon.com/cli/latest/reference/s3/sync.html
answered 2 years ago
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
Thanks for the info. There have been a number of changed files and added folders. The changes are there, but not being recognized. I'll review the flags and see if any might help with troubleshooting.