New Load balancer in AWS not reachable
So, on a fine sunday evening while playing around with kubernetes, I decided to expose my example application using a load balancer. Since I was testing around, and the application was a sample nginx, I did not bother to customise the security group and ended up using the default security group.
After registering the nodes to a target group and adding the appropriate listener to the load balancer, I sent a request to my load balancer DNS, hoping to see the nginx landing page. Lo and behold, the web request started timing out. I triple-checked the instance health and verified that they were indeed healthy. After 10 more minutes of self-sabotaging my configuration, I started googling why my perfectly configured load balancer is not working properly where I stumbled across a stack overflow post
In a nutshell, the default security group created for the load balancer does not work at all and you have to make manual entries in the secutiry group for the the HTTP/HTTPS traffic.
Subscribe to my newsletter
Read articles from Aman Gaur directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by
Aman Gaur
Aman Gaur
I am a DevOps Engineer from India, currently residing in Halifax, Nova Scotia. I have been working in web development for 9 years professionally. I love debugging container issues, cloud implementation issues in AWS, and love playing with Kubernetes. In my Free time, I love analyzing F1 data.