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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-021445e535c669558	Node / Cluster	ami-0d4afc966bba58ce4	Node / Cluster
   Africa (Cape Town)	ami-06e97b80d66d3227e	Node / Cluster	ami-00c3165a753f207e2	Node / Cluster
   Asia Pacific (Mumbai)	ami-08e9b87a800593726	Node / Cluster	ami-02e1664a8c00e727a	Node / Cluster
   Europe (Stockholm)	ami-046ab65ce38495289	Node / Cluster	ami-0a1f4e4caab1671fd	Node / Cluster
   Europe (Paris)	ami-07f4ee0883a39fd93	Node / Cluster	ami-08bff890fa1d36145	Node / Cluster
   Europe (Milan)	ami-0b76920502dc2b0df	Node / Cluster	ami-0670dd6fd4893437c	Node / Cluster
   Europe (London)	ami-0092e587a53128dec	Node / Cluster	ami-0dbe10f70d4c3e721	Node / Cluster
   Europe (Ireland)	ami-082351246305cb57f	Node / Cluster	ami-04d8d9fc48661b99e	Node / Cluster
   Asia Pacific (Osaka)	ami-0eeeb8421d518a61f	Node / Cluster	ami-08c1c7e0502255394	Node / Cluster
   Asia Pacific (Seoul)	ami-0b21d1c499d853a26	Node / Cluster	ami-09291b463f5fe15e0	Node / Cluster
   Middle East (Bahrain)	ami-0d0761d140d3b3d37	Node / Cluster	ami-074eab36554b43bf5	Node / Cluster
   Asia Pacific (Tokyo)	ami-0df83151b6d8a471e	Node / Cluster	ami-037daf852eabf242d	Node / Cluster
   Israel (Tel Aviv)	ami-0cbe2a25d09e2724e	Node / Cluster	ami-0bb7de1383b2b2164	Node / Cluster
   Canada (Central)	ami-086f8f6d9f79d2f65	Node / Cluster	ami-0e86d15496985fc49	Node / Cluster
   South America (Sao Paulo)	ami-03365ffe69b3b55b7	Node / Cluster	ami-0510640ad5d79557f	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0e8c965da30443cf5	Node / Cluster	ami-0c44d33c9a476444d	Node / Cluster
   Asia Pacific (Singapore)	ami-0ae8db5771dc92836	Node / Cluster	ami-0d443415b5049ca74	Node / Cluster
   Asia Pacific (Sydney)	ami-082cac445825bc46a	Node / Cluster	ami-015406811681e04f5	Node / Cluster
   Europe (Frankfurt)	ami-0d6144ed44e94ae95	Node / Cluster	ami-098248071ac649abb	Node / Cluster
   Asia Pacific (Jakarta)	ami-07828beb7ddedb67d	Node / Cluster	ami-04436ad474815850f	Node / Cluster
   US East (N. Virginia)	ami-0bad5ab33380c3f3f	Node / Cluster	ami-03cc36bb1893c71ce	Node / Cluster
   US East (Ohio)	ami-029696dea5051353d	Node / Cluster	ami-044a66f8bdd79fb1a	Node / Cluster
   US West (N. California)	ami-09cc4a7a9ac2c548b	Node / Cluster	ami-0849ac28c0eb3fd4b	Node / Cluster
   US West (Oregon)	ami-0c958c3d751bab880	Node / Cluster	ami-047a34898d7925bcf	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