Wazuh

Deploy Wazuh, an open source security monitoring platform for detecting threats, intrusion attempts, system anomalies, misconfigurations, and unauthorized activity. It also provides a framework for incident response and compliance monitoring.

1. Deploy Wazuh

 Estimated deployment time: 10–15 minutes

Follow the deployment instructions from the Get started section to configure the app, deploy it, and verify software installation.

For information on the app-specific configurations, see the Configuration options section.

Base distribution and plan

  • Supported distribution: Ubuntu 24.04 LTS
  • Recommended plans: Use at least a 4GB Compute Instance. For production, use an 8-core plan with 32GB RAM or higher.

Configuration options

Configure the required options to deploy your instance. For additional customization, add advanced options.

The table maps the Cloud Manager UI fields to their corresponding API/CLI keys (stackscript_data) required for automated deployments.

StackScript ID: 913276

UI field API/CLI key Description
Required options
Email address (for the Let's Encrypt SSL certificate) soa_email_address Your email address to use for generating SSL certificates.
Limited sudo user user_name Your preferred username for the limited sudo user entered without any capital letters, spaces, or special characters.
When adding a limited sudo user, the user is created with a strong generated password for your new Linode instance, and the account is assigned to the sudo group, which provides elevated permissions when running commands with the sudo prefix.
Note: For easier and more secure access with the sudo user, add an account SSH key for the Cloud Manager user during deployment and select that user as an authorized_user. Their SSH pubkey will be assigned to both the root and limited user.
Advanced options
Disable root access over SSH disable_root Applies to a limited sudo user. To block the root user from logging in over SSH, select Yes. Defaults to No.
Note: When you disable the root user from logging in over SSH and don't provide a valid Account SSH Key assigned to the authorized_user, you can still switch to the root user. To do that, log in as root via the Lish console and run cat /home/$USERNAME/.credentials to view the generated password for the limited sudo user.
Linode API token token_password Applies to a custom domain. The Linode API token if you want to use Linode’s DNS Manager to manage DNS records for your custom domain. Follow Manage personal access tokens to get your token on your account with Read/Write access to Domains.
  • If you provide the token along with the subdomain and domain, the installation attempts to create DNS records via the Linode API.
  • If you don't provide the token, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance.
SubdomainsubdomainApplies to a custom domain. The subdomain you want to use, like blog for blog.example.com. Use it only if you specify a Domain.
DomaindomainApplies to a custom domain. The domain name you want to use, like example.com. Use it only if you specify a Linode API token.
Optional data exporter Add-onsadd_onsAn option to include add-ons for your deployment. Possible values are:
  • none (default)
  • node_exporter
  • mysqld_exporter
  • newrelic

Notes:

  • After the app deployment completes, the password for your limited sudo user is generated and stored in the .credentials file in the home directory, along with all of your Wazuh credentials. Log in to your instance as root through the Lish console or SSH, then run cat /home/$USERNAME/.credentials to view its contents.
  • You can automatically configure a custom domain (optional) during deployment. To do that:
    1. First, configure your domain to use Linode’s name servers via your registrar. See Configure your domain's authoritative name servers for details.
    2. Once you complete that, specify the Linode API token, subdomain, and domain for the app in Cloud Manager or via API/CLI/Terraform.

Use API, CLI, or Terraform

In addition to deploying the app to a new Linode instance via Cloud Manager, you can also use the Linode API, CLI, or Terraform. When running the operation, you need to provide the StackScript ID, supported Linux distribution, and app-specific fields along with the standard Linode deployment configurations.

Note: Generate a personal access token to authenticate your API, CLI, or Terraform requests.

curl --location 'https://api.linode.com/v4/linode/instances' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer abc123def456hij789klm' \
  --data-raw '{
    "region": "us-east",
    "type": "g6-standard-4",
    "image": "linode/ubuntu24.04",
    "label": "my-wazuh-one-click-app",
    "root_pass": "@C0mpl3x#P@ssw0rd",
    "stackscript_id": 913276,
    "stackscript_data": {
      "soa_email_address": "jsmith@example.com",
      "user_name": "jsmith"
    }
  }'
linode-cli linodes create \
  --region us-east \
  --type g6-standard-4 \
  --label my-wazuh-one-click-app \
  --image linode/ubuntu24.04 \
  --root_pass @C0mpl3x#P@ssw0rd \
  --stackscript_id 913276 \
  --stackscript_data '{"soa_email_address":"jsmith@example.com", "user_name":"jsmith"}'
resource "linode_instance" "my-linode" {
  region         = "us-east"
  type           = "g6-standard-4"
  label          = "my-wazuh-one-click-app"
  image          = "linode/ubuntu24.04"
  root_pass      = "@C0mpl3x#P@ssw0rd"
  stackscript_id = 913276
  stackscript_data = {
    "soa_email_address" = "jsmith@example.com"
    "user_name"         = "jsmith"
  }
}

2. Access the Wazuh app

  1. Open a web browser and navigate to the domain you entered when creating the https://[domain] instance, replacing [domain] with your custom domain. If you didn't enter a domain, use your Linode instance's default rDNS domain such as 192-0-2-1.ip.linodeusercontent.com.

    See the Manage IP addresses on a Linode guide for information on viewing the rDNS value.

    To securely access your website, prefix the URL with https.

  2. On the Wazuh login page, enter admin as the username and the corresponding password from the .credentials file.

Set up a Wazuh agent

Now that you’ve accessed your Wazuh instance, you need to configure a Wazuh agent on the server you’d like to monitor with Wazuh.

  1. Before adding the agent, allow the monitored server to reach ports 1514 and 1515 on your Wazuh instance by running these commands:

    sudo ufw allow from $AGENTSERVERIP to any port 1514 proto tcp
    sudo ufw allow from $AGENTSERVERIP to any port 1515 proto tcp

    Replace $AGENTSERVERIP with the IP address of the server where you plan to install the Wazuh agent.

  2. Once the firewall rules are added, follow the steps in the Wazuh UI to deploy the Wazuh agent. The agent installation asks you for the following details:

    • The system package you're installing the agent on: RPM, DEB, Windows, macOS. For example, DEB amd64.
    • The server address: Your newly installed Wazuh instance's domain or IP address. For example, my-domain.com.
    • An agent name: The ID for the instance you're installing the agent on. For example, database1.
    wget https://packages.wazuh.com/4.x/apt/pool/main/w/wazuh-agent/wazuh-agent_4.7.5-1_amd64.deb && sudo WAZUH_MANAGER='my-domain.com' WAZUH_AGENT_NAME='database1' dpkg -i ./wazuh-agent_4.7.5-1_amd64.deb
  3. Once you enter that information, Wazuh displays the installation commands.

    sudo systemctl daemon-reload
    sudo systemctl enable wazuh-agent
    sudo systemctl start wazuh-agent

Additional resources

For more information about the installed packages, see their official documentation.

📘

Note that we can't vouch for the accuracy or timeliness of externally hosted resources.


Did this page help you?