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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-005060ae4c15e389c	Node / Cluster	ami-04e5cf320c8db0b46	Node / Cluster
   Africa (Cape Town)	ami-0342c01b6e0b46a5f	Node / Cluster	ami-022943e0378465174	Node / Cluster
   Asia Pacific (Mumbai)	ami-0a090f1bcb9c8714c	Node / Cluster	ami-063bae135fc089150	Node / Cluster
   Europe (Stockholm)	ami-0d93ba9a286812046	Node / Cluster	ami-0bda2a2466b0cabbd	Node / Cluster
   Europe (Paris)	ami-0ca6ac3c62b703dd1	Node / Cluster	ami-08332150e01ec6be2	Node / Cluster
   Europe (Milan)	ami-07040bb8905b7708e	Node / Cluster	ami-055b292950de7e3b7	Node / Cluster
   Europe (London)	ami-0e15fda8bec595eaf	Node / Cluster	ami-0ee15c2793fedf43d	Node / Cluster
   Europe (Ireland)	ami-0f0151ed940f4d549	Node / Cluster	ami-06f0b5f4990fb428c	Node / Cluster
   Asia Pacific (Osaka)	ami-053a37f6f3c3be5bd	Node / Cluster	ami-0adeb13984faf817a	Node / Cluster
   Asia Pacific (Seoul)	ami-066fcec2e21a1c8b2	Node / Cluster	ami-005fcad8c60ffed9c	Node / Cluster
   Middle East (Bahrain)	ami-06de78bdf3b9a2ac2	Node / Cluster	ami-07c0fe8f93e1de78e	Node / Cluster
   Asia Pacific (Tokyo)	ami-075e7cd124f50de84	Node / Cluster	ami-04c5eedb1d3d2b86f	Node / Cluster
   Israel (Tel Aviv)	ami-07f54c55259772c0c	Node / Cluster	ami-02c6ded83645e4d96	Node / Cluster
   Canada (Central)	ami-0004b6be97d136dd4	Node / Cluster	ami-05f817ab968653b81	Node / Cluster
   South America (Sao Paulo)	ami-00874113a460e695d	Node / Cluster	ami-0364e88dbdd5d6cd5	Node / Cluster
   Asia Pacific (Hong Kong)	ami-00788ea8310f90793	Node / Cluster	ami-06a6c1ee299fe4542	Node / Cluster
   Asia Pacific (Singapore)	ami-01a08a55d097a8270	Node / Cluster	ami-0460137584f4b4832	Node / Cluster
   Asia Pacific (Sydney)	ami-0154048b7ddc2941b	Node / Cluster	ami-083df478bfdc5e9be	Node / Cluster
   Europe (Frankfurt)	ami-0142c3dae7b1bc3c3	Node / Cluster	ami-057e8f22b4efbc96d	Node / Cluster
   US East (N. Virginia)	ami-0923c06dd20eabd81	Node / Cluster	ami-07c3351d2e05a44c4	Node / Cluster
   US East (Ohio)	ami-0f6d340d7c9ec8412	Node / Cluster	ami-09300f2d3b21bfb5d	Node / Cluster
   US West (N. California)	ami-09dbaa241a19e793e	Node / Cluster	ami-015c01d6c4760b6fa	Node / Cluster
   US West (Oregon)	ami-091d6db0b554bec13	Node / Cluster	ami-0c91b95ed27de749b	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