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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-098ebd4ddd84e6e1f	Node / Cluster	ami-0076e1734ff4d1a74	Node / Cluster
   Africa (Cape Town)	ami-00fbed52d0ebf5a6f	Node / Cluster	ami-0bbffb9dc13e5e6ff	Node / Cluster
   Asia Pacific (Mumbai)	ami-051b3a41f20d4c2e6	Node / Cluster	ami-03e6bf05f3670c2c2	Node / Cluster
   Europe (Stockholm)	ami-0c787830711b408a3	Node / Cluster	ami-04f8bfab2b3f40a61	Node / Cluster
   Europe (Paris)	ami-05c85e3f4a6042921	Node / Cluster	ami-02c396aa2192a1778	Node / Cluster
   Europe (Milan)	ami-05fa5b4287ccd5ac0	Node / Cluster	ami-0988589fda60551bf	Node / Cluster
   Europe (London)	ami-0a3ad55ce5c8cd0d3	Node / Cluster	ami-03daa14256cfa7b30	Node / Cluster
   Europe (Ireland)	ami-003de55323cdf5bb6	Node / Cluster	ami-0c5349d07c9ca3330	Node / Cluster
   Asia Pacific (Osaka)	ami-0d9641d1200d46cef	Node / Cluster	ami-000650e49532d2375	Node / Cluster
   Asia Pacific (Seoul)	ami-08e1dfa8cd56fb406	Node / Cluster	ami-079db685e4a8cdf5a	Node / Cluster
   Asia Pacific (Tokyo)	ami-0a93361d0841d88ef	Node / Cluster	ami-02e960f018b75f866	Node / Cluster
   Israel (Tel Aviv)	ami-09226853bac1a90b1	Node / Cluster	ami-01af2c578b9fbd516	Node / Cluster
   Canada (Central)	ami-0a8a4a6ae3e3a6f9f	Node / Cluster	ami-0be04022114725803	Node / Cluster
   South America (Sao Paulo)	ami-0e7df13a8d0efef38	Node / Cluster	ami-024b2aabd1d1fe0e1	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0e503910e69b1598f	Node / Cluster	ami-0e41b0b5cfab30ab5	Node / Cluster
   Asia Pacific (Singapore)	ami-08dd622814d46f9fe	Node / Cluster	ami-012c494b1ac9b4033	Node / Cluster
   Asia Pacific (Sydney)	ami-0f68af4ccc81d66a6	Node / Cluster	ami-026c5b937153a6eed	Node / Cluster
   Europe (Frankfurt)	ami-0ae9a415e626b8683	Node / Cluster	ami-0fffc96972373e4fc	Node / Cluster
   US East (N. Virginia)	ami-06fa41b659420cfb8	Node / Cluster	ami-0589901420bdad822	Node / Cluster
   US East (Ohio)	ami-0c59d7f7b8e513d29	Node / Cluster	ami-01c66339a09940fa5	Node / Cluster
   US West (N. California)	ami-01d951c15144622ff	Node / Cluster	ami-0dc2afde3337a5fae	Node / Cluster
   US West (Oregon)	ami-0f6b1e54c63847c08	Node / Cluster	ami-03c1b35379b6f147a	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