AWS Lambda supports Kafka and Amazon MQ event sources in four additional regions
AWS Lambda now supports Amazon MSK, self-manged Apache Kafka and Amazon MQ for Apache ActiveMQ and RabbitMQ as event sources in Asia Pacific (Jakarta), Asia Pacific (Osaka), Africa (Cape Town), and Middle East (UAE). This gives customers more choices for how they want to send messages to Lambda. Customers can build applications quickly and easily with Lambda functions that are invoked based on messages from these event sources connected to an event source mapping.
AWS Lambda now supports Amazon MSK, self-manged Apache Kafka and Amazon MQ for Apache ActiveMQ and RabbitMQ as event sources in Asia Pacific (Jakarta), Asia Pacific (Osaka), Africa (Cape Town), and Middle East (UAE). This gives customers more choices for how they want to send messages to Lambda. Customers can build applications quickly and easily with Lambda functions that are invoked based on messages from these event sources connected to an event source mapping.
Lambda supports messaging event sources such as Amazon Simple Queue Service (SQS) and Amazon Kinesis Data Streams. Now, it is also easy to read from Amazon MQ message brokers or Kafka topics to process messages without needing to create and manage a consumer application. The Lambda function is invoked when the messages exceed the batch size, the payload exceeds 6MB, or when the batch window expires.
This feature incurs no additional charge. You pay for the Lambda invocations triggered by the event source mapping connected to Kafka or Amazon MQ. To learn more, see the Lambda Developer Guide for Amazon MSK, Apache Kafka and Amazon MQ. Self-managed Apache Kafka as an event source is available in all regions where AWS Lambda is available. Amazon MSK and Amazon MQ as event sources are available in all regions where AWS Lambda and the respective service are available.