How do I troubleshoot Elastic Load Balancing connectivity issues?
How do I troubleshoot Elastic Load Balancing connectivity issues?
Skip directly to the demo: 0:26
For more details see the Knowledge Center article with this video: https://repost.aws/knowledge-center/e…
Venkatesh shows you how to troubleshoot Elastic Load Balancing connectivity issues.
Content
0.41 -> [Music]
12.799 -> hello
13.36 -> i'm venkatesh a cloud support engineer
15.599 -> here at the aws office in northern
17.44 -> virginia
18.72 -> today i'm going to show you how to
20.8 -> troubleshoot
21.76 -> connectivity issues to your load
23.519 -> balancer
24.8 -> let's get started after logging into the
28.08 -> aws management console
29.84 -> navigate to the ec2 console then
33.2 -> select load balancers in the navigation
35.6 -> pane
37.44 -> for this discussion i have created an
39.6 -> external load balancer
41.28 -> which has listener configured on port
43.68 -> 80.
44.8 -> the load balancer should be listening to
47.12 -> the port
47.84 -> that the client is attempting to connect
50 -> to if you're planning to use
52 -> any port other than port 80 please make
54.96 -> sure that you have the listener
56.32 -> configured for that specific port
59.84 -> next ensure that the load balancer
62.399 -> security group
63.44 -> is allowing traffic for the configured
66 -> port
66.96 -> since this is an external load balancer
69.84 -> i have allowed access
71.2 -> to the world if you are using an
73.84 -> internal load balancer
75.28 -> your security group rules must allow the
77.68 -> ips
78.64 -> of the clients on the relevant listener
81.2 -> port
83.04 -> verify that the load balancer can
84.88 -> communicate with the backend instances
87.84 -> your backend security group must allow
90.799 -> traffic
91.36 -> from the load balancer subnets on both
94.56 -> the listener
95.36 -> and the health check ports here i have
98.56 -> allowed
99.2 -> all traffic from the vpc of the load
101.6 -> balancer
104.399 -> navigate to the vpc console and ensure
107.6 -> that the network acls of your vpc allow
110.479 -> traffic in both directions
112.56 -> on the listener port and the health
114.399 -> check port for each subnet attached to
116.799 -> the load balancer
118.799 -> now let's check the network acls
122.159 -> attached to subnets you can see
125.759 -> that i have allowed all traffic in
128.879 -> both inbound and outbound rules
133.76 -> also make sure that the route tables
136.319 -> attached to the subnets of the load
138.239 -> balancer
139.04 -> have a default route pointing to the
141.12 -> internet gateway
142.879 -> here you can see that i have an internet
145.599 -> gateway
146.56 -> pointing to 0 0 0
149.76 -> 0 0 which is necessary for the load
153.28 -> balancer
154.319 -> to receive and direct the traffic back
157.04 -> to the client over the internet
160.72 -> finally test the connectivity to your
162.64 -> load balancer using telnet
165.44 -> you can see that we have now established
167.84 -> connection to the load balancer
169.68 -> successfully additionally
172.879 -> if the connectivity issues are sporadic
175.12 -> this may be an indication of capacity
177.2 -> related
177.84 -> or load related issues for more
180.64 -> information about troubleshooting load
182.56 -> related issues
183.76 -> please follow the link provided in the
185.599 -> knowledge center article
188.56 -> thanks for watching and happy cloud
190.56 -> computing from all of us here at aws
199.92 -> you
Source: https://www.youtube.com/watch?v=p7O5adUGBkM