From d86ed23bead42d21d105a84c4240f6b194345a14 Mon Sep 17 00:00:00 2001 From: HarshCasper Date: Thu, 23 Oct 2025 16:49:35 +0530 Subject: [PATCH] docs: Clarify input transformation support for EventBridge Pipes --- src/content/docs/aws/services/pipes.mdx | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/src/content/docs/aws/services/pipes.mdx b/src/content/docs/aws/services/pipes.mdx index fb43dee6..af8ec824 100644 --- a/src/content/docs/aws/services/pipes.mdx +++ b/src/content/docs/aws/services/pipes.mdx @@ -198,11 +198,12 @@ or Amazon S3 logs. The EventBridge Pipes implementation in LocalStack is currently in preview stage and has the following limitations: -* Lack of input transformers. -* Lack of concurrency support (i.e., ParallelizationFactor), resulting in slower processing in high-throughput scenarios. -* Lack of lifecycle management for pipe states (i.e., missing tests for state transitions). -* Lack of re-sharding support when polling from Kinesis and DynamoDB streams. -* Batch handling behavior may have parity issues (e.g., batch flushing rules by size, length, time, etc. are not implemented). +- Input transformation is supported **for targets only**. Enrichment input transformation is not yet available. +- Support for wildcards (`*`) in JSONPath in input transformation is not implemented. +- Lack of concurrency support (i.e., ParallelizationFactor), resulting in slower processing in high-throughput scenarios. +- Lack of lifecycle management for pipe states (i.e., missing tests for state transitions). +- Lack of re-sharding support when polling from Kinesis and DynamoDB streams. +- Batch handling behavior may have parity issues (e.g., batch flushing rules by size, length, time, etc. are not implemented). ## API Coverage