AWS Security ChangesHomeSearch

AWS lambda documentation change

Service: lambda · 2025-11-22 · Documentation low

File: lambda/latest/dg/kafka-esm-create.md

Summary

Updated configuration steps for Kafka event source mappings, including reordering parameters, adding provisioned mode poller settings, and adjusting VPC/security group steps.

Security assessment

The changes reorganize configuration parameters and add details about poller settings but do not address security vulnerabilities or explicitly introduce new security features. While VPC/security group and encryption settings are mentioned, these are existing security practices rather than new security documentation or fixes.

Diff

diff --git a/lambda/latest/dg/kafka-esm-create.md b/lambda/latest/dg/kafka-esm-create.md
index c77b3a472..108342d01 100644
--- a//lambda/latest/dg/kafka-esm-create.md
+++ b//lambda/latest/dg/kafka-esm-create.md
@@ -42 +42 @@ Follow these steps to add your self-managed Apache Kafka cluster and a Kafka top
-    4. (Optional) For **Batch size** , enter the maximum number of records to receive in a single batch.
+    4. If you configure provisioned mode, enter a value for **Minimum event pollers** , a value for **Maximum event pollers** , and an optional value for PollerGroupName to specify grouping of multiple ESMs within the same event source VPC.
@@ -44 +44 @@ Follow these steps to add your self-managed Apache Kafka cluster and a Kafka top
-    5. For **Batch window** , enter the maximum amount of seconds that Lambda spends gathering records before invoking the function.
+    5. (Optional) For **Batch size** , enter the maximum number of records to receive in a single batch.
@@ -46 +46 @@ Follow these steps to add your self-managed Apache Kafka cluster and a Kafka top
-    6. (Optional) For **Consumer group ID** , enter the ID of a Kafka consumer group to join.
+    6. For **Batch window** , enter the maximum amount of seconds that Lambda spends gathering records before invoking the function.
@@ -48 +48 @@ Follow these steps to add your self-managed Apache Kafka cluster and a Kafka top
-    7. (Optional) For **Starting position** , choose **Latest** to start reading the stream from the latest record, **Trim horizon** to start at the earliest available record, or **At timestamp** to specify a timestamp to start reading from.
+    7. (Optional) For **Consumer group ID** , enter the ID of a Kafka consumer group to join.
@@ -50 +50,3 @@ Follow these steps to add your self-managed Apache Kafka cluster and a Kafka top
-    8. (Optional) For **VPC** , choose the Amazon VPC for your Kafka cluster. Then, choose the **VPC subnets** and **VPC security groups**.
+    8. (Optional) For **Starting position** , choose **Latest** to start reading the stream from the latest record, **Trim horizon** to start at the earliest available record, or **At timestamp** to specify a timestamp to start reading from.
+
+    9. (Optional) For **VPC** , choose the Amazon VPC for your Kafka cluster. Then, choose the **VPC subnets** and **VPC security groups**.
@@ -54 +56 @@ This setting is required if only users within your VPC access your brokers.
-    9. (Optional) For **Authentication** , choose **Add** , and then do the following:
+    10. (Optional) For **Authentication** , choose **Add** , and then do the following:
@@ -66 +68 @@ This setting is required if only users within your VPC access your brokers.
-    10. (Optional) For **Encryption** , choose the Secrets Manager secret containing the root CA certificate that your Kafka brokers use for TLS encryption, if your Kafka brokers use certificates signed by a private CA.
+    11. (Optional) For **Encryption** , choose the Secrets Manager secret containing the root CA certificate that your Kafka brokers use for TLS encryption, if your Kafka brokers use certificates signed by a private CA.
@@ -70 +72 @@ This setting applies to TLS encryption for SASL/SCRAM or SASL/PLAIN, and to mTLS
-    11. To create the trigger in a disabled state for testing (recommended), clear **Enable trigger**. Or, to enable the trigger immediately, select **Enable trigger**.
+    12. To create the trigger in a disabled state for testing (recommended), clear **Enable trigger**. Or, to enable the trigger immediately, select **Enable trigger**.