-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Custom Logs Buckets documentation #6254
Conversation
b482198
to
40767aa
Compare
40767aa
to
457622d
Compare
457622d
to
7f153b0
Compare
source/cloud-security/amazon/services/supported-services/custom-buckets.rst
Outdated
Show resolved
Hide resolved
source/cloud-security/amazon/services/supported-services/custom-buckets.rst
Outdated
Show resolved
Hide resolved
`Amazon Simple Queue Service (Amazon SQS) <https://aws.amazon.com/sqs/>`_ is a fully managed message queuing service that offers secure, durable, and available hosted queues to decouple and scale software systems and components. | ||
It allows sending, storing, and receiving messages between software components at any volume, without losing messages or requiring other services to be available. These features make it an optimal component to associate with Amazon S3 Buckets to consume any type of log. | ||
|
||
Combining Amazon SQS with Amazon S3 buckets, allows Wazuh to fetch any JSON, CSV or plain text logs, originated in AWS or not, and process the events inside them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not clear enough. What's new to Wazuh about fetching logs and processing the events inside?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The difference with what already exists is the following:
- Currently, all Wazuh's AWS integrations to read logs stored in buckets like Cloudtrail, Macie, etc. they require specifying the path in the configuration and that the logs are saved in a defined and very strict folder structure. These structures are the ones that can be consulted here (Paths to logs). Wazuh directly accessed those paths and downloaded the items found inside.
- Now, this new feature of
Custom Logs Buckets
allows to read logs stored in any path of a bucket, even from multiple buckets. In addition, it allows one to do it in a distributed and simultaneous way with different managers or Wazuh agents, without duplicating logs. This is done because the bucket publishes a notification to the SQS queue containing the full path of each new file stored in it. The notification is consumed only once, so it won't duplicate alerts.
|
||
The steps to have an S3 bucket reporting creation events are: | ||
|
||
#. Configure an S3 bucket as defined in the :ref:`Configuring an S3 Bucket <s3_bucket>` section with the name provided in the previous section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What previous section? What name provided?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
The available authentication methods are :ref:`IAM Roles <iam_roles>` or :ref:`Profiles <aws_profile>`. | ||
|
||
* ``<profile>``: A valid profile name from a Shared Credential File or AWS Config File with the permission to read logs from the bucket. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* ``<profile>``: A valid profile name from a Shared Credential File or AWS Config File with the permission to read logs from the bucket. | |
* ``<aws_profile>``: A valid profile name from a Shared Credential File or AWS Config File with the permission to read logs from the bucket. |
@@ -252,3 +252,7 @@ Error codes reference | |||
+-----------+-------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ | |||
| 21 | Failed fetch/delete from SQS | Check that no more instances of the wodle are running at the same time. | | |||
+-----------+-------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ | |||
| 22 | Invalid region | Check the provided ``region`` in the ``ossec.conf`` file. | | |||
+-----------+-------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+ | |||
| 23 | Profile not found | Check the provided ``profile`` in the ``ossec.conf`` file. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 23 | Profile not found | Check the provided ``profile`` in the ``ossec.conf`` file. | | |
| 23 | Profile not found | Check the provided ``aws_profile`` in the ``ossec.conf`` file. | |
Description
This PR adds the documentation for the new Custom Logs Buckets feature to be included in wazuh/wazuh#13577, adding new parameters for the AWS module reference and extending the available
<subscriber>
values.Checks
code
font for Bash commands, file names, REST paths, and code.redirects.js
script if necessary (check this guide).