AWS Lambda improves responsiveness for configuring stream and queue-based event sources

AWS Lambda now improves the responsiveness for configuring Event Source Mappings (ESMs) and Amazon EventBridge Pipes with event sources such as self-managed Apache Kafka, Amazon Managed Streaming for Apache Kafka (MSK), Amazon DocumentDB, and Amazon MQ. This enhancement allows changes—such as updating, disabling, or deleting ESMs or Pipes—to take effect within 90 seconds, an improvement from the previous time frame of up to 15 minutes. Customers building event-driven applications use self-managed Apache Kafka, Amazon MSK, Amazon DocumentDB, and Amazon MQ as event sources with Lambda, by configuring ESMs or EventBridge Pipes. Previously, configuration changes that updated, disabled, or deleted these ESMs or Pipes could take up to 15 minutes to go into effect. With today’s announcement, these configuration changes will go into effect within 90 seconds, enabling customers to quickly update and test their applications. This feature is generally available in all commercial [regions](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/) that AWS Lambda and Amazon EventBridge Pipes are available in, except Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Canada West (Calgary), Europe (Spain), and Europe (Zurich). The improved responsiveness is automatically applied to all [Lambda ESMs](https://docs.aws.amazon.com/lambda/latest/dg/invocation-eventsourcemapping.html) and [EventBridge Pipes](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-pipes.html) with self-managed Apache Kafka, Amazon MSK, Amazon DocumentDB, and Amazon MQ event sources, at no additional cost.