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

Graylog Log Management Server

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
Email support

What's installed

Every package and version on the image, identical on every cloud it ships on. 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)

LicensingGraylog Open (SSPL-1.0), no licence key required

Deploy anywhere

Graylog Log Management Server on AWS and Azure.

Google Cloud is 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
    Available

    Amazon Web Services

    AMI · v7.1.9

    AWS AMI ID

    Shown for your region on the AWS Marketplace launch page once you subscribe.

    Released
    Root volume
    gp3 · 30 GiB
    Instance types
    • t3a.large
    • t3.large
    • m6a.large
    • m6a.xlarge
    Regions34 regions· show all
    • us-east-1
    • af-south-1
    • ap-east-1
    • ap-east-2
    • ap-northeast-1
    • ap-northeast-2
    • ap-northeast-3
    • ap-south-1
    • ap-south-2
    • ap-southeast-1
    • ap-southeast-2
    • ap-southeast-3
    • ap-southeast-4
    • ap-southeast-5
    • ap-southeast-6
    • ap-southeast-7
    • ca-central-1
    • ca-west-1
    • eu-central-1
    • eu-central-2
    • eu-north-1
    • eu-south-1
    • eu-south-2
    • eu-west-1
    • eu-west-2
    • eu-west-3
    • il-central-1
    • me-central-1
    • me-south-1
    • mx-central-1
    • sa-east-1
    • us-east-2
    • us-west-1
    • us-west-2
    Launch on AWS MarketplaceAWS launch steps

    5-day free trial, then from $0.04/hr software charge (larger instance sizes cost more) plus your own EC2 costs, billed by AWS.

    Subscriptions are open to AWS India (AISPL) accounts. Outside India? Ask us for a private build.

  2. Azure
    Coming soon

    Microsoft Azure

    Compute Gallery image · v7.2.2

    Azure Compute Gallery image ID
    …/galleries/provencloud_marketplace/images/graylog/versions/2026.11.1
    Released
    OS disk
    Premium_LRS · 30 GiB
    Gallery
    provencloud_marketplace
    Definition
    graylog
    Resource group
    provencloud-marketplace-rg
    VM sizes
    • Standard_D4as_v7
    • Standard_D4as_v5
    • Standard_D8as_v7
    Regions50 regions· show all
    • eastus
    • australiacentral
    • australiaeast
    • australiasoutheast
    • austriaeast
    • belgiumcentral
    • brazilsouth
    • canadacentral
    • canadaeast
    • centralindia
    • centralus
    • chilecentral
    • denmarkeast
    • eastasia
    • eastus2
    • francecentral
    • germanywestcentral
    • indiasouthcentral
    • indonesiacentral
    • israelcentral
    • italynorth
    • japaneast
    • japanwest
    • jioindiawest
    • koreacentral
    • koreasouth
    • malaysiawest
    • mexicocentral
    • newzealandnorth
    • northcentralus
    • northeurope
    • norwayeast
    • polandcentral
    • qatarcentral
    • southafricanorth
    • southcentralus
    • southeastasia
    • southindia
    • spaincentral
    • swedencentral
    • switzerlandnorth
    • uaenorth
    • uksouth
    • ukwest
    • westcentralus
    • westeurope
    • westindia
    • westus
    • westus2
    • westus3
    Azure launch steps
AWS

Getting started on Amazon Web Services

From launch to signed in, step by step.

  1. Subscribe on AWS Marketplace and launch in your region 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 AWS 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.

Azure

Getting started on Microsoft Azure

From launch to signed in, step by step.

  1. Create the VM from the Azure Marketplace listing with TCP 22, 80 and 8081 open in your network security group. Choose ubuntu as the administrator username so SSH and the script paths match, and wait a few minutes for first boot to finish.

  2. Open http://<vm-public-ip>/ and sign in as admin. The password is your VM ID (Azure portal > the virtual machine > Properties > VM ID, for example 02aab8a4-74ef-476e-8182-f6d2ba4166a6). Mongo Express (port 8081, user admin) uses the same password. To receive logs, create an input under System > Inputs (for example Syslog UDP on port 1514 or GELF on 12201) and open that port in your network security group. Change the admin password with sudo bash ~/iscripts/pass_graylog.sh. Choose a VM with at least 4 vCPUs and 16 GB of memory.

  3. For production, limit admin ports to your own IP address.

Security posture

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

  • Clean-room build on Canonical's official Ubuntu 24.04 LTS image from the Azure Marketplace: every component comes from its own official source and no third-party image was launched or copied.

  • No two VMs share a login: first boot sets every password and secret key from the new VM's own vmId (read from Azure IMDS) or from fresh random values, and creates new SSH host keys.

  • The ubuntu login account ships password-locked with an empty authorized_keys, and Azure installs your own SSH key at deploy time.

  • Shell history, logs and cloud-init state are cleared before capture, and the image carries every Ubuntu 24.04 LTS security update with nothing pending.

  • Each gallery version is deployed as a Trusted Launch VM and checked against Microsoft's documented Linux certification test cases, the product's own end-to-end login tests and a stop/start cycle before it is published.

  • Restrict port 22 and the admin consoles to trusted IP ranges, and put public web consoles behind HTTPS with your own certificate.