From 2bcfb2a39b797762e9ef0d0fc5ff90a928f0def1 Mon Sep 17 00:00:00 2001 From: Austin Lai Date: Mon, 8 Sep 2025 13:51:50 -0700 Subject: [PATCH 1/3] FMEPRD-281 --- .../80-integrations/amazon-s3.md | 27 ++++++++++++++++--- 1 file changed, 24 insertions(+), 3 deletions(-) diff --git a/docs/feature-management-experimentation/80-integrations/amazon-s3.md b/docs/feature-management-experimentation/80-integrations/amazon-s3.md index 9922d9002e2..c6d126e05c8 100644 --- a/docs/feature-management-experimentation/80-integrations/amazon-s3.md +++ b/docs/feature-management-experimentation/80-integrations/amazon-s3.md @@ -4,7 +4,7 @@ sidebar_label: Amazon S3 description: "" --- -Amazon Simple Storage Service (Amazon S3) is an object storage service offered by Amazon as part of Amazon Web Services (AWS) that offers the ability to store and retrieve any amount of data, at any time, from anywhere on the web. With this integration you can easily and reliably send high volumes of event data to Harness FME, as well as export your impression data. +Amazon Simple Storage Service (Amazon S3) is an object storage service offered by Amazon as part of Amazon Web Services (AWS) that offers the ability to store and retrieve any amount of data, at any time, from anywhere on the web. With this integration, you can easily and reliably send high volumes of event data to Harness FME, as well as export your impression data. ## Send events to Harness FME @@ -20,7 +20,7 @@ To connect your AWS S3 bucket to Harness FME, you need: **File restrictions:** * Compression examples: gzip, bzip2, snappy, or LZO compression. -* File format: _parquet only_ +* File format: *Parquet only* * Schema: * environmentId: \[String\] Identifier for the environment in Harness FME * trafficTypeId: \[String\] Identifier for the traffic type in Harness FME @@ -376,9 +376,30 @@ The following describes how to send Harness FME impressions to S3. Impressions a To connect your AWS S3 bucket to Harness FME, you need: -* An S3 bucket destination already created. +* An S3 bucket destination that contains files with supported compression. * An AWS account with the ability to grant Harness FME permission to read, put, and remove data in the bucket. **Note: We only remove transactional files created during the transfer.** +**File restrictions**: + +* Compression examples: gzip, bzip2, snappy, or LZO +* File format: *Parquet only* +* Schema: + + * key: [String] Identifier for the user or system triggering or associated with the impression + * label: [String] Label associated with the impression + * treatment: [String] The treatment shown for this impression + * testName AS splitName: [String] Name of the feature flag + * changeNumber AS splitVersion: [Long] Version of the feature flag + * properties: [Map, Nullable] Properties data providing context to the impression + * environmentId: [String] Identifier for the environment in Harness FME + * trafficTypeId: [String] Identifier for the traffic type in Harness FME + * sdk: [String] Name of the SDK sending the impression + * sdkVersion: [String] Version of the SDK + * machineName: [String, Nullable] Name of the machine sending the impression + * machineIp: [String, Nullable] IP of the machine sending the impression + * time AS timestamp: [Long] The time when the impression occurred, in milliseconds past epoch + * receptionTimestamp: [Long] Timestamp when the impression was received by Harness FME + ### Configure integration in Harness FME (outbound) 1. Click the **profile button** at the bottom of the left navigation pane and click **Admin settings**. From ffcee500aa69a0a1c13f78391163c191384b9182 Mon Sep 17 00:00:00 2001 From: Austin Lai <76412946+alai97@users.noreply.github.com> Date: Mon, 8 Sep 2025 14:04:40 -0700 Subject: [PATCH 2/3] SME Review --- .../80-integrations/amazon-s3.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/feature-management-experimentation/80-integrations/amazon-s3.md b/docs/feature-management-experimentation/80-integrations/amazon-s3.md index c6d126e05c8..708eba0bcf3 100644 --- a/docs/feature-management-experimentation/80-integrations/amazon-s3.md +++ b/docs/feature-management-experimentation/80-integrations/amazon-s3.md @@ -376,7 +376,7 @@ The following describes how to send Harness FME impressions to S3. Impressions a To connect your AWS S3 bucket to Harness FME, you need: -* An S3 bucket destination that contains files with supported compression. +* An S3 bucket destination already created. * An AWS account with the ability to grant Harness FME permission to read, put, and remove data in the bucket. **Note: We only remove transactional files created during the transfer.** **File restrictions**: @@ -388,16 +388,16 @@ To connect your AWS S3 bucket to Harness FME, you need: * key: [String] Identifier for the user or system triggering or associated with the impression * label: [String] Label associated with the impression * treatment: [String] The treatment shown for this impression - * testName AS splitName: [String] Name of the feature flag - * changeNumber AS splitVersion: [Long] Version of the feature flag - * properties: [Map, Nullable] Properties data providing context to the impression + * splitName: [String] Name of the feature flag + * splitVersion: [Long] Version of the feature flag + * properties: [String] Arbitrary properties data providing context to the impression * environmentId: [String] Identifier for the environment in Harness FME * trafficTypeId: [String] Identifier for the traffic type in Harness FME * sdk: [String] Name of the SDK sending the impression * sdkVersion: [String] Version of the SDK * machineName: [String, Nullable] Name of the machine sending the impression * machineIp: [String, Nullable] IP of the machine sending the impression - * time AS timestamp: [Long] The time when the impression occurred, in milliseconds past epoch + * timestamp: [Long] The time when the impression occurred, in milliseconds past epoch * receptionTimestamp: [Long] Timestamp when the impression was received by Harness FME ### Configure integration in Harness FME (outbound) From 558435b73b1fad3cd13ea65b6874fc9bb6fb697f Mon Sep 17 00:00:00 2001 From: Austin Lai <76412946+alai97@users.noreply.github.com> Date: Mon, 8 Sep 2025 14:07:38 -0700 Subject: [PATCH 3/3] Copy Nit --- .../80-integrations/amazon-s3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/feature-management-experimentation/80-integrations/amazon-s3.md b/docs/feature-management-experimentation/80-integrations/amazon-s3.md index 708eba0bcf3..d992883819a 100644 --- a/docs/feature-management-experimentation/80-integrations/amazon-s3.md +++ b/docs/feature-management-experimentation/80-integrations/amazon-s3.md @@ -379,7 +379,7 @@ To connect your AWS S3 bucket to Harness FME, you need: * An S3 bucket destination already created. * An AWS account with the ability to grant Harness FME permission to read, put, and remove data in the bucket. **Note: We only remove transactional files created during the transfer.** -**File restrictions**: +**File specifications**: * Compression examples: gzip, bzip2, snappy, or LZO * File format: *Parquet only*