Skip to content

Commit

Permalink
Patch 427 (#448)
Browse files Browse the repository at this point in the history
* Update elb-no-instances.md

* Update elb-no-instances.md

* Updated images for all steps

* Update elb-no-instances.md

* Update en/aws/elb/elb-no-instances.md

Co-authored-by: alphadev4 <[email protected]>
  • Loading branch information
shuklaalok87 and alphadev4 authored Nov 2, 2022
1 parent 0780e45 commit 460af7b
Show file tree
Hide file tree
Showing 8 changed files with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions en/aws/elb/elb-no-instances.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,11 @@
| **Recommended Action** | Delete old ELBs that no longer have backend resources. |

## 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/elb/elb-no-instances/step2.png"/>
3. In the "EC2 Dashboard" scroll down and look for "Load Balancers" and click on "Load Balancers" to get into "Load Balancers" dashboard.</br> <img src="/resources/aws/elb/elb-no-instances/step3.png"/>
4. Select the "Load Balancer" which needs to be verified. </br> <img src="/resources/aws/elb/elb-no-instances/step4.png"/>
5. Select the "Instances" tab from the bottom panel and scroll down to "Edit Availability Zones" option.</br> <img src="/resources/aws/elb/elb-no-instances/step5.png"/>
6. Scroll down and check for "Instances Count" under "Edit Availability Zones". If the load balancer "Instance Count" is 0 it means there are no registered instances. </br> <img src="/resources/aws/elb/elb-no-instances/step6.png"/>
7. Select the unused "Load Balancer" and from "Action" tab from the top panel click on "Delete". </br> <img src="/resources/aws/elb/elb-no-instances/step7.png"/>
8. Click on "Yes,Delete" from the "Delete Load Balancer" panel. </br> </br> <img src="/resources/aws/elb/elb-no-instances/step8.png"/>
6. Check for "Instances Count" under "Edit Availability Zones". If the load balancer "Instance Count" is 0 it means there are no registered instances. </br> <img src="/resources/aws/elb/elb-no-instances/step6.png"/>
7. Select the unused "Load Balancer" and from "Actions" tab from the top panel click on "Delete". </br> <img src="/resources/aws/elb/elb-no-instances/step7.png"/>
8. Click on "Yes,Delete" from the "Delete Load Balancer" pop up that appears. </br> </br> <img src="/resources/aws/elb/elb-no-instances/step8.png"/>
Binary file modified resources/aws/elb/elb-no-instances/step2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/elb/elb-no-instances/step3.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/elb/elb-no-instances/step4.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/elb/elb-no-instances/step5.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/elb/elb-no-instances/step6.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/elb/elb-no-instances/step7.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/elb/elb-no-instances/step8.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 460af7b

Please sign in to comment.