We’re pushing Genesys Cloud interaction events to EventBridge and routing them to a Node.js Lambda. During peak hours, the volume spikes and we hit the Lambda concurrency limit. The SDK isn’t involved here, just raw JSON payloads. EventBridge batches them, but the Lambda times out trying to process the batch before the next one arrives, causing dropped events. I’ve tried increasing the reserved concurrency, but that’s hitting the account limit and the cost is getting ridiculous. The payload looks standard:
{
“source”: “genesys.cloud”,
“detail-type”: “Interaction Event”,
“detail”: {
“conversationId”: “abc-123”,
“eventType”: “interaction.created”
}
}
The Lambda handler is synchronous and simple, just forwarding to a queue. I need a way to decouple the ingestion from the processing without losing data. Async invocation with retry policies seems flaky for ordering. Is there a pattern or config tweak in the EventBridge rule or Lambda configuration that handles this burst better? I’ve checked the docs but nothing specific to GC event volume.