From 4ac5d3c8e45ad27c6a5de79d2f961aa24d1c4b99 Mon Sep 17 00:00:00 2001
From: andriikorotkov <88329385+andriikorotkov@users.noreply.github.com>
Date: Fri, 15 Apr 2022 17:06:48 +0300
Subject: [PATCH] updated docs (#11840)

---
 docs/integrations/destinations/s3.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/docs/integrations/destinations/s3.md b/docs/integrations/destinations/s3.md
index c904713faf67..be09937b0a90 100644
--- a/docs/integrations/destinations/s3.md
+++ b/docs/integrations/destinations/s3.md
@@ -247,6 +247,23 @@ Under the hood, an Airbyte data stream in Json schema is first converted to an A
   * If you will use instance profile authentication, make sure the role has permission to read/write on the bucket.
   * The easiest way to verify if Airbyte is able to connect to your S3 bucket is via the check connection tool in the UI.
 
+In order for everything to work correctly, it is also necessary that the user whose "S3 Key Id" and "S3 Access Key" are used have access to both the bucket and its contents. Policies to use:
+```json
+{
+  "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Action": "s3:*",
+            "Resource": [
+                "arn:aws:s3:::YOUR_BUCKET_NAME/*",
+                "arn:aws:s3:::YOUR_BUCKET_NAME"
+            ]
+            }
+    ]
+}
+```
+
 ## CHANGELOG
 
 | Version | Date | Pull Request | Subject                                                                                                                    |