diff --git a/contents/docs/cdp/batch-exports/index.md b/contents/docs/cdp/batch-exports/index.md
index 474be060ee86..c924991d4801 100644
--- a/contents/docs/cdp/batch-exports/index.md
+++ b/contents/docs/cdp/batch-exports/index.md
@@ -49,7 +49,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.
 
diff --git a/contents/docs/cdp/batch-exports/s3.md b/contents/docs/cdp/batch-exports/s3.md
index 8d9ea82c8b6b..3229c0922e5e 100644
--- a/contents/docs/cdp/batch-exports/s3.md
+++ b/contents/docs/cdp/batch-exports/s3.md
@@ -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