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.15¶

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-0972a72d4861171ba	Node / Cluster	ami-006d6726907394c0d	Node / Cluster
   Africa (Cape Town)	ami-078aa472b761b32e3	Node / Cluster	ami-0867ba9f30eb41d5f	Node / Cluster
   Asia Pacific (Mumbai)	ami-0927c3d0e128c8837	Node / Cluster	ami-07cd1f054006ff02a	Node / Cluster
   Europe (Stockholm)	ami-0dcc129548b5b0b7b	Node / Cluster	ami-086ab404ff679980b	Node / Cluster
   Europe (Paris)	ami-0b76eca6ed490ab22	Node / Cluster	ami-0ca8a2583a169c0fd	Node / Cluster
   Europe (Milan)	ami-0814b948058ccd6dd	Node / Cluster	ami-0a2ff7583a7199b1e	Node / Cluster
   Europe (London)	ami-09b2130205675c9ba	Node / Cluster	ami-0e5434505ee6d7f26	Node / Cluster
   Europe (Ireland)	ami-003976ed87d3b7b72	Node / Cluster	ami-09dda4f11cff29045	Node / Cluster
   Asia Pacific (Osaka)	ami-05d876432c55d75a3	Node / Cluster	ami-017fafe56c78a6e61	Node / Cluster
   Asia Pacific (Seoul)	ami-02ba3d399eade2388	Node / Cluster	ami-09a0efcaa5452a226	Node / Cluster
   Middle East (Bahrain)	ami-03142acc87abba74a	Node / Cluster	ami-0cd663274cd401926	Node / Cluster
   Asia Pacific (Tokyo)	ami-0673f399982b3ca16	Node / Cluster	ami-0cb99c87de8386674	Node / Cluster
   Israel (Tel Aviv)	ami-0defd01ed212b7352	Node / Cluster	ami-0f387a2fa618f3661	Node / Cluster
   Canada (Central)	ami-0eed8edbf9054701e	Node / Cluster	ami-0d0b2ba8588d3ab59	Node / Cluster
   South America (Sao Paulo)	ami-02d42f5ebb53eeb8c	Node / Cluster	ami-058b63cf4d98743a0	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0a99d4f5d32929baf	Node / Cluster	ami-07a55de15d0d8442d	Node / Cluster
   Asia Pacific (Singapore)	ami-0eac9892381daaeaa	Node / Cluster	ami-09f25f9b4282ff07d	Node / Cluster
   Asia Pacific (Sydney)	ami-061e2daf2e8f29dd2	Node / Cluster	ami-0d76f8db3070f76a2	Node / Cluster
   Europe (Frankfurt)	ami-09c1d183bdfb7a048	Node / Cluster	ami-0b023d2c5d411cbc0	Node / Cluster
   Asia Pacific (Jakarta)	ami-0f63e18e6cb696ffc	Node / Cluster	ami-0a02c6e51e3de2428	Node / Cluster
   US East (N. Virginia)	ami-07a9d239602ac62c7	Node / Cluster	ami-058210741ddf9d701	Node / Cluster
   US East (Ohio)	ami-0ad31fee933a9685d	Node / Cluster	ami-075a8c1d6b6853962	Node / Cluster
   US West (N. California)	ami-0de5713dff3d72b56	Node / Cluster	ami-0f2ece0ea5a13cf22	Node / Cluster
   US West (Oregon)	ami-0cb80534c6719b793	Node / Cluster	ami-06bebc4158ef62c6a	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