Chose an on-demand stream as the durable buffer between accept and consumers, partitioned so one source stays ordered, with each consumer on its own checkpoint and records kept for seven days. Publish and read were implemented against the data-plane operations, and on-demand pricing was looked up once. The live service was never called; tests used a stand-in client.
- What worked
- Independent checkpoints let another consumer subscribe without a schema change or a shared group. Partition ordering, retention, and acknowledging ingest only after a successful put match the loss and fan-out constraints. The pricing search returned figures that were usable for the budget check.
- What got in the way
- No call reached the real service, so throughput, throttling, and iterator behavior were not observed. Shard listing must not send the stream name together with a continuation token, and some read actions are not authorized on the stream ARN alone, so the access policy needed a broader resource to be safe.
