Patch 405 (#428)

* Update overlapping-security-groups.md

* Update step2.png

Updated image for step 2

* Update step3.png

Updated image for step 3

* Update step4.png

Updated image for step 4

* Update overlapping-security-groups.md

Updated step 4

* Update overlapping-security-groups.md

* Update step5.png

Updated image for step 5

* Updated images for step 5 & 6

* Updated Images for Step 8,9,10,11

* Update overlapping-security-groups.md

Updated step 11

* Update step9.png

Updated image for step 9

* Update overlapping-security-groups.md

Updated step 12

* Update step12.png

Updated image for step 12

* Update overlapping-security-groups.md

Added Step 13 & 14

* Added Images for step 13 & 14

Added Images for step 13 & 14

* Update overlapping-security-groups.md

Added step 15

* Update overlapping-security-groups.md

* Apply suggestions from code review

Co-authored-by: alphadev4 <[email protected]>

en/aws/ec2/overlapping-security-groups.md

@@ -15,17 +15,19 @@
 | **Recommended Action** | Structure security groups to provide a single category of access and do not duplicate rules across groups used by the same instances. |
 
 ## 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 EC2. </br> <img src="/resources/aws/ec2/overlapping-security-groups/step2.png"/>
 3. Scroll down the left navigation panel and choose "Security Groups" under "Network & Security". </br>  <img src="/resources/aws/ec2/overlapping-security-groups/step3.png"/>
-4. Select the "Security Group" that needs to be verified and scroll down and click on the "Description" tab and copy "Group ID". </br> <img src="/resources/aws/ec2/overlapping-security-groups/step4.png"/>
-5. Navigate to the "EC2 dashboard" and on the "Filter by tags and attributes or search by keyword" box select for the "Security Group ID" from the dropdown menu and paste the "Group ID" copied above.</br> <img src="/resources/aws/ec2/overlapping-security-groups/step5.png"/>
+4. Select the "Security Group" that needs to be verified and scroll down and click on the "Details" tab and copy "Security group ID". </br> <img src="/resources/aws/ec2/overlapping-security-groups/step4.png"/>
+5. Scroll down the left navigation panel and choose "Instances" and search the copied "Security Group ID" copied above.</br> <img src="/resources/aws/ec2/overlapping-security-groups/step5.png"/>
 6. Check the number of "EC2 Instance(s)" using the Security Group and if there are more than 1 instances sharing the same "Security Group" then it's not according to the standard practice of AWS.</br> <img src="/resources/aws/ec2/overlapping-security-groups/step6.png"/>
 7. Repeat steps number 2 - 6 to verify other "EC2 Instances" using same "Security Group".</br>
 8. Navigate to "Security Group" under "Network & Security" and click on the "Create Security Group" at the top.</br> <img src="/resources/aws/ec2/overlapping-security-groups/step8.png"/>
 9. On the "Create Security Group" panel provide a "Security Group Name" and "Description" for the new "Security Group".Select the "VPC" to which "Security Group" belongs.</br> <img src="/resources/aws/ec2/overlapping-security-groups/step9.png"/>
-10. Select the "Inbound Traffic Rules" by clicking on the "Add Rules" button and select the "Protocols" as per the requirement.</br> <img src="/resources/aws/ec2/overlapping-security-groups/step10.png"/>
-11. Click on the "Create" button at the bottom to create a new "Security Group". </br> <img src="/resources/aws/ec2/overlapping-security-groups/step11.png"/>
-12. Navigate to "EC2 dahsboard" and select the "Instance(s)" which are sharing the same "Security Group". Click on the "Actions" button at the top and click on the "Change Security Groups" under "Networking".</br> <img src="/resources/aws/ec2/overlapping-security-groups/step12.png"/>
-13. On the "Change Security Groups" tab select the new "Security Group" and click on the "Assign Security Groups" button to assign the selected "Security Group" to the "EC2 Instance".</br> <img src="/resources/aws/ec2/overlapping-security-groups/step13.png"/>
-14. Reepat steps number 8 - 13 to structure security groups and to avoid twin rules across "EC2 Instances".</br>
+10. Select the "Inbound Traffic Rules" by clicking on the "Add Rule" button and select the "Protocols" as per the requirement.</br> <img src="/resources/aws/ec2/overlapping-security-groups/step10.png"/>
+11. Click on the "Create security group" button at the bottom to create a new "Security Group". </br> <img src="/resources/aws/ec2/overlapping-security-groups/step11.png"/>
+12. Navigate to "Instances" in the left panel and select the "Instance(s)" which are sharing the same "Security Group". Click on the "Actions" button at the top and click on the "Change security groups" under "Security".</br> <img src="/resources/aws/ec2/overlapping-security-groups/step12.png"/>
+13. On the "Change Security Groups" tab select the new "Security Group" under "Associated security groups" and click on "Add security group" button.</br> <img src="/resources/aws/ec2/overlapping-security-groups/step13.png"/>
+14. Click on the "Save" button to assign the selected "Security Group" to the "EC2 Instance".</br> <img src="/resources/aws/ec2/overlapping-security-groups/step14.png"/>
+15. Remove any security group which may not be needed as required from the instance.
+16. Repeat steps number 8 - 15 to structure security groups and to avoid their overlapping in "EC2 Instances".</br>