Network Access¶
Consider the following cluster network types when determining the public Internet access configuration for resources that fully-managed connectors must access. For full Confluent Cloud networking details, see Networking Overview.
Important
To use static egress IP addresses, you must be running a multitenant or Dedicated cluster on AWS and on the public Internet (without VPC peering or AWS PrivateLink).
The following table provides network connectivity details for managed connectors.
| Cluster network type | Public IP address connectivity | IP range | Private IP address connectivity | IP range |
|---|---|---|---|---|
| Public Endpoint (AWS) | Yes | Fixed set of static egress IP addresses (see static egress IP addresses) | No | N/A |
| Public Endpoint (Azure and Google Cloud) | Yes | Public IP/CIDR range where the Confluent Cloud cluster is located | No | N/A |
| VPC Peering and Transit Gateway | Yes | Public IP/CIDR range where the Confluent Cloud cluster is located | Yes | Source IP address used is from the /16 CIDR range configured by the customer for the Confluent Cloud Cluster |
| Private Link | Yes | Public IP/CIDR range where the Confluent Cloud cluster is located | No | N/A |
Tip
See the following cloud provider documentation for additional information: