Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions app/authzed/concepts/audit-logging/page.mdx
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Audit Logging"
description: "AuthZed functionality that publishes detailed logs of SpiceDB API operations to log sinks like AWS Kinesis and Kinesis Firehose."
description: "AuthZed functionality that publishes detailed logs of SpiceDB API operations to log sinks like AWS Kinesis, GCP Pub/Sub, etc."
---

import { Callout, Tabs } from "nextra/components";
Expand Down Expand Up @@ -138,7 +138,7 @@ For Dedicated customers, this role will also need a trust policy which allows th
in order to deliver logs to the stream.

To find the Dedicated AWS account ID, navigate to the Permission System's settings page, find the Audit Log settings,
and choose "AWS Kinesis" or "AWS Kinesis Firehose" as the log sink.
and choose an available log sink.
The account ID will be displayed in the configuration.

This is an example trust policy that allows the AuthZed account to assume the role:
Expand All @@ -163,6 +163,19 @@ This is an example trust policy that allows the AuthZed account to assume the ro
}
```

### GCP Pub/Sub

As a prerequisite to use [Pub/Sub] as a log sink, the **Storage Object Admin** role of the target GCP account
must be granted to the service account being used by SpiceDB Enterprise.

[Pub/Sub]: https://docs.cloud.google.com/pubsub/docs/overview

#### Dedicated

To find the Dedicated GCP service account ID, navigate to the Permission System's settings page, find the Audit Log settings,
and choose an available log sink.
The service account ID will be displayed in the configuration.

## Configuration

The process for setting up audit logging varies depending on the AuthZed product you're using.
Expand Down
Loading