AWS Security ChangesHomeSearch

AWS lambda: Document authentication for Kafka on-failure destinations

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

File: lambda/latest/dg/kafka-on-failure-destination.md · Type: iam

Summary

Adds a section explaining that Kafka on-failure destinations reuse the source access configuration authentication and requires write permission (kafka-cluster:WriteData) on the destination topic.

Security assessment

The added guidance documents least-privilege IAM requirements (kafka-cluster:WriteData) and authentication reuse for Kafka destinations, a security best-practice clarification rather than a fix for a specific vulnerability.

Evidence

+Make sure that the identity you authenticate with can write to the destination topic, not only read from your source topics. For IAM authentication, that means `kafka-cluster:WriteData` on the destination topic. For other methods, that means the equivalent write permission in your cluster's authorization rules.

Diff

diff --git a/lambda/latest/dg/kafka-on-failure-destination.md b/lambda/latest/dg/kafka-on-failure-destination.md
index 3857cef..fc8b3a8 100644
--- a//lambda/latest/dg/kafka-on-failure-destination.md
+++ b//lambda/latest/dg/kafka-on-failure-destination.md
@@ -7 +7 @@
-How a Kafka on-failure destination worksConfiguring a Kafka on-failure destinationRecord format for a Kafka destinationRequirements and limitations
+How a Kafka on-failure destination worksAuthentication for a Kafka destinationConfiguring a Kafka on-failure destinationRecord format for a Kafka destinationRequirements and limitations
@@ -25,0 +26,8 @@ When you configure a Kafka topic as an on-failure destination, Lambda acts as a
+## Authentication for a Kafka destination
+
+A Kafka on-failure destination has no authentication settings of its own. The destination topic is in the same cluster as your source topics, so Lambda writes failed records with the authentication that you already configured in the `SourceAccessConfigurations` parameter of the event source mapping.
+
+This applies to every authentication method that Lambda supports for Kafka, including OAuth 2.0 (`OAUTHBEARER_AUTH`), IAM (`IAM_AUTH`), and IAM with SASL/OAUTHBEARER (`IAM_OAUTHBEARER_AUTH`). If you authenticate with OAuth 2.0, Lambda uses the same identity provider and the same secret to get a token for producing to the destination topic. Configure the authentication once, in the source access configuration. For more information, see [Configuring cluster authentication methods in Lambda](./kafka-cluster-auth.html) for self-managed Kafka and [Configuring Amazon MSK cluster authentication methods in Lambda](./msk-cluster-auth.html) for Amazon MSK.
+
+Make sure that the identity you authenticate with can write to the destination topic, not only read from your source topics. For IAM authentication, that means `kafka-cluster:WriteData` on the destination topic. For other methods, that means the equivalent write permission in your cluster's authorization rules.
+