Confluent integration
Manage Confluent Cloud access, API keys, and routine Kafka administration from service requests and approval workflows.
What it connects
- Retrieve environments, clusters, and topics to scope access and change requests correctly.
- Pull users, service accounts, and role bindings to see who has access to which resources.
- Retrieve API keys and their owners for access reviews and offboarding checks.
- Pull connector status and consumer group lag when a data pipeline looks stuck.
What it automates
- Invite users to Confluent Cloud when a new engineer needs access.
- Create or delete role bindings to grant or remove access to specific clusters and resources.
- Create or delete API keys and service accounts for applications and teams.
- Create topics, update topic settings, and restart or pause connectors from a support ticket.
In practice
- A developer requests access to a Kafka cluster. After approval, STLabs invites them if needed and adds a role binding scoped to that cluster.
- When an engineer leaves, STLabs pulls their Confluent role bindings and API keys, then deletes them after the owning team confirms.
- A team reports that a connector stopped moving data. STLabs checks the connector status and restarts it when the owner agrees.
- A new service needs its own credentials. After approval, STLabs creates a service account and API key for it in the right environment.
