-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
79 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,79 @@ | ||
<!-- | ||
title: Serverless Framework - AWS Lambda Events - Managed Streaming for Apache Kafka (MSK) | ||
menuText: MSK | ||
menuOrder: 18 | ||
description: Setting up AWS MSK Events with AWS Lambda via the Serverless Framework | ||
layout: Doc | ||
--> | ||
|
||
<!-- DOCS-SITE-LINK:START automatically generated --> | ||
|
||
### [Read this on the main serverless docs site](https://www.serverless.com/framework/docs/providers/aws/events/cognito-user-pool) | ||
|
||
<!-- DOCS-SITE-LINK:END --> | ||
|
||
# MSK | ||
|
||
In the following example, we specify that the `compute` function should be triggered whenever there are new messages available to consume from defined Kafka `topic`. | ||
|
||
In order to configure `msk` event, you have to provide two required properties: `arn`, which represents an ARN of MSK cluster and `topic` to consume messages from. | ||
|
||
The ARN for the MSK cluster can be specified as a string, the reference to the ARN resource by a logical ID, or the import of an ARN that was exported by a different service or CloudFormation stack. | ||
|
||
```yml | ||
functions: | ||
compute: | ||
handler: handler.compute | ||
events: | ||
# These are all possible formats | ||
- msk: | ||
arn: arn:aws:kafka:region:XXXXXX:cluster/MyCluster/xxxx-xxxxx-xxxx | ||
topic: mytopic | ||
- msk: | ||
arn: | ||
Fn::ImportValue: MyExportedMSKClusterArn | ||
topic: mytopic | ||
- msk: | ||
arn: !Ref MyMSKCluster | ||
topic: mytopic | ||
``` | ||
|
||
## Setting the BatchSize and StartingPosition | ||
|
||
For the MSK event integration, you can set the `batchSize`, which effects how many messages can be processed in a single Lambda invocation. The default `batchSize` is 100, and the max `batchSize` is 10000. | ||
In addition, you can also configure `startingPosition`, which controls the position at which Lambda should start consuming messages from MSK topic. It supports two possible values, `TRIM_HORIZON` and `LATEST`, with `TRIM_HORIZON` being the default. | ||
|
||
In the following example, we specify that the `compute` function should have an `msk` event configured with `batchSize` of 1000 and `startingPosition` equal to `LATEST`. | ||
|
||
```yml | ||
functions: | ||
compute: | ||
handler: handler.compute | ||
events: | ||
- msk: | ||
arn: arn:aws:kafka:region:XXXXXX:cluster/MyCluster/xxxx-xxxxx-xxxx | ||
topic: mytopic | ||
batchSize: 1000 | ||
startingPosition: LATEST | ||
``` | ||
|
||
## Enabling and disabling MSK event | ||
|
||
The `msk` event also supports `enabled` parameter, which is used to control if the event source mapping is active. Setting it to `false` will pause polling for and processing new messages. | ||
|
||
In the following example, we specify that the `company` function's `msk` event should be disabled. | ||
|
||
```yml | ||
functions: | ||
compute: | ||
handler: handler.compute | ||
events: | ||
- msk: | ||
arn: arn:aws:kafka:region:XXXXXX:cluster/MyCluster/xxxx-xxxxx-xxxx | ||
topic: mytopic | ||
enabled: false | ||
``` | ||
|
||
## IAM Permissions | ||
|
||
The Serverless Framework will automatically configure the most minimal set of IAM permissions for you. However you can still add additional permissions if you need to. Read the official [AWS documentation](https://docs.aws.amazon.com/lambda/latest/dg/with-msk.html) for more information about IAM Permissions for MSK events. |