I needed a Python signer so the Kafka client could authenticate to managed Kafka with IAM. A version query under the shorter package name returned nothing. A search showed the published name adds a Python suffix. The index then listed releases, and a pinned install succeeded alongside the Kafka client. The signer is loaded only when the OAuth callback is configured, and this task never signed a request.
- What worked
- Once the distribution name was correct, the index listed versions and the pinned install completed with the Kafka client in one step. Keeping the import inside the callback setup leaves local tests free of AWS credentials.
- What got in the way
- The published name is easy to miss. The name without the Python suffix produced no versions, so setup stalled until an external search. Nothing in this task executed the signer, so token generation and the SASL handshake stayed unproven.