Using the Confluent Cloud Console for Cluster Linking with Private Networking
To view, create, and modify cluster links and mirror topics in the Confluent Cloud Console,
the cluster link’s destination cluster must be accessible from
your browser. If your destination cluster is a Confluent Cloud cluster with
private networking, you must have completed the setup described in Access Confluent Cloud Console with Private Networking.
If your browser cannot access the destination cluster, you will not see any
cluster links on that cluster, nor an indication of which topics are mirror
topics. You will not be able to create a cluster link with that cluster as its
If your source cluster is also a Confluent Cloud cluster with private
networking, then some features of the Confluent Cloud Console require your
browser to be able to reach your source cluster, also:
- Creating a “Confluent Cloud to Confluent Cloud” cluster link as an OrgAdmin, which creates ACLs and an API key on the source cluster.
- Viewing the source cluster topics’ throughput metric on a cluster link
- Using the drop-down menu of source cluster topic names to create a mirror topic. Topic names must be entered manually.
When creating a cluster link in the Confluent Cloud Console, rest assured that the
drop-down menus automatically filter for source clusters and destination
clusters that can be linked. If you see a drop-down option for the cluster,
then a cluster link is possible and generally available. Preview cases are excluded
from the drop-downs, and require using the Confluent CLI or
the Confluent Cloud REST API to create a cluster link.
Running Cluster Linking API and CLI Commands with Private Networking
Cluster Linking commands require that the location where you are running them has access to the destination cluster of the cluster link:
- Creating, updating, listing, describing, and deleting cluster links
- Creating, listing, and describing mirror topics
For example, when running the Confluent CLI command, the shell must have access to the
destination cluster. If your destination cluster has private networking, one way
to achieve this is to SSH into a virtual machine that has network connectivity
(by means of Privatelink, Transit Gateway, or Peering) to the destination cluster.
Managing Cluster Links with Private Networking
Aside from the above mentioned requirements, the user experience when using a
cluster link with private networking is the same as when using a cluster link
with public networking. The same commands work in the same ways. That means you
can follow the same Cluster Linking tutorials using the same steps, regardless of
whether your clusters use public or private networking.
Exception: When Cluster Linking from a cluster with private networking to a cluster with public networking (currently in Preview),
a source-initiated link is required. This introduces different configurations and an extra step.