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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-05b651014f596129b	Node / Cluster	ami-0de1aa295e76b6f84	Node / Cluster
   Africa (Cape Town)	ami-0cff449c60ef75331	Node / Cluster	ami-096107202ecf78bbe	Node / Cluster
   Asia Pacific (Mumbai)	ami-0a97c901c0dc92eed	Node / Cluster	ami-044138261eba0f51f	Node / Cluster
   Europe (Stockholm)	ami-0c9a9a1e226ed04d9	Node / Cluster	ami-023e007297380de63	Node / Cluster
   Europe (Paris)	ami-0b1a3cb20a71372e1	Node / Cluster	ami-01fc6608256147db5	Node / Cluster
   Europe (Milan)	ami-0785f85e5dff7caef	Node / Cluster	ami-0c8d4ad8284946f78	Node / Cluster
   Europe (London)	ami-09ca3cd9a0a94f457	Node / Cluster	ami-00bfa4b94aa280b2c	Node / Cluster
   Europe (Ireland)	ami-02c5ed3eb64d52fe7	Node / Cluster	ami-00a4e17a4c9ac78f0	Node / Cluster
   Asia Pacific (Osaka)	ami-0692a30fc3dfc6f5f	Node / Cluster	ami-0475b38ebc5aae936	Node / Cluster
   Asia Pacific (Seoul)	ami-00dc8cddae7501e76	Node / Cluster	ami-0a2311a1964ff2787	Node / Cluster
   Middle East (Bahrain)	ami-0a451c1bfa4b7a7d9	Node / Cluster	ami-03f4b5f1d33b3d76f	Node / Cluster
   Asia Pacific (Tokyo)	ami-088ec52f905be180a	Node / Cluster	ami-0577abccff5649304	Node / Cluster
   Israel (Tel Aviv)	ami-0e4093e8c547c7001	Node / Cluster	ami-02549c97426297482	Node / Cluster
   Canada (Central)	ami-06b0ab65d39a99db2	Node / Cluster	ami-0a4209523a01610e0	Node / Cluster
   South America (Sao Paulo)	ami-0f13e6e8f99ab1eb3	Node / Cluster	ami-038151eea0e9d693b	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0ea287f90ee563467	Node / Cluster	ami-01ff29b3f0c018c74	Node / Cluster
   Asia Pacific (Singapore)	ami-0255e1e270979928c	Node / Cluster	ami-01199b3966d110547	Node / Cluster
   Asia Pacific (Sydney)	ami-0c17d644bb10094f2	Node / Cluster	ami-0bb3e697e98ca3cd5	Node / Cluster
   Europe (Frankfurt)	ami-0db42710b70ea6123	Node / Cluster	ami-009e753c3dbbea048	Node / Cluster
   US East (N. Virginia)	ami-0104d468c52de7a15	Node / Cluster	ami-0f1e276545dde7f58	Node / Cluster
   US East (Ohio)	ami-02ea30f5f4422e58c	Node / Cluster	ami-0c12e9ac485caeda0	Node / Cluster
   US West (N. California)	ami-028d67519c0f97c84	Node / Cluster	ami-0aaa56b40472d958c	Node / Cluster
   US West (Oregon)	ami-0326b4adc1d284441	Node / Cluster	ami-0e2b75435d47026b1	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