CUR enrichment
Partner trigger
How partners trigger on-demand enrichments.
Overview
As a partner, enrichments run on demand rather than on the daily schedule: you tell us when an upload is complete, and we process it from there.
The signal is a dotfile named .upload_finished, written into the <timestamp> directory after all partitions have been uploaded. An S3 event notification on that file publishes to an SNS topic we provide, which starts the enrichment.
Setup
- Ask your Greenpixie contact for your SNS notification ARN.
- In the S3 bucket that holds your input data, create an event notification:
- Event type:
s3:ObjectCreated:* - Suffix filter:
.upload_finished - Destination: the SNS topic ARN we provided.
- Event type:
Triggering an enrichment
- Upload all partitions into the
<timestamp>directory, following the partner directory structure. - Once every partition has finished uploading, write an empty file named
.upload_finishedinto the same<timestamp>directory.
input / org_12345 / aws / 1111111111 / 20260722T120000Z / .upload_finishedThe S3 event notification publishes to the SNS topic, and Greenpixie processes the enrichment of that timestamp directory from there.
Write .upload_finished only after all partitions are fully uploaded: it
marks the directory as complete, and the enrichment processes whatever is
present when it starts.