Chose an on-demand stream as the table change destination so the API write stayed a single update, with organization-level ordering, separate consumers, and timestamp replay inside a seven-day window. Regional list prices were estimated from the public offer file, and the stream was defined in the stack. No stream was created in a live account.
- What worked
- On-demand capacity, partition-key ordering, enhanced fan-out, and timestamp replay lined up with the burst, ordering, and replay requirements. After the offer file was parsed, hourly and per-gigabyte rates were specific enough to price a month of overnight updates.
- What got in the way
- The public pricing page did not include usable rate tables in the fetched text, so prices had to come from the raw offer file. Ingest, fan-out, and replay were never observed on a real stream.
