security_event.v1 records to Amazon S3 or compatible
object storage as newline-delimited JSON. Export scope, content detail,
encryption, replay, and delivery health are configured per destination.
See Security Exports for shared filtering,
health, multiple-destination, and replay behavior.
Events
Destination
AWS role
Role-based delivery is recommended for AWS S3. The Console generates a trust policy and a least-privilege write policy for your exact destination. The role trust policy must allow the Forge AWS principal shown in the Console to callsts:AssumeRole only when the destination’s external ID matches.
The minimum S3 permission is s3:PutObject, scoped to the configured prefix:
SSE-KMS
For SSE-KMS:- Enter the full KMS key ARN, not a key ID or alias.
- Use a key in the same AWS region as the bucket.
- Grant the delivery role
kms:Encryptandkms:GenerateDataKeyon only that key. - Ensure the KMS key policy allows the delivery role to use those permissions.
kms:Decrypt.
Filters
Detail
Supported levels aremetadata_only, indexed_summary,
full_body_reference, and full_body_inline. Prompt, tool-input, tool-output,
and raw-body inclusion are independent switches and remain bounded by available
source detail and privacy policy.
Object layout
forge_schema, organization_id, category, and batch_id.
Connection
- Open Settings → Integrations → Amazon S3 and enter the bucket, prefix, region, credentials, endpoint behavior, and encryption settings.
- For AWS role authentication, copy or apply the generated role setup and paste the resulting role ARN into Forge.
- Select event filters, detail policy, replay lookback, and delivery-state retention.
- Send a test batch. Verify the exact object key, object metadata, encryption state, and one decoded JSONL row before activating the destination.