Version 11

    Available AMI's

    Latest AMI list is available on download page.

    Additional steps

    You need to run only one management appliance. You can run multiple front-end and back-end appliances.


    Make sure you provide your EC2 credentials as user  data to launch management-appliance. If you don't do this it'll boot,  but it will not be able to discover other appliances (and form a cluster). To inject credentials encode with base64 following string:

    access_key: YOUR_ACCESS_KEY
    secret_access_key: YOUR_SECRET_ACCESS_KEY

    bucket: YOUR_BUCKET_NAME

    You can find your credentials on your AWS account security page. We recommend you choose bucket you not use for other services. If you don't have a bucket simply create one.


    S3_PING has now a known bug when it tries to create a new bucket. There is a workaround for this: create bucket yourself (using S3Fox for example). After this you can use it in your cluster.


    To encode this string you can use for example this page. Passing this data to management-appliance is really simple. If  you're using Amazon  AWS Management Console, just put your encoded string into User Data field as shown below:


    Do not check base64 encoded checkbox! This  will encode it one more time and your management appliance won't be  able to discover other nodes!


    It's recommended to leave some time (30s – 1min) before running next back-end appliance. Do not select more than one back-end appliance in AWS launching wizard.



    Management, backend and frontend instances communicate with each other using the following services:


    - TCP port 7

    - TCP port 4545

    - TCP port 7080 (7080 may try connect to the public IP)

    If all instances (Management, frontend and backend) are running in the same group, ensure that the group has a rule to allow members of its own group to access resources. Using different groups for different instances would require group access between groups. The document for Security groups is available at