Connect to External Systems

Confluent Cloud offers pre-built, fully managed, Apache Kafka® Connectors that make it easy to instantly connect to popular data sources and sinks. With a simple GUI-based configuration and elastic scaling with no infrastructure to manage, Confluent Cloud Connectors make moving data in and out of Kafka an effortless task, giving you more time to focus on app development.

Source Connector
A source connector, such as the Microsoft SQL Server Source Connector, ingests entire databases and streams table updates to Kafka topics. It can also collect metrics from all of your application servers and store these in Kafka topics, making the data available for stream processing with low latency.
Sink Connector
A sink connector delivers data from Kafka topics into secondary indexes, such as Google BigQuery or batch systems like Amazon S3, for offline analysis.

Note

See Limitations for Connect Confluent Cloud limitations.

Preview Connectors

Caution

Preview connectors are not currently supported and are not recommended for production use.

The following Confluent Cloud connectors are available for preview:

Cloud Platforms Support

The following table shows the cloud platforms supported by each Confluent Cloud connector.

Cloud Connector AWS Azure GCP
Amazon Kinesis Source Connector Yes Yes Yes
Amazon Redshift Sink Connector Yes No No
Amazon S3 Sink Connector Yes No No
AWS Lambda Sink Connector Yes No No
Azure Blob Storage Sink Connector No Yes No
Azure Data Lake Storage Gen2 Sink Connector No Yes No
Azure Event Hubs Source Connector Yes Yes Yes
Azure Functions Sink Connector Yes Yes Yes
Datadog Metrics Sink Connector Yes Yes Yes
Datagen Source Connector Yes Yes Yes
Elasticsearch Service Sink Connector Yes Yes Yes
Google BigQuery Sink Connector No No Yes
Google Cloud Dataproc Sink Connector No No Yes
Google Cloud Functions Sink Connector No No Yes
Google Cloud Spanner Sink Connector No No Yes
Google Cloud Storage Sink Connector No No Yes
Google Pub/Sub Source Connector Yes Yes Yes
Microsoft SQL Server Sink Connector Yes Yes Yes
Microsoft SQL Server Source CDC Connector (Debezium) Yes Yes Yes
Microsoft SQL Server Source Connector Yes Yes Yes
MongoDB Atlas Sink Connector Yes Yes Yes
MongoDB Atlas Source Connector Yes Yes Yes
MySQL Source CDC Connector (Debezium) Yes Yes Yes
MySQL Sink Connector Yes Yes Yes
MySQL Source Connector Yes Yes Yes
Oracle Database Source Connector Yes Yes Yes
PostgreSQL CDC Source Connector (Debezium) Yes Yes Yes
PostgreSQL Sink Connector Yes Yes Yes
PostgreSQL Source Connector Yes Yes Yes
Salesforce CDC Source Connector Yes Yes Yes
Snowflake Sink Connector Yes Yes Yes

Connector controls (GUI-based)

You can use the GUI buttons to start, stop, pause, and delete a connector. Select and display one of your listed connectors to view the controls.

Connector Start, Stop, Pause, and Delete buttons

API for fully-managed connectors

For information and examples to use with the Confluent Cloud API for fully-managed connectors, see the Connect API for Confluent Cloud documentation.

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

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

Preview: Static Egress IP Address Support

Note

Static Egress IP address support is available as a preview feature. Make sure to read and understand what using a preview feature means.

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

Important

Customers must be running a multi-tenant or dedicated Apache Kafka® cluster on AWS and the public Internet (that is, no VPC-peering and no PrivateLink) to use static egress IP addresses. Note this feature is only supported for MongoDB Atlas connectors.

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 (AWS) Yes Fixed set of static egress IP addresses (see static egress IP addresses). None
Public Endpoint (Azure/GCP) 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

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 (AWS) No N/A N/A
Public Endpoint (Azure/GCP) 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

Service Accounts

For information about setting up service accounts, see Service Accounts.

Confluent Cloud Dead Letter Queue

For information about accessing and using the Dead Letter Queue, see Dead Letter Queue.

Connector Limitations

To view a list of connector limitations, see Limitations.

Confluent Cloud Connect Preview

For a description of the Confluent Cloud Connect preview program, see Confluent Cloud Connect Preview.