aws s3 sync --acl does not update the ACL of existing files on S3
Open
feature-request
p3
s3
s3sync
- Dominant language
- Python
- Stars
- 17.3k
- Forks
- 4.6k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 13
Description
If you sync some files from local storage to S3 and then re-run the same sync command with a new `--acl` setting, you'd expect the ACLs of the existing objects on S3 to be updated. However, they are not.
So, for example, after running these commands:
```
aws s3 rm --recursive s3://my-bucket/test/
aws s3 sync --acl public-read local-dir/ s3://my-bucket/test/
aws s3 sync --acl private local-dir/ s3://my-bucket/test/
```
The objects in `s3://my-bucket/test/` will all have an ACL of `public-read`, when they should have an ACL of `private`.
What I'm running:
```
aws-cli/1.14.60 Python/3.6.4 Darwin/17.4.0 botocore/1.9.13
```
Related: #901, https://github.com/aws/aws-cli/issues/1060#issuecomment-258996036
Contributor guide
Assessment
This issue has not been assessed yet.