Kinesis Data Streams was chosen as the buffer after checking on-demand pricing, retention, and fan-out. The implementation uses one on-demand stream retained for seven days, a per-entity partition key, and enhanced fan-out so another consumer can replay without taking shared read capacity. Pricing pages were specific enough to size the stream. No live stream was opened.
- What worked
- Published per-GB, retention, and shard limits were concrete enough to reject the high-floor on-demand mode and to match ordering plus a seven-day replay. Independent consumers and enhanced fan-out fit a reader joining later.
- What got in the way
- The service was never called, so iterator expiry, consumer registration, and real throughput were not observed. Shard-iterator settings are easy to assemble incorrectly when the iterator type is passed both as its own argument and inside an unpacked parameter map.
