Constructing serverless occasion streaming purposes with Amazon MSK and AWS Lambda

As organizations construct fashionable purposes with event-driven architectures (EDA), they typically search options that decrease infrastructure administration overhead whereas maximizing developer productiveness. Amazon Managed Streaming for Apache Kafka (Amazon MSK) and AWS Lambda collectively present a serverless, scalable, and cost-efficient platform for real-time event-driven processing.

On this submit, we describe how one can simplify your event-driven utility structure utilizing AWS Lambda with Amazon MSK. We display easy methods to configure Lambda as a client for Kafka subjects, together with a cross-account setup and easy methods to optimize worth and efficiency for these purposes.

Why use Lambda with Amazon MSK?

Prospects constructing event-driven purposes have a number of key priorities in relation to their structure decisions. They usually search to cut back their operational overhead by utilizing Amazon Net Providers (AWS) to deal with the complicated, underlying infrastructure parts so their groups can give attention to core enterprise logic. Moreover, builders favor a streamlined expertise that minimizes the necessity for repetitive boilerplate code, enabling them to be extra productive and give attention to creating worth. Moreover, these prospects wish to obtain each scalability and cost-effectiveness with out the burden of managing compute infrastructure instantly. Lambda integration with Amazon MSK successfully addresses these necessities, delivering a complete resolution that mixes the advantages of serverless computing with managed Kafka providers. For instance, an ecommerce firm can use Amazon MSK to gather real-time clickstream knowledge from its web site and course of these occasions utilizing AWS Lambda. With this integration, they will set off Lambda features to replace suggestion fashions, ship customized provides, or analyze person conduct immediately—with out provisioning or managing servers. The important thing advantages of utilizing Lambda with Amazon MSK embrace:

1. Simplicity via native integration – AWS Lambda provides native integration with Amazon MSK via a connector useful resource referred to as occasion supply mapping. You need to use this integration to instantly affiliate a Kafka subject—whether or not it’s on Amazon MSK or a self-managed Kafka cluster—as an occasion supply for a Lambda operate with out writing customized client logic. With only a few configuration steps, occasion supply mapping handles partition task, offset monitoring, and parallelized batch processing beneath the hood. It makes use of the Kafka client group protocol to distribute subject partitions throughout a number of concurrent Lambda invocations, helps batch windowing, and permits at-least-once supply semantics. Furthermore, it robotically commits offsets upon profitable operate execution whereas dealing with retries and dead-letter queue (DLQ) routing for failed data, considerably decreasing the operational overhead historically related to Kafka customers.
2. Auto scaling and throughput controls – When utilizing AWS Lambda with Amazon MSK via occasion supply mapping, Lambda robotically scales by assigning a devoted occasion poller per Kafka partition, enabling parallel, partition-based processing. This enables the system to elastically deal with various visitors with out guide intervention. For superior management, provisioned concurrency pre-initializes Lambda execution environments, eliminating chilly begins and delivering constant low-latency efficiency. Moreover, with provisioned occasion supply mapping, you’ll be able to configure the minimal and most variety of Kafka pollers, offering exact management over throughput and concurrency. That is superb for purposes with unpredictable visitors patterns or strict latency necessities.
3. Value-effectiveness – AWS Lambda makes use of a pay-per-use mannequin through which you solely pay for compute time and variety of invocations. When built-in with Amazon MSK, there are not any expenses for idle time, making it superb for bursty or low-frequency Kafka workloads. You’ll be able to additional optimize prices by tuning batch measurement and batch window settings. For mission-critical workloads, provisioned concurrency offers constant efficiency with managed pricing.
4. Occasion filtering – AWS Lambda helps occasion filtering for Amazon MSK occasion sources, which implies you’ll be able to course of solely the Kafka data that match particular standards. This reduces pointless operate invocations and optimizes your operate prices. You’ll be able to outline as much as 5 filters per occasion supply mapping (with the choice to request a rise to 10). Every filter makes use of a JSON-based sample to specify the circumstances a file should meet to be processed. Filters may be utilized utilizing the AWS Administration Console, AWS Command Line Interface (AWS CLI), or AWS Serverless Software Mannequin (AWS SAM) templates. For extra particulars and examples, seek advice from the AWS Lambda documentation on occasion filtering with Amazon MSK.
5. Dealing with Availability Zone outage on your client – Amazon MSK permits excessive availability on your Kafka brokers by distributing them throughout a number of Availability Zones inside a Area. To keep up excessive availability throughout your utility, you equally want a client that provides excessive availability. AWS Lambda provides excessive availability and resilience by working your client features throughout a number of Availability Zones in a Area. Which means even when one Availability Zone experiences an outage, your Lambda operate will proceed to function in different wholesome Availability Zones. Whereas Lambda manages safety patching and Availability Zone failure eventualities, you’ll be able to focus in your utility logic.
6. Cross-account occasion processing – Cross-account connectivity between AWS Lambda and Amazon MSK permits a Lambda operate in a single AWS account to eat knowledge from an MSK cluster in one other account utilizing MSK multi-VPC personal connectivity powered by AWS PrivateLink. This setup is especially useful for organizations that centralize Kafka infrastructure whereas sustaining separate accounts for various purposes or groups.
7. Assist for JSON, Avro, Protobuf, and Schema Registries – AWS Lambda helps Kafka occasions in JSON, Avro and Protobuf codecs by way of occasion supply mapping. It integrates with AWS Glue Schema registry, Confluent Cloud Schema registry, and self-managed Confluent Schema registry , enabling native schema validation, filtering, and deserialization with out customized code.

