"In the load balancing section: Type: Application load balancer Container: Jenkins 8080:8080 Select Create a new load balancer & give it a name: Jenkins-Alb Listener: In the target group: Select create new target group. Target group name: jenkins-tg Protocol: HTTP port: 8080 Deregistration delay: 300 health check protocol : HTTP health check path : /login Then click on create."
"Your service is ready, and within minutes, you will see the status as Active and the deployment as completed. It means our Jenkins master is live. To access, go to: Ec2 > Load balancing > Jenkins-ALB > Copy DNS name. You can even check the health status of the endpoint by going into the target group. It should be "healthy." Copy that DNS into a browser, and you will be able to see the Jenkins home page."
Create an ECS service named jenkins-master-service using the jenkins-master-task family with Fargate compute and the latest platform version. Attach the service to the VPC and a security group that allows Jenkins inbound ports. Configure an Application Load Balancer named Jenkins-Alb and a target group jenkins-tg on HTTP port 8080 with a /login health check and 300s deregistration delay. After the service becomes Active, copy the ALB DNS to access Jenkins and retrieve the initial admin password from task logs. Install the Amazon ECS/Fargate plugin in Jenkins and create a jenkins-agent Fargate task definition for dynamic build agents.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]