AWS Config

AWS Config is a service that enables you to assess, audit, and evaluate the configurations of your AWS resources. Config continuously monitors and records your AWS resource configurations and allows you to automate the evaluation of recorded configurations against desired configurations. With Config, you can review changes in configurations and relationships between AWS resources, dive into detailed resource configuration histories, and determine your overall compliance against the configurations specified in your internal guidelines. This enables you to simplify compliance auditing, security analysis, change management, and operational troubleshooting.

Amazon configuration

  1. On the AWS Config page, go to Settings.

  2. Here, choose the Resource types to record (specify the AWS resource types you want AWS Config to record):

    • All resources

    • Specific types


    For more information about these options, see Selecting Which Resources AWS Config Records.

  3. Select an existing S3 Bucket or create a new one.

    After these steps, it is necessary to configure the rules.

  4. Go to Services > Management Tools > CloudWatch:

  5. Select Rules on the left menu and click on the Create rule button:

  6. Select which service do you want to get logs from using the Service name slider, then, click on the Add target button and add the previously created Firehose delivery stream there. Also, create a new role to access the delivery stream:

  7. Give the rule some name and click on the Create rule button:

  8. Once the rule is created, data will start to be sent to the previously created S3 bucket. Remember to first enable the service you want to monitor, otherwise you won't get any data.

Wazuh configuration

  1. Open the Wazuh configuration file (/var/ossec/etc/ossec.conf) and add the following block:

    <wodle name="aws-s3">
      <bucket type="config">


    Check the AWS S3 module reference manual to learn more about each setting.

  2. Restart Wazuh in order to apply the changes:

    • If you're configuring a Wazuh manager:

      1. For Systemd:

      # systemctl restart wazuh-manager
      1. For SysV Init:

      # service wazuh-manager restart
    • If you're configuring a Wazuh agent:

      1. For Systemd:

      # systemctl restart wazuh-agent
      1. For SysV Init:

      # service wazuh-agent restart