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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-0ebbb18896e72dd98	Node / Cluster	ami-0e4369e0d7d5d1b8a	Node / Cluster
   Africa (Cape Town)	ami-0857bd4dc1473a82d	Node / Cluster	ami-0d5a7b7436672f8d8	Node / Cluster
   Asia Pacific (Mumbai)	ami-0fef439c33b806075	Node / Cluster	ami-04d317234d33ba01b	Node / Cluster
   Europe (Stockholm)	ami-01dc85feaf68b84ee	Node / Cluster	ami-02f90e7f5f17b93c8	Node / Cluster
   Europe (Paris)	ami-0c2a522b5655051f0	Node / Cluster	ami-05fc1ab648011f771	Node / Cluster
   Europe (Milan)	ami-05a6992bd87fe726b	Node / Cluster	ami-023d20495a66e981d	Node / Cluster
   Europe (London)	ami-06ad3287294a8649e	Node / Cluster	ami-0bf635b375a2e9869	Node / Cluster
   Europe (Ireland)	ami-042cf427f1f1d219e	Node / Cluster	ami-07c226d5b1d369370	Node / Cluster
   Asia Pacific (Osaka)	ami-033097fc6f8de9123	Node / Cluster	ami-0ab8d729075481212	Node / Cluster
   Asia Pacific (Seoul)	ami-0c0739753dc29744b	Node / Cluster	ami-0a04db19fad3e87e7	Node / Cluster
   Middle East (Bahrain)	ami-0e90cf4277fded9c6	Node / Cluster	ami-027ad1d8683f752f7	Node / Cluster
   Asia Pacific (Tokyo)	ami-0f9a027b9b6b77ad7	Node / Cluster	ami-02771d4d13879dc74	Node / Cluster
   Israel (Tel Aviv)	ami-0a08a0bd5441e516c	Node / Cluster	ami-045ca4cc88b8e2f96	Node / Cluster
   Canada (Central)	ami-0dc669bce872cf1b3	Node / Cluster	ami-0bff155885827893c	Node / Cluster
   South America (Sao Paulo)	ami-06c45bf50ea931843	Node / Cluster	ami-0dc4f962f3db28255	Node / Cluster
   Asia Pacific (Hong Kong)	ami-09142640304f63369	Node / Cluster	ami-0e4016f50aed070a9	Node / Cluster
   Asia Pacific (Singapore)	ami-0cf306265f11ac2ae	Node / Cluster	ami-02ac6122c16e9ae86	Node / Cluster
   Asia Pacific (Sydney)	ami-064413cf4ab5c63fe	Node / Cluster	ami-092dc89c0f2974b63	Node / Cluster
   Europe (Frankfurt)	ami-0b0652d03fa43b9cf	Node / Cluster	ami-0071e1ddca9a06dcb	Node / Cluster
   US East (N. Virginia)	ami-09f0407918fe2a485	Node / Cluster	ami-0a5c3c8ffba116feb	Node / Cluster
   US East (Ohio)	ami-0f23a566687932ff4	Node / Cluster	ami-099d4ece49abbb697	Node / Cluster
   US West (N. California)	ami-0b3caa9271fb4247b	Node / Cluster	ami-022b091c645fb976d	Node / Cluster
   US West (Oregon)	ami-04f04eeb8e44d46a3	Node / Cluster	ami-016391420761e9e97	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