AWS S3

Connect a bucket you own so ept can index objects under one prefix. ept does not store your AWS access keys.

Back to Integrations Overview

Requirements

• Bucket region us-east-1
• The 12-digit AWS account id that owns the bucket
• A non-empty prefix (dir_name), for example prod or docs/handbook
• Permission in that account to edit the bucket policy and event notifications

What ept does

1. List and read objects under your prefix (scraper + helper roles from the policy on the knowledge source page).
2. Copy content into ept-managed storage for indexing. Downstream services do not need lasting access to your bucket.
3. React to creates and deletes under the prefix via an S3 notification to ks-processing-helper-1:active.

ept never needs PutObject or write access on your bucket.

Connect

1. In the ept AI app, create an AWS S3 knowledge source with bucket, prefix, and AWS account id.
   Creating the knowledge source enables ept to receive notifications from your bucket immediately (once you attach the event notification below). A full backfill does not run yet.
2. Open the knowledge source details page. Confirm AWS Account ID, S3 Bucket, Bucket Prefix, and Bucket Region (us-east-1).
3. Copy the bucket policy and apply it on the bucket (prefix-scoped list/get only).
4. Copy the event notification JSON (it includes the helper Lambda ARN and your prefix filter) and apply it so object create and delete events invoke that Lambda for the prefix. New uploads and deletes then index automatically.
5. Optional once: click Sync ingest to backfill objects that already existed under the prefix before the notification was attached. The button disappears after the first sync.

After the notification is attached, new puts and deletes under the prefix update that knowledge source. Objects outside the prefix are ignored.

Troubleshooting

• Notification will not save (“Unable to validate the following destination configurations”): the helper allow permission for your bucket is missing. Confirm the knowledge source was created successfully, then retry the notification. Contact ept if it still fails.
• Lambda ARN is blank in the app: refresh the knowledge source page; the ARN must show the ks-processing-helper-1:active function in the ept AWS account. Contact ept if it is still empty.
• Objects not indexing after upload: confirm the object key is under the configured prefix (for example prod/file.txt for prefix prod), the notification filter matches that prefix, and the notification was saved successfully. Use Sync ingest once if the objects were already in the bucket before the notification was attached.