How Lambda processes messages out of your Kafka subject

Lambda makes use of occasion supply mappings to course of data from Amazon MSK by actively polling Kafka subjects via occasion pollers that invoke Lambda features with batches of data. These mappings are Lambda managed sources designed for high-throughput, stream-based processing. By default, Lambda detects the OffsetLag for all partitions in your Kafka subject and robotically scales pollers primarily based on visitors. For top-throughput purposes, you’ll be able to allow provisioned mode to outline minimal and most pollers, and your occasion supply mapping auto scales between the minimal and most outlined values. Within the provisioned mode, every poller can course of as much as 5 MBps and helps concurrent Lambda invocations.

After Lambda processes every batch, it commits the offsets of the messages in that batch. In case your operate returns an error for a message in a batch, Lambda retries the entire batch of messages till processing succeeds or the messages expire. You’ll be able to ship data that fail all retry makes an attempt to an on-failure vacation spot for later processing. To keep up ordered processing inside a partition, Lambda limits the utmost occasion pollers to the variety of partitions within the subject. When establishing Kafka as a Lambda occasion supply, you’ll be able to specify a client group ID to let Lambda be part of an current Kafka client group. If different customers are lively in that group, Lambda will obtain solely a part of the subject’s messages. If the group exists, Lambda begins from the group’s dedicated offset, ignoring the StartingPosition. The next diagram illustrates this circulate.

Walkthrough: Construct a serverless Kafka app with AWS Lambda

Observe these steps to construct a serverless utility that consumes messages from an MSK cluster utilizing AWS Lambda:

1. Create an Amazon MSK cluster. Use the AWS Administration Console or AWS CLI to create your MSK cluster. When the cluster is up, create your Kafka subject(s). For detailed directions, seek advice from the Amazon MSK documentation.
2. Create a Lambda operate utilizing the AWS Administration Console or the AWS CLI. To study extra about making a Lambda operate, seek advice from Create your first Lambda operate. The Lambda operate’s execution position must have the next permissions:
   1. Entry to connect with your MSK cluster
   2. Permissions to handle elastic community interfaces in your VPC
3. To attach Lambda to Amazon MSK as a client, arrange occasion supply mapping to hyperlink your MSK subject with the Lambda operate. This enables Lambda to robotically ballot for brand new messages and course of them. Observe the information on easy methods to configure occasion supply mapping.

For reference, configuring occasion supply mapping entails three steps:

4. Community setup – Within the default occasion supply mapping mode, it’s good to configure a networking setup utilizing a PrivateLink endpoint or NAT gateway for occasion supply mapping to invoke Lambda features. In provisioned mode, no networking configuration is required (and also you don’t incur the price of networking parts).
5. Occasion supply mapping parameter configuration – This entails setting mandatory configuration parameters for the occasion supply mapping to have the ability to ballot messages out of your Kafka cluster. This consists of the MSK cluster, subject identify, client group ID, authentication methodology, and optionally, schema registry, scaling mode. You’ll be able to configure the scaling mode for provisioned throughput, together with batch measurement, batch window, and occasion filtering on your occasion supply mapping.
6. Entry permissions – This entails configuring required permissions to entry the required AWS sources, and consists of configuring permissions for the operate to execute the code, permissions for the occasion supply mapping to entry your MSK cluster, and permissions for Lambda to entry your VPC sources.

The next screenshot reveals the console setup for configuring Amazon MSK occasion supply mapping, together with the Amazon MSK set off associated fields.

