You are viewing documentation for an older version of Confluent Platform. For the latest, click here.

Connecting Schema Registry to Confluent Cloud

You can install and configure Schema Registry for Confluent Cloud.



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.

  1. Configure Schema Registry by modifying etc/schema-registry/ Refer to ~/.ccloud/config to get the Confluent Cloud properties settings to use. 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 master
    # Schema Registry instance and for storing the registered schema data. Note that the SASL_SSL:// prefix is required.
    # REQUIRED: Specifies Confluent Cloud authentication. Refer to the SASL
    # properties in ``~/.ccloud/config`` to get this info.
    # 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 :ref:`Schema Registry configuration options <schema-reg-config>`
    and :ref:`Configuring PLAIN <auth-sasl-plain-schema-registry>`.
  2. Start Schema Registry with the file specified.

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

For more information about running a cluster, see the Schema Registry documentation.