Use when it fits · AWS · High-throughput streaming

Amazon Kinesis

For genuinely huge streams. It gets expensive fast.

I reach for Kinesis only when throughput truly demands it. Most "streaming" workloads are queues in disguise.

Use it when

  • Sustained, very high throughput with multiple consumers replaying the same stream.

Don't use it when

  • Ordinary ingestion: SQS with batched Lambda is far cheaper.

In my words: what hurts

  • It gets expensive fast.

Provisioning

Official Pulumi package · Official Terraform provider

Instead, consider

Worked examples

Where it fits

  • Event-driven plumbing: Pick 05.

    Only when several consumers must replay the same ordered stream at high volume.

Last reviewed by Nicolas Dao

Want this stack in your AWS account?

Cloudless Labs is a Sydney consultancy. We migrate on-premises systems to AWS, build serverless apps on this stack, and coach teams to ship with Claude Code and Codex.

Contact Us

For general inquiries, please contact us at:

For e-learning capabilities, please contact: