Skip to content
Jenkins CI Server product logo
  • AWSAvailable on Amazon Web Services
  • Azure· nextMicrosoft Azure is next on the roadmap
  • GCP· nextGoogle Cloud is next on the roadmap
Available

Jenkins CI Server

Jenkins 2.568.3 LTS with 96 plugins, Java 21, Maven, Gradle, Ant, Node.js 24 and Docker CE, behind an nginx reverse proxy. A complete single-node CI server that builds and runs containers out of the box, with the setup wizard already done, a daily backup of jobs and credentials, and a per-instance admin account and secret key generated at first boot.

Version
v2.568.3
Operating system
Ubuntu 24.04 LTS
Architecture
x86_64
Support
Community

What's installed

Every package and version on the image. Nothing else is installed.

  • Jenkins 2.568.3 LTS
  • OpenJDK 21.0.12
  • Maven 3.9.16
  • Gradle 9.7.1
  • Ant 1.10.14
  • Node.js 24.21.0
  • Docker CE 29.8.0
  • Git 2.43.0
  • nginx 1.24.0

Licensing — Open source (MIT), no licence key required

Deploy anywhere

Jenkins CI Server on AWS.

Microsoft Azure and Google Cloud are next on the roadmap. One clean-room build, one first-boot credential model, one patch cadence — identical on every cloud you run. Every identifier below is the real one; copy it and launch.

  1. AWS

    Amazon Web Services

    AMI · v2.568.3

    Available

    AWS AMI ID

    ami-07972685e42db3193
    Released
    September 12, 2026
    Root volume
    gp3 · 20 GiB

    Instance types

    • t3a.medium
    • t3.medium
    • t3a.large
    • m6a.large

    Regions

    • us-east-1
    AWS launch steps

Getting started

From launch to signed in, step by step.

  1. Launch in us-east-1 with TCP 22 and 80 open; wait about two minutes for first boot.

  2. Open http://<instance-public-ip>/ and sign in with username admin and your EC2 Instance ID as the password, exactly as the console shows it (for example i-0123456789abcdef0).

  3. The jenkins user is in the docker group, and JAVA_HOME, MAVEN_HOME and GRADLE_HOME are exported system-wide, so pipelines can build with any of them immediately.

  4. Backups run daily at 00:00 into /home/ubuntu/backups/jenkins (seven days kept), with a plugin manifest for one-command plugin restore.

  5. SSH as ubuntu with your key pair. Change the admin credential with sudo bash /home/ubuntu/iscripts/pass_jenkins.sh; jenkins_status.sh shows versions, services, root URL and job count.

  6. The Jenkins root URL is re-synced on every boot, so a stop/start that changes your IP needs no fix. Set your own hostname and it is left alone.

Security posture

What this image does and does not ship with, one fact per line.

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image: every component comes from its own official repository or release, nothing is copied from any third-party image, and the finished image was scanned for third-party vendor strings before capture.

  • No usable credential ships in the image; passwords are set on your instance at first boot from EC2 instance metadata (IMDSv2) and the scripts that set them delete themselves afterwards.

  • SSH is key-only, root login over SSH is refused, and build-time SSH keys, shell history and logs were removed before imaging.

  • No admin account is baked into the image, deliberately: Jenkins derives user directories from secret.key, the key that encrypts stored credentials, so a pre-made account would force every customer instance to share one.

  • Both the account and secret.key are generated per instance at first boot, together with master.key, the instance identity and telemetry id.

  • The Jenkins servlet listens on 127.0.0.1:8080 only; nginx on port 80 is the sole public web listener.

  • A recovery script recreates the admin account if first boot was ever interrupted.

  • The bundled password tools enforce at least 10 characters with upper- and lower-case letters, a number and a symbol, and verify the new credential with a real sign-in before reporting success.

  • The image is HTTP-only by design so it works at a bare IP with no certificate warnings: terminate TLS at a load balancer or add a certificate before exposing it publicly, and restrict port 22 and any admin ports to trusted IP ranges in your security group.