Skip to content
Fast tool to deploy Storm
Branch: master
Clone or download
Pull request Compare This branch is 32 commits ahead, 31 commits behind KasperMadsen:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Storm-Deploy-Alternative Fork

Fast tool to deploy Storm on Amazon EC2, written entirely in Java.

Note that this is a heavily-modified fork of storm-deploy-alternative. The main difference is that this fork removes a lot of unnecessary code and dependencies, allows the user to choose the download location of of storm, zookeeper, and storm-deploy-alternative-cluster jar. This fork also splits the code base into two modules, storm-deploy-alternative-local and storm-deploy-alternative-cloud, in order to separate the logic and keep the necessary cloud jar size minimal. Another motivation for the fork is that the storm, zookeeper, and storm-deploy-alternative-cluster binaries are pulled from a private s3 instance via hard-coded URLs, and there is no guarantee that they will always be available. This fork allows you to configure where the binaries are downloaded from.

Full explanation of useage can be found at the following link:


  • Runs Storm and Zookeeper daemons under supervision (automatically restarted in case of failure)
  • Only fetch and compile what is needed (can deploy on prepared images in a few minutes)
  • Supports executing user-defined commands both pre-config and post-config
  • Automatically sets up Ganglia, making it easy to monitor performance
  • Automatically sets up Amazon EC2 AMI Tools on new nodes


This tool, requires two configuration files: storm-deploy-alternative-local/conf/credential.yaml and storm-deploy-alternative-local/conf/configuration.yaml. Put your credentials into the file conf/credential.yaml. It's required that you have generated an SSH key-pair on your local machine in ~/.ssh with an empty pass phrase.

Below is an example of a single cluster configuration, for conf/configuration.yaml

# Amazon EC2 example cluster configuration
    - image "us-west-2/ami-c94856a8"        # Ubuntu 14.04 LTS AMI
    - region "us-west-2"                    # Region
    - remote-exec-preconfig {}
    - remote-exec-postconfig {}
    - ssh-key-name "ec2"     # Optional. defaults to "id_rsa"
    - storm-deploy-alternative-cloud-jar-url ""
    - storm-tar-gz-url ""
    - zk-tar-gz-url ""
    - memory-monitor "false"
    - t2.micro {ZK, WORKER, MASTER, UI, LOGVIEWER}      # Request service
    - t2.micro {WORKER}      # Request service
    - t2.micro {WORKER}      # Request service
  • MASTER is the Storm Nimbus daemon
  • WORKER is the Storm Supervisor daemon
  • UI is the Storm and Ganglia User-Interface
  • LOGVIEWER is the Storm Logviewer daemon
  • DRPC is the Storm DRPC daemon
  • ZK is the Zookeeper daemon

Ensure the image resides in the same region as specified. Choose a mirror download URL for storm and zookeeper or put the files in your own S3 bucket and use those URLs.

Below is an example of a single cluster configuration, for conf/credential.yaml

## Amazon AWS Credentials
ec2-identity: "GDYTFC59KU6JKHJG"
ec2-credential: "YIO7jgjhg987qKgRfFJuke958mmGwrPsgsd"


After cloning the repo via git, build the project with Maven with the command: mvn clean package. Two jars will be produced: storm-deploy-alternative-local/target/storm-deploy-alternative-local.jar and storm-deploy-alternative-cloud/target/storm-deploy-alternative-cloud.jar. You need to upload storm-deploy-alternative-cloud/target/storm-deploy-alternative-cloud.jar to some location on the web accessible by your cluster instances via wget. Your own S3 bucket would be a logical location. Update the configuration.yaml entry, storm-deploy-alternative-cloud-jar-url, accordingly.


Execute java -jar storm-deploy-alternative-local/target/storm-deploy-alternative-local.jar deploy CLUSTER_NAME

Deploys all nodes belonging in the cluster with name CLUSTER_NAME.


Execute java -jar storm-deploy-alternative-local/target/storm-deploy-alternative-local.jar kill CLUSTER_NAME

Kills all nodes belonging in the cluster with name CLUSTER_NAME.


Only deploying to Ubuntu AMIs on Amazon EC2 is supported.

You can’t perform that action at this time.