Replacing Glue Lambdas with EventBridge Pipes

Serverless architectures on AWS often rely on Lambda for more than business logic. In many systems, Lambda functions are used as intermediaries between event sources and downstream services, handling simple filtering, transformation, or event forwarding. Although this approach works, it can introduce unnecessary compute, more infrastructure to manage, and added complexity. EventBridge Pipes offers a more streamlined alternative by connecting sources and targets directly, reducing the need for intermediary Lambda functions. The Traditional Pattern A common approach starts with a source such as DynamoDB Streams capturing changes made to a table, after which a Lambda function consumes the stream record and forwards it to another AWS service such as SQS, EventBridge, or Step Functions. This design is flexible and familiar, but it often places Lambda in the middle of the flow even when the function is doing little more than forwarding records after light filtering or reshaping. In these cas