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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-0449ddf54c1ecab98	Node / Cluster	ami-0112b4b82972f9161	Node / Cluster
   Africa (Cape Town)	ami-073d275bbffce5014	Node / Cluster	ami-0ed8aafc35aaddb7a	Node / Cluster
   Asia Pacific (Mumbai)	ami-00e728d61ba9cab5e	Node / Cluster	ami-0d8bd75d832a62792	Node / Cluster
   Europe (Stockholm)	ami-0c413d8f40a18980f	Node / Cluster	ami-029a5121d8f9a2a13	Node / Cluster
   Europe (Paris)	ami-07dae6e41b32c1c59	Node / Cluster	ami-0123e49bbb555a8c3	Node / Cluster
   Europe (Milan)	ami-08da117d9003bab9f	Node / Cluster	ami-0ed0f560a14736f17	Node / Cluster
   Europe (London)	ami-03fda5935049a311c	Node / Cluster	ami-01d5b214474cc9fa6	Node / Cluster
   Europe (Ireland)	ami-08782d4e479e8a8ae	Node / Cluster	ami-039ac4887a9ee05ac	Node / Cluster
   Asia Pacific (Osaka)	ami-0db519b548595ad65	Node / Cluster	ami-029553380b8a782e0	Node / Cluster
   Asia Pacific (Seoul)	ami-07cf0c78bf3ba8fbc	Node / Cluster	ami-08dbdee5e21fedf6a	Node / Cluster
   Asia Pacific (Tokyo)	ami-0860cafcbea8dbb47	Node / Cluster	ami-01453adf2c0dda745	Node / Cluster
   Israel (Tel Aviv)	ami-03abebfd228fbaf33	Node / Cluster	ami-09d5887b245188464	Node / Cluster
   Canada (Central)	ami-0c1e7c1a2cd1ec41b	Node / Cluster	ami-07930745ffd175131	Node / Cluster
   South America (Sao Paulo)	ami-0faf24762b7b6270b	Node / Cluster	ami-00ab57f59f298cb69	Node / Cluster
   Asia Pacific (Hong Kong)	ami-08863cdaa54f11d33	Node / Cluster	ami-0eb2d048832df15cb	Node / Cluster
   Asia Pacific (Singapore)	ami-0dbf3683adad2601e	Node / Cluster	ami-0917ce12d25655ffb	Node / Cluster
   Asia Pacific (Sydney)	ami-0adf167bd4f0cd6a3	Node / Cluster	ami-0d6201863776a5083	Node / Cluster
   Europe (Frankfurt)	ami-0de2f06554fae0ea5	Node / Cluster	ami-0de6fa2dba53f47b3	Node / Cluster
   US East (N. Virginia)	ami-01bf06f15f659cb53	Node / Cluster	ami-05052f9d9041541f9	Node / Cluster
   US East (Ohio)	ami-03a9d374fe902e1f2	Node / Cluster	ami-07b3948494745902b	Node / Cluster
   US West (N. California)	ami-0683abf43803a2457	Node / Cluster	ami-0db41939aedb60f2d	Node / Cluster
   US West (Oregon)	ami-004579f7c9fb6bee5	Node / Cluster	ami-0f9f9ebc8f6e6d208	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