Launch ScyllaDB 2025.4 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.3¶

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-01bc610b33c07270f	Node / Cluster	ami-004229c6cd7ac1581	Node / Cluster
   Africa (Cape Town)	ami-0148ae80a3b61da39	Node / Cluster	ami-026d745f01e895965	Node / Cluster
   Asia Pacific (Mumbai)	ami-02b2c8e56fe3c3673	Node / Cluster	ami-05c01b512ab181ef4	Node / Cluster
   Europe (Stockholm)	ami-0ba6aab5f6c4b5c7d	Node / Cluster	ami-07de4da5b629897c1	Node / Cluster
   Europe (Paris)	ami-061c425b504a78677	Node / Cluster	ami-0e6871893252e3d82	Node / Cluster
   Europe (Milan)	ami-078d219bfa3e2ed77	Node / Cluster	ami-01d298eaaa096f858	Node / Cluster
   Europe (London)	ami-0dbdc2cc11bd3062a	Node / Cluster	ami-005b327d2180fbf21	Node / Cluster
   Europe (Ireland)	ami-06fb506666fc79d06	Node / Cluster	ami-0f8cbe946c546a560	Node / Cluster
   Asia Pacific (Osaka)	ami-060a2885443b3b5e3	Node / Cluster	ami-01b1f98b274c796e1	Node / Cluster
   Asia Pacific (Seoul)	ami-077a84c8fae24819f	Node / Cluster	ami-07147974cfddb25d3	Node / Cluster
   Middle East (Bahrain)	ami-0e40d8786cd9364e7	Node / Cluster	ami-044eada3fd3facaff	Node / Cluster
   Asia Pacific (Tokyo)	ami-074c53d808243644f	Node / Cluster	ami-0dca52152e71783f6	Node / Cluster
   Israel (Tel Aviv)	ami-0a77c81819ed19166	Node / Cluster	ami-0dcee597b51cf7c85	Node / Cluster
   Canada (Central)	ami-0b0fe7967deb5db86	Node / Cluster	ami-0c2a4cb04b7de3047	Node / Cluster
   South America (Sao Paulo)	ami-04e61d933b7ceba44	Node / Cluster	ami-005513a2866ebf2df	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0bb10b271a53ade2b	Node / Cluster	ami-07e15f414d081283a	Node / Cluster
   Asia Pacific (Singapore)	ami-00b0ca6c4a98c28b8	Node / Cluster	ami-06c780825a9f90e34	Node / Cluster
   Asia Pacific (Sydney)	ami-0a6f901b919013bb8	Node / Cluster	ami-082c2d327707fc883	Node / Cluster
   Europe (Frankfurt)	ami-06d23120a34a6b351	Node / Cluster	ami-021246788ba35e1b6	Node / Cluster
   US East (N. Virginia)	ami-00fbf90173fae9245	Node / Cluster	ami-07d0ab6ba23bc1761	Node / Cluster
   US East (Ohio)	ami-0febe491c350cc61c	Node / Cluster	ami-08f77f755e84b94a8	Node / Cluster
   US West (N. California)	ami-0e5092c40491b5305	Node / Cluster	ami-0f4371fd81c2a9497	Node / Cluster
   US West (Oregon)	ami-0d566c547e74be3d1	Node / Cluster	ami-04f66ec62a379e822	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