An EventBridge Pipe uses an Amazon SQS queue as its source and publishes every source event to an EventBridge event bus. A Lambda function in the pipe looks up each event’s stream status from a database and appends that status to the event. The company only wants events published to the event bus when the stream status is ready. What should they do?

Adding a filter step to the pipe is the most efficient and direct solution. EventBridge Pipes allow you to define filters based on the content of the event, including data added by enrichment steps like the Lambda function. This ensures that only events with a ready status are passed to the target (the EventBridge event bus), preventing unnecessary processing and traffic. Modifying the Lambda to return only ready events is incorrect because the Lambda’s purpose is enrichment (appending status), not filtering. Filtering at the Lambda level would be less flexible and harder to manage if filtering logic changes. Adding filters on every EventBridge rule is inefficient; it pushes the filtering responsibility to consumers, leading to redundant configuration and potentially processing unwanted events on the bus. An input transformer modifies the event's structure, not its flow; it cannot drop events based on content.