> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/4.2/additional-protocols/s3/audit-s3-apis.md).

# Audit S3 APIs

This page describes how to set up an HTTP webhook for S3  audit purposes.

S3 API calls can generate JSON events that webhook target applications can receive as a stream of events and for auditing and analysis purposes. Webhook applications like Splunk must be configured to accept the events stream and provide it with an authentication token.

Enabling an audit webhook comes instead of the `BucketLogging` S3 APIs. The purpose of the audit logs is to indicate the nature of traffic.

{% hint style="info" %}
If the WEKA cluster disconnects from the webhook application or the S3 clusters' internal events buffer fills up, events are thrown away. It is recommended to monitor the external webhook target application's availability.
{% endhint %}

**Related topics**

[Configure audit webhook using the GUI](/4.2/additional-protocols/s3/audit-s3-apis/configure-audit-webhook-using-the-gui.md)

[Configure audit webhook using the CLI](/4.2/additional-protocols/s3/audit-s3-apis/audit-s3-apis.md)

[Example: How to use Splunk to audit S3](/4.2/additional-protocols/s3/audit-s3-apis/audit-s3-apis-1.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/4.2/additional-protocols/s3/audit-s3-apis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.