About PismoContact Us

Confluent event configuration tutorial [beta]

This article steps you through configuring the Confluent Cloud platform for streaming event delivery. The configuration process involves three things in Confluent Cloud:

  1. Confluent Cloud cluster — Confluent lets you create a managed cluster, where you create the topics through which you can receive data events.
  2. Confluent Cloud topic — A resource inside a cluster to which events are delivered.
  3. API key — A code used to identify and authenticate an application or user.

📘

Prerequisite

Before you begin, you need to create a Confluent Cloud account. This account enables an application to access and use Confluent Cloud.

Configure a cluster

  1. Log in to your Confluent Cloud account.
  2. In the sidebar, click the Environments tab.
  1. Click the Add Cluster button.
  1. Select a cluster type (choose Basic, Standard, or Dedicated).

  1. Select a cloud provider, region, and zones.

  2. Click Continue.

  3. If you choose the Dedicated cluster type, you must select the networking type Internet.

  1. Click Continue.

  2. For encryption-key management, choose either Automatic or Self managed.

  1. Click Continue.

  2. Finish the configuration and then click Launch cluster.

Add a topic

Create a topic in the cluster for events that will be produced and delivered by Pismo.

  1. In the sidebar, click Topics.
  1. Create a topic and enter a topic name.
  1. Click Create with defaults.

Create API key

  1. In the sidebar, click API Keys.
  1. Click the Add Key button.
  1. Click Granular Access and then click Next.
  1. Click the Topic tab.
  1. Do the following:
    • In the Topic name field, enter the name of the topic you created.
    • In the Pattern type field, select LITERAL.
    • In the Operation field, select WRITE.
    • In the Permission field, select ALLOW.
    • Click Next.
  2. Download and take note of the API Key and Secret.
  3. Contact your Pismo representative to provide:
    • Topic name
    • API key (for example, E2ERBNBA7OUI6FMA)
    • API secret (for example, I5RV95UHc1kpkV4BMjWWsoJ+WtBoUDLvhseqKuvw8/cvge2uEoVy4lJkNcqt4I6w)
    • Bootstrap server (for example, pkc-56d1g.eastus.azure.confluent.cloud:9092)
      Pismo uses this info to set up event delivery to the cluster you have created.

Updated about 2 months ago