This pattern shows how an Amazon EventBridge custom event bus (the eventsv2 API) processes events in order by invoking an AWS Lambda function synchronously (InvocationType REQUEST_RESPONSE) from a FIFO subscriber.

The publisher sends a sequence of OrderPlaced events that share one EventGroupId, each carrying a monotonically increasing sequence number. The FIFO subscriber invokes the consumer AWS Lambda function synchronously, waiting for each event to be confirmed before delivering the next in the group. The consumer logs each sequence number as it processes, and the Amazon CloudWatch log shows the sequence handled in order, one at a time. Synchronous confirmation gives the reliability and back-pressure that teams used to get by adding an Amazon SQS queue between the bus and AWS Lambda, so no Amazon SQS buffer sits in the path.

This deploys one Amazon EventBridge custom event bus, one FIFO subscriber configured for synchronous invocation, one Node.js 24 (TypeScript) AWS Lambda function, an Amazon SQS dead-letter queue (safety net), and the AWS Identity and Access Management (IAM) delivery role.