Access AWS PrivateLink or Azure Private Link with Confluent Cloud Console
When you enable a Confluent Cloud cluster for AWS PrivateLink or Azure Private Link,
some Confluent Cloud Console components, including topic management and ksqlDB, use cluster
endpoints that are not publicly reachable. You must configure your network to route requests
for these components over the AWS PrivateLink, or Azure Private Link, connection.
Unlike VPC peering, AWS PrivateLink and Azure Private Link do not require the use of a proxy to
forward traffic from your browser through your VPC or VNet to the Confluent Cloud cluster.
To access your cluster data in Confluent Cloud Console, when AWS PrivateLink or
Azure Private Link is enabled:
- Open the Confluent Cloud Console and go to your cluster. An error banner displays
stating that your cluster is not accessible over the internet and includes
the endpoint that you need to route to.
- Copy the endpoint that you need to route to.
- Configure your DNS provider to route browser requests to the UI endpoint
and then to the endpoint (VPC or Private Endpoint) connected to Confluent Cloud.
The Confluent Cloud Console displays your cluster’s data.