Skip to content

AWS Technologies Blog

Menu
  • Home
  • KB
  • Services
  • Resources
  • Posts
  • Find
    • Categories
    • Tags
  • About
Menu

Kinesis family

Posted on April 21, 2025 by wpadmin

comparison of Kinesis Data Streams, Kinesis Data Analytics, and Kinesis Data Firehose — all three are part of the AWS Kinesis family, but they serve distinct purposes in a streaming data pipeline.


Kinesis Service Comparison

FeatureKinesis Data StreamsKinesis Data AnalyticsKinesis Data Firehose
Primary RoleReal-time data ingestionReal-time processing of streaming dataNear real-time delivery to AWS destinations
Use CaseCapture high-volume, low-latency dataAnalyze/filter/transform data in motionDeliver data to storage/analytics automatically
Input SourceApplications, services, sensorsKinesis Streams, Firehose, KafkaApplications (direct), Streams, or API
Output TargetLambda, EC2, KDA, custom consumersFirehose, Lambda, S3, Redshift, etc.S3, Redshift, OpenSearch, Splunk, HTTP endpoints
Data StorageTemporary (24 hours default, up to 365 days)No storage — processes on-the-flyNo persistent storage — buffers and delivers
LatencyVery low (milliseconds)Low (seconds to sub-second)Slight delay (usually <60 seconds)
ProcessingExternal consumers handle processingBuilt-in SQL or Apache Flink engineBasic transformations and format conversion
ScalabilityShard-based or on-demandManaged, autoscalingFully managed, scales automatically
Data TransformationNot built-inCustom SQL or Flink-based logicSimple format changes (e.g., JSON to Parquet)
Delivery ReliabilityAt-least-onceAt-least-onceFully managed with automatic retries

Quick Breakdown

1. Kinesis Data Streams

  • Think of it as the raw pipe that captures data events in real time.
  • Requires you to build consumers to read/process the data.
  • Useful when you need custom or fine-grained control over data flow.

2. Kinesis Data Analytics

  • The processing brain for data streams or firehose input.
  • Lets you write SQL or Flink apps to perform filtering, windowing, joins, etc.
  • It can both consume from and publish back to streams or firehose.

3. Kinesis Data Firehose

  • The automatic delivery system.
  • Easiest way to move data from your app or stream into S3, Redshift, OpenSearch, etc.
  • Supports basic transformation, compression, and encryption out-of-the-box.

Example Scenario

Let’s say you’re monitoring website traffic:

  1. Kinesis Data Streams collects click events from all users in real time.
  2. Kinesis Data Analytics aggregates clicks per minute, filters bots, and enriches with geolocation.
  3. Kinesis Data Firehose delivers the enriched data to an S3 bucket in Parquet format for Athena queries.

Let me know if you want diagrams, pricing comparisons, or code examples using all three in a pipeline.

  • Product List
  • Documentation

billing ciem containers cost cspm ebs ec2 ecs edge eks elb event Firewall fsx hybrid iam lambda NACL outpostd policies pop princing rds route53 s3 security serverless services SG siem storage vpc

  • Amazon FSx
  • aws
  • aws notes
  • billing
  • cloud
  • compute
  • containers
  • core
  • databases
  • development
  • ebs
  • ec2
  • ecs
  • edge
  • efs
  • eks
  • hybrid
  • iam
  • lambda
  • network
  • outposts
  • pricing
  • rds
  • route53
  • s3
  • security
  • serverless
  • services
  • storage
  • support
  • vpc
©2025 AWS Technologies Blog | Built using WordPress and Responsive Blogily theme by Superb