Getting Started with Eventador.io

Eventador has publicly available Fully Managed Kafka that you can try out to get a feeling for how Eventador works or build entire production Kafka clusters. This is called the Instant-On environment.

Step 1: Create an account

If you don't already have an account, create one. Otherwise login and skip this step.

  • Create an account or register via GitHub.
  • Enter credit card info on the accounts page (required for production account and developer plans after trial period)

Step 2: Create a Deployment

A deployment is all the components needed to run Apache Kafka. The zookeeper cluster, the Apache Kafka cluster, network rules, monitoring and stats gathering, access control management, etc. All assets are dedicated and in a unique VPC.

  • Click the Deployments tab from the Eventador Console.
  • Click Create Deployment.
  • Select a plan.
  • Select an AWS region.
  • Name the deployment. For this example we will use the name PrototypeCluster. Click Create.

Screenshot

Step 3: Add an ACL

This step is required for all non enterprise deployments. You will need to add an ACL allow rule for access to your new cluster, all clusters are DENY ALL by default. ACL's are deployment specific.

  • From the deployments list - Click the security button to add an ACL for your deployment.
  • Add an IP range you would like to open in CIDR notation.

Here are a few examples of possible ACL entries and their outcomes. If you have any questions or are unsure of what to allow, feel free to contact Support.

any or ANY or 0.0.0.0/0
Allow traffic from any IP address on the internet. Use this option if you will
be connecting from unknown IP addresses or IP addresses that may change
periodically. One such example is users on Heroku.

199.100.11.1 or 199.100.11.1/32
Allow traffic specifically from 199.100.11.1 only. Using curl -4 ipconfig.me
or visiting http://www.ipconfig.me will typically provide you a single IP
address. Entering an IP address with or without a trailing /32 will allow that
single IP.

199.100.11.0/24
Allow traffic from addresses 199.100.11.0 through 199.100.11.255. If you are on
a corporate network, your IP address may come from a pool of public IPs owned
by your company. Typically these IPs exists in a block or range of IP addresses
close together. Allowing access to the entire block can be achieved by using
the correct CIDR block (/NN) (where N denotes a number).

0.0.0.0/0 opens to the world, so dont do this unless thats really what you
want. To find your ip click the Detect my current IP button or run the
following command: curl -4 ifconfig.co

Screenshot

Step 4: Create a Topic (optional)

A topic is a container to hold a stream of related data in Apache Kafka.

  • From the deployments list - Click on your deployment name - in this case PrototypeCluster.
  • Click on the Apache Kafka link.
  • Click on Add Topic.
  • Name the topic demo and set the number of partitions to 16. Replication factor is set to 1 for development cluster but can be increased in production deployments.
  • Click Create.

screenshot

Kafka Endpoint

Once a deployment is created you have a simple endpoint connection (VIP:port) to use in your applications and when connecting to Kafka. To get the endpoint to use in your applications:

  • From the deployments list - Click on your deployment name - in this case PrototypeCluster.
  • Click on the Apache Kafka link.
  • Click on the Connections tab.
  • Copy+Paste the Plain Text Endpoint value into your applications.
  • Optionally, SSL/SASL endpoints are also exposed. There are code samples on how to use them with popular languages.

NOTE: We highly recommend using SSL connections especially with the Instant-On plans.

Congratulations!

You have setup a new Apache Kafka cluster. Now that your topic is created you’re ready to start sending data. Here is an example of producing and consuming data from your Apache Kafka deployment with Kafkacat.