Launch ScyllaDB on AWS¶

Launching Instances from ScyllaDB AMI¶

1. Choose your region, and click the Node link to open the EC2 instance creation wizard.

   The following table shows the latest patch release. See AWS Images for earlier releases.

   6.2.3¶

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-0c5503356d149aeb5	Node / Cluster	ami-0c3b648f9cafa4dd8	Node / Cluster
   Africa (Cape Town)	ami-0acae10ac404d6471	Node / Cluster	ami-0212c40473f2653f4	Node / Cluster
   Asia Pacific (Mumbai)	ami-069430b2f03e03d94	Node / Cluster	ami-09a17cdb5eabf8d63	Node / Cluster
   Europe (Stockholm)	ami-03ccd44c39ece081c	Node / Cluster	ami-0d3597980d763b4d5	Node / Cluster
   Europe (Paris)	ami-0aabc250cad5f1f6e	Node / Cluster	ami-0a72eb8082e2a6095	Node / Cluster
   Europe (Milan)	ami-0a00048eb83f5578d	Node / Cluster	ami-02fa925168676f81e	Node / Cluster
   Europe (London)	ami-03cd7f4be5ffb9f40	Node / Cluster	ami-0f2cb925e66f6fbbd	Node / Cluster
   Europe (Ireland)	ami-062faa721a0d5b39c	Node / Cluster	ami-07b194b2efe52244e	Node / Cluster
   Asia Pacific (Osaka)	ami-05553a285a66fe06d	Node / Cluster	ami-05ed899b22424cdd5	Node / Cluster
   Asia Pacific (Seoul)	ami-0a39ce5ed0c688cdb	Node / Cluster	ami-009d140df49132b3b	Node / Cluster
   Middle East (Bahrain)	ami-0db76d6404e1af64d	Node / Cluster	ami-0087ddf5e6589eb34	Node / Cluster
   Asia Pacific (Tokyo)	ami-06984712b1d4d2f71	Node / Cluster	ami-06f56d5b49eacb28a	Node / Cluster
   Israel (Tel Aviv)	ami-0f1463c93f61b5342	Node / Cluster	ami-0d071b35f4e388d20	Node / Cluster
   Canada (Central)	ami-0d36d383f7a125b57	Node / Cluster	ami-09b18a06e09921c02	Node / Cluster
   South America (Sao Paulo)	ami-0fd72632353befc60	Node / Cluster	ami-0b0661c53016a88a5	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0c866099bd6de05d9	Node / Cluster	ami-0c3cb00ea43b4cdca	Node / Cluster
   Asia Pacific (Singapore)	ami-061e0d6735b941dea	Node / Cluster	ami-00aefcdc9582f3ee8	Node / Cluster
   Asia Pacific (Sydney)	ami-0555431be10236db7	Node / Cluster	ami-02b742db47ce0d035	Node / Cluster
   Europe (Frankfurt)	ami-04bc16008f69f4125	Node / Cluster	ami-0332a3fc032f72491	Node / Cluster
   Asia Pacific (Jakarta)	ami-074808b7c0b354c9b	Node / Cluster	ami-049e340c3b963b444	Node / Cluster
   US East (N. Virginia)	ami-05ae086d67dcf314b	Node / Cluster	ami-003c3ecbf6affbec0	Node / Cluster
   US East (Ohio)	ami-049051aa88de27409	Node / Cluster	ami-0f971cf5a8fec93ac	Node / Cluster
   US West (N. California)	ami-049642f797fc8fec2	Node / Cluster	ami-0a01a880c3cfc22aa	Node / Cluster
   US West (Oregon)	ami-0c0adeb601b98ba2a	Node / Cluster	ami-0abbb4db3ad7859fc	Node / Cluster

2. Choose the instance type. See Cloud Instance Recommendations for AWS for the list of recommended instances.

   Other instance types will work, but with lesser performance. If you choose an instance type other than the recommended ones, make sure to run the scylla_setup script.

3. Configure your instance details.

   • Number of instances – If you are launching more than one instance, make sure to correctly set the IP of the first instance with the seeds parameter - either in the User Data (see below) or after launch.

   • Network – Configure the network settings.

     • Select your VPC.

     • Configure the security group. Ensure that all ScyllaDB ports are open.

   • Advanced Details> User Data – Here, you can add ScyllaDB configuration options in the JSON format. See scylla.yaml for information about supported options.

     The following example shows a configuration using the most popular options.

     • cluster_name - The name of the cluster.

     • seed_provider - The IP of the first node. New nodes will use the IP of this seed node to connect to the cluster and learn the cluster topology and state. See ScyllaDB Seed Nodes.

     • post_configuration_script - A base64 encoded bash script that will be executed after the configuration is completed.

     • start_scylla_on_first_boot - Starts ScyllaDB once the configuration is completed.

     Example:

     {
          "scylla_yaml": {
              "cluster_name": "test-cluster",
              "seed_provider": [{"class_name": "org.apache.cassandra.locator.SimpleSeedProvider",
                                 "parameters": [{"seeds": "10.0.219.209"}]}],
          },
          "post_configuration_script": "#! /bin/bash\nyum install cloud-init-cfn",
          "start_scylla_on_first_boot": true
     }
     

     For full documentation of ScyllaDB AMI user data, see the ScyllaDB Image documentation.

4. Add storage.

   • ScyllaDB AMI requires XFS to work. You must attach at least one drive for ScyllaDB to use as XFS for the data directory. When attaching more than one drive, the AMI setup will install RAID0 on all of them.

   • The ScyllaDB AMI requires at least two instance store volumes. The ScyllaDB data directory will be formatted with XFS when the instance first boots. ScyllaDB will fail to start if only one volume is configured.

5. Tag your instance.

6. Click Launch Cluster. You now have a running ScyllaDB cluster on EC2.

7. Connect to the servers using the username scyllaadm.

   ssh -i your-key-pair.pem scyllaadm@ec2-public-ip
   

   The default file paths:

   • The scylla.yaml file: /etc/scylla/scylla.yaml

   • Data: /var/lib/scylla/

   To check that the ScyllaDB server is running, run:

   nodetool status
   

Next Steps¶

• Configure ScyllaDB

• Manage your clusters with ScyllaDB Manager

• Monitor your cluster and data with ScyllaDB Monitoring

• Get familiar with ScyllaDB’s command line reference guide.

• Learn about ScyllaDB at ScyllaDB University