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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-0e5e2e7b19fb3e217	Node / Cluster	ami-0d33c6731fa2eda0a	Node / Cluster
   Africa (Cape Town)	ami-04129b1281390af55	Node / Cluster	ami-04db9612322feea95	Node / Cluster
   Asia Pacific (Mumbai)	ami-047072cd0eef3ee13	Node / Cluster	ami-0c0b38c8db3cc34a8	Node / Cluster
   Europe (Stockholm)	ami-0cf74c21848886c7d	Node / Cluster	ami-0ce129eb3b4b76478	Node / Cluster
   Europe (Paris)	ami-0e5e525bef2ff6bcb	Node / Cluster	ami-0e7bedb7beca6497f	Node / Cluster
   Europe (Milan)	ami-0f24346ae8061ec3d	Node / Cluster	ami-0c31b0bcf1b73029a	Node / Cluster
   Europe (London)	ami-0d755df54f7378b2d	Node / Cluster	ami-0287af6dff4daee77	Node / Cluster
   Europe (Ireland)	ami-06d65505fd7d034eb	Node / Cluster	ami-006509d1d81f3b4c0	Node / Cluster
   Asia Pacific (Osaka)	ami-002d29cf7845f24d1	Node / Cluster	ami-0355b8fedc0bc2019	Node / Cluster
   Asia Pacific (Seoul)	ami-016d4611d438e8669	Node / Cluster	ami-01c0a220e539ded38	Node / Cluster
   Asia Pacific (Tokyo)	ami-033dbb6551d1a4ade	Node / Cluster	ami-05f6fa11de5655f1f	Node / Cluster
   Israel (Tel Aviv)	ami-0d3826b0898d2505d	Node / Cluster	ami-0912942c6125047fc	Node / Cluster
   Canada (Central)	ami-070812189b6285ac7	Node / Cluster	ami-06e59814a42b52a18	Node / Cluster
   South America (Sao Paulo)	ami-0d68d68a4d80b96b6	Node / Cluster	ami-00722e3f9bc173b9c	Node / Cluster
   Asia Pacific (Hong Kong)	ami-07b4ce957cc41769c	Node / Cluster	ami-07dbafb0b2a1ad43a	Node / Cluster
   Asia Pacific (Singapore)	ami-047b4e9857b4b45bd	Node / Cluster	ami-0087480f1b32f533b	Node / Cluster
   Asia Pacific (Sydney)	ami-0eef0bf3f8a927eab	Node / Cluster	ami-017c622f6e6b2b3b6	Node / Cluster
   Europe (Frankfurt)	ami-04d7eea2fc6701b86	Node / Cluster	ami-0885457c2586937f1	Node / Cluster
   US East (N. Virginia)	ami-0e2b93b41836da970	Node / Cluster	ami-0c0631eee69b89dc9	Node / Cluster
   US East (Ohio)	ami-0c0d4602e163aa58e	Node / Cluster	ami-042db896cca81d0f7	Node / Cluster
   US West (N. California)	ami-019ae1753a7239c1f	Node / Cluster	ami-08c47cf50a797876b	Node / Cluster
   US West (Oregon)	ami-039a07d5190fac8eb	Node / Cluster	ami-05402741ea527f328	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