Overview
This is a repackaged software product wherein additional charges apply for hardening, security configuration, and support.
WHAT IS WAZUH
Wazuh is a free, open source security platform that unifies SIEM (Security Information and Event Management) and XDR (Extended Detection and Response) capabilities. This image runs the complete all-in-one stack on one host: the Wazuh manager (the GPLv2 analysis engine), the Wazuh indexer (an Apache-2.0 OpenSearch fork that stores and searches events), the Wazuh dashboard (an Apache-2.0 OpenSearch-Dashboards fork), and Filebeat. It performs log data analysis, intrusion and threat detection, file integrity monitoring (FIM), vulnerability detection, configuration assessment, active response, and MITRE ATT&CK mapping, with out-of-the-box regulatory compliance reporting for PCI DSS, HIPAA, NIST 800-53, and GDPR. Lightweight agents for Linux, Windows, and macOS enroll over TCP 1515/1514 and stream security telemetry to the manager. The indexer and dashboard are OpenSearch forks under Apache-2.0 - not Elastic SSPL - so the full platform is auditable with no vendor lock-in and no per-agent SaaS fees.
WHAT THIS AMI ADDS
Security hardening:
- The dashboard admin login password is generated uniquely at first boot (no admin/admin default)
- All backing-store credentials - indexer service account, manager REST API users, and Filebeat - are rotated per-instance at first boot and written to /root/wazuh-credentials.txt (mode 0600)
- The Wazuh indexer (OpenSearch) is bound to 127.0.0.1:9200 only - never exposed off-host
- The dashboard listens on 127.0.0.1:5601 and is reachable only through a TLS-terminating nginx on port 443, with a loading splash + readiness gate during startup
- UFW firewall pre-configured: only TCP 22, 443, 1514, 1515, and 55000 are open
- fail2ban, auditd, and AppArmor pre-configured
- CVE scan - every image is scanned for vulnerabilities before release
OS hardening (CIS Level 1):
- CIS Ubuntu 24.04 LTS Level 1 benchmark applied via ansible-lockdown
- auditd, SSH hardening, Kernel hardening, IMDSv2 enforced
Compliance artifacts:
- SBOM - CycloneDX 1.6 at /etc/lynxroute/sbom.json
- CIS Conformance Report at /etc/lynxroute/cis-report.html
- CIS Tailored Profile at /usr/share/doc/lynxroute/CIS_TAILORED_PROFILE.md
Highlights
- Wazuh security baked in: the dashboard admin password and every backing-store credential (indexer service account, REST API users, Filebeat) rotated per-instance at first boot, the OpenSearch indexer bound to 127.0.0.1 only, and the dashboard reachable only through a TLS nginx - unlike bare Wazuh AMIs that ship demo passwords (admin/admin), expose the indexer on port 9200, and put the dashboard straight on the public interface.
- CIS Level 1 hardened Ubuntu 24.04 LTS: auditd, fail2ban, AppArmor, SSH key-only, IMDSv2 enforced. CVE-scanned before every release. SBOM (CycloneDX) and CIS Conformance Report included.
- Full open-source SIEM and XDR: log analysis, intrusion and threat detection, file integrity monitoring, vulnerability detection, and out-of-the-box PCI DSS, HIPAA, and NIST compliance reporting. GPL-2.0 manager with Apache-2.0 OpenSearch indexer and dashboard - no SSPL, no vendor lock-in.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
|---|---|
m6i.xlarge Recommended | $0.05 |
t3.large | $0.03 |
m6i.large | $0.03 |
m6i.2xlarge | $0.07 |
Vendor refund policy
We do not offer refunds for this product. AWS infrastructure charges (EC2, EBS, data transfer) are billed separately by AWS and are not refundable by us.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Wazuh 4.14.5 - Initial release (June 2026)
- Wazuh 4.14.5 all-in-one (manager + indexer + dashboard + Filebeat) on Ubuntu 24.04 LTS
- CIS Level 1 hardening applied (ansible-lockdown/UBUNTU24-CIS)
- CVE-scanned before every release
- Dashboard admin password + all backing-store credentials (indexer, REST API, Filebeat) rotated at first boot
- OpenSearch indexer bound to 127.0.0.1 only; dashboard fronted by TLS nginx with a startup readiness gate
- UFW firewall pre-configured (ports 22, 443, 1514, 1515, 55000 only)
- fail2ban, auditd, AppArmor pre-configured
- SBOM (CycloneDX 1.6) at /etc/lynxroute/sbom.json
- CIS Conformance Report (OpenSCAP) at /etc/lynxroute/cis-report.html
- IMDSv2 enforced
Additional details
Usage instructions
- Launch instance (m6i.xlarge recommended; t3.large minimum; 50 GB disk)
- Open Security Group - allow TCP 443 (dashboard) and TCP 55000 (manager API) from your IP, and TCP 1514 + 1515 (agent events + enrollment) from the networks where your agents run
- SSH: ssh -i key.pem ubuntu@<PUBLIC_IP>
- Read credentials: sudo cat /root/wazuh-credentials.txt
- Open https://<PUBLIC_IP>/ in your browser - accept the self-signed certificate warning - and log in as admin with the password from the credentials file
- Enroll an agent: install the Wazuh agent on a host, point it at the manager (enrollment on TCP 1515, events on TCP 1514); it then appears under Agents in the dashboard
- The manager REST API is available at https://<PUBLIC_IP>:55000/
First launch takes a few minutes while the indexer warms up and security is initialized; until then the URL shows a loading page that refreshes automatically.
The dashboard admin password and all backing-store credentials are generated at first boot and saved to /root/wazuh-credentials.txt. The Wazuh indexer (port 9200) and dashboard backend (port 5601) are bound to 127.0.0.1 only and are not reachable from outside the instance. Replace the self-signed TLS certificate with a CA-signed certificate (or run sudo certbot --nginx) for production use.
Resources
Vendor resources
Support
Vendor support
Visit us online: https://lynxroute.com
For Wazuh documentation: https://documentation.wazuh.com/ For Wazuh upstream issues:
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.