AWS S3 sync operations do not work with S3 directory buckets (S3 Express One Zone) about aws-cli HOT 4 OPEN

Hi @jeffgardnerdev, thanks for reaching out. Could you provide debug logs of this behavior? You can get debug logs by adding --debug to your command, and redacting any sensitive information. Logs with --delete and without --delete would both be appreciated. Thanks!

from aws-cli.

Here are the two debug outputs, one without the --delete option and one with the --delete option. In this case the two prefixes are identical but the sync command copies/deletes 4 of the 5 files every time. Bucket names are redacted. ListObjectsV2 responses for the two prefixes return the objects in a different order.
s3-sync-standard-to-directory-with-delete-debug-output.txt
s3-sync-standard-to-directory-debug-output.txt

from aws-cli.

@jeffgardnerdev, thanks for your patience. I was able to reproduce this behavior, and your theory that this is related to ListObjectsV2 not sorting directory buckets is likely correct. We've reached out to the service team, and I'll leave any updates in this issue.

If other people are experiencing this issue, providing details and any impact in this issue would be appreciated.

Ticket # for internal use : P114641353

from aws-cli.

@RyanFitzSimmonsAK Could you share some more information about the decision to disable the sync command for directory buckets entirely? This is useful functionality that would be nice to keep, provided the ordering issue could be fixed.

from aws-cli.