AWS Lambda now supports SASL/SCRAM authentication for functions triggered from Amazon MSK
AWS Lambda functions that are triggered from an Amazon Managed Streaming for Apache Kafka (Amazon MSK) topic can now access to usernames and passwords secured by AWS Secrets Manager using SASL/SCRAM (Simple Authentication and Security Layer/Salted Challenge Response Authentication Mechanism).
AWS Lambda functions that are triggered from an Amazon Managed Streaming for Apache Kafka (Amazon MSK) topic can now access to usernames and passwords secured by AWS Secrets Manager using SASL/SCRAM (Simple Authentication and Security Layer/Salted Challenge Response Authentication Mechanism).
SASL/SCRAM is a popular authentication mechanism supported by Apache Kafka. To get started, customers who select Amazon MSK as the event source for their Lambda function can choose SASL/SCRAM as their authentication mechanism, and select their credentials from Secrets Manager on the AWS Management Console, AWS CLI or AWS SDK for Lambda. This feature requires no additional charge to use, and is available in all AWS Regions where Amazon MSK is supported as an event source for AWS Lambda. To learn more about using SASL/SCRAM authentication for your Lambda functions triggered from Amazon MSK topics, read the Lambda Developer Guide.