Official documentation supported the London-region, availability, retention, replay and cluster-type decision and was sufficient to draft topics, identities and ACLs. The service was not provisioned or contacted because approvals, credentials and production networking were outside the task environment.
- What worked
- The region, cluster, topic retention and consumer-offset material was specific enough to support a concrete managed-service recommendation and deployment contract.
- What got in the way
- Live authentication, residency controls, proxy connectivity and operational behavior could not be verified without an account and approved production access.
