A smart home security company is designing a high-performing ingestion pipeline for security camera event logs. The pipeline must ingest log payloads from cameras, with each camera sending a JSON payload every . The solution must process these logs with sub-second latency to perform anomaly detection and trigger immediate alerts. Additionally, all raw logs must be archived in Amazon S3 for historical analysis, partitioned by date. Which two actions should a solutions architect recommend to meet these requirements with the lowest operational overhead? (Select two.)
- Configure an Amazon Kinesis Data Stream in On-Demand capacity mode to ingest the camera event logs, and use an AWS Lambda function to process the stream for real-time anomaly detection.Answer
- Configure an Amazon Kinesis Data Firehose delivery stream that uses the Kinesis Data Stream as the source to batch and write the raw logs to Amazon S3, using custom prefixes for date-based partitioning.Answer
- CConfigure an Amazon Kinesis Data Stream in Provisioned capacity mode with 5 shards to ingest the logs, and consume the stream using an AWS Lambda function for real-time alerting.
- DConfigure an Amazon SQS standard queue to ingest the logs from the cameras, and deploy a consumer application on Amazon EC2 instances to process the logs in strict sequential order before archiving them to Amazon S3.
- EConfigure Amazon Simple Notification Service (Amazon SNS) to ingest the logs directly from the cameras, and subscribe an Amazon Kinesis Data Firehose delivery stream to route logs to both Amazon S3 and Amazon DynamoDB for real-time queries.
Answer
Configure an Amazon Kinesis Data Stream in On-Demand capacity mode to ingest the camera event logs, and use an AWS Lambda function to process the stream for real-time anomaly detection. Additionally, configure an Amazon Kinesis Data Firehose delivery stream that uses the Kinesis Data Stream as the source to batch and write the raw logs to Amazon S3, using custom prefixes for date-based partitioning.
The correct architecture leverages Amazon Kinesis Data Streams in On-Demand capacity mode to ingest the stream of security camera logs, which automatically scales to support records per second without administrative intervention. An AWS Lambda function consumes this stream to trigger anomalies with sub-second latency. To satisfy the archiving requirement, Amazon Kinesis Data Firehose reads from the same Kinesis Data Stream, batches the records, and writes them to Amazon S3 using date-based partitioning prefixes, optimizing both cost and operational complexity.
Step-by-Step Solution
Key Concept
Decoupling high-performance stream ingestion for real-time processing and managed archiving using Amazon Kinesis Data Streams and Amazon Kinesis Data Firehose.