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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-000c6bc5b48b5da23	Node / Cluster	ami-0ff23498a5d733900	Node / Cluster
   Africa (Cape Town)	ami-047fa071c1162cb51	Node / Cluster	ami-08004816296e28860	Node / Cluster
   Asia Pacific (Mumbai)	ami-04e71c4ccf481e742	Node / Cluster	ami-09bf2a3d72b8d04e5	Node / Cluster
   Europe (Stockholm)	ami-0794c248351a68a21	Node / Cluster	ami-0bf7a3503def2a04d	Node / Cluster
   Europe (Paris)	ami-004e29054009005f7	Node / Cluster	ami-00550d0ad0b61802c	Node / Cluster
   Europe (Milan)	ami-0bc7912f75f1cc268	Node / Cluster	ami-052934735a66cd9b0	Node / Cluster
   Europe (London)	ami-04fc2211b0fd26091	Node / Cluster	ami-0fb26ba3bdf5f4894	Node / Cluster
   Europe (Ireland)	ami-0e22094fd39de84f7	Node / Cluster	ami-04484a6b1108ffd40	Node / Cluster
   Asia Pacific (Osaka)	ami-08dc66b7222d88a3c	Node / Cluster	ami-06b410a06ecd5a791	Node / Cluster
   Asia Pacific (Seoul)	ami-02552b462efe56a05	Node / Cluster	ami-03b28d7ca5b9a1014	Node / Cluster
   Middle East (Bahrain)	ami-07393df098dfc0bcd	Node / Cluster	ami-034dd2047329a9d91	Node / Cluster
   Asia Pacific (Tokyo)	ami-068ed2ebe363a1862	Node / Cluster	ami-002a98f8aaa9e341d	Node / Cluster
   Israel (Tel Aviv)	ami-0fd89711869cc6077	Node / Cluster	ami-0a7423eb8fa975684	Node / Cluster
   Canada (Central)	ami-020cd749636ba48aa	Node / Cluster	ami-01364c7952e45b732	Node / Cluster
   South America (Sao Paulo)	ami-02700eb68a94894f4	Node / Cluster	ami-0b42f49cd976e5883	Node / Cluster
   Asia Pacific (Hong Kong)	ami-0222765dd4e58fb51	Node / Cluster	ami-07a07c1d5d30efcff	Node / Cluster
   Asia Pacific (Singapore)	ami-04ca9db51746116be	Node / Cluster	ami-0f007f8b7b9a3a19a	Node / Cluster
   Asia Pacific (Sydney)	ami-098cdd2e24344aaa0	Node / Cluster	ami-0cc394e9b8605d5e9	Node / Cluster
   Europe (Frankfurt)	ami-0e84503d09651d278	Node / Cluster	ami-04c09704bf900de79	Node / Cluster
   Asia Pacific (Jakarta)	ami-0ad5793d613e15946	Node / Cluster	ami-05262b4d9f9f1f583	Node / Cluster
   US East (N. Virginia)	ami-071a2aeefeca74230	Node / Cluster	ami-0a2b506840e178553	Node / Cluster
   US East (Ohio)	ami-00d7309bcfdf991a9	Node / Cluster	ami-056778d3d271b8ec9	Node / Cluster
   US West (N. California)	ami-0fe39b395dabd282c	Node / Cluster	ami-03dc7453e3916d379	Node / Cluster
   US West (Oregon)	ami-0cae8a5ae04029370	Node / Cluster	ami-0a861c0c936027cbd	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