Apache Cassandra™ 2.0

Launching the DataStax Community AMI

After creating the security group, you can launch your AMI instances.

Note: On each page, the Help menu or Learn more link provides additional information for understanding the available options.


  1. Launch the AMI using the links in the following table:

    Amazon EC2 offers a number of geographic regions for launching the AMI. Factors for choosing a region include: reduce latency, cost, or regulatory requirements.

    Region AMI
    HVM instances
    us-east-1 ami-ada2b6c4
    us-west-1 ami-3cf7c979
    us-west-2 ami-1cff962c
    eu-west-1 ami-7f33cd08
    ap-southeast-1 ami-b47828e6
    ap-southeast-2 ami-55d54d6f
    ap-northeast-1 ami-714a3770
    sa-east-1 ami-1dda7800
    PV instances
    us-east-1 ami-f9a2b690
    us-west-1 ami-32f7c977
    us-west-2 ami-16ff9626
    eu-west-1 ami-8932ccfe
    ap-southeast-1 ami-8c7828de
    ap-southeast-2 ami-57d54d6d
    ap-northeast-1 ami-6b4a376a
    sa-east-1 ami-15da7808
  2. In Step 2: Choose an Instance Type, choose the appropriate type, and then click Next: Configure Instance Details:

    The left panel allows you to select the instance types based on different criteria. The recommended instances are:

    • Development and light production: m1.large
    • Moderate production: m1.xlarge
    • SSD production with light data: c3.2xlarge
    • Largest heavy production: m3.2xlarge (PV) or i2.2xlarge (HVM)
    • Micro, small, and medium types are not supported.

    When the instance is selected, its specifications are displayed. For example:

    More information for determining hardware and storage requirements is available in the What is the story with AWS storage and Get in the Ring with Cassandra and EC2 blogs.

  3. Configure the instances to suit your requirements:
    1. Select the number of instances.
    2. Select Launch into EC2-Classic.
    3. Open Advanced Details.
    4. Add the following options (as text) to the User Data section.
      Option Description
      --clustername name Required. The name of the cluster.
      --totalnodes #_nodes Required. The total number of nodes in the cluster.
      --version community Required. The version of the cluster. Use community to install the latest version of DataStax Community.
      --opscenter [no] Optional. By default, DataStax OpsCenter is installed on the first instance. Specify no to disable.
      --reflector url Optional. Allows you to use your own reflector. Default: http://reflector2.datastax.com/reflector2.php

      For example: --clustername myDSCcluster --totalnodes 6 --version community

  4. Click Next: Add Storage, and add volumes as needed.

    The number of instance store devices available to the machine depends on the instance type. EBS volumes are not recommended for database storage.

  5. Click Next: Tag Instance and give a name to your DSE instance, such as workload-dsc.

    Tags enable you to categorize your AWS resources in different ways, such as purpose, owner, or environment. Click the Learn more link for more information.

  6. Click Next: Configure Security Group and configure as follows:
    1. Choose Select an existing security group.
    2. Select the Security Group you created earlier.
    3. Click Review and Launch.
  7. In the Step 7: Review Instance Launch page, make any needed changes.
  8. Click Launch and then in the Select an existing key pair or create a new key pair dialog, do one of the following:
    • If you need to create a new key pair, click Choose an existing key pair drop list and select Create a new key pair. Download the key pair (.pem file) to your local machine; you will need it to log in to your Cassandra instances.
    • Select an existing key pair from the Select a key pair drop list and check the acknowledgment statement.
  9. Click Launch Instances.

    The AMI image configures your cluster and starts Cassandra services. The Launch Status page is displayed.

  10. Click View Instances.