Confluent Cloud CLI Overview¶
The Confluent Cloud command line interface (CLI) enables developers to create, manage, and deploy their Confluent components.
The Confluent Cloud CLI requires users to log in with a Confluent Cloud user account.
Confluent Cloud CLI traffic uses the following ports and endpoints:
- Control plane requests are over
443and go to
- Other traffic, for example, for produce/consume, goes over port
9092to Kafka brokers.
The Confluent Cloud CLI only supports basic produce or consume operations. For example, you cannot pass in a properties file using the Confluent Cloud CLI to set other configuration properties or to produce with keys.
For advanced produce or consume operations, use the Confluent
confluent local services kafka produce and
confluent local services kafka consume commands with the
In the Confluent Cloud CLI Command Reference, the following notations were used.
Id of the entity.
ccloud ... listcommand to get the ID of the entity you want to work on.
For example, to delete a ksqlDB app:
List the ksqlDB apps:
ccloud ksql app list
From the output of the above command, get the ID of the ksqlDB app,
Run the command to delete the ksqlDB app:
ccloud ksql app delete <id> [flags]
To learn more about the Confluent Cloud CLI, see these blogs:
- Confluent CLI 1.0 is Now Generally Available for Cloud and Platform
- Confluent CLI Launches Exciting New Features and an Intuitive UI
- Designing and Architecting the Confluent CLI
To quickly try out the Confluent Cloud CLI functionality in your Confluent Cloud cluster, see the Tutorial: Confluent Cloud CLI.