AWS Lambda now makes it easier to build analytics for Amazon Kinesis and Amazon DynamoDB Streams
Customers can now use AWS Lambda to build analytics workloads for their Amazon Kinesis or Amazon DynamoDB Streams. For no additional cost, customers can build sum, average, count, and other simple analytics functions over a contiguous, non-overlapping time windows (tumbling window) of up to 15 minutes per shard. Customers can consolidate their business and analytics logic into a single Lambda function, reducing the complexity of their architecture.
Customers can now use AWS Lambda to build analytics workloads for their Amazon Kinesis or Amazon DynamoDB Streams. For no additional cost, customers can build sum, average, count, and other simple analytics functions over a contiguous, non-overlapping time windows (tumbling window) of up to 15 minutes per shard. Customers can consolidate their business and analytics logic into a single Lambda function, reducing the complexity of their architecture.
Lambda adds another choice for running analytics for short periods of time for streaming data in Kinesis and DynamoDB Streams, in addition to services such as Amazon Kinesis Data Analytics and Kinesis Data Analytics for Apache Flink. Customers can make use of the simplicity and ease of use of Lambda to set up and manage their analytics workload. When using tumbling windows to perform analytics, Lambda will consume records from the event source, and invoke the function when the payload size reaches 5MB. An additional 1MB of the payload is used to maintain state between multiple invokes within a single tumbling window.
Customers can get started by selecting the length of their tumbling window for analytics on the AWS Console, AWS CLI, AWS SAM, AWS CloudFormation, or AWS SDK for Lambda. This feature requires no additional charge to use. This feature is available in all AWS Regions where AWS Lambda, Amazon Kinesis and Amazon DynamoDB are available. To learn more about setting up an analytics workload on Lambda, read the Lambda Developer Guide (Kinesis, DynamoDB) and the AWS Compute Blog.