All Amazon MSK event source configuration parameters in Lambda - AWS Lambda

All Amazon MSK event source configuration parameters in Lambda

All Lambda event source types share the same CreateEventSourceMapping and UpdateEventSourceMapping API operations. However, only some of the parameters apply to Amazon MSK, as shown in the following table.

Parameter Required Default Notes

AmazonManagedKafkaEventSourceConfig

N

Contains the ConsumerGroupId field, which defaults to a unique value.

Can set only on Create

BatchSize

N

100

Maximum: 10,000

DestinationConfig

N

N/A

Capturing discarded batches for Amazon MSK and self-managed Apache Kafka event sources

Enabled

N

True

BisectBatchOnFunctionError

N

False

Configuring error handling controls for Kafka event sources

FunctionResponseTypes

N

N/A

Configuring error handling controls for Kafka event sources

MaximumRecordAgeInSeconds

N

-1 (infinite)

Configuring error handling controls for Kafka event sources

MaximumRetryAttempts

N

-1 (infinite)

Configuring error handling controls for Kafka event sources

EventSourceArn

Y

N/A

Can set only on Create

FilterCriteria

N

N/A

Control which events Lambda sends to your function

FunctionName

Y

N/A

KMSKeyArn

N

N/A

Encryption of filter criteria

MaximumBatchingWindowInSeconds

N

500 ms

Batching behavior

ProvisionedPollersConfig

N

MinimumPollers: default value of 1 if not specified

MaximumPollers: default value of 200 if not specified

PollerGroupName: N/A

Provisioned mode

SourceAccessConfigurations

N

No credentials

SASL/SCRAM or CLIENT_CERTIFICATE_TLS_AUTH (MutualTLS) authentication credentials for your event source

StartingPosition

Y

N/A

AT_TIMESTAMP, TRIM_HORIZON, or LATEST

Can set only on Create

StartingPositionTimestamp

N

N/A

Required if StartingPosition is set to AT_TIMESTAMP

Tags

N

N/A

Using tags on event source mappings

Topics

Y

N/A

Kafka topic name

Can set only on Create

Note

When you specify a PollerGroupName, multiple ESMs within the same Amazon VPC can share Event Poller Unit (EPU) capacity. You can use this option to optimize Provisioned mode costs for your ESMs. Requirements for ESM grouping:

  • ESMs must be within the same Amazon VPC

  • Maximum of 100 ESMs per poller group

  • Aggregate maximum pollers across all ESMs in a group cannot exceed 2000

You can update the PollerGroupName to move an ESM to a different group, or remove an ESM from a group by setting PollerGroupName to an empty string ("").