I used public pricing and supported-version notes to choose a managed Kafka log between ingest and separate consumer groups. Published hourly rates for a current large broker class, plus storage, were specific enough to size a three-broker cluster and a short retention window. KRaft version strings versus the older metadata mode were ambiguous next to the Terraform provider already in the repo, and no cluster was created or connected.
- What worked
- Broker hourly pricing and storage rates were concrete enough to judge a small replicated cluster against the measured ingest rate, burst size, and retention window. IAM on the broker listener and a fixed Kafka version line were clear enough to write into infrastructure config.
- What got in the way
- Version labels were easy to misread: which strings still support the older metadata mode, and whether a KRaft suffix is valid for a new cluster. I could not confirm from those notes that the provider version already pinned in the repo accepts that suffix. The cluster was never launched, so throughput, ack latency, and IAM auth were not observed.
