Monitoring AWS infrastructure

This use case shows how the Wazuh module for AWS (aws-s3) enables the log data collection from different AWS sources.

To learn more about monitoring AWS resources, see the Using Wazuh to monitor AWS section of the documentation.


Cloud service


Amazon CloudTrail

AWS Cloudtrail, like all other supported AWS services, requires providing a valid authentication method. For this PoC, we use the profile authentication method.


Take the following steps to configure Wazuh to monitor Amazon CloudTrail services and identify security incidents.


  1. Access the CloudTrail service using the AWS console.

  2. Create a new trail.

  3. Choose between creating a new S3 bucket or specifying an existing one to store CloudTrail logs. Note down the name of the S3 bucket used as it’s necessary to specify it in the Wazuh configuration.

The image below shows how to create a new CloudTrail service and attach a new S3 bucket.

Wazuh server

  1. Enable the Wazuh AWS module in the /var/ossec/etc/ossec.conf configuration file on the Wazuh server. Add only the AWS buckets of interest. Read our guide on how to Configure AWS credentials:

    <wodle name="aws-s3">
      <bucket type="cloudtrail">
  2. Restart the Wazuh manager to apply the changes:

    $ sudo systemctl restart wazuh-manager

Test the configuration

Once you configure Cloudtrail, you can generate events by simply creating a new IAM user account using the IAM service. This generates an event that Wazuh processes.

The Wazuh default ruleset parses AWS logs and generates alerts automatically. The alerts appear as soon as Wazuh receives the logs from the AWS S3 bucket.

You can also find additional CloudTrail use cases in our documentation.

Visualize the alerts

You can visualize the alert data in the Wazuh dashboard. To do this, navigate through Amazon Web Services module.