# Get started

Configure an Amazon S3 log destination and confirm activity log delivery.

> Security log streaming is available to approved accounts. To request access, email [security-product@stripe.com](mailto:security-product@stripe.com). After Stripe enables your account, configure a destination in the Dashboard.

Set up bucket permissions, configure a destination in the Dashboard, and inspect a delivered activity log file.

## Before you begin

You need:

- A Stripe account enabled for the private preview.
- Access to configure log destinations in the Stripe Dashboard.
- An AWS account where you can create or use an S3 bucket and update its bucket policy.
- The 12-digit AWS account ID of the account that owns the bucket.
- Permission to read the delivered objects using your own AWS identity or ingestion system.

Stripe uses a Stripe-owned AWS role, called the Stripe log-delivery role, with short-lived credentials to deliver logs. You don’t need to create an IAM role or provide AWS access keys to Stripe.

Before setting up your bucket, check your AWS account’s policies:

- For AWS accounts created after September 2026 outside an existing AWS Organization, use **Sign up for AWS (advanced)** instead of **Sign up for AWS (new)**. The new flow uses AWS-managed resource control policies (RCPs) that block Stripe from writing objects to your bucket. See [AWS sign-up options](https://docs.aws.amazon.com/accounts/latest/reference/sign-up-for-aws.html).
- If your AWS account belongs to an AWS Organization, check that its RCPs allow the Stripe AWS accounts to write to your bucket. If you need an exception, use the Stripe AWS account ID shown in the Dashboard destination creation form.

## Create or choose an S3 bucket

In the Amazon S3 console, create a dedicated **General purpose** bucket or choose an existing general purpose bucket for your activity logs. Don’t use a **Directory** bucket.

When creating a bucket:

- We recommend selecting **Account Regional namespace**.
- Keep **Block Public Access** enabled.
- Set **Object Ownership** to **Bucket owner enforced** so that your AWS account owns the delivered objects.

After configuring the bucket settings, click **Create bucket** in the Amazon S3 console. After creation, you can optionally configure retention and read access according to your organization’s policies.

Record the bucket name and the 12-digit AWS account ID of the account that owns it.

## Enter your destination details

After Stripe enables your account, select that account in the Dashboard and open **Settings**. Under **Product settings**, click **Security logs and alerts**. You can configure one destination per log type.

1. Click **Add destination**.
2. Confirm that **Log type** is **Activity logs** and **Destination type** is **Amazon S3**.
3. Optionally, choose a prefix, such as `stripe-logs/`, to separate Stripe activity logs from other objects in your bucket. Include it in the **S3 bucket URL**.
4. Enter the following information:

| Field | Value |
| --- | --- |
| **Destination name** | A descriptive name, such as `Production security logs`. |
| **S3 bucket URL** | Enter `s3://<bucket-name>`, replacing `<bucket-name>` with the bucket name you recorded. To use a prefix, enter `s3://<bucket-name>/<prefix>/` instead. |
| **AWS account ID** | The 12-digit ID of the AWS account that owns the bucket. |

For example, a bucket named `example-security-logs` with the prefix `stripe-logs/` has this S3 bucket URL:

```text
s3://example-security-logs/stripe-logs/
```

Keep the form open while you configure the bucket policy.

## Grant Stripe write access

Copy the policy from **Bucket policy** in the Stripe Dashboard destination form. The Dashboard fills in your bucket name and optional prefix from the destination details you entered.

In the Amazon S3 console, open your bucket’s **Permissions** and edit the bucket policy. Paste the copied policy. If a policy already exists, add the copied statements to its `Statement` array without replacing existing statements. Save the bucket policy.

Configure permissions separately for the people and systems that need to read your activity logs.

For customer-managed AWS Key Management Service (AWS KMS) encryption, the key policy must authorize the Stripe log-delivery role to use the key for delivery. The S3 bucket policy alone doesn’t grant KMS permissions. Have your AWS administrator confirm the key permissions before continuing.

## Create your destination

Return to the Dashboard and click **Create destination**. After Stripe saves the destination, the Dashboard returns to the log destination settings. Saving doesn’t verify S3 access or confirm log delivery.

If you can’t save the destination, see [Resolve setup problems](https://docs.stripe.com/security/logs-and-alerts/get-started.md#resolve-setup-problems).

## Confirm delivery

After a supported activity occurs on your Stripe account, check the configured bucket and prefix for delivered files. See [Tracked action types](https://docs.stripe.com/activity-logs.md#tracked-action-types) to identify supported activity.

Activity log files use this path structure. Values in angle brackets are placeholders:

```text
s3://<bucket-name>/<prefix>/<account>/by-date/<date>/<timestamp>-<id>.jsonl.gz
```

Replace `<bucket-name>` and `<prefix>` with your bucket name and optional prefix. If you don’t use a prefix, omit `<prefix>/`. `<account>` is the source account identifier. `<date>` and `<timestamp>` reflect when Stripe published the activity log for delivery, in UTC. For example, `<date>` is `2026-01-15` and `<timestamp>` is `2026-01-15-14-30-05`. `<id>` identifies the file, not the activity log.

Download a file and decompress it with a gzip-compatible tool. Each JSONL record contains:

| Property | Description |
| --- | --- |
| `delivered` | The timestamp of the delivery attempt. |
| `data` | The activity log data. Properties with default values can be omitted. For example, `livemode` can be absent when its value is `false`. |
| `data.id` | The activity log ID. Use it to deduplicate records. |

For supported action types and links to the activity log schema, see [Activity logs](https://docs.stripe.com/activity-logs.md).

If you use a security information and event management (SIEM) system, also confirm that its ingestion process reads and parses the delivered files.

## Resolve setup problems 

If setup or delivery fails, use these checks to identify the problem:

| Problem | What to check |
| --- | --- |
| You can’t find the log destination settings. | Confirm that Stripe enabled the correct account and that you have access to configure destinations. Contact [security-product@stripe.com](mailto:security-product@stripe.com) if the settings remain unavailable. |
| You can’t save the destination. | Review the form errors. Check the **S3 bucket URL** and the 12-digit **AWS account ID**. If you already have an activity log destination, edit it instead of creating another. |
| No activity log files appear. | Confirm that supported activity occurred after setup. Check the bucket name, prefix, and **AWS account ID** against your destination settings. |
| Files still don’t appear after checking the destination details. | Confirm that the bucket policy includes the statements from the Dashboard and allows writes to the configured prefix. Check applicable explicit `Deny` policies, including organizational resource control policies. |
| Files don’t appear in a bucket with encryption requirements. | Check the bucket policy and any customer-managed KMS key policy. Stripe doesn’t send the `x-amz-server-side-encryption` header. A bucket policy that denies writes without that header prevents delivery. |

For help, email [security-product@stripe.com](mailto:security-product@stripe.com) with your Stripe account ID, destination name, and the error or delivery problem you see. Don’t include AWS credentials or log contents.
