My Jenkins Story: Configure AWS EC2 instances as non-containerized Jenkins Build Agents

This post I am going to demonstrate how to setup & configure a few ‘physical’ /’virtual’ (non-containerized) Jenkins build agents to use for building your Jenkins jobs.

So I have provisioned 3 AWS EC2 instances where one of them is the master with the other two being the build agents— by following my previous guide:

My Jenkins Story: Provisioning Jenkins (master & slaves) on AWS EC2 — using Terraform

After successfully first starting up Jenkins for the first time & gone through the initial setup wizard, when you navigate to the Nodes page under Manage Jenkins > Manage Nodes And Clouds you will likely see the following page with just the master listed as node:

This master node listed represents the master EC2 instance. To configure the other two EC2 instances as ‘build agents’ and register them to Jenkins you first need to get them to talk to each other.