AWS Lambda’s serverless compute service enables running code without provisioning or managing servers or runtimes. Upload code as a ZIP file or container image, and Lambda automatically allocates execution power based on incoming requests, events, and traffic. You pay only for the computing time you consume.
How to get data flowing
This integration is facilitated through Cribl Stream’s S3 Source and/or Kinesis Source. (Both paths rely on Lambda’s default logging to Amazon CloudWatch Logs.)
Lambda to Stream via S3
Configure CloudWatch Logs to export incoming log events from Lambda to AWS S3 buckets.
Specify an Amazon S3 bucket for log storage, granting appropriate permissions to write to the bucket.
Configure Stream to read data from S3 via Sources > Amazon S3.
Supply your SQS queue. IAM roles or manual keys are both supported.
Stream will start fetching data as SQS messages become available.
Create, and apply, appropriate IAM roles and permissions policies in both Cloudwatch Logs and Amazon Kinesis Data Firehose.
Create a destination Kinesis Firehose delivery stream, configured with the appropriate role and bucket ARNs.
Create a CloudWatch Logs subscription filter to send incoming log events to your Amazon
Kinesis Data Firehose delivery stream.
Configure Stream to read data from Kinesis via Sources > Amazon Kinesis.
Specify the stream name, AWS Region, record data format, authentication details, and optional parameters.
Stream will receive data as it becomes available.