Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Document new S3 BatchExports parameters #6638

Merged
merged 2 commits into from
Sep 14, 2023
Merged

feat: Document new S3 BatchExports parameters #6638

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
38e3a6e
feat: Document new S3 parameters
tomasfarias Sep 1, 2023
a641160
feat: Add encryption parameters
tomasfarias Sep 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion contents/docs/cdp/batch-exports/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ Each run has:
4. The option of retrying a specific run.


## Historical exports
## Exporting historical data

You can use batch exports for past data stored in PostHog, known as historical data. For this, you don't need to create a new batch export. The batch export already knows the destination where we wish to send historical data. It only requires the boundaries for the data you want to export, in other words, a start and an end date.

Expand Down
4 changes: 4 additions & 0 deletions contents/docs/cdp/batch-exports/s3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,8 +25,12 @@ Configuring a batch export targeting S3 requires the following S3-specific confi
* **Bucket name:** The name of the S3 bucket where the data is to be exported.
* **Region:** The AWS region where the bucket is located.
* **Key prefix:** A key prefix to use for each S3 object created. This key can include [template variables](#s3-key-prefix-template-variables)
* **Compression:** Select a compression method (like gzip) to use for exported files or no compression.
* **Encryption:** Select a server-side encryption method (`AES256` or `aws:kms`) for AWS to encrypt data at rest.
* **AWS Access Key ID:** An AWS access key ID with access to the S3 bucket.
* **AWS Secret Access Key:** An AWS secret access key with access to the S3 bucket.
* **AWS KMS Key ID:** The AWS KMS Key ID to use for server-side encryption. Only required when selecting `aws:kms` encryption.
* **Events to exclude:** A list of events to omit from the exported data.

### S3 key prefix template variables

Expand Down