> 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/5.1/additional-protocols/s3/audit-s3-apis.md).

# Audit S3 APIs

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

Configuring HTTP webhooks for S3 API operations enables the capture of detailed audit logs, which are essential for analyzing access patterns, supporting security and compliance initiatives, and troubleshooting issues in S3 interactions.

S3 API calls can generate JSON-formatted audit events, which are streamed to target applications such as Splunk for real-time monitoring and analysis. This approach replaces the legacy `BucketLogging` S3 APIs with a more robust and scalable auditing solution. Each event provides granular details about the operation, including the request type, object affected, requester identity, and network metadata.

For example, an audit event generated by a `PutObject` operation includes fields such as the bucket name, object key, operation status, client IP address, user agent, and the WEKA cluster information that processed the request. These elements are crucial for tracing user activity, validating policy compliance, and performing forensic investigations. By understanding the structure and key fields in these logs, users can ensure that operations conform to expected behavior and promptly identify unauthorized access.

{% hint style="info" %}
If the WEKA cluster loses connectivity to the configured webhook application or if the internal event buffer reaches capacity, audit events are discarded. To avoid data loss, it is strongly recommended that the availability and performance of the external webhook target be continuously monitored.
{% endhint %}

**Related topics**

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

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

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

[Example: How to use S3 audit events for tracking and security](/5.1/additional-protocols/s3/audit-s3-apis/example-how-to-use-s3-audit-events-for-tracking-and-security.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/5.1/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.