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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-00a7351d1a4e0a689	Node / Cluster	ami-00db824b9ca7f5ec4	Node / Cluster
   Africa (Cape Town)	ami-0651ac15ef57d3e64	Node / Cluster	ami-0e8224351414779b6	Node / Cluster
   Asia Pacific (Mumbai)	ami-09520dbfe8936a65b	Node / Cluster	ami-076db5539194b235e	Node / Cluster
   Europe (Stockholm)	ami-0a2fb437d2640e312	Node / Cluster	ami-03b5af16a50040f97	Node / Cluster
   Europe (Paris)	ami-0bbe78dff07315ea0	Node / Cluster	ami-0447837d9d94acfeb	Node / Cluster
   Europe (Milan)	ami-0dc16dacbcbed549d	Node / Cluster	ami-0ab643f3e2c33fd28	Node / Cluster
   Europe (London)	ami-0de5178300155de9f	Node / Cluster	ami-046e254550db63e10	Node / Cluster
   Europe (Ireland)	ami-08f95dda4def7e589	Node / Cluster	ami-0e535137c5aeebafa	Node / Cluster
   Asia Pacific (Osaka)	ami-0f3252ba8aa3f7d0b	Node / Cluster	ami-08ad73110f9a9745f	Node / Cluster
   Asia Pacific (Seoul)	ami-0039360039a6a8964	Node / Cluster	ami-07b925935e294e762	Node / Cluster
   Middle East (Bahrain)	ami-07984b4c3da7f7d79	Node / Cluster	ami-05eca6ad686d2b834	Node / Cluster
   Asia Pacific (Tokyo)	ami-0fc719459e7331b65	Node / Cluster	ami-07b5a5bfebafe5b18	Node / Cluster
   Israel (Tel Aviv)	ami-0578dfe2175d09ed8	Node / Cluster	ami-0fed357f5bb32785e	Node / Cluster
   Canada (Central)	ami-0955d02fbf634e945	Node / Cluster	ami-0780f6d26d7fa1a45	Node / Cluster
   South America (Sao Paulo)	ami-05461fea4e98e309e	Node / Cluster	ami-0401915585e4d4d89	Node / Cluster
   Asia Pacific (Hong Kong)	ami-02ae721acf1d0e322	Node / Cluster	ami-012fefa869573e5e5	Node / Cluster
   Asia Pacific (Singapore)	ami-08a6a98f6598d6bee	Node / Cluster	ami-0be4cf3b81bdafdfe	Node / Cluster
   Asia Pacific (Sydney)	ami-0d6fb4dba9203df58	Node / Cluster	ami-05773a2d87f9f44dc	Node / Cluster
   Europe (Frankfurt)	ami-089bb0ce261cdfa84	Node / Cluster	ami-0dc6590e684f990ea	Node / Cluster
   US East (N. Virginia)	ami-0c357fec0fb4862d9	Node / Cluster	ami-0c2e82675c0d49306	Node / Cluster
   US East (Ohio)	ami-0caa2fcf574dc9280	Node / Cluster	ami-0dbe87e4e4da2cbce	Node / Cluster
   US West (N. California)	ami-0104a6a3599d4c6e2	Node / Cluster	ami-0f863b25f164c0021	Node / Cluster
   US West (Oregon)	ami-001a3efd7a000f7f1	Node / Cluster	ami-06b21af73e049b154	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