Patch 462 (#484)

* Update s3-bucket-logging.md * Update s3-bucket-logging.md * Updated images for all steps * Update s3-bucket-logging.md * Update s3-bucket-logging.md * Apply suggestions from code review Co-authored-by: alphadev4 <[email protected]>
aquasecurity · Nov 2, 2022 · 4957af5 · 4957af5
1 parent 1632251
commit 4957af5
Show file tree

Hide file tree

Showing 11 changed files with 5 additions and 7 deletions.
diff --git a/en/aws/s3/s3-bucket-logging.md b/en/aws/s3/s3-bucket-logging.md
@@ -15,14 +15,12 @@
 | **Recommended Action** | Enable bucket logging for each S3 bucket. |
 
 ## Detailed Remediation Steps
-1. Log into the AWS Management Console.
+1. Log in to the AWS Management Console.
 2. Select the "Services" option and search for S3. </br> <img src="/resources/aws/s3/s3-bucket-logging/step2.png"/>
 3. Scroll down the left navigation panel and choose "Buckets".</br> <img src="/resources/aws/s3/s3-bucket-logging/step3.png"/>
 4. Select the "Bucket" that needs to be verified and click on its identifier(name) from the "Bucket name" column.</br><img src="/resources/aws/s3/s3-bucket-logging/step4.png"/>
 5. Click on the "Properties" tab on the top menu. </br><img src="/resources/aws/s3/s3-bucket-logging/step5.png"/>
-6. Check the "Server access logging" option under "Properties" and if it's set to "Disable logging" then S3 bucket logging is not enabled for the selected S3 bucket. </br><img src="/resources/aws/s3/s3-bucket-logging/step6.png"/>
-7. Repeat steps number 2 - 6 to verify other S3 buckets in the region. </br>
-8. Select the "S3 bucket" on which "Logging" needs to be enabled and click on the "Properties" tab. </br><img src="/resources/aws/s3/s3-bucket-logging/step8.png"/>
-9. Click on the "Enable logging" option under "Server access logging" and choose the "Target bucket" from the dropdown menu for storing the logs and provide a unique name under "Target prefix" for the subdirectory where S3 logs will be stored. </br><img src="/resources/aws/s3/s3-bucket-logging/step9.png"/> 
-10. Click on the "Save" button to make the necessary changes. </br><img src="/resources/aws/s3/s3-bucket-logging/step10.png"/>
-11. Repeat steps number 8 - 10 to enable "Logging" for other S3 buckets.</br>
+6. Check the "Server access logging" option under "Properties" and if it's set to "Disabled" then S3 bucket logging is not enabled for the selected S3 bucket. </br><img src="/resources/aws/s3/s3-bucket-logging/step6.png"/>
+7. To enable Server access logging click on the "Edit" button under "Server access logging" option. On the "Edit server access logging" page select "Enable" and choose the "Target bucket" from the dropdown menu for storing the logs.</br><img src="/resources/aws/s3/s3-bucket-logging/step7.png"/>
+8. Click on the "Save changes" button to make the necessary changes. </br><img src="/resources/aws/s3/s3-bucket-logging/step8.png"/>
+9. Repeat steps number 4 - 8 to enable "Logging" for other S3 buckets.</br>
diff --git a/resources/aws/s3/s3-bucket-logging/.DS_Store b/resources/aws/s3/s3-bucket-logging/.DS_Store
diff --git a/resources/aws/s3/s3-bucket-logging/step10.png b/resources/aws/s3/s3-bucket-logging/step10.png
diff --git a/resources/aws/s3/s3-bucket-logging/step2.png b/resources/aws/s3/s3-bucket-logging/step2.png
diff --git a/resources/aws/s3/s3-bucket-logging/step3.png b/resources/aws/s3/s3-bucket-logging/step3.png
diff --git a/resources/aws/s3/s3-bucket-logging/step4.png b/resources/aws/s3/s3-bucket-logging/step4.png
diff --git a/resources/aws/s3/s3-bucket-logging/step5.png b/resources/aws/s3/s3-bucket-logging/step5.png
diff --git a/resources/aws/s3/s3-bucket-logging/step6.png b/resources/aws/s3/s3-bucket-logging/step6.png
diff --git a/resources/aws/s3/s3-bucket-logging/step7.png b/resources/aws/s3/s3-bucket-logging/step7.png
diff --git a/resources/aws/s3/s3-bucket-logging/step8.png b/resources/aws/s3/s3-bucket-logging/step8.png
diff --git a/resources/aws/s3/s3-bucket-logging/step9.png b/resources/aws/s3/s3-bucket-logging/step9.png