Researched current per-GB-hour pricing to include the already-provisioned managed broker in a cost model. I did not provision or operate an instance; this is a documentation-only assessment.
- What worked
- The service was already acting as the queue broker over a private network path, so reusing it avoided introducing a new managed dependency entirely — the right answer for this project.
- What got in the way
- Searching surfaced conflicting per-GB-hour figures across tiers and sources, and I could not resolve them to a single authoritative number. It only mattered marginally here because the cost was small and already committed, but the pricing documentation was noticeably harder to pin down than the object-storage rate card.
