AWS Security ChangesHomeSearch

AWS lambda: Add OAuth 2.0 and IAM auth options for Kafka event source mapping

Service: lambda · 2026-10-09 · Documentation medium

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

Summary

Documents new broker authentication choices (OAUTHBEARER_AUTH, IAM_AUTH, IAM_OAUTHBEARER_AUTH) and clarifies that IAM-based auth does not use a Secrets Manager secret.

Security assessment

The change documents supported authentication methods for Kafka event source mappings, including IAM access control, which is security-relevant configuration guidance but does not address a specific vulnerability.

Evidence

+         * If your broker uses IAM access control, choose **IAM_AUTH**.

Diff

diff --git a/lambda/latest/dg/kafka-esm-create.md b/lambda/latest/dg/kafka-esm-create.md
index 22663f9..97b19e3 100644
--- a//lambda/latest/dg/kafka-esm-create.md
+++ b//lambda/latest/dg/kafka-esm-create.md
@@ -68 +68,7 @@ This setting is required if only users within your VPC access your brokers.
-      2. For SASL/SCRAM or mTLS authentication, choose the Secrets Manager secret key that contains the credentials for your Kafka cluster.
+         * If your broker uses OAuth 2.0, choose **OAUTHBEARER_AUTH**.
+
+         * If your broker uses IAM access control, choose **IAM_AUTH**.
+
+         * If your broker accepts AWS web identity tokens over OAuth 2.0, choose **IAM_OAUTHBEARER_AUTH**.
+
+      2. For SASL/SCRAM, mTLS, or OAuth 2.0 authentication, choose the Secrets Manager secret key that contains the credentials for your Kafka cluster. IAM and IAM with SASL/OAUTHBEARER authentication don't use a secret.