Static Egress IP Addresses for Confluent Cloud Connectors

Use the following information to set up and use static egress IP addresses for connectors running on Amazon Web Services (AWS) and Google Cloud Platform (GCP).

Note

Note the following limitations when using Static egress IP addresses:

  • Public internet only.
  • Available for Confluent Cloud clusters on AWS and GCP.

A list of static egress IP addresses is provided in the Cloud Console. Go to Cluster Settings > Networking to see the addresses.

Static egress IP addresses

Cluster Networking

After you know your static egress IP addresses in Confluent Cloud (that the connector will use), go to the data source or sink provider platform add the static egress IP addresses to the allow list of authorized clients.

If you do not enter all the provided IP addresses, or if you enter any of the IP address numbers incorrectly, you may see the following error message after your connector launches.

There were some errors with your configuration: connection.host: Unable to
connect to the server.

For example:

Connection failure event

Connection failure message

Note that synchronous validation is turned off. If you attempt to load an invalid connector configuration (for example, wrong credentials, collections that do not exist, or an S3 bucket that does not exist) you do not get immediate validation. The connector will start, but then fail with an error message and a list of configuration errors.

For example:

Configuration failure event

Configuration failure message

For additional information about using static egress IP addresses in Confluent Cloud, see Use Static Egress IP addresses.