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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-088c1bbeafc555131	Node / Cluster	ami-00b35850fc3f08633	Node / Cluster
   Africa (Cape Town)	ami-09044d67906c71dad	Node / Cluster	ami-074f2949d8e9d8802	Node / Cluster
   Asia Pacific (Mumbai)	ami-0488c9cd994245f3a	Node / Cluster	ami-0a8290bb0bb777fcb	Node / Cluster
   Europe (Stockholm)	ami-0c59f265f8bc9f572	Node / Cluster	ami-0f3e027597e73eac6	Node / Cluster
   Europe (Paris)	ami-01df92b8953817b9c	Node / Cluster	ami-0e169485cfa91a6bf	Node / Cluster
   Europe (Milan)	ami-09f566f9ddd554054	Node / Cluster	ami-0c28b3a0d223b4943	Node / Cluster
   Europe (London)	ami-0291374ad50dd7635	Node / Cluster	ami-0f2ef5ae3cb2faf7e	Node / Cluster
   Europe (Ireland)	ami-07ca85650d3e03620	Node / Cluster	ami-07de9a55b16d226cb	Node / Cluster
   Asia Pacific (Osaka)	ami-0cdd408025d556885	Node / Cluster	ami-0594e3792d92c1dc5	Node / Cluster
   Asia Pacific (Seoul)	ami-0d76fce2c710c61cd	Node / Cluster	ami-0811e7b27324de9bc	Node / Cluster
   Middle East (Bahrain)	ami-0a384482d7273e8d3	Node / Cluster	ami-077105072b76ecd65	Node / Cluster
   Asia Pacific (Tokyo)	ami-0471cc8f01e28454c	Node / Cluster	ami-08f70b5a6e0d66752	Node / Cluster
   Israel (Tel Aviv)	ami-026f4ec88b171dda3	Node / Cluster	ami-078d713ac67e694b3	Node / Cluster
   Canada (Central)	ami-0b13cc94d997098c3	Node / Cluster	ami-07db8813a9b88d444	Node / Cluster
   South America (Sao Paulo)	ami-0fdf5d32fa1493f69	Node / Cluster	ami-0bd8b78be70b72fd1	Node / Cluster
   Asia Pacific (Hong Kong)	ami-03c1984c1b1850593	Node / Cluster	ami-014fd81980ee8ca28	Node / Cluster
   Asia Pacific (Singapore)	ami-0b4dc004ea0763a07	Node / Cluster	ami-024dc3b64cbfa45dd	Node / Cluster
   Asia Pacific (Sydney)	ami-08fe2f990e6cd91b3	Node / Cluster	ami-05a6fff704c74da2f	Node / Cluster
   Europe (Frankfurt)	ami-005cc9c2419b090f7	Node / Cluster	ami-00c1f71b47b898a19	Node / Cluster
   Asia Pacific (Jakarta)	ami-0fc55af99dfb7da1c	Node / Cluster	ami-0d74aff224fb3892e	Node / Cluster
   US East (N. Virginia)	ami-09f335edc26a97cc2	Node / Cluster	ami-046a642ec12377657	Node / Cluster
   US East (Ohio)	ami-01abe9a79cfc82456	Node / Cluster	ami-030d5453138f0424e	Node / Cluster
   US West (N. California)	ami-010e6e78044952ada	Node / Cluster	ami-0a701378430789f0f	Node / Cluster
   US West (Oregon)	ami-0ad19e29d1c8e1d89	Node / Cluster	ami-02aa457480dceb71f	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