We’ve got a high-volume inbound campaign hitting our CXone org and the EventBridge rule is firing off batches of 100 interaction events to our Lambda consumer. The default concurrency limit is choking the function. I see Throttling exceptions in CloudWatch when the batch size stays at 100, even though we scaled the provisioned concurrency to 50. The events are just standard routing and queue metrics, nothing heavy.
I’m trying to reduce the batch window size in the EventBridge rule configuration via the AWS CLI, but the --maximum-batching-window-in-seconds flag doesn’t seem to apply to HTTP targets or specific rule types the same way. Can anyone share the exact JSON payload or CLI command to set a smaller batch size, like 10 or 20, so the Lambda doesn’t get overwhelmed? Here is the current rule structure I’m working with.
{
"Name": "cxone-interaction-events",
"EventPattern": {
"source": ["aws.eventbridge"],
"detail-type": ["CXone Interaction Event"]
},
"Targets": [
{
"Id": "cxone-lambda-consumer",
"Arn": "arn:aws:lambda:us-west-2:123456789:function:cxone-event-processor",
"MaximumBatchingWindowInSeconds": 60
}
]
}