I’ve got a Kinesis Data Stream with an attached lambda.
Records are JSON, like this:

I’ve got a Kinesis Data Stream with an attached lambda.
Records are JSON, like this:

We have a fleet of about 2000 IoT sensors (this number is increasing rapidly) whose data we need to ingest into an AWS S3 bucket for further analysis and display in the UI. The sensors are used by multiple clients, so the data is segregated in the S3 bucket by client ID. Each sensor sends about 60 packets of data, and each data packet consists of some configuration details of the sensor and an array of 1000 values of acceleration data. These 60 packets need to be stitched together and converted to a single file in JSON to represent a single measurement of a duration of 5 seconds.

I have an AWS Lambda function connected to an AWS Kinesis data stream. The volume of data in the stream has recently scaled up significantly, but the number of concurrent executions of the Lambda function has not increased. “Concurrent executions” always hovers around 2-3, even though you can see that the iterator is backed up with quite a few records waiting to be processed in the queue:
(https://i.sstatic.net/wdBhSgY8.png)

I have an AWS Lambda function connected to an AWS Kinesis data stream. The volume of data in the stream has recently scaled up significantly, but the number of concurrent executions of the Lambda function has not increased. “Concurrent executions” always hovers around 2-3, even though you can see that the iterator is backed up with quite a few records waiting to be processed in the queue:
(https://i.sstatic.net/wdBhSgY8.png)