2 Answers
- Newest
- Most votes
- Most comments
2
Lambda doesn't autoscale with Amazon MQ as an event source. It has a fixed concurrency. For ActiveMQ it is 5, for Rabbit MQ it is 3. Note that these values may change without any notice.
0
Currently the fixed concurrency is 5 for ActiveMQ as an event source and 1 for RabbitMQ as an event source.
answered a year ago
Relevant content
- asked 2 years ago
AWS OFFICIALUpdated 6 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
thank you for the response.
@Uri @furkan we are facing the same problem, do you to how much count has the concurrency for ActiveMQ increased ? Or any workaround to such a situation ?
@Uri For the life of me, I cannot find anywhere in the documentation that states this limit. Is this limitation still in place? I'm trying to evaluate if a Lambda with Amazon MQ as a source is a viable solution for a problem I'm solving and this would be a deal breaker.
As far as I know, this still the limit. To increase the processing speed you can use batching and then use multiple threads in the function to handle the messages in the batch concurrently. Another option is to duplicate the function and create multiple triggers on the same queue. Not very pretty, but will do the work.