Arkinu
AWS service comparison

Amazon Kinesis vs Amazon Kinesis Video Streams: differences and when to use each

Amazon Kinesis
Amazon Kinesis Video Streams

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Analytics

Amazon Kinesis

Family of services for streaming data. Kinesis Data Streams collects and processes streams of records in real time with your own consumer applications, and Amazon Data Firehose delivers streaming data, without writing applications, to destinations such as Amazon S3, Amazon Redshift, or Amazon OpenSearch Service.

Exam phrases that point here

  • «collect and process streaming data in real time»

    Kinesis Data Streams ingests continuous streams of records (clicks, logs, telemetry) and makes them available to consumer applications within seconds or less.

    When not: If you only need to move that data to Amazon S3, Amazon Redshift, or Amazon OpenSearch Service without writing consumers, and a delay of a few seconds or minutes is acceptable, Amazon Data Firehose is a better fit. If the company already uses Apache Kafka, think of Amazon MSK; if what arrives is video, think of Amazon Kinesis Video Streams.

  • «multiple applications must read the same data at the same time»

    In a data stream, each consumer application reads the full stream independently: one can compute metrics while another archives, without taking records away from each other.

    When not: If each message must be processed by a single worker and then disappear, the pattern is a queue (Amazon SQS). If the message must be pushed to multiple subscribers as a notification, think of Amazon SNS.

  • «reprocess the data from the last few days»

    Kinesis Data Streams keeps records for the retention period, so a consumer can read them again from an earlier point, for example after fixing a bug.

    When not: The default retention is 24 hours; for longer you have to extend it, and that costs money. If the goal is to keep the history for months or years so it can be queried, it is usually archived in Amazon S3 (for example, with Firehose).

  • «load streaming data into Amazon S3, Amazon Redshift, or Amazon OpenSearch Service without managing applications»

    Amazon Data Firehose is a managed delivery service: producers send data, and Firehose batches it, optionally transforms it, and delivers it to the configured destination.

    When not: Firehose accumulates data by size or by time before delivering it, so it is near real time, not instantaneous. If you need to process each record with your own logic, with multiple consumers or with reprocessing, use Kinesis Data Streams.

  • «convert the data to Apache Parquet before storing it in Amazon S3»

    Firehose can convert JSON records to columnar formats such as Parquet or ORC and partition the data in S3 during delivery, which makes later queries cheaper and faster.

    When not: If the transformation is a complex batch ETL over data that is already stored, AWS Glue is a better fit. If it is enough to query the data as it sits in S3, Amazon Athena can read it without prior conversion.

  • «process each device's records in order»

    The partition key decides which shard each record goes to; records with the same key go to the same shard and are read in the order they were written.

    When not: If what you need is ordering plus per-message acknowledgment and deletion by a single consumer, an Amazon SQS FIFO queue with a message group ID may be a better fit.

Often paired with

  • AWS Lambda
  • Amazon S3
  • Amazon Redshift
  • Amazon OpenSearch Service
Study Amazon Kinesis →

Media Services

Amazon Kinesis Video Streams

Managed service for streaming live video from devices, such as security cameras, smartphones, or drones, to the AWS Cloud. It lets you process the video in real time or store it for a retention period to analyze it in batches.

Exam phrases that point here

  • «stream video from cameras to AWS to store and analyze it»

    Amazon Kinesis Video Streams ingests video from devices such as cameras, phones, or drones, stores it encrypted and indexed by time, and makes it available for playback or processing.

    When not: If the goal is to produce broadcast-quality live video for television or many screens, think of AWS Elemental MediaLive. If what arrives is data records (clicks, telemetry), not video, Amazon Kinesis Data Streams is the fit.

  • «play live or recorded camera video in an application»

    Kinesis Video Streams offers managed playback with HLS and DASH, live or recorded, without building your own streaming infrastructure.

    When not: HLS playback has a delay of a few seconds. If you need two-way communication with very low latency, the WebRTC capability of the same service is the fit.

  • «low-latency two-way video and audio between a device and a mobile app»

    Kinesis Video Streams with WebRTC manages signaling and the STUN and TURN servers for peer-to-peer connections, for example in video doorbells or baby monitors.

    When not: If what matters is storing the video to watch or analyze it later, use video streams with retention, not a WebRTC session.

  • «apply machine learning to live camera video»

    Kinesis Video Streams delivers the video to consumer applications that can process it in real time with computer vision models, your own or from AWS services.

    When not: If the video is already stored as a file in Amazon S3, you do not need Kinesis Video Streams to analyze it. Amazon Rekognition streaming video analysis has not been available to new customers since April 30, 2026.

  • «ingest time-encoded data, such as radar or lidar»

    The service is not limited to video: it supports any time-series data in which each fragment relates to the previous ones, such as audio, radar, or lidar.

    When not: If the data consists of individual sensor readings (temperature, position), the usual pattern is Amazon Kinesis Data Streams or IoT services.

Study Amazon Kinesis Video Streams →