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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-09829aac8b950459a	Node / Cluster	ami-01a9aea4251611ad6	Node / Cluster
   Africa (Cape Town)	ami-0d953d0f5b2397b17	Node / Cluster	ami-0ab86001ef223a366	Node / Cluster
   Asia Pacific (Mumbai)	ami-0735aa2b8c1388155	Node / Cluster	ami-0a8f7638a36b0c6dd	Node / Cluster
   Europe (Stockholm)	ami-00f0770dfe6dc17a4	Node / Cluster	ami-03542b2da9f87017d	Node / Cluster
   Europe (Paris)	ami-0a5b79cbb20206187	Node / Cluster	ami-0b12cedda38c49f51	Node / Cluster
   Europe (Milan)	ami-0fa90ebe494f05dbe	Node / Cluster	ami-03bd8a5518b1c40c4	Node / Cluster
   Europe (London)	ami-05c7d55c336dd93cc	Node / Cluster	ami-01a2cda043d74ec40	Node / Cluster
   Europe (Ireland)	ami-0165289daf1e70077	Node / Cluster	ami-0fef8a43e75fc3713	Node / Cluster
   Asia Pacific (Osaka)	ami-070dcc375c8a339ea	Node / Cluster	ami-0c1d5859bfed22917	Node / Cluster
   Asia Pacific (Seoul)	ami-0a0bfc5bd836f54b2	Node / Cluster	ami-0fc99f2b9bfd21cfe	Node / Cluster
   Middle East (Bahrain)	ami-097f0231b14e22558	Node / Cluster	ami-0e6058309111366e7	Node / Cluster
   Asia Pacific (Tokyo)	ami-073f4cf9fed153150	Node / Cluster	ami-046f1926a7623ad6c	Node / Cluster
   Israel (Tel Aviv)	ami-00954370df374fbd0	Node / Cluster	ami-039b8a12e37e2b233	Node / Cluster
   Canada (Central)	ami-04f2d2cb9fa98124c	Node / Cluster	ami-064f572a9387ec4ac	Node / Cluster
   South America (Sao Paulo)	ami-0b57f4cfbecb3ebef	Node / Cluster	ami-0ea532d0f98714f65	Node / Cluster
   Asia Pacific (Hong Kong)	ami-07c93c71486fcf094	Node / Cluster	ami-09bce1292618c4720	Node / Cluster
   Asia Pacific (Singapore)	ami-079935912b0be7603	Node / Cluster	ami-09f32e6ce1097a998	Node / Cluster
   Asia Pacific (Sydney)	ami-09f55b72aa586ec96	Node / Cluster	ami-0c19e3323577b6fce	Node / Cluster
   Europe (Frankfurt)	ami-060b390c12cbc2f97	Node / Cluster	ami-0bf8a8df5cb59be6c	Node / Cluster
   US East (N. Virginia)	ami-02e522d092fcb8c07	Node / Cluster	ami-0d0cf807ce676be14	Node / Cluster
   US East (Ohio)	ami-058b5577be0b5500a	Node / Cluster	ami-0596a4798a7f755d8	Node / Cluster
   US West (N. California)	ami-017619d4baf5425e9	Node / Cluster	ami-06189fb61aeeb9300	Node / Cluster
   US West (Oregon)	ami-07f7234468f9ed55e	Node / Cluster	ami-063ed13a964de93d7	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