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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-0a1e80691dc43fd79	Node / Cluster	ami-07a77025382514fb7	Node / Cluster
   Africa (Cape Town)	ami-0aaf37bf5362658c9	Node / Cluster	ami-0fde8651cbaf16422	Node / Cluster
   Asia Pacific (Mumbai)	ami-08ad93c84924c8c97	Node / Cluster	ami-01fa6c2c89b3451bb	Node / Cluster
   Europe (Stockholm)	ami-0342074615cbd445b	Node / Cluster	ami-0a3c4620630c92268	Node / Cluster
   Europe (Paris)	ami-06015ee0aff35235d	Node / Cluster	ami-0a3ec9148522ba819	Node / Cluster
   Europe (Milan)	ami-0dcc42db11b42ba98	Node / Cluster	ami-0e3aab1ef7d939a5e	Node / Cluster
   Europe (London)	ami-022a607e4ee3d2a5b	Node / Cluster	ami-0cbf21a0b655afa21	Node / Cluster
   Europe (Ireland)	ami-0ed1e518d493ab998	Node / Cluster	ami-0feed670a7926f566	Node / Cluster
   Asia Pacific (Osaka)	ami-09b84b8594bf0fa82	Node / Cluster	ami-0b60c428dde3c56f9	Node / Cluster
   Asia Pacific (Seoul)	ami-04711106e369f85ae	Node / Cluster	ami-0284d3085402fb32d	Node / Cluster
   Middle East (Bahrain)	ami-09ba514d02272aa19	Node / Cluster	ami-0b2e75810c4c6a71b	Node / Cluster
   Asia Pacific (Tokyo)	ami-0d12b1dafdca3553c	Node / Cluster	ami-0feccb34736198d06	Node / Cluster
   Israel (Tel Aviv)	ami-03686f022525c642f	Node / Cluster	ami-0dfb0d27135408193	Node / Cluster
   Canada (Central)	ami-09a75fb01bbf7056a	Node / Cluster	ami-0bd7885a5bf27e2bc	Node / Cluster
   South America (Sao Paulo)	ami-0090b7113a294df2f	Node / Cluster	ami-0de6be06052517817	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0053624e4c71874c0	Node / Cluster	ami-0721b37387f2a3a05	Node / Cluster
   Asia Pacific (Singapore)	ami-015cd07027a5869d1	Node / Cluster	ami-02f9f74b21ecc1a2b	Node / Cluster
   Asia Pacific (Sydney)	ami-08624b6cecf9dabda	Node / Cluster	ami-046fbdc8bf9b4de4e	Node / Cluster
   Europe (Frankfurt)	ami-0c1a0c6e58f88b648	Node / Cluster	ami-0cbb9acb49979379c	Node / Cluster
   Asia Pacific (Jakarta)	ami-0b253d6828571bea0	Node / Cluster	ami-06a2c2e5acdbadc4f	Node / Cluster
   US East (N. Virginia)	ami-0dc701eaaab6f478f	Node / Cluster	ami-00fd3ffc7e94c432b	Node / Cluster
   US East (Ohio)	ami-0efcf6510ef137678	Node / Cluster	ami-03dbfe2baea8edf8e	Node / Cluster
   US West (N. California)	ami-09709c2dd1f9a913e	Node / Cluster	ami-0c001d2b3d58c4973	Node / Cluster
   US West (Oregon)	ami-0996d99d36db5c4e3	Node / Cluster	ami-031ca66cc0ce64970	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