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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-071f0898cde517af0	Node / Cluster	ami-03c0f21b229f0bdae	Node / Cluster
   Africa (Cape Town)	ami-0be7bd9a73b253e48	Node / Cluster	ami-0962a76a2404fedde	Node / Cluster
   Asia Pacific (Mumbai)	ami-00274c1717428d383	Node / Cluster	ami-0230e30dab92a78ab	Node / Cluster
   Europe (Stockholm)	ami-0dcdce3d084e1173f	Node / Cluster	ami-06fe6efc086f998e1	Node / Cluster
   Europe (Paris)	ami-0f5fb92d4cc3676a3	Node / Cluster	ami-0d2247356b11bb692	Node / Cluster
   Europe (Milan)	ami-01949daa67def03f9	Node / Cluster	ami-06851a006b46d3907	Node / Cluster
   Europe (London)	ami-02a1bfc043b3dc92c	Node / Cluster	ami-0c582fce1936fb89f	Node / Cluster
   Europe (Ireland)	ami-08188a4bc84f9d7e4	Node / Cluster	ami-0b599b2aaf37d09e8	Node / Cluster
   Asia Pacific (Osaka)	ami-0dd76977cea7549bb	Node / Cluster	ami-01bd9d416d0a7fe7f	Node / Cluster
   Asia Pacific (Seoul)	ami-0df3af24db1d12995	Node / Cluster	ami-0a3c754d32b09851c	Node / Cluster
   Middle East (Bahrain)	ami-02459ab456971fb6c	Node / Cluster	ami-0b034e56a0e5b1a04	Node / Cluster
   Asia Pacific (Tokyo)	ami-057f33621473bb40c	Node / Cluster	ami-0db3ae563ea37ed18	Node / Cluster
   Israel (Tel Aviv)	ami-0c58b90aeb3ea8034	Node / Cluster	ami-05ef3e1b6abe18798	Node / Cluster
   Canada (Central)	ami-0ac4f97344f149591	Node / Cluster	ami-0a3293c58c0aa9b76	Node / Cluster
   South America (Sao Paulo)	ami-01457961976f07e69	Node / Cluster	ami-0f9dc494e576bf6fd	Node / Cluster
   Asia Pacific (Hong Kong)	ami-025402789031c1ab4	Node / Cluster	ami-00ecb703b5fe274df	Node / Cluster
   Asia Pacific (Singapore)	ami-0742df3fc95026686	Node / Cluster	ami-0695ee362fde0c769	Node / Cluster
   Asia Pacific (Sydney)	ami-043d55341f9fca220	Node / Cluster	ami-057d9c7a7056189b9	Node / Cluster
   Europe (Frankfurt)	ami-002671447461e1874	Node / Cluster	ami-0ba9696303f3dbb8a	Node / Cluster
   US East (N. Virginia)	ami-00fbe11ef5eedad78	Node / Cluster	ami-03cd70bfaa72b7e2b	Node / Cluster
   US East (Ohio)	ami-0427e1171c5eb0d58	Node / Cluster	ami-07e27aab6259e2075	Node / Cluster
   US West (N. California)	ami-0edf442b3405b7d43	Node / Cluster	ami-0cce170a481688a2c	Node / Cluster
   US West (Oregon)	ami-072ce522fd27d60c2	Node / Cluster	ami-0c5d95f911a63efe5	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