A video streaming company has a pipe in Amazon EventBridge Pipes that uses an Amazon Simple Queue Service (Amazon SQS) queue as an event source. The pipe publishes all source events to a target…

EventBridge Pipes has a native filter step that evaluates event patterns against the enriched event payload before forwarding to the target. Adding a filter that matches on stream_status = ready ensures only qualifying events are published to the event bus, without modifying the Lambda enrichment function or requiring downstream rule changes.

Updating the Lambda enrichment function to return only ready-status events changes the enrichment logic and suppresses non-ready events from being enriched at all, which could prevent their use in other contexts and conflates enrichment with filtering responsibilities.

Adding a filter to EventBridge rules on the target event bus still allows all events to be published to the bus; the filtering happens after ingestion and does not prevent non-ready events from entering the bus.

An input transformer reshapes the event payload structure for the target but cannot conditionally suppress or filter events; all events still get published to the event bus regardless of stream status.