Serverless Cost-Efficient CI/CD with Jenkins on AWS Fargate: Dynamic Agents and Persistent Storage...
Briefly

Serverless Cost-Efficient CI/CD with Jenkins on AWS Fargate: Dynamic Agents and Persistent Storage...
"Give a service name: jenkins-master-service In the environment: Compute option: launch Type > Fargate Platform version : Latest In the Networking section, select the same VPC in which you have created EFS and select a Security Group (SG); select either the default or create a new one. Remember, in your SG, these ports must be allowed as an inbound rule. 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."
Create an ECS service named jenkins-master-service using Fargate and the jenkins-master-task task definition. Configure networking to use the VPC with EFS and a security group permitting Jenkins ports. Attach an Application Load Balancer named Jenkins-Alb, map container port 8080, and create a target group jenkins-tg on HTTP port 8080 with a /login health check and 300s deregistration delay. Access Jenkins via the ALB DNS and retrieve the initial admin password from the task logs. Install the Amazon ECS/Fargate plugin in Jenkins and create a jenkins-agent Fargate task definition with Linux x86_64, 1 CPU, 3 GB memory and an appropriate task role for dynamic agents.
Read at Medium
Unable to calculate read time
[
|
]