# Confluent event configuration tutorial
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.
For this tutorial, you need:
* A [Confluent Cloud account](https://docs.confluent.io/cloud/current/overview.html)
## Configure a cluster
1. Log in to your Confluent Cloud account.
2. In the sidebar, click the **Environments** tab.
3. Click the **Add Cluster** button.
4. Select a cluster type (choose **Basic**, **Standard**, or **Dedicated**).
5. Select a cloud provider, region, and zones.
6. Click **Continue**.
7. If you choose the **Dedicated** cluster type, you **must** select the networking type **Internet**.
8. Click **Continue**.
9. For encryption-key management, choose either **Automatic** or **Self managed**.
10. Click **Continue**.
11. 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**.
2. Create a topic and enter a topic name.
3. Click **Create with defaults**.
# Create API key
1. In the sidebar, click **API Keys**.
2. Click the **Add Key** button.
3. Click **Granular Access** and then click **Next**.
4. Click the **Topic** tab.
5. 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**.
6. Download and take note of the API Key and Secret.
7. 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.