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 UI-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 connector.

Cloud Connector AWS Azure GCP
Amazon CloudWatch Logs Source Yes Yes Yes
Amazon CloudWatch Metrics Sink Yes No No
Amazon DynamoDB Sink Yes No No
Amazon Kinesis Source Yes Yes Yes
Amazon Redshift Sink Yes No No
Amazon SQS Source Yes Yes Yes
Amazon S3 Sink Yes No No
AWS Lambda Sink Yes No No
Azure Blob Storage Sink No Yes No
Azure Cognitive Search Sink No Yes No
Azure Cosmos DB Sink No Yes No
Azure Data Lake Storage Gen2 Sink No Yes No
Azure Event Hubs Source Yes Yes Yes
Azure Functions Sink No Yes No
Azure Service Bus Source Yes Yes Yes
Azure Synapse Analytics Sink No Yes No
Databricks Delta Lake Sink Yes No No
Datadog Metrics Sink Yes Yes Yes
Datagen Source Yes Yes Yes
Elasticsearch Service Sink Yes Yes Yes
GitHub Source Yes Yes Yes
Google BigQuery Sink No No Yes
Google Cloud BigTable Sink No No Yes
Google Cloud Dataproc Sink No No Yes
Google Cloud Functions Sink No No Yes
Google Cloud Spanner Sink No No Yes
Google Cloud Storage Sink No No Yes
Google Pub/Sub Source Yes Yes Yes
HTTP Sink Yes Yes Yes
IBM MQ Source Yes Yes Yes
Microsoft SQL Server Sink Yes Yes Yes
Microsoft SQL Server Source CDC (Debezium) Yes Yes Yes
Microsoft SQL Server Source Yes Yes Yes
MongoDB Atlas Sink Yes Yes Yes
MongoDB Atlas Source Yes Yes Yes
MQTT Sink Yes Yes Yes
MQTT Source Yes Yes Yes
MySQL Source CDC (Debezium) Yes Yes Yes
MySQL Sink Yes Yes Yes
MySQL Source Yes Yes Yes
Oracle Database Sink Yes Yes Yes
Oracle Database Source Yes Yes Yes
PagerDuty Sink Yes Yes Yes
PostgreSQL CDC Source (Debezium) Yes Yes Yes
PostgreSQL Sink Yes Yes Yes
PostgreSQL Source Yes Yes Yes
RabbitMQ Sink Connector Yes Yes Yes
RabbitMQ Source Yes Yes Yes
Redis Sink Yes Yes Yes
Salesforce Bulk API Source Yes Yes Yes
Salesforce CDC Source Yes Yes Yes
Salesforce Platform Event Sink Yes Yes Yes
Salesforce Platform Event Source Yes Yes Yes
Salesforce PushTopic Source Yes Yes Yes
Salesforce SObject Sink Yes Yes Yes
ServiceNow Sink Yes Yes Yes
ServiceNow Source Yes Yes Yes
SFTP Sink Yes Yes Yes
SFTP Source Yes Yes Yes
Snowflake Sink Yes Yes Yes
Solace Sink Yes Yes Yes
Splunk Sink Yes Yes Yes
Zendesk Source Yes Yes Yes

Cloud Console connector controls

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

Confluent CLI upgrade

The CLI steps for managed connectors show examples using version 2 of the Confluent CLI. For more information see, Migrate to Confluent CLI v2.

API for fully-managed connectors

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

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

Connector data previews

For information about connector data previews, see Connector Data Previews.

Single message transforms

For information about using single message transforms (SMTs), see Single Message Transforms for Managed Connectors.

View connector events

For information about viewing Confluent Cloud connector events, see View Connector Events.

Service accounts

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

Dead letter queue

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

Connector limitations

To view a list of connector limitations, see Limitations.

About preview features

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