From c3117d9efb469b56be43f6ddffba023c6273458b Mon Sep 17 00:00:00 2001
From: Eli Orzitzer <e_orz@yahoo.com>
Date: Thu, 7 Dec 2023 15:38:34 +0200
Subject: [PATCH] Doc change: Add the CreateBucket permission requirement for
 AWS S3

---
 docs/content/s3.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/content/s3.md b/docs/content/s3.md
index aa16509ac..46b5873ed 100644
--- a/docs/content/s3.md
+++ b/docs/content/s3.md
@@ -590,6 +590,7 @@ permissions are required to be available on the bucket being written to:
 * `GetObject`
 * `PutObject`
 * `PutObjectACL`
+* `CreateBucket` (unless using [s3-no-check-bucket](#s3-no-check-bucket))
 
 When using the `lsd` subcommand, the `ListAllMyBuckets` permission is required.
 
@@ -631,6 +632,7 @@ Notes on above:
    that `USER_NAME` has been created.
 2. The Resource entry must include both resource ARNs, as one implies
    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)
 that will generate one or more buckets that will work with `rclone sync`.