AWS lambda: Add OAUTHBEARER_AUTH option for Confluent schema registry
Summary
Documents a fourth authentication method for KafkaSchemaRegistryAccessConfig where Lambda fetches an OAuth 2.0 bearer token from Secrets Manager and refreshes it.
Security assessment
Describes a new OAuth 2.0 bearer-token authentication option and its Secrets Manager secret handling for schema registry access, which is security-relevant documentation but not tied to a specific vulnerability.
Evidence
+ * **OAUTHBEARER_AUTH** — Lambda requests an access token from your OAuth 2.0 identity provider and sends it to your registry as a bearer token. Lambda refreshes the token before it expires. If you choose this option, provide the Secrets Manager ARN containing your OAuth secret in the URI field. The secret uses the same fields as the secret for broker authentication, and supports the same two grant types. For the contents of the secret, see [Configuring the OAuth secret](./kafka-cluster-auth.html#smaa-auth-oauth-secret).
Diff
diff --git a/lambda/latest/dg/services-consume-kafka-events.md b/lambda/latest/dg/services-consume-kafka-events.md index be3c507..d97f7a3 100644 --- a//lambda/latest/dg/services-consume-kafka-events.md +++ b//lambda/latest/dg/services-consume-kafka-events.md @@ -934 +934 @@ For AWS Glue schema registries, if you provide `AccessConfigs` for a AWS Glue re -If you're working with a Confluent schema registry, you can choose one of three supported authentication methods for the `Type` parameter of your [KafkaSchemaRegistryAccessConfig](https://docs.aws.amazon.com/lambda/latest/api/API_KafkaSchemaRegistryAccessConfig) object: +If you're working with a Confluent schema registry, you can choose one of four supported authentication methods for the `Type` parameter of your [KafkaSchemaRegistryAccessConfig](https://docs.aws.amazon.com/lambda/latest/api/API_KafkaSchemaRegistryAccessConfig) object: @@ -939,0 +940,2 @@ If you're working with a Confluent schema registry, you can choose one of three + * **OAUTHBEARER_AUTH** — Lambda requests an access token from your OAuth 2.0 identity provider and sends it to your registry as a bearer token. Lambda refreshes the token before it expires. If you choose this option, provide the Secrets Manager ARN containing your OAuth secret in the URI field. The secret uses the same fields as the secret for broker authentication, and supports the same two grant types. For the contents of the secret, see [Configuring the OAuth secret](./kafka-cluster-auth.html#smaa-auth-oauth-secret). +