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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-01e7120eac20d0cfa	Node / Cluster	ami-0ee16a3de0eaa6b3d	Node / Cluster
   Africa (Cape Town)	ami-075b44601aee859b2	Node / Cluster	ami-02f3ba8c39ea752b0	Node / Cluster
   Asia Pacific (Mumbai)	ami-0eab885ba9f1f993c	Node / Cluster	ami-09c3c4301710374da	Node / Cluster
   Europe (Stockholm)	ami-034c04afd41e45ded	Node / Cluster	ami-0dc27ea411c7c025e	Node / Cluster
   Europe (Paris)	ami-0f17faa27372e8222	Node / Cluster	ami-0de5204ef3d86dd20	Node / Cluster
   Europe (Milan)	ami-05f36c86c493de839	Node / Cluster	ami-08ef601fae34884c1	Node / Cluster
   Europe (London)	ami-00e445f5add6fdf2b	Node / Cluster	ami-017d69b97aa55bc83	Node / Cluster
   Europe (Ireland)	ami-0119e44a807d69413	Node / Cluster	ami-05ae9a0b00a8880f6	Node / Cluster
   Asia Pacific (Osaka)	ami-051088e3d514830e1	Node / Cluster	ami-01da8abc0185d1114	Node / Cluster
   Asia Pacific (Seoul)	ami-098f3fb19670a43c8	Node / Cluster	ami-053eb0cbf7c2f21e6	Node / Cluster
   Middle East (Bahrain)	ami-068c63543286e8f3e	Node / Cluster	ami-053f2a931f82f7bc7	Node / Cluster
   Asia Pacific (Tokyo)	ami-0081b754d1749fc8b	Node / Cluster	ami-05688948eab3d7892	Node / Cluster
   Israel (Tel Aviv)	ami-0746b8885a759a0c3	Node / Cluster	ami-09334c494f7953b33	Node / Cluster
   Canada (Central)	ami-066331a6be03ca59c	Node / Cluster	ami-0b835c9d19691bdcd	Node / Cluster
   South America (Sao Paulo)	ami-0f669f83ca91cd1cb	Node / Cluster	ami-07bc961079521d157	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0735d8d806c3f8fa4	Node / Cluster	ami-0c1cb15f4cd376b15	Node / Cluster
   Asia Pacific (Singapore)	ami-09002b7fa1257f3ac	Node / Cluster	ami-0927f01aa38e0589d	Node / Cluster
   Asia Pacific (Sydney)	ami-08f8032e182589d51	Node / Cluster	ami-07f37daa2c6c5db25	Node / Cluster
   Europe (Frankfurt)	ami-0ab9dd672616d6856	Node / Cluster	ami-07453bcb9492602f0	Node / Cluster
   Asia Pacific (Jakarta)	ami-0670eb4563069be49	Node / Cluster	ami-01625e44c149f2877	Node / Cluster
   US East (N. Virginia)	ami-0aaadc9d29a3fc324	Node / Cluster	ami-0b40d9a9b22024134	Node / Cluster
   US East (Ohio)	ami-075b1ab5f16b2f165	Node / Cluster	ami-06488c6b591a13717	Node / Cluster
   US West (N. California)	ami-0f193da50f79d1bfb	Node / Cluster	ami-0a9825f443a43d613	Node / Cluster
   US West (Oregon)	ami-00cfe33ba9b8a1d66	Node / Cluster	ami-09e3c7fd5b57bd916	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