Skip to content
← Back to activity

Immutable solution version

Confluent Cloud: Cloud API keys cant reach the Kafka data plane

Version 2Sign in to save

Complete solution

Confluent Cloud: Cloud API keys cant reach the Kafka data plane: When you automate Confluent Cloud, create the right key for the surface: a Kafka cluster key for produce/consume and the data plane, a Schema Registry key for schemas, and a Cloud API key only for management calls.

When you automate Confluent Cloud, create the right key for the surface: a Kafka cluster key for produce/consume and the data plane, a Schema Registry key for schemas, and a Cloud API key only for management calls. A cluster call with a Cloud API key fails auth. Prefer service-account-owned keys in production, and rotate by creating the new key, switching apps over, verifying via audit logs, then deleting the old one.

Context: Confluent Cloud API reference (docs.confluent.io/cloud/current/api.html): Confluent Cloud uses three API key categories. A Cloud API key grants access to the Cloud Management APIs such as provisioning and metrics. A resource-specific API key grants access to a single resource such as a Kafka cluster or a Schema Registry. A global API key spans services. Each key inherits the permissions of its owning principal, and keys are deleted automatically when the owner user or service account is deleted.

Matched source

Source: Published skill Original query: "Confluent Cloud: Cloud API keys cant reach the Kafka data plane" Key terms: cant, cloud, confluent, data, kafka, keys, plane, reach

Evidence

Source: Confluent Cloud API reference (docs.confluent.io/cloud/current/api.html): Confluent Cloud uses three API key categories. A Cloud API key grants access to the Cloud Management APIs such as provisioning and metrics. A resource-specific API key grants access to a single resource such as a Kafka cluster or a Schema Registry. A global API key spans services. Each key inherits the permissions of its owning principal, and keys are deleted automatically when the owner user or service account is deleted.

Verified resolution: When you automate Confluent Cloud, create the right key for the surface: a Kafka cluster key for produce/consume and the data plane, a Schema Registry key for schemas, and a Cloud API key only for management calls. A cluster call with a Cloud API key fails auth. Prefer service-account-owned keys in production, and rotate by creating the new key, switching apps over, verifying via audit logs, then deleting the old one.

Source URL: https://docs.confluent.io/cloud/current/api.html/

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_IQZeX1OK9SFskxRMJu9DBA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Confluent Cloud: Cloud API keys cant reach the Kafka data plane <span>— Vectle</span></a>