A company collects logs from on-premises devices on an on-premises server. The company wants a near real-time analytics solution using AWS services and needs to retain logs for 365 days for pattern matching and substring searches, with minimal development effort. Which solution meets these requirements with the least development overhead?

The correct solution leverages Kinesis Agent to efficiently stream logs from on-premises to Kinesis Data Firehose, which then delivers them to Amazon OpenSearch Service. OpenSearch Service is ideal for near real-time pattern matching and substring searches, and its Index State Management (ISM) policies simplify data retention for 365 days. Amazon Managed Service for Apache Flink can perform real-time processing on the Kinesis stream before it reaches OpenSearch. This combination offers a fully managed, scalable solution with minimal development effort. Incorrect options: DynamoDB is not optimized for complex pattern matching and substring searches across large log datasets. Athena on S3 would be better for querying, but the initial DynamoDB choice is suboptimal. Deploying Amazon MSK on-premises is not a standard or efficient way to integrate with AWS services for log analytics. MSK is typically deployed within AWS. Using API Gateway and Lambda to write to DynamoDB for log analytics is less efficient and more complex for high-volume log ingestion compared to Kinesis Data Firehose, and DynamoDB still lacks the search capabilities of OpenSearch.