Jenkins 2.x AMI by Kurian

Kurian edited this page Jan 17, 2018 · 8 revisions

Jenkins Automation Server

Jenkins has been used for various DevOps automation tasks mainly build, CI/CD and deployment

When an AWS EC2 node is spun up using Kurian’s Jenkins AMI, Jenkins automation server is up & running and fully functional, with all the important plugins, latest version of JDK and C/C++ compilers. You can start setting up build jobs on the preconfigured Jenkins CI platform right away.

All the necessary dependent software, mainly OpenJDK, have been baked into the AMI, pre-installed and configured.


  • The AMI has latest Jenkins Continuous Integration platform pre-installed and configured, with the dependent applications.
  • The AMI has all the important plugins preinstalled.
  • The AMI has Oracle JDK 1.8, gcc and g++ compilers, and AWS CLI preinstalled.

How It Works

Jenkins is a Java based application and usual steps are the following, but, it can differ depending on the target OS platform:

  • Install OpenJDK.
  • Install Jenkins package.

Though the above steps are not very hard, it requires some technical skills to get everything right for Jenkins to be up and running. Also, it requires many plugins to be usable in a real-life development environment.

The Kurian’s AMI comes with all the above steps baked in, so the EC2 node spun up from it will be usable from the get-go.

Supported Platforms

Click on the links below to take you to Amazon Marketplace for spinning up EC2 nodes.

AMIs for specific Jenkins and OS versions can be created upon request. Please contact with your requirements.


  • After the node is up and running fully, access Jenkins UI using url: http://NODE-IP:8080.
  • SSH into the EC2 node and obtain password for the admin user from /var/lib/jenkins/secrets/initialAdminPassword
    • sudo cat /var/lib/jenkins/secrets/initialAdminPassword
  • Login as user ‘admin’. Change admin password soon after you login.
  • Rest of the configuration steps are application specific and refer product documentation for details.


An existing Jenkins instance can be migrated to a Jenkins instance spun up from latest version of AMI. Usually that is performed by syncing the JENKINS_HOME directory from old instance to the new instance. However, a specific case of migration can be different and please consult the Jenkins documentation for that.

For help, contact us by email with details of your migration scenario.

Maintenance and Troubleshooting

Kurian can help with configuring Jenkins for your specific needs. Contact us with details to

Remote Access to EC2 Node

Jenkins runs on port 8080 and that must be opened to the network from where you plan to access the application.

The EC2 node can be accessed using any SSL based remote access clients on port 22, using the ssh key you have selected when the node is spun up.

Following are the predefined users available when a node is provisioned:

  • Amazon Linux: ec2-user
  • Red Hat Linux: ec2-user
  • SuSE Linux: ec2-user
  • Fedora: fedora
  • CentOS: centos
  • Debian Linux: admin
  • Ubuntu: ubuntu