Doc change: Add the CreateBucket permission requirement for AWS S3

This commit is contained in:
Eli Orzitzer 2023-12-07 15:38:34 +02:00 committed by Nick Craig-Wood
parent 4245a042c0
commit f62ae71b4c
1 changed files with 2 additions and 0 deletions

View File

@ -590,6 +590,7 @@ permissions are required to be available on the bucket being written to:
* `GetObject` * `GetObject`
* `PutObject` * `PutObject`
* `PutObjectACL` * `PutObjectACL`
* `CreateBucket` (unless using [s3-no-check-bucket](#s3-no-check-bucket))
When using the `lsd` subcommand, the `ListAllMyBuckets` permission is required. When using the `lsd` subcommand, the `ListAllMyBuckets` permission is required.
@ -631,6 +632,7 @@ Notes on above:
that `USER_NAME` has been created. that `USER_NAME` has been created.
2. The Resource entry must include both resource ARNs, as one implies 2. The Resource entry must include both resource ARNs, as one implies
the bucket and the other implies the bucket's objects. the bucket and the other implies the bucket's objects.
3. When using [s3-no-check-bucket](#s3-no-check-bucket) and the bucket already exsits, the `"arn:aws:s3:::BUCKET_NAME"` doesn't have to be included.
For reference, [here's an Ansible script](https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b) For reference, [here's an Ansible script](https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b)
that will generate one or more buckets that will work with `rclone sync`. that will generate one or more buckets that will work with `rclone sync`.