Battle-tested way to configure a Jenkins server on AWS using IaC/CaC?

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • Scout APM - Less time debugging, more time building
  • OPS - Build and Run Open Source Unikernels
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
  • GitHub repo terraform-aws-jenkins

    Terraform module to build Docker image with Jenkins, save it to an ECR repo, and deploy to Elastic Beanstalk running Docker stack

    Are you planning to use Kubernetes or just roll it out on standard EC2 instances? If the latter, check out the CloudPosse terraform module, they always have good stuff.

  • GitHub repo helm-charts

    Jenkins community Helm charts (by jenkinsci)

  • Scout APM

    Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.

  • GitHub repo kubernetes-operator

    Kubernetes native Jenkins Operator

    You mean this operator?

  • GitHub repo terraform-provider-jenkins

    Jenkins Terraform Provider

    Personally I manage and create my jobs manually in jenkins, but terraform does have a Jenkins provider to allow you to create your jobs via IAC (Infrastructure as Code) if you want to be 100% IAC. This has been a very successful solution for out team. I must give a disclaimer though, while we have jobs to build & deploy all of our apps from src, we generally rely on CircleCi for it. We keep the jenkins build jobs up to date and only use them when CircleCi is down (Which has been much less the last year). In addition to that we (the devops team) use jenkins to run all of our repetitive tasks like a fancy cron service. Things such as reset dev databases, backup or github repo to a second location, run password rotations, recycle services etc.

  • GitHub repo reform

    helpful terraform wrapper for templates, secrets and easy organization (by analogrithems)

    I wrote a simple tool that my company let me OpenSource called reform (Seamless Plug). I have a dir called configs that has a subdir for each env {dev, stage, prod, global} in it. I also keep a dedicated git branch per env {dev, stage, prod, global} so i can do R&D in dev. Once I verify it works right I merge to stage.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts