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.

   2025.1.1¶

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-055bc389997f495ac	Node / Cluster	ami-07f4cfe96a8c38af6	Node / Cluster
   Africa (Cape Town)	ami-063ba2de382d89822	Node / Cluster	ami-0af6bbbec2197a160	Node / Cluster
   Asia Pacific (Mumbai)	ami-0abf058de545921ec	Node / Cluster	ami-07d35d5284e599b48	Node / Cluster
   Europe (Stockholm)	ami-0b81e3311a32127cf	Node / Cluster	ami-0344f758a5e3c8cf8	Node / Cluster
   Europe (Paris)	ami-03f51b7b92df71431	Node / Cluster	ami-0d04ad726c918348a	Node / Cluster
   Europe (Milan)	ami-0be8a57d78414b9fe	Node / Cluster	ami-0ec63b16f7587ef2e	Node / Cluster
   Europe (London)	ami-03d521fcc5a29188e	Node / Cluster	ami-077e38d9a8eabf309	Node / Cluster
   Europe (Ireland)	ami-0b89cf9b6fd4404e4	Node / Cluster	ami-08a84766cf796f533	Node / Cluster
   Asia Pacific (Osaka)	ami-04f97481d9b89276e	Node / Cluster	ami-05e6d852b4e861598	Node / Cluster
   Asia Pacific (Seoul)	ami-0d3a5b7e9f0427397	Node / Cluster	ami-00c46c0bfb20039c9	Node / Cluster
   Middle East (Bahrain)	ami-0222be94b0f81d3bc	Node / Cluster	ami-082eda16936a0e026	Node / Cluster
   Asia Pacific (Tokyo)	ami-0b9212d1e9b6e04d8	Node / Cluster	ami-018b353f106a52d5f	Node / Cluster
   Israel (Tel Aviv)	ami-092c73a57f99ff44c	Node / Cluster	ami-00ba31382c37ce2b9	Node / Cluster
   Canada (Central)	ami-0e7f2f4646872e44e	Node / Cluster	ami-0e254767c60a6a9bc	Node / Cluster
   South America (Sao Paulo)	ami-0364969e3a8f70dda	Node / Cluster	ami-06f77de6bd507a38f	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0c81f1afb5b8ea3fc	Node / Cluster	ami-05c6d9ac52cfd007b	Node / Cluster
   Asia Pacific (Singapore)	ami-0cf42c68768448efc	Node / Cluster	ami-0feec6afb2f364a55	Node / Cluster
   Asia Pacific (Sydney)	ami-03e776c82777c793b	Node / Cluster	ami-0ae2b45c6db9bf0e6	Node / Cluster
   Europe (Frankfurt)	ami-0d45d26da02c69b67	Node / Cluster	ami-00cdc0ba093c735e1	Node / Cluster
   Asia Pacific (Jakarta)	ami-0f5c613085a5dc92f	Node / Cluster	ami-01dba2200e54c52c0	Node / Cluster
   US East (N. Virginia)	ami-0c927671626b3c961	Node / Cluster	ami-0a2cb5d7044c2a425	Node / Cluster
   US East (Ohio)	ami-0b05f197052863028	Node / Cluster	ami-0d2d5eb2598790718	Node / Cluster
   US West (N. California)	ami-0eac113117d3ed0ad	Node / Cluster	ami-0af791d32b31b1d59	Node / Cluster
   US West (Oregon)	ami-05f44263e478b9f25	Node / Cluster	ami-057b0c03ba73f128e	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