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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-076913d37d78086c2	Node / Cluster	ami-0eef3f8368a6d7de5	Node / Cluster
   Africa (Cape Town)	ami-0b77d9d1f5059b812	Node / Cluster	ami-008ba0ad4a6d02231	Node / Cluster
   Asia Pacific (Mumbai)	ami-06f7fda0c3ba180f6	Node / Cluster	ami-0bca28b7b61280be5	Node / Cluster
   Europe (Stockholm)	ami-0a6e27b407b8fa476	Node / Cluster	ami-0e0be009271c5b12a	Node / Cluster
   Europe (Paris)	ami-0487c1895531d6ee3	Node / Cluster	ami-0d1d07075b0524c3a	Node / Cluster
   Europe (Milan)	ami-0a6fd9c5728558c52	Node / Cluster	ami-0e832559505ea42f9	Node / Cluster
   Europe (London)	ami-0c88a9fb1b990f351	Node / Cluster	ami-06394e45981b0799e	Node / Cluster
   Europe (Ireland)	ami-0c7e8aa9d71d48f26	Node / Cluster	ami-0c63dc3450fbd3a52	Node / Cluster
   Asia Pacific (Osaka)	ami-02e51756bb1784b77	Node / Cluster	ami-0d042bd7cdea5a3d6	Node / Cluster
   Asia Pacific (Seoul)	ami-0c54078318474c0eb	Node / Cluster	ami-0de12ca38a8509b43	Node / Cluster
   Middle East (Bahrain)	ami-0de64ef50e7c9ee4b	Node / Cluster	ami-084c561424adb4d62	Node / Cluster
   Asia Pacific (Tokyo)	ami-0feab9eec1a58e249	Node / Cluster	ami-029c8a09361c98c9d	Node / Cluster
   Israel (Tel Aviv)	ami-071ec643c336a04cf	Node / Cluster	ami-0467fda2d29ec4e9e	Node / Cluster
   Canada (Central)	ami-011f8f8a9160e23b5	Node / Cluster	ami-005fd415682b6feb8	Node / Cluster
   South America (Sao Paulo)	ami-03459e52d6f64e548	Node / Cluster	ami-023de9e10623f394c	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0eee3b60a58c0684f	Node / Cluster	ami-03c76f52618db5084	Node / Cluster
   Asia Pacific (Singapore)	ami-0966a700f6a3ab719	Node / Cluster	ami-00c40a5adfd469774	Node / Cluster
   Asia Pacific (Sydney)	ami-0340bae000d620391	Node / Cluster	ami-0191db51cd2669dc9	Node / Cluster
   Europe (Frankfurt)	ami-099bd7d10064b24e8	Node / Cluster	ami-0c0da2afddd4ee5a6	Node / Cluster
   US East (N. Virginia)	ami-0d74570489b72a3ec	Node / Cluster	ami-06c96460b66f0f5cc	Node / Cluster
   US East (Ohio)	ami-0949dbede59a56233	Node / Cluster	ami-08219ad6e0e1a07b7	Node / Cluster
   US West (N. California)	ami-07183bdb79af6b724	Node / Cluster	ami-06e836f56df336721	Node / Cluster
   US West (Oregon)	ami-0bb4eb69a20768f59	Node / Cluster	ami-088f2c70b161aaaed	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