Confluent Developer Marketplace Get started
  1. Home
  2. Cloud
  3. Govern Data Streams in Confluent Cloud
  4. Fundamentals
  5. Enable Private Networking

Use Confluent Cloud Schema Registry to Connect to a Public Endpoint in a Private Networking Environment

If you have a private networking environment and you want to use Confluent Cloud Schema Registry, you must open outbound calls (egress) to a public Schema Registry endpoint. Outbound access is required because Confluent Cloud Schema Registry is a multi-tenant Schema Registry.

To connect privately without egressing to the public internet, see Enable Private Networking on Confluent Cloud for Schema Registry.

Prerequisites

  • Confluent Cloud Schema Registry is enabled and configured. For more information about supported features, see Manage Schemas in Confluent Cloud.

  • You must expose port 443 or otherwise manage a TCP-HTTPS (SSL/TLS) port forwarding scheme. You need this to access the managed Confluent Cloud Schema Registry.

Configure Schema Registry to allow outbound calls to your private network

  1. Navigate to a cluster to get to the Schema Registry settings in an environment.

  2. On the information panel under Stream Governance API, note the Schema Registry endpoint. For example, https://confluent.us-east-2.aws.confluent.cloud.

    Stream Governance API panel showing the Schema Registry endpoint URL

  3. Open outbound calls to the Confluent Cloud Schema Registry endpoint. Follow the instructions based on your cloud provider.

    Azure VNet

    Configure outbound call access for Azure networking components. Follow the instructions in the Azure networking documentation.

    AWS VPC

    Configure outbound call access for these AWS VPC networking components:

    Google Cloud VPC

    Configure outbound call access for Google Cloud networking components. Follow the instructions in the Google Cloud networking documentation.

  4. Optional: Verify that your Schema Registry credentials are properly configured, where Schema Registry API key (<schema-registry-api-key>), API secret (<schema-registry-api-secret>), and endpoint (<schema-registry-endpoint>) are specified.

    Run this command to authenticate with the cluster and list the topics registered in your schema.

    curl -u <schema-registry-api-key>:<schema-registry-api-secret> \
<schema-registry-endpoint>/subjects

    If no subjects are created, your output will be empty ([]). If you have subjects, your output should resemble:

    ["test2-value"]

    Here is an example command:

    curl -u <schema-registry-api-key>:<schema-registry-api-secret> \
https://psrc-lq2dm.us-east-2.aws.confluent.cloud/subjects