An application writes real-time streaming data of chats into Amazon Kinesis Data Streams partitioned by user id. Before writing this data into an Amazon Elasticsearch Service cluster (now Amazon OpenSearch Service), an AWS Lambda function checks the content for validation. The validation procedure must receive the data of a specific user in the sequence in which the Kinesis data stream received it without changing the order. However, during peak hours, the lag between data received in Kinesis Data Streams to the data reaching OpenSearch Service is very high, thereby resulting in data anomalies. Which of the following is the best way to fix this issue with the least amount of operational overhead?