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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-07d4b390e642a2a5b	Node / Cluster	ami-0d95c05c75cfbba9a	Node / Cluster
   Africa (Cape Town)	ami-02309d1a317e89501	Node / Cluster	ami-049514eda03c22b4c	Node / Cluster
   Asia Pacific (Mumbai)	ami-07320abdebdf0bc08	Node / Cluster	ami-06f7f4dcc8dac072b	Node / Cluster
   Europe (Stockholm)	ami-0ec116423d7f9fe68	Node / Cluster	ami-04cbb1674e39fe34b	Node / Cluster
   Europe (Paris)	ami-0a72f0adde4e004f4	Node / Cluster	ami-02feba28e2a87323b	Node / Cluster
   Europe (Milan)	ami-01985644963c3db4a	Node / Cluster	ami-0534ff1c1db6c5f46	Node / Cluster
   Europe (London)	ami-01035c7eafe7469c9	Node / Cluster	ami-0a0a6e01f7ce90a1b	Node / Cluster
   Europe (Ireland)	ami-0322d83f74c9a2ccc	Node / Cluster	ami-0b026ea5de7e23e8a	Node / Cluster
   Asia Pacific (Osaka)	ami-0ba994f625ba3e8b1	Node / Cluster	ami-067b7a18c1e67a773	Node / Cluster
   Asia Pacific (Seoul)	ami-0d9f6b02e1a596be4	Node / Cluster	ami-07330a56cf3ebf272	Node / Cluster
   Middle East (Bahrain)	ami-060903380d5c82f19	Node / Cluster	ami-0bdc180c06c572b5a	Node / Cluster
   Asia Pacific (Tokyo)	ami-052a4e03c0c644ea3	Node / Cluster	ami-022a379c22d32852d	Node / Cluster
   Israel (Tel Aviv)	ami-0ddae7630cf7864fa	Node / Cluster	ami-0b492a8a77f547719	Node / Cluster
   Canada (Central)	ami-088079ec130900aca	Node / Cluster	ami-037d8369482b62429	Node / Cluster
   South America (Sao Paulo)	ami-0256afc04f7686bdc	Node / Cluster	ami-0e4081b976f1fbfe0	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0eb8070e17ada2990	Node / Cluster	ami-09f274b6b3270c346	Node / Cluster
   Asia Pacific (Singapore)	ami-00393a82e7eab9f60	Node / Cluster	ami-0379592fdaa0a5156	Node / Cluster
   Asia Pacific (Sydney)	ami-01225d251877f39c8	Node / Cluster	ami-0db2397a7e10a663b	Node / Cluster
   Europe (Frankfurt)	ami-08501dd1bbabfdb95	Node / Cluster	ami-04baac6189f67dd0e	Node / Cluster
   US East (N. Virginia)	ami-0b3a26a0b20187917	Node / Cluster	ami-09c636a303767abe6	Node / Cluster
   US East (Ohio)	ami-0bf666d90a8d42789	Node / Cluster	ami-05b74fa42e95306c8	Node / Cluster
   US West (N. California)	ami-0fdf3eaf4b7889540	Node / Cluster	ami-0876451a126798061	Node / Cluster
   US West (Oregon)	ami-0e2314d10d9492e6b	Node / Cluster	ami-0aeadab6e027fee96	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