Thousands of devices publish telemetry. Several independent applications must read the stream, replay recent records, and process records for each device in order. Producers already emit each device's records in sequence. Which design best meets these ingestion requirements?

1. Write all telemetry to one SQS standard queue and let the applications compete for messages.
2. Use an SNS topic without durable subscriber storage and assume subscribers can replay any earlier published record.
3. Append all devices' records to one EC2 instance's local log and restart the instance to scale consumers.
4. Use Kinesis Data Streams, choose device identifiers as partition keys, and size stream and consumer capacity for the load.