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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-03e13e4ecf1129091	Node / Cluster	ami-052e2a8aa6845bb38	Node / Cluster
   Africa (Cape Town)	ami-0a496d35ede00953b	Node / Cluster	ami-00be4e7d44e880319	Node / Cluster
   Asia Pacific (Mumbai)	ami-00c52349ccd348218	Node / Cluster	ami-0e710dd390112034c	Node / Cluster
   Europe (Stockholm)	ami-033224572443883d6	Node / Cluster	ami-0a35a88bff43b7926	Node / Cluster
   Europe (Paris)	ami-06367325c9c71b443	Node / Cluster	ami-04284c3322f96b019	Node / Cluster
   Europe (Milan)	ami-00bf43865f4feeb1f	Node / Cluster	ami-0bc60980fc67b7d44	Node / Cluster
   Europe (London)	ami-0941f629ede2f858a	Node / Cluster	ami-08eafdfa97030b911	Node / Cluster
   Europe (Ireland)	ami-0bbaceb0ed5918b98	Node / Cluster	ami-00cc8efa2a7179eef	Node / Cluster
   Asia Pacific (Osaka)	ami-0c8336427b78eee7a	Node / Cluster	ami-02fd1cff7013be692	Node / Cluster
   Asia Pacific (Seoul)	ami-020fe538406930103	Node / Cluster	ami-0198fad68dbd3ef3f	Node / Cluster
   Middle East (Bahrain)	ami-0f93cba1e9ce0dd4a	Node / Cluster	ami-03c1986048c71c4a0	Node / Cluster
   Asia Pacific (Tokyo)	ami-0d0ec00399e098136	Node / Cluster	ami-0b4fb7a795957019e	Node / Cluster
   Israel (Tel Aviv)	ami-0715c19a0506020db	Node / Cluster	ami-0a38b8fd710bfefaa	Node / Cluster
   Canada (Central)	ami-0764b80ef2a030aff	Node / Cluster	ami-043ede45f483c7bfc	Node / Cluster
   South America (Sao Paulo)	ami-08d7f20b9ce43086d	Node / Cluster	ami-058f3d5e79e9a3cb8	Node / Cluster
   Asia Pacific (Hong Kong)	ami-010d33620df86f0e5	Node / Cluster	ami-0ba72712466b91567	Node / Cluster
   Asia Pacific (Singapore)	ami-0c035a19ad91496b9	Node / Cluster	ami-0f1c7e4022080efc3	Node / Cluster
   Asia Pacific (Sydney)	ami-01e914f7748cd51e8	Node / Cluster	ami-07e59a4119b8be5f7	Node / Cluster
   Europe (Frankfurt)	ami-00119a0f1e95add21	Node / Cluster	ami-0e7511f73056af265	Node / Cluster
   US East (N. Virginia)	ami-022115938ea3dadc5	Node / Cluster	ami-016e46ade49c1919c	Node / Cluster
   US East (Ohio)	ami-029aa30426cda19fa	Node / Cluster	ami-00fca04c1fbb4a689	Node / Cluster
   US West (N. California)	ami-0dd2b4c193a4848c1	Node / Cluster	ami-0010e8901553347b7	Node / Cluster
   US West (Oregon)	ami-0c3a3c199b875d668	Node / Cluster	ami-0ee436f2b7b8a9e67	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