1. Concepts
Settings > S3 Ingestion is where an organization connects an AWS S3 bucket to Zenskar so usage event files uploaded to that bucket are ingested automatically. This tab manages one connection for the whole organization. Enabling ingestion for a specific usage event, and choosing which folder in the bucket that event reads from, happens separately, when creating or editing a usage event, not on this tab. For the full AWS-side setup, see Set up S3 event sync.
Processor Role ARN and SQS Queue ARN
Zenskar provides a Processor Role ARN and an SQS Queue ARN on this tab. These identify the AWS role and queue Zenskar uses to read from S3 buckets and receive event notifications, and the same values are shown to every organization in a given Zenskar environment. Access to a specific bucket depends entirely on that bucket’s own policy granting the Processor Role ARN read permission, not on these ARNs being unique per organization.
Region requirement
The S3 bucket and its event notifications must be in the us-east-1 AWS region. Buckets in other regions cannot be used.
Connection status is not a live connectivity check
The Connected or Not Connected status on this tab reflects only whether ingestion is enabled and a bucket name has been saved. It does not verify that Zenskar can actually reach the bucket, that the bucket policy is correct, or that the bucket is in the right region. A configuration can show Connected even when the AWS-side setup is incomplete. Upload a test file to confirm ingestion is working end to end.
2. How-to guides
Find the Processor Role ARN and SQS Queue ARN
Go to Settings > S3 Ingestion. The Processor Role ARN and SQS Queue ARN are shown read-only, each with a copy action. These values are needed to configure the bucket policy and event notifications on the AWS side.
Connect an S3 bucket
- Go to Settings > S3 Ingestion.
- Enter the S3 Bucket Name, without the
s3:// prefix.
- Optionally enter an Ingestion Error Bucket, a location where events that fail validation are logged. Left empty, failed events are not captured anywhere.
- Click Save Config.
Complete the AWS-side bucket policy and event notification setup separately. See Set up S3 event sync.
Disconnect an S3 bucket
- Go to Settings > S3 Ingestion.
- Use Disconnect S3 Bucket.
- Confirm the action.
Enable ingestion for a specific usage event
This is configured on the usage event itself, not on this tab. See Set up S3 event sync.
Troubleshooting
- Status shows Connected but no events are being ingested: Connected only means a bucket name is saved; it does not confirm the AWS-side setup is correct. Verify the bucket policy grants the Processor Role ARN read access, the bucket is in us-east-1, and event notifications are configured to the SQS Queue ARN shown on this tab.
- Failed events are not appearing anywhere: an Ingestion Error Bucket was not set. Add one and save to start capturing failed events going forward.
3. Reference
Location
Settings > S3 Ingestion.
Fields
Actions
Status values
Scope
One S3 Ingestion configuration exists per organization. It is not scoped per business entity.
Region requirement
The S3 bucket must be in us-east-1. The SQS queue and the bucket must be in the same AWS region for event notifications to work.
