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.

   2024.2.12¶

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-059ca19d8a2b96a46	Node / Cluster	ami-0dbb91efb6130d041	Node / Cluster
   Africa (Cape Town)	ami-01b4255af24c2cba3	Node / Cluster	ami-0cca66a4bdb463b66	Node / Cluster
   Asia Pacific (Mumbai)	ami-01260c022c144e21a	Node / Cluster	ami-076c5dd71dc340464	Node / Cluster
   Europe (Stockholm)	ami-0286f2638ba4a760e	Node / Cluster	ami-08e293c9d38757df5	Node / Cluster
   Europe (Paris)	ami-0d25ba09e94ffd921	Node / Cluster	ami-00b0dcbdf6bc09fd1	Node / Cluster
   Europe (Milan)	ami-0bfefdddf2c5bc484	Node / Cluster	ami-0e6faf70935e233f0	Node / Cluster
   Europe (London)	ami-0eae3de5832fe7773	Node / Cluster	ami-021e2635e6edbb334	Node / Cluster
   Europe (Ireland)	ami-0426d9639cca4fa38	Node / Cluster	ami-0378291657344c71c	Node / Cluster
   Asia Pacific (Osaka)	ami-0304fb0f694cff0a2	Node / Cluster	ami-08fead06b41ea06cf	Node / Cluster
   Asia Pacific (Seoul)	ami-0613a9e4e18a88e65	Node / Cluster	ami-0e025e044f0897590	Node / Cluster
   Middle East (Bahrain)	ami-06dfa17b1b303a73a	Node / Cluster	ami-0bcf03c7799394cf9	Node / Cluster
   Asia Pacific (Tokyo)	ami-035beb7e2234c9be5	Node / Cluster	ami-0d29f38ed4806138e	Node / Cluster
   Israel (Tel Aviv)	ami-0e9c47ac330126358	Node / Cluster	ami-020c7d2b1c72ce516	Node / Cluster
   Canada (Central)	ami-0775acffc2c5532bf	Node / Cluster	ami-0d99b701b54fe660f	Node / Cluster
   South America (Sao Paulo)	ami-048d7c23fb1a94696	Node / Cluster	ami-0370d38c5a51686d3	Node / Cluster
   Asia Pacific (Hong Kong)	ami-078b732ce781f1b7f	Node / Cluster	ami-0bdc3024002099da4	Node / Cluster
   Asia Pacific (Singapore)	ami-09b88e539248bbcf3	Node / Cluster	ami-0b389cebe68eff6e2	Node / Cluster
   Asia Pacific (Sydney)	ami-01ac6520fef5d0e56	Node / Cluster	ami-00be43e1a9db3dc33	Node / Cluster
   Europe (Frankfurt)	ami-0f2ab06f94b386c64	Node / Cluster	ami-009622ce4666366e4	Node / Cluster
   Asia Pacific (Jakarta)	ami-02b21b9c7885479be	Node / Cluster	ami-0e512b01a0e3f205d	Node / Cluster
   US East (N. Virginia)	ami-04ebdf3f73c237cbb	Node / Cluster	ami-02384f5d98550556d	Node / Cluster
   US East (Ohio)	ami-0b68927d8b1408522	Node / Cluster	ami-077b5c302e88e76ef	Node / Cluster
   US West (N. California)	ami-00ee35f8fb49eb9ab	Node / Cluster	ami-0e6fcdd8cd3aefe92	Node / Cluster
   US West (Oregon)	ami-01eda0b8331df1a7a	Node / Cluster	ami-0e753d1c7d8f3c6e6	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. Configure Security Group. Make sure all ScyllaDB ports are open.

7. Click Launch Cluster. You now have a running ScyllaDB cluster on EC2.

8. 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