Crucial note (please read): If you are recreating a cluster
that was created prior to June 2015, you must select appropriate
Image under the Advanced startup options
below. See Deprecated AMIs on this page
for a list of old machine images. Otherwise your cluster will
get corrupted.

Name of your cluster used for identification and relaunching. If creating a new cluster, type any name you like.

Password

Your choice of password, for the CloudMan web interface and accessing the server via ssh.

Instance type

Type (ie, virtual hardware configuration) of the server to start.

Placement

A specific placement zone where your server will run. This requires you have filled out the previous 6 fields!

Key pair

A specific key pair to be used when launching your server. This requires you have filled out the initial 6 fields!

Default bucket

The default bucket to use. See CloudMan's wiki for a detailed description of this option.

Post-start script

A URL to the post-start script. See CloudMan's wiki for a detailed description of this option.

Worker post-start script

A URL to the post-start script for worker nodes. See CloudMan's wiki for the description.

Shared cluster string

A share string to use for deriving this cluster instance.

Extra User-Data

Pass advanced properties to CloudMan via the the cloudinfrastructure's user-data mechanism. Properties should be in YAMLformatted key-value pairs.

This website is an open service developed by the
Galaxy and
CloudBioLinux
communities. The goal is to make it easy to get started doing
scalable biological analysis on cloud resources. See
this video on how to
get started or
this guide
for a detailed usage example when using the Amazon cloud. The
open source code
is available on Github allowing you to also run this service locally.

This site can be used for any of the available clouds.
Note that you must have appropriate credentials for the
chosen cloud. Provided credentials are not stored anywhere on this site
and are used only to make the initial request to launch the desired instance.
If a given cloud is not available in the list and you would like to see it
there, please contact us.

Launching servers on the Amazon cloud will incur
usage fees
from Amazon for their resources. By using this service you acknowledge your
sole responsibility for any costs accrued.