The next screenshot reveals occasion poller configuration.

The next screenshot reveals further settings you should use, relying in your use case.

Optimizing AWS Lambda for stream processing with Amazon MSK

When constructing real-time knowledge processing pipelines with Amazon MSK and AWS Lambda, it’s vital to tune your setup for each efficiency and cost-efficiency. Lambda provides highly effective serverless compute capabilities, however to get essentially the most out of it in a streaming context, it’s good to make a couple of key optimizations:

1. Allow provisioned concurrency for low-latency processing – For workloads which are delicate to latency—chilly begins can introduce undesirable delays. By enabling provisioned concurrency, you’ll be able to pre-warm a specified variety of Lambda cases in order that they’re all the time able to deal with visitors instantly. This eliminates chilly begins and offers constant response occasions, which is essential for latency-critical use instances.
2. Allow provisioned mode for occasion supply mapping for high-throughput processing – For Kafka workloads with stringent throughput necessities, activate the provisioned mode. The optimum configuration of minimal and most occasion pollers on your Kafka occasion supply mapping will depend on your utility’s efficiency necessities. Begin with the default minimal occasion pollers to baseline the efficiency profile and regulate occasion pollers primarily based on noticed message processing patterns and your utility’s efficiency necessities. For workloads with spiky visitors and strict efficiency wants, enhance the minimal occasion pollers to deal with sudden surges. You’ll be able to fine-tune the minimal occasion pollers by evaluating your required throughput, your noticed throughput, which will depend on elements such because the ingested messages per second and common payload measurement, and utilizing the throughput capability of 1 occasion poller (as much as 5 MB/s) as reference. To keep up ordered processing inside a partition, Lambda caps the utmost occasion pollers on the variety of partitions within the subject.
3. Optimize message batching utilizing measurement and windowing – By integrating Lambda with Amazon MSK, you’ll be able to management how messages are batched earlier than they’re despatched to your operate. Tuning parameters akin to batch measurement (the variety of data per invocation: 1–10,000 data) and most batching window (how lengthy to attend for a full batch: 0–300 seconds) can considerably influence efficiency. Bigger batches imply fewer invocations, which reduces overhead and improves throughput. Nevertheless, it’s vital to strike a stability—too giant a batch or window may introduce undesirable processing delays. Monitor your stream’s conduct and regulate these settings primarily based on throughput necessities and acceptable latency.
4. Apply filters to cut back pointless invocations – Not each file in your Kafka subject may require processing. To keep away from pointless Lambda invocations (and related prices), apply filtering logic instantly when configuring the occasion supply mapping. With Lambda, you’ll be able to outline filtering (as much as 10 filters) standards in order that solely related data set off your operate. This helps cut back compute time, decrease noise, and optimize your funds, particularly when coping with high-throughput subjects with blended content material. For Amazon MSK, Lambda commits offsets for matched and unmatched messages after efficiently invoking the operate.

Conclusion

By combining Amazon MSK with AWS Lambda, you’ll be able to seamlessly construct fashionable, serverless event-driven purposes. This integration eliminates the necessity to handle client teams, compute infrastructure, or scaling logic so groups can give attention to delivering enterprise worth quicker.

Whether or not you’re integrating Kafka into microservices, remodeling knowledge pipelines, or constructing reactive purposes, Lambda with Amazon MSK is a strong and versatile serverless resolution. For detailed documentation on easy methods to configure Lambda with Amazon MSK, seek advice from the AWS Lambda Developer Information. For extra serverless studying sources, go to Serverless Land.

In regards to the Authors

Tarun Rai Madan is a Principal Product Supervisor at Amazon Net Providers (AWS). He makes a speciality of serverless applied sciences and leads product technique to assist prospects obtain accelerated enterprise outcomes with event-driven purposes, utilizing providers like AWS Lambda, AWS Step Capabilities, Apache Kafka, and Amazon SQS/SNS. Previous to AWS, he was an engineering chief within the semiconductor business, and led growth of high-performance processors for wi-fi, automotive, and knowledge heart purposes.

Masudur Rahaman Sayem is a Streaming Knowledge Architect at AWS with over 25 years of expertise within the IT business. He collaborates with AWS prospects worldwide to architect and implement subtle knowledge streaming options that tackle complicated enterprise challenges. As an professional in distributed computing, Sayem makes a speciality of designing large-scale distributed methods structure for optimum efficiency and scalability. He has a eager curiosity and keenness for distributed structure, which he applies to designing enterprise-grade options at web scale.