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

   View image details

   Region	x86 AMI ID	Launch x86	ARM AMI ID	Launch ARM
   Asia Pacific (Hyderabad)	ami-016070e99ff6afd07	Node / Cluster	ami-0b670f946475eea46	Node / Cluster
   Africa (Cape Town)	ami-0e021aa99a4cd0bcf	Node / Cluster	ami-012323a97a9ac22ed	Node / Cluster
   Asia Pacific (Mumbai)	ami-00c07a2a40afb8002	Node / Cluster	ami-0e21393a696e44223	Node / Cluster
   Europe (Stockholm)	ami-0147eda376022e635	Node / Cluster	ami-064e76d446532f339	Node / Cluster
   Europe (Paris)	ami-00a74a19e142439ab	Node / Cluster	ami-0c42d31943fb4add2	Node / Cluster
   Europe (Milan)	ami-06c2e02d952aee67b	Node / Cluster	ami-0ace75ec93a886373	Node / Cluster
   Europe (London)	ami-032a563a2d22d0da1	Node / Cluster	ami-0f75221fc071405e7	Node / Cluster
   Europe (Ireland)	ami-0e7629ce44e511e90	Node / Cluster	ami-0683c253ff1db1a5e	Node / Cluster
   Asia Pacific (Osaka)	ami-01b81a854b625994f	Node / Cluster	ami-0cad5f6253b673271	Node / Cluster
   Asia Pacific (Seoul)	ami-0c5c2cc198fe71cc6	Node / Cluster	ami-094480a8150a9d2b7	Node / Cluster
   Middle East (Bahrain)	ami-00ed757c4e6a20112	Node / Cluster	ami-0c0093363e2c10745	Node / Cluster
   Asia Pacific (Tokyo)	ami-028a70e563392bc11	Node / Cluster	ami-0919564c134394b87	Node / Cluster
   Israel (Tel Aviv)	ami-0ab165b8044b76c96	Node / Cluster	ami-06f78a668c90d253d	Node / Cluster
   Canada (Central)	ami-03cddc166628a9d01	Node / Cluster	ami-098603606c844c530	Node / Cluster
   South America (Sao Paulo)	ami-0273ee341e51f3716	Node / Cluster	ami-0182aed7f6cfbf5ee	Node / Cluster
   Asia Pacific (Hong Kong)	ami-004a46c5ef55c7d0a	Node / Cluster	ami-05d7be2a499cde136	Node / Cluster
   Asia Pacific (Singapore)	ami-0e4b083ff95c32be2	Node / Cluster	ami-0ec66cb0307be4114	Node / Cluster
   Asia Pacific (Sydney)	ami-035d56522c5bf4195	Node / Cluster	ami-06f78b1f6c5c4ba69	Node / Cluster
   Europe (Frankfurt)	ami-079e2554a6e155493	Node / Cluster	ami-040e7be624da6908a	Node / Cluster
   US East (N. Virginia)	ami-07bb579628dfedcd9	Node / Cluster	ami-0c4d6e4e29ff5ec67	Node / Cluster
   US East (Ohio)	ami-0a8ece5310ee3cd91	Node / Cluster	ami-0e435ba4c8f793d00	Node / Cluster
   US West (N. California)	ami-0c821c720e5da0e38	Node / Cluster	ami-0f0ddc16676eb2792	Node / Cluster
   US West (Oregon)	ami-00cc8d0336e7dafae	Node / Cluster	ami-05aa0018dd1c91a46	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