Kinesis Throughput Calculator

shards = max(ceil(MB/s ÷ 1), ceil(records/s ÷ 1000), ceil(consumers × MB/s ÷ 2)) × (1 + headroom), where MB/s = records/s × record KB ÷ 1024. Three separate limits set the shard count and the largest one wins: write bandwidth at 1 MB/s, write rate at 1000 records/s, and read bandwidth at 2 MB/s shared by all standard consumers. That third limit is the one that surprises people — adding a fourth consumer to a stream running near its read ceiling forces a reshard even though ingest has not changed. Confirm shard hour and PUT unit prices for your region.

Resharding a live stream is disruptive and changes ordering guarantees for in-flight partition keys, so it is far better to size with headroom up front than to discover the read limit during a backfill.

This calculator takes 8 inputs: Records written per second, Average record size, Consumer applications, Use enhanced fan-out, Headroom to add for spikes, Shard hour price, Price per million PUT payload units, Enhanced fan-out consumer-shard hour price. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Writes are metered in 25 KB PUT payload units, so a 1 KB record wastes 96% of a unit. Aggregating many small records into one larger record with the Kinesis Producer Library, or batching with PutRecords, is the standard fix and can cut the write meter by an order of magnitude.

When you have more than two or three consumers, or need sub-200 ms propagation. Enhanced fan-out gives each consumer its own 2 MB/s per shard so consumers stop competing, but it adds a per-consumer-shard-hour charge that grows with both the consumer count and the shard count.