Internet Access to Resources¶

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 in Confluent Cloud.

Public and Private IP addresses¶

Refer to the following sections to determine your cloud networking configuration for connectors that do not use static egress IP addresses.

Public IP address accessible over the Internet¶

The following table provides connectivity information for a managed connector with a public IP address accessible over the Internet.

Cluster Network Type	Connectivity Supported?	Data Plane Network Access	Control Plane Network Access
Public Endpoint	Yes	Public IP/CIDR range where the Confluent Cloud cluster is located.	Public IP/CIDR range for us-west-2
VPC Peering and Transit Gateway	Yes	Public IP/CIDR range where the Confluent Cloud cluster is located.	Public IP/CIDR range for us-west-2
Private Link	Yes	Public IP/CIDR range where the Confluent Cloud cluster is located.	Public IP/CIDR range for us-west-2

Tip

See the following cloud provider documentation for additional information:

Private IP address hosted in a customer VPC¶

The following table provides connectivity information for a managed connector with a private IP address hosted in a customer VPC.

Cluster Network Type	Connectivity Supported?	Data Plane Network Access	Control Plane Network Access
Public Endpoint	No	N/A	N/A
VPC Peering and Transit Gateway	Yes	Source IP address used is from the /16 CIDR configured by the customer for the Confluent Cloud Cluster.	None
Private Link	No	N/A	N/A

Static Egress IP Address Support¶

To determine your cloud networking configuration, refer to the following: for connectors running on AWS that use static egress IP addresses.

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).