Hands On: Configuring a Cluster with Public Endpoints

Configuring a Cluster with Public Endpoints

1. Sign up for Confluent Cloud if you have not already done so and respond to the verification email to confirm your account.

2. Log into Confluent Cloud.

3. Create an Environment called “Cloud-Networking.”

4. Click Create a cluster on my own, select a Basic cluster, and Begin configuration.

5. Select AWS as the cloud provider, then select a region and leave availability as Single zone, and click Continue.

6. Give the cluster the name “Public Endpoint Cluster” and click Launch cluster.

7. Review the cluster networking. Click let me explore. Click Cluster overview, Networking.

Test connecting a client to a public cluster.

8. First, get some data into a topic. We can use the Datagen source connector for this purpose. Click on Data integration, and Connectors.

9. Next, search for the Datagen Connector and select it.

10. Now create a topic by clicking Add a new topic, name the topic clickstream, and then click Create with defaults.

11. Select the newly created topic and click Continue.

12. For purposes of this demo, you will enable global access for our connector. In production, it is recommended to use service accounts and specify granular access. Be sure to save the API key and secret pair to a safe place as you will need it later. Click Generate API key and Download.

13. Once you have the credential saved, click continue. Choose the Clickstream template and the output format of JSON and click Continue.

14. Choose one task for the connector and click Continue.

15. Leave the name as the default and click Launch.

Set up a cloud environment to test connectivity.

16. Log in to AWS console and Create a VPC.

Launch an EC2 instance in the VPC, for simulating client traffic.

17. Name the instance and select the Ubuntu AMI.

18. Select a Key pair. You may first need to create one if you haven’t previously done so.

19. Under Network settings, select the networking course VPC that was just created, a public subnet, and a security group that allows SSH access from your local workstation.

20. After completing the EC2 instance configuration, click Launch instance.

19. Associate an Elastic IP address with your EC2 instance so you can ssh in and configure it from your local workstation.

Download the confluent CLI to consume the records.

21. Click CLI and Tools, then follow the instructions to install the CLI on your EC2 instance.

20. Set the environment and cluster, and store the API key for use in consumption.

22. Consume the clickstream data from your public endpoint cluster.

Clean up.

23. Delete the Datagen Connector by going to Data Integration -> Connectors, selecting the connector, and clicking delete. Confirm the deletion by entering the name of the connector.

24. Delete the API keys by clicking Data Integration -> API Keys. Select the API Key you created, click delete API key, and confirm the deletion.

25. Delete the cluster. Click Cluster Overview -> Cluster Settings, then delete cluster. Enter the cluster name to confirm the deletion.