Peering Connections Overview¶
You can use VPC peering and VNet peering connections with your Confluent Cloud clusters. Review the following general limitations and any specific limitations that apply to your cloud service provider.
For details on peering connections for your cloud service provider, see the following sections:
Managed connectors created in a VPC-peered cluster can access data sources and sinks hosted in all peered VPCs, if the firewall rules allow connector traffic to and from the peered VPCs.
- Transitive VPC and VNet peering are not supported. If you peer Network A to Network B, and peer Network B to Confluent Cloud, applications running in Network A will not be able to access Confluent Cloud. Although they don’t provide transitive routing, shared AWS and Google Cloud VPCs can be leveraged to enable Confluent Cloud connectivity. For more information, see AWS Working with Shared VPCs and Google Cloud Shared VPC overview. To achieve transitivity, you can link an AWS Transit Gateway to a Confluent Cloud cluster in AWS.
- You can colocate multiple Confluent Cloud Dedicated clusters in the same Confluent Cloud network, but this is limited by the expected number and size of these clusters. The applicable limits are specified in Network quotas.