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.

   2024.1.18¶

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-00ff36e800da3135f	Node / Cluster	ami-0687ec3813323ac0f	Node / Cluster
   Africa (Cape Town)	ami-0f66202ded3141309	Node / Cluster	ami-0dc39d09858429754	Node / Cluster
   Asia Pacific (Mumbai)	ami-0ff3b446c4b026118	Node / Cluster	ami-0dad3ddd8f7a03f99	Node / Cluster
   Europe (Stockholm)	ami-019fd90c059b0f8ca	Node / Cluster	ami-00fbed44ec455c927	Node / Cluster
   Europe (Paris)	ami-0dcdf3dfe3e642544	Node / Cluster	ami-023b39b3c3b9f7119	Node / Cluster
   Europe (Milan)	ami-08e05229b2f24f022	Node / Cluster	ami-054806f6f16d708d6	Node / Cluster
   Europe (London)	ami-077efae110ad916e1	Node / Cluster	ami-0b2bee71334c2bba5	Node / Cluster
   Europe (Ireland)	ami-0cdb5de1230877056	Node / Cluster	ami-0c3a17d69ef9a3338	Node / Cluster
   Asia Pacific (Osaka)	ami-01c93caa2ed3cdbc9	Node / Cluster	ami-07179b1400392f09e	Node / Cluster
   Asia Pacific (Seoul)	ami-01de95d5588c77260	Node / Cluster	ami-0b137562fe665dd5e	Node / Cluster
   Middle East (Bahrain)	ami-042c9d3727b99ee12	Node / Cluster	ami-07a607d865c37b4b4	Node / Cluster
   Asia Pacific (Tokyo)	ami-0b25cf44962a3760b	Node / Cluster	ami-08ce6ae7f5334a6b7	Node / Cluster
   Israel (Tel Aviv)	ami-05e2512f7f9260117	Node / Cluster	ami-07d6696f08c4e7504	Node / Cluster
   Canada (Central)	ami-02531621131817b22	Node / Cluster	ami-0c848980f3aec211d	Node / Cluster
   South America (Sao Paulo)	ami-09279c06804f8c697	Node / Cluster	ami-0ba17658bbe98f5c5	Node / Cluster
   Asia Pacific (Hong Kong)	ami-074f5c0af81b90850	Node / Cluster	ami-0fc29dc2172dd73e5	Node / Cluster
   Asia Pacific (Singapore)	ami-08006d4d099534776	Node / Cluster	ami-04beddec71085d8cd	Node / Cluster
   Asia Pacific (Sydney)	ami-06645d8741a8bfbdd	Node / Cluster	ami-03fbe1a00e2a92d5a	Node / Cluster
   Europe (Frankfurt)	ami-07d15a1488e433958	Node / Cluster	ami-0d4a74a8e3bc3403c	Node / Cluster
   Asia Pacific (Jakarta)	ami-0aad8a21494e049c4	Node / Cluster	ami-08b2b15c9c2a3dcd9	Node / Cluster
   US East (N. Virginia)	ami-0c767256fb5b02178	Node / Cluster	ami-0449e169468f51562	Node / Cluster
   US East (Ohio)	ami-0c7b2c46f237f7767	Node / Cluster	ami-0d37a435f4f3bf7ae	Node / Cluster
   US West (N. California)	ami-026a73d5edcd0c07a	Node / Cluster	ami-0c31f88a05f4ff7b2	Node / Cluster
   US West (Oregon)	ami-05825666d1763075b	Node / Cluster	ami-0c1d27fefa75948a9	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. Configure Security Group. Make sure all ScyllaDB ports are open.

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

8. 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