This is an example event producer for [Amazon Kinesis] kinesis written in Scala and packaged as an SBT project.
This was built by the [Snowplow Analytics] snowplow team, as part of a proof of concept for porting our event collection and enrichment processes to run on Kinesis.
This has been built to run in conjunction with the [kinesis-example-scala-consumer] consumer.
This project requires Java 1.7 and SBT 0.13.0.
If you are running Vagrant, you can run it using the Snowplow [dev environment] dev-environment. Make sure you run the jvm-7 jvm-7 Ansible Playbook to install both the required Java version and SBT. Instructions on using Ansible to run the different playbooks can be found on the [dev environment README] dev-env-readme.
Assuming you already have [SBT 0.13.0] sbt installed:
$ git clone git://github.com/snowplow/kinesis-example-scala-producer.git
$ cd kinesis-example-scala-producer
$ sbt compile
To come.
The event producer has the following command-line interface:
kinesis-example-scala-producer: Version 0.1.1. Copyright (c) 2013, Snowplow
Analytics Ltd.
Usage: kinesis-example-scala-producer [OPTIONS]
OPTIONS
--config filename Configuration file. Defaults to "resources/default.conf"
(within .jar) if not set
Create your own config file:
$ cp src/main/resources/default.conf my.conf
Now edit it and update the AWS credentials:
aws {
access-key: "cpf"
secret-key: "cpf"
}Make sure that the AWS credentials you use have the permissions required to:
- Create and write to the Kinesis stream specified in the config file
- Create tables in DynamoDB
You can leave the rest of the settings for now.
Next, run the event producer, making sure to specify your new config file. The stream will be created if it doesn't already exist.
$ sbt "run --config ./my.conf"
Finally, verify that events are being sent to your stream by using [snowplow/kinesis-example-scala-consumer] kinesis-consumer or checking the [Kinesis Management Console] kinesis-ui:
Fork this project and adapt it into your own custom Kinesis event producer.
Is a Kinesis event producer the right place to put stream setup code?
Probably not - best practice would be to handle this as part of your standard AWS devops flow, assigning appropriately-locked down IAM permissions etc. However, this stream setup functionality is included in this project, to simplify getting started.
What about an example Kinesis event consumer aka "Kinesis application" in Scala?
See [snowplow/kinesis-example-scala-consumer] consumer.
- Add support for ordered events in the stream [#1]
- Add logging output to the producer [#2]
- Add live Kinesis integration tests to the test suite [#3]
- Add ability to send events as Avro [#5]
- Rebase to run on top of Akka (maybe) [#6]
If you would like to help with any of these, feel free to submit a pull request.
Copyright 2013 Snowplow Analytics Ltd, with portions copyright 2013 Amazon.com, Inc or its affiliates.
Licensed under the [Apache License, Version 2.0] license (the "License"); you may not use this software except in compliance with the License.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.