Ingest from Confluent Cloud

You can create a connection to Confluent Cloud, a fully managed, cloud-native service for Apache Kafka to ingest data into Imply Polaris.

The following characteristics apply to ingestion from Confluent Cloud to Polaris:

• Exactly-once guarantees.
• Occurs across the Internet with TLS encryption and SASL authentication.

Confluent Cloud connection information

• Topic name: The name of the Confluent Cloud topic that contains the event data.

• Bootstrap servers: A list of one or more host and port pairs representing the addresses of brokers in the Kafka cluster. This list should be in the form host1:port1,host2:port2,... For details on where to find the bootstrap server in Confluent Cloud, see Access cluster settings in the Confluent Cloud Console.

  You can also use the Confluent Cloud API to read a cluster and find its bootstrap server information in the kafka_bootstrap_endpoint of the cluster object.

• A Confluent Cloud API key with access to Kafka resources: The API key consists of a key and a secret. The Polaris connection takes both the key and the secret to access data through the connection. Note that resource-specific API keys in Confluent Cloud require an access control list that restricts access. For information on creating and managing API keys in Confluent Cloud, see Use API Keys to Control Access.

The following screenshot shows an example of a successful connection created in the UI:

When you have your table, connection, and ingestion job set up for Confluent Cloud, Polaris automatically ingests data from Kafka topic as data enters the topic defined in the connection.

Learn more

To learn how to ingest data from Confluent Cloud using the Polaris API, see Ingest data from Confluent Cloud by API.