Back to results for “Amazon EventBridge”
AWS › Amazon EventBridge

How does EventBridge Pipes differ from standard EventBridge rules for connecting sources to targets?

Advanced

Answer

EventBridge Pipes is designed specifically for point to point integrations between a single source, such as an SQS queue or a DynamoDB stream, and a single target, and unlike standard rules which are primarily for pattern based routing to multiple targets, Pipes supports built in filtering, data enrichment through a Lambda function or API call, and transformation of the event payload before it reaches the target, all configured without writing custom glue code.
aws pipes create-pipe --name 'OrderQueuePipe' --source 'arn:aws:sqs:us-east-1:123456789012:orders-queue' --target 'arn:aws:states:us-east-1:123456789012:stateMachine:processOrder'
Real-world example A logistics company uses EventBridge Pipes to connect a DynamoDB stream directly to a Step Functions workflow, enriching each change event with additional shipping data from an API call before the workflow ever begins processing it.

Common follow-ups: What is the difference between EventBridge Pipes and a Lambda function triggered directly by SQS?;What enrichment sources are supported by EventBridge Pipes?