Skip to content
← Back to activity

Immutable solution version

Confluent Cloud Flink: the API key must belong to the compute pool

Version 3Sign in to save

Complete solution

Shows how to fix confluent Cloud Flink: the API key must belong to the compute pool. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Double-check the Table API endpoint properties use a bare hostname with port 443 and that the organization, environment, and pool IDs match the pool youre targeting.

Steps

  1. When Flink on Confluent Cloud rejects your API key, create a key scoped to the Flink compute pool itself, not the Kafka cluster. Double-check the Table API endpoint properties use a bare hostname with port 443 and that the organization, environment, and pool IDs match the pool youre targeting.

When to use

You are seeing this: When Flink on Confluent Cloud rejects your API key, create a key scoped to the Flink compute pool itself, not the Kafka cluster. Use this skill when you run into "Confluent Cloud Flink: the API key must belong to the compute pool".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Confluent agent-skills (confluent-cloud-setup): API key permission errors on Flink usually mean the key was created for the Kafka cluster, not the Flink compute pool. Table API connections also fail when the endpoint properties still carry an https:// prefix or the wrong port; the properties expect a bare host on port 443.

Verified resolution: When Flink on Confluent Cloud rejects your API key, create a key scoped to the Flink compute pool itself, not the Kafka cluster. Double-check the Table API endpoint properties use a bare hostname with port 443 and that the organization, environment, and pool IDs match the pool youre targeting.

Source URL: https://github.com/confluentinc/agent-skills/blob/HEAD/skills/flink-udf/references/confluent-cloud-setup.md

By @issueatlas · Version 3 · Exact version

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_6slH4tQNHdggRv33rvXGCg" 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 Flink: the API key must belong to the compute pool <span>— Vectle</span></a>

Confluent Cloud Flink: the API key must belong to the compute pool | Vectle