Access Keys:
Skip to content (Access Key - 0)
Searching Platform v4.6
In This Section
Getting Started

Why put Appistry services on EC2?
EC2 allows you to quickly and inexpensively build servers and Appistry software allows instances to work together to complete task requests by sharing application logic and memory.

AWS Account Required
This tutorial requires a customer to have an existing Amazon EC2 account and be reasonably familiar with its products and services. Where applicable, the tutorial will point to the Amazon Web Services (AWS) documentation to provide more information; Appistry recommends opening them in a new window or tab as you follow through the instructions.
Amazon EC2 Resources

Amazon Machine Image
Appistry did the hard work! We made available a public AMI with a clean copy of CENTOS and Appistry's platform.

Don't know what EC2 is?
Please begin here: http://aws.amazon.com/ec2/

Get an Account and Sign In

  1. Sign up for Amazon Web Services and EC2 as described in Setting up an Account or by clicking "Sign up for Amazon EC2" from the AWS Console page.
  2. Sign in to the Amazon EC2 Console. It may be helpful to watch the short demo video.

    Insantiating a Fabric with SSH and ElasticFox
    Don't want to use the AWS Console? Check out our tutorials for SSH and ElasticFox.

Launch One Instance (required)

In this section, we will launch only one instance of the AMI. Additional instances will be launched in the next section.

  1. Getting Started: Click "Launch Instances".


  2. CHOOSE AN AMI: Click on the "Community AMIs" tab.



  3. Type "appistry" in the "Viewing" search field. Do not hit enter. Click "Select" next to the "appistry/cloudiq-x.x.x.x-rhel5-ami-xx.manifest.xml" AMI.



  4. CREATE KEY PAIR: Create and save a key pair using the name of your choice ("appistry-key-pair" is used here).

    If you have set up an EC2 instance before, this dialog may not appear. Don't worry, you can still make a new key pair before starting your instance.



  5. CONFIGURE FIREWALL: Open SSH (port 22) and HTTP (port 80); Click "Continue".

    If you have set up an EC2 instance before, this dialog may not appear. Don't worry, you can still make Fabric-specific security groups before starting your instance.



  6. LAUNCH: Enter "1" for the "Number of Instances", choose the size of your instance, select your key pair and click "Launch".

    If you didn't get a chance to create a key pair or adjust your security groups, you have a chance to do that here: click the "Create" buttons to the right of "Key Pair Name" and "Security Groups", respectively. Remember: You need a key pair to log into your system and port 22 (SSH) and port 80 (HTTP) should be open.

Your instances are now launching. Click "Close".

Launch a Fabric

In this section, Appistry recommends launching at least two (2) more Workers (for a total of at least three (3)) for trying-out the Fabric.

Seeding the Fabric
There's nothing special about the first instance you launch, it is only required to "seed" the Fabric. Try killing the instance later – the Fabric will continue to run. Additional instances may be spawned using any other instance's Public DNS. Please note that this method of instantiating Workers is only required for the Fabric under the Amazon EC2 environment.

  1. NAVIGATION: Continuing from the "Launch One Instance" section, click "Instances".


  2. My Instances: Wait for your instance "Status" to show as "running" and verify that your key pair is listed next to the instance. Click on the instance and copy the "Private DNS" from the lower pane.



  3. My Instances: Right-click on the instance and click "Launch more like this".



  4. LAUNCH: Update the "Number of Instances"; click "Show Advanced Options"; paste the "Private DNS" into the "User Data" field (make sure there aren't any extraneous carriage returns); and click "Launch". The data from "User Data" will be put into the Appistry Network Bridge "hints" file. If you have a private data center to connect with at this time, it can be put into this field also (on a new line).

Your instances are now launching. Click "Close".



  1. It may take a while as your workers start. Some may start quicker than others. Depending on the number of workers you start, it could take as little as a few minutes to a half hour or more for your workers to reach a solid running state. You can watch the process by opening the Management Console at 'http://<your first worker's public IP>:16080/console/'. When you open the console, click 'Connect' in the upper right hand corner and type 'fabric-admin' as the password. The other fields should be pre-filled. You may notice workers come and go. This is normal behavior. When all the workers are up and running in a stable state, it will settle down.
  2. Follow AWS directions for Connecting to your Instance and specifically Appendix: PuTTY if you plan on connecting via Windows.
    Download PuTTY
  3. Once connected to a worker via SSH, login as "root" and run the following command:
    PROMPT> fabric_ctl -d239.255.0.1:30000 -ufabric-admin/fabric-admin query all
Adaptavist Theme Builder Powered by Atlassian Confluence