1. Home
  2. Blog
  3. Releases

Snowplow 82 Tawny Eagle released with Kinesis Elasticsearch Service support

Jump to

We are happy to announce the release of Snowplow 82 Tawny Eagle! This release updates the Kinesis Elasticsearch Sink with support for sending events via HTTP, allowing us to now support Amazon Elasticsearch Service.

  1. Kinesis Elasticsearch Sink
  2. Distribution changes
  3. Upgrading
  4. Getting help


1. Kinesis Elasticsearch Sink

This release adds support to the Kinesis pipeline for loading of an Elasticsearch cluster over HTTP. This allows Snowplow to now load Amazon Elasticsearch Service, which only supports interaction over this API. (The Snowplow batch pipeline already supports loading of Elasticsearch Service for bad rows.)

Under the covers we are using the excellent Jest library as our HTTP client until such time as Elasticsearch has an offical Java client for HTTP; this should be included in Elasticsearch 5.0.0 per this ticket.

This change should also, pending more testing, allow us to support more versions of Elasticsearch, because the HTTP API is much less opinionated than the Transport Client. Preliminary non-production testing has shown the Kinesis Elasticsearch Sink working up to Elasticsearch version 2.3.4. However, the sink has only been used extensively in production by us on versions 1.4.x and 1.5.x, so please let us know about any issues with versions out of this range.

You can also now control the logging level of the Elasticsearch Sink from the command line via a system property call of the form:

java -jar -Dorg.slf4j.simpleLogger.defaultLogLevel=warn snowplow-elasticsearch-sink-0.7.0 --config {{ config file path }}

Simply change warn to any of:

  • error
  • warn
  • info
  • debug
  • trace

2. Distribution changes

As a step towards supporting Docker formally for our real-time applications we are now distributing the Kinesis applications as 3 distinct Bintray packages:

We continue to make a “meta-distribution” of all three apps available in the Snowplow package in Bintray.

3. Upgrading

The Kinesis apps for R82 Tawny Eagle are available in the following zipfiles:

http://dl.bintray.com/snowplow/snowplow-generic/snowplow_stream_collector_0.7.0.zip http://dl.bintray.com/snowplow/snowplow-generic/snowplow_stream_enrich_0.8.1.zip http://dl.bintray.com/snowplow/snowplow-generic/snowplow_elasticsearch_sink_0.7.0.zip 

Or you can download all of the apps together in this zipfile:


Only the Elasticsearch Sink app has actually changed. The change does include breaking config changes, so you will need to make some minor changes to your configuration file. To upgrade the Elasticsearch Sink:

  • Install the new Elasticsearch Sink app on each server in your Elasticsearch Sink auto-scaling group
  • Update your Elasticsearch Sink config with the new elasticsearch section:
    • The only new fields are elasticsearch.client.type and elasticsearch.client.port
    • The following fields have been renamed:
      • elasticsearch.cluster-name is now elasticsearch.cluster.name
      • elasticsearch.endpoint is now elasticsearch.client.endpoint
      • elasticsearch.max-timeout is now elasticsearch.client.max-timeout
      • elasticsearch.index is now elasticsearch.cluster.index
      • elasticsearch.type is now elasticsearch.cluster.type

Here is the updated config file template:

sink { ... elasticsearch { # Events are indexed using an Elasticsearch Client # - type: http or transport (will default to transport) # - endpoint: the cluster endpoint # - port: the port the cluster can be accessed on # - for http this is usually 9200 # - for transport this is usually 9300 # - max-timeout: the maximum attempt time before a client restart client { type: "" endpoint: "" port: max-timeout: "" } cluster { name: "" index: "" type: "" } } ... }


  • Update your supervisor process to point to the new Kinesis Elasticsearch Sink app
  • Restart the supervisor process on each server running the sink

4. Getting help

For more details on this release, please check out the release notes on GitHub.

If you have any questions or run into any problems, please raise an issue or get in touch with us through the usual channels.

More about
the author

Joshua Beemster
Joshua Beemster

Josh is a Head of Engineering and enjoys mapping out how to manage infrastructure across multiple clouds using a combination of Terraform, K8s and Helm. He works mainly with the teams responsible for infrastructure and the core data processing teams at Snowplow.

View author

Ready to start creating rich, first-party data?

Image of the Snowplow app UI