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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-0f35322268c5ba278	Node / Cluster	ami-01bde2099f824a57c	Node / Cluster
   Africa (Cape Town)	ami-0f276938ab36f3fa0	Node / Cluster	ami-0543495f89bcfd503	Node / Cluster
   Asia Pacific (Mumbai)	ami-0d0d5c016ddd5419c	Node / Cluster	ami-007c3c653a13b4ab8	Node / Cluster
   Europe (Stockholm)	ami-03660566a384aac10	Node / Cluster	ami-02a53af101acf3236	Node / Cluster
   Europe (Paris)	ami-0291ddfb5b7b2f536	Node / Cluster	ami-0f93a4aef86a5a4d9	Node / Cluster
   Europe (Milan)	ami-0a1cd91f303be42f9	Node / Cluster	ami-00f1fa555561ecfb2	Node / Cluster
   Europe (London)	ami-0944bb8ed9dda0a3d	Node / Cluster	ami-06cdaeb14013085c6	Node / Cluster
   Europe (Ireland)	ami-0767ab8c7873b924e	Node / Cluster	ami-01f6e65cf910f80f2	Node / Cluster
   Asia Pacific (Osaka)	ami-09aa3c07df9337b26	Node / Cluster	ami-0dde63e5b9dc74a8e	Node / Cluster
   Asia Pacific (Seoul)	ami-093bf5d867c231b08	Node / Cluster	ami-080022986f71e08f4	Node / Cluster
   Asia Pacific (Tokyo)	ami-0f71e8f72f04967ab	Node / Cluster	ami-0d3d5ed9873cad948	Node / Cluster
   Israel (Tel Aviv)	ami-0dbdf466f93f228aa	Node / Cluster	ami-02a5a94f9f08b6928	Node / Cluster
   Canada (Central)	ami-0b067226949dd922a	Node / Cluster	ami-0ab7754e97430d774	Node / Cluster
   South America (Sao Paulo)	ami-009124c7b9b461b7c	Node / Cluster	ami-0a401d8b9ba109cea	Node / Cluster
   Asia Pacific (Hong Kong)	ami-082fdcb384acdd2b8	Node / Cluster	ami-0e290524d7a32cffe	Node / Cluster
   Asia Pacific (Singapore)	ami-033d667d97ca83a06	Node / Cluster	ami-05ec8d302a9bd45a4	Node / Cluster
   Asia Pacific (Sydney)	ami-02cbe31b1ddd0901f	Node / Cluster	ami-003cd0512be1ccf6b	Node / Cluster
   Europe (Frankfurt)	ami-0336e8260aed07156	Node / Cluster	ami-086bf1f3572f4e0db	Node / Cluster
   US East (N. Virginia)	ami-0d856178eae477e72	Node / Cluster	ami-04dfd8ce1aba6d5cb	Node / Cluster
   US East (Ohio)	ami-02fca47b8c9d9ebbf	Node / Cluster	ami-08756af720c16d265	Node / Cluster
   US West (N. California)	ami-0cb62cf90aa0730c3	Node / Cluster	ami-07e09ab20208372c3	Node / Cluster
   US West (Oregon)	ami-08ba9378e03780196	Node / Cluster	ami-0d16ae42c817879ad	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