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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-0be5bb36850865304	Node / Cluster	ami-0018f3ea6a07e596f	Node / Cluster
   Africa (Cape Town)	ami-0fbc74795c7e15752	Node / Cluster	ami-0e508b823ec815407	Node / Cluster
   Asia Pacific (Mumbai)	ami-07f7f30dbf786b7f4	Node / Cluster	ami-09b51f9c5655139e5	Node / Cluster
   Europe (Stockholm)	ami-099a66ae3a3f11fbf	Node / Cluster	ami-07569a16df3385571	Node / Cluster
   Europe (Paris)	ami-073a9853fdede6ffa	Node / Cluster	ami-0545aebb98881e739	Node / Cluster
   Europe (Milan)	ami-028352c65aa36969b	Node / Cluster	ami-019ce41f4dc67fe87	Node / Cluster
   Europe (London)	ami-00d8398f1c1be98d6	Node / Cluster	ami-0540da00c197fbfd0	Node / Cluster
   Europe (Ireland)	ami-089b6b6c90a259c9c	Node / Cluster	ami-0ea9ef8558ae25ea1	Node / Cluster
   Asia Pacific (Osaka)	ami-063382bafc6d55689	Node / Cluster	ami-0df7a03e4e51a4811	Node / Cluster
   Asia Pacific (Seoul)	ami-0bd62984e4f331334	Node / Cluster	ami-057aebe8a1bf0311b	Node / Cluster
   Middle East (Bahrain)	ami-0bf068d4d56ea2d3a	Node / Cluster	ami-0bbce6582b0eeea48	Node / Cluster
   Asia Pacific (Tokyo)	ami-09fef83da0dc512b2	Node / Cluster	ami-0852f2ef1d2d0c697	Node / Cluster
   Israel (Tel Aviv)	ami-03e6f51282bde2cec	Node / Cluster	ami-086d7f647014cc221	Node / Cluster
   Canada (Central)	ami-05a7f6bc6eaada472	Node / Cluster	ami-017ca679af6c04e80	Node / Cluster
   South America (Sao Paulo)	ami-0be5eb49d7d5b597d	Node / Cluster	ami-0504ca0fd698f346e	Node / Cluster
   Asia Pacific (Hong Kong)	ami-09279777dc2b5325d	Node / Cluster	ami-0ce3016c2fe83be15	Node / Cluster
   Asia Pacific (Singapore)	ami-0405add3d1e87325c	Node / Cluster	ami-028b4be028ee65da9	Node / Cluster
   Asia Pacific (Sydney)	ami-0fac4ea3f833a3b5b	Node / Cluster	ami-06dd6d71366c3ee33	Node / Cluster
   Europe (Frankfurt)	ami-02d08bb04e0d8d780	Node / Cluster	ami-035611717d8a19376	Node / Cluster
   US East (N. Virginia)	ami-0d89902cd3911d93f	Node / Cluster	ami-0916037518ac48656	Node / Cluster
   US East (Ohio)	ami-0a9c91afe56d36ce1	Node / Cluster	ami-0065e5609e2ff4006	Node / Cluster
   US West (N. California)	ami-0ae7adea21c46646c	Node / Cluster	ami-0e4d7fc4cef4b94c6	Node / Cluster
   US West (Oregon)	ami-0807cc8cb8cb24a17	Node / Cluster	ami-0f2b51e6ff7a44b46	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