Register the consumer: aws kinesis register-stream-consumer --stream-arn <arn> --consumer-name my-app; the API returns a ConsumerARN
Subscribe to a shard using SubscribeToShard with the ConsumerARN and a StartingPosition (TRIM_HORIZON, LATEST, AT_SEQUENCE_NUMBER, or AT_TIMESTAMP)
Read from the HTTP/2 event stream returned by SubscribeToShard; each shard delivers up to 2 MB/sec dedicated throughput to this consumer independent of other consumers on the same shard
Handle SubscribeToShard expiration: subscriptions auto-expire after 5 minutes; resubscribe using the sequence number of the last processed record as the next AT_SEQUENCE_NUMBER starting position
Deregister consumers you no longer use: aws kinesis deregister-stream-consumer --consumer-arn <arn> to free slot capacity
Monitor consumer read throughput with the GetRecords.IteratorAgeMilliseconds and SubscribeToShard.IteratorAgeMilliseconds CloudWatch metrics per shard
Known gotchas
Provisioned and On-demand Standard streams support up to 20 registered enhanced fan-out consumers per stream; On-demand Advantage mode raises this to 50 — plan consumer registration budgets accordingly
Enhanced fan-out uses a push model over HTTP/2; if the consumer cannot keep up with 2 MB/sec, the shard will back-pressure and records will age — monitor IteratorAgeMilliseconds and scale consumer processing capacity
Enhanced fan-out consumers are registered at stream level, not shard level; after a shard split or merge you must resubscribe to the new child shards using the new shard IDs
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp