Skip to content
Wazuh SIEM with Grafana product logo
  • AWSAvailable on Amazon Web Services
  • AzureAvailable on Microsoft Azure
  • GCP· nextGoogle Cloud is next on the roadmap
Available

Wazuh SIEM with Grafana

The complete Wazuh 4.14.7 security platform - manager, indexer, dashboard and Filebeat - with Grafana 13.2.1 pre-wired to the indexer and a ready-made alerts dashboard. Checked line by line against the AWS Marketplace AMI policies: every credential is rotated to your instance at first boot, and the indexer never faces the internet.

Version
v4.14.7
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.

  • Wazuh manager 4.14.7
  • Wazuh indexer 4.14.7
  • Wazuh dashboard 4.14.7
  • Filebeat 7.10.2
  • Grafana OSS 13.2.1
  • OpenSearch datasource plugin 2.34.3
  • nginx 1.24.0

LicensingOpen source (GPL-2.0), no licence key required

Deploy anywhere

Wazuh SIEM with Grafana 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 · v4.14.7

    AWS AMI ID

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

    Released
    Root volume
    gp3 · 50 GiB
    Instance types
    • t3a.xlarge
    • t3a.large
    • m6a.xlarge
    • m6a.2xlarge
    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.03/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
    Available

    Microsoft Azure

    Compute Gallery image · v4.14.8

    Azure Compute Gallery image ID

    Selected for you when you create the VM from the Azure Marketplace listing.

    Released
    OS disk
    Premium_LRS · 64 GiB
    VM sizes
    • Standard_D4as_v7
    • Standard_D8as_v7
    • Standard_D4as_v5
    • Standard_D2as_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
    Launch on Azure MarketplaceAzure 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, 1514, 1515, 3000 and 55000 open; wait for the health checks. Use t3a.large as a floor, t3a.xlarge for headroom.

  2. Open http://<instance-public-ip>/ and sign in with username admin and your EC2 Instance ID with a capital I as the password: an instance shown as i-0123456789abcdef0 has the password I-0123456789abcdef0. Wazuh's policy needs an uppercase letter; nothing else changes.

  3. Grafana is at http://<instance-public-ip>:3000 and the Wazuh API at https://<instance-public-ip>:55000, same credential. The Wazuh Security Overview dashboard fills in as the manager starts auditing the host.

  4. Enrol agents on port 1515; they report on 1514.

  5. SSH as ubuntu with your key pair. Change the login everywhere at once with sudo bash /home/ubuntu/iscripts/change_login.sh; wazuh_status.sh prints this instance's exact working credential.

  6. Do not open 9200 (indexer) or 443 (the dashboard's internal HTTPS); both are loopback-only by design.

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.

  • Checked line by line against the AWS Marketplace AMI product policies: no hardcoded secrets, per-instance passwords, no SSH password authentication, no root password login, no baked-in authorized keys, full sudo for the ubuntu user.

  • The image carries only the Wazuh installer's random passwords, with Grafana's randomised during cleanup, and first boot rotates all of them to this instance's credential.

  • The Wazuh indexer (9200) and the dashboard's own HTTPS listener (443) are loopback-only and must not be opened; nginx on 80 is the documented entry point.

  • Build-time alert, archive and state indices were deleted so no build-host inventory ships. pass_wazuh.sh enforces Wazuh's own policy (10+ chars, upper, lower, digit and one of . * + ? -) and keeps Grafana's datasource credential in step.

  • 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 on a 4 vCPU size with a 64 GiB disk, and open TCP 22, 80 and 3000 in your network security group - add 55000 for the Wazuh API, and 1514 and 1515 only when you are ready to enrol agents. Choose ubuntu as the administrator username so SSH and the script paths match. Allow up to ten minutes for the first boot; the indexer is deliberately given a long start-up window.

  2. Open http://<vm-public-ip>/ for the Wazuh dashboard and http://<vm-public-ip>:3000/ for Grafana, both as admin. The Wazuh API on port 55000 uses the users wazuh and wazuh-wui with the same password.

  3. The password is VM- followed by your VM ID - the prefix is required, because the application's own password policy needs an upper-case character and an Azure VM ID is an all-lower-case GUID. In the Azure portal open the virtual machine, choose Properties and copy VM ID, then type it as VM-02aab8a4-74ef-476e-8182-f6d2ba4166a6.

  4. Typing the VM ID without the VM- prefix is the single most common reason a first login fails on this image - Wazuh's password policy rejects it.

  5. Agents enrol at <vm-public-ip>:1515 and then report on 1514. SSH as ubuntu with your key.

Security posture

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

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

  • Every Wazuh and Grafana password is set on first boot from your VM's own vmId with a `VM-` prefix, which Wazuh's password policy requires.

  • The installer's own generated passwords are deleted before capture, so what remains on disk are hashes of random strings that nothing knows.

  • The pre-image cleanup proves the build's own credentials are rejected before capture, and first boot sets every password from the new VM's own vmId, read from Azure IMDS.

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

  • Shell history, logs and cloud-init state are cleared before capture.

  • Verified against Microsoft's documented Linux certification test cases on a VM deployed from this gallery version - 13 passed, 0 failures - with VM extension provisioning confirmed and every helper script executed rather than only reviewed.

  • The indexer on 9200 and the dashboard's own HTTPS listener on 443 are loopback-only by design and the pre-image cleanup aborts if either is found on a public address - do not open those ports.

  • Restrict port 22 to trusted IP ranges, and put the consoles behind HTTPS with your own certificate before exposing them to the internet.