Configuring Access to the Confluent Cloud Web UI with AWS and Azure Private Link
Some Confluent Cloud web UI components like topic management and ksqlDB use cluster
endpoints that are not publicly reachable when AWS or Azure Private Link is enabled
for a cluster. You must configure your network to route requests for these components
over the Private Link connection.
Unlike VPC peering, AWS and Azure Private Link do not require use of a proxy to
forward traffic from your browser through your VPC or VNET to the Confluent Cloud cluster.
You might have to configure multiple endpoints for topic management,
consumer lag, and ksqlDB.
- Copy the specific endpoint from the banner in Confluent Cloud web UI.
- Configure your DNS provider to route requests from your browser to the UI endpoint
to the VPC Endpoint or Private Endpoint you have connected to Confluent Cloud.
- The Confluent Cloud web UI will display your cluster’s data.