Skip to content
SonarQube Code Quality product logo
  • AWSAvailable on Amazon Web Services
  • Azure· nextMicrosoft Azure is next on the roadmap
  • GCP· nextGoogle Cloud is next on the roadmap
Available

SonarQube Code Quality

SonarQube Community Build 26.9.0 on Java 21 with PostgreSQL 16, published through Apache on port 80, with Webmin for the host. The admin credential is staged before SonarQube's first start with no forced reset and no default-credential banner, PostgreSQL never faces the internet, and telemetry is off.

Version
v26.9.0
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.

  • SonarQube Community Build 26.9.0
  • OpenJDK 21.0.12
  • PostgreSQL 16.15
  • Apache 2.4.58
  • Webmin 2.660

Licensing — SonarQube Community Build (LGPL-3.0), no licence key required

Deploy anywhere

SonarQube Code Quality 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 · v26.9.0

    Available

    AWS AMI ID

    ami-0e8d7891a89410da5
    Released
    September 15, 2026
    Root volume
    gp3 · 30 GiB

    Instance types

    • t3a.medium
    • t3a.large
    • m6a.large
    • m6a.xlarge

    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, 80 and 8000 open; allow about ten minutes - three JVMs, embedded Elasticsearch and migrations start first. GET /api/system/status returning UP is the real readiness signal.

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

  3. Webmin: http://<instance-public-ip>:8000, username admin or root, same password.

  4. PostgreSQL is local-only: sudo -u postgres psql over SSH, or tunnel with ssh -L 5432:127.0.0.1:5432 ubuntu@<instance-public-ip> and connect as postgres with the Instance ID.

  5. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_sonarqube.sh, pass_postgres.sh or pass_webmin.sh (12+ characters). Use t3a.large or larger for real analysis volume.

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.

  • A systemd unit ordered before SonarQube sets the admin password, clears the forced reset, removes the default-credential flag, and deletes the server ID so SonarQube mints one unique to this instance on its first start; a second first-boot pass verifies the login and repairs it if needed.

  • SonarQube (9000) and its embedded Elasticsearch (9001) are loopback-only behind Apache, and PostgreSQL admits only 127.0.0.1 - verified from outside on a launched instance.

  • Telemetry is disabled.

  • The password is written as a PBKDF2 hash directly, because SonarQube's own API rejects a lowercase Instance ID; the parameters were confirmed by reproducing a hash SonarQube itself had written.

  • 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.