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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-06a769d52203db6ed	Node / Cluster	ami-0b25e9a57bbd64316	Node / Cluster
   Africa (Cape Town)	ami-023aee541ac25caa7	Node / Cluster	ami-0fa8cde20eaa665b4	Node / Cluster
   Asia Pacific (Mumbai)	ami-000cd84ca43517d5b	Node / Cluster	ami-0af9e8edc7a720bbd	Node / Cluster
   Europe (Stockholm)	ami-0e8a61edcb9eddb68	Node / Cluster	ami-0a9d037ef90da589f	Node / Cluster
   Europe (Paris)	ami-00675134182042c17	Node / Cluster	ami-088aff38c2a113b20	Node / Cluster
   Europe (Milan)	ami-01f3b8a8e6bccab1e	Node / Cluster	ami-0660c71704e3a5cf4	Node / Cluster
   Europe (London)	ami-088ead02c3f33a3e7	Node / Cluster	ami-0eaf6192b7c05bfbb	Node / Cluster
   Europe (Ireland)	ami-002cce5e913ce24a7	Node / Cluster	ami-00b0cfa54c8586b17	Node / Cluster
   Asia Pacific (Osaka)	ami-029d13a240bb96127	Node / Cluster	ami-0c9090478a9c25311	Node / Cluster
   Asia Pacific (Seoul)	ami-014efc4feba6cb522	Node / Cluster	ami-0453c7ae079c9e8e3	Node / Cluster
   Asia Pacific (Tokyo)	ami-0bdf9ea8b22c83da0	Node / Cluster	ami-0d0a82ac58b937338	Node / Cluster
   Israel (Tel Aviv)	ami-0c45232b0f9ab022c	Node / Cluster	ami-0f8f899dbcfe2b3d2	Node / Cluster
   Canada (Central)	ami-0c6cb1c6ba7122461	Node / Cluster	ami-00ddbaa21dcc65b38	Node / Cluster
   South America (Sao Paulo)	ami-0fd8c1b07446ab827	Node / Cluster	ami-0baa179cd62246ebc	Node / Cluster
   Asia Pacific (Hong Kong)	ami-05969f46d82fa5838	Node / Cluster	ami-08ec0c76e51aa9707	Node / Cluster
   Asia Pacific (Singapore)	ami-072182efffe7a38c7	Node / Cluster	ami-098222b94e298d30f	Node / Cluster
   Asia Pacific (Sydney)	ami-027d08a4b1a2459ed	Node / Cluster	ami-04b9af818b0668e0f	Node / Cluster
   Europe (Frankfurt)	ami-01a7f5a4e704ca590	Node / Cluster	ami-057de327e76a5050b	Node / Cluster
   US East (N. Virginia)	ami-03294856178fc15fc	Node / Cluster	ami-01d403fb638c4ceaa	Node / Cluster
   US East (Ohio)	ami-0103eb1a99e9ae010	Node / Cluster	ami-0d5d472e1f1adcbd8	Node / Cluster
   US West (N. California)	ami-0d6054f4a6b0d0414	Node / Cluster	ami-03ed168892bd27cfd	Node / Cluster
   US West (Oregon)	ami-0ba0ee9844ac41d5a	Node / Cluster	ami-0d6cad3654a86c38e	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