Connect Self-Managed Schema Registry to Confluent Cloud

You can work with Schema Registry on Confluent Cloud in multiple ways:

To learn requirements and options for working with Schema Registry by means of access control lists (ACLs) and role-based access control (RBAC), see access control lists (ACLs), RBAC role, and Access control (RBAC) for Stream Lineage.

Connect self-managed Schema Registry to Confluent Cloud

You can connect a self-managed or on-premises Schema Registry to Confluent Cloud as described in this section.



The Confluent Platform installation provides the binaries for Schema Registry that run locally and connect to your Confluent Cloud cluster. You do not have to start the other Confluent Platform services.

Configure and connect

  1. Configure Schema Registry by modifying etc/schema-registry/ The minimally required Schema Registry property settings for Confluent Cloud are provided below:

    # If set to true, API requests that fail will include extra debugging information, including stack traces.
    # REQUIRED: Specifies the bootstrap servers for your Kafka cluster. It is used for selecting the primary
    # Schema Registry instance and for storing the registered schema data.
    # REQUIRED: Specifies Confluent Cloud authentication. required \
      username="<api-key>" \
    # Configures Schema Registry to use SASL authentication.
    # Configures Schema Registry for SSL encryption.
    # Specifies the name of the topic to store schemas in.
    # Specifies the address the socket server listens on. The format is
    # "listeners = listener_name://host_name:port". For example, "listeners = PLAINTEXT://".

    For more information, see Schema Registry configuration options, Configuring PLAIN, and Quick Start for Schema Management on Confluent Cloud (for native cloud Schema Registry).

  2. Start Schema Registry with the file specified.

    bin/schema-registry-start etc/schema-registry/

Docker environment

You can run a mix of fully-managed services in Confluent Cloud and self-managed components running in Docker. For a Docker environment that connects any Confluent Platform component to Confluent Cloud, see cp-all-in-one-cloud.

Suggested reading