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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-09a2e0a230cdf8867	Node / Cluster	ami-094257f56bc5a1735	Node / Cluster
   Africa (Cape Town)	ami-0e2d1fb483efb1211	Node / Cluster	ami-09d597c0976174468	Node / Cluster
   Asia Pacific (Mumbai)	ami-0f5d3531f5f1d5401	Node / Cluster	ami-0aa851d6951631d9e	Node / Cluster
   Europe (Stockholm)	ami-040270bfaa2ddb1a6	Node / Cluster	ami-0026f967d14eb9955	Node / Cluster
   Europe (Paris)	ami-0f1b801fb78b02c32	Node / Cluster	ami-01ac6336f74521500	Node / Cluster
   Europe (Milan)	ami-0774d6fa78ffc7473	Node / Cluster	ami-0015be124515486f0	Node / Cluster
   Europe (London)	ami-00541e5c90cd77e36	Node / Cluster	ami-014cb349327ae1e94	Node / Cluster
   Europe (Ireland)	ami-099f196fca6d4f2ea	Node / Cluster	ami-003d540db518dbe1d	Node / Cluster
   Asia Pacific (Osaka)	ami-08bd441afd16a70e4	Node / Cluster	ami-0f69c8f9a5ea3421f	Node / Cluster
   Asia Pacific (Seoul)	ami-0a452b65bef326baa	Node / Cluster	ami-050c1dc75c1cbae0a	Node / Cluster
   Middle East (Bahrain)	ami-088d55b8dc5b97f14	Node / Cluster	ami-0c4991c87b8464b96	Node / Cluster
   Asia Pacific (Tokyo)	ami-0399c9cbea19dc72f	Node / Cluster	ami-0161021a495a0baaf	Node / Cluster
   Israel (Tel Aviv)	ami-0638626a02f06c610	Node / Cluster	ami-0da2cd4902f16d0fc	Node / Cluster
   Canada (Central)	ami-03173fde45c63ffa0	Node / Cluster	ami-09df1d1326ac8eef2	Node / Cluster
   South America (Sao Paulo)	ami-01db9d1e150c9e415	Node / Cluster	ami-07c6fdad861d258d9	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0b4d7bef19f88a7b2	Node / Cluster	ami-0c1d7815c7fc0c324	Node / Cluster
   Asia Pacific (Singapore)	ami-0653d180cb6470cf8	Node / Cluster	ami-042e45a0b64358bd5	Node / Cluster
   Asia Pacific (Sydney)	ami-052c000bfaf8bd871	Node / Cluster	ami-0585f6c9c381966a0	Node / Cluster
   Europe (Frankfurt)	ami-085c0670aa6e506c3	Node / Cluster	ami-0c8ab958d004c0ed9	Node / Cluster
   Asia Pacific (Jakarta)	ami-03242f636d74b8b55	Node / Cluster	ami-0b7053c5bee6cf634	Node / Cluster
   US East (N. Virginia)	ami-06d3f70054194b951	Node / Cluster	ami-0ffc95542106e3611	Node / Cluster
   US East (Ohio)	ami-0b44a6d919b59b8b2	Node / Cluster	ami-07e83835ba39ce159	Node / Cluster
   US West (N. California)	ami-0189e19b79c855c43	Node / Cluster	ami-092e3576bdb55a4ea	Node / Cluster
   US West (Oregon)	ami-03e44e5d7b59e5bcc	Node / Cluster	ami-0b4126ad2807abb4e	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