Skip to content
Graylog Log Management product logo
  • AWSAvailable on Amazon Web Services
  • Azure· nextMicrosoft Azure is next on the roadmap
  • GCP· nextGoogle Cloud is next on the roadmap
Available

Graylog Log Management

Graylog Open 7.1.9 with OpenSearch 2.19 as the indexer and MongoDB 8.2, plus Mongo Express, behind an nginx reverse proxy. Every internal service is loopback-only, first boot generates a fresh password secret, node ID and clean indices, and Graylog's external URI follows your public IP on every boot.

Version
v7.1.9
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.

  • Graylog Open 7.1.9
  • OpenSearch 2.19.6
  • MongoDB 8.2.12
  • Mongo Express 1.0.2
  • nginx 1.24.0
  • Node.js 24.20.0
  • OpenJDK 21 (bundled)

Licensing — Graylog Open (SSPL-1.0), no licence key required

Deploy anywhere

Graylog Log Management 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 · v7.1.9

    Available

    AWS AMI ID

    ami-09e9752dfea822022
    Released
    September 6, 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 8081 open. Allow up to fifteen minutes - measured under three; the rest is a safety margin for the JVMs.

  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). Mongo Express is on port 8081, same username and password.

  3. Create an input under System → Inputs to start receiving logs. Graylog's REST API is at the same address.

  4. SSH as ubuntu with your key pair. Change passwords with sudo bash /home/ubuntu/iscripts/pass_graylog.sh or pass_mongoexpress.sh.

  5. Graylog's upstream telemetry default is left on; turn it off in the UI or add telemetry_enabled = false to /etc/graylog/server/server.conf.

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.

  • First boot generates a fresh 96-character Graylog password_secret and a fresh node ID, drops the build-time Graylog database and deletes the build-time indices, so no two customer instances share cryptographic material or cluster identity; it then sets the admin and Mongo Express passwords and regenerates Mongo Express's cookie and session secrets.

  • Graylog (9000), OpenSearch (9200/9300) and MongoDB (27017) are bound to 127.0.0.1 and never reachable from outside.

  • MongoDB runs without its own authentication, which is safe only because it is loopback-only.

  • MongoDB's repository key was fetched from MongoDB's own endpoint, not a third-party keyserver.

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