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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-02808d94e8aa8ae27	Node / Cluster	ami-066f130c5fb6e5003	Node / Cluster
   Africa (Cape Town)	ami-012436f0efe4785e4	Node / Cluster	ami-094ff6fd50c54191b	Node / Cluster
   Asia Pacific (Mumbai)	ami-0a7ddd41a2b54ba27	Node / Cluster	ami-0536f68bf906eebe0	Node / Cluster
   Europe (Stockholm)	ami-02497cbeedca24c8e	Node / Cluster	ami-087cf90e69cfdb9a7	Node / Cluster
   Europe (Paris)	ami-0cc32e1ef1237ed96	Node / Cluster	ami-09a6663170b5f85a8	Node / Cluster
   Europe (Milan)	ami-0f6b98b75314dc981	Node / Cluster	ami-0155a82a55227c264	Node / Cluster
   Europe (London)	ami-0423c11d65ebb877f	Node / Cluster	ami-0bfa6e3b5db36b1f6	Node / Cluster
   Europe (Ireland)	ami-057d569a539778042	Node / Cluster	ami-0561efbae1a80ff9d	Node / Cluster
   Asia Pacific (Osaka)	ami-0de8debf2f3b0f6ce	Node / Cluster	ami-08ea65a5ef4c0b40d	Node / Cluster
   Asia Pacific (Seoul)	ami-05227d4d09c67c845	Node / Cluster	ami-0b8fecaefc696b2bb	Node / Cluster
   Middle East (Bahrain)	ami-0830c585172a8740d	Node / Cluster	ami-06592b17ed368d5ce	Node / Cluster
   Asia Pacific (Tokyo)	ami-017f2e44f3631e2bf	Node / Cluster	ami-0e1d17f88f1dc4878	Node / Cluster
   Israel (Tel Aviv)	ami-0fa94801d0ae82d87	Node / Cluster	ami-03819d4f86494b5e1	Node / Cluster
   Canada (Central)	ami-0779db2df6f762ee4	Node / Cluster	ami-085b52180e8c07cc5	Node / Cluster
   South America (Sao Paulo)	ami-0a44123d9eee4878f	Node / Cluster	ami-0456347dfe8d17069	Node / Cluster
   Asia Pacific (Hong Kong)	ami-073d0bfd15139b794	Node / Cluster	ami-0d08f889ab689a6be	Node / Cluster
   Asia Pacific (Singapore)	ami-037315f421902695f	Node / Cluster	ami-06c93b0dedbf975a7	Node / Cluster
   Asia Pacific (Sydney)	ami-0e6c20be869ad9615	Node / Cluster	ami-039183f545e52fb9a	Node / Cluster
   Europe (Frankfurt)	ami-0781b904c736f8fc7	Node / Cluster	ami-01044c0e52eca156c	Node / Cluster
   Asia Pacific (Jakarta)	ami-047ec433760b0ad78	Node / Cluster	ami-01b97cb4c55752496	Node / Cluster
   US East (N. Virginia)	ami-0b676a2642ece0ba8	Node / Cluster	ami-0a984cbebe85a8091	Node / Cluster
   US East (Ohio)	ami-07fff323e7bf1aa5f	Node / Cluster	ami-07bc01579f20f66f6	Node / Cluster
   US West (N. California)	ami-00bcddd1856cb3fd5	Node / Cluster	ami-073a63255bdf7b1f8	Node / Cluster
   US West (Oregon)	ami-007e265f3f94f2ed8	Node / Cluster	ami-03c710fa25a8f3751	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