EventBridge fan-out strategy to avoid Lambda throttling

Hey folks,

We’ve got a Genesys Cloud instance churning out a lot of interaction events. The default EventBridge rule sends them straight to a single Lambda, which hits the concurrency limit around 1,000. We’re seeing dropped events during peak hours. I tried splitting the rule by partition key, but the distribution is uneven.

Is there a way to configure the EventBridge rule to fan out to multiple Lambda destinations or use an SQS queue as a buffer before processing? I’d rather not manage a custom consumer if I can avoid it.

Here’s the current rule config:

{
 "Source": "aws.genesyscloud",
 "DetailType": ["genesys-cloud:interaction"]
}

Any ideas on how to handle this without rewriting the whole ingestion pipeline?