How to use AWS Application Load Balancer (ALB) for Jenkins Server | By M. Sharma

In this video, you’ll see how to use #amazonwebservices ALB for distributing incoming application traffic across target groups via targets, such as EC2 instances, in multiple Availability Zones for Jenkins Server.
For more information on this topic, please visit the resource below:
www.jenkins.io/
docs.aws.amazon.com/elasticlo...
• How to Reset Jenkins A...
• Jenkins Installation: ...
Session Level: Intermediate
To support the Author - bit.ly/3lKmyGo
Subscribe: For More Devops related videos: / @sharmiochannel
You can follow me
LinkedIn: / imoisharma
GitHub: github.com/imoisharma
Twitter: / imoisharma
Medium: / imoisharma
#aws #jenkins #server #demonstration #youtubeshorts #shorts #youtube #trending #amazonwebservices #devops #ogranisation #sharmio #imoisharma #Kubernetes #AWS #application #loadbalancer #trending

[@user-xe8dr6pd6y]

Great video! I would love for you to provide a demo using infrastructure as a tool, specifically Terraform.

[@sharmiochannel]

Certainly!

[@TheDevOpsGuru]

Hey sharmio, wonderful explanation!!
Could you please do the same using terraform or any IAC.

[@sharmiochannel]

sure, will do that.

[@davidibrahim129]

Thanks, Sharmio for the explanation. I have one question, please. Does the response traffic from the instance go back through the ALB or not? I do not see a need for that though, since the ALB is not a stateful firewall but I am not sure.

[@sharmiochannel]

That's correct. The primary purpose of an ALB is to distribute incoming traffic to a group of backend instances based on defined routing rules. Once the ALB forwards a request to an instance, the response traffic from that instance usually flows directly back to the client without going through the ALB again. The ALB doesn't act as a stateful firewall or inspect the response traffic in most common configurations. Instead, it relies on the stateless nature of HTTP and TCP connections, where the client maintains the connection state and knows where to expect the responses.

[@jayparkirvine6429]

Thanks, Sharmio, for the great video! Just wondering how you set the security group and the Network ACL. Do we not need to set the Outbound Rule for the security group for the load balancer with the destination of the security group of the ec2 instance, and also set the Inbound Rule for the security group for the ec2 instance with the security group of the load balancer as origin? I'm having some health check (403) issue, and my guess is it has to do with how I set up the inbound/outbound rules.

[@sharmiochannel]

Hi @jayparkirvine6429, yes you have to set up Inbound & Outbound rules according to your network configuration. If you receive 403 it usually refers to forbidden errors by the client. Please check it out here: community.jenkins.io/t/jenkins-http-status-403-forbidden-error/3214