Skip to main content

Setup Guide for AWS

You are reading documentation for an outdated version. Here’s the latest one!


Snowplow Mini is, in essence, the Snowplow real time stack inside of a single image. It is an easily-deployable, single instance version of Snowplow that serves three use cases:

  1. Giving a Snowplow consumer (e.g. an analyst / data team / marketing team) a way to quickly understand what Snowplow "does" i.e. what you put it at one end and take out of the other
  2. Giving developers new to Snowplow an easy way to start with Snowplow and understand how the different pieces fit together
  3. Giving people running Snowplow a quick way to debug tracker updates

All setup for Snowplow Mini is done within the AWS Console and will incur small amounts of running costs, depending on the size of the EC2 instance you select.

As of 0.6.0, we offer 3 different images for 3 new sizes of Snowplow Mini.

To decide on which size of Snowplow Mini to choose, read on.

large & xlarge & xxlarge‚Äč

Until 0.6.0, Snowplow Mini was being used inside AWS t2.medium, n1-standard-1 in GCP, instances and it served well for demonstration purposes. However, we observed that Snowplow Mini started exceeding its initial motivation and machine resources started to become an obstacle, causing issues with Elasticsearch etc. This is why, Mini is available at 3 different sizes.

  • large¬†: Same image published so far. Elasticsearch has¬†4g¬†heap size and Snowplow apps has¬†0.5g¬†heap size. Recommended machine RAM is¬†8g.
  • xlarge¬†: Double the large image. Elasticsearch has¬†8g¬†heap size and Snowplow apps has¬†1.5g¬†heap size. Recommended machine RAM is¬†16g.
  • xxlarge¬†: Double the xlarge image. Elasticsearch has¬†16g¬†heap size and Snowplow apps has¬†3g¬†heap size. Recommended machine RAM is¬†32g.

This service is available as an EC2 image within the AWS Community AMIs in the following regions:

large / t2.largexlarge / t2.xlargexxlarge / t2.xxlarge

The software stack installed:

  • Snowplow Stream Collector NSQ 2.1.0
  • Snowplow Stream Enrich NSQ 1.4.1
  • Snowplow Elasticsearch Loader 1.0.0
  • Snowplow Iglu Server 0.6.1
  • Elasticsearch-OSS 6.8.9
  • Kibana-OSS 6.8.9
  • Postgresql 9.5
  • NSQ v1.2.0

Note: All services are configured to start automatically so everything should happily survive restarts/shutdowns.

To understand the flow of data please refer to the following diagram:

This image has an empty alt attribute; its file name is snowplow-mini-topology.jpg

Security Group‚Äč

In the EC2 Console UI select Security Groups from the panel on the left.

Select the Create Security Group button and fill in the name, description and what VPC you want to attach it to.

You will then need to add the following InBound rules:


  • Custom TCP Rule | Port Range (80)
  • CIDR range¬†
  • Custom TCP Rule | Port Range (443)
  • CIDR range¬†
  • SSH (optional):
    • Custom TCP Rule | Port Range (22)
    • CIDR range¬†{{ YOUR IP HERE }}/32

For OutBound you can leave the default to allow everything out.

Choose AMI‚Äč

In the EC2 Console UI select the Launch Instance button then select the Community AMIs button. In the search bar enter snowplow-mini-0.12.0 to find the needed AMI and then select it.

Choose Instance Type‚Äč

0.12.0 AMI names explicitly specifies which instance type to use.

  • 0.12.0-large¬†needs¬†t2.large
  • 0.12.0-xlarge¬†needs¬†t2.xlarge
  • 0.12.0-xxlarge¬†needs¬†t2.2xlarge

Configure Instance‚Äč

If you created your Security Group in a different VPC than the default you will need to select the same VPC in the Network field.

NOTE: If you select a custom VPC ensure that you select Enable for the Auto-assign Public IP option.

Add Storage‚Äč

Depending on how long you intend to run Snowplow Mini and how much data you intend to send/store you will need to change the size of the block store accordingly.

For basic testing and debugging;

  • 20-50 Gb should suffice for¬†large
  • 50-100 Gb should suffice for¬†xlarge
  • 100-200 Gb should suffice for¬†xxlarge

We also recommend changing the Volume Type to GP2 from Magnetic for a smoother experience.

Tag Instance‚Äč

Add any tags you like here.

Configure Security Group‚Äč

Select the Security Group you created in Step 2.


Press the Launch button and select an existing key-pair, or create a new one, if you want to be able to SSH into the box.